• State Not Answered
  • Locked Locked
  • Replies 2 replies
  • Subscribers 21 subscribers
  • Views 843 views
  • Users 0 members are here
2025 survey

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.

Options
Related
How was your experience today?
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

change code from CARM compiler to Real view compiler

Murthy r

Hi friends,

I am using the AT91SAM7SE512 controller.

I have downloaded some example codes for this controller.
The codes are in the CARM compiler format.
Now i am using Real view compiler.

What are the modifications i have to do in the code?

Could you please help me.

with regards,

Murthy.R

  • 0

    Convert from CARM

    This chapter gives guidelines for the conversion from the Keil CARM Compiler to the RealView Compilation Tools.

    To convert a program that is initially written for Keil CARM Compiler to the RealView Compiler perform the following steps.

    1. Select the RealView Compiler under Project - Components, Environment, and Books - Folder/Extensions.

    2. Replace and configure the Startup file. Pre-configured startup files for the various supported microcontroller devices are provided in the folder ..\ARM\RV\Startup.

    3. Check if the application is using console I/O functions using printf or scanf. In this case you need to add a library retarget file.

    4. Configure the memory layout of your target hardware.
    Now you may simply re-compile your application code.

    Once you re-compile the application code you may come across the following situations:

    The RealView compilation tools tend to use some more stack. It might be required to increase the stack space of your application.

    Software interrupt (SWI) functions of your application need adaption.

    Combine functions that executed from RAM in a source module and assign the code/consts to RAM using the Options - Properties dialog.

    It is not possible to locate variables to absolute memory addresses. Instead assign the objects to specific memory areas or use pointer constants for memory access.

    The syntax of in-line assembly functions is slightly different.

    The __task attribute is not available and should be removed.