On Fri, Nov 11, 2016 at 12:26 PM, Robert Nelson <robertcnel...@gmail.com> wrote:
> On Fri, Nov 11, 2016 at 12:53 PM, Zach B <zbron...@gmail.com> wrote: > > wow that is incredible useful, I didn't even realize that is what dmesg > did. > > Here is the output I got: > > [ 2117.571792] bone_capemgr bone_capemgr: part_number 'PRU-GPIO-BLINK', > > version 'N/A' > > [ 2117.571876] bone_capemgr bone_capemgr: slot #10: override > > [ 2117.571920] bone_capemgr bone_capemgr: Using override eeprom data at > slot > > 10 > > [ 2117.571967] bone_capemgr bone_capemgr: slot #10: 'Override Board > > Name,00A0,Override Manuf,PRU-GPIO-BLINK' > > [ 2117.573674] bone_capemgr bone_capemgr: slot #10: PRU-GPIO-BLINK > conflict > > P8.11 (#4:univ-emmc) > > [ 2117.582657] bone_capemgr bone_capemgr: slot #10: Failed verification > > univ-emmc is the userspace overlay we automatically load on bootup > > open /boot/uEnv.txt > > you'll notice a cape_universal=enable > > remove that and reboot > > Regards, > > What does that actually do Robert ? I've done this myself in the past, and haven't noticed a difference one way or another. Granted, I am using a heavily modified universal overlay. . . but with only specific pins muxed the way I need it, and everything else stripped out. -- 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/CALHSORqECmXqzYHh40JcoAvo8wPfXbW8tPOOcubHc_0AEqFF6w%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
