Cortex-R5 SPE partition flash

[andrea.pascolini]

Hello,

I would need to flash SPE partition (Xavier NX), so according to what explained in SPE deloper user guide I tried this:

sudo ./flash.sh -k spe-fw <T186 or T194 SoC based Jetson platforms> mmcblk0p1`

The procedure properly completes, but then the system goes to a continuous-reboot state. This is the error message we get from system TTY at every boot:

[0000.150] I> Boot-device: QSPI
[0000.153] I> Boot-device: QSPI
[0000.156] I> Qspi flash params source = mb1bct
[0000.160] I> Qspi using bpmp-dma
[0000.163] I> Qspi clock source : pllc_out0
[0000.167] I> Qspi reinitialized
[0000.170] I> Qspi flash params source = mb1bct
[0000.175] I> ECC region[0]: Start:0x0, End:0x0
[0000.179] I> ECC region[1]: Start:0x0, End:0x0
[0000.183] I> ECC region[2]: Start:0x0, End:0x0
[0000.188] I> ECC region[3]: Start:0x0, End:0x0
[0000.192] I> ECC region[4]: Start:0x0, End:0x0
[0000.196] I> Non-ECC region[0]: Start:0x80000000, End:0x100000000
[0000.202] I> Non-ECC region[1]: Start:0x0, End:0x0
[0000.206] I> Non-ECC region[2]: Start:0x0, End:0x0
[0000.210] I> Non-ECC region[3]: Start:0x0, End:0x0
[0000.215] I> Non-ECC region[4]: Start:0x0, End:0x0
[0000.220] E> FAILED: Thermal config
[0000.228] E> FAILED: MEMIO rail config
[0000.238] I> Boot-device: QSPI
[0000.241] I> Qspi flash params source = mb1bct
[0000.250] I> Qspi flash params source = mb1bct
[0000.261] I> Qspi flash params source = mb1bct
[0000.328] I> Qspi flash params source = mb1bct
[0000.337] I> Qspi flash params source = mb1bct
[0000.365] I> Qspi flash params source = mb1bct
[0000.370] E> LOADER: Failed to verify Stage2Signature SHA2.
[0000.375] E> LOADER: Failed to verify oem header.
[0000.380] C> LOADER: Could not read spe-fw.
[0000.384] E> failed to read spe fw from storage
[0000.388] E> AON SPE init failed
[0000.391] E> Task 78 failed (err: 0x251d0718)
[0000.395] E> Top caller module: AON, error module: LOADER, reason: 0x18, aux_info: 0x07
[0000.402] I> MB1(1.5.1.6-t194-41334769-1740dd39) BIT boot status dump :
0000000000011111111110111111111111111111111100111111101110011111111011011111111000000000000000000000000000000000000000000000000011111011000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
��
[0000.025] W> RATCHET: MB1 binary ratchet value 4 is too large than ratchet level 2 from HW fuses.
[0000.033] I> MB1 (prd-version: 1.5.1.6-t194-41334769-1740dd39)
[0000.039] I> Boot-mode: Coldboot
[0000.042] I> Chip revision : A02P
[0000.045] I> Bootrom patch version : 15 (correctly patched)
[0000.050] I> ATE fuse revision : 0x200

If I flash the full system (no “-k” option) then everything works fine

Thanks in advance

Andrea

[jachen]

Hello, Andrea:
Can you share the full flash command log with
sudo ./flash.sh -k spe-fw mmcblk0p1
?
The error log shows:
[0000.370] E> LOADER: Failed to verify Stage2Signature SHA2.
[0000.375] E> LOADER: Failed to verify oem header.
[0000.380] C> LOADER: Could not read spe-fw.

It means something wrong with spe-fw.
But if you follow the instructions in Jetson Sensor Processing Engine (SPE) Developer Guide: Compiling and Flashing (nvidia.com)
that should not happen.
BTW: Please make sure that the BSP version matches SPE firmware version. Though that may not be the key, we do suggest all components are with same version.

br
Chenjian

[andrea.pascolini]

Hello Jachen,

thanks for your answer. I confirm that I followed all the steps in developer guide. I have just noticed that I copied the same binary both to spe_t194.bin and spe.bin, but I guess this could hardly be the reason behind my problem. As said, no problem if I flash the same firmware together with the rest of file system, by omitting “-k” option.

Here “flash -k” command log:
flash_host.txt (46.0 KB)

And here the relative output from Xavier’s system TTY, including multiple reboots after flashing:
flash_tty.txt (34.1 KB)

Andrea

[jachen]

Hello, Andrea:
That’s a little weird.
Have you ever changed anything in BSP?
I’ve tried flash -k spe-fw before in Xavier NX and it can work well.
(Sorry that I cannot access Xavier NX now so I cannot cross-check the flash log)

In addition, the BSP package version same as configurations, like eMMC xml?

br
Chenjian

[andrea.pascolini]

Hello Jachen, yes, we did change something in the BSP. We have finally managed to program SPE though nv_bootloader_payload_updater tool. Flash -k option flow still under investigation.

Thanks for the support

Andrea