SDK Manager 1.9.3.10904 installation failed with JetPack5.1.2

I ran SDK Manager with by selecting only Jetson Linux on Step2. I followed manual mode operation flow with jumper’ed recovery mode, and then Step4, process stopped with errors - saying “/misc/tsc_controls/xxxx is not supported”.
How can I resolved this?

===============================
21:50:00 DEBUG: running command < true >

21:50:00 INFO: exec_command: true

21:50:00 INFO: command finished successfully

21:50:00 DEBUG: Flash Jetson Linux - flash: using adapter to install NV_L4T_FLASH_JETSON_LINUX_COMP@JETSON_ORIN_NANO_TARGETS to /home/jaoki/nvidia/nvidia_sdk/JetPack_5.1.2_Linux_JETSON_ORIN_NANO_TARGETS

21:50:00 INFO: Flash Jetson Linux - flash: change working directory to /home/jaoki/nvidia/nvidia_sdk/JetPack_5.1.2_Linux_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegra

21:50:00 INFO: Flash Jetson Linux - flash: exec_command: /tmp/tmp_NV_L4T_FLASH_JETSON_LINUX_COMP.sh

21:50:00 INFO: Flash Jetson Linux - flash: sudo ./nvsdkmanager_flash.sh --storage mmcblk1p1 --nv-auto-config --username wruser

21:50:00 INFO: Flash Jetson Linux - flash: user entered mmcblk1p1 --nv-auto-config --username wruser

21:50:00 INFO: Flash Jetson Linux - flash: *** Checking ONLINE mode … OK.

21:50:00 INFO: Flash Jetson Linux - flash: *** Checking target board connection … 1 connections found.

21:50:01 INFO: Flash Jetson Linux - flash: *** Reading ECID … FUSELEVEL=fuselevel_production hwchipid=0x23 bootauth=NS

21:50:01 INFO: Flash Jetson Linux - flash: *** Reading EEPROM … “/home/jaoki/nvidia/nvidia_sdk/JetPack_5.1.2_Linux_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegra/bootloader/tegraflash.py” --chip 0x23 --applet “/home/jaoki/nvidia/nvidia_sdk/JetPack_5.1.2_Linux_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegra/bootloader/mb1_t234_prod.bin” --cfg readinfo_t234_min_prod.xml --dev_params tegra234-br-bct-diag-boot.dts --device_config tegra234-mb1-bct-device-p3701-0000.dts --misc_config tegra234-mb1-bct-misc-p3701-0000.dts --bins “mb2_applet applet_t234.bin” --skipuid --cmd “dump eeprom cvm cvm.bin; reboot recovery”

21:50:01 INFO: Flash Jetson Linux - flash: [ 0.0610 ] MB1: Nvheader already present is mb1_t234_prod_aligned.bin

21:50:01 INFO: Flash Jetson Linux - flash: [ 0.0624 ] Header already present for mb1_t234_prod_aligned_sigheader.bin

21:50:01 INFO: Flash Jetson Linux - flash: [ 0.0682 ] Header already present for mb1_t234_prod_aligned_sigheader.bin

21:50:01 INFO: Flash Jetson Linux - flash: [ 0.0689 ] MB1: Nvheader already present is psc_bl1_t234_prod_aligned.bin

21:50:01 INFO: Flash Jetson Linux - flash: [ 0.0736 ] Header already present for psc_bl1_t234_prod_aligned_sigheader.bin

21:50:01 INFO: Flash Jetson Linux - flash: [ 0.0742 ] adding BCH for mb2_t234_aligned.bin

21:50:01 INFO: Flash Jetson Linux - flash: [ 0.0773 ] MB1: Nvheader already present is psc_bl1_t234_prod_aligned.bin

21:50:01 INFO: Flash Jetson Linux - flash: [ 0.0881 ] Header already present for psc_bl1_t234_prod_aligned_sigheader.bin

21:50:01 INFO: Flash Jetson Linux - flash: [ 0.0887 ] adding BCH for mb2_t234_aligned.bin

21:50:01 INFO: Flash Jetson Linux - flash: [ 0.1146 ] WARNING: boot chain is not completed. set to 0

21:50:01 INFO: Flash Jetson Linux - flash: [ 0.1231 ] Assuming zero filled SBK key

21:50:01 INFO: Flash Jetson Linux - flash: [ 0.1557 ] Assuming zero filled SBK key

21:50:01 INFO: Flash Jetson Linux - flash: [ 0.1646 ] Assuming zero filled SBK key

21:50:01 INFO: Flash Jetson Linux - flash: [ 0.1708 ] MB1-BCT version: 0.10

21:50:01 ERROR: Flash Jetson Linux - flash: [ 0.1720 ] ERROR: /misc/tsc_controls/tsc_locking_ref_frequency_configuration is not supported

21:50:01 INFO: Flash Jetson Linux - flash: [ 0.1800 ] tegrahost_v2 --chip 0x23 0 --magicid MBCT --appendsigheader mb1_cold_boot_bct_MB1_aligned.bct zerosbk

21:50:01 INFO: Flash Jetson Linux - flash: [ 0.1892 ] Assuming zero filled SBK key

21:50:01 INFO: Flash Jetson Linux - flash: [ 0.1912 ] MB1-BCT version: 0.10

21:50:01 ERROR: Flash Jetson Linux - flash: [ 0.1925 ] ERROR: /misc/tsc_controls/tsc_locking_control is not supported

21:50:01 INFO: Flash Jetson Linux - flash: [ 0.2002 ] tegrahost_v2 --chip 0x23 0 --magicid MBCT --appendsigheader mb1_bct_MB1_aligned.bct zerosbk

21:50:01 INFO: Flash Jetson Linux - flash: [ 0.2094 ] Assuming zero filled SBK key

21:50:01 INFO: Flash Jetson Linux - flash: [ 0.2201 ] BR_CID: 0x80012344705DE64C8400000007010200

21:50:01 INFO: Flash Jetson Linux - flash: [ 0.2458 ] Sending bct_br

21:50:06 ERROR: Flash Jetson Linux - flash: [ 0.2896 ] ERROR: might be timeout in USB write.

21:50:06 INFO: Flash Jetson Linux - flash: Command tegrarcm_v2 --new_session --chip 0x23 0 --uid --download bct_br br_bct_BR.bct --download mb1 mb1_t234_prod_aligned_sigheader.bin.encrypt --download psc_bl1 psc_bl1_t234_prod_aligned_sigheader.bin.encrypt --download bct_mb1 mb1_bct_MB1_sigheader.bct.encrypt

21:50:06 ERROR: Flash Jetson Linux - flash: — Error: Reading board information failed.

21:50:06 ERROR: Flash Jetson Linux - flash: *** ERROR: Parsing boardid failed

21:50:06 ERROR: Flash Jetson Linux - flash: command terminated with error

21:50:06 SUMMARY: Flash Jetson Linux - flash: First Error: Installation failed.

Hi,

I think this log does not matter.

This is the real issue here.
Can you please check when this error happened, was serial console outputting anything?
If it was not, then please try the following method:

  1. Try with different USB cables/ports
  2. Use Ubuntu 18.04 in case it’s 20.04 (Please do not use a virtual machine)
  3. Run the following command on your host PC:
sudo -s
echo -1 > /sys/module/usbcore/parameters/autosuspend

Could you also try to reboot your host PC and hotplug usb cable more times and see if you can bypass it?

And please share the host PC info here.

Here is my host PC info.

cat /etc/os-release
NAME=“Ubuntu”
VERSION=“20.04.6 LTS (Focal Fossa)”
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME=“Ubuntu 20.04.6 LTS”
VERSION_ID=“20.04”
HOME_URL=“https://www.ubuntu.com/
SUPPORT_URL=“https://help.ubuntu.com/
BUG_REPORT_URL=“Bugs : Ubuntu
PRIVACY_POLICY_URL=“Data privacy | Ubuntu
VERSION_CODENAME=focal
UBUNTU_CODENAME=focal

Still same write failure happens even if I change to other usb3-usb-c cables.
Is it possible to once write out l4t image into a file on the host Linux pc, and then flash it into sdcard using Etcher?

Thank you for your advice.

Hi,

are you using an SD card as the storage device?
If that’s the case, then maybe consider using the SD card image given in this link:
https://developer.nvidia.com/downloads/embedded/l4t/r35_release_v4.1/jp512-orin-nano-sd-card-image.zip

If it does not boot up, try flashing the QSPI memory on the module individually:

sudo ./flash.sh --no-systemimg -c bootloader/t186ref/cfg/flash_t234_qspi.xml jetson-orin-nano-devkit mmcblk1p1

Hi @j-aoki

This is ubuntu info but not host PC info.

There is a known issue that some kind of host PC will lead to such issue with ubuntu 20.04. So I already knew it would be ubuntu 20.04.

Please share what mother board, CPU are installed on your host PC. Such info will be more helpful to us.

Also, have you tried to totally cold boot your host PC and then flash?

Ah. My apologies. Here is the host pc hardware information.

Dell Optiplex 7070 Small Form Factor Desktop

Configuration:
CPU: Intel® Core™ i7-9700
Memory: 32GB
>>32GB 2x16GB DDR4 2666MHz UDIMM Non-ECC
HDD: 512G SSD
>>M.2 512GB PCIe NVMe Class 40 Solid State Drive

1 Like

I know and have successfully brought l4t up using the pre-build image written into microSD using Etcher.
What I’m trying to do is to build custom Linux into Jetson. More precisely to say, I’m going to build Yocto Linux for Orin.

I will try different host pc to connect with Orin nano.

Thank you.

1 Like

Hi @j-aoki

I just want to confirm, did you ever try the method to disable auto suspend mentioned here?

After you disable auto-suspend, please also replug the cable and re-put the board into recovery mode.

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