I bought the mikroPASCAL PRO for ARM, some click-Boards, Visual TFT and a STM32F4 Discovery Shield. Software installed the drivers and utilities for the STLink. Everything OK. Written small test program compiled, the Discovery fired by F11 (mikroProg / Options -STLink -JTAG, Connection-Normal). So far so good. Unfortunately, you can not debug it, F9 immediately brings an error, see Appendix. One can the compiler then only by Alt + Ctrl + Del kilen, the message is repeated continuously. You can also see the data with the Discovery to be replaced, the LED flashes red / green.
Why is that?
With best regards
rage
Debugproblem with STM32 Discovery
Debugproblem with STM32 Discovery
- Attachments
-
- DiscoveryDebug.jpg (407.13 KiB) Viewed 4935 times
Re: Debugproblem with STM32 Discovery
Hi,
Does this happen each time you run a debugger, with every project ?
Regards,
Filip.
Does this happen each time you run a debugger, with every project ?
Regards,
Filip.
Re: Debugproblem with STM32 Discovery
Yes with every project, regardless of whether demo even written etc. Immediately after the start of the debugger.
Re: Debugproblem with STM32 Discovery
Hello Rage and welcome to the forum
Is your (MikroProg suite for ARM) software updated to the latest version?
If not, then please update it.
Windows 7 and higher might require administrative updating.
Also, do you get this error when you debug a simple code (An LED blinking for example)?
I'm just checking here, but did you compile that code as a debugging type or a release type?
Best Regards
Is your (MikroProg suite for ARM) software updated to the latest version?
If not, then please update it.
Windows 7 and higher might require administrative updating.
Also, do you get this error when you debug a simple code (An LED blinking for example)?
I'm just checking here, but did you compile that code as a debugging type or a release type?
Best Regards
My hobby is collecting MikroElektronika products.
Gotta catch them all!
Gotta catch them all!
Re: Debugproblem with STM32 Discovery
OK, i have checked with a other PC, all ready. With my PC, is not correct. Now make a update for the Discovery, and now running the debugger.
cu
rage
cu
rage
Re: Debugproblem with STM32 Discovery
Hello Rage
I see that I've misunderstood you earlier
Now, if I understand you correctly, you have solved your issue
If so, then I'm glad everything worked out well
Best Regards
I see that I've misunderstood you earlier
Now, if I understand you correctly, you have solved your issue
If so, then I'm glad everything worked out well
Best Regards
My hobby is collecting MikroElektronika products.
Gotta catch them all!
Gotta catch them all!
Re: Debugproblem with STM32 Discovery
I am working with a STM32F429I-Discovery board and while I can program the board with an example such as led blinking (and it works), I cannot run the debugger. When I try the debugger in hardware (software works) I get a dialog saying no device and when I click the OK, I get a dialog saying mikroElektronika ICD hardware not found.
How can I debug with the ST-Link on the discovery board? I've looked through all the options and dug through the forums and this one seems to have a question closest to my problem.
I'm evaluating several IDE's right now for a couple of projects and I will need some good tools for the next couple of years. Yours is the only one where I download an example and the example continues to work after I power cycle the board. I can also download the hex file to the internal boot loader with the unix tool stm32flash. Although I can't figure out what address to tell it to go to to run it. But that is a secondary question. If I can't debug, then its all no good.
I will also need to know how easy it is to use the peripherals such as SPI, I2C, UART, Timers, GPIO, DMA, Interrupts, Low power mode, and if there is a TCP/IP stack available. Right now the clock is set up wrong because the LED is not blinking according to the software settings. I have use STM32Cube with another IDE and found it quite useful for dealing with a lot of the above concerns. Does the mikron Pro for ARM accept generated code or projects from STM32Cube?
Thanks.
How can I debug with the ST-Link on the discovery board? I've looked through all the options and dug through the forums and this one seems to have a question closest to my problem.
I'm evaluating several IDE's right now for a couple of projects and I will need some good tools for the next couple of years. Yours is the only one where I download an example and the example continues to work after I power cycle the board. I can also download the hex file to the internal boot loader with the unix tool stm32flash. Although I can't figure out what address to tell it to go to to run it. But that is a secondary question. If I can't debug, then its all no good.
I will also need to know how easy it is to use the peripherals such as SPI, I2C, UART, Timers, GPIO, DMA, Interrupts, Low power mode, and if there is a TCP/IP stack available. Right now the clock is set up wrong because the LED is not blinking according to the software settings. I have use STM32Cube with another IDE and found it quite useful for dealing with a lot of the above concerns. Does the mikron Pro for ARM accept generated code or projects from STM32Cube?
Thanks.
Re: Debugproblem with STM32 Discovery
Hi,
Did you set ST-link/SWD debugger in the IDE and mikroProg Suite for ARM options ?
Regards,
Filip.
Did you set ST-link/SWD debugger in the IDE and mikroProg Suite for ARM options ?
Regards,
Filip.
Re: Debugproblem with STM32 Discovery
Hi,
Could you please attach the detailed photo of the board and connections ?
Regards,
Filip.
Could you please attach the detailed photo of the board and connections ?
Regards,
Filip.
Re: Debugproblem with STM32 Discovery
Here's a photo
- Attachments
-
- snapshot of board
- IMG_1843.png (605.84 KiB) Viewed 4321 times
Re: Debugproblem with STM32 Discovery
Did you try this: http://www.mikroe.com/forum/viewtopic.p ... 15#p231444
Serge T.
Learning is an endeless process but it must start somewhere!
Learning is an endeless process but it must start somewhere!