From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jesper Skov To: Andrew Lunn Cc: Jesper Skov , Grant Edwards , ecos-discuss@sources.redhat.com Subject: Re: [ECOS] RedBoot porting Date: Mon, 08 Jan 2001 03:04:00 -0000 Message-id: <14937.40644.767218.755234@thinktwice.zoftcorp.dk> References: <20010105115220.A2486@visi.com> <20010108092928.I10158@biferten.ma.tech.ascom.ch> <20010108113554.N10158@biferten.ma.tech.ascom.ch> X-SW-Source: 2001-01/msg00066.html >>>>> "Andrew" == Andrew Lunn writes: >> One way this could be accomplished is by providing a function (in >> RAM application) that saves the virtual vector table, fills it with >> pointers to NOP functions (in RAM) which count usage. Andrew> Another simpler option is to make the ROM copy itself into RAM Andrew> and run from there. Some of the HALs already support this for Andrew> apps, but has it been tested for redboot? It also means you Andrew> can then overwrite the redboot image in FLASH while its Andrew> running the copy in RAM. With the app and the boot loader Andrew> becoming closer tied together its becoming more important to Andrew> be able to upgrade the bootloader in the field as well as the Andrew> application. This should work already for targets that support it. Adding the support to new targets it relatively simple (only really requires PIC startup code that initializes the system, copies everything to RAM and jumps there). Remember, RedBoot _is_ just an application (as far as I know, anyway). Jesper