From: Matthias T. <mt...@we...> - 2013-09-20 18:01:56
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Enoch, > May I suggest making AmForth a BOOFA bootloader friendly by adding > the following to core/amforth.asm: > > .org NRWW_START_ADDR + #ifdef BOOFA ;The BOOFA bootloader + .org > pc+512 ; is 512 words max! + #endif .include > "amforth-interpreter.asm" Looks like a hack to me. First that comes to me is that the bootloader cannot change the content of the NRWW area. I think this will be troublesome if you want to change code there as well. For that it would be better to use the amforth-low instead of the amforth.asm. This requires some glue code for the !i word. And here lies what I call the "hack": both boofa and amforth have code to write to the flash. But they do not cooperate here and do not share code. I think that this can be made in a better way, e.g. some forth code that implements the boot loader protocol. In a few earlier releases I had a customizable start address of the NRWW code part, seems that dropping this was not a smart idea ;) Matthias -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlI8jYQACgkQ9bEHdGEMFjOWPACfX02onpgjKAe76I8n3Go3yTdh 8NQAnildqOz3q/os/un6WYOgsuP0Rgy1 =JhPf -----END PGP SIGNATURE----- |