nrf52832 SDK 11.0.0 and SD 2.0.0-7 problem

RE: nrf52832 SDK 11.0.0 and SD 2.0.0-7 problem

silvergaucho — Fri, 05 Feb 2016 08:37:41 GMT

Thank you guys. As proposed by John, I just updated nRFgo and everything seems to work. Just for knowledge @Elinar every application was compiling fine but the problem was that JLink couldn't program the chip. Now seems to be fixed.

RE: nrf52832 SDK 11.0.0 and SD 2.0.0-7 problem

Einar Thorsrud — Thu, 04 Feb 2016 08:03:53 GMT

ID 0x0079 is correct for S132 2.0.0-7 alpha. You can click "Verify" to check that the SoftDevice is not corrupt (given that the file you have downloaded is not).

You write that you cannot upload any application code? Do you get a error message? What happens if you try to upload the application using a different tool, such as Keil or nrfjprog? Can you try to build one of the example applications from the SDK and program that?

RE: nrf52832 SDK 11.0.0 and SD 2.0.0-7 problem

John — Tue, 02 Feb 2016 20:20:47 GMT

Perhaps this post might be helpful: programming changes

RE: nrf52832 SDK 11.0.0 and SD 2.0.0-7 problem

silvergaucho — Tue, 02 Feb 2016 19:25:41 GMT

Problem is that it seems un-programmable other than erasing... will try to update nRFgo Studio

RE: nrf52832 SDK 11.0.0 and SD 2.0.0-7 problem

John — Tue, 02 Feb 2016 19:16:27 GMT

I've seen this on the nRF51 when my nRFgo Studio was older than the soft device loaded onto the chip. I believe that since the soft device was created after the nRFgo Studio release, nRFgo Studio cannot map the hex version number to a string it can print, so it prints the Unknown instead. Your soft device is probably just fine.