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.

MSP432 upload code to custom board

Other Parts Discussed in Thread: ENERGIA

I'm working on a custom board design using the MSP432 as a data logger. I'm new to custom boards and am not sure the most appropriate method of uploading code to the board. I don't think an on board debugger would be efficient in terms of board space as I will rarely be offloading data. I've written my code in energia so it would need to be compatible. I've looked up FTDI chips and they seem like a good option but I wanted to see if there was something better I should be looking at. I'm not going to be mass producing these boards.


David

  • Hi David,

    If you program through JTAG, SWD, or cJTAG you can use the XDS110. The Energia IDE supports JTAG from the XDS110 by default, but if you want to use SWD you can import the project into CCS and select the proper debugger mode. 

    Thanks,

    Mitchell

  • Thanks for the fast reply, but I'm not sure I understand your answer. Are you suggesting to replicate the XDS110 section of the evaluation board and use that as the interface between my custom board and my PC? Or do you think I should be placing my chip onto my evaluation board and programming it that way, I wouldn't want to do this because it would be a hassle whenever I wanted to offload data.

    Thanks,

    David
  • Hi David,

    I apologize for the confusion. Yes, I'm suggesting to use the XDS110-ET as the bridge between your board and PC. This will be the easiest way to upload code to your board and offload data.

    For this access, all you need to do is replicate either one of the following connectors, as shown in the image below. Connection J8 is intended for any ARM debug probe and connection J102 is intended for the XDS110-ET. I'd recommend first selecting the debugger you plan on using.

    For more details on specific debuggers, please refer to section 2.3.3 and 2.3.4 of the launchpad user's guide

    Let me know if you have any other questions or need more clarification.

    Thanks,

    Mitchell

  • I see thanks for clearing that up for me. That does seem to be the simplest solution so for now I think I'll take that approach.


    Thanks,


    David

**Attention** This is a public forum