Hi i am new to ARM as well as Keil MDK for ARM.
I would like to use Keil with Ulink2 to debug my program in ADI ADuC7020 MCU. I found that when i download and debug it, it won't stop at the Main() and it can only be stepped in Disassembly window only. However, i would like it to debug in source level (in my C source).
I have checked the option "Load Application in startup" as well as "Run to main()" as suggested by other similar posts. It doesn't work for me.
Same issue for simulation too.
It is appreciated if anyone can give me a hint on this issue.
================================================== My Keil version is as follows:
IDE-Version: µVision V4.00u Copyright (c) Keil Elektronik GmbH / Keil Software, Inc. 1995 - 2009
Tool Version Numbers: Toolchain: RealView MDK-ARM Version: 4.03a Toolchain Path: BIN40\ C Compiler: Armcc.Exe V4.0.0.524 [Evaluation] Assembler: Armasm.Exe V4.0.0.524 [Evaluation] Linker/Locator: ArmLink.Exe V4.0.0.524 [Evaluation] Librarian: ArmAr.Exe V4.0.0.524 [Evaluation] Hex Converter: FromElf.Exe V4.0.0.524 [Evaluation] CPU DLL: SARM.DLL V4.03a Dialog DLL: DARMAD.DLL V1.14 Target DLL: BIN\UL2ARM.DLL V1.55 Dialog DLL: TARMAD.DLL V1.13 ==================================================
Thank you very much.
Cheers, Tin
so start here:
http://www.keil.com/support/man/docs/gsac/
http://www.keil.com/support/man/docs/uv4/uv4_ex_hello.htm
http://www.keil.com/support/man/docs/uv4/uv4_examples.htm
Thanks for your reply and the links. I have read through the links but i found no method to solve my case. I wonder if it's a target-specified issue.
thanks.
Don't just read through them; work through the examples - ie, do them yourself, following the steps on your own target.
"i found no method to solve my case"
No, they're not telling you how to solve any particular case; what they do is to teach you how to use the tools effectively - so that you don't get into the problem in the first place!
You need to lay proper foundations before you start building!
Hi Andrew,
I have followed the example and encountered no problem with the example codes. However, when i changed the target to ADuC7020 and made all the necessary changes for this target, my previous problem happened (Cannot debug in source-level).
However, i found that i can debug in the source-level if i checked the box "Use Micro-LIB" in the "Target" tab.
I cannot predict if using Micro-LIB instead of the standard C Lib will affect my application at this moment. I just wonder why this happens.
Thanks a lot.
As the name suggests, the Microlib is much smaller and, therefore, simpler than the "full" standard library.
If it works with Microlib but not the "full" lib, I think that strongly suggests that you have not properly provided all the support required by the "full" lib.
You need to study-up on "Retargetting" if you want to know how to properly support the "full" lib...