Hi,
so I uploaded a Project from STMicroelectronics. It is the IAR Project of the iNEMO Sensor Eval-Board from STmicro.
sourceforge.net/.../download
I failed a plenty times to converting it to KEIL. (missing header files - but I surely added every folder into the includes in the settings and some points more)
If there is somebody who could help me it would be perfect.
In the uploaded file there is also my Keil Project in the EWARM-Project folder.
I have to setup a ROM offset (rom is starting at 0x8003000, because there is a ST DFU bootloader for firmware upgrade applications) in IAR the offset was done by a .icf file.
- i copied the startup file from the KEIL directory and replaced it with the IAR one. (backup also in folder)
anyway take a look into the zip archive please.
It works perfectly in IAR.
- why am I need the project in keil? Because we want to switch from the lite version of IAR to the Keil prof. and we want to debug some code with the keil compiler.
I have a ST-Link and a KEIL uLINK2 and a ULINK PRO debugger.
Please help.
I found a application note for this topic but its seems not to be for free :( url: www.cmc.ca/.../CMC-00200-01917.aspx
with regards Sam
I think you mean downloaded?
Anyhow, ST usually provide both Keil & IAR (and a couple of other) Projects - have you checked?
yep downloaded. sorry for that :)
STMicro offers a SDK with the inemo board but it's sadly just a IAR project.
You are right. Normaly STM provides both project files but in this case they only provide a IAR project with the SDK :((
wr sam
sourceforge.net/.../download i do not think you will find anything from STMicroelectronics at sourceforge.
Erik
instead of critics according to my bad english. here a symbolic chart instead:
inemo SDK from STM (IAR Project) ----> DOWNloaded to my PC
Project modified and tried to convert it to Keil ----> Zipped
Zipped archive ----> UPloaded to Sourceforge
!!!
Have ST given you the required license to upload their source code to SourceForge?
Just because a company have example code available on their web site, doesn't mean that they don't have valid copyrights on the code. Your right to download and use, does automatically imply your right to republish.
its a free to use and free to distribute SDK project!
I can modifie it, I can upload it for others etc.
anyway if you dont trust me here is the original not modified version of the IAR Project included with every inemo eval board.
FW Example and GUI: www.st.com/.../inemo_gui_2_0_0.zip
SDK: www.st.com/.../steval-mki062v2_sdk_1_0_0.zip
Now you can download and install the SDK by your selfs.
....
wr Sam
You sure?
From a license document I do believe is applicable: www.st.com/.../software_license_agreement.pdf
LICENSE STMicroelectronics (“ST”) grants You a non-exclusive, worldwide, non-transferable (whether by assignment, law, sublicense or otherwise), revocable, royalty-free limited license to: (i) make copies, prepare derivatives works, display internally and use internally the source code version of the Licensed Software for the sole and exclusive purpose of developing executable versions of such Licensed Software only for use with the Product; (ii) make copies, prepare derivatives works, display internally and use internally object code versions of the Licensed Software for the sole purpose of designing, developing and manufacturing the Products; (iii) make, use, sell, offer to sell, import or otherwise distribute Products.
Note words like "non-transferable", "display internally", "use internally", ...
It's a common assumption that "royalty-free" means public domain, i.e. void of copyright and free for any use or distribution.
it is like sharing a project with the stm std lib or cmsis. it was completly modified, i think no one at ST would say anything because its free marketing for their product.
so i would say back to topic??????
I would suggest that you download a free IAR Kickstart, and use that to build the software.
That will give you a known-good reference point from which to start...
(of course, if you can't even get it to build with IAR, then you have more fundamental problems)
is my english so bad? we have IAR and everything works fine... i just have problems to get the freertos provided with the iar project compiled in keil. im not a beginner.
So you just think it's okay to ignore "developing executable versions". You really should care more about actual license texts. If you make an open-source application - do make use of open-source code. Not code with specific licenses explicitly saying what you are doing isn't allowed.
"i just have problems to get the freertos provided with the iar project compiled"
What problems, exactly, do you have?
Surely, there must be FreeRTOS examples in Keil for you to study?
www.freertos.org/a00090.html - search for "Keil"...
i think no one at ST would say anything
But what you think is entirely beside the point there. The only thing that actually matters is what ST, and more to the point, their legal department, says, if and when they decide what to do with you.
How large a portion of your (and/or your employer's) net worth are you willing to gamble on them agreeing with your thinking, taking into account the fact that their actual license statement, as quoted here, rather obviously doesn't?
The firmware ST provides has the following LICENSE:
STMicroelectronics (“ST”) grants You a non-exclusive, worldwide, non-transferable (whether by assignment, law, sublicense or otherwise), revocable, royalty-free limited license to: (i) make copies, prepare derivatives works, display internally and use internally the source code version of the Licensed Software for the sole and exclusive purpose of developing executable versions of such Licensed Software only for use with the Product; (ii) make copies, prepare derivatives works, display internally and use internally object code versions of the Licensed Software for the sole purpose of designing, developing and manufacturing the Products; (iii) make, use, sell, offer to sell, import or otherwise distribute Products.
As far as i understand, I can publish my source code which is derivative of ST source code to be used on ST microcontroller. These source code examples meant for GUIDANCE ONLY AIMS AT PROVIDING CUSTOMERS WITH CODING INFORMATION REGARDING THEIR PRODUCTS IN ORDER FOR THEM TO SAVE TIME. I'm not 100% sure about the exact boundaries of this licence. But i saw many people publish Source code derivatives of ST on GitHub, Google code & SourceForge etc..
Don't be so selective. You only read the words that you think sounds good.
Yes - you may do derivative works.
BUT that sentence is longer than that. It continues with "for the sole and exclusive purpose of developing executable versions of such Licensed Software only for use with the Product;"
You see that "executable" word in there? So what do you then think about "sole and exclusive (inversion of inclusive) purpose of developing executable versions?
No sentence saying you can upload the source code. But that you can make use of the source code for creating your own product.
"for the sole purpose of designing, developing and manufacturing the Products;"
So you can a bit simplified share information within company or with factory when producing your product. But no right to distributing your source code.
And "distribute Products"
You can sell or give away the final product. But no license right to distribute your product with the source code. The license does not contain any single line implying that the code is open-source.
But back to start of the text. Consider: "non-exclusive, worldwide, non-transferable (whether by assignment, law, sublicense or otherwise), revocable, royalty-free limited license"
Non-transferable means that you can't sublicense the code. It's a license from ST to you. But if someone else also wants the code, they have to make use of that same non-exclusive license from ST to them. That is incompatible with putting the information on SourceForge.
"Revocable" How would ST be able to do that, if you think you are in the right to sublicense, without conditions, the code to anyone who can locate SourceForge?
"limited license" Maybe _you_ could inform us exactly what _you_ think the limitations are.
Maybe time you consider getting a lawyer, since you do not do too good reading the legalese. And you have been - on a public forum - informed about the license issues. That is usually a good time to backtrack, and consider a different route.
"But i saw many people publish Source code derivatives of ST on GitHub, Google code & SourceForge etc.."
I have seen many examples of people uploading Hollywood movies to share hubs. Does that make it legal? Does that make it safe? Does that mean lawyers can't send a letter requiring lots of money for copyright infringements?
As I did write in a previous post: "It's a common assumption that "royalty-free" means public domain, i.e. void of copyright and free for any use or distribution."
This code is not in the public domain. It is explicitly protected by a license. And you are stepping on that license, violating the rights of the copyright holder.
Get ideas from the code. But do not lift the code, if you want to implement an open-source application. Because it isn't in your right to do that, and it's in ST:s right to sue you. Or lift all of the code, if you only distribute executable binaries. Because you are allowed to give away or sell the final product that is the result of compiling the source code. As long as you don't combine the code from this package with code from the GPL license - the GPL license don't allow GPL-covered code to mix with proprietary code. And since you stil haven't the license for the ST code, you would not only violate the ST license but also the GPL license if you make any project that combines GPL code with this code.