Flash mamba h743

ArduCopter Copter 4.2
1

I am trying to flash ArduCopter stable-4.2.3 MambaH743v4 firmware using STM32CubeProgrammer.
I get a error to reconnect with Read Unprotect enable.
How do I do that? Can you direct me on how to do that.
There is only a USB port.

Thanks

2

I recommend you do it the dfu way - Loading a bootloader with DFU — Dev documentation

3

I used:
MCU#1
Device: Mamba STM32H743
Status: Could not load bootloader FW

     MCU#2
     Device: Mamba STM32H743
     Status: Loaded bootloader FW but could not load latest FW Stable-4.2.3 (arducopter.hex)

     MCU#3
     Device: Matek STM32F765-SE
     Status: Total Success bootloader FW loaded, Stable-4.2.3 FW loaded, and connected to MP

sudo apt-get install dfu-util

MCU#1
Device: Mamba STM32H743
dfu-util --list
Found DFU: [0483:df11] ver=0200, devnum=21, cfg=1, intf=0, path=“1-2”, alt=1, name=“@Option Bytes /0x5200201C/01128 e", serial=“200364500000”
Found DFU: [0483:df11] ver=0200, devnum=21, cfg=1, intf=0, path=“1-2”, alt=0, name="@Internal Flash /0x08000000/16128Kg”, serial=“200364500000”
dfu-util -d 0483:df11 -a 0 --dfuse-address 0x08000000 -D MambaH743v4_bl.bin
Download [=========== ] 45% 7168 bytesdfu-util: dfuse_download: libusb_control_transfer returned -1
dfu-util -d 0483:df11 -a 0 --dfuse-address 0x08000000 -D MambaH743v4_bl.bin
Download [====== ] 26% 4096 bytesdfu-util: Error during download get_status
dfu-util -d 0483:df11 -a 0 --dfuse-address 0x08000000 -D MambaH743v4_bl.bin
Download [========= ] 39% 6144 bytesdfu-util: Error during download get_status
lsusb
Bus 001 Device 019: ID 0483:df11 STMicroelectronics STM Device in DFU Mode
Cannot load MambaH743v4_bl.bin using dfu-util command, INAV Configurator or Betaflight Configurator

MCU#2
Device: Mamba STM32H743
dfu-util --list
Found DFU: [0483:df11] ver=0200, devnum=11, cfg=1, intf=0, path=“1-2”, alt=1, name=“@Option Bytes /0x5200201C/01128 e", serial=“200364500000”
Found DFU: [0483:df11] ver=0200, devnum=11, cfg=1, intf=0, path=“1-2”, alt=0, name="@Internal Flash /0x08000000/16128Kg”, serial=“200364500000”
dfu-util -a 0 --dfuse-address 0x08000000 -D MambaH743v4_bl.bin
Downloading to address = 0x08000000, size = 15668
Download [=========================] 100% 15668 bytes
Download done.
File downloaded successfully
lsusb
Bus 001 Device 019: ID 0483:df11 STMicroelectronics STM Device in DFU Mode
Cannot load MambaH743v4 Stable-4.2.3 Firmware (arducopter.hex) using STMCubeProgrammer, INAV Configurator or Betaflight Configurator

MCU#3
Device: Matek STM32F765-SE
dfu-util --list
Found DFU: [0483:df11] ver=2200, devnum=24, cfg=1, intf=0, path=“1-2”, alt=3, name=“@Device Feature/0xFFFF0000/01004 e", serial=“207A357E3056”
Found DFU: [0483:df11] ver=2200, devnum=24, cfg=1, intf=0, path=“1-2”, alt=2, name="@OTP Memory /0x1FF0F000/01001Ke,01032 e", serial=“207A357E3056”
Found DFU: [0483:df11] ver=2200, devnum=24, cfg=1, intf=0, path=“1-2”, alt=1, name="@Option Bytes /0x1FFF0000/01032 e”, serial=“207A357E3056”
Found DFU: [0483:df11] ver=2200, devnum=24, cfg=1, intf=0, path=“1-2”, alt=0, name=“@Internal Flash /0x08000000/04032Kg,01128Kg,07*256Kg”, serial=“207A357E3056”
dfu-util -d 0483:df11 -a 0 --dfuse-address 0x08000000 -D MatekF765-SE_bl.bin
Download [=========================] 100%
Download done.
MatekF765-SE Stable-4.2.3 Firmware loaded using STMCubeProgrammer and connects to MissionPlanner
Success

4

What happens if you don’t specify -d 0483:df11? It should not be necessary

5

No change for MCU#1 or MCU#2.

For MCU#2, is there a proper command string in which to Download the stable fw using dfu-util since the bootloader fw is loaded?

6

Oh wait - once you have the bootloader on just use mission planner to upload the firmware

7

I have both MCU#1 and MCU#2 loaded with the bootloader but get I commnication error No connection
for ports /dev/ACM0 and /dev/serial/by-id/ardup…

8

You can’t connect with Mission Planner - only upload the firmware - is this what you tried?

9

Yes I only tried to do a firmware up load on both MCU#1 and MCU#2. No luck. I will try do use microsoft next.

10

Success! All MCU broads loaded with firmware 4.2.3. On MCU#1 and MCU#2 fw 4.3.2 was loaded by MissionPlanner using MicroSoft windows 10.

Thanks,
rpac

11

Just some closing notes, All MCUs bootloader fw were uploaded using linux Pop!_OS 22.04 LTS. MCU#1 and MCU#2 were the only devices that needed windows 10 for 4.3.2 fw . If you close off topics by posting as SOLVED, you may do so.