EVC2 Beta Firmware
Note: There are two versions of EVC2SX with different microcontrollers. This means they need to be flashed with the correct firmware. EVC2SX-03 is using the same microcontroller as EVC2S and EVC2N4 (STM32F072C). EVC2SX-03-L4 is using STM32L412C. If you get an error saying that the ELF file is invalid, please check that the file path does not contain any special characters. It's a bug in STM32CubeIDE.
Firmware 0009h (for L4 version, elf): https://1drv.ms/u/s!Atmpv-6qHr_63fpYNro_952MVbeWfQ?e=bxgc1d
Firmware 0009e (for F0 version, elf): https://1drv.ms/u/s!Atmpv-6qHr_63uxa5jjX3NMkByjWFg?e=8Diz9h
This version of the firmware requires using STM32CubeProgrammer for flashing: https://www.elmorlabs.com/forum/topic/firmware-update-using-stm32cubeprogrammer/
Release 0009h (EVC2SX L4 version, EVC2SE)
- Improved I2C communication and device detection
- Fixed EVC2SE DAC reading issue (reads back 1270µA)
Release 0009e (EVC2N4, EVC2S, EVC2SX F0 version)
- Fix EVC2N4 DAC CH2 not working
Older versions:
Firmware 0009d (for F0 version, dfu): https://1drv.ms/u/s!Atmpv-6qHr_61JcpRgmK60eGv9wOxA
Firmware 0009d (for F0 version, bin): https://1drv.ms/u/s!Atmpv-6qHr_62pADAAzxac1i23xqmg?e=dqYtO6
Release 0009a
- The UART header is now accessible as a separate USB Serial COM port
- Firmware now reports patch version separately (ex 0009a) to the software and on the OLED screen
Firmware 0009a: https://1drv.ms/u/s!Atmpv-6qHr_6zdw3hgNCubrYLZ5mtA?e=bKdicl
Firmware 0009b (for L4 version): https://1drv.ms/u/s!Atmpv-6qHr_60OpBT5kbHWfzldL3nw?e=GENByY
Release 0008f
- Compatible with SW 1.0.1.5 and 1.0.1.6
- Fix sensor readings
Firmware 0008f: https://1drv.ms/u/s!Atmpv-6qHr_6zYdDUH6XPfXbhJuCeQ?e=NIw53O
Release 0008e
- Compatible with SW 1.0.1.5 and 1.0.1.6
- Improved I2C error handling
Firmware 0008e: https://1drv.ms/u/s!Atmpv-6qHr_6zKQ3fOCQbbVCNvzVvw?e=XaIUIQ
Release 0008c
- Compatible with SW 1.0.1.5
- EVC2SX ships with 0008, it's recommended to upgrade to 0008c
- Fixed a SPI read issue on EVC2N4
Firmware 0008c: https://1drv.ms/u/s!Atmpv-6qHr_6yuxOZUPhjIRvIKhN9w?e=p9xCaq
Release 0008b
- Compatible with SW 1.0.1.5
- Adds support for EVC2SX (ships with 0008, it's recommended to upgrade to 0008b)
- Fixed I2C read problems
Firmware 0008b: https://1drv.ms/u/s!Atmpv-6qHr_6yq95zIcmhYxnj3UvNw?e=Yhg76v
Release 0007b
- Compatible with SW 1.0.1.4
- Adds support for EVC2S
- Adds I2C Frequency selection (100 KHz and 400 KHz)
- Adds I2C Lock Bus function (prevents other transactions on the bus)
- Fixed a bug where the I2C SCL line could be pulled down by the EVC2 with multiple masters
Release 0006b
- Compatible with 0006 and SW 1.0.1.2
- Fixed a problem when entering the bootloader from software
- Improved ADC readings and added 32-sample averaging
Firmware 0006b: https://1drv.ms/u/s!Atmpv-6qHr_6wJM2VpXNTbB0120gmw?e=JEwZ4g
Release 0006
- Improved the USB interface handling and command efficiency
- Additional I2C functionality for some VRM controllers
- Updated OLED handling
- Enabled permanent storage of some settings
Firmware 0006: https://1drv.ms/u/s!Atmpv-6qHr_6v4Ve_dkKmnNrxswS0Q?e=9jS5Le
Release 0005
- The OLED display is now functional again
- Basic USB interface improvements
- Added functions for entering boot loader from software
Firmware 0005: https://1drv.ms/u/s!Atmpv-6qHr_6s-wXSXp9uV98U7y4aw?e=ZGeTK7
First release 0004
- Improves I2C reliability
- Temporarily disables the OLED display
Firmware 0004: https://1drv.ms/u/s!Atmpv-6qHr_6s6hgfj_y-2NiK0uNbA
Flashing instructions (0007 and later): https://1drv.ms/b/s!Atmpv-6qHr_6yLoNGZJ0ao0-8nnTAQ
Flashing instructions (up to 0006): https://1drv.ms/b/s!Atmpv-6qHr_6soE264GHuUwCVdAKxQ
I've been trying to update my firmware without success for a couple of days now. Maybe you can see something I'm missing. ( Win 8.1 ) I installed the DfuSe_Demo application and opened it before ever plugging evc2 into that computer, Put a jumper on pins 2-3 on the BOOT0 header and plugged it in.
Available DFU Devices is blank
[img]https://i.imgur.com/8ySsfrQ.png?1[/img]
tried uninstalling DFU and plugged evc2 into W8.1 rig to get driver set first and tried installing DfuSe_Demo (both with and without unplugging evc2 first). Still no luck. Tried several variations of this also with jumper on 2-3, on 1-2, no jumper, with and without lcd screen etc.
I noticed that when jumper is on 2-3 the pulsing red light usually ( always ? ) does not turn on like it does at default 1-2
Any ideas ?
@gtijason with the jumper across pins 2-3 does the device appear as pictured in device manager?
I noticed that when jumper is on 2-3 the pulsing red light usually ( always ? ) does not turn on like it does at default 1-2
Seems like that's the default behaviour when in DFU mode as mine also does not pulse the LED.
Quote from Rave on 2019-07-20, 19:33@gtijason with the jumper across pins 2-3 does the device appear as pictured in device manager?
Seems like that's the default behaviour when in DFU mode as mine also does not pulse the LED.
It certainly does not, it shows up as a Universal Serial Bus "Device" not controller and says evbot 2.0
Thanks for showing me how it should look tho. I'm going to try a different rig
It certainly does not, it shows up as a Universal Serial Bus "Device" not controller and says evbot 2.0
Yeah, that's how it should appear if it's in normal mode (not DFU) with the jumper on pins 1-2. Hopefully you figure it out 🙂
Did you work out the issue? When setting it to DFU / BL mode it should not show up in the Device Manager as "EVC 2.0" but rather as "STM Device in DFU Mode".
Quote from elmor on 2019-07-22, 14:04Did you work out the issue? When setting it to DFU / BL mode it should not show up in the Device Manager as "EVC 2.0" but rather as "STM Device in DFU Mode".
I got it to be properly recognized and flashed but it took 14m24s and seems slow to be recognized or something. Step 9 of the firmware update pdf states
"The process should start and takes less than 10 seconds, it will confirm with a message saying Target 00: Verify successful ! "
I'm not sure what's going on, I tried several different rigs. I took video of the process/attempts but they are long so here's a screenshot of the successful flash mp4 for reference
New firmware added to the first post.
Quote from GtiJason on 2019-07-30, 18:03Quote from elmor on 2019-07-22, 14:04Did you work out the issue? When setting it to DFU / BL mode it should not show up in the Device Manager as "EVC 2.0" but rather as "STM Device in DFU Mode".
I got it to be properly recognized and flashed but it took 14m24s and seems slow to be recognized or something. Step 9 of the firmware update pdf states
"The process should start and takes less than 10 seconds, it will confirm with a message saying Target 00: Verify successful ! "
I'm not sure what's going on, I tried several different rigs. I took video of the process/attempts but they are long so here's a screenshot of the successful flash mp4 for reference
Is that on Win 7? Could be that it's slower on there. Good you got it working at least. Will try to make the update procedure smoother in the future.
I just got my EVC2 today, after ordering it on the 1st 🙂 I'm running Win 7 and have installed the EVC 2.0 driver. The software page is a complete blank even after uninstalling and reinstalling the driver. I decided that it may need to be programmed/flashed before it would work. I placed the jumped on pin 2-3 and it shows up as a STM32 Bootloader?
Thank You
Uploaded files:
I have it up and running. It has Firmware Ver .05 and was trying to use software ver 1.0.1.2d. Software Bootloader - New way to update the firmware?? I'm currently testing it with a EVGA GTX-980Ti Classified (IR3595b) plugged into the EVBot connector.
Thank You for your Help.
Uploaded files:
