classicrocker883 / MRiscoCProUI

This is optimized firmware for Voxelab Aquila & Ender3 V2/S1 3D printers.
https://classicrocker883.github.io/
Other
79 stars 17 forks source link

How to build for N32? #8

Closed KimmoHop closed 1 year ago

KimmoHop commented 1 year ago

When building for Aquila N32, which environment and board should be selected in platformio.io? N32F103RE_voxelab_maple gives Error: Build environment 'N32F103RE_voxelab_maple' is incompatible with BOARD_CREALITY_V427. Use one of these: STM32F103RE_creality, STM32F103RE_creality_xfer, STM32F103RC_creality, STM32F103RC_creality_xfer, STM32F103RE_creality_maple

Using BOARD_VOXELAB_AQUILA gives Error: Build environment 'N32F103RE_voxelab_maple' is incompatible with BOARD_VOXELAB_AQUILA. Use one of these: GD32F103RE_aquila, GD32F103RC_aquila, GD32F103RE_aquila_maple, GD32F103RC_aquila_maple, GD32F103RE_voxelab, GD32F103RC_voxelab, GD32F103RE_voxelab_maple, GD32F103RC_voxelab_maple

What is the difference between Mriscoc-fall and MriscocProUI?

This is very confusing, when there is not enough description...

classicrocker883 commented 1 year ago

Mriscoc-fall is the one most updated. I wrote that in the readme in the other branch. MriscocProUI was what i was working on before the latest fall update by mriscoc. So i branched off that and worked mainly on that. I will probably delete the proui branch and when there is another update merge the current Fall one with that so theres no confusion.

right now the Fall branch works when having N32F103RE_voxelab_maple for the default_env in platformio.ini with MB BOARD_VOXELAB_AQUILA

if that doesnt work what you can also do is add -DVOXELAB_N32 to env: GD32F103RE_voxelab_maple or STM32F103RE_creality_maple (or with RC) build_flags after -DTEMP_TIMER_CHAN=4 in file --> ini/stm32f1-maple.ini and use BOARD_CREALITY_V4 if you use _crealitymaple

you may have to change the Configuration.h file to

configurations/Aquila/ MM or UBL /Configuration.h

also if you are using a BLTouch, you may have to uncomment BLTOUCH_DELAY 500 + BLTOUCH_FORCE_SW_MODE in Configuration_adv.h

im unsure if the ProUIex extra features work with the N32, but you can test it out if you want and let me know if it does. uncomment #define ProUIex 1 if that doesnt flash, then just comment it back.

KimmoHop commented 1 year ago

Marlin way of defining compatible environments is, well, awkward ;D

Thanks a lot, now MM build without ProUIex goes through (after commenting out line with onDrawUBLSlot()). I might even try it ;)

KimmoHop commented 1 year ago

@classicrocker883 ProUIex (at least toolbar, not sure what else there should be) seems to work fine with N32 👍

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.