SOLVED The serial settings are fine, I just had the wrong display type defined in the firmware. I’m a very paranoid person apparently.

Thanks everyone.

Original post:

I have acted recklessly and now I need help.

I tried to update my Ender 3 Pro with an SKR V1.3 to Marlin 2.1 and I tried to skip some steps.

I couldn’t find a v1.3 example in the configurations repo so I used a v1.4 instead because it had the right processor.

I changed some stuff over but didn’t give it a thorough look and I didn’t change the SERIAL_PORT 1 and 2 settings.

When I tried to load the new firmware from the SD card the screen was blank and it hasn’t worked since.

The firmware file changed to a .elf so it maybe installed?

I wonder if I can even load via the SD if I’ve super messed up it’s serial config. I tried some other firmware versions plus BigTreeTech’s from 3 years ago but I don’t think they’re being read.

If I’ve messed up those serial configs I wonder how I could undo it without the SD card. Help…

P.s. does anyone have a copy of Marlin 2.1 that works with the SKR V1.3 or the config files for that board on the Ender 3 Pro?

Catch you on the flip side 😎 👉👉

  • warhammercasey@lemmy.world
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    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

    • MoonlitCringeOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      Thanks for the info. You were right it was the display settings. Look at me getting worried over nothing.