Flashing 900-82888-0040-000 for the first time in a custom carrier fails

Robotics & Edge Computing Jetson & Embedded Systems Jetson AGX Xavier
,
1

Hi,
For bring-up, I do need to flash a production AGX Xavier module.
The custom carrier is debugged so far, as the power sequence is valid and the AGX module accepts USB connection on USB0.

Do those production modules come with a pre-installed OS already?

My host shows the AGX module entered recovery mode after lsusb.

Then trying to flash the OS with SDKmanager on a native ubuntu 18.04 host.
This fails with Error:

14:38:15 INFO: Flash Jetson AGX Xavier - flash: [ 9.6449 ]
14:38:15 INFO: Flash Jetson AGX Xavier - flash: [ 9.6451 ] Retrieving EEPROM data
14:38:15 INFO: Flash Jetson AGX Xavier - flash: [ 9.6452 ] tegrarcm_v2 --oem platformdetails eeprom cvb /home/<user>/nvidia/nvidia_sdk/JetPack_4.6_Linux_JETSON_AGX_XAVIER_TARGETS/Linux_for_Tegra/bootloader/bbd.bin
14:38:15 INFO: Flash Jetson AGX Xavier - flash: [ 9.6463 ] MB2 Applet version 01.00.0000
14:38:15 INFO: Flash Jetson AGX Xavier - flash: [ 9.6641 ] 000000003626070d: E> I2C: slave not found in slaves.
14:38:15 INFO: Flash Jetson AGX Xavier - flash: [ 9.7192 ]
14:38:15 INFO: Flash Jetson AGX Xavier - flash: [ 9.7192 ]
14:38:15 INFO: Flash Jetson AGX Xavier - flash: [ 9.7218 ] tegradevflash_v2 --oem platformdetails eeprom cvb /home/<user>/nvidia/nvidia_sdk/JetPack_4.6_Linux_JETSON_AGX_XAVIER_TARGETS/Linux_for_Tegra/bootloader/bbd.bin
14:38:15 INFO: Flash Jetson AGX Xavier - flash: [ 9.7229 ] CPU Bootloader is not running on device.
14:38:15 INFO: Flash Jetson AGX Xavier - flash: [ 9.7253 ]
14:38:15 INFO: Flash Jetson AGX Xavier - flash: Error: Return value 4
14:38:15 INFO: Flash Jetson AGX Xavier - flash: Command tegradevflash_v2 --oem platformdetails eeprom cvb /home/<user>/nvidia/nvidia_sdk/JetPack_4.6_Linux_JETSON_AGX_XAVIER_TARGETS/Linux_for_Tegra/bootloader/bbd.bin
14:38:15 INFO: Flash Jetson AGX Xavier - flash: --- Error: Reading board information failed.
14:38:15 INFO: Flash Jetson AGX Xavier - flash: [ Component Install Finished with Error ]
14:38:15 INFO: Flash Jetson AGX Xavier - flash: [host] [ 676.00 KB used. Disk Avail: 837.24 GB ]
14:38:15 INFO: Flash Jetson AGX Xavier - flash: [ NV_L4T_FLASH_JETSON_XAVIER_WITH_OS_IMAGE_COMP Install took 9s ]
14:38:15 ERROR: Flash Jetson AGX Xavier - flash: [error]: : [exec_command]: /bin/bash -c /tmp/tmp_NV_L4T_FLASH_JETSON_XAVIER_WITH_OS_IMAGE_COMP.sh; [error]:
14:38:15 ERROR: Flash Jetson AGX Xavier - flash: command terminated with error
14:38:15 SUMMARY: Flash Jetson AGX Xavier - flash: First Error: Installation failed.
14:38:15 SUMMARY: NVIDIA Container Runtime with Docker integration (Beta) - target: Depends on failed component
14:38:15 SUMMARY: Multimedia API - target: Depends on failed component
14:38:15 SUMMARY: TensorRT on Target - target: Depends on failed component

I stumbled upon “CPU Bootloader is not running on device” and “Reading board information failed”.
The latter is, we do not implement a carrier board EEPROM, but the first issue looks serious. Why is that?

If needed, I can provide the logs of the SDKmanager.

Any help is appreciated.

Best regards.

2

You better check the design guide for the eeprom. The “carrier board eeprom” does not matter. But the “module eeprom” is needed. Check the i2c section.

3

Thank you Wayne,

I will check the I2C section for sure.
But I have some update.

As a form of last resort, I went back to JETPACK 4.4.1 instead of 4.6.1 and now I was able to flash the OS successfully using the SDKmanager.

Therefore, I guess, there is something with the scripts coming with the 4.6.1 release.

BR
Frank

4

Hi,

Please directly try flash.sh instead of sdkmanager and see if both of release can flash your board.

Honestly, if you can prove that jetpack release 4.6.1 cannot flash even the devkit, then we can help check. But if this only happens to your carrier board, then I would suggest you to review your board design first. For example, there are lots of users and vendors over this forum too but they didn’t report their board cannot get flashed with sdkm.

5

Hi Wayne,

made some progress.
Disconnected two i2c devices from I2C3: i2c@3180000, and now manual flash.sh did work with 4.6.1, but sdkmanager did not still.

But as you mentioned in your first response, there are issues with i2c.
Need some time to resolve those, as I currently cannot get any response from i2c, regardless which bus.

So, you my not hear from me for a day or two. (Probably)

Best regards,
Frank