DevEBox and WeAct Studio boards support request

[synersignart]

Feature request

DevEBox stm32H743 and stm32H750 with 25mhz crystal frequency

Issues is currently having difficulty building from the latest Ardupilot firmware not completing with memory errors
apart from which if it does build it could not connect

WeAct Studio stm32H743 with 25mhz crystal frequency

Id need help for this board as well into the supported List
nice to add dual imu feature

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Platform
[v ] All
[ v] AntennaTracker
[ v ] Copter
[ v ] Plane
[ v ] Rover
[v ] Submarine

Additional context

these are development board nice to have for users who wish to experiments and would be helpful with a sample hwdef in the list as a guide as a working flight controller

[aviralgarg05]

I would like to solve the issue. Please assign me the issue

[synersignart]

I would like to solve the issue. Please assign me the issue

the issue for the DevEbox H750 is building the firmware its self with the latest Ardupilot which seems to have memory issues
https://github.com/mcauser/MCUDEV_DEVEBOX_H7XX_M

the issue for the Weact studio H743 is connecting after flashing the custom firmware
https://github.com/WeActStudio/MiniSTM32H7xx

both require a clear documentation of building the basic firmware for ardupilot arducopter and arduplane

[miftahul-commits]

I tried to flash it with holybro pixhawk 6c firmware since it has around same number of pins, but it wouldn't even show up in device manager. So i used an arduino to convert the pc usb to stm32 uart PA14/15 and it now shows up in mission planner but can't connect with error "heartbeat packages not received" and "the string contains no elements. Now i will most likely try to build a firmware for this board.
Do you have any update or suggestions?

[synersignart]

I tried to flash it with holybro pixhawk 6c firmware since it has around same number of pins, but it wouldn't even show up in device manager. So i used an arduino to convert the pc usb to stm32 uart PA14/15 and it now shows up in mission planner but can't connect with error "heartbeat packages not received" and "the string contains no elements. Now i will most likely try to build a firmware for this board. Do you have any update or suggestions?

yes id like to get it working even with 6 UARTS and 10 PWM 4ADC out of it. also there is this Weact studio H743 which I cant seem to get it working base of the Matek H743 as the Weact Studio H743 uses 25mhz crystals .
and for the most part run off the current release of Ardupilot hwdef with features like lidar and opticalflow functioning .

[miftahul-commits]

1. does your WeActSTM32H7 connect to pc via usb after flashing with ardupilot? (Mine might turn out to be faulty, causing errors)
   does it shows up in ports anything other than stm32bootloader?
2. I edited the MatekH743 hwdef file to have only one SPI and one I2C (with pins specified in schematic pdf for them) but the result has not changed, can it be because of some board configuration issue?

hwdef.txt
hwdef-bl.txt

arduplane_with_bl(hex).txt

[miftahul-commits]

I tried to flash it with holybro pixhawk 6c firmware since it has around same number of pins, but it wouldn't even show up in device manager. So i used an arduino to convert the pc usb to stm32 uart PA14/15 and it now shows up in mission planner but can't connect with error "heartbeat packages not received" and "the string contains no elements. Now i will most likely try to build a firmware for this board. Do you have any update or suggestions?

yes id like to get it working even with 6 UARTS and 10 PWM 4ADC out of it. also there is this Weact studio H743 which I cant seem to get it working base of the Matek H743 as the Weact Studio H743 uses 25mhz crystals . and for the most part run off the current release of Ardupilot hwdef with features like lidar and opticalflow functioning .

I think it supports upto 3 ADC and 4 UART (and 4 USART) , at least in the CubeMX , the pwm might be possible but idk the rest

[synersignart]

1. does your WeActSTM32H7 connect to pc via usb after flashing with ardupilot? (Mine might turn out to be faulty, causing errors)
   does it shows up in ports anything other than stm32bootloader?

   2. I edited the MatekH743 hwdef file to have only one SPI and one I2C (with pins specified in schematic pdf for them) but the result has not changed, can it be because of some board configuration issue?

hwdef.txt hwdef-bl.txt

arduplane_with_bl(hex).txt

so far no luck getting to to communicate the mavlink , even use the boot file of Mronexus and MicoAirh743

[miftahul-commits]

1. does your WeActSTM32H7 connect to pc via usb after flashing with ardupilot? (Mine might turn out to be faulty, causing errors)
   does it shows up in ports anything other than stm32bootloader?

   2. I edited the MatekH743 hwdef file to have only one SPI and one I2C (with pins specified in schematic pdf for them) but the result has not changed, can it be because of some board configuration issue?

hwdef.txt hwdef-bl.txt
arduplane_with_bl(hex).txt

so far no luck getting to to communicate the mavlink , even use the boot file of Mronexus and MicoAirh743

Hey i managed to connect it...
All you have to do is set the
Oscillator_hz to 25Mhz in the hwdef files of matekh743 instead of 8/16mhz

Make sure to make a folder with new name(and set AP_HW_ accordingly) in hwdef folder to avoid bootloaders from previous attempts

Also add the new board name to boards.txt file and give it a serial no.

I followed this post
https://discuss.ardupilot.org/t/install-bootloader-and-firmware-for-customized-fc-fails/130542

Now the question is will the setting of 25Mhz cause any problem or damage the board?

[synersignart]

thanks miftahul-commits I would try again , on ardupilot 4.7.4
what changes did you made on the Hwdef so far and if the AP_HW new name?
the reason i ran it on 25mhz is I dont want to change the crystal the board came with
and this is hows its ran on INAV without any issues

also one of the challenge is to generate a bootloader bin for the WEACTSTM32H743

1. does your WeActSTM32H7 connect to pc via usb after flashing with ardupilot? (Mine might turn out to be faulty, causing errors)
   does it shows up in ports anything other than stm32bootloader?

   2. I edited the MatekH743 hwdef file to have only one SPI and one I2C (with pins specified in schematic pdf for them) but the result has not changed, can it be because of some board configuration issue?

hwdef.txt hwdef-bl.txt
arduplane_with_bl(hex).txt

so far no luck getting to to communicate the mavlink , even use the boot file of Mronexus and MicoAirh743

Hey i managed to connect it... All you have to do is set the Oscillator_hz to 25Mhz in the hwdef files of matekh743 instead of 8/16mhz

Make sure to make a folder with new name(and set AP_HW_ accordingly) in hwdef folder to avoid bootloaders from previous attempts

Also add the new board name to boards.txt file and give it a serial no.

I followed this post https://discuss.ardupilot.org/t/install-bootloader-and-firmware-for-customized-fc-fails/130542

Now the question is will the setting of 25Mhz cause any problem or damage the board?

[miftahul-commits]

hwdefdat.txt
hwdef-bldat.txt

there is a boards.txt file add your boards name there, mine is WEACTSTM32H743 (shouldve kept it short). Also the same name should be included with AP_HW in your hwdef.dat file.

if you try to run
./waf configure --board WEACTSTM32H743
and then
./waf plane
there should be an error telling there is no bootloader file, there will be a suggested prompt to generate the file, something like tools/.../... ( i dont remember) , just run that and a bootloader will be created. then run
./waf plane ......again and there should a working build

[synersignart]

I manage to get around the Bootloaders by renaming the closest board with nearly similar bootloader so I can build the new board
this one works for me and manage to build the hex and apj as needed thanks

hwdefdat.txt hwdef-bldat.txt

there is a boards.txt file add your boards name there, mine is WEACTSTM32H743 (shouldve kept it short). Also the same name should be included with AP_HW in your hwdef.dat file.

if you try to run ./waf configure --board WEACTSTM32H743 and then ./waf plane there should be an error telling there is no bootloader file, there will be a suggested prompt to generate the file, something like tools/.../... ( i dont remember) , just run that and a bootloader will be created. then run ./waf plane ......again and there should a working build