TMS320F280039C: Code Generation in ccs studio from Plecs

Hi Sairaj,

Do you have access to CCS v12 (Eclipse-based)? That is the version of CCS that is being used in the video, and PLECS may not have verified that the output project works for our new version of CCS since the video is from 2 years ago. 

It also looks like the compiler is not linking properly, can you verify that all the files that are needed to run the PLECS software example are included in the Include Paths? This is located in the project properties under Compiler/Linker. Please verify both

Regards,

Peter

Hi,

I have installed CCS studio v12 and tried to Compile the Code now the error what we are getting has been changed please find the error screenshots attached.

Regards,

Sairaj

Hi Sairaj,

Now it looks like the issue is with respect to plx_ipc_impl.h. Can you try accessing this file and making sure it is in the project files?

If you do see the file but are still getting the issues, make sure that the project is visible to the C2000 Compiler. You can verify this by looking at the C2000 Compiler > Include Options in the project properties. Below is an example of the Include Options typically in the project

Regards,

Peter

Hi peter,

we are able to compile and build the code for F280049.

To test the working as of now we have F280025C Launchpad with us as plecs does not support 2x series .is there any way we can port the generated Code from F280049 to F280025C? if yes what are the files we need to make changes.

Regards,

Sairaj

Hi Sairaj,

I'm not familiar with the structure of the PLECs generated code and how easy it would be to port. I think that is something that you may get better support directly from PLECs, in case they may have an internal package for our F28002x series that they could share to you. 

If that is not possible, it should be possible to port over the software. I think the easiest way would be to leverage our Universal Project project type from our C2000WARE example and pull in all of your current source project files into that Universal Project. Ensure it builds properly with the F28004x device then you can leverage our SysConfig migration support to automatically port to the F28002x device which will pull in all of the necessary device support files for the project.

You could either do that or try to pull in one of our F28002x blinky examples and copy over the source files for the F28004x project you have and attempt a build, then try to resolve any build warnings that come up

Regards,

Peter

Hi Peter,

iam just attaching the Code files created by plecs

 280049.zip

Regards,

Sairaj

Hi Sairaj,

Thank you for your message, we have US holiday today so I will get back to you once I return to office tomorrow. Thank you

Regards,

Peter

Hi Sairaj,

I reviewed the provided project you sent me. It looks like the code generation uses our bitfield, which makes it a little harder to port the code. For the TI provided sources like tiinc and tisrc, these can directly be found for F280025C device so you can directly replace with those. For such like linker command files, you can also use the generic ones provided in the C2000WARE SDK as that should be suitable for most use cases. For the PLECs specific driver libraries, those will have to be manually ported over

Regards,

Peter