Hello Markus, thank you very much for your videos. Your calm way of explaining the meaning of certain instructions and how to use them works perfect for me. I am interested in BLE Firmware Over The Air (FOTA). Could you please make a video on that subject, based on a simple peripheral?
Such a great hands on video.could you please explain the I2C code in zephyr in this that would be more helpful and much appreciated. Keep up the great work.
Hi Markus, great video (very explanatory). You mentioned (@10:30) that for the 'gpio_add_callback' you can add multiple call back functions... is this done by adding further 'gpio_add_callback' statements to the same port? Please can you expand your explanation?
Hi, with gpio_init_callback you just initialize a gpio_callback structure (cb-function, pinnr) . With gpio_add_callback you add this structure associated with the GPIO-port (driver) in this case GPIO0. For another button on the same port you can add another gpio_callback structure. To activate the specific interrupt and pin you call than gpio_pin_interrupt_configure_dt which is actually the same as gpio_pin_interrupt_configure(port, pin, flags).
Hey, could you do a video on the nRF RTC in v2.4.2? The documentation around it is a little unclear for configuration. Thanks for all the work you've put into these videos!!
The pins are labeled on the DevKit. Hardewarefiles like the Schematics you find under Downloads at the Webpage from the DevKit (www.nordicsemi.com/Products/Development-hardware/nRF52840-DK)
Unfortunately there is no video as I don't have the nRF5340-DK. I'll probably skip the nRF5340 as I'm more interested in the nRF54, which should be available around the beginning of next year.
I can understand and enjoy a tool that generates a device configuration/init C file for GPIO init but let me be and to hell with proprietary tools that are added to the build chain and make some "magic" that no one can reuse later outside this steaming pile of unique framework.
