Hi,
I am using BBB PRU1_0 pin (P8_45) as output. To set the pinmux, I use
Device Tree where I put the pin in MODE5:
&am33xx_pinmux {
trigger_pins: trigger_pins {
pinctrl-single,pins = <
AM33XX_IOPAD(0x8a0, PIN_OUTPUT | MUX_MODE5) /* P8_45 |
PRU1_0 | lcd_data0 */
>;
};
};
PRU Kernel modules are built-in (buildroot system), but I have noticed that
during the boot, the state is LOW (not surprising because that pin has a
pull-down resistor because it is used to select the boot mode).
Then, later in the kernel boot process, the pin change its state to HIGH
(my PRU program is not yet launched).
I can reproduce this on the Debian image, with:
uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-14-TI-00A0.dtbo
enable_uboot_cape_universal=1
The pin remains low at boot but after
config-pin -a p845 pruout
The pin level become HIGH.
This behavior does not occur on pin P8_46.
I was thinking about setting the pin as INPUT in Device Tree and after
starting my PRU program that sets __R30 to 0, switch the pinmux to PRU
output. But because I use TI kernel, I am not sure if I can change pinmux
on runtime.
Does anyone has a idea why the pin P8_45 switch to high when pinmuxing to
PRU out?
Is it possible to change pinmux on runtine?
Thanks
--
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/20fdd991-2a97-4cc9-8a5c-6c524972cb3c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
