Parsing board information failed

Hey,
I am trying to flash an Xavier AGX module with Rogue Carrier for NVIDIA® Jetson AGX Xavier™
but it fails with this error message:

Parsing board information failed.

The whole terminal log:

~~~~~~~~~~~~~~~~~~~~~~~~~~~
      Xavier Modules       
~~~~~~~~~~~~~~~~~~~~~~~~~~~
1. Xavier
2. Xavier Industrial
3. Cancel (back to main)
Enter choice:  1
cti/xavier/rogueX/base
###############################################################################
# L4T BSP Information:
# R32 , REVISION: 7.1
###############################################################################
# Target Board Information:
# Name: cti-agx-agx103-00, Board Family: t186ref, SoC: Tegra 194, 
# OpMode: production, Boot Authentication: NS, 
# Disk encryption: disabled ,
###############################################################################
copying soft_fuses(/home/home/nvidia/nvidia_sdk/JetPack_4.6.1_Linux_JETSON_AGX_XAVIER_TARGETS/Linux_for_Tegra/bootloader/t186ref/BCT/tegra194-mb1-soft-fuses-l4t.cfg)... done.
./tegraflash.py --chip 0x19 --applet "/home/home/nvidia/nvidia_sdk/JetPack_4.6.1_Linux_JETSON_AGX_XAVIER_TARGETS/Linux_for_Tegra/bootloader/mb1_t194_prod.bin" --skipuid --soft_fuses tegra194-mb1-soft-fuses-l4t.cfg --bins "mb2_applet nvtboot_applet_t194.bin" --cmd "dump eeprom boardinfo cvm.bin;reboot recovery" 
Welcome to Tegra Flash
version 1.0.0
Type ? or help for help and q or quit to exit
Use ! to execute system commands
 
[   0.0032 ] Generating RCM messages
[   0.0054 ] tegrahost_v2 --chip 0x19 0 --magicid MB1B --appendsigheader /home/home/nvidia/nvidia_sdk/JetPack_4.6.1_Linux_JETSON_AGX_XAVIER_TARGETS/Linux_for_Tegra/bootloader/mb1_t194_prod.bin zerosbk
[   0.0060 ] Header already present for /home/home/nvidia/nvidia_sdk/JetPack_4.6.1_Linux_JETSON_AGX_XAVIER_TARGETS/Linux_for_Tegra/bootloader/mb1_t194_prod.bin
[   0.0085 ] 
[   0.0106 ] tegrasign_v3.py --getmode mode.txt --key None
[   0.0107 ] Assuming zero filled SBK key
[   0.0127 ] tegrasign_v3.py --file /home/home/nvidia/nvidia_sdk/JetPack_4.6.1_Linux_JETSON_AGX_XAVIER_TARGETS/Linux_for_Tegra/bootloader/mb1_t194_prod_sigheader.bin --key None --length 1136 --offset 2960 --pubkeyhash pub_key.key
[   0.0127 ] Assuming zero filled SBK key
[   0.0165 ] tegrahost_v2 --chip 0x19 0 --updatesigheader /home/home/nvidia/nvidia_sdk/JetPack_4.6.1_Linux_JETSON_AGX_XAVIER_TARGETS/Linux_for_Tegra/bootloader/mb1_t194_prod_sigheader.bin /home/home/nvidia/nvidia_sdk/JetPack_4.6.1_Linux_JETSON_AGX_XAVIER_TARGETS/Linux_for_Tegra/bootloader/mb1_t194_prod_sigheader.hash zerosbk
[   0.0194 ] 
[   0.0214 ] tegrabct_v2 --chip 0x19 0 --sfuse tegra194-mb1-soft-fuses-l4t.cfg.pdf sfuse.bin
[   0.0223 ] 
[   0.0243 ] tegrarcm_v2 --listrcm rcm_list.xml --chip 0x19 0 --sfuses sfuse.bin --download rcm /home/home/nvidia/nvidia_sdk/JetPack_4.6.1_Linux_JETSON_AGX_XAVIER_TARGETS/Linux_for_Tegra/bootloader/mb1_t194_prod_sigheader.bin 0 0
[   0.0249 ] RCM 0 is saved as rcm_0.rcm
[   0.0272 ] RCM 1 is saved as rcm_1.rcm
[   0.0272 ] RCM 2 is saved as rcm_2.rcm
[   0.0272 ] List of rcm files are saved in rcm_list.xml
[   0.0272 ] 
[   0.0273 ] Signing RCM messages
[   0.0295 ] tegrasign_v3.py --getmontgomeryvalues montgomery.bin --key None --list rcm_list.xml --pubkeyhash pub_key.key
[   0.0298 ] Assuming zero filled SBK key
[   0.0522 ] Copying signature to RCM mesages
[   0.0555 ] tegrarcm_v2 --chip 0x19 0 --updatesig rcm_list_signed.xml
[   0.0581 ] 
[   0.0582 ] Boot Rom communication
[   0.0607 ] tegrarcm_v2 --chip 0x19 0 --rcm rcm_list_signed.xml --skipuid
[   0.0618 ] RCM version 0X190001
[   0.0629 ] Boot Rom communication completed
[   1.0795 ] 
[   2.0854 ] tegrarcm_v2 --isapplet
[   2.0880 ] Applet version 01.00.0000
[   2.0912 ] 
[   2.0955 ] tegrarcm_v2 --ismb2
[   2.1012 ] 
[   2.1032 ] tegrahost_v2 --chip 0x19 --align nvtboot_applet_t194.bin
[   2.1041 ] 
[   2.1063 ] tegrahost_v2 --chip 0x19 0 --magicid PLDT --appendsigheader nvtboot_applet_t194.bin zerosbk
[   2.1069 ] adding BCH for nvtboot_applet_t194.bin
[   2.1093 ] 
[   2.1120 ] tegrasign_v3.py --key None --list nvtboot_applet_t194_sigheader.bin_list.xml --pubkeyhash pub_key.key
[   2.1121 ] Assuming zero filled SBK key
[   2.1167 ] tegrahost_v2 --chip 0x19 0 --updatesigheader nvtboot_applet_t194_sigheader.bin.encrypt nvtboot_applet_t194_sigheader.bin.hash zerosbk
[   2.1189 ] 
[   2.1214 ] tegrarcm_v2 --download mb2 nvtboot_applet_t194_sigheader.bin.encrypt
[   2.1221 ] Applet version 01.00.0000
[   2.1243 ] Sending mb2
[   2.1244 ] [................................................] 100%
[   2.1413 ] 
[   2.1454 ] tegrarcm_v2 --boot recovery
[   2.1478 ] Applet version 01.00.0000
[   2.1551 ] 
[   3.1614 ] tegrarcm_v2 --isapplet
[   3.1676 ] 
[   3.1695 ] tegrarcm_v2 --ismb2
[   3.1699 ] MB2 Applet version 01.00.0000
[   3.1720 ] 
[   3.1736 ] tegrarcm_v2 --ismb2
[   3.1744 ] MB2 Applet version 01.00.0000
[   3.1769 ] 
[   3.1801 ] Retrieving board information
[   3.1821 ] tegrarcm_v2 --oem platformdetails chip chip_info.bin
[   3.1827 ] MB2 Applet version 01.00.0000
[   3.1871 ] Saved platform info in chip_info.bin
[   3.1914 ] Chip minor revision: 2
[   3.1915 ] Bootrom revision: 0xf
[   3.1916 ] Ram code: 0x2
[   3.1916 ] Chip sku: 0xd0
[   3.1917 ] Chip Sample: non es
[   3.1920 ] 
[   3.1923 ] Retrieving EEPROM data
[   3.1924 ] tegrarcm_v2 --oem platformdetails eeprom cvm /home/home/nvidia/nvidia_sdk/JetPack_4.6.1_Linux_JETSON_AGX_XAVIER_TARGETS/Linux_for_Tegra/bootloader/cvm.bin
[   3.1934 ] MB2 Applet version 01.00.0000
[   3.1975 ] Saved platform info in /home/home/nvidia/nvidia_sdk/JetPack_4.6.1_Linux_JETSON_AGX_XAVIER_TARGETS/Linux_for_Tegra/bootloader/cvm.bin
[   3.2325 ] 
[   3.2327 ] Rebooting to recovery mode
[   3.2363 ] tegrarcm_v2 --ismb2
[   3.2374 ] MB2 Applet version 01.00.0000
[   3.2396 ] 
[   3.2396 ] Rebooting to recovery mode
[   3.2414 ] tegrarcm_v2 --reboot recovery
[   3.2420 ] MB2 Applet version 01.00.0000
[   3.2508 ] 
Parsing board information failed.
root@home-Latitude-5491:~/nvidia/nvidia_sdk/JetPack_4.6.1_Linux_JETSON_AGX_XAVIER_TARGETS/Linux_for_Tegra# cd bootloader/
root@home-Latitude-5491:~/nvidia/nvidia_sdk/JetPack_4.6.1_Linux_JETSON_AGX_XAVIER_TARGETS/Linux_for_Tegra/bootloader# ./chkbdinfo -i cvm.bin
ERROR: calculated CRC8 0xec != stored CRC8 0x13
root@home-Latitude-5491:~/nvidia/nvidia_sdk/JetPack_4.6.1_Linux_JETSON_AGX_XAVIER_TARGETS/Linux_for_Tegra/bootloader#

I have several modules with several carriers and the others works well.
Any idea what could happened?

The problem is that somehow your module eeprom value is being modified. But somehow the last bit which represents for CRC checksum does not get update.

If the board still able to boot up, which i2c tool to modify the eeprom value.

Yes,
the module can be boot up (with old Jetpack - 4.5)
how can i reflash it?

This is nothing related to “re-flash”. Reflash 1000 times won’t restore it.

You have to modify the eeprom value. This is a memory that won’t change by sdkmanager or any other flash tool. You can only modify it with i2c tool.

Read the module eeprom layout and check if your eeprom still has correct value or not.

https://docs.nvidia.com/jetson/l4t/index.html#page/Tegra%20Linux%20Driver%20Package%20Development%20Guide/jetson_eeprom_layout.html

Hey,
Thank you for fast replying.
I have two boards, with same carrier.
One of them is Jetpack 4.5 with eeprom values:


0x01
0x00
0xff
0x00
0x48
0x0b
0x04
0x00
0x04
0x50
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x36
0x39
0x39
0x2d
0x38
0x32
0x38
0x38
0x38
0x2d
0x30
0x30
0x30
0x34
0x2d
0x34
0x30
0x30
0x20
0x50
0x2e
0x30
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0xff
0xff
0xff
0xff
0xff
0xff
0xff
0xff
0xff
0xff
0xff
0xff
0xff
0xff
0xff
0xff
0xff
0xff
0xf3
0x34
0x4d
0x2d
0xb0
0x48
0x31
0x34
0x32
0x33
0x36
0x32
0x31
0x30
0x36
0x34
0x32
0x34
0x35
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0xff
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x4e
0x56
0x43
0x42
0x1c
0x00
0x4d
0x31
0x00
0x00
0xff
0xff
0xff
0xff
0xff
0xff
0xff
0xff
0xff
0xff
0xff
0xff
0xf3
0x34
0x4d
0x2d
0xb0
0x48
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x13

the second one is with Jetpack 4.6.1 that works well.

0x01
0x00
0xff
0x00
0x48
0x0b
0x04
0x00
0x04
0x50
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x36
0x39
0x39
0x2d
0x38
0x32
0x38
0x38
0x38
0x2d
0x30
0x30
0x30
0x34
0x2d
0x34
0x30
0x30
0x20
0x50
0x2e
0x30
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0xff
0xff
0xff
0xff
0xff
0xff
0xff
0xff
0xff
0xff
0xff
0xff
0xff
0xff
0xff
0xff
0xff
0xff
0xf5
0x34
0x4d
0x2d
0xb0
0x48
0x31
0x34
0x32
0x33
0x36
0x32
0x31
0x30
0x36
0x34
0x32
0x34
0x31
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x4e
0x56
0x43
0x42
0x1c
0x00
0x4d
0x31
0x00
0x00
0xff
0xff
0xff
0xff
0xff
0xff
0xff
0xff
0xff
0xff
0xff
0xff
0xf5
0x34
0x4d
0x2d
0xb0
0x48
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0xbb

The differences between two AGXs are:

  1. UUID
  2. MAC address
  3. Byte #129 that is 0xff in the module that invalid to flash and 0x00 in the new one the byte title is “Reserved”.

Can I write a new CRC in the EEPROM?

The CRC is just the last bit of the eeprom. Yes, you can write.

I’ll try it,
Where can I find information about byte #129 that has been changed from 0x00 to 0xff?

If that is reserved, then the value does not matter.

It works,
Thank you

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.