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

Tasking Keil compiler conversions

Hi,

I've some questions about the Cx51 keil development:

I've one c-file which must be converted from Tasking compiler to the keil compiler

_sfrbyte x _at(y) (Tasking Compiler) -> Sfr(x, y) (Keil compiler)?????

Are these conversions are correct?

_xdat (Tasking compiler) --> xdata (Keil compiler)

_data (Tasking compiler) --> data (Keil compiler)

REENTRANT void function() (Tasking Compiler) --> void function() REENTRANT; (Keil Compiler)

Moreover do you know which controller I've to add to the keil project if the "Intel MCS 51 family" is required?

best regards
Jens

Parents
  • A compiler doesn't run code - it just translates it.

    So, as long as this "TUSB6250" thing uses the standard 8051 instruction set (which it almost certainly does), you can use any compiler that generates standard 8051 output - that is the beauty of a standard architecture like the 8051 (or ARM)!

    When you select a target device in uVision, that is just configuring the tools for the "peripheral" features of the specific chip - SFRs, memory sizes, etc - it makes no difference to the basic instruction set!

Reply
  • A compiler doesn't run code - it just translates it.

    So, as long as this "TUSB6250" thing uses the standard 8051 instruction set (which it almost certainly does), you can use any compiler that generates standard 8051 output - that is the beauty of a standard architecture like the 8051 (or ARM)!

    When you select a target device in uVision, that is just configuring the tools for the "peripheral" features of the specific chip - SFRs, memory sizes, etc - it makes no difference to the basic instruction set!

Children
No data