Programming guide for nrf5 SDK

[leonhart88]

I'm starting to read all the resources and examples included in the SDK. However, there doesn't seem to be a lot of emphasis on explaining how the programming architecture works (ie. event driven, task driven, or what).

A lot of the tutorials and examples simply show you how to compile and run one of the SDK examples. Is there any documentation that explains how one would create their own application entirely from scratch?

This would probably help in understanding the underlaying code in examples rather than just taking an example and adding on custom code.

[endnode]

In tutorial section of this forum there are 4 guides to Bluetooth Low Energy (in the middle of the page, starting with the advertisement explanation and exercises). I believe that's what you describe. By reading the code of these examples and following code snippets and exercises you should get glimps how Nordic BLE stack work and what "standard application architecture" is on top of that. If you decide to go with Nordic BLE stack (note that there are other options so that might be the reason why there is no authoritative guide to app's architecture = it depends on the radio stack) then you can see many sequence diagrams including basic flow charts of thread vs. interrupt driven event retrieval architectures on Infocenter. There are also several "project templates" in the nRF5 SDK which should be "the master architecture" example if you decide to go with nRF5 SDK and Nordic BLE stacks (Soft Device).

If anything missing could you be more specific? E.g. by linking some other examples from different embedded architectures and SDKs...

[endnode]

Oh and last one: you might find attempts to bring some higher level language to nRF5x like PuckJS (Java Script) or micropython if you really want to bypass low-level ANSI C libraries and related things. Unfortunately there is no magic out of the air so these systems might work well in basic use cases like advertising beacon or single GAP Peripheral connection link but when adding more and more concurrent things (wither BLE connections or wired interfaces) you will hit the limits. Basically no mass market product uses these, all stick to old fashion C + ASM mix done by senior developers...