can i flash partition update ?

hi

Jetson TX2 Document

Flashing U-Boot Only
To flash the full L4T image to the reference platform see Flashing U-Boot Full L4T Image above. To flash a new version of U-Boot, perform the following:
To flash the new U-Boot
•Execute the following command on Jetson TX1:
sudo ./flash.sh -k EBT <platform> mmcblk0p1 •Execute the following command on Jetson TX2: sudo ./flash.sh -k kernel mmcblk0p1

i tested tx1 ok
i tested tx2 not ok

can i flash partition update ?

sudo ./flash.sh -k kernel jetson-tx2 mmcblk0p1
./tegraflash.py --chip 0x18 --applet “/mnt/ILPSANGEL01/JETSON.TX2/Linux_for_Tegra/bootloader/mb1_recovery_prod.bin” --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.0914 ] Generating RCM messages
[ 0.1036 ] tegrarcm_v2 --listrcm rcm_list.xml --chip 0x18 --download rcm /mnt/ILPSANGEL01/JETSON.TX2/Linux_for_Tegra/bootloader/mb1_recovery_prod.bin 0 0
[ 0.1156 ] RCM 0 is saved as rcm_0.rcm
[ 0.1228 ] RCM 1 is saved as rcm_1.rcm
[ 0.1270 ] List of rcm files are saved in rcm_list.xml
[ 0.1297 ]
[ 0.1297 ] Signing RCM messages
[ 0.1414 ] tegrasign_v2 --key None --list rcm_list.xml --pubkeyhash pub_key.key
[ 0.1447 ] Assuming zero filled SBK key
[ 0.1770 ]
[ 0.1771 ] Copying signature to RCM mesages
[ 0.1904 ] tegrarcm_v2 --chip 0x18 --updatesig rcm_list_signed.xml
[ 0.2231 ]
[ 0.2232 ] Boot Rom communication
[ 0.2350 ] tegrarcm_v2 --chip 0x18 --rcm rcm_list_signed.xml
[ 0.2383 ] BootRom is not running
[ 0.2929 ]
[ 5.3882 ] Retrieving EEPROM data
[ 5.3885 ] tegrarcm_v2 --oem platformdetails eeprom cvm /mnt/ILPSANGEL01/JETSON.TX2/Linux_for_Tegra/bootloader/cvm.bin

holding <<<<<<<<<<<<<<

hello walterkim,

i’ve test jetson tx2 with updating the kernel partition without the system holding failure.
may i know which JetPack version you were using?
thanks

Hi walterkim,

Is this still an issue in your project?
Please update the status then we can help to resolve it.

Thanks

I do see something which might be an issue. The command line was this:

sudo ./flash.sh <b>-k kernel</b> jetson-tx2 mmcblk0p1

If using lower case “-k”, then you name a partition ID, e.g., “-k EBT” or “-k LNX”. The word “kernel” is not defined. If you use the “-K” upper case, then it is for the name of an actual kernel Image file.

So this section below in the document is not correct for TX2?

///////////////////////////////////////////////
To flash the new U-Boot
•Execute the following command on Jetson TX1:
sudo ./flash.sh -k EBT <platform> mmcblk0p1 •Execute the following command on Jetson TX2: sudo ./flash.sh -k kernel mmcblk0p1
/////////////////////////////////////////////////

I think just -K is right for updating kernel partition.

So how do I flash only the new U-Boot on TX2
Does it also use “sudo ./flash.sh -k EBT mmcblk0p1”

and how about the following description? is it correct for just to update kernel?
//////////////////////////////////////////////////////////////////////
Replacing the Kernel
You can replace the kernel with your own custom kernel. Use the procedure that applies to the type of storage device from which your device boots.
To replace the kernel in systems that boot from internal eMMC
These steps can be used in SD card and USB storage device cases.

  1. Boot the Jetson TX1/TX2 system.
  2. Copy the new kernel files, using scp, into the /boot directory.
  3. Reboot the Jetson TX1/TX2 system.
    /////////////////////////////////////////////////////////////////////////////////////////

Thanks

hello jason2_fan,

there’s erroneous in the R28.1 documentation.
we should use below commands to update u-boot partition for R28.1/TX1,

$ sudo ./flash.sh –k LNX jetson-tx1 mmcblk0p1

and below commands for R28.1/TX2.

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