Am 09.10.2013 19:31, schrieb Matthias Trute: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hello, > >> At this moment i am sceptical about the produced code, because >> after converting hex to bin i get 30447 bytes with a big block of >> FF in the middle ? > That's right. You may want to study the differences between the NRWW > and RWW address regions of the atmega microcontroller flash. How they > relate to amforth and what code is in which segment I've described in > the technical user guide at amforth.sf.net, I wont repeat it here. The > padding of FFFF words is only necessary for stupid hex file formats, > smarter ones (like elf) can address the segments directly and are > smaller wrt file size. Not that this really matters for a few KB of > file size however.. > > Smart flash programs (like the current avrdude) can skip those blocks > and work significantly faster. > >> When i disassemble the bin there are much invalide opcodes. > Most of them are opcodes of the forth VM, so called execution > tokens, and not opcodes for the atmega controller. The remaining > numbers are... numbers or addresses. If you want to study the > internals, I'd recommend the LST file from the assembler. It contains > the sources and the generated code in one single text file. > > Matthias >
Now I understand - Thank You! ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk _______________________________________________ Amforth-devel mailing list for http://amforth.sf.net/ Amforth-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amforth-devel
