News:

When asking for technical help at the very least let us know the version of firmware you are running.
Cliff's Calibration (Mapping) Guide is a MUST READ: http://www.vemssupport.com/forum/index.php/topic,97.0.html

Main Menu

New 1.2.20 Fw

Started by billman, January 07, 2014, 11:33:05 PM

Previous topic - Next topic

billman

Hi I read about the new 1.2.20 but I can not understand the position about:

requires uhex bootloader (all boards and ECU purchased since 2011-03 has uhex bootloader) Verify in VemsTune File / "Firmware info": Marked by the 'u' as in "v3.3_u009583"
older devices upgradable after locking certain internal "fuse" bit with an [AVR-ISP] device (or a cheap 5-wire DSUB25 parallel printer port stk200 or similar ISP cable with avrdude).


For what part do we need this? For RS232->USB do we need this?

VEMS

Hello Bill,

This is only applicable if you have a petty old board, the new 1.2.20 firmware (and all firmwares up) are restricted to uhex bootloader only (which is applied standard in boards since 2011-03), firmware release will from now on only be released in uhex format.

But this requires users of older boards to upgrade their bootloader if applicable (and they want to run the latest firmware). Checking of bootloader version in your board is easy: In VemsTune -> File -> Firmware info -> SerialNumber; If this starts with "v3.3_u" you have uhex bootloader (good) if it stats with "v3.3_n" you have non-hex bootloader (requires upgrade).

Best regards, Dave

fphil

As a matter of fact, the new release is 652K instead of 856K. What happens? Big cuts of dead code?

VEMS

Hello Philippe,

The actual firmware code file (uhex) got a bit bigger mainly due to many speed improvements, but after size offset from removal of hex file from distribution, total package size is less.

Best regards, Dave

Erikk

I tried uploading 1.2.20 to one of my ECU's on the bench.
Everything looked well until i applied a 60-2 triggersignal from soundcard, Vemstune disconnects and the Ecu gets stuck.
Sometimes it gets stuck with an injector FET activated, sometimes the same channel is stuck in High-Z mode, Injector-PWM is activated.

The board starts as it should when rebooted.

Went back to 1.2.17 and everything works as it should again.

Vemslog:
https://drive.google.com/file/d/0By3dCB55iWzTMGFwSDI2cncwaWc/edit?usp=sharing


Using latest Nightly VemsTune with ini-update and firmware from the firmware-web-tool.
The board has uhex bootloader

mads b (dk)

Are VEMS shop going to sell the firmware upgrade cable for old boards.... i have a 3.1 board


Thanks Mads
Vw beach buggy 1.6 VNT turbo, Vems 3.1 no. 57

Seight-v8

I am glad someone asked this question, as have been wondering about this......

My ecu is n_001401, but how do you obtain a copy of the new bootloader?

I have a self made ISP cable and can unlock the required "bits" but cannot find the bootloader to upload to the ecu.

cheers

scott
Engine:Rover V8 4600cc
Vems Firmware:V1.2.38, GPS, SDcard, LCD & Dual lambdas, Wasted spark, 36-1 trigger, Cam Sync & Bluetooth serial.

http://www.vems.hu/wiki/index.php?page=MembersPage%2FScottRichmond

peter_jensen

Boot loader upgrade can be complex process unless you are familiarly with processors and electronics.
I will recommend sending the box to Hungary for update.
If you like to do the work by you self then buy a USB boot loader. I have used the USB loader several times and it´s much easier then mess around with command prompt.

Vems.dk

billman


jrussell

The USB ISP cable is here: http://shop.vems.hu/catalog/cable-p-165.html

But as was mentioned previously by Peter, it's much preferred to send the ECU to HU to get upgraded unless you have experience programming microcontrollers. Send them an email at [email protected] to get a return authorization.

Or if you're in the US, [email protected].

Thanks!
VEMS USA - Located in beautiful Burlington, Vermont
1988 RX7 Turbo

GintsK

Purpose of fuse bit changing was not afterwards ability to change bootloader using serial communication?

MWfire


lost

I'm also intrested in new bootloader for v3.3_n002183  on PCB is mark v3.5 ...

Seight-v8

don't know whether I would be happy to return my ecu all the way to hungry...im not saying it would get lost or damaged.....but

Is there no one in the UK that could do this?

what's the worse case scenario that could happen during boot loader update if you were to do it yourself?

I have better than average PC skills, with computers & dos programming....so could handle it I am sure....

cheers

scott
Engine:Rover V8 4600cc
Vems Firmware:V1.2.38, GPS, SDcard, LCD & Dual lambdas, Wasted spark, 36-1 trigger, Cam Sync & Bluetooth serial.

http://www.vems.hu/wiki/index.php?page=MembersPage%2FScottRichmond

MWfire

Quote from: lost on January 09, 2014, 05:20:58 PM
I'm also intrested in new bootloader for v3.3_n002183  on PCB is mark v3.5 ...

I can upgrade you in Croatia.