• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 31 subscribers
  • Views 451 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

SYSCONFIG: How to do a "clean" SysConfig-based project migration from AM2434_ALV to AM2434_ALX (same part, different package)

Tilman
Prodigy 110 points

Part Number: SYSCONFIG
Other Parts Discussed in Thread: AM2434

Tool/software:

Hi TI, dear fellow engineers,

My question aims at getting a better understanding of how to correctly migrate an existing SysConfig-based example project from one device package to another.

I do have Code Composer Studio Version 12.8.0.00012 installed, my SysConfig is v. 1.21.0.

I want to migrate the example project epwm_duty_cycle_sync_am243x-evm_r5fss0-0_nortos_ti-arm-clang, which is configured to be used with the general-purpose Evaluation Module AM2434-EVM.
I want the project to be used with AM2434-LP instead.
AM2434-EVM has AM2434 in the ALV package.
AM2434-LP has AM2434 in the ALX package.

So my basic assumption is this:
A migration from AM2434_ALV to AM2434_ALX should be possible without major problems, as the two devices basically have the same silicon, just in a different package. Please correct me on this, if I am wrong.

To make a long story short:
Looking at the final result I did succeed in the project migration (got the very same physical output on the Launch Pad, as I do on the EVM).

BUT: the following issues leave me with doubts on whether the way I got there is correct:

Issue #1:
After importing the project I change the device package configuration in SysConfig:

This does result in the following error message:
"Error encountered while migrating project 'epwm_duty_cycle_sync_am243x-evm_r5fss0-0_nortos_ti_arm-clang': Target 'AM2434_ALV' has no cores with the ID 'r5fss0-0' - migration operation aborted!

This error message sounds a bit strange to me, because physically AM2434_ALV for sure has an R5FSS0-0 core. But I do understand, that I need to do also reconfigure the target configuration and possibly some flags.

So I carry on by changing the target configuration from AM2434_ALV to AM2434_ALX and in addition to that under "project properties" --> "SysConfig" --> "Miscellaneous" I change two flags as follows:

After these changes and adjustments on my part, the project compiles without errors or warnings. The project can be used with AM2434-LP and delivers the desired results without any visible problems.


Issue #2:
After doing all of the above, in the "Project Properties" no change has been applied to the original device variant:

It is still the original device configuration, using AM2434_ALV, even though the package has been changed in SysConfig before.

So to sum it all up:
How would I correctly migrate that project?
Can a project be migrated like this at all, or is what I did simply not intended to be done like this?
Why does the device variant remain unchanged in the "Project Properties"?

Thank you for your support!

  • +1
    TI__Guru 62858 points

    Hi Tilman,

    Thanks for your query.

    I will suggest to create a project using the empty project already provided in the MCU+SDK.

    Import the empty project for AM243x ALX and copy the epwm_duty_cycle.c file in the project and modify the code accordingly.

    After that open the example.syscfg file and configure the parameters accordingly by taking reference from existing epwm example provided for AM243x ALV and take reference from datasheet to see the exact pin details.

    This way you will not need to update the project settings in CCS as the imported project is already configured for AM243 ALX package.

    Hope the above information helps.

    Regards,

    Tushar

  • 0 in reply to Tushar Thakur
    Prodigy 110 points

    Hi Tushar,

    thank you for your answer.

    I guess that's a feasible solution.

    So what I take away from this case:
    SysConfig can and shall be used to configure new projects.
    The use of SysConfig to change/modify exisiting projects has limits and may result in artifacts from the original project remaining in the modified project.

    Thanks again.

    Regards,
    Tilman