"Config error - fix and reboot" on Matek F405 wing (new board)

ArduPlane Plane 4.1
1

Hi all,

I hope to have some advice about how to solve the configuration problem on Matek F405 wing board.

Steps followed :
connected the board to usb ( board new, no pins and no battery cables installed)
flashed Ardupilot firmware with stable version;
in Mission Planner installed Arduplane 4.1.0
executed acc. calibration with success.
disconnected the board
Installed the battery cables
connected to Mission Planner
following message appears “Conf error: fix problem and reboot”.

I flashed and reinstalled all many times without success.

Any idea ?
Thanks
Corrado

2

It should give more information that this. Can you attach a telemetry
log?

I’ve tried to replicate here but haven’t been able to. A copy of your
parameters might be useful.

My goess is that you’re running out of memory during initialisation.
We’ve just merged a patch to master which differentiates allocation errors
from configuration errors, so flashing master might give a little more
information.

3

HI peterbarker,
thank you for your reply.

Unfortunately I had no log, given that the problem didn’t allow to proceed with the configuration,unless it saved some data in a file that I don’t know where is placed.

Nevertheless , i tried to connect the board again, in order to find out something else to share for a better evalution of the problem, and I came to an apparent solution that I hope could find an explanation. I forgot to mention that I installed the oled (but NOT ENABLED in Mission Planner, although it was an oled that worked without problem on another F405 Wing board with INAV installed) and I was continuosly flashing and installing without taking care of it, it was always attached. The error persisted.

Incidentally I detached it from the board for making another attempt, just because it was bothering, and the board connected without problem.

Then I tried to connect again with the same oled installed and the error appeared again.
So a first conclusion was that the error was due to the oled.

I changed the oled with another that is installed on another Matek F405 wing ( with Arduplane installed) and that i know is working . With this oled there is no error, whether the oled is enabled or not

So my second ,trivial , conclusion is that the first oled is faulty.

I wonder if the oled alone can be the cause of unsuccesful configuration, mainly in the early phases when I can’t save anything that can help in debugging.

Sorry for this long reply, but I wanted to report all the actions i made in order to give you an alternative to the log for evaluating better the problem.

Now i will proceed with the configuration in order to see if everything is ok.

Corrado

1 Like
4

Unfortunately I had no log, given that the problem didn¢t allow to proceed with the configuration,unless it saved some data in a file that I don¢t know where is placed.

I’m not sure how MissionPlanner works in this regard - but telemtry logs
should be available regardless of whether the autopilot drops you out into
the “config error loop”. Certainly MAVProxy will give you one :slight_smile:

So my second ,trivial , conclusion is that the first oled is faulty.

Are the OLEDs of the same type? We support two different “notify
displays”.

I’ll dig one out and connect it to see if I can reproduce.

Now i will proceed with the configuration in order to see if everything is ok.

Glad you got past this problem :slight_smile:

Corrado

Yours,

5

I re-installed the oled that creates the problem, in order to see if MissionPlanner writes out some file but I don’t see anything in the folder.

But this is what I read in the Messages windows, below the hud:
“Config error: Baro: unable to initialise driver
Config Error: fix problem then reboot”

The oled I used don’t seem to be different and I configure as NTF_DISPLAY_TYPE=1.
The upper one in the picture is the faulty one.

Corrado

oled
oled1920×3416 280 KB

6

I’m getting this problem with a Matek F405-miniTE board. It formerly ran AC 4.1.7, but 4.2.x fails. I get an endless string of config errors, and it never gets far enough to show any sensor feedback.

Here’s what the messages look like:

7/18/2022 3:57:22 PM : Config Error: fix problem then reboot
7/18/2022 3:57:21 PM : Config Error: Baro: unable to initialise driver
7/18/2022 3:57:17 PM : Config Error: fix problem then reboot
7/18/2022 3:57:16 PM : Config Error: Baro: unable to initialise driver
7/18/2022 3:57:12 PM : Config Error: fix problem then reboot
7/18/2022 3:57:11 PM : Config Error: Baro: unable to initialise driver
7/18/2022 3:57:07 PM : Config Error: fix problem then reboot
7/18/2022 3:57:06 PM : Config Error: Baro: unable to initialise driver
7/18/2022 3:57:02 PM : Config Error: fix problem then reboot
7/18/2022 3:57:01 PM : Config Error: Baro: unable to initialise driver
7/18/2022 3:56:57 PM : Config Error: fix problem then reboot
7/18/2022 3:56:56 PM : Config Error: Baro: unable to initialise driver
7/18/2022 3:56:55 PM : motors not allocated
7/18/2022 3:56:55 PM : RCOut: Initialising
7/18/2022 3:56:55 PM : MatekF405-TE 004D0027 58535014 20393658
7/18/2022 3:56:55 PM : ChibiOS: 93e6e03d
7/18/2022 3:56:55 PM : ArduCopter V4.2.2 (4fcfa4b2)
7/18/2022 3:56:55 PM : motors not allocated
7/18/2022 3:56:55 PM : RCOut: Initialising
7/18/2022 3:56:55 PM : MatekF405-TE 004D0027 58535014 20393658
7/18/2022 3:56:55 PM : ChibiOS: 93e6e03d
7/18/2022 3:56:55 PM : ArduCopter V4.2.2 (4fcfa4b2)
7/18/2022 3:56:54 PM : motors not allocated
7/18/2022 3:56:54 PM : RCOut: Initialising
7/18/2022 3:56:54 PM : MatekF405-TE 004D0027 58535014 20393658
7/18/2022 3:56:54 PM : ChibiOS: 93e6e03d
7/18/2022 3:56:54 PM : ArduCopter V4.2.2 (4fcfa4b2)

EDIT: I think I mis-spoke regarding previous FW, as it seems that 4.2.0 was the first for this board. However, I had this board flying in a quad a few months ago, but now in a new quad, it won’t boot.

7

I’m using old version of F405 Wing updated to Arduplane 4.2.2 and I have no such problems, therefore I cannot be of great help. If you have installed an oled as I had, what i can suggest is to disconnect it and reboot again to see if it can be the problem.

Corrado

8

I ve got this error message with a matek f405 wing fc: Config error: Baro: unable to calibrate…and the board stucked in initialising.
Finally i figured out it caused a bad noname sd card in the fc slot for logging. Without that sd or with an other good sd card everything worked fine again…strange