Hi, I have the exact same problem. I am using the PocketBeagle and the newest image "Debian 9.3 2018-03-05 4GB SD IoT".
When using this image on BeagleBone, everything is working normally, with dmesg I can see that both PRUs are booted successfully, and also I tried to used them with success. Now I am migrating from BeagleBone to the PocketBeagle with the same image. But here the PRUs are not booted at all, the folder /sys/class/remoteproc1 and /sys/class/remoteproc2 are missing ! (not a case with BeagleBone) You wrote to add &pruss_soc_bus to the .dtsi file. But which file exactly? The am335x-pocketbeagle-common.dtsi or ? I tried to add this part of code to the am335x-pocketbeagle-common.dtsi and also to am335x-pocketbeagle.dts and I used "make src/arm/am335x-pocketbeagle.dtb" to update the changes but nothing helps. The PRUs want boot. Help! Kind Regards, Ivan Dana petak, 30. ožujka 2018. u 22:37:42 UTC+2, korisnik RobertCNelson napisao je: > > On Fri, Mar 30, 2018 at 12:56 AM, Jaremy Creechley <[email protected] > <javascript:>> wrote: > > > > I'm working on creating a variant of a Buildroot image using the > > 4.9.82-ti-rt kernel (taken from @RCN's stretch/ sources) and modified to > use > > u-boot overlays. The buildroot image works well on the Beaglebone Green > > (with the PRU's loading much quicker than the 4.4.x branch I'd used > > previously using TI's recently modified `/sys/class/remoteproc/` > scheme). > > > > The image also boots the PocketBeagle and loads `g_ether` and boots > fine. > > However, it does not load the PRU units and only loads `remoteproc0` > [the > > omap timer (?)]. There are no `/sys/class/remoteproc/` entries for > either of > > the PRU units. The kernel logs don't show anything, no errors, or > anything > > regard the PRU units (aside from remoteproc0). > > > > Based on the serial output from the BBG, the U-Boot version correctly > boots > > using U-Boot 2018.03. Also, the u-boot based cape manager loads on both > the > > BBG and PB boards after some tweaking with the uEnv.txt file. Still I > have > > not been able to get remoteproc to load the PRU units. > > > > Does anyone have any suggestions? Do I need to load another cape? I've > tried > > setting the 4-9 PRU dtbo in `uEnv.txt` to no avail. > > > > I've been reading through the DTS and DTSI sources in the Linux kernel > as > > well as the bb.org-overlays. It seems that the linux in-tree dtsi files > for > > the PocketBeagle don't mention the PRUSS hardware units at all. This is > in > > contrast to the BBB and BBG which both set the `status` field to "ok" > for > > both PRU units. My suspicion based on that is that the PRUSS and > remoteproc > > configurations aren't updated for the PB. The bb.org overlay's also do > not > > mention the PB at all that I've found. However, it appears that several > > people have the PRU's loading and working on the PB's. Hence my > confusion! > > Add this to your pocket beagle dts: (it's essentially what the overlay > does..) > > > &pruss_soc_bus { > status = "okay"; > > pruss: pruss@4a300000 { > status = "okay"; > > pru0: pru@4a334000 { > status = "okay"; > }; > > pru1: pru@4a338000 { > status = "okay"; > }; > }; > }; > > Regards, > > -- > Robert Nelson > https://rcn-ee.com/ > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/1a5427bb-ead5-4da2-890a-fcec858a399e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
