CUSTOM STM32F446RE CONTROLLER SWD FLASHING ISSUE

[TH.16.336]

Hello All,

We have an custom board using stm32f446re controller which has 6 PIN SWD JTAG connector.

We are using NUCLEO-F446RE kit as debugger to flash the custom board as explained in "6.2.4 Using ST-LINK/V2-1 to program and debug an external STM32 application" from below link,

https://www.st.com/content/ccc/resource/technical/document/user_manual/98/2e/fa/4b/e0/82/43/b7/DM00105823.pdf/files/DM00105823.pdf/jcr:content/translations/en.DM00105823.pdf

1. Removed CN2 jumpers
2. Connected CN4 SWD pins of NUCLEO-F446RE to custom SWD connector as appropriate signals.

But we are not flash or debug as we are getting below error in System workbench for STM32 IDE,

Wrong device detected

 Open On-Chip Debugger 0.10.0+dev-00021-g524e8c8 (2019-04-12-08:48)

 Licensed under GNU GPL v2

 For bug reports, read

  http://openocd.org/doc/doxygen/bugs.html

 srst_only separate srst_nogate srst_open_drain connect_assert_srst

 Info : The selected transport took over low-level target control. The results might differ compared to plain JTAG/SWD

 adapter speed: 480 kHz

 adapter_nsrst_delay: 100

 Info : Listening on port 6666 for tcl connections

 Info : Listening on port 4444 for telnet connections

 Info : clock speed 480 kHz

 Info : STLINK v2.1 JTAG v34 API v2 M25 VID 0x0483 PID 0x374B

 Info : using stlink api v2

 Info : Target voltage: 3.253193

 Error: init mode failed (unable to connect to the target)

 in procedure 'init' 

 in procedure 'ocd_bouncer'

Can someone help to understand what is the issue here?

[TH.16.336]

Hello All,

There was a wrong SWDIO & SWDCLk connection from NUCELO SWD connector to custom board.

After resolving the hardware connectivity, now we are getting the flashing issue as below.

Open On-Chip Debugger 0.10.0+dev-00021-g524e8c8 (2019-04-12-08:48)

Licensed under GNU GPL v2

For bug reports, read

http://openocd.org/doc/doxygen/bugs.html

srst_only separate srst_nogate srst_open_drain connect_assert_srst

Info : The selected transport took over low-level target control. The results might differ compared to plain JTAG/SWD

adapter speed: 480 kHz

adapter_nsrst_delay: 100

Info : Listening on port 6666 for tcl connections

Info : Listening on port 4444 for telnet connections

Info : clock speed 480 kHz

Info : STLINK v2 JTAG v31 API v2 SWIM v7 VID 0x0483 PID 0x3748

Info : using stlink api v2

Info : Target voltage: 3.223483

Info : Stlink adapter speed set to 480 kHz

Info : STM32F446RETx.cpu: hardware has 6 breakpoints, 4 watchpoints

Info : Listening on port 3333 for gdb connections

Info : accepting 'gdb' connection on tcp/3333

Error: timed out while waiting for target halted

TARGET: STM32F446RETx.cpu - Not halted

in procedure 'reset' 

in procedure 'ocd_bouncer'

Info : device id = 0x10006421

Warn : STM32 flash size failed, probe inaccurate - assuming 512k flash

Info : flash size = 512kbytes

Error: Target not halted

Error: failed erasing sectors 0 to 0

Error: flash_erase returned -304

Cross verified the FLASH SIZE and it's 512KB.

Can someone help here to understand the issue?