• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 82 subscribers
  • Views 161 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.

TMDSDOCK28379D: Shifting from experimenter kit to launchpad

Milarepa
Expert 1670 points
Part Number: TMDSDOCK28379D
Other Parts Discussed in Thread: LAUNCHXL-F28379D, C2000WARE

Hello,

I had written a code for TMDSDOCK28379D F28379D Delfino Experimenter Kit in CCS platform. It worked well with the hardware.

I would like to know whether the same code will work with LAUNCHXL-F28379D C2000 Delfino LaunchPad.

My second query is what are the differences between the boards. What all should we take care when we shift from experimenter kit to launchpad, keeping the code same.

My third question is when TMDSDOCK28379D  experimenter kit will be back in stock. I am ordering from India.

Thank you.

  • 0
    Mastermind 6200 points
    Milarepa said:
    I would like to know whether the same code will work with LAUNCHXL-F28379D C2000 Delfino LaunchPad.

    In principle yes. Many of the TI examples will work on both. The problem is one of pin availability.

    Milarepa said:
    My second query is what are the differences between the boards. What all should we take care when we shift from experimenter kit to launchpad, keeping the code same.

    I think you will (probably) have to work that out yourself pin by pin but there's fewer pins available on the LAUNCHPAD. For example CANA is not available on the LAUNCHPAD.

    Milarepa said:
    What all should we take care when we shift from experimenter kit to launchpad

    Pin availability notwithstanding, at least the clock crystal is different. If you've inherited from a C2000Ware demo project then define _LAUNCHXL_F28379D in predefined symbols to adapt settings in device.c.

    Also, if you are using JTAG for debugging on your controlCARD that won't be available on the LAUNCHPAD, you will have to use the on board emulator. Flashing the code takes 10x the time in my experience!

    In my view going from controlCARD to LAUNCHPAD will be a retrograde step but depends on how many outputs on your controlCARD you are prepared to disable on the LAUNCHPAD.