Some Guidance on moving from Arduino to nRF52840

[PhilAJ52]

I have an application that has been built using Arduino boards and shields for prototyping, and software developed using their IDE...all works fine.

The device comprises BLE, Infra Red Input and Output, plus a TFT screen...

I am now looking to move to mass production and the proposed manufacturing company is suggesting the nRF52840 as processor of choice.

My queries are;

a) I am assuming that my onboard software will need to be redeveloped for Nordic libraries etc ...Will the nRF5 SDK and nRF52840 DK give me everything I need to develop the software, including libraries for BLE, display driving (not sure which displayto use yet) ?

OR do I have to use the IAR or SEGGER systems?

b) Are there any libraries available for Infra Red protocol transmission ?

c) A more technical question regarding the actual BLE Chip. On the Arduino - the BLE Device Id could change after reset of the boards - meaning that it couldn't be used to 'tie in' to a user's App. Is the Device Id  within the nRF52840 unique - and available to my software??

Thanks for any help that can be given.

Phil

[butch]

Have you seen https://github.com/sandeepmistry/arduino-nRF5?  It doesn't provide Arduino BLE wrapper.  You didn't say what board you are on now, and I don't know on what boards Arduino provides BLE wrapper, if at all.  Is there is an Arduino BLE library for your board?  Then you might need to port it to NRF52?  I cannot vouch for that link, it probably is a minimal implementation.

In my limited experience (I do just a little Arduino, and much NRF52) there is just a little support for Arduino on the NRF52.  For example, the NRF52DK and its user manual talks briefly about Arduino headers (that you can add to the back of the board.)  And I was just yesterday reading about the Arduino Primo which uses the NRF52, but just went out of support by arduino.org (politics around arduino?)  But I suppose you are asking whether you can abandon Arduino?

b) I don't think "Infra Red protocol" defines a standard.  You would need to give more detail.

c) the device ID is available and unique (not that it is guaranteed unique, just that it is pseudo-randomly generated at the factory and with very high probability is unique.)