2018-01-23 09:51 PM
2018-01-24 12:47 AM
The debugger can talk to the chip or loses connectivty. Check you have the right pins connected and device doesn't power down. On the PC side make sure you have picked the right debugger and flash algorithm.
2018-01-24 01:42 AM
Anuraag P wrote:
I am getting an error 'Internal Command Error'Where, exactly, are you getting that error? What software are you using? What hardware are you using?
Has it ever worked, or is this a 'new' problem?
Anuraag P wrote:
it saysWhat says?
2018-01-24 03:34 AM
I am using Keil software for flashing the code. It is a new problem. When I tried to write some application it started behaving in this way..
2018-01-24 03:36 AM
it says in the sense a popup is coming on the screen. let me post you the screen shot.L
2018-01-24 04:01 AM
Anuraag P wrote:
the screen.
There you go again.
Remember that we cannot see your screen - so we have no idea what you're doing, or what tools you are using unless you clearly state these things in your post!
(Yes, you have now revealed that you are using Keil - but that was not in your initial post).
2018-01-24 04:02 AM
Anuraag P wrote:
I am using Keil software for flashing the code.
So what happens if you use the ST-Link Utility?
ie, is this a fundamental issue, or is it just something to do with Keil...
2018-01-24 07:20 AM
The use of Keil was inferred.
Would agree ST-LINK Utilities would be a good test. If code meddles with debug pin use 'connect under reset' options or strap BOOT0 low.
2018-01-24 07:27 AM
'Connect under reset' should also help if the code is going to sleep