debug fail

RE: debug fail

Simonr — Thu, 06 Jan 2022 11:01:43 GMT

Glad to hear you figured it out! Don't hesitate to submit a new ticket if you run into further issues.

Best regards,

Simon

RE: debug fail

dimmomo — Thu, 06 Jan 2022 02:21:17 GMT

thank u for help

i have figure out the reason why this happened

it is hardware fault

some pins have not been connected to GND

now all can run well

best regards

RE: debug fail

Simonr — Wed, 05 Jan 2022 13:30:44 GMT

It seems like readback protection might be enabled here, so try using nRF Command Line tools and the nrfjprog --recover command to recover the board, which should put it back into "normal" operating mode.

Best regards,

Simon

RE: debug fail

dimmomo — Wed, 05 Jan 2022 08:04:08 GMT

thank u for reply

right now a new problem appeared

i use the nrf connect to load the follow hex。 ble_app_hrs

\components\softdevice\s140\hex\s140_nrf52_7.2.0_softdevice.hex

\examples\ble_peripheral\ble_app_hrs\pca10056\s140\arm5_no_packs\_build\nrf52840_xxaa.hex

it seem failed。

and i use keil to debug

i had a nrf52832 development experience bofore。it worked well and easy to get started

i guess that the reason caused this may be the reset or configure something

can u give me advise？

best regards

RE: debug fail

Simonr — Wed, 05 Jan 2022 07:24:19 GMT

Hi again

How have you connected the third party board to the DK or J-Link device you use to program it and debug the device?

Since this is the BLE UART app it is also expected to be connected to the PC over UART which I'm guessing this third party module is not, so the ble_app_uart might not be the best application to test on a third party board. I would suggest trying out the ble_app_hrs example. The connection seems to be correct in nRFConnect as it seems to program the board correctly, but there's some issue running the project.

Best regards,

Simon

RE: debug fail

dimmomo — Wed, 05 Jan 2022 01:20:53 GMT

thank u for reply、

i wrote the wrong type.

actually i use NRF 52840.

the example is \examples\ble_peripheral\ble_app_uart\pca10056\s140\arm5_no_packs

today i tried the new SDK nRF5_SDK_17.1.0_ddde560

i just compile the project to produce the nrf52840_xxaa.hex。

i use nrf connect for desktop 3.9.1 to write the \components\softdevice\s140\hex\s140_nrf52_7.2.0_softdevice.hex & nrf52840_xxaa.hex to the board。as follow

i power again the board。it is still not work。

and debug has the same trouble as what i said as the title

and i want to mention that i use a third party board（RF-BM-ND06） installed with NRF52840

circuit is as follow

pls give some advice。

best regards

RE: debug fail

Simonr — Tue, 04 Jan 2022 12:39:07 GMT

First off, I see that you say you're flashing the S140 SoftDevice and an nRF52840 application onto an nRF52832, which would cause issues as the nRF52832 has less RAM and Flash memory than an nRF52840, so an application and the S140 SoftDevice might exceed the memory of the nRF52832. You need to use the S132 and an application made for the nRF52832 to ensure correct operation.

Can you also share some information on what example application this nrf52840_xxaa.hex is based on?

Best regards,

Simon

RE: debug fail

dimmomo — Tue, 04 Jan 2022 08:45:53 GMT

I uploaded the wrong first picture ，pls check as above