The nrf54h20 burning results using nrfutil alone are inconsistent with the burning results using vscode

Hi,

    Our product has reached the mass production stage and needs to be burned using the nrfutil command, but the burning result is inconsistent with the result of vscode

    We need to test the pin and RF so we modify some code in radio_test

ncs2.8.0

IC: REVB

According to the following link, the configuration is successful

docs.nordicsemi.com/.../ug_nrf54h20_gs.html

radio_test

I will attach my project.

nrf54h20_factory_test.zip

When I use vscode to burn, it works fine. I can test that a pin is high level when powered on and becomes low level after 3s.

But when I use nrf54h20_factory_test\build\nrf54h20_factory_test\zephyr\generated_nrfutil_batch.json  burn firmware it doesn't work.

nrfutil device erase --traits jlink --x-family nrf54h  --core Application --all
nrfutil device erase --traits jlink --x-family nrf54h  --core Network --all
nrfutil device reset --reset-kind RESET_PIN  

nrfutil device program --traits jlink --x-family nrf54h  --core Application --firmware suit_mpi_application_merged.hex
nrfutil device fw-verify --firmware suit_mpi_application_merged.hex
nrfutil device program --traits jlink --x-family nrf54h  --core Network --firmware suit_mpi_radio_merged.hex
nrfutil device fw-verify --firmware suit_mpi_radio_merged.hex
nrfutil device program --traits jlink --x-family nrf54h  --core Application --firmware suit_installed_envelopes_application_merged.hex
nrfutil device fw-verify --firmware suit_installed_envelopes_application_merged.hex
nrfutil device program --traits jlink --x-family nrf54h  --core Network --firmware uicr_merged.hex
nrfutil device fw-verify --firmware uicr_merged.hex

nrfutil device reset --reset-kind RESET_PIN  

Related