Maximilian Gerhardt

Compiles just fine with your platformio.ini + code. ``` Linking .pio\build\esp32s3box\firmware.elf Retrieving maximum program size .pio\build\esp32s3box\firmware.elf Checking size .pio\build\esp32s3box\firmware.elf Advanced Memory Usage is available via "PlatformIO Home > Project Inspect"...

Oh, you're actually right. On 5.1.1 it's broken, same for 5.1.0. Use ```ini platform = [email protected] ``` in the `platformio.ini` for a workaround.

The version in `library.properties` was not updated, so all library crawlers will not see this new version: https://github.com/yaacov/ArduinoModbusSlave/blob/v2.1.0/library.properties#L2

Works! https://registry.platformio.org/libraries/yaacov/ModbusSlave/versions 

Maintainer of [platform-gd32](https://github.com/CommunityGD32Cores/platform-gd32) and [ArduinoCore-GD32](https://github.com/CommunityGD32Cores/ArduinoCore-GD32) here -- how can we help the efforts? What's the current state? Any people actively working on it? >I believe that Creality3D has posted a...

>As of now, only 303 chip works perfectly, And with what config is that? Do people use the Maple core with a STM32 chip to compile for a GD32F303 that...

>i mean build with standard stm32f103re_creality env works just fine, reportedly, no extra bugs Yeah and since that is using STM32Duino with STMicro's USB stack, everyone running that on GD32...

You're right, although USB is by-standard enabled in `stm32_common`, the linker cleanly throws out all USB code in the final linker stage (I can see that in the `.map` file),...

If you are using the `STM32F103RE_creality` [environment](https://github.com/MarlinFirmware/Marlin/blob/2a1c2e26ed38e55c52d569807884585a9523389c/ini/stm32f1.ini#L117-L152), that is using the `MARLIN_F103Rx` board, and its clock init code would be in https://github.com/MarlinFirmware/Marlin/blob/bugfix-2.1.x/buildroot/share/PlatformIO/variants/MARLIN_F103Rx/variant.cpp#L114-L130. Of course, the extra bits in the PLL...

This occurred again in https://community.platformio.org/t/platformio-tries-to-upload-to-wrong-port-even-if-declared-in-platformio-ini/19989 -- if a user hasn't worked with PlatformIO for a while and suddenly the workflow changes, confusion is bound to happen.