The device cann't start

we will suggest our retest colleague connect the serial UART for testing the case!
Brfore found the problem, we didn’t connect the UART, and when it occurd, connected the UART, there are nothing output!

Hi, we want to just flash the cbbot.bin for the boot up failed board, and it flash failed.
We got the flash log:
1s1191_update_cboot_failed.log (4.1 KB).
It had these errors:
[1216_10:57:30][0010.105] Loading NvTbootBootloaderDTB
[1216_10:57:30][0010.121] Verifying NvTbootBootloaderDTB in SecurePKC mode
[1216_10:57:30][0010.141] NvTbootBootloaderDTB is corrupted!
[1216_10:57:30][0010.145] Error in NvTbootLoadBinary: 0x14 !
[1216_10:57:30][0010.149] Bootloader DTB Load Address: 0x83000000
[1216_10:57:30][0010.154] Bootloader DTB invalid, fallback to kernel DTB.
What does this mean?

It looks something wrong with your cboot image.
How do you flash cboot.bin only?

Could you flash all on failed board successufully?
Or just flash cpu-bootloader failed?

we used the cmd to flash cboot.bin on normal board, it flash succseefully. The cmd is:
sudo ./flash.sh -k EBT -u ./Product03/rsa_priv.pem jetson-nano-devkit-emmc-smpsq mmcblk0p1.

We had tested to flash all image files on the failed board , it can flash successufully, and boot up ok!

Where is the rsa_priv.pem come from?

Could you try the following command instead?
sudo ./flash.sh -r -k cpu-bootloader <board> mmcblk0p1

Our board had burned efuse with PKC key. we are Nano product, we had checked the cmd on another case(How to flash cboot only). And we had tested the cmd on normal board, I think it is ok.

There are some users encounter the similar issue, but they resolve with different host PC.
Unable to flash: Error: probing the target board failed. and boot: Error in NvTbootLoadBinary: 0x14 - #17 by linuxdev

Are you using the VM with Ubuntu or standalone x86-64 Ubuntu?
and what’s your Ubuntu version?

We didn’t used VM ,we know VM’s error.
We had flashed successfully on normal board.
I think maybe the emmc had bad block, because the board could bootup after reflash all Image bin.

We want to check the emmc bad block by flash cboot.bin only.
It flash cboot.bin failed, and had the error logs.

Do you still have these errors when you flash cboot.bin only?

yes!

Hi yong.lu,

Could you help using R32.7.3 released recently to check if this issue still exists?
Jetson Linux R32.7.3 | NVIDIA Developer

Do you doubt where?

Hi @yong.lu

Sorry to jump in. What is the exact issue now?

It looks like you can flash the board and boot up ok on 12/16. Is this still an issue?

Hi, we found 5 piece boards which cann’t boot up, and there are nothing from uart .
So we did experiments on a few of them for reflash, they can boot up again.
So we doubt the emmc maybe had bad block or maybe one boot partition was destroyed.
So we test to flash cboot.bin only on the last abnormal board , and found it cann’t flash.

Hi,

Not sure why you just want to flash cboot. Why not just full flash all of them and tell us the result?

???
we need konw the reson, please see my previous reply.
The modules in question had run aging video test, when do other tests , they need reboot, we found them cann’t boot up again. We are worried that the customer cannot turn on the machine in use!

請問一下你能否說明你現在的問題到底是什麼?

你剛告訴我說你的cboot flash 有問題但是你的full flash好像沒問題.
請問這是你想表達的嗎? 還是你想說其他的事情?

我想說的是你正在拿一個奇怪的步驟(單燒cboot) 來說明你覺得emmc有問題. 這聽起來是個不怎麼有說服力的測試. Full flash 也會燒cboot. 如果full flash沒問題的話那我會覺得你不用在意cboot flash error.

沟通的有点问题:我们的问题是:在生产测试中,发现5台设备无法开机,这些设备都是在测试使用中出现无法开机问题! 出现问题时接上串口,没有任何信息输出!即使重新上电,也无法开机,串口没有任何东西输出。 这个问题提给贵司帮忙分析!
在这个过程中,我们自我排查原因:1,5台设备中对其中4台重新烧录整个Image 包后,可以正常启动,猜测是不是emmc 有坏块或着哪个启动分区被破坏; 2.尝试先单独烧录cboot.bin看是否可以开机,尝试失败,这个尝试想请贵司看看有没有什么突破口!

我觉得我上面都有说清楚吧!至今未收到有效回复。

厄 這邊有幾點事情要澄清一下

  1. 關於你的第一個問題, 說實話我們沒有辦法分析. 更何況如果你是拿你們自己的開發版, 我們更無法澄清這到底是哪方的問題 如果懷疑是module問題我們會希望用devkit做測試.

我们的问题是:在生产测试中,发现5台设备无法开机,这些设备都是在测试使用中出现无法开机问题! 出现问题时接上串口,没有任何信息输出!即使重新上电,也无法开机,串口没有任何东西输出。 这个问题提给贵司帮忙分析!

而且你又馬上告訴我們說, 你整機重燒之後就可以正常啟動. 那我們更不覺得這部份有問題. 正常來說就算emmc有壞塊的話uart還是會有log.
老實說, 在我們的立場, 我們根本不能確定你一開始那5台module原本有沒有燒東西…
如果這個問題在這4片module上能反覆發生的話, 那我們才會懷疑是module問題…

2.尝试先单独烧录cboot.bin看是否可以开机,尝试失败

所以你這一條其實是想問兩個問題是嗎? 還是這個單獨燒錄cboot.bin跟你所謂的"不能開機" 你覺得有關連?