But what is that board here? Looks like you still have some customization.
Could you just download fresh BSP and let sdkmanager to flash it?
Sorry - I must have copied the wrong thing. There are a lot of balls in the air. I tried both flashing the xavier on the devkit with our custom config and with the base config for the devkit. Both failed.
I attempted to do a start from scratch build today. I copied my existing 4.5.1 jetpack to another location. I ran the sdkmanager and installed a new xavier 4.5.1 Jetpack. I then ran:
sudo ./flash.sh jetson-xavier mmcblk0p1
This also fails. See this log:
Uart Log:
The error generated when running on the devkit is from the same command (tegrarcm_v2) but the error code is different - this generates Return value 8 instead of Return value 2
The UART spills errors:
[0130.389] E> FAILED: Thermal config
[0130.396] E> FAILED: MEMIO rail config
[0130.411] E> Task 50 failed (err: 0x7979061c)
[0130.415] E> Top caller module: ALIASCHECKER, error module: ALIASCHECKER, reason: 0x1c, aux_info: 0x06
[0130.424] I> MB1(1.5.1.6-t194-41334769-1740dd39) BIT boot status dump :
000000000001111111111000011111111111111001100011111000000000000000000000000000000000000000000000000000000000000000000000000000001100100000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
So that’s interesting. I’m going to try grabbing the UART log from our carrier board (successful and unsuccessful) and see how it compares.