I02CAN (CanHat) Doesnt Function as claimed with CB1

It was claimed this was test and worked perfect with the Manta Boards and a CB1, yet on all three of my Manta set ups (M8P, M4P, Manata EZ) these boards do not function as they are supposed to with the EBB36 board. Connection constantly resets in canbus making flashing klipper impossible on the EBB36.

My BoardEnv.txt has the proper line uncommented:
uncomment the following overlays in order to use both TFT35_SPI and MCP2515
overlays=tft35_spi mcp2515

My /etc/network/interfaces.d/can0 has the proper lines as outlined by several sources:
allow-hotplug can0
iface can0 can static
bitrate 1000000
up ifconfig $IFACE txqueuelen 256
pre-up ip link set can0 type can bitrate 1000000
pre-up ip link set can0 txqueuelen 256

Running ifconfig can0 brings up the following:
can0: flags=193 mtu 16
unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 256 (UNSPEC)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

Followed the steps via the Maz0r guide. The EBB36 takes the USB flash of CanBoot as expected.

~/klippy-env/bin/python ~/klipper/scripts/canbus_query.py can0
I had around a 10% success rate getting a UUID using this command.

~/CanBoot/scripts/flash_can.py -i can0 -q
I had around a 90% success rate getting a UUID using this command.

Attempting to flash always led to this failure:


As with almost every BTT/BiQu product launch, the documentation is no where to be seen. Whats interesting and what should have thrown a massive red flag to me, was when Biqu launched all these new products right before the new year, EVERYTHING got a github repository, except the IO2CAN and new TFT35 SPI screen, both of which I have 3 pairs sitting on my workbench, useless as they dont work as described.

The only reason I purchased them and how many I did is because I was assured they were tested and worked as expected.

EDIT:

Now on top of everything, even with a reboot, I'm getting an OS "No Buffer Space" Error

biqu@BTT-CB1:~$ ~/klippy-env/bin/python ~/klipper/scripts/canbus_query.py can0
Traceback (most recent call last):
File "/home/biqu/klippy-env/lib/python3.9/site-packages/can/interfaces/socketc an/socketcan.py", line 679, in _send_once
sent = self.socket.send(data)
OSError: [Errno 105] No buffer space available

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "/home/biqu/klipper/scripts/canbus_query.py", line 64, in
main()
File "/home/biqu/klipper/scripts/canbus_query.py", line 61, in main
query_unassigned(canbus_iface)
File "/home/biqu/klipper/scripts/canbus_query.py", line 25, in query_unassigne d
bus.send(msg)
File "/home/biqu/klippy-env/lib/python3.9/site-packages/can/interfaces/socketc an/socketcan.py", line 658, in send
sent = self._send_once(data, msg.channel)
File "/home/biqu/klippy-env/lib/python3.9/site-packages/can/interfaces/socketc an/socketcan.py", line 681, in _send_once
raise can.CanError("Failed to transmit: %s" % exc)
can.CanError: Failed to transmit: [Errno 105] No buffer space available

Start with the reported BoardEnv.txt overlay, /etc/network/interfaces.d/can0 configuration, and the Klipper canbus_query.py and CanBoot flash_can.py commands. Reproduce the intermittent UUID discovery and flashing failure on the CB1 with an EBB36, then investigate the CAN resets and "No buffer space available" error; done means CAN communication and flashing work reliably.

Written by the indexing model from the issue text.