Peripheral devices / drivers support for Mesh SDK

RE: Peripheral devices / drivers support for Mesh SDK

Susheel Nuguru — Thu, 05 Apr 2018 09:47:33 GMT

really sorry for the late reply. Normally we would reply much faster, but due to easter holidays, we have very very thin staffing.

The link you sent is not an SDK, its just a demo done on the Nordic Playground on the Git repo. Anyone can create repos there.

The official repos are at https://github.com/NordicSemiconductor

Once again , sorry for the late reply

RE: Peripheral devices / drivers support for Mesh SDK

aafanasj — Wed, 04 Apr 2018 22:14:54 GMT

My question was clear enough.

I am playing with T52 Mesh Demo. And have not found peripheral asked for in Mesh SDK incorporated to Mesh Demo. This is why my questions were raised.

I saw the link provided by leonwj before... and asked about official release to get both - baseline + Mesh working.

Thank you for answer. Will take a look.

Regards,

Alexander A.

RE: Peripheral devices / drivers support for Mesh SDK

aafanasj — Wed, 04 Apr 2018 22:03:55 GMT

Thank you.

RE: Peripheral devices / drivers support for Mesh SDK

leonwj — Wed, 04 Apr 2018 20:10:41 GMT

ok, not a Nordic employee... but, the simple task of reading will go a long way to helping you progress things along!

In the github repository that you linked to, it clearly states the following in the Running the demo section...

2. Download Nordic nRF5 SDK for Mesh v1.0.1 and extract it under Thingy:52 SDK, rename the directory from "nrf5_SDK_for_Mesh_v1.0.1_src" to "mesh_sdk".

So from this you should clearly be aware that there's a single Nordic Mesh SDK located here, which the Thingy-52 mesh demo brings into its build path to obtain mesh functionality.

In terms of UART etc. functionality merged with Mesh, I did a quick search of the forum and the following link which should be relevant to your needs is clearly available.

If you are looking to specifically to bring sensors/actuators into a compliant Mesh solution, then you really should be looking at the Bluetooth SIGs Mesh Model Specification v1.0. This will ensure that any end solution you build is interoperable with other mesh stacks. (Since you are looking at other Mesh stacks, it appears that this might be important to you). (caveat: Since these (Model profiles) are optional features within the Mesh spec, I do not believe that they have currently been implemented in the Nordic stack, but should be on their roadmap - my recommendation is for you to reach out to your Nordic reps for additional insight into things)

Finally, as you are aware, Bluetooth Mesh is an infant technology so i'm sure that even within the Nordic Mesh there will be some changes in how the underlying Mesh stack is implemented. My suggestion would be to try to adhere to the SIG profiles as best as you can in order to insulate your solution from any stack changes. This will be important regardless of which mesh stack you choose to implement.

Regards,

RE: Peripheral devices / drivers support for Mesh SDK

natersoz — Wed, 04 Apr 2018 17:59:59 GMT

I will go out on a limb here:

The reason you are not getting a reply is that your questions are too broad to supply a proper answer.

If you are working with SDK-15, the peripheral device drivers (ADC, SPI, Timers, RTC, ...) are all in the directory

./modules/nrfx/drivers/...

In SDK 14 they can be found here:

components/drivers_nrf

There are plenty of examples (nice job Nordic), and if you need to dig deeper the Product Specification provides good coverage of the register usage: http://infocenter.nordicsemi.com/index.jsp?topic=%2Fcom.nordic.infocenter.nrf52%2Fdita%2Fnrf52%2Fchips%2Fnrf52840_ps.html

The Softdevice Specification provides a description of the constraints placed on the peripherals when BLE is active.

http://infocenter.nordicsemi.com/index.jsp?topic=%2Fcom.nordic.infocenter.s132.sds%2Fdita%2Fsoftdevices%2Fs130%2Fs130sds.html

Additional constraints and modifications are required for mesh:

http://infocenter.nordicsemi.com/index.jsp?topic=%2Fcom.nordic.infocenter.s132.sds%2Fdita%2Fsoftdevices%2Fs130%2Fs130sds.html

So, the answers are all there. What more could you ask for?

RE: Peripheral devices / drivers support for Mesh SDK

aafanasj — Wed, 04 Apr 2018 16:14:11 GMT

Hello support team,

No reply for a weeks.... Good support?

Looking at SiLabs solution in parallel.

Thanks,

Alexander A.

RE: Peripheral devices / drivers support for Mesh SDK

aafanasj — Wed, 28 Mar 2018 19:37:08 GMT

Hello support team,

May I ask you to answer to the questions raised?

We would like to go forward with BLE Mesh platform to be choosen.

Thanks,

Alexander A.

RE: Peripheral devices / drivers support for Mesh SDK

aafanasj — Mon, 26 Mar 2018 04:21:15 GMT

Hello support team,

May I ask you to answer to the questions raised?

We would like to go forward with BLE Mesh platform to be choosen.

Thanks,

Alexander A.

RE: Peripheral devices / drivers support for Mesh SDK

aafanasj — Thu, 22 Mar 2018 13:34:55 GMT

Hello Aryan,

I am talking about Mesh Demo - https://github.com/NordicPlayground/Nordic-Thingy52-mesh-demo

Is it not SDK?

Regards,

Alexander A.

RE: Peripheral devices / drivers support for Mesh SDK

Susheel Nuguru — Thu, 22 Mar 2018 11:14:57 GMT

I am very confused when you say Thingy52 Mesh SDK. What is this SDK? I do not think we have any Thingy Specific Mesh SDK