Am Dienstag, 28. April 2020 23:56:34 UTC+2 schrieb [email protected]: > > I was able to toggle those 2 lines as GPIO and validate their manipulation > using a logic analyzer. > > When done, I went back to the other program to communicate with the micro > SD card in the slot and it worked just as if those pins had never been > changed! I was like Wow! Very impressive! >
Fine! Note: the pinmuxing is only active in the time after the pruio_config() call and before the DTOR call to pruio_destroy(). The DTOR restores the original setting (by default). (A cosmetic note: I prefer calling pruio_pgio_setValue() before pruio_config() -> all start values get set simultaneously.) > So when I do a show-pins -v > > μSD d3 60 fast rx up 0 mmc 0 d3 > mmc@48060000 (pinmux_mmc1_pins) > μSD d2 61 fast rx up 0 mmc 0 d2 > mmc@48060000 (pinmux_mmc1_pins) > μSD d1 62 fast rx up 0 mmc 0 d1 > mmc@48060000 (pinmux_mmc1_pins) > μSD d0 63 fast rx up 0 mmc 0 d0 > mmc@48060000 (pinmux_mmc1_pins) > μSD clk 64 fast rx up 0 mmc 0 clk > mmc@48060000 (pinmux_mmc1_pins) > μSD cmd 65 fast rx up 0 mmc 0 cmd > mmc@48060000 (pinmux_mmc1_pins) > > this will always show uSD d0 and uSD d1 as mmc under pinmux_mmc1_pins even > when they are switched to GPIO mode briefly under libpruio control? Just > asking out of curiosity? > I don't know the show_pins tool. What happens when you execute it in a second shell while your libpruio prog is running? Perhaps it lists the kernel setting, but ignores the hardware state. -- 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/948e664e-38fd-4aeb-bfd1-3d7bb8f07508%40googlegroups.com.
