3DPrinting is a place where makers of all skill levels and walks of life can learn about and discuss 3D printing and development of 3D printed parts and devices.
The r/functionalprint community is now located at: or [email protected]
There are CAD communities available at: [email protected] or [email protected]
No bigotry - including racism, sexism, ableism, homophobia, transphobia, or xenophobia. Code of Conduct.
Be respectful, especially when disagreeing. Everyone should feel welcome here.
No porn (NSFW prints are acceptable but must be marked NSFW)
No Ads / Spamming / Guerrilla Marketing
Do not create links to reddit
If you see an issue please flag it
No guns
No injury gore posts
If you need an easy way to host pictures, https://catbox.moe may be an option. Be ethical about what you post and donate if you are able or use this a lot. It is just an individual hosting content, not a company. The image embedding syntax for Lemmy is 
Moderation policy: Light, mostly invisible
The SD card reader has nothing to do with the serial port, so you're fine on that point.
I would just try and roll back to the bigtreetech firmware for the 1.3, even if it's for an older Marlin. Once thats working, build Marlin 2.1, updating the configuration to match the known working one.
Thanks for the suggestions, you were right about the SD card being fine, it was just dodgy display settings on my part.
Messing up the serial configuration shouldn’t affect your SD card. SD cards typically run off SPI or SDIO whereas a serial port runs off a UART or a USB virtual comm port if the processor on the board supports that. They shouldn’t affect eachother.
I would confirm your serial settings are correct, flash it using the SD card, then hook up your computer to its usb port and see if you can send/receive commands over a serial console. If you can see stuff you probably just misconfigured your display settings.
Worst case you have to buy a $5 stlink off Amazon and flash it using JTAG which is guaranteed to work unless there’s some kind of physical damage
Thanks for the info. You were right it was the display settings. Look at me getting worried over nothing.