Not currently as far as I am aware
Okay that clears it. That’s why the IOMCU on 2.4.8 bricks
Just popping back again to ask what IOMCU firmware I’m running. Since you told there is no target for a Pixhawk1 with a F103 iomcu for bdshot, does that also mean it’s somehow running an older version of the firmware otherwise? Not that I’m having any issues, I’m just curious.
This is what is displayed in the messages tab:
iomcu: 0 0 411FC231
That’s very unusual - I guess it could be a clone
I have a real Clone of a 2.4.6 (1Mb), one of the “originals” from Hobby King from way back in the day:
IOMCU: 420 1001 411FC231
Is it possible to do something like a force io fw update?
Well yeah it’s a clone considering the 2.4.8 is a generic FC. Anyway I did a Google search on that and saw this one result too. Check his logs, he has the same IOMCU log
Power on while pressing the safety switch
Not that it matters but the 2.4.8’s are not clones as there was never an official one to clone from. It’s a component cost reduced version of the 2.4.6 relabeled as a 2.4.8 so it sounds like a upgrade.
Did all 2.4.8s use F103? Or did the early ones use F100? By the way my 2.4.8 has the MS5611 baro
Oh okay, I have done this multiple times to recover from the soft-bricked state caused by the dshot fw update without realising that it also updated the bootloader. So I guess the Message log will show 0 0 only
Is this the F100 or F103?
I don’t know that any of them did. But one from the 2017 vintage was F100
I don’t know. It’s a bencher I connect on occasion for one reason or another. I would not use it in any model. Open yours up and check.
OK, opened up this one I have and it’s a F100 also.
Mine is definitely F103. I have checked.
So my question is is the arducopter firmware working with both 100 and 103?
You would need to do a specific firmware to support 103
You mean the bdshot part right? Everything else works fine. The “0 0” message is the curious thing