From: Mike B. <mi...@mj...> - 2010-03-15 22:27:42
|
Aha! Found it! The assembler generates a file with an .eep extension which is actually a hex file. That will no doubt be the missing ingredient. The automatically-generated batch file AvrBuild.bat begins to make slightly more sense. Once I get through this, I'll be tempted to write something for the benefit of others as ignorant as myself! Mike Hi Mike, > The amforth files for Bf create a hex file on AVRStudio without error or warning, and a > STK500 claims to successfully copy it to flash via ISP (just the one file, no EEPROM file as > indicated at one point in the amforth documentation). Exactly that is the problem: You definitly need the EEPROM hex file, without it amforth cannot work at all. Strange that the avrstudio does not generate one.. You may find hex files in earlier versions, I sometimes miss to generate one for a release. mea culpa. Please do not mix the versions however... Matthias ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Amforth-devel mailing list Amf...@li... https://lists.sourceforge.net/lists/listinfo/amforth-devel |