I might be onto something:
I cut off the pins that I don't need on the 2209 from the J3 column (pins 2, 3 & 5). 
After declaring the drivers in the board.txt file this is the status of the drivers from m122:
(I think my driver 1 socked is broken, no matter what I put in there it sais that there is no driver, I will look into it some other time)
Now I need to reconnect the cables to the board as before so that I can go on with testing.
Update:
Succes! All axis moving as they should.
@gloomyandy yeah, I should have been more clear, all of the messages above were for trying to get the 2209's to work in uart mode. I've changed the title of this topic to better reflect my current situation.
@jay_s_uk said in Accidentally bought tmc2130:
That's why we have this note. I should probably update it anyway to lump 2240s in with 5160s and mention it only applies to stepsticks
I was referring to the last part that mentiones the mixing of EZ drivers.
Well, well, look what I found in the user's manual for the skr 3 EZ:
You might wanna add this to the TeamGloomy page.
Hypothetically speaking, would it be possible to just bridge the correct pins in order to select uart for the z drivers?
@gloomyandy 2240's are only available as stepsticks for now, I don't see how that would create an issue though.
The angel on my right shoulder is telling me to sell or return the 2130's and buy compatible drivers, while the devil on my left is whispering to my ear to find the schematics of the board, cut and solder the appropriate tracks in order to select uart mode.
Now that I think about it, how does the board know to use uart or spi if you can't "install the proper jumpers"?
Guess this is what you get for not reading the documentation properly.
Sidenote: on the TeamGloomy page at the skr 3 ez general information section it shows the driver ports for the skr 3, not the EZ variant.
I wanted to upgrade my corexy printer from tmc2209 to tmc5160 EZ drivers for 48v operation. Mainboard is a SKR 3 EZ. According to the documentation on the TeamGloomy website, this board does not support mixing SPI with UART drivers, so I decided to also buy two tmc2130 EZ drivers for the z axis. Guess my suprise when I learn that there is no native suport for tmc2130 in rrf.
Does anyone know if I can operate the EZ drivers in step/dir mode? If yes, how do I change the stepper driver current? Should I just plugin the 2209's (stepstick format) and modify the config to drive them with step/dir comands?
Is it possible to modify rrf to support 2130 drivers? I'm willing to spend some time tinkering with compiling rrf.
First print with the new board at relatively high speeds (compared to the previous setup) and no CAN disconnects! I guess this means that the cabling is fine.
First time power on with the skr 3 ez and the CAN-FD adapter went fine. I guess that means that something went wrong with the exp ports on the skr 2.
I need to print a new mounting bracket for the new board before doing more in-depth testing. I'll also ubdate everything to 3.5.1 .
I'm about to buy a SKR 3, hopefully this will solve the original issue that started this thread. If it still keeps on disconnecting, I'll buy a new cable or replace the original wires that it came with and hopefully that will be the end of it.
@gloomyandy I honestly can't observe any damage on the CAN-FD board. Is there a posibility that something might have happened to the exp ports on the skr?
If you unplug everything else from the board and just have the CAN-FD connected do you seem the same issue?
Yes, I still have the same issue.
When you are running these tests how are you powering the board?
The board is connected to a 24v psu. I have tried powering the board over usb as well (yes, I did move the vdd-usb jumper for this), but to no avail.
@gloomyandy do you mean the white and yellow wires?
Also, the board refuses to boot up if i have the can adapter connected but not the toolboard.
I feel like I should mention that this system worked for the last month, and only just now that I started to print faster it began showing the initial behavior.
@gloomyandy No, if I power on the board without the CAN-FD interface, the board boots up just fine.
@gloomyandy isn't that what the can adapter from mellow is called? The one connected to the exp ports
@gloomyandy Everything works fine untill I connect the efd to the board. After that, it's the same story again...
Closer inspection of the efd doesn't reveal any burns. It also passes the smell test (no burnt electronics smell)
@gloomyandy ok, removing everything from the board (except the esp32) after deleting everything in the config file except the networking stuff lets the board boot up. I can acces the board through web control. I guess I will shut it down and start plugging in stuff untill it stops working again.
@gloomyandy If you mean the green one I think it's a power indicator.
If you put a firmware.bin file on the root of the sd card and reboot the board do you see any leds flicker for a short while after power on?
Yes, and after that it repeats the previous behaviour.
Also if you check the card after a waiting a short while has the firmware.bin has the name changed to something else?
It turns into a cursor file.
@gloomyandy I've changed the link, you should be able to see the video now.
Reflashing the firmware did not solve the issue.
@gloomyandy this is the behavior that I'm associating with boot loop:
https://drive.google.com/file/d/1EX8ncjLaL5Gg9t0ZIwL676H8gxXVDZhE/view?usp=drivesdk
The difference between what I did now and before is that before when problem occurred, I would first pause the print, and then press the button. This time I just pressed the button without stopping the print.
