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.

Need support for MSP432, GDB_AGENT, using msp-fet

Other Parts Discussed in Thread: MSP-FET

I see that the msp-fet supports the msp432p401x chips.

I have the LP and the XDS110 is working fine.  I also have a msp-fet with the adaptor that I am testing out for our prototypes.

the prototypes are 1.8V and we won't be able to use the XDS.  So I'm testing out the msp-fet.

I need a gdb_agent with appropritate configuration file to run against the msp-fet connected to the msp432p401.

this is on a linux box.

any suggestions?

  • Hi Eric,

    Not really sure why you can not use the XDS110, could you please give us more information on this?? I ran a few test using the xds110 that comes on the RED MSP432 LP and I was able to program/debug another MSP432 with external voltage of 1.8v.

    Anyway I'll discuss this (gdb_agent support) with the tools team because I'm not sure if there is a plan to support this in the near future.

    Regards,

    David
  • Hi David,

    thanks for looking into this and trying your experiment.

    The XDS110 (which runs at 3.3V) connected to the JTAG pins on a 1.8V msp432p401x turns out will power the msp432 to 3 volts through the JTAG I/O pins through the clamps that are put on i/o pins.

    So what happens is even though the msp432 is powered from a 1.8 V power supply when any of the jtag pins are at 3.3 V the chip will be powered at the higher level.

    this doesn't work for a 1.8V design.
  • Hi David,

    thanks for passing on the request up the chain.

    we'd prefer to stay with TI tools for our needs. So if TI did enhance gdb_agent to support the msp-fet with the msp432 cpus that would be most excellent.

    gdb_proxies (like gdb_agent_console) is the way the rest of the world debugs low level using the gnu tool chains. The other emulators we've looked at support gdb_proxies (ARM direct and SEGGER). But we'd prefer to use TI products with TI chips.

    We know that the h/w paths all work because we have made use of the msp-fet with the msp432 under CCS 6.1.3 and that all works. But we really want to move away from CCS (too complicated) to pure gdb talking to a gdb_proxy.

    So if there is a way to figure out the configuration for gdb_agent to make use of the msp-fet talking to a msp432, that would be perfect.
  • Hi David,

    Or anyone.... Any movement on this? Any more information?

    Sure would be nice if I could use all the msp-fets that we bought for our msp432 (1.8v) design.
  • Hey Eric,

    sorry for letting you wait but we had to collect some more information.

    Currently, we are not planning to enhance the GDB agent to support MSP-FET and MSP432 MCUs.

    However, we have a solution to your issue. As announced here there will be a new full featured standalone version of the XDS110 which would also support 1.8V. We expect the standalone XDS110 debug probe to be publicly available in November time frame. This new debug probe is already supported with the currently available MSP432 GCC Support Package 1.0.0.1

    In case this is too late for your prototyping, we could send you a pre-production unit.

    Best regards,

    Bob

  • Hi Bob,

    we would like to take you up on the pre-production unit.

    Is there a schematic we could look at?



    also there are some issues with the MSP432 GCC Support Package 1.0.0.1. I'll submit those under a seperate note tonight.
  • Hi Bob,

    haven't heard anything from anyone on this. Not sure if something got lost in the ether. Could you poke the folks again? thanks.
  • SDO does not support the MSP-FET probe. It is my understanding that we will not be adding that support to GDB Agent. The long term plan is to drop GDB Agent altogether for GDB support through Open OCD.
  • Edward Fewell said:
    SDO does not support the MSP-FETprobe. It is my understanding that we will not be adding that support to GDB Agent. The long term plan is to drop GDB Agent altogether for GDB support through Open OCD.

    Sounds like a good plan.

    I've tried using openocd with the xds110 and haven't been able to get it to function reliabily.

    Do have an openocd configuration that will work with the xds110 and/or the msp-fet that I can help you debug?

  • The XDS110 can be used via the CMSIS-DAP support already in OpenOCD (be sure to use 0.9 or later, the performance in 0.8 was very poor).  Native support for XDS110 is in development, and there is nothing yet to try.

  • Edward Fewell said:

    The XDS110 can be used via the CMSIS-DAP support already in OpenOCD (be sure to use 0.9 or later, the performance in 0.8 was very poor).  Native support for XDS110 is in development, and there is nothing yet to try.

    what exactly do you mean by "native support"?

    I've tried using 0.9 OpenOCD with the XDS110-ET and found it unusable, too slow, buggy (repeated crashes/hangs) etc.

  • Hi Edward,

    do you have an openocd configuration for the XDS110-ET that you know works? Can you please send it to me?

    thanks,

    eric
  • Support for XDS110 under OpenOCD is still in development and not expected to be complete until first quarter 2017.

  • Hi Ed,

    I've recently bought a stand alone XDS110 to try with openocd. We need a gdb server and can not use Code Composer (our source code really won't fit into an IDE).

    We have an XDS110 with CMSIS-DAP f/w version 2.3.0.5. I'm using it with the released version of OpenOCD (0.10.0) as of SHA 646566e. I'm using this with a Rev 2 MSP-EXP432P401R launch pad.

    The performance of the on board XDS110-ET is really slow but it seems to work (f/w 2.3.0.3) swd, jtag doesn't work.

    with the standalone XDS110, I haven't been able to get it to work at all.

    The wiki page as well as the product page clearly states that openocd is supported.

    Is this working in house?
  • What target are you trying to connect using the standalone XDS110?  We would expect the XDS110 standalone to work via the CMSIS-DAP interface, but it has not been tested for that. 

**Attention** This is a public forum