readme: clarify U2C note

Signed-off-by:  Eric Callahan <arksine.code@gmail.com>
This commit is contained in:
Eric Callahan 2023-01-05 12:39:18 -05:00
parent ec96191e4b
commit 74dac182a7
No known key found for this signature in database
GPG Key ID: 5A1EB336DFB4C71B

View File

@ -181,11 +181,12 @@ acceptance of the
[candlelight](https://github.com/candle-usb/candleLight_fw), such as a [candlelight](https://github.com/candle-usb/candleLight_fw), such as a
[Canable](https://canable.io/). Alternatively, a device that supports [Canable](https://canable.io/). Alternatively, a device that supports
Klipper's USB-CAN bridge mode works well. Klipper's USB-CAN bridge mode works well.
- The BTT U2C v2.1 CAN peripheral does not work with CanBoot. The device fails - The BTT U2C v2.1 CAN device does not consistently work with CanBoot. On
when large data transfers are requested. Note that this problem may also some systems (anecodotally the Raspberry Pi 4) the device fails when
lead to Klipper to shutdowns. Avoid this device until BTT has resolved the large data transfers are requested. Note that this problem may also
problem. lead to Klipper to shutdowns. This device *may* work depending on your
- If using a MCP2515 CAN Device (ie: Waveshare RS485 CAN HAT) it is possible hardware setup, however tread carefully.
- If using a MCP2515 CAN device (ie: Waveshare RS485 CAN HAT) it is possible
that packets will be dropped when reading flash back from the node during that packets will be dropped when reading flash back from the node during
the verification process. That said, I have successfully tested the 12 MHz the verification process. That said, I have successfully tested the 12 MHz
Crystal variant with the Crystal variant with the