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

Linker error

Hi, Iam getting the following error while trying to build an example Keil project for UART (downloaded from NXP's website).

Build target 'MCB2300 Debug'
linking....\Obj\uart_debug.axf: error: L6938E: Invalid value for --ro-base.
Target not created

Kindly give your suggestions to debug this error.

  • I don't have the environment available right now, but have you opened the project and checked what address is specified for read-only memory? Maybe it is empty. Note that the project can contain multiple target definitions.

  • "Kindly give your suggestions to debug this error."

    The steps are the same, irrespective of the toolchain:

    1. Read the message: what is it telling you?

    In your case, it is telling you that the value specified for "--ro-base" in your project is not valid

    2. Check the Project: what --ro-base value did you specify?

    3. Check the manual: what are the valid types and/or ranges of values for --ro-base?

    4. Fix the Project: so that it specifies a valid value for --ro-base!

  • Some useless observations

    - Chetan is probably using an evaluation copy of the Keil ARM tools.
    - NXP examples were probably built using a full version of the tools with the option Use Memory Layout from Target Dialog option selected

    This Use Memory Layout from Target Dialog option is not available and disabled in the evaluation version.

    Chetan will probably find that this option is selected but that he is unable to de-select it.

    This will result in the error message that Chetan is experiencing through no fault of his own.

    He should be able to figure out how to fix it himself now.

  • Possible explanation:

    Sometimes "valid" --ro-base values for the chip being used are not "valid" while using the evaluation version of the Keil tools.

  • Thanks everyone for your valuable suggestions.
    Yes Patrick, you are correct. I also got a confirmation from NXP semiconductors and the linker error is due to
    the evaluation s/w that Iam using.