AnsweredAssumed Answered

Application Loader

Question asked by lproctor on Jun 24, 2010
Latest reply on Jun 26, 2010 by PrasanthR

I have a requirement that allows our BF527 based system to load multiple application images.  To meet this requirement, I am proposing to create a loader application that is invoked on system reset (BMODE =  0001).  The initCode of the loader image is at 0xffa0 0000, and the main is linked to the top of external SDRAM.  The loader image will be responsible for determining the application image to load, then copying the non-bootable image from flash into the blackfin memory space, including SDRAM, then jumping to the loaded images init_code (0xffa0 0000).  The non-bootable image is basically the ROM input sections of the application e.g. use the SPLITTER utility to do this, then invoke a tool (hex2binary) to create the final non-bootable image.  I plan to use the memory initializor features to unpack initialized data.  What is incorrect about my approach?  Is there a better approach?