• State Not Answered
  • Replies 20 replies
  • Subscribers 69 subscribers
  • Views 722 views
  • Users 0 members are here
Attachments (2) Download All
Nordic Case Info
  • Case ID: 332280
Options

Unable to program board

amanb

I'm seeing an issue when trying to program the nRF54H20 board. I have python 3.10.9 installed. Does nrfutil specifically need python 3.9? Any support with this would be appreciated

  • 0 in reply to Jennifer Gibbs

    Hi Jennifer,

    I am able to build it using this configuration as well. However, I am seeing an issue when trying to program the board - it is failing. Even though VS claims a successful program, upon looking at the terminal, I see the error that I attached to this ticket regarding the nrfutil module use of python39.dll.

    Do you see this issue as well or are you able to program the board with the built firmware?

    Thanks,

    Aman

  • 0 in reply to amanb

    Hello Aman,

    I just checked and I do not get that error, it flashes for me. I have python 3.11.9 on my machine. I went ahead and also opened an nRF Connect terminal in VS Code and issued the flash command from within my build directory without issue (as well as queried my python version), see attached. 

    Fullscreen ncs_terminal.txt Download 
    PS C:\Nordic\eddystone> py --version
Python 3.11.9
PS C:\Nordic\eddystone> cd ..
PS C:\Nordic> cd ..
PS C:\> cd ncs/v2.7.0
PS C:\ncs\v2.7.0> cd nrf/samples/peripheral_hr_coded/build
Set-Location: Cannot find path 'C:\ncs\v2.7.0\nrf\samples\peripheral_hr_coded\build' because it does not exist.
PS C:\ncs\v2.7.0> cd nrf/samples
PS C:\ncs\v2.7.0\nrf\samples> cd bluetooth
PS C:\ncs\v2.7.0\nrf\samples\bluetooth> cd peripheral_hr_coded
PS C:\ncs\v2.7.0\nrf\samples\bluetooth\peripheral_hr_coded> cd build    
PS C:\ncs\v2.7.0\nrf\samples\bluetooth\peripheral_hr_coded\build> west flash
-- west flash: rebuilding
[0/11] Performing build step for 'peripheral_hr_coded'
ninja: no work to do.
[2/11] Performing build step for 'ipc_radio'
ninja: no work to do.
[11/11] Generating ../zephyr/dfu_suit.zip
-- west flash: using runner nrfutil
Using board 001051192672
-- runners.nrfutil: Flashing file: C:\ncs\v2.7.0\nrf\samples\bluetooth\peripheral_hr_coded\build\peripheral_hr_coded\zephyr\uicr_merged.hex
-- runners.nrfutil: Programming image
-- runners.nrfutil: Verifying image
-- runners.nrfutil: Programming image
-- runners.nrfutil: Verifying image
-- runners.nrfutil: Erase
-- runners.nrfutil: Programming image
-- runners.nrfutil: Verifying image
-- runners.nrfutil: Board with serial number 1051192672 flashed successfully.
-- west flash: using runner nrfutil
-- runners.nrfutil: reset after flashing requested
Using board 001051192672
-- runners.nrfutil: Flashing file: C:\ncs\v2.7.0\nrf\samples\bluetooth\peripheral_hr_coded\build\ipc_radio\zephyr\uicr_merged.hex
-- runners.nrfutil: Erase
-- runners.nrfutil: Programming image
-- runners.nrfutil: Verifying image
-- runners.nrfutil: Reset
-- runners.nrfutil: Board with serial number 1051192672 flashed successfully.
PS C:\ncs\v2.7.0\nrf\samples\bluetooth\peripheral_hr_coded\build>

    Are you not able to capture all of your terminal output and copy it to a text file?

    Thank you,
    Jennifer Gibbs

  • 0

    Hello Aman,

    Sorry for the delayed response. We were in Norway last week for training and I now know exactly how to solve the issue you are having. Please let me know if you are still stuck after trying the following:

    In VS Code, open an nRF Connect terminal and issue the following command:

    pip install nrf-regtool==5.5.1

    Thank you,
    Jennifer Gibbs

  • 0

    Hello Aman,

    Were you able to get everything installed using the pip command I provided?

    Thank you,

    Jennifer Gibbs

  • 0 in reply to Jennifer Gibbs

    Hi Jennifer,

    Sorry, I haven't been working on this for a few months now as I've had a few other high priority tasks to take care of. Coming back to this now

    I've updated to SDK 2.8.0 and I am seeing a very similar issue to this ticket:

     (Missing Forum Reply)  

    I responded on there to get some feedback but it seems that the ticket will be taken private, so I am posting my details here as well. Thanks so much for your help!

    Regards,

    Aman

    -- west flash: using runner nrfutil
    -- runners.nrfutil: Flashing file: C:\Users\aman\peripheral_hids_mouse\peripheral_hr_coded\build_8\peripheral_hr_coded\zephyr\uicr_merged.hex
    -- runners.nrfutil: Reset
    Error: One or more batch tasks failed:
    - [Probe] Device error: Error in ADAC operation: Timeout in ADAC communication, code: Generic

    board details:
    NRF54H20-DK
    PCA10175
    rev 0.8.0

    I've updated my j-link, nrfutil device, nrf-regtools and nrfutil-trace libraries to match the dependencies. I am able to update the BICR and trigger the SUIT DFU, but when I try to recover the board, I see the same ADAC issue. 

    C:\Users\aman\Downloads>nrfutil device list
    1051173461
    product J-Link
    board version PCA10175
    ports COM62, vcom: 0
    COM61, vcom: 1
    traits boardController, devkit, jlink, seggerUsb, serialPorts, usb

    Found 1 supported device(s)


    C:\Users\aman\Downloads>nrfutil device recover --core Application --serial-number 1051173461
    x Failed to recover 1051173461, [Probe] Device error: Error in ADAC operation: Timeout in ADAC communication
    Error: One or more recover tasks failed:
    * 1051173461: [Probe] Device error: Error in ADAC operation: Timeout in ADAC communication, code: Generic

    C:\Users\aman\Downloads>nrfutil device recover --core Network --serial-number 1051173461
    x Failed to recover 1051173461, [Probe] Device error: Error in ADAC operation: Timeout in ADAC communication
    Error: One or more recover tasks failed:
    * 1051173461: [Probe] Device error: Error in ADAC operation: Timeout in ADAC communication, code: Generic

Related