librelist archives

limitations of the free SW tools?

From:

Peter Mc Collum

Date:

2010-01-27 @ 01:25

Hi Peter,

I haven't bought the watch yet, but I'm curious to hear from you (or 
anyone!) about what exactly can be accomplished by using only the Free SW 
tools. A couple of guys on the ChronosWiki indicated that you have to buy 
the non-free tools to really do anything, but I wonder if that was an 
exaggeration...?

Someone said that only "main.c" can be modified, but the real 
functionality is in lower-level modules...?

 

Thanks,

Pete
 
> Date: Mon, 25 Jan 2010 19:41:42 -0800
> From: peterj@benlo.com
> Subject: [chronos] Door Lock Control
> To: chronos@librelist.com
> 
> Found on the web:
> 
> Zachary Shivers and Ziyan Zhou blogged recently about their use of the watch 
> to unlock a door. Source in the svn.
> 
> https://ziyan.info/2010/01/secure-wireless-door-lock/
> 
> I like the tap method for entering the code (shave and a haircut, two 
> bits). That has some interesting potential for applications where pressing 
> the buttons could be difficult.
> 
> The project was put together for the MSP430 Ultra-Low Power Challenge:
> 
> http://www.designmsp430.com/default.aspx
> 
> For those new to the MSP430, there is lots of good source code there to 
> browse and analyse.
> 
> Just got my watch in the mail today. Looking forward to playing with it 
> soon.
> 
> Peter
> 
> 
 		 	   		  

 Today I spent some time playing with the Door Lock project:

 https://ziyan.info/2010/01/secure-wireless-door-lock/

The project compiles fine, no errors.
Unfortunately the code is too big for the IAR Kick-Start version.

For this reason I arranged the IAR Eval-Version which does not have a
size limit (but a time limit).
Unfortunately I still get:
Fatal Error[e89]: Too much object code produced (more than 0x4000
bytes) for this package

Does anybody else use the Eval version?
Did I miss some settings?

If you are interested I am willing to share the compiling Door Lock project.

Cheers,
Mario