I received a new RadioLink Mini-Pix, and it booted nicely after unboxing. Then I decided to flash a newer ArduCopter build into it. With a Linux host, I however noticed that the bootloader thought the device was a ‘PX4Flow’.
So to get things lean, I booted the device into STM32 DFU mode and flashed in a stable AC 3.6.11 with bootloader (mini-pix build) using BetaFlight flasher, ticking ‘erase whole chip’ checkbox.
Now the Mini Pix does not boot past the bootloader, while rapidly flashing red light. I can, however, reflash with QGroundControl or Mission Planner a different firmware - I tried 4.0rc1 Copter, different Plane builds (to erase any settings) but the thing just won’t boot further. I also DFU-flashed recent ChibiOS bootloaders, even one that I built out of latest git. No success.
When I flash AC 4.0rc1, the device goes slightly past the bootloader (Linux dmesg indicates the device first as a mini-pix-BL, then as a mini-pix, disconnecting USB in between). However it hangs there immediately, with only power led on.
I also added an sdcard to get diagnostics. While booting, it does create the directory ‘APM’ for logging, but the directory remains empty.
I’ve handled the device carefully what comes to static electricity etc, but have I now actually bricked it? Could it be that due to that PXFlow strangeness, the STM32 is somehow retaining incorrect boot registers? How could I truly reset it?
Any hints appreciated.