[SOLVED] nRF52832-QFAA-R7 - Non-function by unknown

[Usr]

Hi,

I have a problem with the nRF52832-QFAA-R7 chip on a developed board.
The chip can be programmed via SWD, but then neither the DFU mode nor the program starts.
For the programming I use a Segger J-Link, the nRF5-SDK 15.2.0 and nRFgo Studio. The wiring is essentially a ground circuit like the Sparkfun developer board.
The pcb was manufactured and assembled by a professional pcb manufacturer. The programming and tests were carried out with a constant voltage source of 3.3V.

used codes:

- softdevice s132
- sfe_nrf52832_dfu bootloader for UART
- ble dfu boot loader from sdk examples
- simple app codes (led blink, ble communication, ...)

I have tested and measured the following:

- UART bootloader programmed -> no UART connection and no HIGH start signal
- ble bootloader programmed -> no device found, no activity at PIN30
- RESET line measurement, no permanent ground fault on the RESET line
- Program, Bootloader and Softdevice tested on other board -> works

What do I overlook?

[Sigurd]

Hi,

Usr said:

tested on other board -> works

What board is this? The nRF52832-DK?

What IDE/toolchain are you using? 

Are you able to run simple peripheral examples, sush as blinky ?

[Usr]

The other board is a Sparkfun nRF52832 breakout board wich I still had here.
I have tried some IDE's (eclipse, Visual Studio Code ,Arduino IDE(sorry for this)) with gcc toolchain.
I've used a simple led flashing code.

[Sigurd]

Usr said:

nRFgo Studio

nRFgo Studio is deprecated, so I recommend using nRFConnect for Desktop, and use the Programmer app instead.

Usr said:

I've used a simple led flashing code.

and did that work? Did the led flash/blink?

[Usr]

It doesn't works. I have tried nRFConnect and it doesn't works too.
The JTAG programming works very well but then neither the program nor the bootloader starts. Even if I only upload the ble dfu I get no function.

[Sigurd]

Did you test with blinky? It can be found in SDK_folder\examples\peripheral\blinky.

Try using Segger Embedded Studio(SES), with the SES-project found in blinky\pca10040\blank\ses. Try to start a debug session (Debug -> Go, or press F5), and check if you are able to step through the code.

[Usr]

I've tried it out, it doesn't works too.
I have a suspicion. Could it be that a not gnd connected "Die pad" is the solution?
There was a false layer in pcb design for this connection.

[Sigurd]

Since you added [SOLVED] to the title, I assume that this was the issue.