• State Not Answered
  • Replies 3 replies
  • Subscribers 25 subscribers
  • Views 162 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 290503
Options
nRF5 SDK is not maintained anymore
More Info: Consider nRF Connect SDK for new designs

Flashing issues

user113531

I use flash and erase button at Visual Studio Code but get warnings:
I use custom board, nrf sdk 1.9.1

Flashing build to 960168015
west flash -d c:\Users\maxim\Desktop\Projects\Git\vitals_app_v3_0\vitals\build --skip-rebuild -r nrfjprog --dev-id 960168015 --erase

-- west flash: using runner nrfjprog
-- runners.nrfjprog: mass erase requested
-- runners.nrfjprog: Flashing file: C:\Users\maxim\Desktop\Projects\Git\vitals_app_v3_0\vitals\build\zephyr\merged_domains.hex
-- runners.nrfjprog: C:\Users\maxim\Desktop\Projects\Git\vitals_app_v3_0\vitals\build\zephyr\merged_domains.hex targets both nRF53 coprocessors; splitting it into: C:\Users\maxim\Desktop\Projects\Git\vitals_app_v3_0\vitals\build\zephyr\GENERATED_CP_NETWORK_merged_domains.hex and C:\Users\maxim\Desktop\Projects\Git\vitals_app_v3_0\vitals\build\zephyr\GENERATED_CP_APPLICATION_merged_domains.hex
Parsing image file.
WARNING: A programming operation has been performed without --verify.
WARNING: Programming can fail without error.
Parsing image file.
WARNING: A programming operation has been performed without --verify.
WARNING: Programming can fail without error.
Applying pin reset.
-- runners.nrfjprog: Board with serial number 960168015 flashed successfully.

Terminal will be reused by tasks, press any key to close it.

1. How to deal with warnings?

2. After erase and flash the device not reset 

3. Sometimes if i press Debug action i get "Error: GDB failed: Cannot access memory at address 0x85a61330 (from data-disassemble -s 0x85a61330 -e 0x85a61970 -- 5)" 

Thanks.

Parents
  • 0

    Hello,

    These warnings are caused due to an update in nrfjprog (nRF Command Line Tools), which is used by West when flashing the devices. 

    1: Just be aware that the programming is not using the --verify flag. In general, that is not a problem. This would typically only be an issue when you are using nrfjprog --program, but you forget to erase the chip first (using --eraseall or --sectorerase).

    2: I have seen that from time to time. When you see this, what DK/sample are you using?

    3: Does that depend on what application you are trying to debug? Or is it regardless of the application? Does it happen if you use "nrfjprog --recover" on the device before programming and start a debug session?

    Best regards,

    Edvin

Reply
  • 0

    Hello,

    These warnings are caused due to an update in nrfjprog (nRF Command Line Tools), which is used by West when flashing the devices. 

    1: Just be aware that the programming is not using the --verify flag. In general, that is not a problem. This would typically only be an issue when you are using nrfjprog --program, but you forget to erase the chip first (using --eraseall or --sectorerase).

    2: I have seen that from time to time. When you see this, what DK/sample are you using?

    3: Does that depend on what application you are trying to debug? Or is it regardless of the application? Does it happen if you use "nrfjprog --recover" on the device before programming and start a debug session?

    Best regards,

    Edvin

Children
Related
Terms of service