Cause: Improper PLL configuration, or missing external clock.
Solution: In system_stm32f4xx.c, set PLL_M and PLL_N for 168MHz operation. Also ensure proper decoupling on VDD.
Project: LA104 Digital Oscilloscope / Logic Analyzer Focus: Custom Firmware Development & Hardware Unlocking Status: Ongoing Community Development
Most serious LA104 firmware work happens in the community space.
With custom firmware leveraging the PIC32’s GPIO bit-banging, you can implement a simple CMSIS-DAP v1 adapter. This allows you to debug ARM Cortex-M microcontrollers using OpenOCD.
The LA104 is powered by an STM32F407VG (Cortex-M4 with FPU). The stock firmware uses a custom UI and a proprietary PC client. But the open-source community (especially the DSLogic and libsigrok folks) has done incredible work reverse-engineering and rebuilding the firmware from scratch.
The two main firmware paths I explored were:
Cause: Improper PLL configuration, or missing external clock.
Solution: In system_stm32f4xx.c, set PLL_M and PLL_N for 168MHz operation. Also ensure proper decoupling on VDD.
Project: LA104 Digital Oscilloscope / Logic Analyzer Focus: Custom Firmware Development & Hardware Unlocking Status: Ongoing Community Development la104 firmware work
Most serious LA104 firmware work happens in the community space. Cause : Improper PLL configuration, or missing external
With custom firmware leveraging the PIC32’s GPIO bit-banging, you can implement a simple CMSIS-DAP v1 adapter. This allows you to debug ARM Cortex-M microcontrollers using OpenOCD. Most serious LA104 firmware work happens in the
The LA104 is powered by an STM32F407VG (Cortex-M4 with FPU). The stock firmware uses a custom UI and a proprietary PC client. But the open-source community (especially the DSLogic and libsigrok folks) has done incredible work reverse-engineering and rebuilding the firmware from scratch.
The two main firmware paths I explored were:
