Zephyr 101 - Learn the basics to get your first build

## Relevant links

Let me know what you think in the comments. Thanks 🙏

[JG-mzhg]

Yeah, that Zephyr dev environment setup is really a pain. I packed everything into a self-contained Docker container and I can only recommend this :)

[apaskiewicz]

Thank you for sharing your knowledge with us. I really appreciate it.

[aslan-mehmet]

I just want to add zephry as submodule how do I do that?

[illy_og]

Is there somehow a tutorial to port boards? It's somehow very difficult to do that without any experience

[CuriousMaker]

Is that a CNC milling machine over your right shoulder? Sorry I got distracted.

[junaidaslam]

Hi... One suggestion. Can you please make a video about stepwise debugging with Zephyr?

[junaidaslam]

Have you also prepared a stepwise guide into "How to support a new SoC based on an existing supported architecture like Cortex-m etc"?

Or if you can guide me to such a resource, it will be very nice.

[junaidaslam]

Hi, one more question...

Do we manually append vector table entries in .s file with ISR symbols if CONFIG_GEN_ISR_TABLES=n in Kconfig file? I saw that by default __vector_relay_handler is called for every interrupt and then appropriate call is made based on an initialized _vector_table array of pointers....

This whole initialization of vector table is quite confusing because for CPU exceptions its has a well defined vector entries and for the rest of them it is initialized using the python script... Also, i could not find any source code sequence which could lead me to appropriate files to peek into the whole thing..

If i am correct, then apart from CPU interrupts, only those interrupts are made part of the vector table which are explicitly registered using calls like RQ_CONNECT() etc...

Am i correct?

[ffgg-zvgg]

I can't setup the environment. I want to work on nrf52840dk.