Hi,
how do I upgrade Keil to the latest Peripheral Library (3.5.0) by ST for the STM32. It didn't succed in doing it myself without advise.
Kind regards Hans
It's not an upgrade to Keil - it's an "upgrade" to your Project.
How to upgrade, of course, depends on what you're upgrading from...
ST have some documents about changing from one version of their library to another.
Personally, I think it's probably best to leave any existing projects alone (unless you have some specific need of the later library) - and just use the new library when you start a new project...
Hi, right now I'm using the files in the RV31 directory of Keil, for example the STM32F10xR.LIB. As the peripheral library dosn't come with .LIB files, it seems to me, that I have to do something in keil. Kind regards
True - it is supplied as source. If you want a Library, you have to build it yourself.
The alternative, of course, is to just include the source files in your Project...
> The alternative, of course, is to just include the source files in your Project...
That's what I do - selectively add the source files from ST to my project. It's easy to end up with a mix of headers from Keil and ST so make sure the include path is set to the ST peripheral lib.
Easiest way to start is with the examples from ST. There's some instructions how to compile them for Keil MDK in the template folder and each example has a README.
Andrew
Thanks Guys,
i finally can compile my project again ;)
For all with the same problem: I took the template project from ST which comes with the library and deleted everything which is not necessary (all the stuff for the eval boards).
Is it complicated to build a .LIB-file out of the sources? Compiling all the C sources takes quite some time... With the LIB file it took about 1 second to compile, now it's about 50 seconds (right now i've all files included).
Shouldn't be too hard to create a library once you have all the object files you want. The tool is C:\Keil\ARM\BIN40\armar.exe and it's documented (poorly) under the "RealView Utilites Guide". There's also a section "Create a Library File" in the uVision IDE User's Guide that explains how to do it from the IDE.
It's probably easier to just use the commandline, though. If you type in armar without arguments you'll get a brief help.
Here's the real documentation on ARM's website: infocenter.arm.com/.../index.html
So don't do that, then!
Compile only the sources that you actually need.
You shouldn't be changing these files, so they shouldn't need rebuilding often...