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.
Hi,
We recently upgraded our uVision to a newer version, because of the newer RealView-ARM-compiler. The compiler is great, but we have a lot of trouble with debugging/flashing our devices (str710 and str715).
With debugging, uVision places the program in Flash, starting @address 0x4000000, and that is not where it should be. It should be @address 0x2000000.
In the previous uVision, we had in the "options" dialog, a tab named "LA Locate", where we could define "User classes". In that field, we've stored the address mapping for Code, Data, Constants and IRQ_codes. But with the new uVision, there is no option like that AT ALL!. We've tried every possible address mapping under the tab "Target" and "Linker", but still, not able to debug the program correctly.
The WORKING value of "User classes" in the tab "LA Locate" in the previous uVision was:
DATA (0x2000A000-0x2000FFFF), CODE (0x20000000-0x2000FFFF), CONST (0x20000000-0x2000FFFF), CODE_IRQ (0x20000000-0x40009FFF)
Does anybody have any idea where we must put the correct values, so we can debug in SRAM en run the application in Flash?
Thank you so, so much!!
Jay.
what version of uVision?
The old one: 3.23 with the Keil c-compiler ca.exe V2.41,
The new one: 3.72 with RealView MDK-Basic, V3.40
Thanks!
Does that mean you were previously using Keil's own, original tools - rather than the RealView tools that originated with ARM (before they acquired Keil)?
If that's the case, then it's not just uVision you've updated - but the entire toolchain!
And a complete change of toolchain is never a trivial exercise!!
:-0
Yes, you're right.. But.. It SHOULD work.. right? I SHOULD be able to communicate in the right way with the microcontroller(s) from uVision.. But.. It doesn't.. And it drives me crazy, and I want to know why, and I want to get it work!
Please.. If someone knows a solution... Please..
Porting a project from one toolchain to another is a major exercise; especially when it comes to things like Linker settings - which are entirely proprietary and beyond the scope of any standards like ANSI 'C'...
Have you contacted Keil support for assistance in this?
If you have Keil (Hitex) STR7 board you can try example that can be found in c:\Keil\ARM\Boards\Keil\MCBSTR7\Blinky\
Otherwise you can use examples in c:\Keil\ARM\Boards\Keil\MCBSTR7\ as basis for porting.
Also, this is a major jump as Keil compiler had some extensions for embedded systems so same code will surely not compile and link on new toolchain.