NRF54H20 SDK v2.9.0-nRF54H20-rc1 boot behavior

[vsle0n]

I am experiencing weird radio core boot behavior after switching to SDK v2.9.0-nRF54H20-rc1.

First I followed the bring up guide for SDK v2.8.0, flashed latest BICR for that SDK version and nrf54h20_soc_binaries_v0.7.0_engc.zip.

But after installation of SKD v2.9.0-nRF54H20-rc1 it takes about 10 seconds from reset to reach void main() in debug on radio core.

Also I get the following log output before reaching void main():

*** Booting nRF Connect SDK v2.9.0-nRF54H20-rc1-4df6ce63408b ***
*** Using Zephyr OS v3.7.99-f5efb381b8af ***
E: nRFs GDPWR request not applied

I then spotted that there are nrf54h20_soc_binaries_v0.8.0 binaries. I tried to flash it, but it looks like I need to switch the MCU to lifecycle "empty"

I was not able to do this using nrftool.

Could you please suggest a solution?

[Elfving]

Hi,

I think this could be related to the required changes mentioned in the migration guide.

Have you had a look at the steps mentioned here under "nRF54H20 SoC binaries"? 

Have you updated nrfutil to the version mentioned under the headline "nrfutil" here? 

Regards,

Elfving

[vsle0n]

Hi,

Thanks for your help. I followed the steps and unfortunately it got even worse now I an not able to debug at all.

Also the guide says to install trace 3.10.0 but nrftool fails to locate it, the most recent version is 3.1.0

I am getting the following debug output:

ERROR: ResetTarget failed (-1).
Failed to halt CPU.
Resetting target
WARNING: Failed to read memory @ address 0x0E054B08
Setting breakpoint @ address 0x0E054B08, Kind = 2, Type = THUMB, BPHandle = 0x0001
Starting target CPU...
ERROR: CPU is not halted
ERROR: Cannot read register 15 (R15) while CPU is running
Reading common registers: ERROR: Cannot read register 0 (R0) while CPU is running
Read register 'r0' (4 bytes) from hardware: 0xEFBEADDE
ERROR: Cannot read register 1 (R1) while CPU is running
Read register 'r1' (4 bytes) from hardware: 0xEFBEADDE
ERROR: Cannot read register 2 (R2) while CPU is running
Read register 'r2' (4 bytes) from hardware: 0xEFBEADDE
ERROR: Cannot read register 3 (R3) while CPU is running
Read register 'r3' (4 bytes) from hardware: 0xEFBEADDE
ERROR: Cannot read register 4 (R4) while CPU is running
Read register 'r4' (4 bytes) from hardware: 0xEFBEADDE
ERROR: Cannot read register 5 (R5) while CPU is running
Read register 'r5' (4 bytes) from hardware: 0xEFBEADDE
ERROR: Cannot read register 6 (R6) while CPU is running
Read register 'r6' (4 bytes) from hardware: 0xEFBEADDE
ERROR: Cannot read register 7 (R7) while CPU is running
Read register 'r7' (4 bytes) from hardware: 0xEFBEADDE
ERROR: Cannot read register 8 (R8) while CPU is running
Read register 'r8' (4 bytes) from hardware: 0xEFBEADDE
ERROR: Cannot read register 9 (R9) while CPU is running
Read register 'r9' (4 bytes) from hardware: 0xEFBEADDE
ERROR: Cannot read register 10 (R10) while CPU is running
Read register 'r10' (4 bytes) from hardware: 0xEFBEADDE
ERROR: Cannot read register 11 (R11) while CPU is running
Read register 'r11' (4 bytes) from hardware: 0xEFBEADDE
ERROR: Cannot read register 12 (R12) while CPU is running
Read register 'r12' (4 bytes) from hardware: 0xEFBEADDE
ERROR: Cannot read register 13 (R13) while CPU is running
Read register 'sp' (4 bytes) from hardware: 0xEFBEADDE
ERROR: Cannot read register 14 (R14) while CPU is running
Read register 'lr' (4 bytes) from hardware: 0xEFBEADDE
ERROR: Cannot read register 15 (R15) while CPU is running
Read register 'pc' (4 bytes) from hardware: 0xEFBEADDE
ERROR: Cannot read register 16 (XPSR) while CPU is running
Read register 'xpsr' (4 bytes) from hardware: 0xEFBEADDE
Removing breakpoint @ address 0x0E054B08, Size = 2
WARNING: Failed to read memory @ address 0xDEADBEEE
WARNING: Failed to read memory @ address 0xDEADBEEE

[Elfving]

Did you mean to say that none of this was a problem with NCS 2.8?

Regards,

Elfving

[vsle0n]

Yes, I have the second board which is not updated to SOC binaries 0.8.0 and I am able to debug the same exact project on it just fine on SDK 2.8.0 and with a startup delay/problem, described in the ticket, on SDK v2.9.0-nRF54H20-rc1.