• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 53 subscribers
  • Views 1091 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.

Connecting MSP430FR4133 GDB on linux

Mathews John
Prodigy 105 points

Other Parts Discussed in Thread: MSP430FR4133

I am fairly new to the community and got an MSP430FR4133 to learn how to code on an MSP. I followed the instructions on the manual . I am able to compile and create an object using the makefile suggested but I am not able to flash it into the the MCU.


I ran gdb_agent_console and it gets stuck while it's waiting for client

>gdb_agent_consol msp430.dat

Successfully configured msp430.dat
CPU Name             Port
--------             ----
MSP430              :55000

Starting all cores
CPU Name             Status
--------             ------
MSP430               Waiting for client

I can confirm that my board is connected to the computer

>lsusb

Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 002: ID 2047:0013 Texas Instruments
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 005: ID 413c:8160 Dell Computer Corp. Wireless 365 Bluetooth
Bus 003 Device 004: ID 413c:8162 Dell Computer Corp. Integrated Touchpad [Synaptics]
Bus 003 Device 003: ID 413c:8161 Dell Computer Corp. Integrated Keyboard
Bus 003 Device 002: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth)
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

From what I understand gdb_agent_console creates a virtual port of sorts so that I can communicate with the device on the USB. Is there any way to direct the gdb_agent_console to the USB port to which the board is connected? 

  • 0
    TI__Guru**** 173310 points

    After starting the GDB agent, did you follow the next steps listed in the Users Guide: "4.6.3.2 Debugging with GDB"? That should allow you to run and debug a program.

    If you still have trouble after following those steps I would suggest posting to the MSP forums. Their team creates that User Guide and they will have the expertise to address further questions.

  • 0 in reply to AartiG
    Prodigy 105 points

    AartiG,


    Thanks for the reply. I could not figure out the role of gdb_agent_console until today.

    For someone who is stuck in the same position as I am:
    gdb_agent_console acts as a virtual server of sorts. When you are in debug mode, target remote :55000 makes calls to this console.  Debugging is then done through this connection. So before you run the debugger, have the gdb_agent_console running on another terminal.