Not support by U-Boot

[jay72]

trying to flash BoardID3636, getting above msg
sudo ./flash.sh -r -k jetson-tx2 mmcblk0p1
pls advise.

[DaveYYY]

Hi,

Please give more information so we know what’s happening; we don’t do telepathy.

1. P3636 is the TX2 NX module, which is to be used with the Xavier NX DevKit, and flashed with jetson-xavier-nx-devkit-tx2-nx, not jetson-tx2.
2. Please provide both the flashing log from the host and the serial console log from the device here.
3. What’s the purpose of using -r -k in the flashing command? Are you re-using the system image?

[jay72]

sudo ./flash.sh -r -k kernel-dtb jetson-tx2 mmcblk0p1

###############################################################################
# L4T BSP Information:
# R32 , REVISION: 7.3
###############################################################################
# Target Board Information:
# Name: jetson-tx2, Board Family: t186ref, SoC: Tegra 186, 
# OpMode: production, Boot Authentication: NS, 
# Disk encryption: disabled ,
###############################################################################
./tegraflash.py --chip 0x18 --applet "/home/user/nvidia/nvidia_sdk/JetPack_4.6.3_Linux_JETSON_TX2_TARGETS/Linux_for_Tegra/bootloader/mb1_recovery_prod.bin" --skipuid --cmd "dump eeprom boardinfo cvm.bin" 
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.0069 ] Generating RCM messages
[   0.0094 ] tegrarcm_v2 --listrcm rcm_list.xml --chip 0x18 0 --download rcm /home/jay/nvidia/nvidia_sdk/JetPack_4.6.3_Linux_JETSON_TX2_TARGETS/Linux_for_Tegra/bootloader/mb1_recovery_prod.bin 0 0
[   0.0105 ] RCM 0 is saved as rcm_0.rcm
[   0.0118 ] RCM 1 is saved as rcm_1.rcm
[   0.0118 ] List of rcm files are saved in rcm_list.xml
[   0.0118 ] 
[   0.0119 ] Signing RCM messages
[   0.0148 ] tegrasign_v3.py --key None --list rcm_list.xml --pubkeyhash pub_key.key
[   0.0149 ] Assuming zero filled SBK key
[   0.0351 ] Copying signature to RCM mesages
[   0.0382 ] tegrarcm_v2 --chip 0x18 0 --updatesig rcm_list_signed.xml
[   0.0407 ] 
[   0.0408 ] Boot Rom communication
[   0.0438 ] tegrarcm_v2 --chip 0x18 0 --rcm rcm_list_signed.xml --skipuid
[   0.0453 ] RCM version 0X180001
[   0.0724 ] Boot Rom communication completed
[   1.0787 ] 
[   2.0842 ] tegrarcm_v2 --isapplet
[   2.0868 ] Applet version 01.00.0000
[   2.1180 ] 
[   2.1218 ] Retrieving EEPROM data
[   2.1220 ] tegrarcm_v2 --oem platformdetails eeprom cvm /home/jay/nvidia/nvidia_sdk/JetPack_4.6.3_Linux_JETSON_TX2_TARGETS/Linux_for_Tegra/bootloader/cvm.bin
[   2.1239 ] Applet version 01.00.0000
[   2.2183 ] Saved platform info in /home/jay/nvidia/nvidia_sdk/JetPack_4.6.3_Linux_JETSON_TX2_TARGETS/Linux_for_Tegra/bootloader/cvm.bin
[   2.2913 ] 
Board ID(3636) version(301) sku(0001) revision(D.0)
not supported by U-Boot

[DaveYYY]

@DaveYYY

P3636 is the TX2 NX module, which is to be used with the Xavier NX DevKit, and flashed with jetson-xavier-nx-devkit-tx2-nx, not jetson-tx2.

Have you checked this?
Do you know what carrier board you are using?

[jay72]

pls indicate where do v find the carrier board details

P3636 is the TX2 NX module, which is to be used with the Xavier NX DevKit, and flashed with jetson-xavier-nx-devkit-tx2-nx, not jetson-tx2.
—not checked, want to make sure the params r correct

[DaveYYY]

If you don’t know what you are doing, then just take a picture of your hardware setup.

@jay72

—not checked, want to make sure the params r correct

Clearly it’s incorrect.

[DaveYYY]

The carrier board for Xavier NX/TX2 NX looks like this:

The carrier board for TX2 looks like this:

[jay72]

it is the Xavier NX/TX2 NX and also confirmed with the .conf file in the flash folder.
the process is gone thru.
thanks for the kind assistance.