#Trying to update ADXL sensor, Perpetual MCU Protocol error

19 messages · Page 1 of 1 (latest)

high granite
#

Your Klipper version is: v0.12.0-286-g81de9a861-dirty
MCU(s) which should be updated:
mcu: Current version v0.12.0-286-g81de9a861
adxl: Current version v0.12.0-25-g99d7af87
Up-to-date MCU(s):
<none>

I updated my host, then built firmwares per instructions for the Octopus and Mellow ADXL, updated both, and I can not get rid of this error with the accelerometer enabled in config. Only the 2nd time trying to use this ADXL, first time was flawless.

tacit vigil
#

Well, according to the message, the adxl is not in fact up to date

#

So one has to assume something did not go as planned with flashing it

#

Can you screenshot the process there?

high granite
#

makeconfig settings

#

It does have a 'boot' button, and I was holding it when I connected the adxl board to the host pi

tacit vigil
#

I wouldn't expect that board to have a bootloader on it

#

But don't know the device to know for sure

high granite
#

I'm going by this guide

tacit vigil
#

Fair enough...but....

high granite
#

Hm this is the Device

PXL_20240828_201443914.jpg
tacit vigil
#
  1. There's no real reason to have katapult on that board, unless it's being used to work around rp2040 usb issues
  2. Your screenshot when you actually flash shows the board going into bootsel, not katapult. If katapult was on the board, it should have gone into katapult there.
  3. If katapult is not there, then "no bootloader" would be the correct setting
high granite
tacit vigil
#

I'd say give it a shot

#

Worst case scenario is you end up needing to reflash katapult and klipper