TMS570LS1224: "How can I implement the bootloader on top of a system that already runs an RTOS-based task structure

user6193261

Part Number: TMS570LS1224

Tool/software:

Hi TI team,

This is my current memory layout plan for the TMS570LS1224:

MEMORY
{
VECTORS (X) : origin=0x00000000 length=0x00000020 /* 32 B → sector 0 (0x00000–0x0001F) */
KERNEL (RX) : origin=0x00000020 length=0x00007FE0 /* ~32 KB–32 B → sectors 0–1 (0x00000–0x07FFF) */
BOOTLDR (RX) : origin=0x00008000 length=0x00010000 /* 64 KB → sectors 2–5 (0x08000–0x17FFF) */
CONFIG (RWX): origin=0x00018000 length=0x00008000 /* 32 KB → sector 6 (0x18000–0x1FFFF) */
OTA_INFO (RX) : origin=0x00020000 length=0x00004000 /* 16 KB → sector 7 (0x20000–0x23FFF) */
FILESYS (RWX): origin=0x00024000 length=0x0001C000 /*112 KB → sector 7 (0x24000–0x3FFFF) */
APP_A (RX) : origin=0x00040000 length=0x00080000 /*512 KB → sectors 8–11 (0x40000–0xBFFFF) */
APP_B (RX) : origin=0x000C0000 length=0x00080000 /*512 KB → sectors 12–15 (0xC0000–0x13FFFF) */

STACKS (RW) : origin=0x08000000 length=0x00000800 /* 2 KB SRAM */
KRAM (RW) : origin=0x08000800 length=0x00000800 /* 2 KB SRAM */
RAM (RW) : origin=(0x08000800+0x00000800) length=(0x0002F800 - 0x00000800) /* SRAM */
}

I’m currently designing a system with:

A bootloader
Two application partitions (APP_A and APP_B), both running with RTOS (FreeRTOS)
A shared KERNEL and VECTORS section
Shared regions for CONFIG and FILESYS

I have a few key questions:

How should I properly implement a bootloader on a system that runs RTOS-based tasks?
Most TI examples (like CAN bootloaders) don’t show how to integrate the bootloader with RTOS context switching or how to prepare the RTOS environment before jumping to the app.
Is it possible to let APP_A and APP_B share the same VECTORS and KERNEL memory region?
If so, how should I configure both the linker and runtime to avoid reinitializing or corrupting shared memory areas?
For regions like CONFIG and FILESYS, is it valid and safe for both applications to share and access them?
What precautions or patterns do you recommend to avoid conflict or corruption during runtime or OTA updates?

7 months ago

0 user6193261 7 months ago

Prodigy 80 points

[May 7–9]

We successfully programmed the application to its designated flash partition and observed that the jump was properly executed. However, vector-related issues remain unresolved, which continue to prevent task creation.

[May 9]

By examining the Memory Browser and CPU Registers, we confirmed that both sets of code have their own independent vector sections without overlap.
In the configuration where the Bootloader is non-RTOS and App-A uses RTOS, task creation failed due to the prvRaisePrivilege() function failing to trigger the vPortSWI (SVC Handler). This caused the execution to loop endlessly at svcEntry within the bootloader section.
We then revised the architecture so that both the Bootloader and App-A are RTOS-based. Under this setup, the SVC call successfully transferred control, and the system no longer entered the svcEntry loop. However, when the system reached vTaskStartScheduler(), the function was not entered for unknown reasons. We confirmed at the assembly level that the function was compiled and present in the flow, but it was skipped during execution.

0 user6193261 7 months ago

Prodigy 80 points

Eventually, we resolved the issue by explicitly disabling FIQ and IRQ in the bootloader, and re-enabling them later in App-A. With this adjustment, the entire system was able to run correctly.

0 user6193261 7 months ago

Prodigy 80 points

Although the system is currently running, we are still in the process of validating the full functionality of the application.
If there are any critical considerations or best practices we should follow—particularly regarding interrupt enable/disable handling and vector management across the bootloader and application—we would be sincerely grateful for your guidance.

0 user6193261 7 months ago

Prodigy 80 points

Additionally, I would like to highlight that the current stable setup involves both the bootloader and App-A being RTOS-based.
When the bootloader does not run RTOS and attempts to launch an RTOS-based application, the system still fails at the SVC transition stage—specifically, it cannot branch correctly from prvRaisePrivilege() to vPortSWI, causing a persistent loop at svcEntry.

0 jagadish gundavarapu 6 months ago in reply to user6193261

TI__Guru 72836 points

Hi,

Sincere apologies for the delayed response.

Unfortunately, i don't have any ready example to share regarding this requirement.

However, i helped some of the customers in the past with Bootloader+RTOS application, i am sharing those threads here and i am requesting to refer them once. Because these threads might be useful for you.

(+) TMS570LC4357: TMS570LC43x Bootloader Transition to RTOS Application: Unexpected SVC Entry - Arm-based microcontrollers forum - Arm-based microcontrollers - TI E2E support forums

(+) TMS570LS3137: Bootloader FreeRTOS program - Arm-based microcontrollers forum - Arm-based microcontrollers - TI E2E support forums

(+) TMS570LC4357: freertos bootloader application getting problem in I2C - Arm-based microcontrollers forum - Arm-based microcontrollers - TI E2E support forums

--
Thanks & regards,
Jagadish.