This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

nRF52840 can not burn in .hex (ERROR HighLevel_probe_init)

Hi,

I use the nRF52840 chip, which is designed as a module.

I use nRF9160 DK to burn the hex file.

1.And i can use nRF connect to read the ic of the module.

  But can not burn in .hex.(log is as follows)

2021-03-30T06_50_19.116Z-log.txt

2.I used nrfjprog to clear the flash and the results are as follows.

3.I used nrfjprog to burn hex, but it was not successful. The result is as follows.

What could be the problem?

Thanks.

Sheng

Parents
  • Hi,

    I found nothing in the log indicating that the programming failed, and the nrfjprog screenshots look normal. How do you conclude that the flashing failed?

    Note that in the log there are a few lines with the word "ERROR" spelled out. That is the log level, and does not necessarily mean that any of it is an error. It is normal that logging levels are named e.g. "Fatal", "Error", "Warning", "Info" and "Debug", and this is the case for the nRF Connect programmer app as well. It just so happens that a lot of that nrfjprog output gets logged in the "Error" category of log messages. I am not sure if any of them are indicative of an error or not.

    If you describe more about what you do, what application you are trying to flash, etc., what you expect to happen, and how the board behaves after programming, if there are any error messages displayed inside nRF Connect programmer app, then I have more information to figure out what might be the issue.

    Regards,
    Terje

Reply
  • Hi,

    I found nothing in the log indicating that the programming failed, and the nrfjprog screenshots look normal. How do you conclude that the flashing failed?

    Note that in the log there are a few lines with the word "ERROR" spelled out. That is the log level, and does not necessarily mean that any of it is an error. It is normal that logging levels are named e.g. "Fatal", "Error", "Warning", "Info" and "Debug", and this is the case for the nRF Connect programmer app as well. It just so happens that a lot of that nrfjprog output gets logged in the "Error" category of log messages. I am not sure if any of them are indicative of an error or not.

    If you describe more about what you do, what application you are trying to flash, etc., what you expect to happen, and how the board behaves after programming, if there are any error messages displayed inside nRF Connect programmer app, then I have more information to figure out what might be the issue.

    Regards,
    Terje

Children
No Data
Related