Vector table in RAM

Charles said:

I have been able to re-locate the vector table into RAM via the Xlink cmd file but I don't know how to inform the Xlink how to generate a ROM copy. I also then need to inform the startup code that it needs to copy the ROM copy to RAM. I was thinking I could use the DATA16_I and DATA16_ID but the documentation states that the data is packed in under the discretion of the linker and that will not force the vector to the correct address in RAM. Is there a way I can generate my own segments and inform the startup code about these new segments?

Page 48 of the IAR Linker and LIbrary Tools Reference Guide discusses the use of the -Q segment command to perform scatter loading.

Charles said:

I was also thinking that my boot-loader could do the copying if required but it would be nice if the startup code can do it.

Good thinking, because your boot-loader code will need to do it.  An example of a what it could be done is illustrated on page 49 of the IAR Workbench IAR Linker and Library Tools Reference Guide.