mriscoc / Ender3V2S1

This is optimized firmware for Ender3 V2/S1 3D printers.
Other
2.62k stars 358 forks source link

[BUG] GD23F103RC_voxelab Environment Firmware Not Working (Marlin Firmware Auto Build) #865

Closed brentrichardjr closed 1 year ago

brentrichardjr commented 1 year ago

Bug Description

Auto Build firmware using GD32F103RC_voxelab doesn't work on the aquila.

Auto Build firmware using GD32F103RC_voxelab_maple works as expected.

Pulled repo today (4/16/23). Used configurator.pyw to generate config files (Aquila-G32-BLTUBL-T13)

I'll try to respond to any questions the best I can. I'm new to compiling my own firmware. Thanks for all you do!

Bug Timeline

No response

Expected behavior

No response

Actual behavior

No response

Steps to Reproduce

No response

Version of Professional Firmware

2.1.3 Mriscoc

Printer model

Voxelab Aquila

Electronics

GD23F103

Add-ons

Sprite Pro Extruder; CR Touch

Bed Leveling

UBL Bilinear mesh

Your Slicer

Prusa Slicer

Host Software

SD Card (headless)

Additional information & file uploads

No response

mriscoc commented 1 year ago

If you use the Configurator, the default environment configured in the Platformio.ini for the G32 version is GD32F103RC_voxelab_maple, using that environment is correct.

classicrocker883 commented 1 year ago

if youre looking for Voxelab Aquila specific

check out this repo here

I was able to get it to work for the GD32 and N32 chips, and the interface be more like Alex's. be aware that these chips must use "Maple" configuration and "RC" default_envs in platformio.ini

the chips cannot flash with anything more than 256k, technically 89.1% of 256k but yeah. if you want ProUIex and UBL with all the added features, you will have to disable some things in the *Marlin/Config...h* files. the _maple env uses more memory space but there is nothing you can do since it wont flash without it. Manual Mesh and all the other features should fit fine. UBL* seems to take up the most memory.

github-actions[bot] commented 1 year ago

This issue has had no activity in the last 60 days. Please add a reply if you want to keep this issue active, otherwise it will be automatically closed within 10 days.

github-actions[bot] commented 1 year ago

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.