After three years of avoiding it I've finally decided to fight the dragon of writing my own device tree overlay. It's for a PocketBeagle application that uses both PRUs to talk to 13 pins: 8 GPIOs, 3 pruins, and 2 pruouts. I'm happy to say that I've succeeded in getting one that works!
But I made it with a heap of conjecture and experimentation, and I'm pretty sure it stinks. It would be a big favour for you to tell me all the ways it's lousy. It doesn't use the New Syntax, but I'm OK with that --- I guess I'm more worried about future proofing, brittleness, and things that are actually wrong (and only working because I'm getting lucky). If it matters, I'm running on 10.0 IOT. (I can't use 10.3 for (happily-soon-eliminated) Reasons <https://github.com/beagleboard/Latest-Images/issues/80>.) Without further adieu, I give you: pb-cameo-aphid.dts. It's a bit long for this message, so I've uploaded it here: http://mg-1.uk:31132/pb-cameo-aphid.dts.txt Thanks for any insights, --Tom -- 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 beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/b8170506-2a98-4863-9065-a89e4ad29a08n%40googlegroups.com.
