I want to know the project which code was developed with IAR,the project can port to keil MDK? If I could,where do I need to change,and how to do it .thanks
I use SDK15.0.
I want to know the project which code was developed with IAR,the project can port to keil MDK? If I could,where do I need to change,and how to do it .thanks
I use SDK15.0.
Nothing specific to Nordic here - porting code from one toolset to another is a standard task.
Have you checked the Keil website to see if they have anything in general about porting from IAR?
It requires a good understanding of both the original, "source" toolset, and the destination toolset.
At the source code level, the 'C' programming language is standardised, but has a number of implementation-defined features - so you will need to check these in each toolset, and make any necessary adjustments.
Tools often add their own proprietary extensions to the language - these will not be portable, so you'll have to work out what to do.
Tools often have an option to disable all extensions - so you may be able to use that to identify if any have been used.
The linkers will be different - so you will have to understand the IAR Linker configuration, and translate that to Keil.
The Project setup will be different - so, again, you will have to understand the IAR Project configuration, and translate that to Keil.
It may be simpler to simply start again from scratch ...
there are many errors when I rebuild the project
It's obviously impossible to give any specific help without knowing what the errors are!
So just read what the errors are telling you, and fix what is wrong.
But remember that one error early in a compilation will often produce many more resulting errors in the rest of the compilation.
Therefore, always address the earliest error first - one fix is likely to cure many errors!
Nothing specific to Nordic here - porting code from one toolset to another is a standard task.
Have you checked the Keil website to see if they have anything in general about porting from IAR?
It requires a good understanding of both the original, "source" toolset, and the destination toolset.
At the source code level, the 'C' programming language is standardised, but has a number of implementation-defined features - so you will need to check these in each toolset, and make any necessary adjustments.
Tools often add their own proprietary extensions to the language - these will not be portable, so you'll have to work out what to do.
Tools often have an option to disable all extensions - so you may be able to use that to identify if any have been used.
The linkers will be different - so you will have to understand the IAR Linker configuration, and translate that to Keil.
The Project setup will be different - so, again, you will have to understand the IAR Project configuration, and translate that to Keil.
It may be simpler to simply start again from scratch ...
there are many errors when I rebuild the project
It's obviously impossible to give any specific help without knowing what the errors are!
So just read what the errors are telling you, and fix what is wrong.
But remember that one error early in a compilation will often produce many more resulting errors in the rest of the compilation.
Therefore, always address the earliest error first - one fix is likely to cure many errors!