Porting 900-82888-0080-000 (Jetson AGX Xavier Industrial) on Customer Carrier Board Failed

[kaichu.wu]

Hello there,

We have designed a carrier board for Jetson AGX Xavier and trying to port Jetson AGX Xavier Industrial on it.

The current status is as follows:

• We have ported a device tree for JAXi on our carrier board.
• We can’t flash JAXi via SDKManager 1.7.3. It ends with the following error messages

...
15:42:03.028 - info: NV_L4T_FLASH_JETSON_XAVIER_WITH_OS_IMAGE_COMP@JETSON_AGX_XAVIER_TARGETS: [  14.4655 ] tegrarcm_v2 --oem platformdetails eeprom cvb /home/nvidia/nvidia/nvidia_sdk/JetPack_4.6_Linux_JETSON_AGX_XAVIER_TARGETS/Linux_for_Tegra/bootloader/bbd.bin
15:42:03.038 - info: NV_L4T_FLASH_JETSON_XAVIER_WITH_OS_IMAGE_COMP@JETSON_AGX_XAVIER_TARGETS: [  14.4675 ] MB2 Applet version 01.00.0000
15:42:03.235 - info: NV_L4T_FLASH_JETSON_XAVIER_WITH_OS_IMAGE_COMP@JETSON_AGX_XAVIER_TARGETS: [  14.8722 ] 000000003626070d: E> I2C: slave not found in slaves.
15:42:03.236 - info: NV_L4T_FLASH_JETSON_XAVIER_WITH_OS_IMAGE_COMP@JETSON_AGX_XAVIER_TARGETS: [  14.9268 ] 
15:42:03.236 - info: NV_L4T_FLASH_JETSON_XAVIER_WITH_OS_IMAGE_COMP@JETSON_AGX_XAVIER_TARGETS: [  14.9269 ] 
15:42:03.236 - info: NV_L4T_FLASH_JETSON_XAVIER_WITH_OS_IMAGE_COMP@JETSON_AGX_XAVIER_TARGETS: [  14.9321 ] tegradevflash_v2 --oem platformdetails eeprom cvb /home/nvidia/nvidia/nvidia_sdk/JetPack_4.6_Linux_JETSON_AGX_XAVIER_TARGETS/Linux_for_Tegra/bootloader/bbd.bin
15:42:03.249 - info: NV_L4T_FLASH_JETSON_XAVIER_WITH_OS_IMAGE_COMP@JETSON_AGX_XAVIER_TARGETS: [  14.9335 ] CPU Bootloader is not running on device.
15:42:03.249 - info: NV_L4T_FLASH_JETSON_XAVIER_WITH_OS_IMAGE_COMP@JETSON_AGX_XAVIER_TARGETS: [  15.0826 ] 
15:42:03.255 - error: NV_L4T_FLASH_JETSON_XAVIER_WITH_OS_IMAGE_COMP@JETSON_AGX_XAVIER_TARGETS: Error: Return value 4
15:42:03.256 - info: Event: NV_L4T_FLASH_JETSON_XAVIER_WITH_OS_IMAGE_COMP@JETSON_AGX_XAVIER_TARGETS - error is: Error: Return value 4
15:42:03.256 - info: NV_L4T_FLASH_JETSON_XAVIER_WITH_OS_IMAGE_COMP@JETSON_AGX_XAVIER_TARGETS: Command tegradevflash_v2 --oem platformdetails eeprom cvb /home/nvidia/nvidia/nvidia_sdk/JetPack_4.6_Linux_JETSON_AGX_XAVIER_TARGETS/Linux_for_Tegra/bootloader/bbd.bin
15:42:03.283 - error: NV_L4T_FLASH_JETSON_XAVIER_WITH_OS_IMAGE_COMP@JETSON_AGX_XAVIER_TARGETS: --- Error: Reading board information failed.
15:42:03.283 - info: Event: NV_L4T_FLASH_JETSON_XAVIER_WITH_OS_IMAGE_COMP@JETSON_AGX_XAVIER_TARGETS - error is: --- Error: Reading board information failed.
15:42:03.283 - info: NV_L4T_FLASH_JETSON_XAVIER_WITH_OS_IMAGE_COMP@JETSON_AGX_XAVIER_TARGETS: [ Component Install Finished with Error ]
15:42:03.283 - info: NV_L4T_FLASH_JETSON_XAVIER_WITH_OS_IMAGE_COMP@JETSON_AGX_XAVIER_TARGETS: [host] [ 684.00 KB used. Disk Avail: 227.13 GB ]
15:42:03.283 - info: NV_L4T_FLASH_JETSON_XAVIER_WITH_OS_IMAGE_COMP@JETSON_AGX_XAVIER_TARGETS: [ NV_L4T_FLASH_JETSON_XAVIER_WITH_OS_IMAGE_COMP Install took 17s ]
15:42:03.284 - info: NV_L4T_FLASH_JETSON_XAVIER_WITH_OS_IMAGE_COMP@JETSON_AGX_XAVIER_TARGETS: 
15:42:03.284 - error: command error code: 11
15:42:03.284 - info: Event: NV_L4T_FLASH_JETSON_XAVIER_WITH_OS_IMAGE_COMP@JETSON_AGX_XAVIER_TARGETS - error code is: 1011
15:42:03.284 - error: NV_L4T_FLASH_JETSON_XAVIER_WITH_OS_IMAGE_COMP@JETSON_AGX_XAVIER_TARGETS: command terminated with error
15:42:03.284 - info: Event: NV_L4T_FLASH_JETSON_XAVIER_WITH_OS_IMAGE_COMP@JETSON_AGX_XAVIER_TARGETS - error is: command terminated with error
15:42:03.293 - info: Event: NV_L4T_FLASH_JETSON_XAVIER_WITH_OS_IMAGE_COMP@JETSON_AGX_XAVIER_TARGETS - install ended - failure
15:42:03.295 - info: Summary: NV_L4T_FLASH_JETSON_XAVIER_WITH_OS_IMAGE_COMP@JETSON_AGX_XAVIER_TARGETS: Installation failed. 

• We can flash JAXi via “flash.sh”. But the Ubuntu install process seems never completed and stuck in the orange background.

We don’t have any available AGX Dev kit left for AB testing.

Any help or possible solution is appreciated.
Best regards.

[WayneWWW]

1. If you want to share any log, share the complete log. Do not just share me the last few lines.

2. Please compare if your flash.sh and sdkmanager are really flashing the same board config. Also, if you don’t apply any patch, will flash.sh be able to flash too?

3. In your system that is able to boot up, could you dump the uart log? so that we can tell what gets stuck there?

[kaichu.wu]

log.zip (131.9 KB)

Hello Wayne,

Thanks for the quick response!

1. The completed log is attached.
2. flash.sh can flash our custom carrier board without any patch.
3. We didn’t expose the original debug uart. How can I change the debug uart to /dev/ttyTHS4?

Thanks!

[WayneWWW]

Use dtc tool to modify the bpmp dtb back to dts and modify the “port” under the serial. Rebuild the dtb file again with dtc tool and flash this new bpmp dtb.

[WayneWWW]

Also, ttyTHS4 should be disabled in kernel device tree.

[WayneWWW]

If exposing out the debug uart pin is easier for you, then just expose them out.

It would be easier to use the default uart port.

[kaichu.wu]

Hello Wayne,

Thanks for the quick response.

After skipping the OEM-config process, we can see the Ubuntu desktop successfully, but with some sudo permission error.

Then, we found inspiration from the article below.

Flashed TX2 and sudo failed

That is a problem. It means the sample rootfs was likely not unpacked by root (only root can preserve sudo permissions). There are many other files which would also have failed, you just found the first thing most people run into when sample rootfs is unpacked incorrectly (similar issues with not using sudo during apply_binaries.sh). On JetPack you should use your regular user, and then it prompts for password…but with command line you just have to use sudo directly for rootfs and apply_binaries…

The solution is to delete the L4T folder and download a clean one via SDKManager.

The cause of our issue is related to the false permission of rootfs on the host machine, which generates a system image with false permission.

Best,
Kaichu