• State TI Thinks Resolved
  • Locked Locked
  • Replies 8 replies
  • Answers 1 answer
  • Subscribers 32 subscribers
  • Views 1291 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.

CCS/TM4C1230C3PM: Code programed by TM4C123GH6PM can't run on TM4C1230C3PM platform

Iris Lu
Prodigy 130 points
Part Number: TM4C1230C3PM
Other Parts Discussed in Thread: TM4C123GH6PM,

Tool/software: Code Composer Studio

I use the origine code in TM4C123GH6PM launch pad, and can run well in TM4C123GH6PM plateform now, but don't work in TM4C1230C3PM plateform.

Is there any way such as modify the associated configuration file to migrate code.

  • 0
    Guru 13040 points

    Hi,

    Did you try to modify the target part number on the project's properties?

    Regards

    Bruno

  • 0
    Guru 117855 points

    As firm/I are "No fan" of CCS - that approach is ceded to friend/poster Bruno.

    To migrate code properly (w/best chance of success) - is it not your responsibility to insure:

    • each/every Peripheral present in the original code "continues" w/in the new MCU
    • each/every MCU Pin - specified by the original code - appears in that same location & capability - w/in the new MCU
    • all "timings" w/in the original code are achievable w/in the new MCU.    Should the new MCU run @ higher system clock - have allowances been made?
    • are all critical "Power, Analog, Hibernate Pins" properly managed - both in terms of pin location & specification - w/in the new MCU's board design?

    A simple "IDE click" - minus the disciplined/aware method/guide (listed above) - may not (fully) pave the road to (migratory) success...    (i.e. "some" (slight) consideration must be granted to "any/all differences" between the two MCUs.)

  • 0
    TI__Guru 72500 points
    "Doesn't work" does not give any details. The TM4C1230C3PM is a subset of the TM4C123GH6PM. If the device is stuck in a data abort, check to see if the code is using a peripheral that is not on the TM4C1230C3PM such as the second CAN module or the PWM.
  • 0 in reply to Bob Crosby
    Guru 117855 points

    Post is derivative of that (hour earlier) noting, "each/every Peripheral present in the original code "continues" w/in the new MCU."

    Should not (some) attribution be (fairly) granted?       (leads to, "Are earlier arriving postings (even) read?"   Mentioned as this is NOT 1st occurrence of such...)

  • 0 in reply to cb1_mobile
    Guru 13040 points
    **LIKE**
    A much better reply than mine, indeed!
    A simple change of part number can make things work... or burn something! :)
  • 0 in reply to Bruno Saraiva
    Guru 117855 points
    Thank you, Sir. Improper to say "better" - "different - perhaps more encompassing" seems to work as well.

    Note that, "Repetition is the sincerest form of flattery" - and the (first) key point was "repeated" by another - minus ANY attribution!
  • 0 in reply to cb1_mobile
    TI__Guru 72500 points
    Yes, CB1, you are right on the mark. I just wanted to emphasis some of the differences. Thank you for your prompt and correct reply.
  • 0 in reply to Bob Crosby
    Guru 117855 points
    Thank you - appreciated.
    While "differences" (were) to receive "emphasis" - the "lack of previously employed peripheral" was in no way "different!"

    Far better method is to note one's "agreement" w/previously noted point (which reinforces) - rather than "restate that which has been previously presented" w/out comment - which confuses & confounds...