Holybro Kakute H7 V2: Config Error: INS: unable to initialise driver

Hi folks,
I have a new Holybro Kakute H7 V2. Flashed Copter 4.2.3 initially with STM32CubeProgrammer, and I’m getting following error:

17.10.2022 01:07:33 : Config Error: fix problem then reboot
17.10.2022 01:07:30 : Config Error: INS: unable to initialise driver
17.10.2022 01:07:30 : INS: unable to initialise driver
17.10.2022 01:07:30 : Barometer 1 calibration complete
17.10.2022 01:07:30 : Frame: QUAD/BF_X
17.10.2022 01:07:30 : RCOut: Initialising
17.10.2022 01:07:30 : KakuteH7 001F0039 31315101 34313931
17.10.2022 01:07:30 : ChibiOS: 38022f4f
17.10.2022 01:07:30 : ArduCopter V4.2.3 (a480c0a7)
17.10.2022 01:07:30 : Frame: QUAD/BF_X
17.10.2022 01:07:30 : RCOut: Initialising
17.10.2022 01:07:30 : KakuteH7 001F0039 31315101 34313931
17.10.2022 01:07:30 : ChibiOS: 38022f4f
17.10.2022 01:07:30 : ArduCopter V4.2.3 (a480c0a7)
17.10.2022 01:07:30 : Frame: QUAD/BF_X
17.10.2022 01:07:30 : RCOut: Initialising
17.10.2022 01:07:30 : KakuteH7 001F0039 31315101 34313931
17.10.2022 01:07:30 : ChibiOS: 38022f4f
17.10.2022 01:07:30 : ArduCopter V4.2.3 (a480c0a7)
17.10.2022 01:07:29 : Calibrating barometer

Already checked other solutions on this topic (like powering from battery etc.), but can’t get it to work. Also, the BRD_TYPE parameter is missing.
Any help very welcome.

edit: found following statement on Holybro’s website:

Ardupilot Target : KakuteH7v2 (Latest/Master firmware , support will be added in Ardupilot 4.3)

…is this the reason?

Probably. Download the .apj file from here and use the “load custom firmware” option in Mission Planner now that you have a version of Ardupilot on the board.
Kakute H7 v2

…it works! Thank you very much Sir!
Forgot to check the /latest directory…

One thing to mention, had to change the firmware before uploading the v2 version because MP told me that 4.2.3 is already on board, and I choose 4.3 beta 3. With that, I got following:

17.10.2022 03:00:46 : Config Error: Baro: unable to initialise driver
17.10.2022 03:00:46 : Config Error: fix problem then reboot
17.10.2022 03:00:43 : motors not allocated
17.10.2022 03:00:43 : RCOut: Initialising
17.10.2022 03:00:43 : KakuteH7v2 001F0039 31315101 34313931
17.10.2022 03:00:43 : ChibiOS: 75a01029
17.10.2022 03:00:43 : ArduCopter V4.3.0-beta3 (553af395)
17.10.2022 03:00:43 : motors not allocated
17.10.2022 03:00:43 : RCOut: Initialising
17.10.2022 03:00:43 : KakuteH7v2 001F0039 31315101 34313931
17.10.2022 03:00:43 : ChibiOS: 75a01029
17.10.2022 03:00:43 : ArduCopter V4.3.0-beta3 (553af395)
17.10.2022 03:00:42 : motors not allocated
17.10.2022 03:00:42 : RCOut: Initialising
17.10.2022 03:00:42 : KakuteH7v2 001F0039 31315101 34313931
17.10.2022 03:00:42 : ChibiOS: 75a01029
17.10.2022 03:00:42 : ArduCopter V4.3.0-beta3 (553af395)

Maybe this could help for developing.

OK, I see firmware for that board is in the latest beta. A better choice than master (4.4.0-dev) at this point I think.

Why better choice? Latest beta 4.3 doesn’t work, the one I flashed from /latest (4.4.0-dev) does.

Ah, I thought you were saying that beta 3 did work. Never mind then, it doesn’t matter if the Dev version has untested features if it’s the only one that works currently for that board. Carry on.

The beta should work and its a problem if it doesn’t. It’s possible this is a power issue - I have seen this with some baros. I will try on the board I have here. If it is genuinely fixed in 4.4 then I know which change is responsible.

1 Like

I cannot reproduce this on beta3 - works fine. Can you try fully erasing the board first?

As I have my equipment in an other apartment, I will do it next weekend and report.

Ok, I can confirm that 4.3.0 beta3 works fine when doing full chip erase before.

1 Like