Can't flash custom board via nRF52840DK in VS Code

RE: Can't flash custom board via nRF52840DK in VS Code

backstreet.devisor — Wed, 16 Aug 2023 18:24:05 GMT

Yeah, it worked. Thank you so much again for your help.

This topic can be closed.

RE: Can't flash custom board via nRF52840DK in VS Code

Håkon Alseth — Wed, 16 Aug 2023 08:25:12 GMT

Hi,

"west flash" does a pin reset by default:

...
[ #################### ]   0.000s | Verifying image - Verify successful
[ #################### ]   4.452s | Verify file - Done verifying                                                       
Applying pin reset.
-- runners.nrfjprog: Board with serial number 1050749332 flashed successfully.

If you route the "RESET" signal to the reset pin of your custom board, you should be able to flash and run as expected.

Kind regards,

Håkon

RE: Can't flash custom board via nRF52840DK in VS Code

backstreet.devisor — Tue, 15 Aug 2023 17:37:48 GMT

Thank you Hakon for continuing to help me.
After entering the command "nrfjprog --debugreset" in the terminal, my board started up without a power reset.

Is there any way to make this command the default after re-flashing my board? Or do I always have to enter it manually?

RE: Can't flash custom board via nRF52840DK in VS Code

Håkon Alseth — Tue, 15 Aug 2023 08:58:45 GMT

Hi,

Could you try the following?

If you issue "nrfjprog --debugreset" and the board runs as expected afterwards; then it is due to the reset procedure during programming.

Kind regards,

Håkon

RE: Can't flash custom board via nRF52840DK in VS Code

backstreet.devisor — Mon, 14 Aug 2023 16:02:01 GMT

Hi Hakon.

Yes, this is really weird. I'm using a connection like the one in the picture with the board (I don't have the 10-pin version). With a connection like mine, does your custom board start right after programming?

Thanks.

RE: Can't flash custom board via nRF52840DK in VS Code

Håkon Alseth — Mon, 14 Aug 2023 13:27:42 GMT

Hi,

That is strange. When testing here, it runs after a flash in vscode when using a 10-pin cable to another board.

Try to use Segger Ozone, and use the "attach to running target" to see if it is stuck somewhere.

Kind regards,

Håkon

RE: Can't flash custom board via nRF52840DK in VS Code

backstreet.devisor — Fri, 11 Aug 2023 17:07:21 GMT

Thank you for your help. Yes, the crystal failed. I replaced it and everything worked properly.

Can you please tell me, Hakon, how to make it start immediately after downloading the firmware to my custom board via nrf52840DK? Because now when I download the firmware via VS Code I have to power off and on and only then my board starts working. And when I load the program in SES my board starts immediately without rebooting.

RE: Can't flash custom board via nRF52840DK in VS Code

Håkon Alseth — Fri, 11 Aug 2023 10:05:34 GMT

Hi,

[quote user="backstreet.devisor"]Do I have a 32 kHz crystal soldered on my board that doesn't work?[/quote]

Effectively; yes.

It is either loaded incorrectly or similar, making it not resonate properly.

Check for shorts on the lines in question and do a visual inspection to see if anything is out-of-the-ordinary.

Kind regards,

Håkon

RE: Can't flash custom board via nRF52840DK in VS Code

backstreet.devisor — Thu, 10 Aug 2023 17:59:20 GMT

But after adding CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC=y
my board worked.

What does it mean?

Do I have a 32 kHz crystal soldered on my board that doesn't work?

RE: Can't flash custom board via nRF52840DK in VS Code

backstreet.devisor — Thu, 10 Aug 2023 17:51:24 GMT

Thank you Hakon for your response. My board won't enter debug mode. Here is the output from the debug console.

JLinkGDBServerCL: SEGGER J-Link GDB Server V7.88a Command Line Version
JLinkGDBServerCL: 
JLinkGDBServerCL: JLinkARM.dll V7.88a (DLL compiled May  3 2023 14:37:59)
JLinkGDBServerCL: 
JLinkGDBServerCL: -----GDB Server start settings-----
JLinkGDBServerCL: GDBInit file:                  none
JLinkGDBServerCL: GDB Server Listening port:     52792
JLinkGDBServerCL: SWO raw output listening port: 2332
JLinkGDBServerCL: Terminal I/O port:             2333
JLinkGDBServerCL: Accept remote connection:      localhost only
JLinkGDBServerCL: Generate logfile:              off
JLinkGDBServerCL: Verify download:               off
JLinkGDBServerCL: Init regs on start:            off
JLinkGDBServerCL: Silent mode:                   on
JLinkGDBServerCL: Single run mode:               on
JLinkGDBServerCL: Target connection timeout:     0 ms
JLinkGDBServerCL: ------J-Link related settings------
JLinkGDBServerCL: J-Link Host interface:         USB
JLinkGDBServerCL: J-Link script:                 none
JLinkGDBServerCL: J-Link settings file:          none
JLinkGDBServerCL: ------Target related settings------
JLinkGDBServerCL: Target device:                 nRF52840_xxAA
JLinkGDBServerCL: Target device parameters:      none
JLinkGDBServerCL: Target interface:              SWD
JLinkGDBServerCL: Target interface speed:        12000kHz
JLinkGDBServerCL: Target endian:                 little
JLinkGDBServerCL: 
=thread-group-added,id="i1"
=cmd-param-changed,param="pagination",value="off"
z_arm_reset () at C:/nordicsemi/v2.2.0/zephyr/arch/arm/core/aarch32/cortex_m\reset.S:73
73	    movs.n r0, #0
[New Remote target]

RE: Can't flash custom board via nRF52840DK in VS Code

Håkon Alseth — Thu, 10 Aug 2023 12:09:13 GMT

Hi,

Q1: Have you tried entering debug mode and see where it's stuck?

Q2: Could this be a problem with the external LF clk?

Can you try to set "CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC=y" and see if the other board boots up as expected?

Kind regards,

Håkon