MikroProg for STM error in debug mode

[rehrag]

MikroProg for ARM can not detect the MicroProg Adapter in debug mode. To flash teh device run w/o error.
First I have flash the device STM32F302CB with debug mode on
When I start the debugger I get the message "No device" and than "mikroelektronika ICD hardware not found"

At an other project with STM32F429ZI the same procedure will run w/o problems.

What is the reason for that behavior?

[rehrag]

The MikroProg for STM communication via USB works very instable !
I have installed all of that with Administrator rights;

Operating System: WIN7
MikroC for ARM: v6.0.0 (the v6.1.0 start with an errror on my PC, so I went back to the previous Version)
MikroProg for ARM: v1.50 (installed as Administrator)

I have used both, with SW and JTAG => with the same reaction

sometimes the programming of MCU STM32F302CB is running, but not stable
often I get the error message "USB communication error" or "Connection error" or "no ECU"

If I get a propper Connection an can program the ECU, the dbugging is not possible, If I get an communication to the MCU
and it seems to run step by step; the values of variable is shown unchanged

Why is the communication so insable? I have ordered an new MicroProg device, but it Shows the same behavior

[jovana.medakovic]

Hello,

I tested an UART example in debug mode on MikroC for ARM 6.1.0 and it works fine.
Please, check your configurations bits.
Can you send me your project, so I can try to debug it?
Also, can you try to change the USB cable?

Kind regards,
Jovana

[rehrag]

Hello,

which configirations bits I have to check?
I tried the connection with several USB cable, ever the same reaction
I gues, the connection from MikroC for ARM to the MikroProg device is the problem

MikroC v6.1.0 delivert an error at startup, therefore I use v6.0.0

I will send you my project

[rehrag]

Hello Jovana,

attached I send you my project

[jovana.medakovic]

Hi,

You need to be mindful of the programming/debugging lines (A13, A14, A15) and you have to be sure not to use them in your code.
When I commented out your function GPIOA_Init(); I was able to debug properly.

Kind regards,
Jovana

[rehrag]

Thanks for your support
I will that testing next weekend
as I understand; I should not use A13 A14 A15 with other function - right

regards

[jovana.medakovic]

Hi,

Exactly that, you should not use A13 A14 A15 and you will debug your project.

Kind regards,
Jovana

[rehrag]

Jovana,
is that the reason too, that I get error messages like "USB communication failed" or "no ECU" ?
The USB communication seems very instable.
Do you have an idee, what can I do to get a stable communication to the MikroProg?
which driver version do you prefer?

regards

[jovana.medakovic]

Hi,

This problem will be solved in the next update of mikroProg Suite for ARM and it should be soon.

Kind regards,
Jovana

[rehrag]

Thanks Jovana, that sounds great

kind regards