ST 8032 In-Application Programming

Hi All,

I am trying to get my In-Application Programming up and running on an ST micro uPSD33xx. When activating the newly programmed image I need to switch execution from the boot flash to the main flash. When this happens the micro will just blindy contiune retrieving instructions from the next memory location as if nothing has happened, unaware of the switch in flash device.

For everything to not fall in a big heap I am planning to have a routine which is fixed at the same absolute in both applications - it is this routine which will handle the switching of memory banks (and so the instuctions being retreieved should be identical in both apps).

First of all, does that sound insane to anyone out there?

Secondly, and prehaps a daft question, how should I determine *where* to locate the absolute routine. What guidelines can you offer as to how one determines where to locate such a 'shared' routine?

Cheers for any help/recommendations.

Andy

Parents
  • Andy,

    It sounds somewhat like you've been reading my long-winded discussions at ST's message board. If not, you can take a look here:

    www.stmcu.com/forums-cat-2229-11.html&start=0

    Assuming you've done that and that's why you're looking here, I can tell you this: All I did to figure out where to place my swapover routine was look in the memory map and find a place where it fit. I've thought about it some since then, however, and forcing it to exist right past the end of the interrupt vectors seems like a more reasonable thing, given that I've integrated it with the startup code.

Reply
  • Andy,

    It sounds somewhat like you've been reading my long-winded discussions at ST's message board. If not, you can take a look here:

    www.stmcu.com/forums-cat-2229-11.html&start=0

    Assuming you've done that and that's why you're looking here, I can tell you this: All I did to figure out where to place my swapover routine was look in the memory map and find a place where it fit. I've thought about it some since then, however, and forcing it to exist right past the end of the interrupt vectors seems like a more reasonable thing, given that I've integrated it with the startup code.

Children
More questions in this forum