• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 28 subscribers
  • Views 716 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Code migration from RM48 to RM44 by HALCoGen 04.04.00

dison wang
Expert 1620 points
Other Parts Discussed in Thread: RM48L952, RM44L520, HALCOGEN

Hi there,

I have completed a prototype development which MCU is RM48L952. Right now I want change the MCU to RM44L520 which is pin to pin with RM48L952. The hardware have been completed and past the test.

My question is

1. is there any simple way to migration from RM48 to RM44

2. I used HALCoGen 04.04.00 to generate the code for RM48 before. Is there any simple way to migrate code by set up the HALCoGen tools.

3. If I have to re-write the code or re-build a code by HALCoGen?

Thanks,

Dison

  • 0
    TI__Mastermind 49120 points
    Hi Dison,

    Unfortunately there is no easy way in HALCoGen to migrate a project from one MCU to another. You can reference this application note for understanding the significant differences between the RM48 and RM44 MCUs: www.ti.com/.../spna206.pdf

    Theoretically, as long as you are only using the modules that are common to both the MCUs, you should be able to run the same code project by just modifying the linker command file to account for the reduced flash and RAM sizes. Any exception to this is documented in the app note that I referenced.

    Regards,
    Sunil
  • 0 in reply to Sunil Oak
    Expert 1620 points
    Hi Sunil,

    Thanks for your reply.

    I just use some modules that are common to both the MCUS.

    q1, Can I down load the code of RM48 to RM44 without any change (include ccs), works?
    q2, If I create a RM44'S project of Halcogen which will share my RM48 project, and I re-generate code, what will happen?
    q3, )How can I create a RM44l520 project of CCS, because I can not find the RM44 target MCU when I want create a RM44 project of CCS.

    Thanks,

    Dison
  • 0 in reply to Sunil Oak
    Expert 1620 points
    Hi Sunil,

    My development system tool are CCS6, HALCoGen04.04, XDS100V2.
    The XDS100V2 should support the RM44L520, but I can not find the target MCU in CCS when XDS100V2 was set up as a simulation tool.
    Would you tell me the reason and what can I do?

    Thanks,

    Dison
  • 0 in reply to dison wang
    TI__Mastermind 49120 points
    Hi Dison,

    Please make sure that the latest Hercules emulation package is installed within CCS. You can normally do this by "checking for updates" and choose the latest Hercules emulation package with support for the RM44x MCUs.

    As for your other questions:

    q1, Can I down load the code of RM48 to RM44 without any change (include ccs), works?
    >> You need to recompile the source code after modifying the flash and RAM available to the CPU for program and data storage.

    q2, If I create a RM44'S project of Halcogen which will share my RM48 project, and I re-generate code, what will happen?
    >> I don't clearly understand this question. Can you please clarify?

    q3, How can I create a RM44l520 project of CCS, because I can not find the RM44 target MCU when I want create a RM44 project of CCS.
    >> Yes, please install the latest version of the Hercules emulation package for CCS v6.1.0.
  • 0 in reply to Sunil Oak
    Expert 1620 points
    Hi Sunil,

    Thanks for your reply.

    You are right, After I re-installed the ccs6.1. I got it. I also re-installed HalCoGen.

    A project was created by HalCoGen, that was shared with CCS 6.1. I generated the code and build all in CCS6.1.

    Everything was good, The JTAG passed the inspection by "test connection" button function.

    When I want download the code to MCU, I got a error which show below.

    Error connecting to the target:
    (Error -241 @ 0x0)
    A router subpath could not be accessed.
    A security error has probably occurred.
    (Emulation package 0.0.0.0)

    Could you help me to find failure point?


    Thanks,




    Dison
  • 0 in reply to dison wang
    TI__Mastermind 49120 points
    Thanks for creating a separate post for the JTAG communication issue.