• State Not Answered
  • Replies 19 replies
  • Subscribers 69 subscribers
  • Views 562 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 335787
Options

Blinky example doesn't work on NRF54H20-DK

Mykhaylo

Hello!

I have NRF54H20-DK and I'm trying to run the Blinky example.

I am able to build and program the DK, but nothing happens on LEDs.

Could you please help what else I should check?

NRF54H20-DK: 0.8.2

nRF Connect SDK: v2.7.99-cs2

Thanks.

Parents
  • 0

    Hi

    So the boot status here points to the secure domain firmware reporting an error, and it seems to point to an error while booting the local domains. Does it return the same code after you have recoverd the local domains with the second set of commands I gave you? Try running nrfutil device x-boot-status-get --traits devkit again now and see what it returns.

    Best regards,

    Simon

Reply
  • 0

    Hi

    So the boot status here points to the secure domain firmware reporting an error, and it seems to point to an error while booting the local domains. Does it return the same code after you have recoverd the local domains with the second set of commands I gave you? Try running nrfutil device x-boot-status-get --traits devkit again now and see what it returns.

    Best regards,

    Simon

Children
  • 0 in reply to Simonr

    Hi, Simon

    I'm in contact with topic creator and I'm currently in posession of this DK in question, so I will continue working on it.

    Here is what console outputs before and after command sequence. First x-boot-status-get was executed right after board power-on.

    (v2.7.99-cs2) F:\nrf-connect-sdk\zephyr> nrfutil device x-boot-status-get --traits devkit
boot_status: 0x0bafff76

(v2.7.99-cs2) F:\nrf-connect-sdk\zephyr> nrfutil device x-adac-discovery --traits devkit
001051163442
adac_auth_version     1.0
vendor_id             Nordic VLSI ASA
soc_class             0x00005420
soc_id                0ebc5e28-1454-11ef-ce03-bd6d7690493f
hw_permissions_fixed  [00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00]
hw_permissions_mask   [01, 00, 00, 00, 87, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00]
psa_lifecycle         LIFECYCLE_ROT (0x2000)
sda_id                0x01
secrom_revision       0xdb8bd920
sysrom_revision       0x3df7dba0
token_formats         [TokenAdac]
cert_formats          [CertAdac]
cryptosystems         [Ed25519Sha512]
Additional TLVs:
  TargetIdentity: [ff, ff, ff, ff, 01, 26, 01, 00]


(v2.7.99-cs2) F:\nrf-connect-sdk\zephyr> nrfutil device x-boot-mode-set --boot-mode safe --traits jlink
v Set boot mode 1051163442

(v2.7.99-cs2) F:\nrf-connect-sdk\zephyr> nrfutil device erase --all --log-level trace --core Application --traits jlink
v Erased 1051163442

(v2.7.99-cs2) F:\nrf-connect-sdk\zephyr> nrfutil device erase --all --log-level trace --core Network --traits jlink
v Erased 1051163442

(v2.7.99-cs2) F:\nrf-connect-sdk\zephyr> nrfutil device x-boot-mode-set --boot-mode normal --traits jlink
v Set boot mode 1051163442

(v2.7.99-cs2) F:\nrf-connect-sdk\zephyr> nrfutil device recover
v Recovered 1051163442

(v2.7.99-cs2) F:\nrf-connect-sdk\zephyr> nrfutil device x-boot-status-get --traits devkit
boot_status: 0x0bafffff

    So it seems like boot_status has changed after these operations

Related