Marlin VS MRiscoCProUI

I've re-installed the firmware: UBL-NoProbe-3x3-N32.bin (is this correct?) I have no probe but not sure on N32 or G32 and 3x3 or 5x5.

Firmware: Alex's Firmware 1.3.5.1 BLTouch-9x9-G32.bin

corresponding DWIN_SET in Marlin/Display firmware/Firmware Sets/

so to your last question why cant you update to marlin 2.1.x , well you can , but since its a different chip you will need an init script . if you want to do that with the 2.1.x copy this file https://github.com/alexqzd/Marlin/blob/main/Marlin/src/HAL/STM32F1/HAL.cpp into Marlin/src/HAL/STM32F1/HAL.cpp and add a #define VOXELAB_N32 into your config file , and bam it works .kinda i had some icons missing , its honestly a bit of a hassle to get working spez for someone without microprocessor experiance .

There is a limit in the firmware around 250c ish so if you want to print materials that need a higher temp you will have to modify the firmware. If that is something you want to do best to start with Alex's FW. There is a modified version here for high temps but may not be exactly the one you need. If you can't compile yourself I'm sure someone could do it for you if you make a request.

I could not find this guide to compile the firmware for it, could you link to it? It may be the pins of the CPU are wired up to different things on the aquila board and you need to define them properly. As you have the STM32 then there should not be any other changes to look out for unlike the other chips. You could compare the configuration files with Alex's to see if you have missed anything.

I would suggest using Alex's firmware if you are printing at high temps. Then you can use his repository to mod and compile you own FW. (for the H32 chip use this one) Some people have already done the high temp mod on some versions like Printsleo3D

This is where it has moved to

I don't know much about compiling firmware but it might be better to base the edits on Mriscoc instead of Alex's as it has much better support for the H32 chip so should be a lot easier to compile.

I'm see that there are newer firmware available. This one (https://github.com/classicrocker883/MRiscoCProUI/releases), for example.

I just thought of another thing you could try. Give Mriscoc ProUI FW as it may have the option to configure this or is already properly set up for this version of the probe.

If for some reason your FW does not support those Gcodes then update it to the latest version, or try Alex's or Mriscoc ProUI firmwares.