openocd-user

[OpenOCD-user] OpenOCD 0.10.0-dev on windows slash style problem

[MARTIN Jean-L. <jea...@al...>]

Hi all,

I’m facing a problem with OpenOCD on Windows 10.
Version is  : Open On-Chip Debugger 0.10.0-dev (2018-11-05-04:10)
It seems that it doesn’t interpret correctly Windows style backslash.
I have highlighted red windows backslash not correctly interpreted

Configuring upload protocol...
AVAILABLE: esp-prog, esptool, ftdi, iot-bus-jtag, jlink, minimodule, olimex-arm-usb-ocd, olimex-arm-usb-ocd-h, olimex-arm-usb-tiny-h, olimex-jtag-tiny, tumpa
CURRENT: upload_protocol = ftdi
Uploading .pioenvs\esp-wrover-kit\firmware.bin
Open On-Chip Debugger 0.10.0-dev (2018-11-05-04:10)
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
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)
Info : Target halted. PRO_CPU: PC=0x40000400 (active)    APP_CPU: PC=0x40000400
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)
Info : esp32: Debug controller 0 was reset (pwrstat=0x5F, after clear 0x0F).
Info : esp32: Core 0 was reset (pwrstat=0x5F, after clear 0x0F).
Info : Target halted. PRO_CPU: PC=0x5000004B (active)    APP_CPU: PC=0x00000000
Info : esp32: Core 0 was reset (pwrstat=0x1F, after clear 0x0F).
Info : esp32: Debug controller 1 was reset (pwrstat=0x5F, after clear 0x0F).
Info : esp32: Core 1 was reset (pwrstat=0x5F, after clear 0x0F).
Info : Target halted. PRO_CPU: PC=0x40000400 (active)    APP_CPU: PC=0x40000400
** Programming Started **
auto erase enabled
Info : Target halted. PRO_CPU: PC=0x4009171A (active)    APP_CPU: PC=0x40000400
Info : Flash mapping 0: 0x10020 -> 0x3f400020, 23 KB
Info : Flash mapping 1: 0x20018 -> 0x400d0018, 67 KB
Info : Target halted. PRO_CPU: PC=0x4009171A (active)    APP_CPU: PC=0x40000400
Info : Auto-detected flash size 4096 KB
Info : Using flash size 4096 KB
Info : Target halted. PRO_CPU: PC=0x4009171A (active)    APP_CPU: PC=0x40000400
Info : Target halted. PRO_CPU: PC=0x4009171A (active)    APP_CPU: PC=0x40000400
wrote 139264 bytes from file .pioenvs\esp-wrover-kit\firmware.bin in 2.993481s (45.432 KiB/s)
** Programming Finished **
** Verify Started **
Info : Target halted. PRO_CPU: PC=0x4009171A (active)    APP_CPU: PC=0x40000400
read 136224 bytes from file .pioenvs\esp-wrover-kit\firmware.bin and flash bank 0 at offset 0x00010000 in 0.681558s (195.187 KiB/s)
contents match
** Verified OK **
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)
Info : esp32: Debug controller 0 was reset (pwrstat=0x5F, after clear 0x0F).
Info : esp32: Core 0 was reset (pwrstat=0x5F, after clear 0x0F).
Info : Target halted. PRO_CPU: PC=0x5000004B (active)    APP_CPU: PC=0x00000000
Info : esp32: Core 0 was reset (pwrstat=0x1F, after clear 0x0F).
Info : esp32: Debug controller 1 was reset (pwrstat=0x5F, after clear 0x0F).
Info : esp32: Core 1 was reset (pwrstat=0x5F, after clear 0x0F).
Info : Target halted. PRO_CPU: PC=0x40000400 (active)    APP_CPU: PC=0x40000400
** Programming Started **
auto erase enabled
Error: couldn't open c:UsersjlmartinDocumentsPlatformIOProjects╔81122-115851-espidf-blink.pioenvsesp-wrover-kiootloader.bin
embedded:startup.tcl:454: Error: ** Programming Failed **
in procedure 'program_esp32'
in procedure 'program_error' called at file "C:\Users\jlmartin\.platformio\packages\tool-openocd-esp32/share/openocd/scripts/target/esp32.cfg", line 153
at file "embedded:startup.tcl", line 454
*** [upload] Error 1

So I think that the problem is in “startup.tcl” file. But not able to find it …

I’ll really appreciate any support !!

Cordialement,

Jean-Loïc MARTIN
Bureau d'études électronique ALTRAN
Parc Altaïs
57 rue Cassiopée
F-74650 CHAVANOD
Tél direct : +33 (0)4 50 09 46 44
Adresse Mail : jea...@al...<mailto:jea...@al...>

Re: [OpenOCD-user] OpenOCD 0.10.0-dev on windows slash style problem

[Andreas F. <and...@gm...>]

Den tors 22 nov. 2018 18:34MARTIN Jean-Loïc <jea...@al...>
skrev:

> Hi all,
>
>
>
> I’m facing a problem with OpenOCD on Windows 10.
>
> Version is  : Open On-Chip Debugger 0.10.0-dev (2018-11-05-04:10)
>
> It seems that it doesn’t interpret correctly Windows style backslash.
>
Probably you need to escape them. But just use forward slash instead, they
should work as well.

/Andreas

>

Re: [OpenOCD-user] OpenOCD 0.10.0-dev on windows slash style problem

[Paul F. <fer...@gm...>]

Hi,

This is interesting...

On Thu, Nov 22, 2018 at 05:14:36PM +0000, MARTIN Jean-Loïc wrote:
> wrote 139264 bytes from file .pioenvs\esp-wrover-kit\firmware.bin in 2.993481s
> (45.432 KiB/s)
...
> read 136224 bytes from file .pioenvs\esp-wrover-kit\firmware.bin and flash bank
> 0 at offset 0x00010000 in 0.681558s (195.187 KiB/s)

So here it worked just fine with backslashes.

> Error: couldn't open
> c:UsersjlmartinDocumentsPlatformIOProjects╔81122-115851-espidf-blink.pioenvsesp-wrover-kiootloader.bin

And here they're removed.

Now the question is, what were the actual commands it were executing?

What's inside esp32.cfg there on your system?

It looks like it has 2 "program" invocations and the first one is
"proper" (probably filename is in {} braces) and the second one lets
Tcl process the string.

So I'd say it's most likely a bug in that esp32.cfg rather than in
OpenOCD upstream.

-- 
Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
mailto:fer...@gm...

Re: [OpenOCD-user] OpenOCD 0.10.0-dev on windows slash style problem

[Paul F. <fer...@gm...>]

On Fri, Nov 23, 2018 at 09:56:55PM +0300, Paul Fertser wrote:
> So I'd say it's most likely a bug in that esp32.cfg rather than in
> OpenOCD upstream.

Yes, if your copy is the same as
https://github.com/espressif/openocd-esp32/blob/master/tcl/target/esp32.cfg
then I'd say it's missing this trick: http://openocd.zylin.com/4083

-- 
Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
mailto:fer...@gm...