#2.4R2 MCU FW mismatch

7 messages · Page 1 of 1 (latest)

winter yarrow
#

Hello, I recently came into possession of a 2.4r2 with a number of different upgrades and a firmware issue with MCUs not using the same fw as klipper version.

I had a few goes at flashing the firmware on the MCUs last night but seemed to no avail.

If no guides is anyone interested in loosely guiding/helping me dispel the fog of reverse engineering this printer 😂

I've read through a few different voron docs and guides but am missing a good order to go about starting my investigation/fix

As I did not build the printer I was wondering if there are any good guides out there to work backwards without a complete teardown and rebuild as the printer was working well before the firmware issue.
Thanks in advance

#

Additionally would klippy log have the details for when the firmware was flashed prior to it stoping working? If it does I'm hoping I can use a bunch of the information from prior to that point to help with mapping things out

severe belfry
#

I think the main area where there can be significant variance from a truly stock build is in the electronics bay.

Once you've appraised what's in there and how things are wired, compared to a current-ish build manual, it's probably going to be easiest to start fresh, with a clean install on the pi, and flashing properly up-to-date klipper on the mainboard.

Not aware of any guide that is out there for this process of "adopting a cast off" perhaps something for the future.

I don't believe there is any sort of timestamp associated with flashing embedded anywhere.

near portal
winter yarrow
#

I was going to look at the date for the last successful print in mainsail and then look for when things went pear shaped

near portal
#

I suppose the other thing you could look at is the datestamp on the files in the klipper/build directory. Hardly conclusive either, but might be a useful data point

winter yarrow