BDShot FW on IOMCU (F103) of newer Pixhawk 2.4.8 doesn't work

[EvansCesilThomas]

Bug report

Issue details

Setting BRD_IO_DSHOT on a Pixhawk 2.4.8 with F103 co-processor fails to load the dshot firmware onto it and soft-bricks (solid amber iomcu indicator, no ACT indicator, IOMCU unhealthy message)
Normally, the Messages tab shows iomcu: 0 0 411FC231
but when bricked, it shoes iomcu: 0 0 0

Version
4.6.2, 4.6.3
stock Pixhawk-bdshot

Platform
[ x ] Copter

Airframe type
Quad

Hardware type
Pixhawk 2.4.8

Logs
N/A

[Pratham-Saini2703]

@EvansCesilThomas i would like to work on this issue can you assign it to me . i read description of this isssue and i think that i can resolve it so , can you assign this issue to me i will resolve it as soon as possible.

[EvansCesilThomas]

I don't think this has to be assigned, nor am I an ardupilot maintainer, so no idea how exactly this is done. A developer told me that you need to make a firmware target for the F103 chip to support bdshot. So if you fix it, I think you may post about it in the forums and the developers can pitch in

[andyp1per]

It's not really a Pixhawk 2.4.8 though, is it right? It's a clone - it works on a genuine Pixhawk which uses F100. If you want to fix this you need to include the F103 dshot firmware in the hwdef, but you cannot to do this without breaking the original pixhawk (it's either or - F100 or F103 - not both, which means you need to create a new target

[EvansCesilThomas]

It is a 2.4.8. The original one was named Pixhawk1 or 2.4. But 2.4.8 refes to the generic FCs. I thought since it is still a popular (I think) board and most new 2.4.8's come with the F103 these days, it might be good if someone can fix this. Also what happens if you put the F103 bdshot fw on the Pixhawk1 FW? What breaks? Thanks