System Workbench for STM32

Another confusing behavior ... I have two boards - an STM32F429I-Discovery and my own board with a STM32F405 ... First I tested an LED blinker on the Discovery ... worked. Then I made a new project for my own board ... programmed that board through the ST-Link of the Discovery board ... and found the following:

Everything works great if I first build the project and then use burn chip to put the ELF on the processor. But it does not program the chip when I call run directly which would include building and burning in one ... very strange.

When I call run the building goes well and then the programmer says ...

Error: open failed
in procedure 'program'
in procedure 'init' called at file "embedded:startup.tcl", line 473
in procedure 'ocd_bouncer'

• OpenOCD init failed **

shutdown command invoked

When I call Target/Program chip I get ...

Info : STLINK v2 JTAG v17 API v2 SWIM v0 VID 0x0483 PID 0x3748
Info : using stlink api v2
Info : Target voltage: 2.860408
Info : stm32f4x.cpu: hardware has 6 breakpoints, 4 watchpoints
target state: halted
target halted due to debug-request, current mode: Thread
xPSR: 0x01000000 pc: 0x08002f64 msp: 0x20020000
configuring PLL

• Programming Started **

auto erase enabled
Info : device id = 0x10016413
Info : flash size = 1024kbytes
target state: halted
target halted due to breakpoint, current mode: Thread
xPSR: 0x61000000 pc: 0x20000042 msp: 0x20020000
wrote 16384 bytes from file Debug/FR_Test_0001.elf in 0.963602s (16.604 KiB/s)

• Programming Finished **
• Verify Started **

target state: halted
target halted due to breakpoint, current mode: Thread
xPSR: 0x61000000 pc: 0x2000002e msp: 0x20020000
target state: halted
target halted due to breakpoint, current mode: Thread
xPSR: 0x61000000 pc: 0x2000002e msp: 0x20020000
verified 13440 bytes in 0.374401s (35.056 KiB/s)

• Verified OK **
• Resetting Target **

shutdown command invoked

16:46:52 Build Finished (took 2s.87ms)