So if this continues to be a problem for you. Once you unload a cape, you should instead just reboot. This is not ideal, but it's what we have right now . . .
On Mon, Nov 7, 2016 at 2:18 PM, William Hermans <[email protected]> wrote: > > > On Mon, Nov 7, 2016 at 1:39 PM, Theodosis Ntegiannakis < > [email protected]> wrote: > >> >> >> On Monday, November 7, 2016 at 9:19:58 PM UTC+2, William Hermans wrote: >>> >>> > and with sudo sh -c "echo 'BB-UART2' > /sys/devices/platform/bone_cap >>>> emgr/slots" >>>> > i get sh: echo: I/O-error >>>> >>>> This generally means the cape couldn't be loaded. You can sometimes >>>> find more detail at the end of dmesg output, but failures when trying >>>> to load capes are usually pretty cryptic. >>>> >>> >>> I've seen this happen several time when loading a cape, that is trying >>> to configure pins that have already been configured. For me, this happened >>> after unloading the previous cape. There still seems to be a "bug" when >>> unloading capes. >>> >>> >>> Should i report this "bug" somewhere? >> > > No, I think it's a known issue already. > -- 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/CALHSORooJFkd9N074uiKfFM5bWSPm4r6C%3DK7oP4_q2W%2BoLhPRg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
