Serial console debug error using TX2 NX

[ckaran672]

Hi, I am trying to debug the serial console. I am using jetson tx2 nx (https://www.waveshare.com/wiki/JETSON_NANO_TX2_NX). I am following jetsonhacks (https://jetsonhacks.com/2019/04/19/jetson-nano-serial-console/) video for reference, after setting up my serial device in minicom i.e. ttyUSB0 and powering ON my jetson tx2 nx the booting shows this error:-
login: tegra-i2c 3160000.i2c: no acknowledge from address 0x0
[ 6.794929] tegra-i2c c240000.i2c: no acknowledge from address 0x50
[ 6.801881] tegra-i2c 3180000.i2c: no acknowledge from address 0x50

[WayneWWW]

Hi,

So what was your original purpose of using serial console?

[ckaran672]

I am trying to boot the system using desktop mode after finishing the headless setup and it showing an error tegra-i2c 3160000.i2c: no acknowledge from address 0x0
[ 6.794929] tegra-i2c c240000.i2c: no acknowledge from address 0x50
[ 6.801881] tegra-i2c 3180000.i2c: no acknowledge from address 0x50
, so to solve this I refer to this forum (Tegra-i2c 7000c400.i2c: no acknowledge from address 0x50) and it shows serial debug so i try to do it and again while booting in serial it shows this error tegra-i2c 3160000.i2c: no acknowledge from address 0x0
[ 6.794929] tegra-i2c c240000.i2c: no acknowledge from address 0x50
[ 6.801881] tegra-i2c 3180000.i2c: no acknowledge from address 0x50

[WayneWWW]

Hi,

Then the next question is this a custom board made by yourself or it is from other vendor

[WayneWWW]

Any I/O interface on Jetson is related to the carrier board you are using.

For example, if these i2c interfaces are not enabled on your board, then you need to disable it manually.

Thus, I need to clarify this is a carrier board made by yourself. If it is not, then you need to get the customized BSP from the vendor who provided you the board.

[ckaran672]

I am using https://www.waveshare.com/wiki/JETSON_NANO_TX2_NX this developer kit.

[WayneWWW]

Could you use serial console and attach the full dmesg log as text file (please do not share screen anymore)?

[WayneWWW]

As I said, attach them as file… not just copy and paste…

[WayneWWW]

Also I need the log from Jetson… not your host PC.

[ckaran672]

ok sorry for the mistake I will send you that.

[ckaran672]

erc@erc~$ dmesg .txt (59.1 KB)
Here is the attached file for dmesg on jetson tx2 nx device

[WayneWWW]

Please also reboot the device and share those boot log from serial console.

[ckaran672]

erc@ubuntu~$ sudo minicom.txt (31.6 KB)
Here is the attached file for boot log from serial console

[WayneWWW]

Hi,

I just checked the log on my side and there is no such log there appeared.

This is actually a common error to show up when you have some application that trying to access these i2c bus/address.

As I don’t know if you modify something there, I cannot tell.

But this should be no harm for now.

[ckaran672]

ok thank you for your reply but still the question is how could I solve it as I am trying to boot into the system using a display, it shows the same error (tegra-i2c 3160000.i2c: no acknowledge from address 0x0
[ 6.794929] tegra-i2c c240000.i2c: no acknowledge from address 0x50
[ 6.801881] tegra-i2c 3180000.i2c: no acknowledge from address 0x50) and Also while debugging it shows the same error so what step I need to take to solve it?

[linuxdev]

I don’t know which bus is used for the HDMI’s DDC wire, but it is at address 0x50. That wire is what provides the monitor’s information to the GPU for plug-n-play. If you’ve used any kind of VGA adapter, then this error would probably be expected. An equivalent error is if the power rails are not set up; the i2c circuitry in the monitor is not powered by the monitor, but is instead powered by the HDMI cable, and lack of setup to provide that power to the HDMI port (usually set up via device tree) would cause that power to fail. I don’t know if the bus being referred to for the i2c issue is for video or not, but likely it is since video fails (if a monitor is expected due to hot plug not being configured correctly then being headless would not be correctly detected and a monitor might be expected despite being headless).

Overall, I am wondering if your waveshare manufacturer provides flash software or patches that you might have missed? This is where any custom device tree would need to come from if it has any difference from the NVIDIA carrier board.