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 am using Keil Microvision 3 to create a hex file to be burned to Philips P89V51 RDBN chip.
In the source group there are two files : 1. STARTUP.A51 2. A program to glow LEDs on port 2 [I have #included <p89v51rx2.h>] before main prog in this file]
While "building target" I get the following mesage in the build window:- warning C318: can't open file 'P89V51Rx2.H'
May, I know what is causing this issue?
Is the Keil software on my comp missing a file?
If yes, how can I solve this issue?
Thank you Hans-Bernhard Broeker for confirming my doubt.
I searched for the file P89V51rx2.h and it is available on the net.
I think the solution to the issue is, creating a P89V51rx2.h file in the "Include" folder of Keil. Is this correct?
I'm new to computers and embedded systems. So, I hope you do not mind my questions which might be obvious to a pro but really problematic for a beginner.
Thanks once again.
Take a look here. You may download the header file from this page:
http://www.keil.com/dd/chip/3711.htm
Jon
You thank me, yet you didn't answer my question: what made you think that this file should exist, under that precise name? Where did that bit of information come from, and why did you trust that source of information more than your compiler manuals?
Hello Hans-Bernhard
I got trained in 8051 controller at an embedded trainig institute. But it wasn't a in-depth training. The trainer just told me how to use Keil for compiling programs and how to load them to the chip using Flash Magic. While compiling programs he taught us to set include the particular file as a header file.
Now, the institute has been shut down.
There are so many books in the Keil uVision 3 software, making it really difficult to know from where to start.
Could you please guide me where in which order should I read the books?
well, my dear Watson, I would suggest getting started with the "getting started guide".
Do not 'read' it, work through the examples.
Once you are done with that, I think you will know what to read next.
Erik
Hello Erik,
Thank you for the guidance.