Hello there, it seems there are some issues with my Jetson Orin Nano PWM. I tried to run the sample from jetson-gpio GitHub - NVIDIA/jetson-gpio: A Python library that enables the use of Jetson's GPIOs, however, it seems the output does not have its lowest frequency at zero volts. I used sudo /opt/nvidia/jetson-io/jetson-io.py
and configured PIN 33 as the PWM pin, but directly using oscilloscope and running jetson-gpio/samples/simple_pwm.py
using python3 with Jetson.GPIO installed gave me this wave which makes no sense.
Hi ziyiwangandd,
Are you using the devkit or custom board for Orin Nano?
What’s the Jetpack version in use?
Please share the steps how do you configure and enable PIN33 for PWM.
And share the result of the following command on your board.
$ sudo busybox devmem 0x02434040
Hi KevinFFF,
I am using a devkit of Jetson Orin Nano with Jetpack 5.1.3.
Here is how I configure and enable PIN33:
I used sudo /opt/nvidia/jetson-io/jetson-io.py
, choose Configure Jetson 40pin Header
, Configure Header pins manually
, and then checked pwm5
which corresponds to PIN33. After that I saved the pin configuration and reboot. And then I tried to use the sample in nvidia/jetson-gpio
to get proper PWM waves.
The output of
sudo busybox devmem 0x02434040
is 0x00000405
and I believe I followed the instruction on the official wiki Welcome — Jetson Linux<br/>Developer Guide 34.1 documentation
Thanks
Is this still an issue to support? Any result can be shared?
Yes, unfortunately, I am still unable to find out why the signal is like that.
It is the expected result to me.
Could you refer to the steps in Unable to generate PWM with Nvidia Jetson AGX Orin Development Kit - #6 by KevinFFF to generate PWM?
If it is still not working, please also verify with the latest JP5.1.4(R35.6.0) or JP6.1(R36.4.0).
Hello KevinFFF,
I had already tried the steps in Unable to generate PWM with Nvidia Jetson AGX Orin Development Kit - #6 by KevinFFF and it was still unable to generate any PWM signals via PIN 33 on the Jetson Orin Nano. I used PIN 34 as the ground.
Could you verify with the latest JP5.1.4(R35.6.0) or JP6.1(R36.4.0)?
Have you checked if the issue specific to PIN33?
(i.e. you can also try modify simple_pwm.py for PIN15 and PIN32)
Please also provide the full dmesg and device tree for further check.
Hello Kevin, I probably cannot upgrade the jetpack because some dependencies that I am using right now are depending on it, but I have tried to modify the pins, but it still seems like the signal is bad.
What version of jetpack are you running. Hardware and software PWM works fine on jp 5.1.4. (requires ubuntu 20.04 host) It is broken on 6.0 and 6.1.
I’m currently using jetpack 5.1.3
I have some userspace cli that will set it up and run it. Just to verify, you did turn on the overlay for that?
I have some user space and python code that is known working, would you like that too?
Your device tree also looks good to me.
Do you have another devkit to upgrade to JP5.1.4 just to clarify if the issue is specific to JP5.1.3?
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.