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

problem: uvision 3 upgrade to uvision 4

I have a project which was completed by another persion by using uvision 3. Recently I plan to add some new fuctionalities in this project.
Since I only have uvision 4 on my machine, so, I plan to use uvision 4 to open the project and see if I can complie the project.

Without touching anything of the source and header files, I opened this project using uvison 4. However, when I compiled this project, there was an error message, "_swi_0 multiply defined in hal.o and rtx_config.o".

Is it caused by the toolchain upgrade? could anyone help on this issue?

Thanks a lot!

The hardware platform is LPC 2103 (Arm-7 core based)
RTOS: keil MDK RTOS

Louis

Parents
  • I checked the configure file: rtx_config.c for both uvision 3 and uvision 4,

    for uvision 3, there is a defination for _swi_0_ in this file for the project.

    however, for uvision 4, I opened a sample project by ARM, there is NO defination for _swi_0_.

    If I just comment out the defination for _swi_0_ in the rtx_config.c, and then compile the project using uvision 4, there are lots of compilation and linking errors.

Reply
  • I checked the configure file: rtx_config.c for both uvision 3 and uvision 4,

    for uvision 3, there is a defination for _swi_0_ in this file for the project.

    however, for uvision 4, I opened a sample project by ARM, there is NO defination for _swi_0_.

    If I just comment out the defination for _swi_0_ in the rtx_config.c, and then compile the project using uvision 4, there are lots of compilation and linking errors.

Children
No data