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.
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
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.
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
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
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.
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.
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.