Can folks pick up https://rcn-ee.net/rootfs/bb.org/testing/2018-04-15/buster-iot/bone-debian-buster-iot-armhf-2018-04-15-4gb.img.xz for BeagleBone Blue and report issues? You might want to also do: ‘sudo apt-get update && sudo apt-get upgrade -y’ to get the very latest.
Please report issues here and https://github.com/StrawsonDesign/Robotics_Cape_Installer.
I found a typo…
–Mark
I found a typo…
Here’s the source line with the typo:
https://github.com/StrawsonDesign/Robotics_Cape_Installer/blob/628d329da7bfc6fb5a37b79664ebbd558310e856/debian/templates#L5
Don’t think we need to have this fixed necessarily before making the latest-images release, but this is where we can make the pull request to if James doesn’t fix it himself.
fixed in commit 08f600eb473a3cbc3fdf4ec0113f5269650a060a
I like these easy ones ^.^
I loaded the image on a BeagleBone Black and ran sudo apt-get update && sudo apt-get upgrade -y’
The attached file shows the boot sequence.
What did I do wrong?
–Mark
screenlog.0 (21.7 KB)
V0.4.1 out and pretty damn reliable for me now: https://github.com/StrawsonDesign/Robotics_Cape_Installer/releases/tag/v0.4.1
I liked the led-drivers implementation in the Blue device tree so much I merged it back into my roboticscape device tree for Black and Black wireless. I also enabled the IIO ADC driver to keep things consistent. Right now I’ve just been playing on 4.9, are there any big changes I should know about in 4.14 regarding the device tree on the Blue? Also, are we even supporting 4.4 now?
Robert: I have the following pull requests for you. The first is for the device trees in 4.9. The second is for an ancient issue that didn’t really effect me until now in am335x_evm.sh
https://github.com/beagleboard/linux/pull/160
https://github.com/RobertCNelson/boot-scripts/pull/82
With the above two pull requests we are finally back to the following on black-roboticscape black-wireless-roboticscape and blue:
debian@beaglebone:~$ rc_test_drivers
Kernel: 4.9.88-ti-r110
BeagleBoard.org Debian Image 2018-03-05
Debian: 9.4
PASSED: gpio 0
PASSED: gpio 1
PASSED: gpio 2
PASSED: gpio 3
PASSED: pwm1
PASSED: pwm2
PASSED: eqep0
PASSED: eqep1
PASSED: eqep2
PASSED: pru-rproc
PASSED: uart1
PASSED: uart2
PASSED: uart4
PASSED: uart5
PASSED: i2c1
PASSED: i2c2
PASSED: spi
PASSED: LED
PASSED: ADC iio
Side note, is anyone noticing /dev/gpiochip 0&1 get correctly set to the GPIO user group as per udev rules but 2&3 do not? I tried setting them again in the roboticscape systemd service but they still get put back to being owned by root later in the boot process.
~James
Hi James,
Sorry been traveling this week.
V0.4.1 out and pretty damn reliable for me now:
https://github.com/StrawsonDesign/Robotics_Cape_Installer/releases/tag/v0.4.1
pushed out to buster..
I liked the led-drivers implementation in the Blue device tree so much I
merged it back into my roboticscape device tree for Black and Black
wireless. I also enabled the IIO ADC driver to keep things consistent. Right
now I've just been playing on 4.9, are there any big changes I should know
about in 4.14 regarding the device tree on the Blue? Also, are we even
supporting 4.4 now?Robert: I have the following pull requests for you. The first is for the
device trees in 4.9. The second is for an ancient issue that didn't really
effect me until now in am335x_evm.sh
Starting pull..
pulled and pushed out...
With the above two pull requests we are finally back to the following on
black-roboticscape black-wireless-roboticscape and blue:
debian@beaglebone:~$ rc_test_driversKernel: 4.9.88-ti-r110
BeagleBoard.org Debian Image 2018-03-05
Debian: 9.4PASSED: gpio 0
PASSED: gpio 1
PASSED: gpio 2
PASSED: gpio 3
PASSED: pwm1
PASSED: pwm2
PASSED: eqep0
PASSED: eqep1
PASSED: eqep2
PASSED: pru-rproc
PASSED: uart1
PASSED: uart2
PASSED: uart4
PASSED: uart5
PASSED: i2c1
PASSED: i2c2
PASSED: spi
PASSED: LED
PASSED: ADC iioSide note, is anyone noticing /dev/gpiochip 0&1 get correctly set to the
GPIO user group as per udev rules but 2&3 do not? I tried setting them again
in the roboticscape systemd service but they still get put back to being
owned by root later in the boot process.
It's a weird race condition.
Regards,
James,
I tried to upgrade the kernel. When I tried to run rc_test_drivers, I got the following output
Kernel: 4.9.95-bone-rt-r10
BeagleBoard.org Debian Image 2018-03-05
Debian: 9.4
PASSED: gpio 0
PASSED: gpio 1
PASSED: gpio 2
PASSED: gpio 3
PASSED: pwm1
PASSED: pwm2
PASSED: eqep0
PASSED: eqep1
PASSED: eqep2
ERROR: pru-rproc driver not loaded
PASSED: uart1
PASSED: uart2
PASSED: uart4
PASSED: uart5
PASSED: i2c1
PASSED: i2c2
PASSED: spi
ERROR: LED driver not loaded
ERROR: ADC iio driver not loaded
I still do not have the pru driver. Am I doing something wrong?
Thanks,
Li Bai
Pushed some build fixes for beagle-tester based on new API.
That has the wrong pru driver..
https://elinux.org/Beagleboard:BeagleBoneBlack_Debian#4.14.x-ti
https://elinux.org/Beagleboard:BeagleBoneBlack_Debian#U-Boot_PRU_Options
Regards,
Robert,
Thank you for your instruction. I updated the kernel to 4.14-ti. The output from rc_test_driver is as follows:
rc_test_drivers
Kernel: 4.14.37-ti-rt-r46
BeagleBoard.org Debian Image 2018-03-05
Debian: 9.4
PASSED: gpio 0
PASSED: gpio 1
PASSED: gpio 2
PASSED: gpio 3
PASSED: pwm1
PASSED: pwm2
PASSED: eqep0
PASSED: eqep1
PASSED: eqep2
ERROR: pru-rproc driver not loaded
PASSED: uart1
PASSED: uart2
ERROR: uart4 driver not loaded
PASSED: uart5
ERROR: i2c1 driver not loaded
PASSED: i2c2
PASSED: spi
PASSED: LED
ERROR: ADC iio driver not loaded
I still do not have pru-rproc driver loaded. Also, it takes about 2 mins and 30 seconds to initiate an ipaddress 192.168.6.2 on the unit. Please help to see whereI have done wrong. I am attaching the uEnv.txt in the message.
Thanks,
Li Bai
uEnv.txt (2.03 KB)
Robert,
I am not familiar with Beaglebone Blue. When you have time, will you please let me know if I am doing something wrong? I do not know how to enable pru-rproc.
Thanks,
Li Bai
let's see what you got:
sudo /opt/scripts/tools/version.sh
Regards,
Hi Li,
The May 10th image from Robert has been working well for me with all the drivers enabled and working with the included 4.14 kernel.
Best,
James