System call explained

I recently got stuck with this problem, when i do a system (“/bin/mytestexe -s 13”)call. it  would return a 100 insted of a 1, many forums do give a lot of vague explanations why this happens. the the answer to this problem can be found in the WAIT.h file. If you go thorough this file we will get to know that. The return is 4bytes long not 8…
2byte code return, 2 byte execution info
1) bytes code return:
It shows the value my code has returned. my function (executable) used to return a 1. this makes the output 100.

2) bytes execution info
It shows the info of the command, for example the compiler could not find “/bin/mytestexe” it would return a 127 error if it cant the the file. Refer (sys/wait.h) for more details efinisions of the error codes.

New Blog…on MSP430 soon…

Finaly after a month of travel…i am back to mumbai, and i am working on a new blog/tutorial on how to get started on MSP 430xx family of Microcontrollers…they are ultra low power controllers! and TI gives free samples 🙂 all u need is a MSP Launch pad by TI which is just 4$…also check out this cool video from TI..showing how a controller can be powered from GRAPES :-O

There is a lot of Forums an wikis which will help u get started in no time…