Embedded Coder for ARM Cortex-R processors Problem for TMS570LC43x

Hello everyone,

I am trying to run a really simple Simulink model on a TMS570LC43X Hercules Launchpad (LAUNCHXL2-570LC43) using the "Embedded Coder for ARM Cortex-R processors" package. I am using MATLAB R2020b. You can see a screenshot of the model below:

(The block says that it accepts any data as input and internally casts it to boolean but I cast the constant into a boolean did my tests that way too just in case it is necessary.)

This model was working before but it suddenly started to not work. When I say "Build, Deploy & Run", I get this (note: name of the model is different is some screenshots):

When I say "Monitor & Tune", I get this:

I guessed that this problem was about the endianness so I started to investigate that. First of all, I changed the endianness to "Big Endian" because my kit supports Big Endian. I did it from Hardware Implementation>Device details>Byte ordering:

This didn't change anything. In fact, the linker still didn't have an option for big-endian in the diagnostic output. So I decided to modify the support package to compile and link the generated code in big-endian.

I've entered the toolbox folder and removed every single compiler and linker option for little-endian and added big-endian to the necessary parts. When I said "Build, Deploy & Run", it successfully loaded the out file to the kit:

But the kit didn't start blinking the LED. When I said "Monitor & Tune", it gave this output:

As far as I know, this file comes with the package and is not created when building. So I can't turn this file endian type by modifying the code of the package. After this, I reverted the modifications to the package.

I was considering the possibility of the kit having a problematic code and crushing before we were able to connect or upload code. I checked and saw that I can upload code from Code Composer Studio so I don't think this is the problem. I still erased the entire flash using UniFlash just in case. This didn't solve the problem either.

After this, I was considering the possibility of my com port or baud rate being wrong. I was guessing that the timeout I get on "Monitor & Tune" could be caused by this. I checked these settings and they were correct:

I tried to get one of the example models of the support package and build my model in that file to keep my configurations the same as the example. It didn't work. I added the model folder in the path, but this also didn't work. At this point, I am out of ideas.

I guess I am making a really small mistake but I can't find it. Does anyone have any idea about what might be the problem? Or can anyone who has the same kit try to use the DigitalWrite of this package and see if they have the same problem?

Answer 1

[Stella scarpetta]

Hola, lo pudiste solucionar ?