Issues Detecting I2C Devices on Jetson Orin NX 16GB with Custom Carrier Board

Robotics & Edge Computing Jetson & Embedded Systems Jetson Orin NX
,
1

Hello everyone,

We are using a Jetson Orin NX 16GB module with a custom carrier board that we designed ourselves. I’m encountering some difficulties with detecting I2C devices connected to the board.

When I run i2cdetect -y, I see a list of I2C devices on the bus, but I’m unable to communicate with the hardware we’ve connected. Specifically, when I try i2cdetect -y 2, I still can’t establish communication.
here is the detail output of i2c detect
i2c_check.txt (20.1 KB)

Additionally, could someone explain where I can find the base addresses for the I2C1 or SPI peripherals on the SOM module?

And how can I reduce the flashing time ? for each flash it takes around 60 minutes .

Any help or guidance would be greatly appreciated!

Thank you.

3

Hi pranal.m,

What’s your Jetpack version in use?

Which I2C bus are you using?

You can refer to Jetson/L4T/peripheral/ - eLinux.org for the I2C base address mapping.

What are you trying to modify for the development? Kernel image or dtb or something else?

4

we are using jetpack 5.1

we are using I2C1 and I2C2.

We are modifying the dts file to integrate the audio codec.
Also, I am facing issues writing a node for the audio codec. If you have a sample node for the audio codec, that would be helpful.

And are we modifying only hardware/nvidia/platform/t23x/p3768/kernel-dts/cvb/tegra234-p3767-common-audio.dtsi? Is this the correct file to modify?

5

You can refer to Audio Setup and Development — Jetson Linux Developer Guide documentation (nvidia.com) for details.

Yes, this device tree is used for Orin NX.

7

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.