Hello,
I have a few questions about sending code via J-Link.
We are doing our project on vscode with 2.6 sdk. When working with nrf5340dk, flash via vscode was enough. However, we will need to send code to the cards we will design via external j-link. I want to send code via Nrf Connect Desktop -Programmer application. Which file will I need to upload? What is its extension? Is the file to be uploaded created within the build file?
Hi there,
I use the nRF52840_DK and the JLink (7.94e) the SWD connection to a Xiao nRF52840 BLE Sense MCU
I power the target on first
I power on the nRF52840_DK making sure the 4 wires are connected to P20 from the swd on Xiao expansion board
I open the Nrf_connect for Desktops , Click programer and select the DK as the source.
the status window will tell you which driver and DLL is loaded, depending on the settings it may open and start a read attempt automatically . I know by the Revision and Product family ID in the top right window.
When I turn everything off and leave the power off on the target custom board, The DK reads its internal SOC (Rev 3) when powered up.
both boards are running the Nordic_Blinky_LBS code, built for two different board targets. I only had to add the button "D1" to my custom board device tree as b1 , The Kconfig file options generates a uf2 file build for dragging and dropping to the custom target. works really well.
you can use the other file types as well with the programmer app and Jlink
HTH
GL :-) PJ
here is the setup.
Hi there,
I use the nRF52840_DK and the JLink (7.94e) the SWD connection to a Xiao nRF52840 BLE Sense MCU
I power the target on first
I power on the nRF52840_DK making sure the 4 wires are connected to P20 from the swd on Xiao expansion board
I open the Nrf_connect for Desktops , Click programer and select the DK as the source.
the status window will tell you which driver and DLL is loaded, depending on the settings it may open and start a read attempt automatically . I know by the Revision and Product family ID in the top right window.
When I turn everything off and leave the power off on the target custom board, The DK reads its internal SOC (Rev 3) when powered up.
both boards are running the Nordic_Blinky_LBS code, built for two different board targets. I only had to add the button "D1" to my custom board device tree as b1 , The Kconfig file options generates a uf2 file build for dragging and dropping to the custom target. works really well.
you can use the other file types as well with the programmer app and Jlink
HTH
GL :-) PJ
here is the setup.
