Nrf52840 Custom Board Not Detected After erase from VSCode

[Dhaval Dalvadi]

We are facing strange issue we have this board https://www.raytac.com/product/ins.php?index_id=47

whenever we flash any firmware it works fine but if we erase from vs code it no more detectable to flash or do anything again ?

using nrf connect sdk 2.7.0 already have brick 5 boards so worried to try on more

[Vidar Berg]

Hello,

Have you created a custom board with the Raytac module in the link, or are you using a Raytac development board? In either case, it would be helpful to see a picture of your setup (board + debugger) along with your board schematics. I can't think of any obvious reasons why the board would become bricked after an erase.

Best regards,

Vidar

[Dhaval Dalvadi]

Here is schematic for reference 

connection using Segger and have connected 3.3v and GND from TTL and SWDIO and SWDCLK from segger 
it flashes other boards but not if already flashed and trying to reflash this custom board 

Here is the error message from nRF connect sdk Desktop Programmer when try to connect and flash

14:44:42.102 Failed "reading readback protection status for application core". Error: code: 1, description: Generic, message: Batch task protection-get failed, [Probe] Device error: Failed to write DebugPort register 2: Unknown Error in J-Link DLL (error code =-1)
14:44:42.313 Error: Failed with exit code 1. One or more batch tasks failed: - [Probe] Device error: Failed to write DebugPort register 2: Unknown Error in J-Link DLL (error code =-1), code: Generic. Message: Batch task protection-get failed, [Probe] Device error: Failed to write DebugPort register 2: Unknown Error in J-Link DLL (error code =-1).
14:44:42.313 Error: Failed with exit code 1. One or more batch tasks failed: - [Probe] Device error: Failed to write DebugPort register 2: Unknown Error in J-Link DLL (error code =-1), code: Generic. Message: Batch task protection-get failed, [Probe] Device error: Failed to write DebugPort register 2: Unknown Error in J-Link DLL (error code =-1).

[Vidar Berg]

OK, I can't think of any obvious reasons for this. Please provide as much relevant details as possible. Were you using a board from Raytac?

[Dhaval Dalvadi]

Vidar Berg module is from Raybac but have made our own board as shared schematic 

[Dhaval Dalvadi]

Hi Vidar Berg 
I think this post is also similar Recovering nrf52840 DK after erasing in VS Code nRFconnect extension

except its nrf52840DK but we have custom board

in ids its giving only one as its through segger 
working board and non working board both fives single id 

[Vidar Berg]

 I don’t see anything in the linked Q&A that appears related to the issue you’re facing. --ids returns the serial numbers of connected J-link probes. Is your J-link driver and nfjprog version up to date? What error do you get when you run --recover? Post nrfjprog log here please.

[Dhaval Dalvadi]

Vidar Berg 
Let me know if anything else needed

[Vidar Berg]

The full log is generated by including '--log' in your nrfjprog command as stated in the nrfjprog output you posted. Anyway, I don't think it will be needed after all. The error message already shows that the debugger is unable to connect to the target at all. I wonder if this could be due to mismatched IO voltages between the debug probe and the nRF.

Dhaval Dalvadi said:

Segger and have connected 3.3v and GND from TTL and SWDIO and SWDCLK from segge

I'm not sure I understand what you mean here, but note that the IO voltage on the chip is controlled by the UICR.REGOUT0 register when using the High Voltage mode configuration and that it is always 1v8 after an eraseall.