From 74dac182a7b73274bd41de35b2809d2ae0daa434 Mon Sep 17 00:00:00 2001 From: Eric Callahan Date: Thu, 5 Jan 2023 12:39:18 -0500 Subject: [PATCH] readme: clarify U2C note Signed-off-by: Eric Callahan --- README.md | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index a3e6d38..49fb106 100644 --- a/README.md +++ b/README.md @@ -181,11 +181,12 @@ acceptance of the [candlelight](https://github.com/candle-usb/candleLight_fw), such as a [Canable](https://canable.io/). Alternatively, a device that supports Klipper's USB-CAN bridge mode works well. -- The BTT U2C v2.1 CAN peripheral does not work with CanBoot. The device fails - when large data transfers are requested. Note that this problem may also - lead to Klipper to shutdowns. Avoid this device until BTT has resolved the - problem. -- If using a MCP2515 CAN Device (ie: Waveshare RS485 CAN HAT) it is possible +- The BTT U2C v2.1 CAN device does not consistently work with CanBoot. On + some systems (anecodotally the Raspberry Pi 4) the device fails when + large data transfers are requested. Note that this problem may also + lead to Klipper to shutdowns. This device *may* work depending on your + 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 the verification process. That said, I have successfully tested the 12 MHz Crystal variant with the