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?
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!
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.