I flashed with firmware and got it to connect but then Config Error: Baro: unable to initialise driver. Saw some change buzz to on but didn’t work
What can it be?
The wrong firmware maybe. You would not be the 1st. What exact board is it and post a screen shot from the messages screen in Mission planner after connecting that shows which firmware.
How about answering the questions I asked?
do you spot any issue?
No, because that screen shot is not the messages screen. Then go to the HW ID screen and post a screen shot of that.
And you were showing the Plane Firmware page and Rover is installed.
I wanted to just try FC in rover first, downloaded .hex file with rover now, get same problem and view
You seem to have a problem following simple instruction. Good luck.
1 Like
Sorry totally new to this doing as best I can. where can I find HW ID?
So, you have a Speedybee F405-Wing?
Post a screenshot of the MP Messages screen after you connect where it shows the firmware version. Like this:
HW ID screen:
No, the 1st picture is the Messages Screen. Can you not just do what is asked?
The HW ID screen shows no hardware recognized.
Can you specify what speedybee do you have? Maybe post a picture…
Usually because the wrong firmware has been flashed. Yes, lets’s see a photo of the board you have.
1 Like
First try re-flashing Rover by downloading the .apj from here and using Mission Planners “load custom firmware” to flash it. Then see what shows up on the HW ID screen. If nothing I suppose the board is scrap.
SP F405-wing
Easy to recover.
Download and Install STM32 Cube Programmer.
https://www.st.com/en/development-tools/stm32cubeprog.html
Disconnect all peripherals except for the Wifi Adapter. You must not have anything connected to the GPS serial port. It sits on one of the USARTs that the factory bootloader probes.
Press the button on the Wifi adapter and plug in the USB in your computer.
Start STM32 Cube Programmer, connect via USB, clear the whole chip.
Upload the correct firmware file, I assume you want Rover.
https://firmware.ardupilot.org/Rover/stable/SpeedyBeeF405WING/ardurover_with_bl.hex
That’s it.
If the previous suggestion does not work, and to be sure that the board has a hardware issue, you can also install back some INAV version and check if the baro is working there. I had some issues with ADC pins which worked in INAV and did not work in ardupilot.