This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Compiling differences between C51 v7.03 and v8.06

Hello!

I have uVision that compiles fine with the C51 v7.03 compiler and the related package, but not complete with the 8.06. I used two different Keil installations. All files are in the same folder.

In the 8.06 I get linker errors like "object does not fit in to pdata page" and "0080H". This looks like the compiler was thinking the PDATA was only 128 bytes, but it is set to 256 bytes in the startup.a51. Any clue what's different in the newer Keil package?

Also there is a warning in 8.06 (which does not show in 7.03) "converting non-pointer to pointer" on this

ptr_xdata = sPtr_obj->Adresse;


while the vars are set like this:

uchar uc_set_obj( uchar pdata *ptr_Set)
{
   uchar i;
   uchar xdata *ptr_xdata;
   struct stOBJADR code *sPtr_obj;

   sPtr_obj=&Obj[*ptr_Set];
   .
   .
   .
   ptr_xdata = sPtr_obj->Adresse;
}


The struct stOBJADR has a member "uint Adresse;"

I can see no wrong use of the pointers. I just want to be sure that the warning does not affect the code to not work correctly.

Parents
  • You sure? A data packet in the internet is sent to an address, the IP. <p>

    No, it is not. The packet is sent to a destination. There are _two_ addresses in a packet, a source and a destination.

    Network hardware has a MAC address, where data is addressed to.

    The MAC of a NIC is a property of the NIC itself. It only becomes a destination/target if it is put in the right field in the network packet.

    If you send a letter, you send it to an address.

    A house has an address, which describes its location. It becomes a destination/target when it is written on the right part of the envelope.

    So, I think that's part of the problem. You're saying "address" when you mean "destination/target", while everyone else (and all available literature) defines "address" as "location/place".

Reply
  • You sure? A data packet in the internet is sent to an address, the IP. <p>

    No, it is not. The packet is sent to a destination. There are _two_ addresses in a packet, a source and a destination.

    Network hardware has a MAC address, where data is addressed to.

    The MAC of a NIC is a property of the NIC itself. It only becomes a destination/target if it is put in the right field in the network packet.

    If you send a letter, you send it to an address.

    A house has an address, which describes its location. It becomes a destination/target when it is written on the right part of the envelope.

    So, I think that's part of the problem. You're saying "address" when you mean "destination/target", while everyone else (and all available literature) defines "address" as "location/place".

Children
No data