• State TI Thinks Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 2 answers
  • Subscribers 31 subscribers
  • Views 974 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.

Original question:

TMDSEMU110-U: How to control XDS110 GPIO pins?

TMDSEMU110-U: GPIO control for embedded XDS110

Sebastian Brueckner
Intellectual 395 points
Part Number: TMDSEMU110-U
Other Parts Discussed in Thread: AWR1642, , EK-TM4C1294XL

Hi,

I found the the ability of the TMDSEMU110-U to control a few GPIO pins to be very useful (e.g,. to control AWR1642 SOP pins).

For an embedded XDS110 debugger: What pins of the Tiva MCU can be used to replicate the GPIOOUTx pins of the TMDSEMU110? Are there any additional requirements to get this to work with the XDS110 firmware and dbgjtag.exe PC tool?

Best regards

Sebastian

  • 0
    TI__Guru**** 171309 points

    Sebastian,

    You should use PF0 through PF3, but make sure you use a buffer to avoid any damage to the device. 

    These pins match the GPIO numbers mentioned in the XDS110 User's Guide (SPRUI94).

    Hope this helps,

    Rafael

  • 0 in reply to desouza
    Intellectual 395 points

    Hi Rafael,

    I can't get it to work. Maybe you can spot the problem. Here is what I am doing.

    On the PC I am running this batch file to toggle GPIOOUT0..1 on and off:

    :loop
dbgjtag.exe -f @xds110 -Y gpiopins,config=0x3,write=0x3
dbgjtag.exe -f @xds110 -Y gpiopins,config=0x3,write=0x0
goto loop

    As a first test, I connect the original TMDSEMU110-U with the little AUX breakout board and apply 3.3V to TGTVDD(SENSE). I can see a square wave on GPIOOUT0 and GPIOOUT1 using an oscilloscope - as expected.

    To try the same on custom hardware, I am using an EK-TM4C1294XL launchpad. I installed a 16 MHz crystal and flashed the XDS110 firmware. The board correctly shows up as XDS110 on the PC and the xdsdfu and dbgjtag tools will talk to it without a problem.

    Running the batch scripts now, I see no activity on any of the PF0..3 pins, they all sit at 0V.

    Reading back the GPIO config after running the batch file always returns 0 (on the TMDSEMU110, I see the config value 0x03 as set from batch file):

    dbgjtag.exe -f @xds110 -Y gpiopins -v

-----[Print the board config pathname(s)]------------------------------------

xds110.i

-----[Print the controller-open software log-file]---------------------------

The library build date was 'Jan 24 2019'.
The library build time was '14:27:46'.
The library package version is '8.0.903.6'.
The library component version is '35.35.0.0'.
The controller does not use a programmable FPGA.
The controller has a version number of '5' (0x00000005).
The controller has an insertion length of '0' (0x00000000).
The user GPIO pin config is 0x00.
The user GPIO pin input is  0x00.

    What am I doing wrong? Do the version pins PK4..7 need to be set to a specific value?

    Thanks for your help

    Sebastian

  • 0 in reply to Sebastian Brueckner
    Intellectual 395 points

    Hi,

    I still wasn't able to set any GPIOs on my custom XDS110 hardware.

    Is there some kind of sense pin for target system voltage that needs to be connected? Or some form of GPIO readback?

    Any help is appreciated.

    Sebastian