I am having great difficulty with zephyr. In particular I cannot build an application with any kind of random number generator in it. However, this is just a special case of a larger problem. In the connect sdk are a plethora of samples but, apparently there is no curator's guide as to what each one is. It seems that one must open the main.c, if it exists, associated with each sample and try figure out what it does It's like being given an Encyclopedia Britannica with the Table of Contents and Subject Index removed. There must be a better way.
I am using VSCODE with the SDK Connect Extensions along with the associated toolchain. I cannot figure out, starting from scratch, how to set up a new project (application in Nordic parlance). I need a simple step by step guide about how to do that. There are several tutorials/guides on Nordic's website that claim to do that, but they all leave out crucial steps.
A VSCODE SDK Connect project has several files associated with it; I have no idea what these files are for or how they are set up. I need a hitchhiker's guide to the structure of these projects. There are, on here, documents that claim to do that, but, in fact, they do not. They appear to have been written by those with expert knowledge because they explain things using esoteric terms and very abstract language. I'm sure they all make perfect sense to those who know how things work, but to a novice, like me, they are just meaningless word salads, gibberish.
Getting back to Zephyr, I need a guide to the libraries, apparently the standard library naming conventions were not good enough for the developers so the names and locations have all changed; <stdio.h> is now somewhere else.
I have developed software for several different manufacturer's microcontrollers; STM, TI, Arduino, Raspberry Pi, and others all under VSCODE . They all use a toolchain very similar to yours, There are quirks and peculiarities associated with all of these manufacturers software, but nothing serious, no show stoppers, I could read and mostly understand their documentation; that is not the case for Nordic's. When something goes wrong, and there is always something going wrong, I am helpless, I can't experiment, I can't find the relevant documentation and probably couldn't understand it even if I could.
Will one of you kind souls can help me.
