✨ Mellow/Fly RRF E3 V1.0 (STM32F407VG)

[belge96]

Description

Since the Mellow/Fly RRF E3 V1.0 still wasn't supported i decided to add it myself, i thought, if i do add support i may aswell publish it for other people to have aswell (still had one of those boards around and didn't want to use RRF)

Requirements

Mellow/Fly RRF E3 V1.0 (should work directly with a standard Ender 3 config for another E3* motherboard)

Benefits

Added previously unsupported motherboard (incompatible pinout etc)

Potential issues

This motherboard doesn't seem to have an EEPROM chip so it NEEDS an SD card for EEPROM emulation

[ellensp]

you have board_build.variant = MARLIN_FLY_RRF_E3_V1

So there should be a folder buildroot/share/PlatformIO/variants/MARLIN_FLY_RRF_E3_V1 to define the new variant

[belge96]

you have board_build.variant = MARLIN_FLY_RRF_E3_V1

So there should be a folder buildroot/share/PlatformIO/variants/MARLIN_FLY_RRF_E3_V1 to define the new variant

it uses marlin_STM32F407VGT6_CCM like BigTreeTech E3 RRF (which uses the same CPU/MCU) uses and doesn't have a separate definition either

the only difference between this and the BigTreeTech board is that it has an entirely different pinout and less ports (BTT has more optional ones)

[thisiskeithb]

This motherboard doesn't seem to have an EEPROM chip so it NEEDS an SD card for EEPROM emulation

Flash-based emulation is preferred since it doesn’t require an SD card to be present.

[thisiskeithb]

Review how this is done on other boards like the BTT E3 RRF:

Marlin/Marlin/src/pins/stm32f4/pins_BTT_E3_RRF.h

Lines 397 to 406 in f0b115a

	#if ENABLED(WIFISUPPORT)
	//
	// WIFI
	//
	#define ESP_WIFI_MODULE_COM 3 // Must also set either SERIAL_PORT or SERIAL_PORT_2 to this
	#define ESP_WIFI_MODULE_BAUDRATE BAUDRATE // Must use same BAUDRATE as SERIAL_PORT & SERIAL_PORT_2
	#define ESP_WIFI_MODULE_RESET_PIN PA4
	#define ESP_WIFI_MODULE_ENABLE_PIN PA5
	#define ESP_WIFI_MODULE_GPIO0_PIN PA6
	#endif

[ellensp]

look at other examples

[Anet_ET4]
extends                     = stm32_variant
board                       = marlin_STM32F407VGT6_CCM
board_build.variant         = MARLIN_F4x7Vx    <- says to use files in buildroot/share/PlatformIO/variants/MARLIN_F4x7Vx

[env:BTT_E3_RRF]
extends             = stm32_variant
board               = marlin_STM32F407VGT6_CCM
board_build.variant = MARLIN_BTT_E3_RRF <- says to use files buildroot/share/PlatformIO/variants/MARLIN_BTT_E3_RRF

Yours

[env:FLY_RRF_E3_V1]
extends             = stm32_variant
board               = marlin_STM32F407VGT6_CCM
board_build.variant = MARLIN_FLY_RRF_E3_V1 <- says to use files buildroot/share/PlatformIO/variants/MARLIN_FLY_RRF_E3_V1

But you have not provided this variants directory so this line is invalid.

[ellensp]

the CI error is due to the tight formatting constraints on board pins files.
you need to run "make format-pins -j" or buildroot/share/scripts/pinsformat.py to format your Marlin/src/pins/stm32f4/pins_Fly_RRF_E3_V1.h file.

[thisiskeithb]

the CI error is due to the tight formatting constraints on board pins files.

We also need this PR merged since it’s used for one of the tests:

• Revert "♻️ BTT_SKR_V3_0 => BTT_SKR_3" Configurations#1109

[thinkyhead]

A custom variant is specified, but there's no MARLIN_FLY_RRF_E3_V1 folder included. Do you have the variant files or know where to get them?

[thinkyhead]

This is about ready to merge, but we need to resolve the issue with the missing custom variant. If the FLY_RRF_E3_V1 enviroment is truly identical to the BTT_E3_RRF then we can dump the FLY_RRF_E3_V1 environment and just specify BTT_E3_RRF as the build environment for this board.

[thinkyhead]

This is still missing some pieces. Where is the best place to acquire them?