VEMS Home Products Documentation Wiki Webstore
WikiHome ProjectPage DocsPage UnderDevelopment MembersPage SiteIndex RecentChanges Preferences
MembersPage/SteinOvePrestmo/MyNotes (2006-05-31 03:49:32)
[Start] [Notes ] [Wiring] [SensorPage]

This page contains my notes and questions regarding the assembly of my V3.1 Genboard. My board is nr 81.

25.05.2006: Questions regarding firmware update

It was now time for me to update the original firmware on my V3.1 board. I've downloaded vemsMT1.0.36 from http://www.vems.se as this was the latest official firmware version.

Step 1 First thing was to download the original config and tables by using the "download-config" command found in the vemsMT1.0.36 folder. The config and tables download went ok.

Step 2 Next was to generate new MTT Config and tables fils by using the "generate-config" command. This reported in the [config.log] file and [table log] file. Only warnings, no erros.

Step 3 Uploaded the new firmware with the "upload-firmware" command, but during this operation something must have happend.

When I restarted the board MT crashes before It starts and from Bray terminal I get a running "<0><0>" signal. This starts as soon as it gets power.

Step 4: Boot loader With a help from Dave25 on IRC I started the board in bootloader mode. Bootloader was started by shortcutting pin 2 and 3 during power up (cable disconnected from PC) Then connecting the seriel cable to PC while power on. With Bray terminal the board replied to "v" and "S" test commands in bootloader. Disconnected Bray terminal window. Edited the "update-firmware" bat file by removing the "t" in the commandline. Saved and run the file. Megaloader did its job but as soon as the megaloader command "E" was run the board started to send out the continuous <0><0> signal again in bray.

I need help to understand what going on !!!!

Check 1 I removed an extension seriel cable between the card and computer but that didn't help. Now only 30cm of cable from the computers serial output to the board.

Check 2 I notised from earlier checks with bray connected at powerup. The first signs to appear on the screen was the "<0>" sign. This is the bootloader signal. While the board was sending out the "<0>" signal I jumped pin 2 and 3 on the serial cable the board and it went into bootloader mode. (checked in bray afterwards with bray connected (19200 8n1))

Question: What can cause the board to constantly send out bootloader signal after I tried to upgrade the firmware???

26.05.2005 Time to upgrade bootloader with STK200 parallel port cable

Jorgen recommended me on IRC to upgrade bootloader. Before I can do this I need to make a STK200 parallel port cable.

STK200 cable info found here: http://www.x-dsl.hu/genboard/programmer.txt

HDRpin#AVRpinparallelpinparallelPin#Note
1PDOBusy11Black
2VCC--Used separate VCC (Not in use)
3SCKStrobe1Orange
4PDIdata02Yellow
5RESETINIT16Red
6GNDGND23Brown

Error message from Bootloader update

C:\vems\avrdude\bin>avrdude -p m128 -c stk200 -t

AVRDUDE: AVR device not responding

AVRDUDE: initialization failed, rc=-1

Double check connections and try again, or use -F to override this check.

AVRDUDE done. Thank you.

C:\vems\avrdude\bin>

Any know why I got this message?

New cable design...

It looks like the cable I've made it's not supported by AVRDUDE.

I'll rewire the cable i've made to this configuration.

http://www.bsdhome.com/avrdude/

This cable is to be used togheter with the "-C bsd" command in AVRDUDE

AVR pin commandISP header #Parallel port pinNotes
AVR /RESET57Yellow
AVR SCK (clock input)38Black
AVR PDI (RXD) (instruction in)49Red
AVR PDO (TXD) (data out)110Orange
Signal Ground618Brown
* MOSI and MISO are not used.

Correct pins from the schematics AVR pin 2 = RXD/PDI -> ISP header Pin4, AVR Pin3 = TXD/PDO -> ISP header pin 1

From Avrdude.conf file

id = "bsd";

desc = "Brian Dean's Programmer, http://www.bsdhome.com/avrdude/";

type = par;

vcc = 2, 3, 4, 5;

reset = 7;

sck = 8;

mosi = 9;

miso = 10;

Must remember to dump 128k flash to disk first:

avrdude -c bsd -p m128 -U flash:r:save.hex

genboard has the 2x3 pin style standard. Though the onboard ISP connector has 2x6 pins, one end is the same as the old 2x3 ISP connector (used on v2.x as well). You can verify on schematics, and measure to the related AVR pins (note that on atmega128 PDI / PDO are used for ISP not MOSI / MISO)

15.02.2006: Question regarding the flyback set-up

Looking at what was in my Rescue kit 1 (came with the V3.1) I'm now having problems finding out which is which of the flyback diodes. 2 types found in the kit but non of them looks or have similar names/measured values of those found in GenBoard/VerThree/RescueKit

Edit: 17.02.2006 '

Note that in forward direction all diodes (the zeners and transient protection diodes too) measure small (typically <0.7V) voltage.

I need flyback control for my high ohm injectors and the Idle control output (Idle control need a 12v PWM signal to operate the spring loaded butterfly)

Possible solution 1:

Utilize the GenBoard/Manual/DDFlyback for both injectors and the Idle control output if I have the correct parts in the Rescue kit.

Possible solution 2:

Install low voltage flyback diodes from Rescue kit 1 together with the new GenBoard/Manual/PowerFlyback

Q: Which of the two solutions is the best from my set-up?

Turbo comments

Is the K03 => K04 stepup significant?

No, The K03 is rated to approx 210-230hp on my engine while the K04 should be able to give me between 260-300hp

Flow maps for [K03-2072] and [K04-0025] turbo. [More Flow maps here]

A question from MembersPage/DeanPavlekovic

Hi Stein, can you possibly give the part number and the diameter of you crank trigger wheel if the engine is still not assembled?

TIA

PS I can be emailed at dpavlekovic at gmail dot com, or just add to MembersPage/DeanPavlekovic

Questions 19.12.04

If you have a stepper chip, check GenBoard/BuildProcedures/Stepper.

Info from Jörgen:

This is the Elfa part# for the fuseholder: 33-153-48

You find fuses here: http://www.elfa.se/elfa-bin/dyndok.pl?vat=0&dok=2013505.htm

Good news 29.08.04

I got a "Hello" in Bray terminal, finally.

After I tried to use Hyperterm, I got contact with the GenBoard with Bray terminal.

The reason for my initial problems was all down to bad wiring and bad reading of diagrams.

I somehow managed to switch the pins on the PS2 connector. (sendt + to gnd pin...) and forgot to attach the contrast wire on the LCD.

Question: (29.08.04)

Nothing on the list today (yet)

To do list

More to come.

Below are things I have done

Initial Testing

The first thing I did after I recieved the GenBoard. I checked it for visible damage/short circuits, I couldn't see anything special (But are the SMDs assembled by machines? 95% of the top side was automated with picknplace and reflow-soldering. The bottom side was by human for v3.1. For v3.2 both sides will be automated. )

I made a serial cable, LCD display cable and a PS2 cable with connection. My seriell connection cable has been checked against the 1.8m extension cable and should be ok.

My power supply is an old AT PC supply (gives 11.6V). On the 12V power cable I have an 2A fues.

Problems

For the first power up I connected the Genboard with the seriell cable, LCD and PS2 keyboard. 12v was connected with an alligator clip to the right leg of the 1n4007 diode (diode mounted to the bottom side). GND connected to the GND wire loop.

When I turned on the power nothing happend. I couldn't see any signes of life in the LCD or when trying to connect to the Genboard with Bray terminal at 9600baut, 8n,1.

I have also tried to connect to the Genboard with only the serial cable connected without a possitive result

When I tried to hook up the PS2 keyboard again, a couple of seconds after the GenBoard got power, the powersupply fans stopped. I also felt a slight smell of warm electric components :/ I can't see any damage to the board or components. I have feeling somethings wrong with the PS2 wiring/keyboard?

Q:

Can I have damaged the Genboard the first time I powered it up?

Any hints where I can meassure with a DVM ?

A:

I tried powering mine up last night with similar results, mine is however a very early v3.1 (#30) while I guess that yours is one of the last ones.

I verified that my AVR does nothing by measuring 0v on the pre_inj lines. With some luck mine has accidently been delivered without bootloader or firmware. The FET drivers are inverting and to keep the injectors closed the engine management will turn those lines 'high' as soon as it gets power.

VCC is easy to verify by checking that you have 5v on the topmost pin of the PS2 connector. Also check that you have 5v on the forth pin from the left on the top row of JP_ISPI. This is the reset line.

---

Re:

I measured 5V on both pins and on Pre_Inj lines.

My AVR is alive. :D

Q:

I now get "Connected" with Bray terminal, but get no reply when trying the "Man" command.

A: as we don't use RTS, CTS or flow-control, "Connected" means really nothing.

Pin numbers on MAX232 chip

Where are pin1 and pin 16 on the MAX232 chip?

pin1 is close to EC36, pin16 is close to EC18

pin8 close to LM1815, pin9 close to AVR

[Atmel ATMEGA128 Pin-out]

Checklist

'My test results are in Italic''

MAX232 meassurements (only power connected)

Pin1 6.9v

Pin2 8.99v

Pin3 2.4v

Pin4 4.59v

Pin5 -4.4v

Pin6 -8.54v

Pin7 8.59v

Pin8 0v

Pin9 5v

Pin10 0v

Pin11 5v

Pin12 5v

Pin13 0v

Pin14 -8.55v

Pin15 0v

Pin16 5v

The rest is not done as I have to check the com. cable first

This assumes you expect to talk to the test (or real) application (firmware) at 9600,8n1 (not the bootloader):

The above 2 command is meant to determine which direction of the RX,TX has problem. If the indication of action happens (ign259 signal change, or mcd output in terminal) than the other direction has the problem.

If you wiped out your test-application by an unsuccessful bootloader-procedure, you can only talk to bootloader (you can force talking to bootloader by shorting the GenBoards RX,TX while serial cable is disconnected). BootLoader talks 19200,8n1 by default and has no such simple way for testing the directions independently as the firmware has. It emits some very short squarewave at powerup that can be captured on a digital scope with some experience.

please move this to relevant page