So my Pixhawk 2.4.8 has a F103 IOMCU instead of F100. I was wondering if replacing the second last line from iofirmware_dshot_lowpolh.bin with iofirmware_f103_8MHz_dshot_lowpolh.bin will solve the issue ( ardupilot/Tools/IO_Firmware at master · ArduPilot/ardupilot · GitHub ).
@andyp1per I wrote the hwdef for the 2.4.8 using iofirmware_f103_dshot_lowpolh.bin and now I seem to be hot water after I tried flashing the dshot fw onto it. Now, firwmware erases doesn’t seem to rewrite the fw on the iomcu to the standard version. What can I do? I don’t have the safety switch with me now so can you tell me which two pins I have to short while restarting the FC to try booting it into bootloader mode?
Please think about throwing this old Pixhawk clone where it doesn’t create any harm…
Even if you get BDshot running, the old F4 MCU hasn’t enough processing power to do sophisticated rpm based notch filtering with several notches. (multi notch)
Yes, I know, but this is for a project and even this is sort of expensive by our standards. Please help in unbricking the iomcu or at the very least disabling it while the other stuff still works
It is now that you spent the money on it and should really replace it. This was one motivation for producing the hardware to avoid post. Did you spend ~$60 for that FC?