We are trying to map the code in question to a specific area in memory between the boot code and main code, so that it can be used by both the bootloader and main application.

I believe you are on the wrong track. It is much better to make independent bootloader and application parts of code, 2 projects for both, 2 independent compiler/linker settings for both, etc. MCU boots always to bootloader. Bootloader checks validity of loaded application code and either jumps to app or keeps waiting for bootload commands. Application on receipt of boot command restarts MCU and somehow signals bootloader that it shouldn't jump back to app. But please don't ask me how and why, it was discussed already so many times.

.sbss and .sdata are similar to .bss and .data, but data in these sections are accessed using shorter "Address Register Indirect with Displacement Mode" addressing mode. A5 register is initialized at startup and points to sbss/sdata sections. Variables are addressed relative to sbss/sdata sections. This allows to save some code space.

Thank you, Edward, this is very helpful. Do you know how/if it is possible to disable the Address Register Indirect with Displacement Mode in CodeWarrior 10? Would changing the Code and Data models in the C/C++ Build Tools Settings have this effect?

We are trying to map the code in question to a specific area in memory between the boot code and main code, so that it can be used by both the bootloader and main application. It sounds like this indirect addressing may be problematic, since the boot loader and main application are compiled seperately.

We are trying to map the code in question to a specific area in memory between the boot code and main code, so that it can be used by both the bootloader and main application.

I believe you are on the wrong track. It is much better to make independent bootloader and application parts of code, 2 projects for both, 2 independent compiler/linker settings for both, etc. MCU boots always to bootloader. Bootloader checks validity of loaded application code and either jumps to app or keeps waiting for bootload commands. Application on receipt of boot command restarts MCU and somehow signals bootloader that it shouldn't jump back to app. But please don't ask me how and why, it was discussed already so many times.