My environment:
Self-developed baseboards based on Jetson Orin Nx core boards
Jetson_Linux_R36.2.0_aarch64.tbz2
VM development environment for sdk - ubuntu20.04
I’ve been able to burn my sdk on the Jetson Orin Nx development board, but when I change it to my own board, I get the timeout problem again!
What is the cause of the timeout problem on our previous board (below) and what should I do to fix it?
Check the uart log first. Timeout could be lots of reasons. Need the log to tell.
What kind of serial port logs are needed, serial port logs for boot-up after flash, or serial port prints during flash?
The following is the serial port log for boot up after a failed flash.
MobaXterm_192.168.150.129_20240304_160922__timeout__boot_log.txt (46.7 KB)
Is this log the one that meets the requirements?
No… you need to share the log when you got error. Always this case.
If your issue is error during flash, then share the log during flash.
E> I2C: slave not found in slaves.
E> I2C: Could not write 0 bytes to slave: 0x00ae with repeat start true.
E> I2C_DEV: Failed to send register address 0x00000000.
E> I2C_DEV: Could not read 256 registers of size 1 from slave 0xae at 0x00000000 via instance 0.
MobaXterm_192.168.150.129_20240304_160922__timeout__seriol_flash_log2.txt (34.3 KB)
MobaXterm_192.168.150.129_20240304_160922__timeout2.txt (260.1 KB)
I reflash the log logs as above.
我用中文說好了
在你第一次flash完之後Linux_for_Tegra/bootloader/generic/BCT/tegra234-mb2-bct-misc-p3767-0000.dts這個檔案會被copy到Linux_for_Tegra/bootloader/底下，下次再燒會從這個路徑抓
所以你改原檔案是沒用的，要嘛連Linux_for_Tegra/bootloader底下的那一份一起改、要嘛整包BSP全部刪掉重來
這個底板EEPROM read size的問題真的有非常多人問過了…
你拿error log去Google就可以找到一大堆討論
我修改Linux_for_Tegra/bootloader/generic/BCT/tegra234-mb2-bct-misc-p3767-0000.dts之后，已经可以继续烧录了，非常感谢你的回复！
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
