Re: Keil Uvision 4 Full Version
Velasco Thibault
all:I updated my keil MDK version to the latest which is V5.37,and then I found that the project can't build anymore.since the V5.37 do not support the compiler 5 and set the default compiler to compiler 6,I installed the compiler 5(Arm compiler version 5 ,V5.06 update7) with a independent patch.and then add the compiler 5 to the keil,set the compiler 5 as the default compiler,but keil can't build the project,build output as follows:
Keil MDK does not have a program like Processor Expert. Processor Expert (PE) will create a uVision project that you can subsequently use as the heart of your development. Processor Expert currently does not support S32K. Hopefully we can head in this direction soon. I understand that PE is inside S32-DS. uVision is the IDE of Keil MDK.
If you create a project using S32KDS - it is fairly easy to port it to uVision. I did this relatively easy with the NXP AN5413 Cookbook examples: www.keil.com/appnotes/docs/apnt_304.asp You can add or use FreeRTOS.
uVision has the utility Manage Run-Time Environment (MRTE) that you can select various components into your project. In the window below you can see components you can select. You can get the evaluation version of MDK to expand on these.
uVision supports FreeRTOS - just select it in MRTE (or Arm Keil RTX) and the files are added to your project. You can now configure FreeRTOS or Keil for your needs. Keil RTX has a Apache 2.0 license. -software/CMSIS_5
I was planing to use ARM Keil MDK lite edition as it is free and compatible with commercial products (with a 32Kb limitation). Of course I would like to use the latest version of the SDK to have the latest features and bug correction. From my understanding, the last version is v6.0.20.1338 (v6.0.20.1338 release note).
I don't really understand this warning. Did it means that I don't have the possibility to use the latest SDK (which is not conceivable for me) or did it means that I have to use the (not included) compiler version 5?
I have tried to build an example from the latest SDK 6.0.20 with the included ARM compiler (v6) and as the guide tells us, the LTO option prevents us to build it. But if I disable this option the project builds.
Hi Olivier,
Thank you for posting your question online.
In order to develop your application with DA14531 you will need Keil MDK IDE.
SDK v6.0.14 and SDK v6.0.16 use ARM Compiler v5.
SDK v6.0.18 and SDK v6.0.20 (which is the latest SDK release) use ARM Compiler v6.
The DSPS SDK use ARM Compiler v5. The next version of DSPS SDK is going to be released in ARM Compiler v6.
The Codeless SDK use ARM Compiler v6 and exceeds the 32kB limitation.
ARM Keil MDK lite edition has the 32kB limitation (which will stop you from testing specific examples) and does not offer the Link Time Optimization option.
ARM Compiler v6 requires the LTO option for the most examples.
On the DA14531 you can load a firmware up to 48kB, but with the lite edition you will not be able to create a firmware over 32kB.
Now let me try to answer your questions:
The latest SDK (v6.0.20) should be used only with a licensed Keil IDE in order for all the examples to built and work as expected.
Generally, I believe that during the MDK installation you accept their Term and Conditions. In those terms it is stated that if you are going to develop a product with MDK you will have to buy a license. So, I would have to suggest you get a license if you intend to create a product, if you are just testing you can try and use the MDK Professional License which has a 30-day free period: keil.com/MDKEvaluationRequest/
Best Regards,
OV_Renesas
The SDK v6.0.20 (and v6.0.18) has been tested and qualified with LTO enabled. You could probably build a few examples with LTO disabled but we cannot provide support on that. The SDK is qualifies only with LTO enabled.
Yes, you could use SDK v6.0.16. You can find on the Release Notes all the features and issues that have been included/fixed in the most recent versions. With SDK v6.0.16 you can make an application for a commercial product.
Best Regards,
OV_Renesas
So I have understood that you don't recommend using the latest SDK version with ARM v6 compiler without LTO. But however, I haven't understood if you recommend using the latest SDK with ARM compiler v5. I have tried to install it and build an example, it builds without error.
Some precisions: to have the example to build with the latest sdk and arm compiler 5 I had to make some adjustment: I had to copy the compiler options of an old sdk example (using compiler v5) and past them in the new example. After that I had to do the same thing but for linker options. This time it was a bit more difficult some options from compiler 6 had to be combined with options from compiler 5 (--userlibpath)...
We cannot support that if any issues occur.
We support SDK v6.0.18 and SDK v6.0.20 with ARM Compiler v6 and LTO enabled.
And we support SDK v6.0.14 and SDK v6.0.16 with ARM Compiler v5, LTO must be enabled on some examples (i.e. prox_reporter).
This is the way the SDK had been tested and validated in order to be released.
If you change the settings we cannot take the responsibility that the project will actually built and work as expected.
Since you want to use the latest SDK v6.0.20 you have two options:
1) Keil uVision with ARM Compiler v6 and LTO enabled, it will require a Keil license.
2) Work with the prox_reporter example on Eclipse based IDE and try to work with GCC. There are not going to be a lot of examples available on GCC, but you can try to built your idea on the prox_reporter example which has been ported on GCC.
Best Regards,
OV_Renesas
In this tutorial, we will learn what Keil IDE is? Why it used and what are its best features. At the start, you are provided with a brief but explanatory introduction of Keil uVision and its uses. After that online source for downloading the latest version of Keil is provided along with the methods of download after that a complete explained installation method is provided. This is a second tutorial on a series of tutorials on tiva launchPad. In the first tutorial, we have seen the introduction of the Tiva launchpad.
Real time environment, code building facility, source code editing and code debugging is provided in a single powerful environment named as keil Vision IDE. It is used to accelerate your embedded software development and is an easy to use IDE. You can create individual window layout anywhere on the visual surface using keil Vision and it can also supports multiple screens.
You can easily download the latest version of keil according to the requirement from online sources. Using the website given below I will guide you how to download and get started with the latest version of keil u vision. Click on the link given below and allow you pc to switch the current running app to the online browser.
By default, it is assumed that the C++test project for running tests on Keil uVision project is created in the same location as the original Keil uVision project. This approach is not required; however it does significantly simplify the setup process, and all Test Configurations provided for running tests on Keil uVision projects are created with this assumption.
To be able to correctly execute unit testing or application monitoring, you may need to modify the original project by extending the program stack size and extending the program heap size. Typically, it should be sufficient to add about 0x1000 bytes of additional stack and heap (0x1000 for each). The size of the required additional heap and stack depends on the tests configuration and may be different for different projects configurations.
All Test Configurations for uVision projects contain a special step that will automatically build the runtime library. Thus, there is no need to perform an external build of runtime library and add its product to the linker command line.
If you prefer to use a prebuilt version of the runtime library in the testing process, you need to manually build the library and add it to the C++test build settings> linker flags. For more details, see Working with the C++test Runtime Library.
The implementation of ITM based communication channel is based on CMSIS header files and does not depend on particular hardware. It should work for all Cortex M3/M4 microcontrollers that support the ARM Core Sight Debug and Trace Technology with Instrumentation Trace Macrocell. This is the recommended solution from C++test version 7.3.2.x on. In most cases, you should not need to introduce any modifications to the communication channel implementation.
The serial communication channel is implemented specifically for the STM32F103 chip (USART2 is used by default). If you want to run testing on a different chip or use another communication channel, you may need to modify the definition of the communication channel or add a new one. The default implementation of the communication channel for the STM32F103ZE chip assumes that UART will be initialized by a hardware initialization routine provided by your project. Thus, the implementation of the communication channel init function
is left empty. If you want to perform initialization of UART inside the C++test runtime library, you need to provide the initialization code for this routine. The UART parameters will be provided via the CppTestStreamParameters structure, passed as a function argument (CppTestStreamParameters is defined in CppTestTransportRS232Common.h file). It is initialized with the values defined in the TestRunnerGenerationStep execution flow step (see the test flow definitions in Keil-specific Test Configurations).
7fc3f7cf58