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 just start to develop LPC 1768 application using Keil uVision4.21. I have some questions which I can not find the answer from my document / web search:
1. Where to find a list of Compiler and Linker error messages for uVision 4.21?
2. When I build example project. I got:
Program Size: Code=72538 RO-data=155114 RW-data=348 ZI-data=64436
the document said: ZI-data:Shows how many bytes are occupied by zero-initialized data. RW-data:Shows how many bytes are occupied by read-write data. RO-data:Shows how many bytes are occupied by read-only data. Code: Shows how many bytes are occupied by code.
I do not understand why "RO-data" is much bigger than "Code"? When this might happened?
3. After I successfully debug my code, which file I should hand to manufacture and how they could put it to the board without Keil develop tools?
What you need to know about this forum is that there is a lot of hostile posturing going on, don't take it personally. Mixed in there's also a lot of good information so it's best to just ignore the noise. I'll take a stab at answering your questions, personally I don't think they were unreasonable, I guess my standards for purity are just a bit lower:
uVision itself is just a front end for the compiler/linker so you're asking for the ARM compiler and linker error messages. I've never found such a list but the ARM documentation site would be the place to look: http://infocenter.arm.com/
2. I do not understand why "RO-data" is much bigger than "Code"? When this might happened?
RO-data contains all your code plus all read-only data. If you have tables or other initialized data in your program they will end up in the RO data. Make sure you have the map file enabled in your "Listing" options. The map file will tell you exactly what's using up the space. Sometimes you can reduce RO data by not initializing large structures in the definition and doing it in code instead.
Keil puts out an ELF file as xyz.axf. You can also generate a HEX file that should be usable by third parties. Whoever ends up manufacturing your board should have an idea how to convert into whatever format they need.
Andrew
Does it?
That's not how I read this: http://www.keil.com/support/man/docs/armlink/armlink_chdcjdgb.htm
These really are very basic questions if you are contemplating a commercial project!
Before starting a commercial development I would strongly recommend that you get (further) professional training and/or engage a Consultant to assist you.
Keil list a number of workshops, seminars, training providers, and consultants: http://www.keil.com/events/classlist.asp http://www.keil.com/events/seminarlist.asp http://www.keil.com/events/links.asp http://www.keil.com/condb/
NXP also have similar resources.
Your local NXP and/or Keil representatives/distributors should also be able to advise you...
Thank you for your help.