___  
  / _ \ 
 | | | |
 | |_| |
  \___/ 
        

  ___  
 / _ \ 
/ /_\ \
|  _  |
| | | |
\_| |_/
       
       

       
/'\_/`\
|     |
| (_) |
| | | |
(_) (_)
       
       

 _   _ 
( ) ( )
| |/'/'
| , <  
| |\`\ 
(_) (_)
       
       

 __     __
 \ \   / /
  \ \ / / 
   \ V /  
    \_/   
          

IMPORTANT: enter the case-INsensitive alphabetic (no numbers) code AND WRITE SOME SHORT summary of changes (below) if you are saving changes. (not required for previewing changes). Wiki-spamming is not tolerated, will be removed, so it does NOT even show up in history. Spammers go away now.


Visit Preferences to set your user name
Summary of change:
Com1 is used as communication port. I get into bootloader mode using the terminal program. (Bray) I send Manmcbffmcb in the terminal program. I then change to 19200 baud and send S to check the reply. The reply from the controller is AVREFI1. I then send v to the controller. The reply is 20. I exit the terminal program and start AVRprog.exe I have successfully uploaded vems.hex (from '''v3_firmware_2004-11-24_v9''' ) into the ATMEGA using the AVRprog.exe. I exited the program using the exit button on AVRprog.exe I can download config.mtt from the controller using the terminal program (Bray) and the mcd command. But I can still not get MegaTunix to communicate to the controller. I started the MegaTunix via command prompt. Then I changed the com port to COM1. This is the message I get from Megatunix: The MegaSquirt ECU appears to be currently disconnected. This means that either one of the following occurred: # Wrong Comm port is selected on the Communications Tab. ''Possibly, but you aleady know from Bray terminal that COM1 to be used'' # The MegaSquirt serial link is not plugged in. ''Unlikely...'' # The MegaSquirt ECU does not have adequate power. ''If other apps / terminal can talk to it, it's got enough power.'' # The MegaSquirt ECU is in bootloader mode. ''Check with a terminal, or better with prog.pl. Do a verify @ 19200, and if you don't need to "t" talk to the "msavr" application first, it's in bootloader mode. ---- '''comm experiments - surely talking to firmware''' save output of these commands to files, zip and upload (or take notes at least): * 9600 baud * Man (is ''Hello>'' printed ? although MegaTunix does not use this command; if this aint work, MegaTunix won't be able to talk for sure: likely because it's in bootloader, see below ) * '''mcd - works''' * mct * mdv * mdi * '''bye''' (if above work, this is needed to leave the "menu" mode => megatune protocol (1 byte command mode), so MegaTunix can talk to it * A (outputs binary, check the number of bytes at least) * m (outputs binary, check the number of bytes at least) ---- if above talking to firmware is a success, provide '''details of MegaTunix you try to use''' * platform * version, where you dowloaded from * and configs added * other customizations * '''Capture and publish the MegaTunix log''' (turn on interrogation, serial in, serial out), see MegaTunix page Above details are needed to help you. ----- if above talking to firmware fails, '''See if it's in bootloader mode''' - MegaTunix cannot talk to * '''without''' Manmcbffmcb * in 19200baud * send ''S'' and see if ''AVREFI1'' is printed * send v and see if ''20'' is printed If above ''AVREFI1'' / ''20'' is printed, you know it's in bootloader mode: after firmware upload the marker word wasn't written (I can only use prog.pl, like ''perl bin/prog.pl vems.hex 19200 :COM5 Etwf'' because avrprog does not support COM5; prog.pl is faster anyway). Repeat above test of bootloader. Dave A said MegaTunix 0.70 is broken, and to use 0.71 instead. This should hopefully fix the comms problem.
Optional: Add document to category:
Wiki formatting: * is Bullet list ** Bullet list subentry ... '''Bold''', ---- is horizontal ruler, <code> preformatted text... </code> See wiki editing HELP for tables and other formatting tips and tricks.