• State Not Answered
  • Replies 16 replies
  • Subscribers 66 subscribers
  • Views 1037 views
  • Users 0 members are here
Attachments (1) Download All
Nordic Case Info
  • Case ID: 312659
Options

Did Worker Process die? on Flash

Schmid

Hi, while working with the nRF9160DK i get this Error a lot of times, I can't say "Yes" or something else and have to wait until the progress bar fills completely. Even if I disconnect the DK.

It really takes some time on a workday because this happens a lot. I hope there is a fix,

Greetings,
Philipp

  • 0 in reply to Edvin 

    (.venv) yat033@WICHITA-PH workspace % nrfjprog -v
nrfjprog version: 10.24.0 external
JLinkARM.dll version: 7.94e

    Custom hardware and a SEGGER j-link Ultra+.
    Flashing the binary (bootloader + application) in seperate parts works fine, combined it consistently fails.
    Doing a full chip erase with `nrfjprog --recover` and then flashing without `--sectorerase` also works fine.
    My suspicion is that with `--sectorerase` and a large binary, the erase component of the job takes too long (12 seconds) and thus the job times out. Is there perhaps a 10 second internal timeout on the erase operation?

  • 0 in reply to Schmid

    Hello,

    Does it work if you do it directly from cmd line using west? If not, what does it say/output/log?

  • 0 in reply to Edvin

    It doesn't make a difference whether it is run through west or directly with `nrfjprog`.
    I have also attached the generated log file.

    (.venv) yat033@WICHITA-PH workspace % west flash -d build/taurus/egrazor
-- west flash: rebuilding
[0/13] Performing build step for 'nrf_secure_boot'
ninja: no work to do.
[3/3] Completed 'nrf_secure_boot'
-- west flash: using runner nrfjprog
-- runners.nrfjprog: reset after flashing requested
Using board 505102200
-- runners.nrfjprog: Flashing file: build/taurus/egrazor/zephyr/merged.hex
Timed out waiting for progress updates.sing non-volatile memory - block 2 of 2
Did worker process die?
[ #################### ]   9.899s | Erase file - Done erasing
ERROR: An internal error has occurred, please try again.
NOTE: For additional output, try running again with logging enabled (--log).
NOTE: Any generated log error messages will be displayed.
FATAL ERROR: command exited with status 63: nrfjprog --program build/taurus/egrazor/zephyr/merged.hex --sectorerase --verify -f NRF91 --snr 505102200
    8130.log.log

  • 0 in reply to JordanYates

    I see. 

    I don't think that nrfjprog would time out if everything is working as expected. I see there are some errors in the log, so it suggests that something else has happened, other than a timeout of ~10 seconds. 

    Is it possible to upload the .hex file that you are trying to program? Perferably both the merged and separated ones.

    Have you tried on a different computer than the M2 Mac?

    I will forward the log to our nrfjprog team, and see if they can make sense of it. 

    Best regards,

    Edvin

  • 0 in reply to Edvin

    What errors are you referring to? `JLINK_HasError()` is just a check that is being called after every operation, and I can't see anything else.

    Hopefully the information I have already provided is enough, as I am finishing up at my current job tomorrow and are therefore not in a position to upload binaries or perform additional checks.

    If I run into the same problem again in the future I will be sure to open another ticket Slight smile

Related