steps to reproduce:
Switch NX in recovery mode
Connect to host PC USB cable
Check if NX is in system by lsusb
Flash SPE firmware:
sudo ./flash.sh -k spe-fw jetson-xavier mmcblk0p1
Steps used to build firmware
build firmware
1. Install arm toolchain
sudo apt-get install gcc-arm-none-eabi
2. unpack l4t_rt_aux_cpu_src.tbz2 (https://developer.nvidia.com/jetson-sensor-processing-engine-spe-software-sources-3242)
3. set enviroment variables (dont forget change path to your!) and change directory to "cd rt-aux-cpu-demo"
export TOP=/home/imp/workspace/l4t-rt
export CROSS_COMPILE=/usr/bin/arm-none-eabi-
export OUTDIR=${TOP}/out
export FREERTOS_DIR=${TOP}/FreeRTOSV8.1.2/FreeRTOS/Source
export FREERTOS_COMMON_DIR=${TOP}/freertos-common
4. make firmware
make TARGET=t19x
5. In out folder you can see spe.bin
6. Copy it to:
Linux_for_Tegra/bootloader/spe_t194.bin
7. Flash it (after switch NX to REC mode):
sudo ./flash.sh -k spe-fw jetson-xavier mmcblk0p1
any insights?
There are the same error when tried to flash my firmware or original from Linux_for_Tegra/bootloader:
*** Updating [spe-fw] with spe_t194.bin ***
[ 0.0249 ] tegrasign_v2 --key None --getmode mode.txt
[ 7.5122 ] Parsing config file :tegra19x-mb1-pinmux-p2888-0000-a04-p2822-0000-b01.cfg
[ 7.5172 ] Parsing config file :tegra194-mb1-bct-scr-cbb-mini.cfg
[ 7.5441 ] Parsing config file :tegra19x-mb1-padvoltage-p2888-0000-a00-p2822-0000-a00.cfg
[ 7.5459 ] Parsing config file :tegra194-mb1-bct-pmic-p2888-0001-a01-p2822-0000.cfg
[ 7.5792 ] Parsing config file :tegra19x-mb1-pinmux-p2888-0000-a04-p2822-0000-b01.cfg
[ 7.5876 ] Parsing config file :tegra194-mb1-bct-scr-cbb-mini.cfg
[ 7.6106 ] Parsing config file :tegra19x-mb1-padvoltage-p2888-0000-a00-p2822-0000-a00.cfg
[ 7.7339 ] tegrahost_v2 --chip 0x19 0 --blocksize 512 --magicid MEMB --addsigheader_multi /home/imp/workspace/Linux_for_Tegra/bootloader/15300/tmpzJ0vnj1_1.bct /home/imp/workspace/Linux_for_Tegra/bootloader/15300/tmpzJ0vnj1_2.bct /home/imp/workspace/Linux_for_Tegra/bootloader/15300/tmpzJ0vnj1_3.bct /home/imp/workspace/Linux_for_Tegra/bootloader/15300/tmpzJ0vnj1_4.bct
Host PC is laptop, USB 2.0 and different ports\cable are used
jachen
July 24, 2020, 3:19am
5
Hello, Andrey:sudo ./flash.sh -k spe-fw jetson-xavier mmcblk0p1
br
hi @jachen
jachen
July 24, 2020, 3:45am
7
Hello, imp.savrik:
br
jachen
July 24, 2020, 3:49am
8
Hello, Andrey:Welcome â Jetson Linux<br/>Developer Guide 34.1 documentation
br
AFAIK, doc/faq.md only seem to address AGX firmware flashing, also TX2
jetson-xavier-nx-devkit?
jachen
July 24, 2020, 3:57am
11
Hello, Andrey:
As to faq.md, it describes the possible reason for flash failure with customized SPE firmware. Please check it.
br
Thank you for the update!
from developers: âflashing to jetson-xavier-nx-devkit seems workedâ
[ 24.7661 ] Writing partition
[ 24.7682 ] tegradevflash_v2 --write spe-fw 1_spe_t194_sigheader.bin.encrypt
[ 24.7731 ] Bootloader version 01.00.0000
[ 24.7782 ] Writing partition spe-fw with 1_spe_t194_sigheader.bin.encrypt
[ 24.7793 ] [................................................] 100%
[ 25.4420 ]
[ 25.4422 ] Coldbooting the device
[ 25.4444 ] tegrarcm_v2 --ismb2
[ 25.4514 ]
[ 25.4551 ] tegradevflash_v2 --reboot coldboot
[ 25.4575 ] Bootloader version 01.00.0000
[ 25.4646 ]
*** The [spe-fw] has been updated successfully. ***
They flashed the AGX stock[default] firmware, as it seems to me;
Is the firmware originally somewhere in â/lib/firmware/â? If you know the name of the file, then load might be mentioned by file name in dmesg.
1 Like
jachen
July 27, 2020, 3:09am
15
SPE firmware is located in partition spe-fw, not in root-FS. Also, itâs loaded by MB1, not kernel.
br