This week, I focused on understanding how we can transition our STM32 firmware from development hardware to the much smaller hardware required for the final wearable. As part of this work, we disassembled a commercially available headphone and examined how its internal electronics were packaged and accessed. This gave us a useful reference for compact wiring and connections, while also helping us consider how we can maintain access for firmware testing and debugging once the electronics are integrated into the mask.
One specific issue I investigated was how we will flash and debug the STM32 without the built-in programming interface provided by a development board. Based on our research, we decided to use an ST-Link through the STM32’s SWD interface. Our current plan is to expose the necessary programming and debugging connections using individual wires or small programming pads. During development, these connections will allow us to upload firmware, inspect program execution, and diagnose issues. The temporary wires can later be cut or removed once the firmware has been tested and the final device has been programmed.
I also continued considering the firmware and RTOS requirements for running the audio processing on the wearable. This includes planning how audio acquisition, processing, and output should be coordinated, and how task timing, buffering, and memory usage could affect the feedback loop. As we move toward implementation, maintaining reliable debugging access will help us evaluate these constraints on the final hardware. Over the next week, I plan to refine the programming and wiring approach and continue developing the firmware structure, with particular attention to RTOS task organization and meeting the timing requirements of the audio processing.