Custom firmware build BL Touch error

Kovs · 30 September 2021 21:08

Wanted to update my firmware via the firmware builder. Selected all the options that have worked in the past with the exception of changing the filament sensor option from low to high. Now, i keep getting this error.

PS: BL option being selected is port

CRCinAU · 1 October 2021 00:09

Looks like a change to the Marlin config verification bits… I’ve updated the builder, please try again.

M4X1P00 · 1 October 2021 03:12

I’m having the same issue at the moment.
Have you had any luck fixing it?

Kovs · 1 October 2021 15:37

Just tried it and same error

Drewbacca · 1 October 2021 23:05

I keep getting this error as well

CRCinAU · 2 October 2021 00:54

It would help if people said which printers they’re trying to build for - as it could well be that the Configurations haven’t been updated for specific printers since the code change in Marlin for additional validation…

Drewbacca · 2 October 2021 05:15

sorry, this is an Ender 3 Max with the 4.2.2 board

Kovs · 4 October 2021 19:17

Mine is the Ender 3 + 4.2.7 board

moni11811 · 4 October 2021 21:37

Same issue with Ender 3 + 4.2.7

CRCinAU · 4 October 2021 22:55

Ok, it looks like the issue comes from here for the Ender 3 + 4.2.7:

github.com

MarlinFirmware/Configurations/blob/bugfix-2.0.x/config/examples/Creality/Ender-3/CrealityV427/Configuration_adv.h#L847

    
      
           */
          
          
/**
           * Danger: Don't activate 5V mode unless attached to a 5V-tolerant controller!
           * V3.0 or 3.1: Set default mode to 5V mode at Marlin startup.
           * If disabled, OD mode is the hard-coded default on 3.0
           * On startup, Marlin will compare its eeprom to this value. If the selected mode
           * differs, a mode set eeprom write will be completed at initialization.
           * Use the option below to force an eeprom write to a V3.1 probe regardless.
           */
          #define BLTOUCH_SET_5V_MODE
          
          
/**
           * Safety: Activate if connecting a probe with an unknown voltage mode.
           * V3.0: Set a probe into mode selected above at Marlin startup. Required for 5V mode on 3.0
           * V3.1: Force a probe with unknown mode into selected mode at Marlin startup ( = Probe EEPROM write )
           * To preserve the life of the probe, use this once then turn it off and re-flash.
           */
          //#define BLTOUCH_FORCE_MODE_SET
          
          
/**

Here for the Ender 3 Max:

github.com

MarlinFirmware/Configurations/blob/bugfix-2.0.x/config/examples/Creality/Ender-3 Max/Configuration_adv.h#L847

    
      
           */
          
          
/**
           * Danger: Don't activate 5V mode unless attached to a 5V-tolerant controller!
           * V3.0 or 3.1: Set default mode to 5V mode at Marlin startup.
           * If disabled, OD mode is the hard-coded default on 3.0
           * On startup, Marlin will compare its eeprom to this value. If the selected mode
           * differs, a mode set eeprom write will be completed at initialization.
           * Use the option below to force an eeprom write to a V3.1 probe regardless.
           */
          #define BLTOUCH_SET_5V_MODE
          
          
/**
           * Safety: Activate if connecting a probe with an unknown voltage mode.
           * V3.0: Set a probe into mode selected above at Marlin startup. Required for 5V mode on 3.0
           * V3.1: Force a probe with unknown mode into selected mode at Marlin startup ( = Probe EEPROM write )
           * To preserve the life of the probe, use this once then turn it off and re-flash.
           */
          //#define BLTOUCH_FORCE_MODE_SET
          
          
/**

Lets see what I can do about fixing that…

EDIT: Pull Request is pending: Disable BLTOUCH_SET_5V_MODE on Ender 3 / Ender 3 Max Creality boards by CRCinAU · Pull Request #582 · MarlinFirmware/Configurations · GitHub

moni11811 · 4 October 2021 23:13

Many thanks CRC - Waiting on you to get my MicroSwiss working

moni11811 · 5 October 2021 03:47

Hey CRC I see the commit was closed - any updates? I still get the same error when compiling

CRCinAU · 5 October 2021 04:09

Yeah - I targeted the wrong branch for the PR…

Updated PR: Disable BLTOUCH_SET_5V_MODE on Ender 3 / Ender 3 Max Creality v4 boards by CRCinAU · Pull Request #583 · MarlinFirmware/Configurations · GitHub

Once it gets merged, the update will go to the builders at ~1 minute past the hour.

outto · 3 November 2021 01:36

I got a similar error that the customer firmware build failed. I’m trying to build the firmware for CR-10 with BLtouch and SD Cards enable. Several tries and reducing to minimal set of features but still got build failed. Could you please advise. Thanks.

4d43605c	2021-11-03 12:14:45	2021-11-03 12:15:11	Creality	CR-10	Failed
9527616a	2021-11-03 12:17:27	2021-11-03 12:17:57	Creality	CR-10	Failed
f870ac22	2021-11-03 12:19:46	2021-11-03 12:20:09	Creality	CR-10	Failed
47784e56	2021-11-03 12:21:47	2021-11-03 12:22:11	Creality	CR-10	Failed
a0cd2dfa	2021-11-03 12:23:31	2021-11-03 12:23:58	Creality	CR-10	Failed

Here is the detail on error screen
Build In Progess
Build Reference: 6c515df0
Submit time: 2021-11-03 01:43:41 UTC
Last Change: 2021-11-03 01:44:08 UTC
Current Status: Build Failed!
Builder Allocated: syd-builder
Errors:
Firmware is 12170 bytes too big for mainboard