ESP8266 Community Forum

- Tue Oct 14, 2014 3:25 am #1593 Yes thats also what was told to me at the openocd irc channel.
Still wondering if johnsmirl just misread/misunderstood something or if he found openocd with xtensa support somewhere...

Would be great to have debugging on the ESP and if I knew that beforehand that no official openocd support for xtensa exists I wouldn't had
put this expensive FT2232H on my devboard (And ordered the parts) . But well thats alone my fault I didn't checked that before and took some forum claims for serious ....

- Tue Oct 14, 2014 6:52 am #1612 I had found a web page describing OpenOCD on xtensa. I had not tried because I had no hardware at that time. I can ask on the xtensa mailing list and see what they say.

Where I get my modules

- Tue Oct 14, 2014 10:49 am #1618 The Xtensa Tools OCD Daemon supports FT2232 (or at least some way of hooking it up). And it's not licensed. Not sure about redistributing the installer, but if someone picks up the latest Xtensa Tools software eval, it's in there.
http://ip.cadence.com/support/sdk-evaluation-request
Works best with the Xtensa Tools GDB (xt-gdb, also in there) rather than the mainline GDB version, and xt-gdb isn't licensed either.

- Fri Nov 28, 2014 12:20 am #3435 I've connected FTDI 2232-based JTAG probe to ESP-03 and connected to it with xt-ocd + xt-gdb.
Used ARM-USB-TINY-H probe and the following topology.xml:

Code: Select all<configuration>
  <controller id='Controller0' module='ft2232' probe='flyswatter' vid='0x15ba' pid='0x002a' usbser='OLVGHYS?' speed='10MHz'/>
  <driver id='XtensaDriver0' module='xtensa' step-intr='mask,stepover,setps' />
  <chain controller='Controller0'>
    <tap id='TAP0' irwidth='5' />
  </chain>
  <system module='jtag'>
    <component id='Component0' tap='TAP0' config='trax' />
  </system>
  <device id='Xtensa0' component='Component0' driver='XtensaDriver0' />
  <application id='GDBStub' module='gdbstub' port='22000'>
    <target device='Xtensa0' />
  </application>
</configuration>


It kind of works, at least I'm able to dump/change memory or write to peripheral registers and see signals on output pins.
It's not very stable though, sometimes it gets reset or its debug FSM starts jumping between 'stopped' and 'debugged' states.