Hi, we are designing a product that needs LTE connectivity and BLE for local setup.
The nRF9160DK uses an nRF52840 with some links for COEX and comms.
Is there any reason why the nRF52832 cannot be used instead?
Thanks
Hi, we are designing a product that needs LTE connectivity and BLE for local setup.
The nRF9160DK uses an nRF52840 with some links for COEX and comms.
Is there any reason why the nRF52832 cannot be used instead?
Thanks
Hello,
Is there any reason why the nRF52832 cannot be used instead?
The reason for why we have used the nRF52840 is because we want to support ZigBee and Thread (802.15.4) and all features of BT5 i.e. long-range on the nRF9160 DK. The nRF52840 also supports more peripherals and has a bigger flash (1 MB) for bigger code size.
For more information on the differences, please see the nRF52 Comparison table.
If your application does not need what I mentioned above, the nRF52832, or even nRF52810/811, might be sufficient. We recommend starting the development of an nRF52840 DK, and then downscaling when you see what device is sufficient.
Hope this answers your question. Let me know if you have any more.
Kind regards,
Øyvind
Hello,
Is there any reason why the nRF52832 cannot be used instead?
The reason for why we have used the nRF52840 is because we want to support ZigBee and Thread (802.15.4) and all features of BT5 i.e. long-range on the nRF9160 DK. The nRF52840 also supports more peripherals and has a bigger flash (1 MB) for bigger code size.
For more information on the differences, please see the nRF52 Comparison table.
If your application does not need what I mentioned above, the nRF52832, or even nRF52810/811, might be sufficient. We recommend starting the development of an nRF52840 DK, and then downscaling when you see what device is sufficient.
Hope this answers your question. Let me know if you have any more.
Kind regards,
Øyvind
You're welcome!
-Øyvind