At some point, we received the error mentioned here, but since it seems to be a hardware problem, can you please tell us how to debug this further? Strange thing is, it worked before…
Thank you!
R
jetson@agx:~$ sudo python3
Python 3.8.5 (default, Jul 28 2020, 12:59:40)
[GCC 9.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import Jetson.GPIO as GPIO
WARNING: Carrier board is not from a Jetson Developer Kit.
WARNNIG: Jetson.GPIO library has not been verified with this carrier board,
WARNING: and in fact is unlikely to work correctly.
>>> GPIO.JETSON_INFO
{'P1_REVISION': 1, 'RAM': '16384M', 'REVISION': 'Unknown', 'TYPE': 'Jetson Xavier', 'MANUFACTURER': 'NVIDIA', 'PROCESSOR': 'ARM Carmel'}
>>> GPIO.VERSION
'2.0.16'
>>>
jetson@agx:~$ cat /etc/nv_tegra_release
# R32 (release), REVISION: 5.0, GCID: 25531747, BOARD: t186ref, EABI: aarch64, DATE: Fri Jan 15 23:21:05 UTC 2021
jetson@agx:~$
jetson@agx:~$ cat /proc/device-tree/compatible
nvidia,galennvidia,jetson-xaviernvidia,p2822-0000+p2888-0001nvidia,tegra194
jetson@agx:~$ ls -l /proc/device-tree/chosen/plugin-manager/ids
total 0
-r--r--r-- 1 root root 25 Feb 25 21:40 2888-0004-400
-r--r--r-- 1 root root 25 Feb 25 21:40 framos-imx464-0
-r--r--r-- 1 root root 4 Feb 25 21:40 name
jetson@agx:~$
you may flash previous JetPack release versions to rule out it’s a software regression,
please check JetPack Archive for the page it includes access to previously released versions of JetPack.
for the steps to dig this further,
you may arrange hardware resources to probe the pin and measure the signaling,
thanks
Hey Jerry, as I said, it worked before with this new version of Jetpack, we also tried a fresh install, but still the same.
We did more tests today and we could find that the GPIO pins seems to be partially working: eg. we have 5V and 3V on the pins, including on 3 & 5 for I2C and we can see activity on the oscilloscope when we scan the i2c bus.
so actually our adafruit_pca9685 I2C device is detected, but there seems to be a problem in python…
The content and CRC is described in product documentation, but we do not provide a utility to re-write it. The serial number and part number information should be accessible from the barcode sticker on the module and user can use standard i2ctools utilities for writing it.
Then maybe we can only fix the part-number address, can you tell us what should be in here for Jetson AGX devboard 32GB? Can we get the values from the box sticker?
Worked, now the board is detected by Jetson.GPIO (warning is gone) but unfortunately the i2c device still does not work 🙁 should I open a new topic regarding this, or you think the other missing bytes in the EEPROM could cause this? Do I have to also put the serial in there?
Hello @razvanphp , I am one of the FAEs at FRAMOS. I was wondering if this is an issue that FRAMOS team could help resolve.
Do you have a contact at FRAMOS that you are communicating, please? If not, please let me know where you are based and how you came to use the FRAMOS adapter so we can get you in touch with appropriate team member.
The most important feedback we have here is to update your write_eeprom.sh script to prevent writing on address 0x56 on I2C bus 0, since this will override the jetson eeprom, not the adapter or camera modules of Framos.
Unfortunately we did not see the bus 30 as in documentation and we thought it’s maybe on 0…