So, this is what so (fun?) about the BB ecosystem. I'm updating to the most recent image, trying to run code that has been working great for a good long time now, and it fails utterly with the same issue Nuno is experiencing.
I understand William Herman's point of view - for him, this is blaringly obvious. Why so hard? I'm sure he wonders. I'm willing to bet that William is an expert at embedded linux, and perhaps does it as a day job. That's admirable, and I think it would be fun to do that too. But I don't. I like making blinky lights. https://www.facebook.com/claytongulick/videos/pcb.10155266610164779/10155266622269779/?type=3&theater My point here, is that if the BB community expects folks like me to stick around and not just use a raspberry pi for everything, we need to make this stuff easier. I'm using the same documented SPI pins that Nuno is using, and on the latest image, it just doesn't work. Not only that, but the commands in uEnv.txt have changed. Where is the documentation on this? How are we expected to figure this out? And now, according to Robert, I just simply can't use the pins I was using before without using something called dtb-rebuilder? Look guys, I know this stuff is like breathing to you and not a big deal. But changes like this without clear documentation are going to lose the hobbyist/maker community. Sorry for the rant, I'm a bit frustrated, it's midnight and I've been working on this for hours without success, just to get SPI working the same way it used to. For now, I'm going to revert to an older image. I'd love to update my github doc with some clear instructions on how to get SPI up and going on all of the documented SPI pins if someone can point me to a place where I can figure it out. Thanks! -Clay On Wednesday, October 25, 2017 at 2:10:39 PM UTC-5, RobertCNelson wrote: > > On Wed, Oct 25, 2017 at 12:05 PM, <nuno....@gmail.com <javascript:>> > wrote: > > Hi, > > > > Definitely a must read about SPI, however with the IoT image ( Debian > 9.2 > > 2017-10-10 4GB SD IoT ) as is I was not able to configure the pins. what > I > > did and what I get: > > > > $config-pin P9.18 spi > > P9_18 pinmux file not found! > > bash: /sys/devices/platform/ocp/ocp*P9_18_pinmux/state: No such file or > > directory > > Cannot write pinmux file: > /sys/devices/platform/ocp/ocp*P9_18_pinmux/state > > > > Can anyone know how to solve this issue? > > P9_18 is allocated for i2c2, i haven't provided a way to bring this out.. > > You'll need to use the dtb-rebuilder and carve out that pin.. > > 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 beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/1bcaed35-368a-4f50-858c-2d81005e4c7a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
