##    
         
  ###    
   ##    
   ##    
   ##    
  ####   
         

 _______ 
(_____  )
     /'/'
   /'/'  
 /'/'___ 
(_______)
         
         

______ 
|  ___|
| |_   
|  _|  
| |    
\_|    
       
       

  _  __
 | |/ /
 | ' / 
 | . \ 
 |_|\_\
       

_________
\__    _/
   )  (  
   |  |  
   |  |  
   |  |  
|\_)  )  
(____/   
         

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:
'''The firmware compilation and configuration needs some files and packages and steps, here is a summary''': http://www.vems.hu/files/Firmware/docs/FirmwareOverView.png (note: if you want to update this picture, you can find the editable image in the zip in the same dir) This page is being cleaned up and moved to GenBoard/Manual/Firmware. There is a step by step guide on this page: MembersPage/JohanEriksson/VerThreeFirmForDummies but there is also a snapshot of the released firmware on GenBoard/UnderDevelopment/FirmwareChanges. * GenBoard/FirmWare/CVSUsage tells you how to get a local firmware working directory * AtMega/AvrGccFAQ helps you get !WinAVR * AtMega/PerlInterpreter helps you get PERL * GenBoard/FirmWare/BuildFirmwareFAQ explains how to build ''vems.hex'' and ''boot/main.hex'' * GenBoard/Firmware/BootLoader helps you get ''boot/main.hex'' or ''vems.hex'' to the AVR and set the fuses * GenBoard/Firmware/Upload helps you get ''vems.hex'', ''boot/main.hex'' or ''mix.hex'' to the AVR (but Boot Loader is recommended finally, see below) * ''etc/*_factor.c'' are missing from the picture. If you need custom curves for your temperature or pressure sensors, you can use them in the ''make'' step. Some people use ''EasyTherm'' and ''inc2tbl'' perl script to produce custom ''etc/*factor.c'' files, but parabola (2nd order polynom) fitting would be 10 lines in perl. * GenBoard/InitialConfig helps you build your ''etc/config.txt'' and ''etc/tables.txt'' * See GenBoard/Manual/Firmware/MyMake for ''my_make'' related info * GenBoard/MenuSystem helps you use the menu and ''make mtt'' * GenBoard/Version describes the version naming procedure for firmware revisions * [http://www.stack.nl/~dimitri/doxygen/index.html Doxygen] was proposed to use for generating code documentation (and maybe for installation-doc too?) ----- Using the GenBoard/Firmware/BootLoader (having ''boot/main.hex'' on the avr, and uploading ''vems.hex'' via ''prog.pl'' or ''avrprog'' not ''avrdude'') is preferred. The bootloader makes updating the firmware at a later date much easier. You might want to load just straight firmware to begin with to test your board on the desk. I would recommend getting the GenBoard/Firmware/BootLoader installed and working before you install the board in your car. Without the BootLoader you will need to connect the STK200 cable to the board in order to update the firmware. ----- You can get a recent [http://megasquirtavr.sourceforge.net/msavr_fw_snapshot.tar.gz firmware HEAD snapshot] without a cvs client (see GenBoard/Firmware/CVSUsage), but don't use the CVS head unless you know what you are doing. Use the released snapshot instead.
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.