grbl VS BTT_SKR_13_14_14T_SD-DFU-Bootloader

The other thing to consider is the $12 config in GRBL itself: Arc tolerance. Drawing circles is EITHER a long series of small line segments, OR an "arc". If this problem only effects arcs: you can likely limit your search there.

You can use NO limit switches with GRBL. Here is some info. But NC is generally a better option because if there is a failure in a wire or connector, the circuit will open and stop the machine.

Grbl is a firmware for Arduino based microcontroller dev boards. https://github.com/gnea/grbl/wiki Once programmed you stream the gcode to the grbl controller over USB. It's constrained by the limitations of the Arduino hardware or runs on but it's a great entry point to CNC machines. Note that a 32 bit grbl is under development but pre built control boards are still rare.

The gnea/grbl GitHub Getting Started page spells all that out.

This may not be a fit, but it may give you ideas for prototyping/software dev. I have prototyped various CNC/optical/medical projects using GRBL GitHub and a simple benchtop frame-gantry setup that I made from 80/20 and steppers.

To learn more: https://github.com/gnea/grbl/wiki/Grbl-v1.1-Configuration

If it really is GRBL, you'll find most of the information you need at https://github.com/gnea/grbl/wiki and the $ commands at https://github.com/gnea/grbl/wiki/Grbl-v1.1-Commands

Take a look at https://github.com/GadgetAngel/BTT_SKR_13_14_14T_SD-DFU-Bootloader -- it may help. It's not only for the larger boards.

However, I couldn't manage to find the original bootloader for this chip. I found this : https://github.com/GadgetAngel/BTT_SKR_13_14_14T_SD-DFU-Bootloader which is very interesting for many older BTT controllers, but not the SKR 3 EZ.

If you want to investigate, you might start by looking at https://github.com/GadgetAngel/BTT_SKR_13_14_14T_SD-DFU-Bootloader

The only other way is to use a little programmer such as an ST-Link, which looks similar to but is different from the little USBasp programmers that can be used for 8-bit boards. An ST-Link can flash firmware directly, but it's not as simple as using the SD card. See, for example, https://www.youtube.com/watch?v=7O_ZOdnM0SU and https://github.com/GadgetAngel/BTT_SKR_13_14_14T_SD-DFU-Bootloader

For LPC based boards this may help. It seems to allow flash over USB.

It doesn't sound like an EEPROM fault, because that only affects various settings, not what functions and codes it supports. It sounds like something is wrong with the bootloader, eg it's reading the firmware file but not storing it. If nothing else works, is it worth getting a little STLink in-system programmer and reinstalling the bootloader and firmware completely? There's a link at https://github.com/GadgetAngel/BTT_SKR_13_14_14T_SD-DFU-Bootloader which should be helpful if you want to try that.

(If all else fails, you can try reflashing the bootloader - something on this page may help you.)

Technically, it's possible to use a programmer to update the firmware, and I've seen descriptions of how to do that with various small programmers. Here's an example. Perhaps a google search will find more information, given that it does exist. People have used that technique to read and (re)load bootloaders and firmware.