Modify the spreadsheet to enable the internal pullup for GPIO3_PY.00 (which is currently set to not assigned (is it floating and that is why it is generating the random interrupts?).
Yes, you are right. We think that might cause the the interrupt.
Use the dts2cfg.py script to generate .cfg files (is this for 3 files: pinmux, gpio, and pad? Or just 1 file: pinmux)
should only have one pinmux file if you use the command to generate pinmux only. We only need pinmux so no need to generate the pad setting.
I am not going to try anything until I am sure of the process, since I don’t want to brick my system.
After creating the pinmux file, go to Linux_for_Tegra/bootloader and search pinmux.
HP-Compaq-6200-Pro-MT-PC:~/nvidia/nvidia_sdk/JetPack_4.3_Linux_P2888-0060/Linux_for_Tegra/bootloader$ find -iname “*pinmux *.cfg”
./tegra19x-mb1-pinmux-p2888-0000-a04-p2822-0000-b01.cfg -> This is the file name you previously flash into your board, but it is a copy.
./t186ref/BCT/tegra19x-mb1-pinmux-p2888-0000-a04-p2822-0000-b01.cfg -> this is the real one
I would suggest you to rename the old one as back-up and put the new one under Linux_for_Tegra/bootloader/t186ref/BCT. Please remember to rename the new file to the same name as the old one so that the flash script could find it.
and don’t worry about the device would be dead or not. If you hit any error, just use the old pinmux to re-flash it again and it would be alive again. Actually, device is seldom dead because of changing only pinmux.