Open Software, Open

This post is about getting started with application development over Contiki i.e. www.sics.se/contiki... Better use the release version which is latest one i.e. 2.5 rc1 in my case at the moment. Otherwise if you use development branch from CVS i.e. 2.x, than make sure you use it at your own risk :). I have the broadcast demo loosing packets for 2.x and it worked out of box for 2.4. Later got fixed in 2.5 rc1. Getting Contiki Download Contiki from  http://www.sics.se/contiki/download.html . You can setup a CVS in parallel to the latest release, in a separate folder contiki-2.x. MSP430 tools are required for Contiki building and installing. Download the MSP430 tools here  http://www.sics.se/contiki/install-and-compile.html . On this page they are located at  http://www.sics.se/~adam/msp430-gcc/ If in any of the tools installation you get error of file over write error, I got this error when installing gcc for msp430, try using  dpkg  --install --force-all  gcc

" ...your document is just great. Please put this on your blog or somewhere ... " -- Mdsr The initiation of a project can be started by any of è è Marketing Requirement Document MRD : This document is conducted by marketing team , which identifies possible product gaps in the industry. They later come up with MRD, highlighting what market is anticipating in the future. This serves as stimulus for product/project initiation. It can be regarded as a wish list + requirement. è Software Requirement Specification SRS : This document is composed by Technical Management at the company. They take input from MRD and devise how to achieve what is proposed by marketing guys. If marketing guys are just beating about the bush, than engineering starts from this document. This document explains the product composition and/or product placement. It shows what is required and where, but not shows how. *There is an IEEE standard for SRS, which is just amazing template to u

I successfully fixed the hardware issue which was causing the interrupt to loose over I2C bus. Below is the method for it. IMB400 looks something like : 1.8KOhm resistor is required, its very cheap and easily available. I bought it from SimLim tower here in Singapore, 4 for just 20 cents. Its 1/4W 5% tolerance . The IMB400 sensor board, containing Camera, Microphone and Speaker required a pull-up resistor attached between VCC and R8 to work with Linux 2.6.29b image . The need of the resistor is mentioned as Currently this driver requires a pull up resistor on the data line of the gpio based i2c bus. I have a 1K8 resistor between vcc at the side of the board and the right pad of r8. Without this only this nothing can currently be read back from the chip. There are set of commands to run the sample application making use of the camera driver OV7470. After careful soldering the back of IMB400 scanned back image looks like below: The file system image, blob, and kernel images a

Ok, I have to admit that I am trying to shift my JAVA development to JDeveloper, though natively I am an Eclipse user. I found some issues in the JDeveloper, thought better to report them to you since I am unaware of any fix/issue/bug tracking system. In JDeveloper if you have the Application Navigator opened, and you just expand and collapse the > Projects, it flickers alot. I switched to Classic theme. This is propotional to the items within the project. The more the number of items, the more the flickering is.  I am using Ubuntu 10.04 LTS, Running on Lenovo X200. Anti-aliasing Not able to deleted in a newly created java file in a newly create java project

Imote2 Camera driver for TinyOS is available in contribution directory of  TinyOS 2.x . It goes by the name of  tinyos-2.x-contrib . Its location within is  tinyos-2.x-contrib/intelmote2/apps I am assuming that you have tinyos-2.1.1 installed, this is required to have Camera Driver build. If you dont have it installed... than better have it done by invoking: apt-get install tinyos-2.1.1 From here on to get the driver working,  the procedure is as follows: Browse to opt directory. cd /opt The recommended way to get the source of tinyos-2.x and tinyos-2.x-contribis is through CVS. echo "Getting TinyOS 2.x and TinyOS 2.x-contrib from CVS" echo "Press enter when asked for password." cvs -d:pserver:anonymous@tinyos.cvs.sourceforge.net:/cvsroot/tinyos login cvs -z3 -d:pserver:anonymous@tinyos.cvs.sourceforge.net:/cvsroot/tinyos co -P tinyos-2.x cvs -z3 -d:pserver:anonymous@tinyos.cvs.sourceforge.net:/cvsroot/tinyos co -P tinyos-2.x-contrib --OR--  echo "