VisualGDB not finding Olimex Tiny info

[jhinkle]

Attempting my first try at Visual GDB with embedded ESP8266

Using Olimex OpenOCD JTAG ARM-USB-TINY-H — the device shows up twice in “Device Manager”.

Using Win7

The following errors occur when I attempt to start the debugger:

 

Open On-Chip Debugger 0.9.0 (2015-11-04-20:38)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
trst_and_srst separate srst_gates_jtag trst_push_pull srst_open_drain connect_deassert_srst
adapter speed: 1000 kHz
stop_wdt
Error: libusb_get_string_descriptor_ascii() failed with LIBUSB_ERROR_NOT_FOUND
Error: no device found
Error: unable to open ftdi device with vid 15ba, pid 002a, description ‘Olimex OpenOCD JTAG ARM-USB-TINY-H’ and serial ‘*’

 

I’m lost as to where to start looking for a direction to resolve this.

Any help appreciated – thanks.

 

 

[jhinkle]

I think I resolved it.

 

Got Zidag and it loaded the Olimex driver.

[jhinkle]

Next issue …

VisualGDB flashed the ESP-03 but display the following information:

trst_and_srst separate srst_gates_jtag trst_push_pull srst_open_drain connect_deassert_srst
adapter speed: 1000 kHz
stop_wdt
Info : clock speed 1000 kHz
Info : TAP esp8266.cpu does not have IDCODE
Info : halted: PC: 0x4000118c
Info : debug cause: 0x20
Info : accepting ‘gdb’ connection on tcp/3333
Info : TAP esp8266.cpu does not have IDCODE
Warn : xtensa_poll: DOSR has set InOCDMode without the Exception flag. Unexpected. DOSR=0x04
target state: halted
Info : halted: PC: 0x4000118c
Info : debug cause: 0x20
Warn : xtensa_deassert_reset: ‘reset halt’ is not supported for Xtensa. Have halted some time after resetting (not the same thing!)
Info : halted: PC: 0x40005668
Info : debug cause: 0x1
Info : halted: PC: 0x4010013c
Info : debug cause: 0x8
Info : halted: PC: 0x4010013c
Info : debug cause: 0x8
Info : halted: PC: 0x4010013c
Info : debug cause: 0x8
Info : halted: PC: 0x4010013c
Info : debug cause: 0x8
Info : halted: PC: 0x4010013c
Info : debug cause: 0x8
Info : halted: PC: 0x4010013c
Info : debug cause: 0x8
Info : halted: PC: 0x4010013c
Info : debug cause: 0x8
Info : halted: PC: 0x4010013c
Info : debug cause: 0x8
Interrupt suppression during single-stepping is now enabled
Watchdog feeding during stops is now enabled

 

My break point was never reached so the ESP has crashed or not running.

I connected the jumper pads on the ESP-03 which allows GPIO16 to manipulate the RESET pin.

I have connected GPIO16 to jtag pin 3

I’ve connected GPIO0 to vcc (thru a resistor).

GPIO15 to vcc  (thru a resistor).

I believe GPIO0 and GPIO15 are proper — if not — please tell me.

I’ve loaded the HTTP RTOS server as the test program.

I’ve “break all” and went to see the hardware registers to check the IP — but non have been implemented.

Are the ESP8266 hardware registers going to be available in the future?

Without access to the registers I have no idea as to the IP location … locked?  running??

I know it never entered “user_init”

Any comment appreciated.

 

 

[jhinkle]

Update

Changed Reset in debug properties to “Reset Chip”.

It never breaks at my breakpoint in “user_init” but does break on its own in the “ServerTask” … note ServerTask is created and started from user_init() so it does not make sense.

the following is reported when the break occurs: Received a SIGTRAP: Trace/breakpoint trap.

Any comments appreciated.

 

[jhinkle]

Went back to debug – “Emulate a CPU reset”

help?

[jhinkle]

Update

Started a new project

ESP8266-NOFLASH –> Blink LED

All works as expected.

So what’s happening to the HTTP Server – RTOS project?

 

[jhinkle]

Update

Started another new project

ESP8266 -> Blink Led using IoT sdk.

It locks/fails just like the HTTP – rtos project.

 

So running out of ram seems to work OK — but — bring in the sdk and it fails.

Are this good proven projects?

 

[support]

Hi,

Please try experimenting with the FLASH type, speed and size settings. The default ones are valid for the Olimex ESP8266 board and different settings may be required for ESP-03.

[jhinkle]

Where do you set/change the flash FLASH type, speed and size settings.

I have looked in properties and fond nothing.

Thanks in advance to informing me.

[jhinkle]

Sorry – found them.

 

The settings are correct – they are the same when flashing the chip using esptool.

 

[support]

OK, first of all, we did test all the projects on the Olimex board, so it is probably some small configuration issue with ESP-03. In order to resolve it, you need to localize the problem. It can be in one of the following places:

• FLASH programming never happens
• FLASH programming succeeds, but starting the program fails
• The built images are wrong
• The program fails to start with JTAG attached

To figure this out, please try the following:

1. Change the firmware to turn on the LED, disable interrupts and wait indefinitely
2. Try programming the firmware. If it does not start, unplug the board and plug it back. Does the LED turn on?
3. If yes, try debugging it with no FLASH programming. Does this help? If yes, try changing the reset mode in VisualGDB Project Properties.
4. If the programming does not turn on the LED, try programming the same .bin images (not the .ELF file) using esptool. Does this work? If yes, something breaks programming and the full GDB log might provide answers.

If you encounter any difficulties at any point, please feel free to share the details and we will try to help you.

[jhinkle]

ESP-03 is the same as the Olimex ESP8266 board.

Any other suggestions?

My trial period is up soon and I have not got things to work yet.

Thanks.

 

 

[support]

Hi,

It’s hard to suggest anything without seeing the outcome of the tests suggested above. We have ordered a bunch of ESP-03s and will make a tutorial once they arrive.

If you need a trial extension, simply use the contact form on our website and mention this thread and we will extend your trial.

[jhinkle]

I would like to use this program — but only if I can get it to work.

I gave up on jtag and setup for gdbstub using a serial port.

Compiled and flash OK but the GDB Session failed to start with error: “Program is not being run”.

Any ideas.

Thanks.

 

[jhinkle]

More info

Connecting to GDB stub …

too long

target remote //./COM3

I tried at both 74800 and 115200 baud … both behaved the same way.

Again — flashed OK — just not debug.

 

[Author]

Posts