I'm getting this all the time, when trying to connect to a STM32VLDISCOVERY board via it's on-board ST-LINK,
or, when the thing was in good mood and working for a few debug runs, then all of a sudden, if doing anything or just returning from the kitchen, that evil red line in the status strip would ruin my day once more.
I'm using CrossWorks for ARM 2.1 and 2.2 (parallel install, to see if 2.2 is doing anything better), the problem persists with both versions.
My host OS is either Windows XP 32bit SP2 or Windows 7 home premium 64bit, while I have a feel that it's a bit worse on Win7, that may be subjective.
The board as such (or any of the bunch of those I have) works fine, and I can debug with a tiny free Chinese toolchain which doesn't support C++, which Is why I bought CrossWorks, but I'm short of giving up on it...
Out of desparation, I soldered together a JTAG adapter for my olimex OCD --> discovery board, kinda ridicilous since it has a debugger on-board, but it works on the mentioned free toolchain, not so in CrossWorks. (not giving details here, since this is not the question, and frankly, I expect the ST-LINK to work)
The actual program to debug is a bit different in CrossWorks from the other tollchain's, since there I added some C++ stuff (not using new/delete), alongside all the system specific C code, and I made the stack a lot bigger.
Since it *sometimes* works and usually just stops in the middle of debugging (preferably short before I'm getting close to a bug), I don't think it's the program, though...
(have read about the startup from reset issues... I put in a delay loop of a few seconds before main gets called, and I now put C++ objects that would otherwise be created before main(), into function scope, for testing)
Any clues what the problem could be ?
Please sign in to leave a comment.