How thienan2050/bluetooth-low-energy-fundamentals works
Project type and purpose
• This is not a web‐app or microservice suite but a collection of embedded C firmware examples and solutions for a Bluetooth Low Energy (BLE) fundamentals course.
• It uses the Zephyr RTOS and the Nordic nRF Connect SDK to build BLE prototypes on Nordic Semiconductor hardware (nRF52, nRF53, nRF54 boards).
• Each “li/li_ej” directory is a standalone exercise (“ej”) or its solution (“_sol”), containing a CMake build description, Zephyr Kconfig, board overlays, a project config (prj.conf), a sample.yaml (for flashing/debugging), and a main.c (and sometimes additional modules like my_lbs.c/h).
File‐structure analysis
• Top‐level directories: l2, l3, l4, l5, l6 – correspond to “Level 2” through “Level 6” of the course.
• Under each level: “l?_eX” = exercise X; “l?_eX_sol” = solution.
• Common files per example:
• CMakeLists.txt – Zephyr/CMake build entry
• Kconfig.sysbuild (and sometimes Kconfig) – build‐time configuration
• boards/…conf & .overlay – hardware‐specific pin/radio settings
• prj.conf – Zephyr/BT stack runtime settings (e.g., advertisement interval, connection parameters)
• sample.yaml – nRF Connect tooling config for flashing & logging
• src/main.c (+ optional service modules like my_lbs.c/h) – application logic
• Some complex exercises (e.g., l3_e2, l6_e2, l4_e3) introduce multi-image builds for multi-core parts of the SoC (network core vs app core) and use rpmsg/HCI IPC, sysbuild, and child_image directories.
README insights
• The repo backs a self-paced BLE course.
• Goals: hands-on with BLE advertisement, connection, GATT services, security, packet sniffing.
• Uses Nordic hardware and Zephyr‐based nRF Connect SDK.
• Each exercise is meant to be built and run on two boards to form a unidirectional or bidirectional BLE link.
Final advice
• Be exhaustive but clear: break the system into Build, Firmware, Hardware, Wireless, Tools.
• Zephyr modules (Bluetooth Host/Controller) and any multi-core IPC.
• This level of detail will give course participants and maintainers a crystal‐clear view of how an example is built, deployed, and runs over BLE.