• State Resolved
  • Locked Locked
  • Replies 13 replies
  • Subscribers 31 subscribers
  • Views 1595 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.

In circuit debugger, how do I load firmware into my own PCB with TM4C and MSP430 MCU

AJ_ee
Expert 1930 points
Other Parts Discussed in Thread: TM4C123GH6PM, SEGGER, MSP430F5529

Hello,

I have been using the TM4C123GH6PM launch pad with keil and have gotten comfortable with it. I am now in a phase where I would like to switch to designing my own board with it. My question, how will I be able to download the firmware. I know I'll do it through the JTAG pins but I noticed I couldn't find a "Stellaris Debugger" kinda like the ICD debbuger from Microchip. Maybe I'm missing something here. I have been used to working with the PIC microcontrollers in the past and I had something like a JTAG port on my PCB that I could interface directly to the MPLAB ICD3 that I could purchase from Microchip. I am looking for something like that here. I noticed that in the TM4 Launchpad, the Stellaris debugger is built in the design of the board and it looks like there are two TM4C's on the Launchpad, which kinda confused me. Anyway, could anyone please point me to right direction on how I could load the firmware now in my own PCB  (not the Launchpad). Also, I'd like to throw the same question using the MSP430. I am also using it on a different project. I will be using the IAR workbench for the MSP430 by the way.

Thanks.

AJ

  • 0
    Guru 47900 points
    As you report using IAR - your consideration of the top selling (and superior) "J-Link" should receive your attention. You may purchase a high performance J-Link from Segger - and gain a great discount by selecting the, "Student version" - and complying w/Segger's instructions.

    My firm employs the small (0.050" pitch, 2x5 pin) ARM mini header along w/this vendor's "ADA2-A" 20 (0.1") pin to 10 (0.05") pin adapter. Saves huge amount of board space - and IAR/Segger enables "SWD" - which SAVES you 2 pins for YOUR Use.

    We've no use for MSP as enlightened vendors have (long) provided Cortex M0, M0+ MCUs (way low cost) - both attach in the same way to ADA2-A.
  • 0
    TI__Guru**** 244400 points
    Hello AJ

    The ICDI binary is not a public release. You would need to either buy a standalone debug probe or jumper a TM4C12x LaunchPad. Please see the following application note for more details

    www.ti.com/.../spma075.pdf
  • 0 in reply to cb1
    Expert 1930 points
    Thank you for your response cb1. I shall look into this J-link.

    Regards,
    Aj
  • 0 in reply to Amit Ashara
    Expert 1930 points
    Thanks Amit,

    I think this can be helpful. It looks like I could create my own in circuit debugger using my TM4C. Do you have something a document similar that I can use for the MSP430?

    Actually the only reason I am also considering MSP430 for another project is the low power but if I could use ARM on both projects, I'd prefer that. Is there a low power ARM MCU you could suggest?
  • 0 in reply to AJ_ee
    TI__Guru**** 244400 points
    Hello AJ

    Which MSP430 document are you referring to?
  • 0 in reply to AJ_ee
    Expert 1930 points
    I just would like to add, with regards to the low power, the sleep current 'd like to have max is around 200uA. I'm not sure if ARM MCU could do the job for that.
  • 0 in reply to Amit Ashara
    Expert 1930 points
    Hi Amit,

    I am using the MSP430F5529 Launchpad and would like to build my own circuit board with that same MCU

    Regards,
    AJ
  • 0 in reply to AJ_ee
    Expert 1930 points
    I was wondering if maybe there is also an in circuit debugger document I could use for this, just like the one you suggested on the TM4C
  • 0 in reply to AJ_ee
    TI__Guru**** 244400 points
    Hello AJ_ee

    As I mentioned we do not publish the ICDI binary. Also the MSP430 has a different debug architecture, which may not be comprehended by the ICDI. I would suggest using an external debug probe.
  • 0 in reply to Amit Ashara
    Expert 1930 points
    Hi Amit,

    Thank you. I understand the ICDI not being public. What I will probably end up doing is using one of my TM4C Launchpad boards and use a jumper as described in the document you posted earlier to download firmware to the TM4C on my circuit board.

    As for the MSP430, I know it is not ICDI and my question is, do you have some sort of a similar document you posted earlier, in which I could probably just jumper some wires as well using the MSP Launchpad. I guess I could purchase a debug probe but this is the first time we will be using this MCU in our products and we cutting cost. The MSP is not a hundred percent go yet so I wana minimize spending and I am the only on our team who is planning to use it. If I could use that similar "jumper" technique here as the TM4C, I'd like to try that out.

    AJ
  • 0 in reply to AJ_ee
    TI__Guru**** 244400 points
    Hello AJ

    That is a question for the MSP Forum. I am specifically working on TM4C so I can guide you better on TM4C
  • 0 in reply to Amit Ashara
    Expert 1930 points
    Hi Amit,

    Oh I see, I forgot that this forum is specifically for the TM4C. My apologies. Thank you very much for your help. I appreciate it.

    Regards,
    AJ
  • 0 in reply to AJ_ee
    Guru 47900 points

    We should note that (other) ARM MCU vendors produce very low power ARM MCUs - and that by "standardizing upon ARM" - you could program ALL of your boards via the SAME "J-Link." As "J-Link" is vendor agnostic - and has been around for a long time - many judge it as superior (by far) to any (single) vendor's (very restricted) device.   Most of the "serious" helpers here employ the J-Link - and again w/greatly reduced "student pricing" (you do NOT have to be a student) - it's an unbeatable  value!

    In time the extra performance & proven robustness of the J-Link - along w/its ability to accommodate ARM MCUs from MANY vendors - is likely to prove "irresistible." (you may even note that there are (many) "pirated" J-Links (as it is SO popular) yet very few (i.e. none that I know of) pirated, single vendor, ICDI devices - likely for "good reason.")