Custom board programming failed

RE: Custom board programming failed

bjorn-spockeli — Tue, 15 May 2018 06:57:20 GMT

Sylvain: Happy to hear that the new PCB is working as it should. I guess we can assume that the IC was damaged somehow or nor properly soldered to the PCB.

RE: Custom board programming failed

Sylvain — Mon, 14 May 2018 18:13:44 GMT

Hi Bjorn,

The new PCB works well.

Thanks for the support.

Sylvain.

RE: Custom board programming failed

bjorn-spockeli — Wed, 09 May 2018 10:35:05 GMT

Yes, please let me know if see the same behaviour on the new PCB or not.

RE: Custom board programming failed

Sylvain — Wed, 09 May 2018 09:40:10 GMT

I'll try to solder a new PCB on Monday. I'll keep you in touch.

RE: Custom board programming failed

bjorn-spockeli — Wed, 09 May 2018 09:11:22 GMT

Yes, I think that we can rule out any driver issue then, since you're able to flash and verify another nRF52840 device.

Are you able to check if code actually runs on the device if you omit the --verify option? E.g. flash one of the precompiled peripheral examples that blinks a led or one of the ble examples and see if the board advertises. You could also try to compile an example yourself and see if your're able to flash and debug it for instance.

All our ICs are production tested so faulty devices should be screened out, but the chip might have been damaged during soldering to the PCB or it could be ESD damage. Hard to say with out examining the IC.

RE: Custom board programming failed

Nguyen Hoan Hoang — Tue, 08 May 2018 19:56:21 GMT

I see the output that it tries to program 2 boards at the same time. Is it that intended ? Could that be a conflict problem ?

RE: Custom board programming failed

Sylvain — Tue, 08 May 2018 13:20:36 GMT

Yes same behaviour with a precompiled HEX file.

I have 2 nRF52840PDK, same behaviour with the two. When I try to program one PDK with another PDK, everything works fine.
So, definitely I think the problem come from the chip on the custom board. Maybe the flash is damaged ... is it possible ?

RE: Custom board programming failed

bjorn-spockeli — Tue, 08 May 2018 12:47:09 GMT

Do you see the same behavior if you try to flash one of the precompiled application examples from the nRF5 SDK, e.g. ble_app_hrs?

If you omit the --verify option and flash the SoftDevice and a precompiled application, is the nRF52840 DK advertising( LED 1 blinking)? If yes, is it visible and connectable in the nRF Connect app?

Also do you only have this one nRF52840 DK or do you have another one that you could test with?

RE: Custom board programming failed

Sylvain — Tue, 08 May 2018 09:07:01 GMT

Sadly, it is the same result ...

C:\Users\Sylvain>nrfjprog --version
nrfjprog version: 9.7.2
JLinkARM.dll version: 6.32a

C:\Users\Sylvain>nrfjprog -f nrf52 --program s140_nrf52_6.0.0_softdevice.hex --chiperase --verify --log
Parsing hex file.
Erasing user available code and UICR flash areas.
Applying system reset.
Checking that the area to write is not protected.
Programing device.
Verifying programming.
ERROR: Write verify failed.

devzone.nordicsemi.com/.../0488.log.log

RE: Custom board programming failed

bjorn-spockeli — Tue, 08 May 2018 08:39:11 GMT

Could you try to update to JLinkARM.dll v6.32a from Segger? Here is the link.

RE: Custom board programming failed

Sylvain — Tue, 08 May 2018 08:19:32 GMT

My version of nrfjprog is the last one. I downloaded and installed this file nRF5x toolset installer for Windows (JLinkARM, JLink CDC, nRFjprog, and mergehex) V9.7.2.

Result in the terminal:

nrfjprog version: 9.7.2
JLinkARM.dll version: 6.20i

The log file is attached to this post.
devzone.nordicsemi.com/.../5383.log.log

RE: Custom board programming failed

bjorn-spockeli — Tue, 08 May 2018 07:38:58 GMT

Which version of nrfjprog and which JlinkARM.dll version are you using( You can check by running nrfjprog --version) ? If you're not using nrjfprog v9.7.2 and/or JLinkARM.dll v6.32a, then please update to the latest version.

If you are using the latest versions, then could you run the same command with the --log option, i.e.

nrfjprog -f nrf52 --program s140_nrf52_6.0.0_softdevice.hex --chiperase --verify --log

This will generate a log.log file in the directory where you called nrfjprog. Please attach it to this case.

RE: Custom board programming failed

Sylvain — Mon, 07 May 2018 16:06:28 GMT

Here're the results :

C:\Users\Sylvain>nrfjprog -f nrf52 --program s140_nrf52_6.0.0_softdevice.hex --chiperase --verify
Parsing hex file.
Erasing user available code and UICR flash areas.
Applying system reset.
Checking that the area to write is not protected.
Programing device.
Verifying programming.
ERROR: Write verify failed.

It is the same problem as previous...

RE: Custom board programming failed

bjorn-spockeli — Mon, 07 May 2018 13:07:22 GMT

The connections look good and since you're able to erase and flash, but not verify, then I do not think this is a connection issue.

Could you try to program the SoftDevice using nrfjprog and not nRFGo Studio using the following command:

nrfjprog -f nrf52 --program <name of softdevice hex>.hex --chiperase --verify