Engine:
6cyl inline COP
Primary trigger = VR
Secondary trigger = VR
Vems wireloom with relays and fuses
Firmware 1.2.38
Trigger Setup
Had to modify old v3.3 board hardware from Hall to VR.
Problem: Primary trigger VR is OK but no secondary trigger show up on triggerlog.
Solution: reviewed the hardware by checking following items for VR setup:
- Primary Trigger VR
- remove R30 OK
- solder SJ6 OK
- solder JP2-JP7 OK
- Secondary Trigger VR
- solder LM1815 OK
- solder SJ7 OK
- wire EC18pin12 --> pin3 2nd LM1815 OK
- solder 1k smd pulldown resistor between VRinput-GND OK
- connect LM1815 pin5 to +5V OK
- R182=0 OK
- removed C103 was the final trick, without removing I had not sec trigger
Help! Can someone help me with analysing triggerlog?
Seems there are some problems with Too many PTrig, LessPTrig and LessStrig
http://www.vems.hu/files/Marteleur%20Tim/v3.3_u000374-2020-12-28-21.42.58CamSyncOK.triggerlog
http://www.vems.hu/files/Marteleur%20Tim/v3.3_u000374-2020.12.26-19.23.21CAM2.vemscfg
Problem Solved now 27/12/2020!
Thanks to Dave I could reflash the chip and start all over with the apropriate files to load the new bootloader and firmware.
Now running firmware 1.2.38.
Below is output of the AVR after first attempt to upgrade.
I think my fault was not uploading the bootupgrade 1.1.94bootupload first.
I tried to upgrade the bootloader by using the Isp cable from the webshop and the Avr pocket programmer. The lock failed 0x3c ! = 0x2c
What can I do next to solve this?
This is the result:
Microsoft Windows [versie 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. Alle rechten voorbehouden.
C:\Users\Timmo6>c C:\>avrdude -c usbtiny -p m128 -U lfuse:w:0x2f:m -U hfuse:w:0xc4:m -U efuse:w:0x ff:m -U lock:w:0x3c:m
avrdude: AVR device initialized and ready to accept instructions
Reading | ################################################## | 100% 0.02s
avrdude: Device signature = 0x1e9702
avrdude: current erase-rewrite cycle count is -50462977 (if being tracked)
avrdude: reading input file "0x2f"
avrdude: writing lfuse (1 bytes):
Writing | ################################################## | 100% 0.01s
avrdude: 1 bytes of lfuse written
avrdude: verifying lfuse memory against 0x2f:
avrdude: load data lfuse data from input file 0x2f:
avrdude: input file 0x2f contains 1 bytes
avrdude: reading on-chip lfuse data:
Reading | ################################################## | 100% 0.01s
avrdude: verifying ...
avrdude: 1 bytes of lfuse verified
avrdude: reading input file "0xc4"
avrdude: writing hfuse (1 bytes):
Writing | ################################################## | 100% 0.01s
avrdude: 1 bytes of hfuse written
avrdude: verifying hfuse memory against 0xc4:
avrdude: load data hfuse data from input file 0xc4:
avrdude: input file 0xc4 contains 1 bytes
avrdude: reading on-chip hfuse data:
Reading | ################################################## | 100% 0.01s
avrdude: verifying ...
avrdude: 1 bytes of hfuse verified
avrdude: reading input file "0xff"
avrdude: writing efuse (1 bytes):
Writing | ################################################## | 100% 0.01s
avrdude: 1 bytes of efuse written
avrdude: verifying efuse memory against 0xff:
avrdude: load data efuse data from input file 0xff:
avrdude: input file 0xff contains 1 bytes
avrdude: reading on-chip efuse data:
Reading | ################################################## | 100% 0.01s
avrdude: verifying ...
avrdude: 1 bytes of efuse verified
avrdude: reading input file "0x3c"
avrdude: writing lock (1 bytes):
Writing | | 0% 0.00s ***faile
d;
Writing | ################################################## | 100% 0.08s
avrdude: 1 bytes of lock written
avrdude: verifying lock memory against 0x3c:
avrdude: load data lock data from input file 0x3c:
avrdude: input file 0x3c contains 1 bytes
avrdude: reading on-chip lock data:
Reading | ################################################## | 100% 0.01s
avrdude: verifying ...
avrdude: verification error, first mismatch at byte 0x0000
0x3c != 0x2c
avrdude: verification error; content mismatch
avrdude: safemode: Fuses OK
avrdude done. Thank you.