Just an update; yes, the .dtbo file was misnamed. After renaming the file:
cp /lib/firmware/libpruio-0A00.dtbo /lib/firmware/libpruio-00A0.dtbo I was able to execute: sudo echo libpruio > /sys/devices/bone_capemgr.9/slots That produced this in dmesg: [ 796.178041] bone-capemgr bone_capemgr.9: part_number 'libpruio', version 'N/A' [ 796.178221] bone-capemgr bone_capemgr.9: slot #7: generic override [ 796.178264] bone-capemgr bone_capemgr.9: bone: Using override eeprom data at slot 7 [ 796.178311] bone-capemgr bone_capemgr.9: slot #7: 'Override Board Name,00A0,Override Manuf,libpruio' [ 796.184663] bone-capemgr bone_capemgr.9: slot #7: Requesting part number/version based 'libpruio-00A0.dtbo [ 796.184728] bone-capemgr bone_capemgr.9: slot #7: Requesting firmware 'libpruio-00A0.dtbo' for board-name 'Override Board Name', version '00A0' [ 796.191902] bone-capemgr bone_capemgr.9: slot #7: dtbo 'libpruio-00A0.dtbo' loaded; converting to live tree [ 796.320640] bone-capemgr bone_capemgr.9: slot #7: #3 overlays [ 796.652764] omap_hwmod: pruss: failed to hardreset [ 796.669190] bone-capemgr bone_capemgr.9: slot #7: Applied #3 overlays. [ 796.745317] pruss_uio 4a300000.pruss: pins are not configured from the driver After this, the analog pins worked as expected: ➜ libpruio-0.2 sudo src/examples/1 F6A0 ED00 ED10 E5D0 DD20 DA70 D580 EEB0 F310 EDB0 EE40 E690 DF10 D770 D5B0 EEF0 F280 ED10 ECE0 E5E0 DE40 D840 D8C0 EEC0 F2F0 EC80 ED40 E5C0 DCA0 DBC0 D910 EEA0 F290 ED10 ED60 E5D0 DCD0 D790 D5D0 EE70 F260 ED00 EDA0 E5B0 DD60 D860 D9B0 EEB0 F360 ED70 EE40 E680 DD80 DDF0 DA70 EEE0 F340 ED20 EDE0 E640 DC40 D820 DA20 EEB0 F2D0 EDA0 EDA0 E540 DB20 D870 D7B0 EEB0 F2D0 EDA0 EE30 E650 DE20 DBE0 D950 EEF0 F2B0 ED40 ED80 E550 DC40 DC70 D750 EEB0 F2A0 EDD0 EDF0 E690 DE10 D7D0 D5E0 EEE0 F2A0 ED50 EDF0 E6B0 DE20 D720 D6A0 EEC0 Thanks for the help, Brandon On Sun, Mar 29, 2015 at 4:35 PM, Brandon Stafford <bran...@rascalmicro.com> wrote: > Ah, I had noticed the 0A00 difference, but I assumed it was intentional! > Should have figured that out. > > I'll give it a try on Monday. Thanks for the response. > > Brandon > > On Fri, Mar 27, 2015 at 12:29 PM, TJF <jeli.freih...@gmail.com> wrote: > >> @Brandon, >> >> when you use BB-BONE-PRU-01 overlay you won't have run-time pinmuxing >> capability. >> >> Am Mittwoch, 25. März 2015 20:22:01 UTC+1 schrieb Brandon Stafford: >>> >>> When I try to load libpruio, this happens: >>> >>> sudo echo libpruio > /sys/devices/bone_capemgr.9/slots >>> echo: write error: No such file or directory >>> >> >> There's a typo in the file name. Rename the device tree overlay to >> libpruio-00A0.dtbo (note the position of the 'A') and the file should load. >> >> BR >> >> -- >> 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. >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > Brandon Stafford > Rascal Micro: small computers for art and science > Somerville, MA, USA > -- Brandon Stafford Rascal Micro: small computers for art and science Somerville, MA, USA -- 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. For more options, visit https://groups.google.com/d/optout.
