Any changes in flash and bootloder procedures when moving from S12 to S12X

[AndersJ]

When migrating from S12 to S12X,

are there any significant differences to consider when

writing bootloaders, executing from ram/stack... etc?

Is it likely that legacy code will work?

Will XGATE have any implications?

Any other cracks to fall into?

Thanks,

Anders J

[Steve]

Anders, you should be able to find what to change from the various app notes that cover the main aspects of the transition. Either AN2615, AN3469, AN3510 will apply.

[colinh]

Hi Anders

It's not likely, but not impossible, that your legacy code will work without change.  Most migrations from S12 to S12X require the usual review of memory map, peripheral features etc.

There should be no real need to consider the XGATE in your loader.

One feature you can probably take advantage of (and I'm 90% certain it is not supported in the S12) is the ability to set the vector base address.  This lets you more easily utilise interrupts in your loader if that is something that would be useful to you.

Hope this helps

Colin

[kef]

Yes, VBR is certainly an advantage, but also probably a problem for Anders. S12X doesn't allow any resource remapping, there are no more INITRM, INITRG and INITEE registers. Old Freescale S12 bootloaders were moving all bootloader code from flash to RAM and remapping RAM to the vector area. Serious code modifications are required to port such S12 bootloader to S12X.