How lora-net/swdm031_img_xfer works
This Zephyr demo runs in two compile-time roles: an initiator sends a 42-frame monochrome image over FLRP-BURST, while a slave listens, receives it, and renders it on the OLED. The main loop handles startup, button-driven and periodic transfer control; the transfer module owns FLRP operations and receive-side reporting, and the display module provides queued text and image output. Relationships for role behavior and image rendering are documented in the README; source excerpts show main-loop calls and display behavior, but not all FLRP callback wiring.
Main entry points: main.c Role main loop · app_flrp_img_xfer.c FLRP transfer · oled_display.c Display service · image_chick_looking.c Image frames
Components 8
Application control
- Role main loop
src/main.c
Image transfer
- FLRP transfer
src/common/app_flrp_img_xfer.c - Image frames
src/image_data/image_chick_looking.c
OLED presentation
- Display service
src/oled_display/oled_display.c - Startup logo
src/oled_display/lora_logo.c
Other components
- User
- Peer device
- OLED hardware
Connections 8
- User → Role main loop: presses button
src/main.c - Role main loop → FLRP transfer: starts transfer
src/main.c - Role main loop → Display service: updates display
src/main.c - Role main loop → Startup logo: animates logo
src/main.c - Image frames → FLRP transfer: provides payload
README.md - FLRP transfer → Peer device: transfers image
README.md - FLRP transfer → Display service: delivers received image
README.md - Display service → OLED hardware: renders frames
src/oled_display/oled_display.c