Porting a IAR Project to Keil (stm32 + freertos)

"Anyway I contacted ST to get a clear answer and maybe a permission to share my project wich bases on the ST Lib and Code Example's provided with my eval-board in technical forums.
So I hope they give me a quick answer."

And that is the correct route to go.
Step 1 - check what licenses apply.
Step 2 (if needed) - make explicit questions/requests to the license holder.

Note that the ST forum moderators aren't employed by the legal department. Their task would probably be described as "helpful with a low profile".

The interesting thing is that companies often have interesting licenses. Like the manufacturer of a USB thumb memory who had a license forbidding use on multiple computers. I obviously can't connect it to multiple computers concurrently, since it basically forms its own hardware lock. And on the other hand, it's explicitly sold (explicitly mentioned in their marketing material) for transfer of data between computers, so they can't mean that it must be permanently locked down to a single computer.

When companies publish dumb licenses, we can increase their costs by writing them and ask specific questions about the licenses. Sometimes they do realize that it might be better to modify the license.

"Anyway I contacted ST to get a clear answer and maybe a permission to share my project wich bases on the ST Lib and Code Example's provided with my eval-board in technical forums.
So I hope they give me a quick answer."

And that is the correct route to go.
Step 1 - check what licenses apply.
Step 2 (if needed) - make explicit questions/requests to the license holder.

Note that the ST forum moderators aren't employed by the legal department. Their task would probably be described as "helpful with a low profile".

The interesting thing is that companies often have interesting licenses. Like the manufacturer of a USB thumb memory who had a license forbidding use on multiple computers. I obviously can't connect it to multiple computers concurrently, since it basically forms its own hardware lock. And on the other hand, it's explicitly sold (explicitly mentioned in their marketing material) for transfer of data between computers, so they can't mean that it must be permanently locked down to a single computer.

When companies publish dumb licenses, we can increase their costs by writing them and ask specific questions about the licenses. Sometimes they do realize that it might be better to modify the license.

ST is a case in point!

http://bit.ly/KzCLkJ

my.st.com/.../Flat.aspx

yes I postet it @ 4/24/2012 but no answers.

i think the problem is the ICF file which contains the offset and stack informations.
I can't get it run it with Keil.

Look again!

"i think the problem is the ICF file which contains the offset and stack informations.
I can't get it run it with Keil."

Presumably, because ICF files are entirely an IAR thing?

But what would that have to do with headers?

You said you have IAR, so you need to study its documentation, and use whatever features the IDE may have, to understand what this "ICF file" is doing.

Then you need to study the Keil documentation to determine how to achieve the same things with the facilities that Keil provides.

From what you say, that will need you to study the Linker Manual and look at Scatter files...

You might also look at the Configuration Wizard.
http://www.keil.com/support/man/docs/uv4/uv4_ut_configwizard.htm

As the responder in your cross-post says, are you able to set-up a Keil Project for an STM32 from scratch - or from one of the DevKit or Discovery Board examples?
That would seem like a sesible first step...

Similarly, have you looked on the FreeRTOS site for Keil examples?

Ersan.

this is something I will be doing in the very near future but I will be using RTX as I want to include into my current project

If I can get something going I will share the project with you.

Intersting little things mems sensors.

My interest is using it in conjuction with a GPS module. eg position bouncing around but no accelerations treat the system as stationary and try moderate the reported position due to GPS selectivity (is thats whats its called these day).

I have a ublox gps sat on a window sill that says its moving in a area on average 25m in diameter, but occasionaly goes for a long walk a 100 m or so away.

Danny