I am currently facing the Nvidia flashing issue with SDKManager. I am trying to flash it but I am observing the I2c read errors for eeprom device.
We are using the connect-tech carrier board and we are facing the issues.
We are able to flash the basic software using flash.sh as it is not reading the eeprom. However, we are facing issues with SDKManager. We recently updated SDKmanager with above version. Is this a known issue ?
I am attaching the console logs and terminal logs from SDKManager.
Logs from Xavier console :
[0057.322] W> Profiler not initialized
[0057.325] I> Welcome to MB2(TBoot-BPMP) Applet (version: 00.00.2018.32-mobile-d95d9a83)
[0057.333] W> Profiler not initialized
[0057.337] I> DMA Heap @ [0x40020000 - 0x40065800]
[0057.341] I> Default Heap @ [0xd486400 - 0xd48a400]
[0057.346] W> Profiler not initialized
[0057.350] W> Profiler not initialized
[0057.353] W> Profiler not initialized
[0057.409] I> sdmmc DDR50 mode
[0057.413] I> No supported QSPI flash found
[0057.417] E> QSPI Flash: Insufficient flash size (0 MB)
[0057.422] I> QSPI Flash is not present.
[0057.473] E> Link startup dme_set failed
[0057.477] E> UFS initialization failed
[0057.481] I> UFS is not present
[0057.484] W> Profiler not initialized
[0057.491] I> Found 17 partitions in SDMMC_BOOT (instance 3)
[0057.501] I> Found 42 partitions in SDMMC_USER (instance 3)
[0057.506] W> Profiler not initialized
[0057.510] W> Profiler not initialized
[0057.513] W> Profiler not initialized
[0057.517] I> Entering 3p server
[0057.520] I> USB configuration success
[0058.473] I> Populate chip info
[0058.513] I> Populate eeprom info
[0058.517] I> Populate eeprom info for module cvm
[0064.941] I> Populate chip info
[0064.984] I> Populate eeprom info
[0064.988] I> Populate eeprom info for module cvb
[0064.992] E> I2C: slave not found in slaves.
[0064.996] E> I2C: Could not write 0 bytes to slave: 0x00ac with repeat start true.
[0065.004] E> I2C_DEV: Failed to send register address 0x00000000.
[0065.010] E> I2C_DEV: Could not read 256 registers of size 1 from slave 0xac at 0x00000000 via instance 0.
[0065.019] E> eeprom: Failed to read I2C slave device
[0065.024] E> NV3P_SERVER: Failed to get eeprom handle for cvb from eeprom manager.
[0065.032] E> NV3P_SERVER: Could not read eeprom for module cvb.
Incidentally, during flash the Jetson is in recovery mode. After flash completes the Jetson automatically reboots. The optional software is not installed during flash, and is actually started after flash completes and the Jetson is fully booted. This implies that the first boot account setup must be completed after that reboot, but before the optional software can be installed (it uses ssh over the network, and there is no way to ssh without the account).
Also, it is not necessarily obvious, but you can uncheck various JetPack tasks. For example, you can uncheck installation of items to the host PC, and you can uncheck flash; in this case the optional component installation is the only thing it will do, and for this it expects a fully booted Jetson (not in recovery mode) with the account setup and networking already running (networking might be from the USB cable since it creates a virtual ethernet device with address 192.168.55.1, but you can use any valid IP address for the Jetson).