search

espressif / esp-idf

Espressif IoT Development Framework. Official development framework for Espressif SoCs.
Apache License 2.0
13.33k stars 7.2k forks source link

[TW#24178] Error in set up of the environment for Wrover Kit in Eclipse. #2151

Closed AmbimatElectronics closed 6 years ago

AmbimatElectronics commented 6 years ago

Environment

//Detailed problem description goes here. Ans:- please find attachment debugg error in eclipse eclipse juno error

igrr commented 6 years ago

Please check that OpenOCD is running and port 3333 is not blocked by the firewall.

AmbimatElectronics commented 6 years ago

Hello,

The port is not blocked.

Not sure how to check if the OpenOCD is running or not.

Neel.

On 05-Jul-2018, at 9:05 PM, Ivan Grokhotkov notifications@github.com wrote:

Please check that OpenOCD is running and port 3333 is not blocked by the firewall.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/espressif/esp-idf/issues/2151#issuecomment-402763444, or mute the thread https://github.com/notifications/unsubscribe-auth/AeQORukrtFbUxV4PDOnObC-BFze9Lmpxks5uDjJIgaJpZM4VDOkW.

igrr commented 6 years ago

Hi @AmbimatElectronics, to check whether OpenOCD is running, i think you can try using Task Manager. Also you can open the command line window where you started OpenOCD, and check that it has not crashed or exited; the output should look like:

Open On-Chip Debugger 0.10.0-dev (2018-06-05-14:52)
Licensed under GNU GPL v2
For bug reports, read
    http://openocd.org/doc/doxygen/bugs.html
none separate
adapter speed: 20000 kHz
esp32 interrupt mask on
force hard breakpoints
Info : ftdi: if you experience problems at higher adapter clocks, try the command "ftdi_tdo_sample_edge falling"
Info : clock speed 20000 kHz
Info : JTAG tap: esp32.cpu0 tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)
Info : JTAG tap: esp32.cpu1 tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)
cpu0: Current bits set: BreakIn BreakOut RunStallIn
cpu1: Current bits set: BreakIn BreakOut RunStallIn

Running OpenOCD is described here: https://docs.espressif.com/projects/esp-idf/en/latest/api-guides/jtag-debugging/index.html#configuring-esp32-target. This is linked from step 12 in the guide about using Eclipse for debugging (https://docs.espressif.com/projects/esp-idf/en/latest/api-guides/jtag-debugging/using-debugger.html#jtag-debugging-using-debugger-eclipse).

AmbimatElectronics commented 6 years ago

Thanks Ivan.

We were setting everything up in Windows but it looks like the suggested OS is Linux.

Is there a specific Ubuntu version that you know your development environment works best with?

What about the version of Eclipse?

Do let me know.

Neel.

On 09-Jul-2018, at 7:17 PM, Ivan Grokhotkov notifications@github.com wrote:

Hi @AmbimatElectronics https://github.com/AmbimatElectronics, to check whether OpenOCD is running, i think you can try using Task Manager. Also you can open the command line window where you started OpenOCD, and check that it has not crashed or exited; the output should look like:

Open On-Chip Debugger 0.10.0-dev (2018-06-05-14:52) Licensed under GNU GPL v2 For bug reports, read http://openocd.org/doc/doxygen/bugs.html none separate adapter speed: 20000 kHz esp32 interrupt mask on force hard breakpoints Info : ftdi: if you experience problems at higher adapter clocks, try the command "ftdi_tdo_sample_edge falling" Info : clock speed 20000 kHz Info : JTAG tap: esp32.cpu0 tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1) Info : JTAG tap: esp32.cpu1 tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1) cpu0: Current bits set: BreakIn BreakOut RunStallIn cpu1: Current bits set: BreakIn BreakOut RunStallIn Running OpenOCD is described here: https://docs.espressif.com/projects/esp-idf/en/latest/api-guides/jtag-debugging/index.html#configuring-esp32-target https://docs.espressif.com/projects/esp-idf/en/latest/api-guides/jtag-debugging/index.html#configuring-esp32-target. This is linked from step 12 in the guide about using Eclipse for debugging (https://docs.espressif.com/projects/esp-idf/en/latest/api-guides/jtag-debugging/using-debugger.html#jtag-debugging-using-debugger-eclipse https://docs.espressif.com/projects/esp-idf/en/latest/api-guides/jtag-debugging/using-debugger.html#jtag-debugging-using-debugger-eclipse).

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/espressif/esp-idf/issues/2151#issuecomment-403414762, or mute the thread https://github.com/notifications/unsubscribe-auth/AeQORqwmOSF18vm6iJJSa0i9GY5hOr77ks5uEx-ugaJpZM4VDOkW.