Hello,
I am working with the Jetson TX2 platform using an Auvidea J140 daughter board and JetPack 3.3.
For our project I have modified and rebuild the kernel and device tree using instructions from RidgeRun (https://developer.ridgerun.com/wiki/index.php?title=Compiling_Jetson_TX1/TX2_source_code)
When I use the JetPack UI I can properly flash the board and install software.
However, for testing I need to make changes to the device tree so I need to be able to flash the DTB only.
Again using the instructions from RidgeRun I have been able to do so but now I have an issue.
Putting the board in recovery mode and running
sudo ./flash.sh -r -k kernel-dtb jetson-tx2 mmcblk1p1
I get the following error :
###############################################################################
# L4T BSP Information:
# R28 (release), REVISION: 2.1, GCID: 11272647, BOARD: t186ref, EABI: aarch64,
# DATE: Thu May 17 07:29:06 UTC 2018
###############################################################################
Error: probing the target board failed.
Make sure the target board is connected through
micro-B USB port and is in recovery mode.
augmenta@augmenta-ThinkPad-T460:/media/augmenta/JetPack/JetPack3.3/64_TX2/Linux_for_Tegra$ sudo ./flash.sh -r -k kernel-dtb jetson-tx2 mmcblk1p1
###############################################################################
# L4T BSP Information:
# R28 (release), REVISION: 2.1, GCID: 11272647, BOARD: t186ref, EABI: aarch64,
# DATE: Thu May 17 07:29:06 UTC 2018
###############################################################################
# Target Board Information:
# Name: jetson-tx2, Board Family: t186ref, SoC: Tegra 186,
# OpMode: production, Boot Authentication: ,
###############################################################################
./tegraflash.py --chip 0x18 --applet "/media/augmenta/JetPack/JetPack3.3/64_TX2/Linux_for_Tegra/bootloader/mb1_recovery_prod.bin" --cmd "dump eeprom boardinfo cvm.bin" --skipuid
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.0025 ] Generating RCM messages
[ 0.0035 ] tegrarcm_v2 --listrcm rcm_list.xml --chip 0x18 --download rcm /media/augmenta/JetPack/JetPack3.3/64_TX2/Linux_for_Tegra/bootloader/mb1_recovery_prod.bin 0 0
[ 0.0044 ] RCM 0 is saved as rcm_0.rcm
[ 0.0049 ] RCM 1 is saved as rcm_1.rcm
[ 0.0049 ] List of rcm files are saved in rcm_list.xml
[ 0.0049 ]
[ 0.0050 ] Signing RCM messages
[ 0.0059 ] tegrasign_v2 --key None --list rcm_list.xml --pubkeyhash pub_key.key
[ 0.0067 ] Assuming zero filled SBK key
[ 0.0103 ]
[ 0.0103 ] Copying signature to RCM mesages
[ 0.0112 ] tegrarcm_v2 --chip 0x18 --updatesig rcm_list_signed.xml
[ 0.0124 ]
[ 0.0125 ] Boot Rom communication
[ 0.0133 ] tegrarcm_v2 --chip 0x18 --rcm rcm_list_signed.xml --skipuid
[ 0.0142 ] RCM version 0X180001
[ 0.0153 ] Boot Rom communication completed
[ 1.0237 ]
[ 1.0280 ] tegrarcm_v2 --isapplet
[ 1.0320 ] Applet version 01.00.0000
[ 1.0531 ]
[ 1.0579 ] Retrieving EEPROM data
[ 1.0586 ] tegrarcm_v2 --oem platformdetails eeprom cvm /media/augmenta/JetPack/JetPack3.3/64_TX2/Linux_for_Tegra/bootloader/cvm.bin
[ 1.0634 ] Applet version 01.00.0000
[ 1.0819 ] Saved platform info in /media/augmenta/JetPack/JetPack3.3/64_TX2/Linux_for_Tegra/bootloader/cvm.bin
[ 1.1599 ]
Parsing board information failed.
However, if I run JetPack UI it works.
Any ideas on what could be the issue ?
I really don’t want to have to re-flash the entire TX2 image and s/w every time I need to test a change in the device tree
Thank you in advance for your assistance.