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?
I do not understand why "RO-data" is much bigger than "Code"?
Your mistake is most likely in beliving there's anything to understand there. Why shouldn't it?
which file I should hand to manufacture and how they could put it to the board without Keil develop tools?
If you need to ask, no file of yours is production-worthy. If they don't already know, they won't be producing anything worth having.
you (Hans-Bernhard Broeker) are not worthy to put your post here - it is not only a junk. But also offense.
But what was wrong with his statements?
The factories I make use of do know what files they need to be able to program.
And I do know what files I need to send and what is needed to make use of them.
And reading the map file would tell what the different figures means, and what are included, and why they have the size they have. Map files are not something unique to Keil, so an experienced developer would be able to solve this riddle. An unexperienced developer, on the other hand, might not. But should then consider getting more experience before starting to ship firmwares for production. Costs becuase of bugs in the firmware tends to be very high, if involving factory-produced equipment. So it does help to be reasonably experienced before being the final outpost before shipping firmware to the factory.
Next thing: When told new information, there are many ways to react. Getting angry for having been found wanting is _not_ a good route to go. It is way smarter to realize that if you missed out here, you are probably missing out in other situations too - which could be quite expensive if found after the factory run. Or even more expensive after the devices have been sold and shipped.
Before you ship, you should be comfortable with the programming language. And with the target hardware. And with the used tools. And with the results of the validations and testing. And with the feedback from customer tests of prototypes. Right now, you are not comfortable with the tools. What other areas are you not comfortable with?
First, as I said I am beginner and look for help from this forum. I do not think only -experienced- developper should be here. If you like to help, THANK YOU. If not, do not waste the resource.
Second, in my post, I would like to know what the build output means. As I said, I have searched the document and found the definition. But it is not enough for me to understand it.I know there are flash / RAM on the chip. So I believe the most of the code should be on flash and some might be on RAM (like constants, etc.). I do not know in which case there are so many RO-Data. If you can give me a example, THANK YOU. If you do not know, do not waste the resource.
Third, In our site, manufactory people need instruction from Engineering group. Also, as I said in my post, I am a beginner, and do not know what I should hand it to them. (.AXF, .HEX, etc.) and what they need in order to put it into the board. I do not say I will put the example code into it. But sooner or later we pwill put our code into it. Again, we are beginner and try to learn the procedure to do it.
Also, provide helpful post to the beginner is good for this community. Be nice!
-- "And I do know what files I need to send and what is needed to make use of them." --
If you like to to tell, THANK YOU. If not, do not waste the resource. It is not nice just to show off without provide any help to the new commer.
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.
Third, In our site, manufactory people need instruction from Engineering group.
And who is Engineering --- you all on your lonesome? Certainly not. So stop trying to impress your colleagues with knowledge you don't have by acquiring it here, where you believe none of them will be looking, and start asking them for advice. They're the ones who know your shop's procedure.