nrfjprog in a daisy chain

RE: nrfjprog in a daisy chain

Sigurd — Thu, 09 Nov 2017 19:42:46 GMT

Normally daisy chaining programming allows you to connected several chips/devices to a single programming interface, and then program them all at once.

Q: How does the SWD know which nrf52 device it is programming since there is one on the nrf52DK and one on the thingy52?

A: When you have connected another device to the Debug out port (P19 or P20) on the nRF52-DK, the Segger J-Link OB debugger on the nRF52-DK will detect the supply voltage of the board and program/debug the target chip on the external board instead of the on-board nRF52832.

If you are interested in production programming, we have a white paper on that here.

RE: nrfjprog in a daisy chain

Dash — Thu, 09 Nov 2017 19:29:39 GMT

If daisy chaining is not supported then how does the procedure in this link work?How does the SWD know which nrf52 device it is programming since there is one on the nrf52DK and one on the thingy52?

RE: nrfjprog in a daisy chain

Sigurd — Thu, 09 Nov 2017 19:11:29 GMT

Note that the nRF5x devices are programmed using SWD, and SWD does not support daisy-chaining.

RE: nrfjprog in a daisy chain

Sigurd — Thu, 09 Nov 2017 19:05:11 GMT

Hi,

You can use the -s command to select the debugger you want to use. From the documentation :

-s --snr <serial_number> Selects the debugger with the given serial number among all debuggers connected to the computer for the operation. Must be combined with another command.