And I’ll change duty cycles with px.ChangeDutyCycle(). This worked fine for me, but then I messed up the OS and had to re-flash the SD with a new image. The thing is that now no PWM signal is generated neither from pin 33 nor 32. Any ideas?
Hi @JerryChang , thanks a lot for you response! Isn’t that done with sudo /opt/nvidia/jetson-io/jetson-io.py ? I mean, I did the configuration using sudo /opt/nvidia/jetson-io/jetson-io.py and then rebooted but no signal coming out neither pin 33 nor 32…
Hi @JerryChang sorry to bother you (had a busy couple of days) I read what you sent but I did have the PWM working on my other SD image and I did not configured the pins via this pinmux nor did I needed to reflashed (I just configured as PWM outputs from opt/nvidia/jetson-io/jetson-io.py, this seem normal to you? I’m new to the Jetson Nano but do not understand why before it worked so nicely and now seems more tricky to enable the PWMs… Thanks in advance!
No no, only one Jetson Nano dev kit, 2 SDs. On my original SD I broke my linux kernel so I started from scratch on a new card, install all the necessary things for my project but PWM signals are not working… Did I messed up by changing the SDs?
So it seems that Pin 32 is enabled, though not signal coming out from Jetson.GPIO Python lib.
PD: I had to install busybox (as it seems is not pre-installed in the NVIDIA image) and got some ugly messages (I could execute the command though as showed above):
ottobot@ottobot-nano:~$ sudo apt-get install busybox -y
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
0 upgraded, 1 newly installed, 0 to remove and 47 not upgraded.
Need to get 367 kB of archives.
After this operation, 782 kB of additional disk space will be used.
Get:1 http://ports.ubuntu.com/ubuntu-ports bionic-updates/universe arm64 busybox arm64 1:1.27.2-2ubuntu3.4 [367 kB]
Fetched 367 kB in 2s (222 kB/s)
debconf: delaying package configuration, since apt-utils is not installed
Selecting previously unselected package busybox.
(Reading database ... 243980 files and directories currently installed.)
Preparing to unpack .../busybox_1%3a1.27.2-2ubuntu3.4_arm64.deb ...
Unpacking busybox (1:1.27.2-2ubuntu3.4) ...
Setting up busybox (1:1.27.2-2ubuntu3.4) ...
Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
Processing triggers for initramfs-tools (0.130ubuntu3.13) ...
update-initramfs: Generating /boot/initrd.img-4.9.253-tegra
WARNING: missing /lib/modules/4.9.253-tegra
Ensure all necessary drivers are built into the linux image!
depmod: ERROR: could not open directory /lib/modules/4.9.253-tegra: No such file or directory
depmod: FATAL: could not search modules: No such file or directory
Warning: couldn't identify filesystem type for fsck hook, ignoring.
I: The initramfs will attempt to resume from /dev/zram3
I: Set the RESUME variable to override this.
depmod: WARNING: could not open /var/tmp/mkinitramfs_62hMan/lib/modules/4.9.253-tegra/modules.order: No such file or directory
depmod: WARNING: could not open /var/tmp/mkinitramfs_62hMan/lib/modules/4.9.253-tegra/modules.builtin: No such file or directory
/sbin/ldconfig.real: Warning: ignoring configuration file that cannot be opened: /etc/ld.so.conf.d/aarch64-linux-gnu_EGL.conf: No such file or directory
/sbin/ldconfig.real: Warning: ignoring configuration file that cannot be opened: /etc/ld.so.conf.d/aarch64-linux-gnu_GL.conf: No such file or directory
Hi @JerryChang , thanks for your answer and happy new year! Not completely sure on how to enable pwm pins manually with padctrl but will look into it, in the meantime, i leave you here the boot logs. Thanks a lot (I see some PWM logs but I do not understand if something is failing…) log.txt (196.9 KB)
Hi @JerryChang , unfortunately I tried reinstalling the OS (even previous versions) but PWM is not working… Really bothers me, it was working before (maybe a hardware component broke). Nonetheless, I cannot spend more time trying to fix it… Thanks anyways!