BT840E module programming issue

[PEPL]

IDE: Segger Embedded Studio for ARM V4.12  ,   nRFgo studio

SDK: nRF5_SDK_15.2.0_9412b96 + SDK for Mesh3.1.0,

Softdevice: 6.1.1

Computer Platform: Windows 8 64 Bit

Hardwares: 1 NRF52 Development Board,  2 BT840E modules

RTT viewer:J-link RTT Viewer V6.40

While programming module, below error encounters.. 

Also tried from windows command prompt, but no success and log file as attach here..

log_error.log

[Hung Bui]

Hi,

Have you powered the module ? Which programmer did you use to program the module ? 

Please take a close up photo of your hardware setup. 

[PEPL]

Yes we are powering the module externally from our custom board....

We had embed a module to our custom designed board...  and it powered(3.3V) from that... 

Using a nrf52840 DK  board for programming a module... 

We have our two custom boards and the BLE module to other board is programming properly and working... 

The hardware setup is shown as in above picture.. 

[Hung Bui]

Please correct me if I'm wrong. 

You have 2 setups, both with the BT840E module. And on one of the custom board, the module worked fine and you don't have any problem to program it. But on the other custom board, you can't program it ? 

If it's the case, I would suggest to double check the PCB and soldering, connection.  It's more likely a hardware issue. 

[PEPL]

Hung Bui said:

You have 2 setups, both with the BT840E module. And on one of the custom board, the module worked fine and you don't have any problem to program it. But on the other custom board, you can't program it ? 

Yes that's correct... 

Hung Bui said:

If it's the case, I would suggest to double check the PCB and soldering, connection.  It's more likely a hardware issue.

 No, because in the beginning it was working fine, I have tried many examples on that module... And the other day I saw this error, and unable to program the module .. 

The last code flashed in module was mesh example code... 

By the way I thought the same as you, and checked the Hardware first, like voltage on the module supply pin and programmer pin, checked the voltage level as per suggested in datasheet like on reset pin , etc... 

According to you what else do I test when this kind of issue get generated ?.. 

[Hung Bui]

I don't think the mesh firmware could have any affect here. The SWD interface engages before any firmware can run. 

Could you try using Jlink Commander and capture the log ? It may provide more logging information for us. 

Please follow the instruction here: https://wiki.segger.com/J-Link_Commander