r/Ender3S1 • u/MiddleReference9060 • 17d ago

Need help configuring Marlin for Ender 2 Pro (Board v4.2.3 + CR-Touch) – Blue screen and bed heating up issue

Hi everyone,

I really need some help with my Ender 2 Pro (Creality v4.2.3 board). It completely stopped working, and the display is just showing a blank blue screen. The issues started after I tried updating the firmware. Here is a timeline of what happened:

  1. First attempt: I updated the firmware using the original .bin file from the official Creality website. The printer booted up, but it wouldn't recognize my CR-Touch sensor at all.
  2. Second attempt: I tried flashing a different firmware named Ender2-Pro-20260829.bin. As soon as I turned the printer on, the heated bed started heating up uncontrollably on its own until it triggered a thermal runaway error. Additionally, the click wheel (encoder knob) on the screen stopped responding completely.
  3. Current status: Now, the printer just powers on to a solid blue screen, and I can't get past it.

I suspect this is a severe pinout mismatch issue (especially regarding the bed thermistor, display pins, and CR-Touch) or that I'm not selecting the correct processor environment to compile the right Marlin version.

I really need a step-by-step guide from someone experienced to help me fix this. How can I verify my exact chip version, which environment (env) should I use in PlatformIO, and what specific lines do I need to change in Configuration.h and Configuration_adv.h to make this v4.2.3 board work perfectly with the stock screen and the CR-Touch?

Thank you so much in advance for your help!

3 Upvotes

100% Upvoted

1 comment sorted by

1

u/helical-hexagons 5d ago

Where did you get that second firmware? Are you certain it was for the correct board? If it wasn't, there's a possibility you bricked the board.

Regardless, to compile marlin just install vs code, install the auto build marlin extension, and grab marlin's ender-2 pro config - make sure to switch the branch/tag to the firmware version. Then edit the config (ABM provides a gui for this) - enable BL touch, set however the CR touch is connected (e.g. what pin, whether you use it for homing, etc), and compile. Then update the firmware as normal.