We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.
I am trying to get started using arm gcc from CodeSourcery within Keil.
Although my projects compile, run correctly, and will even debug up to the size limits of the debugger it seems that the debugger has no idea where variables are located. A simple
int k=0; while (1) { k++; }
loop does not show k changing (optimisation is off and the asm seem to be doing the right thing). When looking at the asm another sram location contains the changing k value, but not the one the Keil debugger believes is k. Why does this happen ?
Also within the IDE when I switch to gcc I can no longer "go to definition" (the option in the right click menu is completely gone).
It almost seems like Keil and the linker don't know about one another. Are these limitations of the Keil IDE with gcc or am I doing something wrong (is there a secret "make Keil work good with gcc" button hidden in some super nest GUI menu)?
If not it seem Keil + gcc is of very limited use, how do others get around this ?
No; my point is, first, that you need to be talking to CodeSourcery for GCC issues - that is (was?) the defined support route.
Second, why use uVision at all with GCC? There are plenty of Eclipse-based environments for use with GCC.
and it seems that Keil themsleves now have one in the form of this "DS5" thing.
hence I'm not so sure if that changes the policy with regard to support for GCC...