Is there anyone who has an Adapter for the Keil µVision IDE for code compilation with the Realview ARM Compiler?

I would like to evaluate how Rhapsody works together with the Keil µVision IDE.

ask willert for an evaluation www.willert.de ... these guys are the Rhapsody 8-16Bit Gurus for Rhapsody and they have everything you need...

I have ordered a demo dvd from Willert. But I thought initially there is also an Adapter for Keil from Telelogic directly.

I will see how WST meets our expectations.

I think you can also ask Telelogic to get the adapter but what you get at the end is the Willert solution. In other words -Telelogic is a Willert reseller in that case ...

BTW the adaptor from Willert is not "just" a simple adapter with some property settings . The Willer solution also contains a high performance and memory optimized Framework called the . ?? RTX ?? if I remeber well ... and they call all this a together the Willert Bridge for ARM µVision - but correct me if I'm wrong....

Hi

Mickey's right, ours is the State Of the Art Adapter. If you mail me your data I'll take care that you'll receive a demo-DVD. (If you've not already received one)

Walter

(from Willert)

Thanks for the offer, Walter, but I've already received one.

Ordered on Thursday, received via mail on Friday.

A download wouldn't have been much faster.

I have now tried to get the WST to compile code for my hardware.

But I get the following error:

"WST52ltMain.c", line 54: Error: #5: cannot open source input file "AT91SAM7S128.H": No such file or directory
#include "AT91SAM7S128.H" /* AT91SAM7S128 definitions */

It is obvious that the include path is wrong. But I have checked my make template and there the variable INCDIR2 is set correctly but it seems not to be included into the generated make file.
Instead the following option is included:
-IC:\Keil\ARM\INC\Atmel
Because WSTCPUFamily is set to Atmel and WSTCPU is set to AT91SAM7S128 but according to RXF documentation this property is not used.

Why is the INCDIR2 setting not used?

I have traced down the problem to Recompiling the libs. Since the make batch didn't run successfully it couldn't work. In the meanwhile I could solve the problem by setting the Include Path of the Component to my desired path.

I've also tried to rebuild the libs with the original make file on another machine but the same error occurs. It seems that some of the c sources of oxf are missing and therefore it is not possible to build the libs.

I can imagine that in the eval version the sources are not provided ... so you're not able to compile it for another hardware -

Better you ask Willter support directy if you have any problems in this case

Initially I had another problem with the Batch file. The reason was that there was a cygwin/MSys installed on my machine. (http://www.willert.de/page/en/page_ID/29#MakeErrors) After finding this reason I got the other error. I have already requested support from Willert.

I just thought there might be people around with the same problem. I'm using this forum as a kind of knowledgebase. So I'm posting all major problems I discover and also the solutions/workarounds I've found. I hope that's OK.

I guess that's ok ... I think the reason for this forum is to allow us to ask any kind of questions and make any kind of comments ... I just saw your cryptic error message



so my hint to you .. ask Willert ... was in reality ... "I have no idea"

Hi

I'm back from being on-the-road. I have not seen any support requests regarding this. Unfortunately.
When we send out a demo-DVD you can ask for support in case of problems (The install program gives you the email address)
OK then we support it via this:
- Off course there is no source code, if we send DVD's with source code we have found out that 50% of the people stop mailing us and work with the demo version. Sorry.
- The demo version is made for the Keil environment and the NXP LPC processor. You can install the keil compiler as well, it is on the DVD. You can even create working programs, Keil has a simulator that allows you to run programs on a PC.
- You can create stuff for an ATMEL or any other ARM processor. You set a property WST_CPUFAMILY to the right CPU family and it finds the include files

If you have any more questions, feel free to mail me at wvdheiden@willert.de

Hi Walter,

I've just forgot to post here that your support already told me, that the sources are not included. It's a pity that I first applied all the changes necessary for a new µC and then discovered that it doesn't work without the sources. But I can understand your point, of course.

I have another point to add. It's not done only by changing WSTCPUFamily, since the folder structure is different for Atmel (i.e. C:\Keil\ARM\INC\Atmel\SAM7S). I've set WSTCPUFamily=Atmel and WSTCPU=AT91SAM7S128. But WSTCPU seems not to be used at the moment, I think I've read this in the docs.
I also had to change WSTDevice=DARMATS. Since these values (INCDIR2, DEVICE) have to be changed in the WST52lt.mak I assumed that I have to rebuild the libs.

So the compiled libs for LPC should also work with my Atmel ARM7?
I had an error which was not obvious to me so I assumed it has to do with the wrong lib. But some days later my colleague told me the same error and he's not working with WST at all.

Thanks for your help.

doublette, please remove

Hi

Yes they should all work. The code for the arm is the same. Sources are delivered for the relevant parts like timer etc. They are compiled by Rhapsody.

We have included help (start/WST Framework/RXF doc and some getting started stuff. Perhaps you should read that first.

We have, however, discovered one error. Since we included the last version of Keil in the last minute, off course Murphy hit us with a change in the keil linker. You need to add --device DARMP (double minus!!) to link succesfully.

If you send me a mail on my email address, I can send you an eval version with source. You have to sign an NDA first but then I can send you a full version.

Walter