Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Compiled FW does not boot on Ender 3 Pro with 4.2.7 Board & BLTouch 3.1 #22948

Closed
Gunhawk007 opened this issue Oct 13, 2021 · 9 comments
Closed

Comments

@Gunhawk007
Copy link

Did you test the latest bugfix-2.0.x code?

Yes, and the problem still exists.

Bug Description

I am tryting to compile Marlin FW for my Ender 3 Pro, for which I have the Hardware upgraded with Creality's V4.2..7 Silent Board with the TMC Steppers and also installed a BLTouch V3.1 probe.

When I am using the FW from Crealitys site, everything works as expected.

Bug Timeline

First test to compile own FW - never did before

Expected behavior

I epected the printer to boot from the compiled FW which has been saved on the SD-Card. Please note that the V4.2.7. board has a different FW install procedure that needs the FW placed on the SD Card and not to be flashed via USB.
The normal behavior should be that after switching on the printer with the SD-Card having the FW on it, the LCD screen should light up empty for about 15 sec and then displays the Ender Logo followed by showing the Main Menue/Info Screen

Actual behavior

After inserting the SC-Card containing the freshly built FW and switching on the printer, the LCD screen lights up with an empty screen and stays there until being switched of - waited for about a minute or so. Normally, the printer should boot up after about 15 secs.

Steps to Reproduce

  1. Download the FW and Configuration
  2. Copy over the configuration files for Creality->Ender-3 Pro->CrealityV427
  3. Follow the instructions to enable BLTouch
  4. Compile the FW using Visual Code and Marlin Auto Build Extention using the Environment "STM32F103RET6_creality
  5. Locate the compiled BIN file and save to SD-Card
  6. Insert SD-Card into the powered off printer
  7. Turn on the printer -> LCD Screen lights up up remains blank - no Ender Logo, no boot

Version of Marlin Firmware

Marlin V1.1.2 2020-04-25 Ender-3 Pro www.creality.com

Printer model

Ender-3 Pro

Electronics

Upgraded electronics with Creality V4.2.7 Mainboard

Add-ons

BLTouch V3.1 Z-Probe installed for Auto-Level

Bed Leveling

ABL Bilinear mesh

Your Slicer

Cura

Host Software

No response

Additional information & file uploads

Configurations used for Built:
Issue_Config_tested.zip

Firmware coming out of tthe built prozess:
firmware-20211012-213446.zip

Firmware downloaded from Creality proven to work OK:
Ender-3 Pro_4.2.7_BLTouch_Marlin2.0.1_V1.1.2_TMC2225.bin.zip

@thisiskeithb
Copy link
Member

Have you tried removing the SD card after flashing? #22898

@Gunhawk007
Copy link
Author

Yes I did.
I can also confirm that the filename of the new binary presented on the SD-Card is different from the one that has been used to boot up the machine successfully - this has been mentioned in the forums - make sure the binary is named differently from the currently installed one as the system stores the bin filename in the EEPROM and prevents an install.

@descipher
Copy link
Contributor

Sounds like it's a display configuration problem, there is a recent change e.g IS_U8GLIB_ST7920 vs ENABLED(U8GLIB_ST7920) in the configuration_adv file.
The config examples have IS_U8GLIB_ST7920 but 2.0.9.2 default uses ENABLED(U8GLIB_ST7920).

@Gunhawk007
Copy link
Author

Thanks for the hint.
I have now done the following in Configuration_adv.h:

  • Replaced the Line
    #IF IS_U8GLIB_ST7920
  • with the following
    #if ENABLED(U8GLIB_ST7920)

The code compiles successfully, the the result (blank screen on boot) remains the same. Reverting back to my old FW immediately solves it so it may be something else.

@Gunhawk007
Copy link
Author

Can perhaps someone with the same HW than me 427 mainboard version coming without the transfer board and BLTouch share their config and binary so I can test it on my HW? Maybe I have a board with a sometimes faulty update routine.

@J0hnMatrix
Copy link

J0hnMatrix commented Oct 22, 2021

Hello,
I have the same issue but on an Ender-3 with a FYSETC Cheetah 1.2 (stock display).
I kept the same settings as 2.0.9 and after flashing the new FW with FlyMCU, the screen stay blank.
Have tried to connect the printer with Octoprint (to see if the motherboard still can "speak") but no luck

Working config is Marlin-2.0.9_en.zip
Affected config is Marlin-2.0.9.2_en.zip
Marlin-2.0.9_en.zip
Marlin-2.0.9.2_en.zip

@Gunhawk007
Copy link
Author

UPDATE:
I have now successfully built my firmware and got it to run with my Ender 3 Pro and the 4.2.7. Board. Even BLTouch works with the board now. However, it seems that my filament sensor I have attached as well does not report correctly. The sensor is attached to the dedicated 3Pin connector and seem to operate correctly (LED on Sensor is lit/off when filament is inside or out. However, the M412 State always reports the same.
Is there a setting that I need to use (similar to Z_MIN_USES Pin 17) to indicate where the sensor is connected? BLTouch is also connected to the 5 Pin Port on the board, which mean it does not uses ENDStop but uses Pin 17

@ellensp
Copy link
Contributor

ellensp commented Dec 3, 2021

Your trying to use this as a support forum.

This Issue Queue is for Marlin bug reports and development-related issues, and we prefer not to handle user-support questions here. (As noted on this page.) For best results getting help with configuration and troubleshooting, please use the following resources:

After seeking help from the community, if the consensus points to a bug in Marlin, then you should post a bug report.

@ellensp ellensp closed this as completed Dec 3, 2021
@github-actions
Copy link

github-actions bot commented Feb 2, 2022

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.

@github-actions github-actions bot locked and limited conversation to collaborators Feb 2, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants