The firmware compilation and configuration needs some files and packages and steps, here is a summary:
(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.
- 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
- [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.