CPU Bootloader is not running on device

varun_pandithurai · August 21, 2021, 9:21am

[  57.0777 ] tegrarcm_v2 --boot recovery
[  57.0811 ] Applet version 01.00.0000
[  73.3581 ] 
[  74.3623 ] tegrarcm_v2 --isapplet
[  89.6456 ] 
[  89.6481 ] tegrarcm_v2 --ismb2
[  89.6500 ] MB2 Applet version 01.00.0000
[ 114.0875 ] 
[ 114.0912 ] tegrarcm_v2 --ismb2
[ 114.0943 ] MB2 Applet version 01.00.0000
[ 130.3773 ] 
[ 130.3793 ] Retrieving board information
[ 130.3809 ] tegrarcm_v2 --oem platformdetails chip chip_info.bin
[ 130.3825 ] MB2 Applet version 01.00.0000
[ 146.6737 ] Saved platform info in chip_info.bin
[ 146.6780 ] Chip minor revision: 2
[ 146.6781 ] Bootrom revision: 0xf
[ 146.6781 ] Ram code: 0x2
[ 146.6781 ] Chip sku: 0xd0
[ 146.6782 ] Chip Sample: non es
[ 146.6782 ] 
[ 146.6791 ] Retrieving EEPROM data
[ 146.6793 ] tegrarcm_v2 --oem platformdetails eeprom cvm /home/htic/Jetson_Xavier_kernel/Thine_0/Xavier/Linux_for_Tegra/bootloader/cvm.bin
[ 146.6822 ] MB2 Applet version 01.00.0000
[ 154.8180 ] 0000000036360018: 
[ 154.8714 ] 
[ 154.8753 ] tegradevflash_v2 --oem platformdetails eeprom cvm /home/htic/Jetson_Xavier_kernel/Thine_0/Xavier/Linux_for_Tegra/bootloader/cvm.bin
[ 154.8791 ] CPU Bootloader is not running on device.
[ 171.1110 ] 
Error: Return value 4
Command tegradevflash_v2 --oem platformdetails eeprom cvm /home/user_name/Jetson_Xavier_kernel/Thine_0/Xavier/Linux_for_Tegra/bootloader/cvm.bin
Reading board information failed.

WayneWWW · August 23, 2021, 2:55am

You should share more detail about your board, your command and what software release you are using.

Not just gave a log and said nothing.

varun_pandithurai · August 23, 2021, 3:53am

Hi @WayneWWW ,
I tried using the build tool in this git GitHub - jtagxhub/jetpack-agx-build: build assistant scripts for Nvidia Jetson platforms: AGX Xavier, TX2, TX1 and Nano
I also tried using sdk manager but the same error comes
I am using Jetpack 4.5

WayneWWW · August 23, 2021, 3:55am

So what is your board?

varun_pandithurai · August 23, 2021, 3:56am

Hi @WayneWWW ,
I am using Jetson Xavier AGX

WayneWWW · August 23, 2021, 3:57am

32gb? 16gb? 8gb? Devkit? Custom board?

varun_pandithurai · August 23, 2021, 3:58am

Hi @WayneWWW
32gb Devkit

WayneWWW · August 23, 2021, 4:00am

Please move to rel-32.6.1 and try again.

varun_pandithurai · August 24, 2021, 12:33pm

Hi @WayneWWW
I got the same error again

17:31:08 INFO: Flash Jetson AGX Xavier - flash: — Parsing board ID (ERROR: calculated CRC8 0x2a != stored CRC8 0x51) succeeded.

17:31:08 ERROR: Flash Jetson AGX Xavier - flash: command terminated with error
17:31:08 SUMMARY: DateTime Target Setup - target: Depends on failed component

WayneWWW · August 24, 2021, 12:35pm

What is the environment of your host machine?

And why did you say “I hit same error again”? It seems what you post now didn’t show up in previous comment.

varun_pandithurai · August 24, 2021, 1:07pm

Hi @WayneWWW
I am Using Ubuntu 18.4

The previous Error I posted was from the Build tool from Git.

But I got the same error while using Jetpack4.5 and jetpack4.6

WayneWWW · August 24, 2021, 3:16pm

Did you ever successfully flash this xavier before? Or this is the first time?
Do you have other xavier devices on your side?

varun_pandithurai · August 25, 2021, 3:55am

Hi @WayneWWW
Yes I flashed this Xavier AGX few times before it was done without any errors.
Yeah I do have another Xavier AGX there is no problem in flashing it.

WayneWWW · August 25, 2021, 5:36am

Did you ever use i2c tool to modify the on-module eeprom on this problematic xavier?

Can you share the full error log as an attachment?

varun_pandithurai · August 25, 2021, 6:38am

Hi @WayneWWW
I used I2C tools to access camera alone did not try to modify the on-module eeprom on the problematic xavier
The I2C bus I used was i2c1 (c240000)
I have attached the log here

error.txt (5.5 KB)

Is there a way to set values in on-module eeprom to default ?

WayneWWW · August 25, 2021, 6:57am

Is your board still able to boot up? I mean since the flash work is not done yet, your board may still able to boot into OS.

If so, need you to use i2c tool to modify the eeprom content.

varun_pandithurai · August 25, 2021, 6:58am

Hi @WayneWWW
The Board is able to boot to the previously installed version

WayneWWW · August 25, 2021, 7:01am

Please use below command and dump the result first.

sudo i2cdump -y 0 0x50

varun_pandithurai · August 25, 2021, 7:06am

Hi @WayneWWW
This is the result of “sudo i2cdump -y 0 0x50”

No size specified (using byte-data access)
0 1 2 3 4 5 6 7 8 9 a b c d e f 0123456789abcdef
00: 00 32 35 36 48 0b 04 00 04 4b 00 00 00 00 00 00 .256H??.?K…
10: 00 00 00 00 36 39 39 2d 38 32 38 38 38 2d 30 30 …699-82888-00
20: 30 34 2d 34 30 30 20 4b 2e 30 00 00 00 00 00 00 04-400 K.0…
30: 00 00 ff ff ff ff ff ff ff ff ff ff ff ff ff ff …
40: ff ff ff ff 7e 89 e5 4b 04 00 31 34 32 30 32 32 …~??K?.142022
50: 30 30 32 34 35 34 30 00 00 00 00 00 00 00 00 00 0024540…
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 …
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 …
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 …
90: 00 00 00 00 00 00 4e 56 43 42 1c 00 4d 31 00 00 …NVCB?.M1…
a0: ff ff ff ff ff ff ff ff ff ff ff ff 7e 89 e5 4b …~??K
b0: 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ?..
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 …
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 …
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 …
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 51 …Q

i2c

WayneWWW · August 25, 2021, 7:13am

please modified the last field 0x51 to 0x2a to match your error log.

ERROR: calculated CRC8 0x2a != stored CRC8 0x51