Glad it's working!
To use the config-pin utility you also have to load one of the universal
cape overlays (which will create the pinmux files in /sys/). It sounds
like you're making your own device-tree so you're fine. The universal
overlay files are for those who don't want to (or can't)
Thank you for your reply. I modified the device PinMux to Mode5:
$cat /sys/kernel/debug/pinctrl/44e10800.pinmux-pinctrl-single/pins | grep
8a8
pin 42 (PIN42) 44e108a8 000d pinctrl-single
$cat /sys/kernel/debug/pinctrl/44e10800.pinmux-pinctrl-single/pins | grep
8ac
pin 43 (PIN43) 44e108ac
The mode pr1_pru1_pru_r31_* is for PRU input (R31 is the direct input
register). Use the pr_pru_pru_r30 option (R30 is the PRU direct output
register) or something like the config-pin utility and universal overlay
which makes this simple for you, eg:
config-pin P8.43 pruout
On 5/16/2023
Thank you for your reply.
Now i generated the device tree overlay to configured the P8_43 to Mode6
(pr1_pru1_pru_r31_2) and P8_44 to Mode6 (pr1_pru1_pru_r31_3). This was
successful:
$cat /sys/kernel/debug/pinctrl/44e10800.pinmux-pinctrl-single/pins | grep
8a8
pin 42 (PIN42) 44e108a8 0016
You likely need to configure the pin multiplexing for the pins you wish
to use so they can be controlled by the PRU. This is typically done via
a device-tree overlay, or something like cape-universal and the
config-pin utility if you don't like making device-tree files:
Hello everybody,
I am still trying to run the stepper motor with Machinekit. I configured
the hal and i was expecting some step/dir signal on the output pins, but
nothing happens (i am monitoring with the oscilloscope).
I tried to generate steps by changing the hpg.stepgen.00.position-cmd
