The Memory segment FLASH of the simple_peripheral_oad_offchip and onchip projects overlap the beginning of the FLASH_BIM segment of the boot loader project.

The simple_peripheral project defines the end of the main FLASH application segment at line 244 of the linker command file <cc13x2_cc26x2_app.cmd> (also attached) and typically located at the path below
C:\ti\simplelink_cc13x2_26x2_sdk_4_30_00_54\examples\rtos\CC26X2R1_LAUNCHXL\ble5stack\simple_peripheral_oad_offchip\tirtos\ccs

This results in the allocation shown in line 16 of the linker .map file <simple_peripheral_oad_offchip_CC26X2R1_LAUNCHXL_tirtos_ccs.map> (attached), where the FLASH segment ends at address 0x561A0 (origin = 0xD0, length = 0x560D0) instead of ending at address 0x56000 (origin = 0xD0, length = 0x55F30).

This linker file was generated using the project's default linker symbols FLASH_ROM_BUILD=2, OAD_IMG_E=1, SECURITY.

This can be confirmed by the project cc26x2r1lp_bim_offchip or onchip, where the linker command file <bim_cc26x2_cc13x2.cmd> defines FLASH_BIM_START at 0x56000

This issue does not manifest itself unless the main application is larger than 0x55F30.

This could be tracked during testing by creating a RESERVED_OAD memory segment in the linker command file of the simple_peripheral projects that will cause the linker to throw an error in case any other memory segments overlap. Being in two different projects (the bim and the simple_peripheral), the linker is unaware of this overlap. Due to this same reason, the Flash loader is also unaware of the conflict.