Flashing, programming the NRF Series 5 (52820, 52833)

[MuRa]

Hello everyone,

This was discussed before, elsewhere (link) , however, it is meant for the "nRF51422 chip " and I need to resolve some other points too ...

1.  it is necessary to put the target to the high-z via reset when programming or not, namely can only the four pins from the SWD (vdd, gnd, SWD i/o and SWD clock) be used to flash the final program (hex) on a new chip , case for prototyping, it is ok to stay on the nrf52dk :
   1. the wiring setup  [ nrF52DK ] -> SWD -> [ nrf52820 -> i2c/twi-> sensor ] 
      1. I guess the use of OB J-Link allows me to use the J-Scope, namely to read the GPIOs of the target in this case? BTW I guess that the J-Scope is used within the code eg. NRF_LOG_INFO that I am currently using to printout to the UART (putty...)   
   2. The external sensor is used via the TWI , therefore, sometimes it is a need to access the sensor separately from the uC, hence the idea of high-z ... however, if it is possible to access the sensor via the target, namely via the J-Scope than I guess the high-z is not necessary...
2. Previous fleshing software was apparently the nRFGO Studio, but it is obsolete, I have not found what else to use these days probably due to so many options ?
3. Does Nordic provide the service of flashing the firmware on newly bought chip, or is this only possible via the distributors, in short who to address when such need is required? 
4. Can the NRF52820, x833 be programmed, developed on / via the nRF52DK according to the above connections, I  guess the SEGGER provides all the "JLink" software to achieve that?

Any help is much appreciated!

Best.

[Håkon Alseth]

Hi,

 

 it is necessary to put the target to the high-z via reset when programming or not, namely can only the four pins from the SWD (vdd, gnd, SWD i/o and SWD clock) be used to flash the final program (hex) on a new chip , case for prototyping, it is ok to stay on the nrf52dk :

1. the wiring setup  [ nrF52DK ] -> SWD -> [ nrf52820 -> i2c/twi-> sensor ] 
   1. I guess the use of OB J-Link allows me to use the J-Scope, namely to read the GPIOs of the target in this case? BTW I guess that the J-Scope is used within the code eg. NRF_LOG_INFO that I am currently using to printout to the UART (putty...)   
2. The external sensor is used via the TWI , therefore, sometimes it is a need to access the sensor separately from the uC, hence the idea of high-z ... however, if it is possible to access the sensor via the target, namely via the J-Scope than I guess the high-z is not necessary...

SWD requires VDD/GND/SWDIO/SWDCLK to be wired up correctly, as per the picture in the thread that you linked to.

SWD is used to program the nRF device. It cannot be used to interface generic sensors.

 

Previous fleshing software was apparently the nRFGO Studio, but it is obsolete, I have not found what else to use these days probably due to so many options ?

nrfjprog for instance, which is delivered as a part of the nrf command line tools: https://www.nordicsemi.com/Products/Development-tools/nrf-command-line-tools/download 

nRF connect for desktop also has a "programmer" application that you can use.

Does Nordic provide the service of flashing the firmware on newly bought chip, or is this only possible via the distributors, in short who to address when such need is required? 

We do not offer pre-flashed devices.

If you contact your local distributor or regional sales manager, they can probably help you get in touch with 3rd-party companies that provide such services.

 

Can the NRF52820, x833 be programmed, developed on / via the nRF52DK according to the above connections, I  guess the SEGGER provides all the "JLink" software to achieve that?

For nRF52833 development, I strongly recommend that you use a nRF52833-DK:

https://www.nordicsemi.com/Products/Development-hardware/nRF52833-DK

 

For nRF52820 development, you can use the nRF52833-DK:

https://infocenter.nordicsemi.com/topic/sdk_nrf5_v17.1.0/nrf52820_user_guide.html?cp=8_1_5_2

 

Kind regards,

Håkon

[MuRa]

Thank you for the reply, indeed, very good reply, the only thing I am not sure what is meant here with regard to the right dev board, a bit ambiguous answer... 

In short, in case of choosing the nrf52820 chip, can it still be programmed/flashed via the nRF52DK? I guess the nRF52833-DK is used to develop for the nRF52833 , including the smaller versions like the nRF x... 820 or am I wrong? In this case I am wondering what is the point of using the nRF52DK then

Since we are talking about two chips that are rather close in line, I am wondering what is their main difference, for example in quick look there is a diff in memory size and package, and price definitely, but is there anything else I should know ?

Thank you in advance and all the best. 

[Håkon Alseth]

Hi,

 

MuRa said:

In short, in case of choosing the nrf52820 chip, can it still be programmed/flashed via the nRF52DK? I guess the nRF52833-DK is used to develop for the nRF52833 , including the smaller versions like the nRF x... 820 or am I wrong? In this case I am wondering what is the point of using the nRF52DK then

Yes, you can still program any nRF52-device with the nRF52-DK.

The reason I recommend a nRF52833-DK is because this and the nRF52820 are quite similar, meaning that you can emulate a nRF52820 using  nRF52833-DK, as described in the former link.

MuRa said:

Since we are talking about two chips that are rather close in line, I am wondering what is their main difference, for example in quick look there is a diff in memory size and package, and price definitely, but is there anything else I should know ?

nRF52820 is a subset of the nRF52833, meaning that nRF52820 a "cut-down" version of the nRF52833.

You can get a better overview of the differences between the nRF52-devices on this site:

https://infocenter.nordicsemi.com/topic/struct_nrf52/struct/nrf52.html?cp=4

 

Kind regards,

Håkon