nRF52832 begginer questions

[Marton Schliszka]

Hello!

I'm planning to start a project with the nrf52832 chip, I mainly choose this product, because of the low power consumptions and ble.

I would like to start my development on an nrf52 DK so I can get familiar with the software solutions Nordic provides for programming for example the SDK V17, but before I make my purchase I would have some questions what came up to me as my read the documentation of the sdk.

One of my main concern is the programming of the chips in the production state if my project gets that far. If I use for example SEGGER and the nRF52 SDK I will be able to migrate my codes to a nRF52832 chip which is built in an enviroment as the reference circuit shows in the chips documentation with the pheriferials I build around it? My guess is then I will need to configure a new custom board header where I define my LED outputs for example, am I right?

What hardware tools are necessary for a production stage implementation of the chip? Can you recommend me some documentation about this?

What programming enviroment do you recommend for the project? First I started to get familiar with SES, but the most examples use KEIL in the documentation. Do you recommend to switch?

As everybody, I have experience with arduino boards, a little micropython, and some bare-metal programming of MSP microcontrollers. For a low energy application do you recommend bare-metal programming or the program written with the sdk will be effective enough with the right interrupt and timer handling?

Can you reccommend some straightforward learning material beside the nRF5 SDK documentation?

How long do you thing this chip will be available? How long is usually the product life cycle? This is a completly new project so I wouldn't want to start on an outdated product.

Thank you very much:

Marton

[tesc]

Hi,

Your assumptions regarding changing board are correct. In nRF5 SDK, changing to a different board is done by changing a header file (board file) into the correct configuration of pins, etc. for the new board.

Regarding the production stage, usually one would outsource to a production facility. In some instances one would send the SoCs via a third party for programming, or program the devices after production. For the latter one must have programming pins available and use a J-Link programmer, or in advance have programmed a DFU solution onto the SoC.

Our main recommendation is SES. We used Keil as main IDE in the past, hence the amount of (older) documentation using Keil.

I would definitely use the SDK. It is developed with efficiency in mind, and also it is well tested and has workarounds for erratas.

For learning materials, see e.g. the short range guides here on DevZone.

For future proofing you might want to look into nRF Connect SDK / documentation / guides, which is our new SDK. nRF52 is supported in nRF Connect SDK and has a long life in front of it still, so I would not be worried starting an nRF52 project today.

For further questions regarding production stage (what possibilities you have there, contact info for third parties, etc.) please contact our regional sales manager for your area. If you do not know who that is, please let me know in a private message or ask in a private ticket and we will let you know. The same goes for future plans and product longevity.

Regards,
Terje

[Marton Schliszka]

Hello, 

Thank you very much for your fullfilling answeres I will look into the guides and contact you if we will come to a production state and we dont find a regional sale manager. 

Best regards:

Márton

[tesc]

Hi,

Note that Regional Sales Managers are employees of Nordic Semiconductor who are responsible for a geographic area. If you need to contact the one for your area, you can send a private message or create a private ticket, and we will provide the contact details. (That is, they are not third parties.)

Regards,
Terje