Subpage of AfreshTiny
Firmware Releases
Recent [vemstune] supports round firmware upgrade and operation with the non-AIM firmware (round firmware is also shipped inside, and ini also).
The AIM capable firmwares uses the Megatune (zipped in with the firmware)
The stable release:
Non-AIM: [round_2010-04-07.zip] (1.4.3)
AIM: [round_2009-10-12.zip] (0.4.0)
Old releases : http://www.vems.hu/download/round/
- [round_2007-04-25.zip]
- some useful linear wideband voltage output modes require this, see AfreshTiny/VoltageOutput
Firmware upgrade
Firmware upgrade does not change the WBO2 and EGT calibration configuration saved in EEPROM. But display modes changed (there are 8 display-mode "slots"), so you need to set up these slots if you upgrade firmware. Without setting the display mode slots properly, the display will show unintended values.
Firmware upgrade with command line tools
- verify that your COM-port works. Settings: 19200,8n1. Try in MegaTune (or possibly in TerminalProgram: SManmxc, expect something like "MenuPingx")
- unzip the archive. You will see in firmware directory:
- round.chex firmware file
- roundloader.exe native win32 binary
- "UploadFirmware.bat" You need to edit this, and adjust to your COMx port:
- eg. change COM3 => COM2 (whatever applies):
- roundloader.exe -p COM3 -s 19200 -f round.chex -c write
- if you see C:\tmp\STABLE1_0\minrtest\round.chex change it to round.chex
- We shiped pre configured batch files for COM3 and COM4
- make sure supply connection is stable. Supply must not drop out during firmware upgrade. If that accident happens, use Round Emergency Revival, see AfreshTiny/FirmwareUpgrade/SsssssFlood ("SSSSSS" flooding) would be needed to get it back to life again. Use a good supply, with stable connection
- Quit MegaTune or any terminal program.
- start "UploadFirmware.bat" from a "run -> cmd" shell, not by clicking on it so you see the output (success or error). Firmware upgrade takes appr 25 seconds.
Supported windows versions
Roundloader.exe seems to work on win32 systems from w98 to XP (and likely newer), if COM-port is otherwise working:
- XP with pl2303 USB-RS232 adapter cable from WebShop: success
- Successfully upgraded/verified firmware with roundloader on WinXp sp2, notebook with USB/RS232 adapter. Seems fine. (MembersPage/GergelyLezsak)
- Successfully used roundloader to upload new firmware. Used on Dell D810 laptop on COM1. (Stefcross)
Supported Linux method ... Oldschool firmware upgrade method - for experts only
prog.pl Works (similar to BootLoader) with new (included in the zip) prog.pl version (PERL and serialport module required, NOT included). Prog.pl only recommended on linux, or if roundloader does not work for some reason. Ask for a linux roundloader native executable if you need it.
Firmware upgrade with VemsTune
- First download the latest VemsTune ( http://www.vems.hu/download/v3gui/ )
- make sure supply connection is stable. Supply must not drop out during firmware upgrade. If that accident happens, use Round Emergency Revival, see AfreshTiny/FirmwareUpgrade/SsssssFlood ("SSSSSS" flooding) would be needed to get it back to life again. Use a good supply, with stable connection
- Quit MegaTune or any terminal program.
- Start VemsTune , set up the serial port
( if the old firmware is AIM-capable VT need to set Round to Boot mode manually -> see AfreshTiny/FirmwareUpgrade/SsssssFlood )
- download the needed firmware by VemsTune WebTool ( VemsTune/WebTool )
- select "Tools/Firmware/Firmware Upload"
- select the needed firmware
Recover from interrupted firmware upgrade
Normally, this should NOT be necessary.
For round, if firmware upgrade is interrupted, the serial loopback method will NOT work. Either it will stay in bootloader by itself, or only 'S' flooding will work: send a file from TerminalProgram full of "SSSSSSSSSSSSSSSSSSSSSSSSSSSSS" (make it 6..30kbyte to be convenient, because it sends appr 2kbyte/sec) in 19200,8n1 while the round is powered up; than any standard firmware upgrade tool like roundloader should be able to communicate and upgrade firmware
Revert to default config (wbo2, EGT, etc...)
Avoid this ! Only do it if variables seem to be badly misconfigured.
- before doing it take not of calibration variables: wbo2_pump_pwzero, wbo2_nernstdc_target, egt_offset, egt_cal,
- write 255 into wbo2_pump_pw_zero, save (burn to eeprom) and reboot.
This procedure should not normally be necessary. It reverts to wbo2_pump_pw_zero=0x65 and egt_offset=0xC0 so you might want to recalibrate:
- adjust pump_pw_zero (best values vary from 0x62..0x68 for a certain controller)
- and egt_offset (easy, looking at the temp, especially if the sensor is room-temp or an alligator clip is used on the EGT terminals)