Page 1 of 1
backup firmware
Posted: Thu Apr 14, 2016 2:56 pm
by robvoi
I assambled my printer. (pro B)
The stock firmware seems to work, beside the XAxis moving in the wrong direction.
Before I aplpy the new firmware I would like to backup the stock firmware. Is there a way to do this?
Re: backup firmware
Posted: Thu Apr 14, 2016 7:55 pm
by Mark
Nope, just install the new firmware. You can change the motor direction as follows:
http://www.geeetech.com/forum/viewtopic ... 17&t=17037
Re: backup firmware
Posted: Thu Apr 14, 2016 8:30 pm
by robvoi
Thanks Robert
Re: backup firmware
Posted: Mon Mar 05, 2018 8:20 am
by lkomnino
Really!! No way to backup stock Fw!?!
Had a 3-4 week diagsnosis to find that my m/board was bad, after it working with stock fw, and then had problems when upgraded to latest Marlin.
Got new board sent out, and all good.
So really REALLY want to save Fw before any changes.
Std Fw says marlin 1.0.1, and tried the pro B fw from here after doing a 're-burn bootloader', and that wasn't a cure.
Baffled that there is no way to save current config!
How about a copy atmega 2650 contents via arduino uno, or something?
Re: backup firmware
Posted: Mon Mar 05, 2018 11:22 pm
by _kaktus_
Each development environment for µC AVR allows reading the code from μC.
But only if μC is not protected against such activities. (configuration of fuse bits)
I think that you can backup flash memory and eeprom on your own. ;-)
kaktus
Re: backup firmware
Posted: Tue Mar 06, 2018 12:15 am
by lkomnino
In which case here are default setting as taken from fresh replacement board, for my CTC i3 pro B Reprap:
Note: All standard, with MK3B Dual power Heatbed, direct drive extruder, and plywood frame, also GT2560 Rev A (not A+).
Acc: 1400
Vxy Jerk: 13
Vz Jerk: 0.30
Ve Jerk: 5
Vmax x: 400
Vmax y: 400
Vmax z: 2
Vmax e: 45
Vmin: 0
VTrav min: 0
A max x: 1400
A max y: 1400
A max z: 100
A max e: 80000 (80K)
A-Retract: 5000
X Step/mm: 78.74
Y Step/mm: 78.74
Z Step/mm: 2560.0
E Step/mm: 105.0
Autotemp: Off
Temp Min: 210
Temp Max: 250
Temp fact: 0.10
PID-P: 19.86
PID-I: 1.00
PID-D: 98.93
PID-C: 1
PLA
Fan: 255
Nozzle: 180
Bed: 70
ABS
Fan 255
Nozzle: 240
Bed: 100
Re: backup firmware
Posted: Tue Mar 06, 2018 7:35 pm
by lkomnino
[quote=_kaktus_ post_id=82981 time=1520263333 user_id=62475]
Each development environment for µC AVR allows reading the code from μC.
But only if μC is not protected against such activities. (configuration of fuse bits)
I think that you can backup flash memory and eeprom on your own. ;-)
kaktus
[/quote]
So it is possible? or not?
Not too great with ins and outs of micro controllers.
Re: backup firmware
Posted: Wed Mar 07, 2018 11:48 am
by _kaktus_
Definitely yes.
But unfortunately you need to have the right knowledge and programmer eg USBASP.
On the controller board, you need to find the right outputs.
I do not know your controller board, but I assume that the manufacturer provided such a possibility.
kaktus
Re: backup firmware
Posted: Fri Jun 21, 2019 8:45 pm
by tkordemets
In case anyone misses it - I managed to download the firmware and conf with following command lines:
Code: Select all
avrdude -p atmega2560 -c wiring -P com5 -b 115200 -F -U flash:r:existingMarlin_fw.hex:i
and
Code: Select all
avrdude -p atmega2560 -c wiring -P com5 -b 115200 -F -U eeprom:r:existingMarlin_eeprom.hex:i
where com is your virtual serial port and existing...hex is the file name to be written. To run avrdude you need to navigate to C:\Program Files (x86)\Arduino\hardware\tools\avr\bin and make sure avrdude.conf is in the same directory.
Under windows it wrote on some really weird hidden directory under my user and took a while to actually find it.
Disclaimer: Files look legit but I have not tried to actually restore the conf using them.
Re: backup firmware
Posted: Sat Jun 22, 2019 3:40 pm
by _kaktus_
Hi.
Note that this is most likely not the way to make a copy of the entire program from FLASH memory.
The FLASH space in this project is divided into bootloader and user application.
You also don't have FuseBits configuration.
After loading the copy made this way into the new µC, the controller will not work.
In my opinion, this is a good method to make a copy of the current application and its configuration.