Using third party nrf52

RE: Using third party nrf52

Edvin — Mon, 12 Feb 2018 08:34:38 GMT

Hello,

This is an old thread, but it seems that your issue is not completely like this one. I suggest you start a new thread, where you describe the problem in detail. You can link to this case, but describe what is similar, and what are the differences. I see that you get some info when you write "nrfjprog -i", but explain where in the process it fails, and what output you get, and we will help you.

BR,

Edvin

RE: Using third party nrf52

cpersoz — Fri, 09 Feb 2018 08:40:18 GMT

Hello, did you found a workaround about this? I'm facing to a similar issue except that my JLink properly respond and returns all the Raytac Module information when entering nrfjprog.exe -i
All advices are welcome!
Thanks.

RE: Using third party nrf52

Einar Thorsrud — Mon, 29 Aug 2016 06:29:30 GMT

Just to be sure, can you execute the command nrfjprog.exe -i when you have the debugger connected to your board? If you get a number printed out, that is the ID of the debugger. Then try "nrfjprog.exe --family NRF52 -s -r", just to see if something works. If it does not, can you try to powercycle the board and disconnect and reconnect the debugger and try again?

RE: Using third party nrf52

TZ — Fri, 26 Aug 2016 08:38:01 GMT

Both nrfjprog and nRFgo Studio give no response (cannot detect the bluetooth device) so i cannot verify the flashing process.

RE: Using third party nrf52

Einar Thorsrud — Fri, 26 Aug 2016 08:32:48 GMT

You can use the verify functionality of nrfjprog (--verify) or nRFgo Studio (after selecting the .hex-file, click the "Verify" button instead of the "Program" button). This will compare the content of the flash with the .hex file. If it succeeds, you can confidently say that the earlier programming was successful.

RE: Using third party nrf52

TZ — Fri, 26 Aug 2016 04:13:41 GMT

I did tried again and the SD file is flashing in 12 seconds time while the application file is flashing in 5 seconds time. However, is it any other way that i can use in order to make sure that I have successfully load my SD? Besides, i did uninstall and install the latest nRFgo Studio but it seems like give no changes to the condition.

RE: Using third party nrf52

psharma — Fri, 26 Aug 2016 02:57:08 GMT

The second and the third pictures look pretty much the same to me. I don't think the second picture is flashing the soft device, but actually the application.

Writing SD generally takes about 12 seconds, as it is large while application is uploaded in merely 5 seconds. So you may be able to distinguish based on that.

The nRFgo Studio error seems like some trouble in nrfjprog installation. Try uninstalling and reinstalling the latest one.

RE: Using third party nrf52

TZ — Fri, 26 Aug 2016 02:04:44 GMT

There are 5 pins, Vcc, Gnd, Reset, SWDIO and SWCLK from the chip connected to the debugger. I did test with the blinky example that there are output on the pin of the chip. After that I have tried with "ble_app_uart" example but I am still not able to find the device via bluetooth scanner. The first picture is NRFgo Studio, and CMD The second picture is when I load the softdevice. The third picture is when I load the application file.

RE: Using third party nrf52

psharma — Thu, 25 Aug 2016 12:52:08 GMT

How are you verifying that keil indeed is programming the device? It would be helpful if you could post the outputs of the flashing sequence in keil (at the bottom of the keil window).

Can you also verify if you can successfully flash a blinky example that doesn't need a softdevice?

RE: Using third party nrf52

Einar Thorsrud — Thu, 25 Aug 2016 11:29:11 GMT

How have you connected the chip to the debugger in detail? How did you verify that Keil was able to flash (I ask because it seems strange that you see a different situation from Keil and nRFgo Studio).

RE: Using third party nrf52

TZ — Thu, 25 Aug 2016 09:56:43 GMT

it did show up the "nRF5x Programming" in the Device Manager but there is "No Device Detected,...".Besides, by using nrfjprog, it shows "JlinkARM .dll load failed..."

RE: Using third party nrf52

Einar Thorsrud — Thu, 25 Aug 2016 08:53:10 GMT

If you are able to program through Keil, you should have the debugger hooked up correctly, and it should not be an issue programming with nRFgo Studio or nrfjprog either. In nRFgo Studio you should see the debugger show up under "nRF5x Programming" in the Device Manager panel on the left side. (There will not be a separate line for the debugger, as only kits or dongles from Nordic shows up that way). Regarding the SoftDevice you are right that if you have a BLE application (or another application that is built to be used with a SoftDevice, it will not work if the SoftDevice is not flashed.)

RE: Using third party nrf52

omgann — Thu, 25 Aug 2016 03:54:06 GMT

I had did cross check where SWIO 3V while SWCLK 0V. Actually I am able to flash the program though keil but the program did not activate the bluetooth. I think that not flashing softdevice is my major problem. I am using jlink V6.00g.

RE: Using third party nrf52

psharma — Wed, 24 Aug 2016 10:38:17 GMT

Segger J-Link and nRF Go Studio will work out of the box if your connections are correct and your nRF52832 on the third-party module is functioning.

J-Link Commander will not be able to write the SoftDevice or any HEX to the SoC if it is not able to communicate with it.

I suggest that you cross check your SWDIO and SWDCLK connections, and ensure that the module is powered within 1.8V - 3.6V. It is not 5V tolerant. If the module has previously been provided 5V on any pin, it is most likely damaged.

Alternatively you may make sure your J-Link is working fine by connecting another nRF51/nRF52 SoC and detecting it. If that doesn't work you could try the solution in this question to validate j-link firmware, and reinstall the latest j-link drivers from here.

Basically you want to figure out whether your problem is in the J-Link, it's drivers, your connections, or the module.

Good luck!