I needed to update my old Creality CR-10 s5 (super 500, or CR-10s 5 model) with newer firmware than Marlin 1.8.x so I downloaded the latest Marlin and set out to configure it. I ran into some issues with the firmware not recognizing the built-in Micro SD card slot. Here is a list of the fixes I implemented to get mine working and I also included a zipped file of my build of the Marlin 2.1.2.2 patched with bugfixes firmware as of 2/26/2024. Additionally, I had issues getting my Win 11 PC to recognize the printer. After opening up the control box, I found that I have the control board with the FTDI chip and had to get a proper CDM driver which I have also included. Since there are many different variations of the driver to use, I ended up using the USB serial converter driver from the FTDI install package and it worked. I did have to assign the driver manually though, so be prepared to do that.

First of all, make sure you are modifying your own, you get a copy of the _Bootscreen.h, _Statusscreen.h, Configuration.h, and Configuration_adv.h config files for your respected version of the Creality CR-10 S5. My included build has the V1 config files.

I normally update my temps for the preheat PLA and ABS values, as well as make other default firmware changes for acceleration, jerk, e-steps, etc. to match my printer; so you may need to make changes for yours. I also do manual mesh bed leveling, so it is set to 7x7 bed leveling to ensure this big piece of glass is level. !Change as Needed!

After all of this, I still couldn't get the SD card interface to work. After researching and modifying and uploading the firmware numerous times, I found that making these changes helped:

**pins_RAMPS_CREALITY.h file:
uncomment line 45: #define HAS_ONBOARD_SD_DETECT
change variable value from 49 to -1 on line 48: #define SD_DETECT_PIN -1

**Configuration_adv.h file:
change LCD to ONBOARD on line 1745: #define SDCARD_CONNECTION ONBOARD

Remember to always make changes at your own risk! What works for some may not work for others. I hope this helps someone who had the same issue I was having. I will consider this a work in progress because of the nature of firmware and custom changes that may need to be made.