BLE SIG mesh

RE: BLE SIG mesh

awneil — Wed, 04 Sep 2019 12:29:01 GMT

All Nordic's BLE devices are SoC - ie, MCU + Radio.

So, if that's not what you want, then you need to look elsewhere.

But, again, Serialisation allows you to use the SoC as little more than a "dumb" radio - with the "Host" doing most of the work.

RE: BLE SIG mesh

Pavankumar K — Wed, 04 Sep 2019 11:59:11 GMT

We need only BLE without MCU.. kindly advise..

RE: BLE SIG mesh

awneil — Wed, 04 Sep 2019 10:09:34 GMT

I've only used the Nordic SDK

As noted above, HCI is not in the Nordic SDK - so I have no idea.

The nRF52832 Dev Kit has a nRF52832-QFAA - and that can certainly run the Nordik BLE Mesh SDK examples...

I would always (not just for Nordic) recommend starting with the higher-memory part; once you have a solid feel for your actual memory requirements, then you will be in a position to evaluate whether a reduced-memory part is feasible ...

"Premature optimisation is a root of all kinds of evils"

RE: BLE SIG mesh

DD_connectivity — Wed, 04 Sep 2019 09:53:07 GMT

Hi Awneil,

So just to get clear idea on Hardware side, before finalizing a SoC.

nRF52832-QFAA is good enough in terms of capability and memory to run SIG MESH on it with HCI ?

Should we go for nRF52832-QFAA or nRF52832 QFAB is also fine ?

I hope i need not use nRF52840 to achieve this one since i have some cost concerns.

Do share your inputs.

RE: BLE SIG mesh

awneil — Wed, 04 Sep 2019 08:58:28 GMT

The nRF52 chips support BLE SIG Mesh at the radio level.

For HCI, see:

https://devzone.nordicsemi.com/f/nordic-q-a/30810/nrf52-hci-support/121826#121826

If you wanted to stick with the Nordic SDK, you could consider Serialisation:

https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.sdk5.v15.3.0/lib_serialization.html