• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 82 subscribers
  • Views 215 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

TMS320F28377D-Q1: Memory Allocation while using scheduler VS TI RTOS

Aparna Venugopal
Prodigy 130 points
Part Number: TMS320F28377D-Q1
Other Parts Discussed in Thread: C2000WARE

Hi,

I am using SYS/BIOS 6.83. I looked into the memory allocation view and wanted to find out the difference between using SYS/BIOS kernel and using a scheduler. I saw some sections LS05SARAM, M01SARAM, RAMM0, RAMM1, etc which are available only in one of the systems. (.stack is present in MS01SARAM in the SYS/BIOS project whereas it is present in RAMM1 in the scheduler project)

Could someone point me towards the resources for this memory allocation, so that I can analyze this further? I could not find details regarding this in TRM or SYS/BIOS manual.

Also, is there any option in CCSstudio which would provide details of memory usage at a higher level than that is obtained from the Memory allocation to compare the memory consumption between the two systems?

And is there any option to see stack growing in real-time, or between breakpoints? In the ROV, the stack space view only provides the stack for the Task thread. I need this for other threads like hwi and swi too.

Thanks,

Aparna

  • +1
    TI__Guru 53175 points

    You can always edit your cmd files to change the way the memory is allocated. The default linker command files that SYS/BIOS examples and templates use may be different from the ones that you get when you import a C2000Ware example, but there's no reason why you couldn't update the cmd file in the SYS/BIOS project to use the same memory names and allocations as the C2000Ware cmd file if that is preferred.

    There's a good document here if you're new to editing linker command files:

    https://software-dl.ti.com/ccs/esd/documents/c2000_c28x-compiler-understanding-linking.html

    In addition to the memory allocation view, you can always just open up the .map file in your project build folder that gets generated by the linker. I don't think the information is necessarily "higher level," but it may be easier to compare side-by-side at least.

    The stack used for Hwis and Swis are just the system stack. That stack usage can be monitored in ROV in the Hwi section--you might have to switch the view from Basic to Module to see it. You can also always just open the Memory Browser and view the stack that way.

    Whitney