Sudden kernel panics and power instability on FireBeetle 2 ESP32-P4 when running AI vision scripts

Hi everyone,

I’ve been experimenting with the new FireBeetle 2 ESP32-P4 for an edge AI project, and while the MIPI CSI support is a huge step up, I’ve hit a technical wall regarding power stability and process isolation that I’m hoping the community can help with.

I’ve noticed that whenever the board is under heavy load—specifically when I’m running real-time image recognition scripts while simultaneously testing how a mobile visit this site executor interacts with my local IoT gateway—the ESP32-P4 triggers a "Cache Disabled" error or a full kernel panic. The most frustrating part is that the power LED remains green, but the serial monitor just spits out register dumps before hanging. While discussing this with a few other makers, it seems like the high-concurrency requests from my background automation might be causing transient voltage drops that the on-board regulator isn't catching fast enough.

Has anyone else noticed their AIoT projects hitting silent reboots or experiencing I2C bus hangs when the system is working hard on multitasking? I’m seeing occasional "Task watchdog got triggered" warnings in my logs that only seem to happen during these intensive sessions, which makes me think the CPU is struggling to balance the vision processing threads alongside my other background processes.

I’m trying to figure out if there’s a way to make the power delivery more resilient—perhaps by adding a specific capacitor across the 3.3V rail or if I should look into a more aggressive task-priority configuration in the ESP-IDF to ensure the kernel remains fluid even in "noisy" multitasking situations. If you’ve found a way to stabilize your FireBeetle workflow while pushing the hardware to its limits, I’d really value your advice!

Best regards!