look up table

In what way does it "not work at all?"

Have you tried this in the simulator?

Have you looked in the map file & verified that the code constants are being placed in a sensible location?

Are you getting any errors or warnings during the build?

Post the smallest complete program that illustrates the problem - and remember those 'pre' and '/pre' tags when posting code (see the 'Notes' immediately above the 'Message' window when you post).

dear Andy Neil
if you still read me, first of all, thanks for writing me back anyway, cause this problem is making me crazy, any way, i haven't tried it on simulator,instead i am trying this code directly on hardware each time i proramme it, the irony is that it works perfectly well when i initialize the array element by element,but it doesn't work when i try it the following way:
A[] = {0x00,0x03F,0x050,0x090,0x050,0x03F};
or

A[] = {0x00,0x03F,0x050,0x090,0x050,0x03F};

you have any suggestion?

The array defined with initializers is initialized by the runtime startup code, whereas the other way is by explicit assignment in your program. Are you including the runtime startup in your project?

http://www.keil.com/support/man/docs/c51/c51_ap_startup.htm

"Are you including the runtime startup in your project?"

It shouldn't be necessary to explicitly include it - if you don't explicitly include it, you should automatically get the default.

"i haven't tried it on simulator, instead i am trying this code directly on hardware each time i proramme it"

And you say it's driving you crazy - so don't do it!
Unless you have a chip with on-chip debug - in which case, use it!

IF you can reproduce the problem in the simulator, it will be much easier to debug; if you can't, it most likely means that you have a hardware fault, misconfiguration, or your interfacing is bad.

"you have any suggestion?"

I'm still waiting for your response to my previous questions & suggestion:

Have you looked in the map file & verified that the code constants are being placed in a sensible location?

Are you getting any errors or warnings during the build?

Post the smallest complete program that illustrates the problem.

Note that

unsigned char code A[]={0x00,0x3F,0x50,0x90,0x50,0x3F,0xAA};

A[1] = 0x00;
A[2] = 0x3F;
:
A[6] = 0xAA;

dear Andy Neil
i am so thankful to youR attention, i checked startup.A51 to see if there is any option to manipulate the enternal code memory of 8051 for initialization, and there is no such option so far as i can see, so tell me if i am making a mistake, and then, this code is perfectly working well when i am initializing the array element by element in AT89C52 internal RAM, but because of the volume of data, i have no other option except using the code space. i even translated the C51 code i had written to assembly all by hand and it worked, but because of some complexities, it's not possible to wtire the entire code in assembly, i am looking forward to hear from you, thanKs.

You need to find out why the initialisation in the definition isn't working.

See my previous replies:

* Check your 'C' array indexing;

* Use the simulator.

We cannot help you further unless you post the smallest complete program which shows the problem. Please copy and paste this from you editor - do not retype it.

have you ever tried to set the "code" definition in the first place.
are you sure the array definition "A" is not defined elsewhere. Try out the following definition:

code unsigned char MyArray[7]={0x00,0x3F,0x50,0x90,0x50,0x3F,0xAA};

thanks for your attention, and thanks foR your replay, actually there was nathing wrong with the code i had written, there was something wrong with the version of software i was using, i didn't know it was using a cracked one.