Troubles connecting mikroProg hardware

[carnecro]

I am trying to connect my EasyMxPRO for STM32 ARM development board with any of my IDE's

CrossWorks: error message 'Cannot find debug component from ROM Table' when selecting ST-Link/V2 as target
Atollic Studio: error message 'Error in Initializing ST-Link device' from gdbserver and bunch of errors from client, see screenshot
OpenOCD: gdbserver can start configured with -f interface/stlink-v2.cfg -f target/stm32f4x_stlink.cfg but when the debugger connects, error message occurs:
Info : device id = 0x00000000
Warn : Cannot identify target as a STM32 family.
Error: auto_probe failed
and the session is disconnected.

What's wrong with your hardware? Are you ST-Link/V2 compatible? Can I attach my ST-Link/V probe and bypass your hardware?

Robert

[dejan.odabasic]

Hello,

Our onboard programmer is fully ST-Link/V2 compatible.

Did you installed ST-Link drivers for EasyMx board?
Didi you try to use EasyMx board with one of our compilers or with mikroProg Suit for ARM?

Best regards.

[pspeirs]

Hi,

I'm looking at switching from the 8 bit PIC to the Atollic TrueSTUDIO offering but would like to connect it to the EasyMX Pro development board for STM32. Do the two play happy together?


Cheers,
Paul

[filip]

Hi,

We haven't tested this, but if the Atollic studio support ST-link v2 (which is 100 percent compatible with the on-board mikroProg) it should work.

Regards,
Filip.

[pspeirs]

OK,

Might be worth giving this a go as the MikroE boards have no equal in terms of competition. One question though, your board accepts a number of different physically sized MCUs from 48 to 144 pins, however your board appears to only have 104 pins to the board. How does this work to support a smaller or larger MCU?

Cheers,
Paul