TMS320F28P650DK: FreeRTOS in CCS 12.7.1

Hello,

This expert is out of office. Please expect some delay in response until 8/20.

Best Regards,

Allison

Hi Avinash,

A few clarifying questions, which version of C2000Ware are you using?

1. Is the device entering low power mode at any point in your application? Which optimization level are you using? I have verified that CCS is able to place breakpoints in a standard FreeRTOS application (you can try one of the Demos included in C2000Ware)

2. What is the tick rate you have configured in FreeRTOSConfig.h? It is not recommended to go above 1000Hz, since most of the time will be spent switching tasks in the tick interrupt handler itself. For tasks which need a higher execution frequency, you can setup a separate timer with the reqd. frequency that will unblock this task. Note that the task priorities will also play a role here. 

Thanks,

Arnav

Hello Arnav,

                     we are using C2000Ware_5_02_00_00 version.

1.Yes the device entering low power mode when i try to put breakpoint in my newly added/derived files.Optimization level is off as shown in the snapshot below.

2.Tickrate i will configure 1000 Hz and will let you know the task behaviour.

Arnav, is it possible for you to connect over teams call? Please let me know.

Best Regards,

Avinash 

Hello Arnav,

                    Issue 1.below error while debugging and when we try to put breakpoint.

For the above issue i tried the following:

As i was not able to put the breakpoint in newly added files which has freeRTOS tasks in it. To solve this, i removed many other models (modules like EPWM,ADC,EQEP ,CAN,SPI, CPU Timer1) which were configured in SYSCONFIG and with that i have also deselected clocks of many modules which were configured in SYSCTL of SYSCONFIG in ccs studio. After removing this i rebuild it and i was able to put breakpoints in debug mode in the tasks of freeRTOS.

Using above steps the issue got resolved.

     Best Regards,

       Avinash

Hi Avinash, 

Good to hear. Considering our offline discussion as well, I will close this thread. Please feel free to open a new one if further issues should arise.

Thanks,

Arnav

Hello Arnav,

                    When i reconfigured and integrated only ADC Module to the existing project the same issue i am observing.The issue not yet resolved..please help here..

Best Regards,

Avinash 

Hi Avinash,

Can you attach an image of the debug call stack on pausing the program? Is the application still going into reset like it was during the call, or are you seeing the low power mode issue? If it is the former, further debugging would be needed to find where the reset is being triggered.  

Thanks,

Arnav

Hello Arnav,

                     I have attached the image of debug call stack after pausing the program. After pausing the program i am seeing _system_post_cinit message as in the image attached.after this when i try to remove/add breakpoint from freertos tasks am getting the error "device may be operating in low power mode.

Please check this and help resolve this issue ASAP.

Best Regards,

Avinash

Hello Arnav,

                     I have attached the image of debug call stack after pausing the program. After pausing the program i am seeing _system_post_cinit message as in the image attached.after this when i try to remove/add breakpoint from freertos tasks am getting the error "device may be operating in low power mode.

Please check this and help resolve this issue ASAP.

Best Regards,

Avinash

Arnav Menon R: This _system_post_cinit  issue got resolved by increasing memory for freeRTOS in RAM_lnk_cmd file. 

Currently I have configured 2 tasks of 1ms and 10ms(with preemption and time slicing enabled), but only 1ms task which is created first is running.

Priorities changed and also tried with equal priority, but behaviour is same.Only one task is running all the time.Task switching not happening.

 Help here pls.

Best Regards,

Avinash

Hi Avinash,

Please check if 

1. The tasks are all created successfully - check the value returned from the task create function

2. The tick interrupt is occurring as expected - place breakpoints inside xTaskIncrementTick (tasks.c) and portTickISR to check if it is being hit periodically

Thanks,

Arnav