TMS570LC4357: FreeRTOS code failing when optimized

Mark Steele

Intellectual 330 points

Part Number: TMS570LC4357
Other Parts Discussed in Thread: HALCOGEN

I am using the Halcogen generated FreeRTOS code for the TMS570LC4357 MCU. Also using TI's ARM compiler.

I set up the following example task, which runs every 1 ms and toggles a GPIO. There are no other tasks running:

The results of looking at the logic analyzer are as follows:

This result is as expected, as you can see the GPIO has a frequency of 1000Hz

Now, if I set opt_level = 2, we see the following results:

Usually the GPIO toggle behaves as expected, however, sometimes the first GPIO toggle will happen before the delay takes place. It seems as if some code is executing in the task before the task can block.

Now, if I turn off optimizations for vTaskDelayUntil (but all other code has opt_level = 2), like so:

We are back to getting as expected results:

I'm wondering, is this an issue with Halcogen's generated code? From what I've read online, FreeRTOS is able to run with optimizations using the ARM compiler. Has anyone else seen this issue?

over 2 years ago

0 jagadish gundavarapu over 2 years ago

TI__Guru* 76886 points

Hi Mark,

Can i get your complete project to debug the issue at my end?

Even you can do a private message to me by zip your project.

Thanks & regards,
Jagadish.

0 Mark Steele over 2 years ago in reply to jagadish gundavarapu

Intellectual 330 points

Hi Jagadish,

I've created a new project in Code Composer Studio, using Halcogen generated code. I've attached that project.

FreeRTOS_Opt_test.zip

The code is as follows, very similar to my previous example.

When I run with no optimizations, I see the following. This is expected behavior. GIOA6 sets when we start the task, GIOA7 toggles the entire time the task is running, and then finally GIOA6 clears once the task is finished running. The task then delays.

Now, when I turn on opt_level=2, I see the following. It appears as if GIOA6 sets right before the task should be blocking. The task actually executes sometime later.

Zoomed in, you see GIOA6 only clears for a very small amount of time:

Now, if I turn off optimizations for vTaskDelayUntil (like I did in my previous example), I see the expected results again:

0 jagadish gundavarapu over 2 years ago in reply to Mark Steele

TI__Guru* 76886 points

Hi Mark,

I kept optimization level-2 as you mentioned.

But don't know why i could not see the issue you are mentioning. Here is the output.

What is the compiler version you are using?

Thanks & regards,
Jagadish.

0 Mark Steele over 2 years ago in reply to jagadish gundavarapu

Intellectual 330 points

Hi Jagadish,

That's interesting. I'm using TI v18.12.2.LTS.

0 jagadish gundavarapu over 2 years ago in reply to Mark Steele

TI__Guru* 76886 points

Hi Mark,

Mark Steele said:
That's interesting. I'm using TI v18.12.2.LTS.

I even tested with "TI v18.12.2.LTS" but still i can't reproduce the issue you are mentioning. What about CCS version are you using latest one?

Thanks & regards,
Jagadish.

0 Mark Steele over 2 years ago in reply to jagadish gundavarapu

Intellectual 330 points

Hi Jagadish,

I am not using latest. I am using:

Code Composer Studio
Version: 9.1.0.00010

OS: Windows 10, v.10.0, x86_64 / win32
Java version: 1.8.0_144

0 jagadish gundavarapu over 2 years ago in reply to Mark Steele

TI__Guru* 76886 points

Hi Mark,

I could not see the issue you are mentioning, even with the

Code Composer Studio
Version: 9.1.0.00010

Compiler
TI v18.12.2.LTS.

Not sure why, could you please check whether the code you attached to me is right one or not?

Can you please download the attached code in this thread and test with it?

Thanks & regards,
Jagadish.

0 Mark Steele over 2 years ago in reply to jagadish gundavarapu

Intellectual 330 points

Hi Jagadish,

I just realized the issue. In the file /source/os_tasks.c, I added that #pragma to turn off all optimizations for vTaskDelayUntil and I forgot to remove it before uploading the project.