Re: [OpenOCD-user] Error: unable to open ftdi device

[<Pet...@t-...>]

Hello Paul,

today I've played again a little bit with the setup, and now it works: My first very simple program is running on the ARM Cortex-M3! See below.

Thank you very much for your help and patience with me!

I would like to ask one further question. I am planning to run in addition a commercial board. I'm thinking of an Arduino Board Due 32-Bit with an Atmel SAM3X8E as Core - ARM Cortex-M3 revision 2.0 running at up to 84 MHz. Perhaps the original one or a cheaper one. I've heard that on that board no FTDI chip is used, but a different one from China. Do you know if someone has used OpenOCD successful to run such a board?

Best regards,
Peter

---
GNU MCU Eclipse 32-bit Open On-Chip Debugger 0.10.0+dev-00352-gaa6c7e9b (2018-10-20-02:36)
Licensed under GNU GPL v2
For bug reports, read
	http://openocd.org/doc/doxygen/bugs.html
WARNING!
This file was not tested with real interface, but is assumed to work as this
interface uses the same layout as configs that were verified. Please report your
experience with this file to openocd-devel mailing list, so it could be marked
as working or fixed.
trst_and_srst separate srst_gates_jtag trst_push_pull srst_open_drain connect_deassert_srst
Info : auto-selecting first available session transport "jtag". To override use 'transport select <transport>'.
adapter speed: 1000 kHz
adapter_nsrst_delay: 100
jtag_ntrst_delay: 100
trst_and_srst separate srst_nogate trst_push_pull srst_open_drain connect_deassert_srst
cortex_m reset_config sysresetreq
Info : clock speed 1000 kHz
Info : JTAG tap: stm32f1x.cpu tap/device found: 0x3ba00477 (mfg: 0x23b (ARM Ltd.), part: 0xba00, ver: 0x3)
Info : JTAG tap: stm32f1x.bs tap/device found: 0x16410041 (mfg: 0x020 (STMicroelectronics), part: 0x6410, ver: 0x1)
Info : JTAG tap: stm32f1x.cpu tap/device found: 0x3ba00477 (mfg: 0x23b (ARM Ltd.), part: 0xba00, ver: 0x3)
Info : JTAG tap: stm32f1x.bs tap/device found: 0x16410041 (mfg: 0x020 (STMicroelectronics), part: 0x6410, ver: 0x1)
Info : stm32f1x.cpu: hardware has 6 breakpoints, 4 watchpoints
Info : Listening on port 3333 for gdb connections
Started by GNU ARM Eclipse
Info : Listening on port 6666 for tcl connections
Info : Listening on port 4444 for telnet connections
Info : accepting 'gdb' connection on tcp/3333
target halted due to debug-request, current mode: Thread 
xPSR: 0x21000000 pc: 0x08000300 msp: 0x20004fc8
Info : device id = 0x20036410
Info : flash size = 64kbytes
Info : JTAG tap: stm32f1x.cpu tap/device found: 0x3ba00477 (mfg: 0x23b (ARM Ltd.), part: 0xba00, ver: 0x3)
Info : JTAG tap: stm32f1x.bs tap/device found: 0x16410041 (mfg: 0x020 (STMicroelectronics), part: 0x6410, ver: 0x1)
target halted due to debug-request, current mode: Thread 
xPSR: 0x21000000 pc: 0x08000300 msp: 0x20004fc8
semihosting is enabled
Info : JTAG tap: stm32f1x.cpu tap/device found: 0x3ba00477 (mfg: 0x23b (ARM Ltd.), part: 0xba00, ver: 0x3)
Info : JTAG tap: stm32f1x.bs tap/device found: 0x16410041 (mfg: 0x020 (STMicroelectronics), part: 0x6410, ver: 0x1)
target halted due to debug-request, current mode: Thread 
xPSR: 0x21000000 pc: 0x08000300 msp: 0x20004fc8, semihosting
Info : JTAG tap: stm32f1x.cpu tap/device found: 0x3ba00477 (mfg: 0x23b (ARM Ltd.), part: 0xba00, ver: 0x3)
Info : JTAG tap: stm32f1x.bs tap/device found: 0x16410041 (mfg: 0x020 (STMicroelectronics), part: 0x6410, ver: 0x1)
target halted due to debug-request, current mode: Thread 
xPSR: 0x61000000 pc: 0x2000003a msp: 0x20004fc8, semihosting
Info : JTAG tap: stm32f1x.cpu tap/device found: 0x3ba00477 (mfg: 0x23b (ARM Ltd.), part: 0xba00, ver: 0x3)
Info : JTAG tap: stm32f1x.bs tap/device found: 0x16410041 (mfg: 0x020 (STMicroelectronics), part: 0x6410, ver: 0x1)
target halted due to debug-request, current mode: Thread 
xPSR: 0x61000000 pc: 0x2000003a msp: 0x20004fc8, semihosting
===== arm v7m registers
(0) r0 (/32): 0x00000020
(1) r1 (/32): 0x00000000
(2) r2 (/32): 0x2000003C
(3) r3 (/32): 0x2000403C
(4) r4 (/32): 0x08000E3C
(5) r5 (/32): 0x20000E80
(6) r6 (/32): 0x00000020
(7) r7 (/32): 0x00000014
(8) r8 (/32): 0xFD7F77CC
(9) r9 (/32): 0xDBFBFFCD
(10) r10 (/32): 0x730C4ACB
(11) r11 (/32): 0x90104B3B
(12) r12 (/32): 0xBFFFFFFF
(13) sp (/32): 0x20004FC8
(14) lr (/32): 0x08000345
(15) pc (/32): 0x2000003A
(16) xPSR (/32): 0x61000000
(17) msp (/32): 0x20004FC8
(18) psp (/32): 0xE8632EA8
(19) primask (/1): 0x01
(20) basepri (/8): 0x00
(21) faultmask (/1): 0x00
(22) control (/2): 0x00
===== Cortex-M DWT registers


-----Original-Nachricht-----
Betreff: Re: [OpenOCD-user] Error: unable to open ftdi device
Datum: 2019-04-10T16:51:40+0200
Von: "Paul Fertser" <fer...@gm...>
An: "Pet...@t-..." <Pet...@t-...>

Hello,

On Wed, Apr 10, 2019 at 02:00:27PM +0200, Pet...@t-... wrote:
> today I've learned how to include an .ld-script to the linker. The
> compiler and linker generated an .elf-file without error
> messages. Running it from Eclipse I got the following messages.

This means you're using some other config file most likely in the case
you run it with Eclipse.

> Info : stm32f1x.cpu: hardware has 6 breakpoints, 4 watchpoints
> Info : Listening on port 3333 for gdb connections
> Info : JTAG tap: stm32f1x.cpu tap/device found: 0x3ba00477 (mfg: 0x23b (ARM Ltd.
> ), part: 0xba00, ver: 0x3)
> Info : JTAG tap: stm32f1x.bs tap/device found: 0x16410041 (mfg: 0x020 (STMicroel
> ectronics), part: 0x6410, ver: 0x1)
> Error: timed out while waiting for target halted

This means something else was changed (probably on hardware level)
since you last tried it, your current elf file is not even considered
because the error surfaces earlier.

This error with STM32 might appear if target's RESET line is tied low
externally. I can't think of anything other obvious enough to cause
this.

Please try to understand what hardware and config-wise might have
changed since you last tried (when you saw incorrect addresses).

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