_ _ | | | | | | | | | | | | | |__| | \____/
_____ / ____| | (___ \___ \ ____) | |_____/
____ / ___| | | _ | |_| | \____|
_ _ | | | | | | | | | | | | \ \_/ / \___/
## ## #### ## #### ## ##
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: '''Firmware''' Since I need to have customized code for IAC, tried to compile new firmware. This is not so easy in windows. There's a great howto at MembersPage/JohanEriksson/VerThreeFirmForDummies but I had problems When I tried "make all" from cmd.exe: ... make (e=2): The system cannot find the file specified. make: *** [vems.o] Error 2 I get the same from cygwin's sh.exe, and in sh.exe from unxutils '''I've found that it was nothing to do with the shell and make.exe, but with avr-gcc.exe which wasn't found. '''(Since it was not in path) I've found that spaces are not welcome in winavr's path, and Marcell said that if 'lib' environment variable is set (to anything) that confuses make.exe, so I made a batch file which sets the environment before I can say "make all". It is like: set lib= set path=%path%;D:\VEMS\winavr\bin\;D:\VEMS\winavr\utils\bin\; After that I was able to compile the firmware succesfully. Thanks for the ideas Cell and Ben. ---- About setting prog.pl under win32: * Had an ActivState perl installation * Had to download SerialPort.pm, it's in Win32-SerialPort-0.19.tar * Had to download and install win32-api pm, which was in Win32-API-0.41.zip. This one really need to be installed not just having copied into lib directory. **To install: > ppm **>add repository name_of_the_package_folder **>install win32-api 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.