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

improper fixup

sorry for a new thread when there are many threads on this topic but its just that i couldnt find any satisfactory solution :
I am using keil evaluation version (small rom less than 2k) and i am getting the improper fixup error for the interrupts . When i comment those interrupt function , i dont get these error. From other threads , i understand that the code starts from 800h in this version and the interrupt is located in 13h and it is not possible to jump in code size : small .

Is there any solution for this or does it mean interrupts cannot be used in this model ?
Please help me out here.. struck for several days

Thanks !
Ram

Parents
  • Quite possibly not.

    However, the IDE and the compiler, etc, are not supplied separately - they are always bundled together.

    So, to be precise, I should have said, "The current eval download would include uVision-4"

    Similarly, an installation that includes uVision-2 would also include significantly different (older) versions of all the other tools (compiler, etc).

    My point was that any installation (eval or otherwise) that includes uVision-4 will be very different from any installation (eval or otherwise) that includes uVision-2 - so it is not valid to single-out one being an eval as the cause of this problem.

    Sorry for not making that clear.

    "are you suggesting that the issue is with the IDE"

    The IDE may be a problem due to the way it calls the other tools - in particular, in the defaults that it applies.

    Also, the project file format has changed significantly between UV2 and UV4 - so there may be an issue in the conversion.

    And, of course, the compiler, etc, will also be different.

Reply
  • Quite possibly not.

    However, the IDE and the compiler, etc, are not supplied separately - they are always bundled together.

    So, to be precise, I should have said, "The current eval download would include uVision-4"

    Similarly, an installation that includes uVision-2 would also include significantly different (older) versions of all the other tools (compiler, etc).

    My point was that any installation (eval or otherwise) that includes uVision-4 will be very different from any installation (eval or otherwise) that includes uVision-2 - so it is not valid to single-out one being an eval as the cause of this problem.

    Sorry for not making that clear.

    "are you suggesting that the issue is with the IDE"

    The IDE may be a problem due to the way it calls the other tools - in particular, in the defaults that it applies.

    Also, the project file format has changed significantly between UV2 and UV4 - so there may be an issue in the conversion.

    And, of course, the compiler, etc, will also be different.

Children