csocom
September 27, 2022, 9:14am
1
In Booting we can see I2C Error, So How can we solve it?
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 4.9.253 (root@shpark-B80GV-AP07BKE) (gcc version 7.3.1 20180425 [linaro-7.3-2018.05 revision d29120a424ecfbc167ef90065c0eeb7f91977701] (Linaro GCC 7.3-2018.05) ) #14 SMP PREEMPT Wed Jul 13 15:05:22 KST 2022
[ 0.000000] Boot CPU: AArch64 Processor [411fd071]
[ 0.000000] OF: fdt:memory scan node memory@80000000, reg size 32,
[ 0.000000] OF: fdt: - 80000000 , 7ee00000
[ 0.000000] OF: fdt: - 100000000 , 7f200000
[ 0.000000] earlycon: uart8250 at MMIO32 0x0000000070006000 (options ‘’)
[ 0.000000] bootconsole [uart8250] enabled
[ 1.069890] tegradc tegradc.1: dpd enable lookup fail:-19
[ 1.575834] Host read timeout at address 545c00c4
[ 1.765634] imx219 7-0010: imx219_board_setup: error during i2c read probe (-121)
[ 1.773288] imx219 7-0010: board setup failed
[ 1.801717] imx219 8-0010: imx219_board_setup: error during i2c read probe (-121)
[ 1.809286] imx219 8-0010: board setup failed
[ 3.862299] ser_console: loading out-of-tree module taints kernel.
[ 4.025237] random: crng init done
[ 4.028641] random: 7 urandom warning(s) missed due to ratelimiting
[ 4.205459] using random self ethernet address
[ 4.224550] using random host ethernet address
[ 5.080814] tegra-i2c 7000c400.i2c: no acknowledge from address 0x41
[ 5.087620] tegra-i2c 7000c400.i2c: no acknowledge from address 0x41
we use “Nvidia Netson Nano Module”
S/N:142092294303
kayccc
September 27, 2022, 11:03pm
2
Issue happened on your custom carrier board or dev?
Which JetPack version>
hello csocom,
i2c no acknowledge
failure usually due to i2c communication without correct regulator settings.
are you using Nano developer kit, or you’re having customize carrier board?
hello csocom,
please check Jetson Nano Product Design Guide and review your board,
you should given correct regulator settings to resolve i2c no acknowledge
failures.
csocom
September 29, 2022, 7:53am
9
Our Solutions: Jetson Nano Module(16GB)+ Custom Board.
We research file <Jetson_Nano_Product_Design_Guide_DG-09502-001_v2.3.pdf>.
https://docs-download.oss-cn-shanghai.aliyuncs.com/厂商资料/英伟达/英伟达硬件/Jetson%20Nano-Z/Jetson%20Nano-Z%20Product%20Design%20Guide%20DG-09502-001v2.1.pdf ](chrome-extension://efaidnbmnnnibpcajpcglclefindmkaj/https://docs-download.oss-cn-shanghai.aliyuncs.com/厂商资料/英伟达/英伟达硬件/Jetson%20Nano-Z/Jetson%20Nano-Z%20Product%20Design%20Guide%20DG-09502-001v2.1.pdf )
BUT Note:
**CAM_I2C interface is connected to the power monitor device on the module which uses I2C address 7’h40. 0x40
We can’t find out " 0x41 I2C address".
is it shifted I2C address ? (0x41 << 1) ------> 0x82
hello csocom,
it might be hardware monitor, INA3221, which use I2C addresses. 0x40 - 0x43
please review your device tree settings, such as ina3221x@41
, you should modify that DT properties according to your product design.
csocom
October 4, 2022, 9:17am
11
Dear JerryChang ! Thanks for your Reply.
I have Questions
Our Custom Board PCB don’t have “INA3221 IC”, so we want to no use it.
we don’t want to control I2C ( 0x41, INA3221), so we will disable to “0x41 I2C” in the SW Jetpack linux program, is it Right?
Does it exist INA3221- IC(0x41 ) on Jetson Nano Module ?
I know Only 1EA, INA3221-IC(0x40 ) on Jetson Nano Module ----> Product Design Guide.pdf
hello csocom,
please update the device tree to remove 0x41 accordingly.
system
Closed
October 26, 2022, 5:32am
14
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.