Migrate Hispeedv1 (QQS-Pro) to HAL/STM32

[Foxies-CSTL]

Requirements

Delta QQS with board hispeedv1 (clone aka MKS_Robin_mini with removable drivers).

Description

Change env hispeed :

FLSUN QQ (STM32F103VET6)

[env:flsun_hispeed]
platform = ${common_stm32f1.platform}
extends = common_stm32f1
board = genericSTM32F103VE
extra_scripts = ${common.extra_scripts}
buildroot/share/PlatformIO/scripts/mks_robin_mini.py
buildroot/share/PlatformIO/scripts/add_nanolib.py
build_flags = ${common_stm32f1.build_flags} -DMCU_STM32F103VE -DSS_TIMER=4
lib_deps = SoftwareSerialM
#Adafruit NeoPixel=https://github.com/Foxies-CSTL/Robin-NeoPixel-Lib/archive/master.zip

to hispeedv1:

FLSUN QQS Pro (STM32F103VET6) using hal STM32
board Hispeedv1

[env:flsun_hispeedv1]
platform = ${common_stm32.platform}
extends = common_stm32
build_flags = ${common_stm32.build_flags} -DMCU_STM32F103VE -DSS_TIMER=4 -DENABLE_HWSERIAL3 -DTRANSFER_CLOCK_DIV=8
board = genericSTM32F103VE
board_build.core = stm32
board_build.variant = MARLIN_F103Vx
board_build.ldscript = ldscript.ld
board_build.offset = 0x7000
board_build.firmware = Robin_mini.bin
board_upload.offset_address = 0x08007000
build_unflags = ${common_stm32.build_unflags} -DUSBCON -DUSBD_USE_CDC
extra_scripts = ${common.extra_scripts}
pre:buildroot/share/PlatformIO/scripts/generic_create_variant.py
buildroot/share/PlatformIO/scripts/stm32_bootloader.py
buildroot/share/PlatformIO/scripts/mks_encrypt.py

It is the same as the MKS Robin_nano boards except the generated name which must be Robin_mini.bin.

Benefits

Removal of additional scripts to reduce the binary, compatible with the latest Neopixel library.
Have the same environment as MKS_Robin_nano.

Configurations

platformio.txt

Related Issues

I have successfully compiled a new firmware under STM32 HAL with the latest changes PR #20325 from @sjasonsmith on the platformio.ini.
I have a Delta QQS with TMC2209 in single-wire mode, the Neopixel activated with an active WIFI module (ESP12s).
I performed an autocalibration (G33) ok, perform a UBL with a bed at 60 ° C and run a test print to correct my segments between the towers.
Everything seems functional.

[Foxies-CSTL]

If it's not ready, you can change to Draft.

Yes, I always start a PR with a draft and when I see that there are no more errors I go through it. But there, either I close it, or I leave it open to help you (if that helps you) so .......

[sjasonsmith]

I think we might have been too early with this. I thought @Foxies-CSTL had everything working, and did not realize there were TFT UIs that STM32F1 users have, which do not work on STM32.

I don't really want two environments for every board for the two HALs. I would like to simply move boards to the new HAL, hopefully with no functionality lost. Perhaps we are best just with the two robin stm32 environments for right now.

[Foxies-CSTL]

I thought @Foxies-CSTL had everything working

Hi @sjasonsmith @rhapsodyv , I assure you that for the Delta FLSun QQS-Pro printer with hispeedv1 motherboards (with and without removable stepper drivers) all the functionalities are operational. All this with the Marlin color interface (TFT_COLOR_UI) but some prefer to stay on the old classic interface (TFT_CLASSIC_UI) for convenience stories, usually or that they don't like this one. In the new Hal STM32 environment, this option doesn't work.
There you go, I hope I was clear.

[sjasonsmith]

@rhapsodyv, the env is exactly the same as mks_robin_nano35_stm32, except for the following line:

board_build.firmware = Robin_mini.bin

Do you know if this filename matters, or can it be anything we want? If the name is flexible it seems like we could use one STM32 environment for this board, nano, and Robin Mini.

[thisiskeithb]

Do you know if this filename matters, or can it be anything we want? If the name is flexible it seems like we could use one STM32 environment for this board, nano, and Robin Mini.

MKS bootloaders look for specific file names or they won’t update.

[sjasonsmith]

MKS bootloaders look for specific file names or they won’t update.

Are you sure? This nano env did not always have the "35" at the end on it, that was only after the TFT screen was added. Previously it was jus mks_robin_nano.

[sjasonsmith]

We could always use extends to inherit everything and only override the filename though, if necessary.

[thisiskeithb]

Are you sure? This nano env did not always have the "35" at the end on it, that was only after the TFT screen was added. Previously it was jus mks_robin_nano.

The firmware binary wasn’t named that though. It should be Robin_nano35.bin

[sjasonsmith]

The firmware binary wasn’t named that though. It should be Robin_nano35.bin

Nope, it was just mks_robin_nano.bin. If I'm not mistaken mks_robin_nano and mks_robin_nano_35 worked on the same board, but the 35 version has extra source/dependencies for 3.5" TFT support.

Maybe they only match the first portion of the name, and the rest doesn't matter.

[Foxies-CSTL]

Nope, it was just mks_robin_nano.bin. If I'm not mistaken mks_robin_nano and mks_robin_nano_35 worked on the same board, but the 35 version has extra source/dependencies for 3.5" TFT support.

Yes, you right.

Maybe they only match the first portion of the name, and the rest doesn't matter.

no, it's not working if I rename it Robin_nano.bin or Robin_nano35.bin for my board. But with the Nano environment, the generation gives me a "Robin_nano.bin" and if I rename it to "Robin_mini.bin", I can flash it. Another thing, the electronics that FLSun has to modify is similar to the nanoV2 but the description of the eeprom at the start of the "Pins" file is different. It is the same as the Nanov1.2 and Mini.

[Foxies-CSTL]

@thinkyhead ,
It's only for hispeedv1_maple, so you can delete it ;-)
Now the definition for hidpeedv1 is in the "stm32f1" section and I use this

#
# FLSUN QQS Pro (STM32F103VET6)
# Hispeedv1 Robin mini variant
#
[env:flsun_hispeedv1]
extends                     = mks_robin_nano_v1v2_common
board_build.encrypt_mks     = Robin_mini.bin
build_flags                 = ${mks_robin_nano_v1v2_common.build_flags} -DENABLE_HWSERIAL3
build_unflags               = ${mks_robin_nano_v1v2_common.build_unflags} -DUSBCON -DUSBD_USE_CDC

regards