Lpc2000

seangra wrote:

>--- In lpc2000@yahoogroups.com, Robert Adsett <subscriptions@a...> 
>wrote:
>
>  
>
>>'Shared' in this case I believe refers to the Linux equivalent 
>>to a dll. I don't see a way to achieve that in a micro in any 
>>sort of useful manner.
>>    
>>
>
>Let's say that I split my application into my code, and the LGPL'd 
>library.  Either can be compiled independantly of the other.  
>
>So, when compiled, I have 2 seperate binary files to load into the 
>uC.  The library must be loaded at a specific offset in the uC, and 
>must begin with a jump table containing function pointers that my code 
>requires in order to interface to it.
>
>I provide the source code to my version of the LGPL'd library to 
>anyone for free, but you must buy my side of the app.
>
>That satisfies (and is in the spirit of) the LGPL, no?
>  
>
Yes, the key is "the spirit of", empowering the user rather than 
chaining them.  For example, if a user did not want to write files to 
your MMC device (via your driver), they could get a copy of the library 
source, modify it in such a way to provide their own I/O desires, then 
load the library back into the controller.

You have empowered the user to make changes.  From a technical 
standpoint, would it work successfully?  It is an interesting idea, one 
that I have conisdered.  I would like to dynamically load programs off 
the MMC drive into RAM, then excute them from RAM.    These would be 
transitory programs, setup programs.  Where it doesn't make sense to put 
a bunch of code that only gets once a year into FLASH.

I have not looked into the technical aspects of this, have you?

BTW, I'm using newlib.

Regards,

TomW



-- 
Tom Walsh - WN3L - Embedded Systems Consultant
http://openhardware.net, http://cyberiansoftware.com
"Windows? No thanks, I have work to do..."
----------------------------------------------------