Hello,
I used pwm gpio pin 18, on l4t R32.2.3, it can be used by changed the pinmux config tegra19x-mb1-pinmux-p2888-0000-a04-p2822-0000-b01.cfg
pinmux.0x02434090 = 0x00000401; # soc_gpio12_ph0: rsvd0, pull-down, tristate-enable, input-enable, lpdr-disable
.
But when upgraded to l4t R32.3.1, nerther changing the pinmux config nor using the new tools Jetson‑IO, the pwm pin can’t be used normally.
Tested by Jetson.GPIO simple_pwm.py, it show
Traceback (most recent call last):
File "/home/zhkj-robot/Documents/jetson-gpio/samples/simple_pwm.py", line 52, in <module>
main()
File "/home/zhkj-robot/Documents/jetson-gpio/samples/simple_pwm.py", line 40, in main
p = GPIO.PWM(output_pin, 50)
File "/home/zhkj-robot/Documents/jetson-gpio/lib/python/Jetson/GPIO/gpio.py", line 597, in __init__
self._reconfigure(frequency_hz, 50.0)
File "/home/zhkj-robot/Documents/jetson-gpio/lib/python/Jetson/GPIO/gpio.py", line 635, in _reconfigure
_set_pwm_period(self._ch_info, self._period_ns)
File "/home/zhkj-robot/Documents/jetson-gpio/lib/python/Jetson/GPIO/gpio.py", line 245, in _set_pwm_period
f.write(str(period_ns))
IOError: [Errno 22] Invalid argument