# Can't Flash Orin Production SoM **URL:** \ **Category:** Jetson AGX Orin\ **Tags:** reflash, board-design\ **Created:** [March 30, 2024, 11:37am UTC](https://forums.developer.nvidia.com/t/cant-flash-orin-production-som/287926 "2024-03-30T11:37:24Z")\ **Posts on this page:** 15\ **Page:** 1
**Author:** ![smcentee](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/smcentee/32/223479_2.png) [@smcentee](https://forums.developer.nvidia.com/u/smcentee)\ **Post date:** [March 30, 2024, 11:37am UTC](https://forums.developer.nvidia.com/t/cant-flash-orin-production-som/287926/1 "2024-03-30T11:37:24Z")
I am having trouble flashing a production Orin SoM in our custom carrier board. If I place the SoM in the dev kit, I can flash it without issue, but if I try and flash it while in our system, it fails as follows: > ############################################################################### > > # L4T BSP Information: > > # R35 , REVISION: 4.1 > > # User release: 0.0 > > ############################################################################### > > # Target Board Information: > > # Name: auto2-gpgpu, Board Family: t186ref, SoC: Tegra 234, > > # OpMode: production, Boot Authentication: NS, > > # Disk encryption: disabled , > > ############################################################################### > copying emc\_fuse\_dev\_params(/home/jimmy/Downloads/nvidia/hw/Auto2/JetPack\_5.1.2\_Linux\_JETSON\_AGX\_ORIN\_TARGETS/Linux\_for\_Tegra/bootloader/t186ref/BCT/tegra234-br-bct-diag-boot.dts)… done. > copying device\_config(/home/jimmy/Downloads/nvidia/hw/Auto2/JetPack\_5.1.2\_Linux\_JETSON\_AGX\_ORIN\_TARGETS/Linux\_for\_Tegra/bootloader/t186ref/BCT/tegra234-mb1-bct-device-p3701-0000.dts)… done. > copying misc\_config(/home/jimmy/Downloads/nvidia/hw/Auto2/JetPack\_5.1.2\_Linux\_JETSON\_AGX\_ORIN\_TARGETS/Linux\_for\_Tegra/bootloader/t186ref/BCT/tegra234-mb1-bct-misc-p3701-0000.dts)… done. > ./tegraflash.py --chip 0x23 --applet “/home/jimmy/Downloads/nvidia/hw/Auto2/JetPack\_5.1.2\_Linux\_JETSON\_AGX\_ORIN\_TARGETS/Linux\_for\_Tegra/bootloader/mb1\_t234\_prod.bin” --skipuid --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” --cmd “dump eeprom cvm cvm.bin; dump custinfo custinfo\_out.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.0208] tegrarcm\_v2 --chip 0x23 0 --ismb2applet > [0.0216] File rcm\_state open failed > [0.0219] ERROR: failed to read rcm\_state > [0.0219] > [0.0227] tegrasign\_v3.py --key None --getmode mode.txt > [0.0230] Assuming zero filled SBK key > [0.0224] Pre-processing config: tegra234-mb1-bct-device-p3701-0000.dts > [0.0286] Pre-processing config: tegra234-mb1-bct-misc-p3701-0000.dts > [0.0385] Parsing partition layout > [0.0419] tegraparser\_v2 --pt readinfo\_t234\_min\_prod.xml.tmp > [0.0450] Kernel DTB used: None > [0.0450] WARNING: dce base dtb is not provided > > [0.0450] Parsing partition layout > [0.0479] tegraparser\_v2 --pt readinfo\_t234\_min\_prod.xml.tmp > [0.0493] Creating list of images to be signed > [0.0505] tegrahost\_v2 --chip 0x23 0 --partitionlayout readinfo\_t234\_min\_prod.xml.bin --list images\_list.xml zerosbk > [0.0515] MB1: Nvheader already present is mb1\_t234\_prod\_aligned.bin > [0.0528] Header already present for mb1\_t234\_prod\_aligned\_sigheader.bin > [0.0536] MB1: Nvheader already present is mb1\_t234\_prod\_aligned.bin > [0.0592] Header already present for mb1\_t234\_prod\_aligned\_sigheader.bin > [0.0594] MB1: Nvheader already present is psc\_bl1\_t234\_prod\_aligned.bin > [0.0655] Header already present for psc\_bl1\_t234\_prod\_aligned\_sigheader.bin > [0.0665] adding BCH for mb2\_t234\_aligned.bin > [0.0705] MB1: Nvheader already present is psc\_bl1\_t234\_prod\_aligned.bin > [0.0879] Header already present for psc\_bl1\_t234\_prod\_aligned\_sigheader.bin > [0.0882] adding BCH for mb2\_t234\_aligned.bin > [0.1094] Filling MB1 storage info > [0.1095] Parsing dev params for multi chains > [0.1164] Generating br-bct > [0.1174] Updating dev and MSS params in BR BCT > [0.1175] tegrabct\_v2 --dev\_param tegra234-br-bct-diag-boot\_cpp.dtb --brbct br\_bct.cfg --chip 0x23 0 > [0.1226] Updating bl info > [0.1274] tegrabct\_v2 --brbct br\_bct\_BR.bct --chip 0x23 0 --updateblinfo readinfo\_t234\_min\_prod.xml.bin > [0.1312] WARNING: boot chain is not completed. set to 0 > [0.1333] Generating signatures > [0.1341] tegrasign\_v3.py --key None --list images\_list.xml --pubkeyhash pub\_key.key --sha sha512 > [0.1344] Assuming zero filled SBK key > [0.1534] Warning: pub\_key.key is not found > [0.1531] Parsing dev params for multi chains > [0.1532] Generating br-bct > [0.1545] Updating dev and MSS params in BR BCT > [0.1546] tegrabct\_v2 --dev\_param tegra234-br-bct-diag-boot\_cpp.dtb --brbct br\_bct.cfg --chip 0x23 0 > [0.1704] Updating bl info > [0.1715] tegrabct\_v2 --brbct br\_bct\_BR.bct --chip 0x23 0 --updateblinfo readinfo\_t234\_min\_prod.xml.bin --updatesig images\_list\_signed.xml > [0.1723] WARNING: boot chain is not completed. set to 0 > [0.1735] Get Signed section of bct > [0.1751] tegrabct\_v2 --brbct br\_bct\_BR.bct --chip 0x23 0 --listbct bct\_list.xml > [0.1760] Signing BCT > [0.1768] tegrasign\_v3.py --key None --list bct\_list.xml --pubkeyhash pub\_key.key --sha sha512 > [0.1770] Assuming zero filled SBK key > [0.1793] Sha saved in br\_bct\_BR.sha > [0.1797] Warning: pub\_key.key is not found > [0.1790] Updating BCT with signature > [0.1797] tegrabct\_v2 --brbct br\_bct\_BR.bct --chip 0x23 0 --updatesig bct\_list\_signed.xml > [0.1804] Offset :4608 Len :3584 > [0.1825] Generating SHA2 Hash > [0.1833] tegrasign\_v3.py --key None --list bct\_list.xml --sha sha512 > [0.1836] Assuming zero filled SBK key > [0.1836] Assuming zero filled SBK key > [0.1876] Sha saved in br\_bct\_BR.sha > [0.1873] Updating BCT with SHA2 Hash > [0.1882] tegrabct\_v2 --brbct br\_bct\_BR.bct --chip 0x23 0 --updatesha bct\_list\_signed.xml > [0.1892] Offset :4608 Len :3584 > [0.1895] Offset :68 Len :8124 > [0.1896] > [0.1896] Generating coldboot mb1-bct > [0.1906] tegrabct\_v2 --chip 0x23 0 --mb1bct mb1\_cold\_boot\_bct.cfg --misc tegra234-mb1-bct-misc-p3701-0000\_cpp.dtb --device tegra234-mb1-bct-device-p3701-0000\_cpp.dtb > [0.1915] MB1-BCT version: 0.10 > [0.1916] ERROR: carveout /misc/carveout/aux\_info@CARVEOUT\_UNUSED1/ is not supported > [0.1920] ERROR: carveout /misc/carveout/aux\_info@CARVEOUT\_UNUSED1/ is not supported > [0.1924] ERROR: carveout /misc/carveout/aux\_info@CARVEOUT\_UNUSED1/ is not supported > [0.1927] ERROR: /misc/tsc\_controls/tsc\_locking\_config is not supported > [0.1930] ERROR: /misc/tsc\_controls/tsc\_locking\_diff\_configuration is not supported > [0.1932] ERROR: /misc/tsc\_controls/tsc\_locking\_ref\_frequency\_configuration is not supported > [0.1932] ERROR: /misc/tsc\_controls/tsc\_locking\_control is not supported > [0.1932] ERROR: /misc/tsc\_controls/tsc\_locking\_adjust\_configuration is not supported > [0.1932] ERROR: /misc/tsc\_controls/tsc\_locking\_fast\_adjust\_configuration is not supported > [0.1932] ERROR: /misc/tsc\_controls/tsc\_locking\_adjust\_delta\_control is not supported > [0.1932] ERROR: /misc/tsc\_controls/tsc\_capture\_control\_ptx is not supported > [0.1932] ERROR: /misc/tsc\_controls/tsc\_capture\_config\_ptx is not supported > [0.1932] ERROR: /misc/tsc\_controls/tsc\_stscrsr is not supported > [0.1932] ERROR: /misc/tsc\_controls/tsc\_locking\_adjust\_num\_control is not supported > [0.1932] > [0.1932] Parsing config file :tegra234-mb1-bct-device-p3701-0000\_cpp.dtb > [0.1932] Added Platform Config 9 data with size :- 100 > [0.1933] > [0.1933] Updating mb1-bct with firmware information > [0.1943] tegrabct\_v2 --chip 0x23 0 --mb1bct mb1\_cold\_boot\_bct\_MB1.bct --updatefwinfo readinfo\_t234\_min\_prod.xml.bin > [0.1976] tegrahost\_v2 --chip 0x23 0 --align mb1\_cold\_boot\_bct\_MB1\_aligned.bct > [0.2122] tegrahost\_v2 --chip 0x23 0 --magicid MBCT --appendsigheader mb1\_cold\_boot\_bct\_MB1\_aligned.bct zerosbk > [0.2145] adding BCH for mb1\_cold\_boot\_bct\_MB1\_aligned.bct > [0.2146] > [0.2166] tegrasign\_v3.py --key None --list mb1\_cold\_boot\_bct\_MB1\_aligned\_sigheader.bct\_list.xml --pubkeyhash pub\_key.key --sha sha512 > [0.2175] Assuming zero filled SBK key > [0.2204] Warning: pub\_key.key is not found > [0.2229] tegrahost\_v2 --chip 0x23 0 --updatesigheader mb1\_cold\_boot\_bct\_MB1\_aligned\_sigheader.bct.encrypt mb1\_cold\_boot\_bct\_MB1\_aligned\_sigheader.bct.hash zerosbk > [0.2276] Generating recovery mb1-bct > [0.2289] tegrabct\_v2 --chip 0x23 0 --mb1bct mb1\_bct.cfg --misc tegra234-mb1-bct-misc-p3701-0000\_cpp.dtb --device tegra234-mb1-bct-device-p3701-0000\_cpp.dtb > [0.2325] MB1-BCT version: 0.10 > [0.2328] ERROR: carveout /misc/carveout/aux\_info@CARVEOUT\_UNUSED1/ is not supported > [0.2335] ERROR: carveout /misc/carveout/aux\_info@CARVEOUT\_UNUSED1/ is not supported > [0.2365] ERROR: carveout /misc/carveout/aux\_info@CARVEOUT\_UNUSED1/ is not supported > [0.2365] ERROR: /misc/tsc\_controls/tsc\_locking\_config is not supported > [0.2365] ERROR: /misc/tsc\_controls/tsc\_locking\_diff\_configuration is not supported > [0.2365] ERROR: /misc/tsc\_controls/tsc\_locking\_ref\_frequency\_configuration is not supported > [0.2365] ERROR: /misc/tsc\_controls/tsc\_locking\_control is not supported > [0.2365] ERROR: /misc/tsc\_controls/tsc\_locking\_adjust\_configuration is not supported > [0.2366] ERROR: /misc/tsc\_controls/tsc\_locking\_fast\_adjust\_configuration is not supported > [0.2366] ERROR: /misc/tsc\_controls/tsc\_locking\_adjust\_delta\_control is not supported > [0.2366] ERROR: /misc/tsc\_controls/tsc\_capture\_control\_ptx is not supported > [0.2366] ERROR: /misc/tsc\_controls/tsc\_capture\_config\_ptx is not supported > [0.2366] ERROR: /misc/tsc\_controls/tsc\_stscrsr is not supported > [0.2366] ERROR: /misc/tsc\_controls/tsc\_locking\_adjust\_num\_control is not supported > [0.2366] > [0.2366] Parsing config file :tegra234-mb1-bct-device-p3701-0000\_cpp.dtb > [0.2366] Added Platform Config 9 data with size :- 100 > [0.2366] > [0.2367] Updating mb1-bct with firmware information > [0.2387] tegrabct\_v2 --chip 0x23 0 --mb1bct mb1\_bct\_MB1.bct --recov --updatefwinfo readinfo\_t234\_min\_prod.xml.bin > [0.2412] tegrahost\_v2 --chip 0x23 0 --align mb1\_bct\_MB1\_aligned.bct > [0.2430] tegrahost\_v2 --chip 0x23 0 --magicid MBCT --appendsigheader mb1\_bct\_MB1\_aligned.bct zerosbk > [0.2439] adding BCH for mb1\_bct\_MB1\_aligned.bct > [0.2463] tegrasign\_v3.py --key None --list mb1\_bct\_MB1\_aligned\_sigheader.bct\_list.xml --pubkeyhash pub\_key.key --sha sha512 > [0.2469] Assuming zero filled SBK key > [0.2503] Warning: pub\_key.key is not found > [0.2512] tegrahost\_v2 --chip 0x23 0 --updatesigheader mb1\_bct\_MB1\_aligned\_sigheader.bct.encrypt mb1\_bct\_MB1\_aligned\_sigheader.bct.hash zerosbk > [0.2526] Error: Skip generating mem\_bct because sdram\_config is not defined > [0.2527] Error: Skip generating mem\_bct because sdram\_config is not defined > [0.2527] Copying signatures > [0.2536] tegrahost\_v2 --chip 0x23 0 --partitionlayout readinfo\_t234\_min\_prod.xml.bin --updatesig images\_list\_signed.xml > [0.2586] mb1\_t234\_prod\_aligned\_sigheader.bin.encrypt filename is from images\_list > [0.2588] psc\_bl1\_t234\_prod\_aligned\_sigheader.bin.encrypt filename is from images\_list > [0.2588] Boot Rom communication > [0.2598] 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 > [0.2607] BR\_CID: 0x80012344705DD5018000000009010080 > [0.2892] Sending bct\_br > [0.3327] Sending mb1 > [0.3334] Sending psc\_bl1 > [0.3484] Sending bct\_mb1 > [0.3540] Boot Rom communication completed > [0.3574] tegrahost\_v2 --chip 0x23 0 --align applet\_t234\_aligned.bin > [0.3756] tegrahost\_v2 --chip 0x23 0 --magicid MB2A --appendsigheader applet\_t234\_aligned.bin zerosbk > [0.3766] adding BCH for applet\_t234\_aligned.bin > [0.3872] tegrasign\_v3.py --key None --list applet\_t234\_aligned\_sigheader.bin\_list.xml --pubkeyhash pub\_key.key --sha sha512 > [0.3875] Assuming zero filled SBK key > [0.3908] Warning: pub\_key.key is not found > [0.3956] tegrahost\_v2 --chip 0x23 0 --updatesigheader applet\_t234\_aligned\_sigheader.bin.encrypt applet\_t234\_aligned\_sigheader.bin.hash zerosbk > [0.4066] Sending mb2\_applet… > > [0.4087] tegrarcm\_v2 --chip 0x23 0 --pollbl --download applet applet\_t234\_sigheader.bin.encrypt > [0.4094] BL: version 1.2.0.0-t234-54845784-562369e5 last\_boot\_error: 3839622591 > [0.5623] Sending applet > [0.5939] ERROR: might be timeout in USB write. > Error: Return value 3 > Command tegrarcm\_v2 --chip 0x23 0 --pollbl --download applet applet\_t234\_sigheader.bin.encrypt > Reading board information failed. Is this because the production SoMs are initially blank? ---
**Author:** ![WayneWWW](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/waynewww/32/14043_2.png) [@WayneWWW](https://forums.developer.nvidia.com/u/WayneWWW)\ **Post date:** [March 30, 2024, 11:38am UTC](https://forums.developer.nvidia.com/t/cant-flash-orin-production-som/287926/2 "2024-03-30T11:38:36Z")
Most likely hardware design issue. If want to check software side, share your serial console log from UART during flash period. ---
**Author:** ![smcentee](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/smcentee/32/223479_2.png) [@smcentee](https://forums.developer.nvidia.com/u/smcentee)\ **Post date:** [March 30, 2024, 11:40am UTC](https://forums.developer.nvidia.com/t/cant-flash-orin-production-som/287926/3 "2024-03-30T11:40:14Z")
But after it’s initially flashed, I can re-flash it without issue in our custom carrier board. Above is what is displayed during flashing while in the custom carrier board. ---
**Author:** ![WayneWWW](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/waynewww/32/14043_2.png) [@WayneWWW](https://forums.developer.nvidia.com/u/WayneWWW)\ **Post date:** [March 30, 2024, 11:43am UTC](https://forums.developer.nvidia.com/t/cant-flash-orin-production-som/287926/4 "2024-03-30T11:43:04Z")
You have been this forum for a while. Is there any problem in understanding " share your serial console log from UART"? We won’t ask duplicated info if you already shared. ---
**Author:** ![smcentee](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/smcentee/32/223479_2.png) [@smcentee](https://forums.developer.nvidia.com/u/smcentee)\ **Post date:** [March 30, 2024, 11:43am UTC](https://forums.developer.nvidia.com/t/cant-flash-orin-production-som/287926/5 "2024-03-30T11:43:35Z")
Sorry, ok. I dont have access to the UART, but I’ll try some things. ---
**Author:** ![WayneWWW](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/waynewww/32/14043_2.png) [@WayneWWW](https://forums.developer.nvidia.com/u/WayneWWW)\ **Post date:** [March 30, 2024, 11:44am UTC](https://forums.developer.nvidia.com/t/cant-flash-orin-production-som/287926/6 "2024-03-30T11:44:15Z")
Also, your new comment brings another question. Are you talking about you have lots of modules there and only fresh module could hit such issue? ---
**Author:** ![smcentee](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/smcentee/32/223479_2.png) [@smcentee](https://forums.developer.nvidia.com/u/smcentee)\ **Post date:** [March 30, 2024, 11:44am UTC](https://forums.developer.nvidia.com/t/cant-flash-orin-production-som/287926/7 "2024-03-30T11:44:57Z")
Yes, only the fresh modules (unflashed) have this issue. ---
**Author:** ![WayneWWW](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/waynewww/32/14043_2.png) [@WayneWWW](https://forums.developer.nvidia.com/u/WayneWWW)\ **Post date:** [March 30, 2024, 11:46am UTC](https://forums.developer.nvidia.com/t/cant-flash-orin-production-som/287926/8 "2024-03-30T11:46:11Z")
Ok. Still need the uart log to see what is going on. ---
**Author:** ![smcentee](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/smcentee/32/223479_2.png) [@smcentee](https://forums.developer.nvidia.com/u/smcentee)\ **Post date:** [March 30, 2024, 11:53am UTC](https://forums.developer.nvidia.com/t/cant-flash-orin-production-som/287926/9 "2024-03-30T11:53:25Z")
How can I grab the Uart log from my flashing computer (Ubuntu 18.04.6 LTS)? I can minicom into the production SoM from the flashing computer, but it doesn’t display any output during flashing (or anytime). ---
**Author:** ![WayneWWW](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/waynewww/32/14043_2.png) [@WayneWWW](https://forums.developer.nvidia.com/u/WayneWWW)\ **Post date:** [March 30, 2024, 11:54am UTC](https://forums.developer.nvidia.com/t/cant-flash-orin-production-som/287926/10 "2024-03-30T11:54:50Z")
First, could you clarify if you can dump the log from NV devkit? I mean do you have the knowledge about how to dump it? Second, I cannot answer how to dump uart log for your custom board because this is your board. ---
**Author:** ![smcentee](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/smcentee/32/223479_2.png) [@smcentee](https://forums.developer.nvidia.com/u/smcentee)\ **Post date:** [March 30, 2024, 11:57am UTC](https://forums.developer.nvidia.com/t/cant-flash-orin-production-som/287926/11 "2024-03-30T11:57:16Z")
I do not have an external cable connected to the UART of the SoM, but I’ll see what I can figure out. ---
**Author:** ![WayneWWW](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/waynewww/32/14043_2.png) [@WayneWWW](https://forums.developer.nvidia.com/u/WayneWWW)\ **Post date:** [March 30, 2024, 11:57am UTC](https://forums.developer.nvidia.com/t/cant-flash-orin-production-som/287926/12 "2024-03-30T11:57:51Z")
Are you talking about NV devkit case or you are talking about your own board? ---
**Author:** ![smcentee](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/smcentee/32/223479_2.png) [@smcentee](https://forums.developer.nvidia.com/u/smcentee)\ **Post date:** [March 30, 2024, 12:00pm UTC](https://forums.developer.nvidia.com/t/cant-flash-orin-production-som/287926/13 "2024-03-30T12:00:42Z")
My own board. I do not have an issue with the Orin AGX dev kit. If I replace the Orin production SoM into the dev kit, I can flash it and then place the flashed production SoM back into our board, and it works fine. I didn’t know if I was missing something to actually flash the SoM in our board, instead of the dev kit. ---
**Author:** ![WayneWWW](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/waynewww/32/14043_2.png) [@WayneWWW](https://forums.developer.nvidia.com/u/WayneWWW)\ **Post date:** [March 30, 2024, 12:02pm UTC](https://forums.developer.nvidia.com/t/cant-flash-orin-production-som/287926/14 "2024-03-30T12:02:05Z")
Ok, then waiting for you to fix that UART console problem. If you cannot share the log, then nothing we can help here. ---
**Author:** ![system](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/system/32/68080_2.png) [@system](https://forums.developer.nvidia.com/u/system)\ **Post date:** [April 13, 2024, 12:02pm UTC](https://forums.developer.nvidia.com/t/cant-flash-orin-production-som/287926/15 "2024-04-13T12:02:53Z")
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.