Over the air,

RE: Over the air,

Federico — Tue, 07 Jan 2014 15:06:34 GMT

Thank you Runar, I'll follow your recommendations. Have a nice day,

RE: Over the air,

run_ar — Tue, 07 Jan 2014 14:51:18 GMT

You are right; the nRF8200 is only for the DK. Since you would have to move to another platform for production I would recommend that you do that early on in the process and do most of your development there. The nRF8001 will simply handle the transport, so you should choose an application controller that has enough flash to store the application; alternatively you should create a bootloader that you can use to overwrite the application. How to actually do the update will depend on the MCU you choose.

I would also advise you to consider the nRF51822 as this already has a Device firmware update example in its SDK and is a newer more up to date product.

Of course, if you are looking for a simple connectivity solution and can live with the limitations (lower data throughput and fixed stack) of the nRF8001 you might be interested in knowing that there are SDK ports for a few MCU’s available upon request from the support portal. Take a look at these pages on devzone: nrf8001-communicaton-to-other-microcontroller getting-started

Br, Runar

RE: Over the air,

Federico — Tue, 07 Jan 2014 14:17:52 GMT

Thank you so much Runar for your answer.

So, using a MCU with more flash would be the solution and no aditional hardware will be necesary ? I've suspected in our case that the 8200 was just for the 'dev kit' and for production we have to move to another one.

Thank you so much,

RE: Over the air,

run_ar — Mon, 06 Jan 2014 21:10:26 GMT

Hi,

I don't think anyone has tried this with the nRF8200. Since the flash size of the MCU is only 16 KByte I suspect you wouldn't have enough space to do this. I would suggest that you use an MCU with more flash; Have you considered using the nRF51822?

Br, Runar