I bought some Silicon Labs C8051 boards, equipment, and PC for
someone recently and am
going through a computer now. I found some SW - created by Silicon
Labs for the C8051F340
board I'm playing with now. It doesn't look like the guy ever
compiled any of this code.
There is a Keil uVision3 compiler installed - version 3.50 it
says. In several of the
source code directories I find files that I suspect are for the Keil
They have extensions of .wsp and .omf. I've tried to run the
uVision IDE and open these
files - but it doesn't seem to work with them.
Does uVision3 create or use files with these extensions, as a
project file of some sort,
and if so, how do I open them ?
Note that uVision-3 is very old indeed - long obsolete.
So what is your goal here?
Is this a load of "surplus" that you've acquired off ebay, or
Pretty sure uVision-3 didn't use .wsp - maybe some sort of
"workspace" file for some other IDE?
Maybe ask on the SiLabs forum? (don't forget to link your
.omf would be an OMF file:
first, re SiLabs 'canned' code you will be better off here
second the SiLabs 'canned' code rely VERY heavy on macros, which are
automatically included if you use the SiLabs software
third, with the SiLabs software you get a brand new unrestricted
Keui. (OK restricted as in can only be used with SiLabs chips)
Just out of interest: how do they enforce that?
The license number of course <doh>
That would restrict use of a particular installation of the
software - but would not stop you using the generated code in other
target devices ...
Of course. Nothing unusual about that.
So back to my question, then: How do they enforce that you can
only use it for SiLabs chips ?
It's the only for SiLabs chips bit that I'm asking
Let's try again:
What part don't you comprehend???
The license number can restrict what options you have for the
project. Same as it can restricts middleware features. It's hardly
Same as www2.keil.com/.../mdk
Seriously, there are ways to circumvent many protection
So they'll probably come around and slap your wrist if you break
the license agreement by being too much of a know-it-all smarty
My point is that 8051 opcodes are 8051 opcodes - they are not
specific to SiLabs.
So how can they restrict you to only loading those opcodes onto an
SiLabs 8051 chip and not a Brand-X 8051 chip?
Other than, of course, simply relying upon you to abide by the
Well done, I think you've understood it.
Like a lot of these things, it relies on a mixture of pig
ignorance and trust.
My goal was compiling SiLabs sample code and programming the
After some practice I was able to get it done - using the Keil
compiler I got in
the Silabs IDE I downloaded.
I got all this through a friend.
View all questions in Keil forum