Architecture¶

One source tree serves two chips and two RTOSes: 40 FreeRTOS applications under apps/ (37 for IPRO7 and IPRO7AI, 3 for IPRO6S), and a Zephyr v4.4.0 module for IPRO7. Both paths share the HAL, the SoC drivers and the prebuilt libraries. The build flow and memory layout are in Build System & Configuration.

System overview¶

Prebuilt libraries ship with their public headers and are linked automatically; nothing has to be configured to use them. Debug information is stripped but symbol names are kept, so map files and nm still work.

FreeRTOS and Zephyr¶

flowchart TB
  A["FreeRTOS applications in apps/"] -->|"make / build_freertos.sh"| C["bsp/hal · SoC drivers · prebuilt libraries"]
  B["zephyr/samples and Zephyr samples"] -->|"west build"| D["zephyr/drivers · zephyr/hal_glue"]
  D --> C

On the Reef, and for any product that needs low power, the camera, audio or the NPU, use the FreeRTOS path. Zephyr boards, samples and flashing are covered in Zephyr RTOS.

Components¶

All paths below are under components/.

How IPRO7 reaches a network, and the IPRO6S applications on the other end of the SDIO link, are in Networking.

Directory layout¶

IPRO-SDK-V2.2.1/
├── apps/                    FreeRTOS applications (40)
│   ├── ai/                  NPU and Edge AI applications
│   ├── bluetooth/ble/       BLE examples
│   ├── bluetooth/le_audio/  LE Audio headset
│   ├── multimedia/          USB webcam, JPEG decoding, PDM recording, cloud voice
│   ├── platform/            chip and board references, IPRO6S Wi-Fi; common/ holds shared OTA code
│   ├── test/                driver tests, hardware bring-up and benchmarks (19)
│   └── turnkey/common/      shared USB console code
├── bsp/                     HAL, SoC drivers (ipro7_soc, ipro6_soc), board configuration, linker scripts
├── components/              middleware and libraries
├── cmake/                   toolchain detection, build macros, autoconf.h generator
├── tools/                   serial_monitor.py, create_ota.py, teach_web/, zephyr/ scripts, bundled CMake, Android example app source
├── zephyr/                  Zephyr module: boards, soc, dts, drivers, samples, tests
├── build_freertos.sh        front end for FreeRTOS build, flash and monitor
├── project.build            build driver called by every application Makefile
├── west.yml                 Zephyr west manifest
├── CMakeLists.txt
├── Kconfig
└── VERSION.txt

Run ./build_freertos.sh -l for the full list of applications, or see Examples.

BLE stack¶

The host ships as source and runs on FreeRTOS through the ipro_bt_host/port/ layer; there is no UART HCI between the host and the controller. Three .config keys pick one of 16 IPRO7 controller archives to link. The IPRO6S Bluetooth controller is not part of this release; the IPRO6S applications are Wi-Fi only. Archive selection, bring-up order and API usage are in BLE Development.

BSP and drivers¶

Peripherals covered by the HAL:

Reef pin assignments, the speaker enable and similar definitions are in bsp/board/ipro7/ipro7ai_reef_board_config.h as BOARD_* macros; the board's pinout is on the IPRO7AI Reef EVK page and the chip's pin functions in Pinout & Peripheral Mapping.

Hands-on on the Reef¶

See the layers meet in the out-of-box firmware ipro7ai_reef_demo: its .config chooses the RTOS and components, its main.c calls the shared platform init and the board header, and the FreeRTOS shell shows the result at run time.

Next: build the same structure yourself in Create Your First Application, then check it with Test Your Application.

Related documents¶

• Build System & Configuration: build flow, .config, memory layout, new applications
• BLE Development: archive selection, bring-up order, GATT example
• Networking: Ethernet, lwIP, Wi-Fi through an IPRO6S over SDIO
• Zephyr RTOS: Zephyr boards, samples and flashing
• IPRO7AI Reef EVK: the board every example uses
• IPRO7, IPRO7AI, IPRO6S: chip specifications