EASYMX PRO v7 STM32F407VGT6 issues with Cube IDE and CubeProgrammer Connections

General discussion on mikroElektronika development boards.
Post Reply
Author
Message
mick
Posts: 2
Joined: 19 May 2021 15:38

EASYMX PRO v7 STM32F407VGT6 issues with Cube IDE and CubeProgrammer Connections

#1 Post by mick » 19 May 2021 17:26

Cube IDE and CubeProgrammer fails to connect to EASYMX PRO v7 STM32F407VGT6 via ST-LINK V2 or ST-LINK USB dongle

Because EASYMX PRO v7 STM32F407VGT6 is available from DigiKey , my plan is to start using it instead of Diymore STM32F4 which works fine under same below mentioned conditions.
A brand new EASYMX PRO v7 STM32F407VGT6 fails to connect to Cube IDE and CubeProgrammer while Diymore STM32F407VGT6 works fine.
Schematic wise these two boards are very similar. In my opinion, they should work with identical .ioc configuration . Please. correct me if I am wrong.

It seems like it needs some extra hardware setup or configuration. Please advice.
Last time I had similar issue the reason was a counterfeit IC. Hopefully this is not the case with Miroe.


1.) Cube IDE settings
2.) .ioc graphic setup : PA14 - SWCLK , PA13 - SWDO,
3.) Debuggers: a) st-link v2 or b) st-link USB Dongle

Part 1
****************************************************************************************************
using st-link USB Dongle. Debug Config - ST-LINK (ST-LINK GDB server)
Cube IDE fails to connect to EASYMX PRO v7 STM32F407VGT6 with the following error :
----------------------------------------------
STMicroelectronics ST-LINK GDB server. Version 5.8.0
Copyright (c) 2020, STMicroelectronics. All rights reserved.

Starting server with the following options:
Persistent Mode : Disabled
Logging Level : 1
Listen Port Number : 61234
Status Refresh Delay : 15s
Verbose Mode : Disabled
SWD Debug : Enabled

Target no device found

Error in initializing ST-LINK device.
Reason: No device found on target.
-----------------------------------------------

Part 2
***********************************************************************
With Debug Probe set to ST-LINK (OpenOCD) it fails
-----------------------------------------------------------------------
Open On-Chip Debugger 0.11.0-rc2+dev-00037-g4c4dbd9 (2021-02-09-13:39)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
Info : Listening on port 6666 for tcl connections
Info : Listening on port 4444 for telnet connections
Info : STLINK V2J37S7 (API v2) VID:PID 0483:3748
Info : Target voltage: 3.195806
Error: init mode failed (unable to connect to the target)


Error message from debugger back end:
localhost:3333: The system tried to join a drive to a directory on a joined drive.
Failed to execute MI command:
target extended-remote localhost:3333
---------------------------------------------------------------------------

Part 3
***************************************************************************
Cube Programmer fails to connect with EASYMX PRO v7 STM32F407VGT6, Diymore STM32F407VGT6 works fine.

User avatar
filip
mikroElektronika team
Posts: 11874
Joined: 25 Jan 2008 09:56

Re: EASYMX PRO v7 STM32F407VGT6 issues with Cube IDE and CubeProgrammer Connections

#2 Post by filip » 20 May 2021 08:17

Hi,

I believe you have raised the same issue on the HelpDesk, so lets please continue there.

Regards,
Filip.

mick
Posts: 2
Joined: 19 May 2021 15:38

Re: EASYMX PRO v7 STM32F407VGT6 issues with Cube IDE and CubeProgrammer Connections

#3 Post by mick » 20 May 2021 13:45

Hi,
Thanks for your quick response.
I also, raised some other questions on the Help Desk which wouldn't be relevant here.
So, I still hope receiving an email with answers for those questions.
Best,

Post Reply

Return to “Development Boards”