31f3f91801
rd03e.c: RD03E_FRAME_LEN was 5 but the frame's own documented layout (header + gesture + distance_lo + distance_hi + footer[2]) is 6 bytes. The footer check read buf[i+3], colliding with the distance high byte at that same index — so every frame that validated at all was forced to have distance_cm = lo | 0x5500 (~218m) regardless of what the sensor reported. Distance readings were garbage 100% of the time, not intermittently. mems_mic.c: i2s_del_channel() was missing on 2 of 3 init failure paths, leaking the channel handle. bmp280.c: the I2C bus/device handles leaked on 4 of 5 init failure paths; added a fail label that releases both. app_main.c: sensors now init before Wi-Fi bring-up, matching the rationale sensor_driver.h already documents (a hanging sensor bus must not be able to block network bring-up). rtlsdr_experimental.c: rtlsdr_exp_stop() waited 500ms before usb_host_uninstall(), but the daemon task blocks up to 1000ms inside usb_host_lib_handle_events() before re-checking its running flag — the delay must exceed that or teardown races a live daemon task. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
55 lines
2.2 KiB
C
55 lines
2.2 KiB
C
// Quantumancy ESP32-P4 Sensor Node — entry point.
|
|
//
|
|
// UNVERIFIED AGAINST REAL HARDWARE. Nobody working on this workstream has a
|
|
// physical ESP32-P4 (or the BMP280 / RD-03E modules) to flash and test
|
|
// against. This firmware is real, structurally-sound ESP-IDF C, reasoned
|
|
// about carefully against ESP-IDF's documented APIs and the public
|
|
// datasheets/protocol docs for each sensor -- but "compiles and reads
|
|
// correctly" is where the verification stops. See README.md's "What's
|
|
// verified vs. not" section before treating any of this as field-tested.
|
|
//
|
|
// Boot sequence: initialize every registered sensor driver first (so a
|
|
// slow/hanging sensor bus can't block network bring-up -- see
|
|
// sensor_driver.h), then bring up Wi-Fi station mode (device_config.h
|
|
// credentials), wait (briefly, non-fatally) for an initial connection, and
|
|
// hand off to the telemetry task, which periodically samples the sensor
|
|
// registry and POSTs the results to the backend. Wi-Fi reconnection and
|
|
// per-cycle "are we online" checks happen independently after this, so a
|
|
// boot-time Wi-Fi hiccup doesn't wedge the device -- it just starts
|
|
// reporting once the connection comes up.
|
|
|
|
#include "wifi_manager.h"
|
|
#include "sensor_registry.h"
|
|
#include "telemetry_client.h"
|
|
#include "esp_err.h"
|
|
#include "esp_log.h"
|
|
#include "freertos/FreeRTOS.h"
|
|
#include "freertos/task.h"
|
|
|
|
static const char *TAG = "app_main";
|
|
|
|
// How long to wait at boot for the first Wi-Fi connection before giving up
|
|
// on blocking and handing off to the telemetry task anyway (which will
|
|
// simply skip cycles until wifi_manager's own retry logic connects).
|
|
#define BOOT_WIFI_WAIT_MS 20000
|
|
|
|
void app_main(void) {
|
|
ESP_LOGI(TAG, "Quantumancy sensor node starting");
|
|
|
|
sensor_registry_init_all();
|
|
|
|
ESP_ERROR_CHECK(wifi_manager_start());
|
|
|
|
esp_err_t err = wifi_manager_wait_connected(pdMS_TO_TICKS(BOOT_WIFI_WAIT_MS));
|
|
if (err == ESP_OK) {
|
|
ESP_LOGI(TAG, "Wi-Fi connected at boot");
|
|
} else {
|
|
ESP_LOGW(TAG, "Wi-Fi not connected within %d ms at boot -- continuing anyway, "
|
|
"wifi_manager will keep retrying in the background", BOOT_WIFI_WAIT_MS);
|
|
}
|
|
|
|
telemetry_client_start_task();
|
|
|
|
ESP_LOGI(TAG, "startup complete, telemetry task running");
|
|
}
|