Flash erase of custom board with u-blox module

RE: Flash erase of custom board with u-blox module

Simonr — Mon, 29 Jun 2020 10:17:40 GMT

I see. Glad you were able to figure it out on your own!

Best regards,

Simon

RE: Flash erase of custom board with u-blox module

Venkat Vallapaneni — Mon, 29 Jun 2020 09:31:36 GMT

Hi Simon,

Thanks for the reply. We found the issue. We had some LEDs which are drawing more current and so voltage is not coming properly to the module.

RE: Flash erase of custom board with u-blox module

Simonr — Mon, 29 Jun 2020 06:53:38 GMT

Are you using the onboard debugger on your DK to flash the device or a dedicated debugger (if so, is it a J-Link debugger or something else)? Can you show me how your module is connected to the debugger? Are you using a 10-pin header or are you connecting the custom board to the DK as in the picture shown below?

Either way, please triple-check that the pin-out is correct in your setup.

Best regards,

Simon

RE: Flash erase of custom board with u-blox module

Venkat Vallapaneni — Fri, 26 Jun 2020 12:43:28 GMT

Hi Simon,

I tried --recover command but no luck. Looks like the problem is much before accessing flash operations. The very first coresight reg access failed: In the log file attached, you may notice this:

. . . Segger_read_debug_port_register: JLink INFO JLINK_CORESIGHT_ReadAPDPReg(DP reg 0x00)
2020-Jun-26 13:57:24 . . . . Segger_read_debug_port_register: JLink INFO T2F18 000:705.933
2020-Jun-26 13:57:24 . . . . Segger_read_debug_port_register: JLink INFO failed

When I did the same thing for DK, I get the ID:

2020-Jun-26 13:58:15 . . . . Segger_read_debug_port_register: JLink INFO JLINK_CORESIGHT_ReadAPDPReg(DP reg 0x00)
2020-Jun-26 13:58:15 . . . . Segger_read_debug_port_register: JLink INFO T1B7C 000:627.395
2020-Jun-26 13:58:15 . . . . Segger_read_debug_port_register: JLink INFO Value=0x2BA01477

Does the info code signify anything? They are different for DK: T1B7C (which is passing) and my custom board: T2F18 (which is failing)

Thanks,

Venkat.

RE: Flash erase of custom board with u-blox module

Simonr — Fri, 26 Jun 2020 12:35:22 GMT

Hi Venkat

Can you try recovering the chip, by using the nrfjprog --recover command, as it might be the APPROTECT that is hindering you from accessing the chip's flash memory.

Best regards,

Simon