The footprint of TinyOS is less than 400 bytes, what does this mean? Because tinyos-release-tinyos-2_1_2 I have downloaded from github repository is 56.3 MB. Which part of this is is the core or base code of tinyOS that occupies less than 400 bytes?
1
There are 1 best solutions below
Related Questions in TINYOS
- tinyos implementation of routing table for multiple nodes
- Unable to compile and return for a Python function, in a try-except structure
- Segmentation Fault error in nesC for Flooding packet acknowledgement using TinyOS
- How to run a command line in HTML using javascript?
- How the TinyOS communicates with the TelosB hardware?
- How to test Multitasking in TinyOS?
- How to connect LED's in nesC?
- How to transmit a message to particular nodes in tinyOS?
- How to fix an error : 'Could not load library 'toscomm': no toscomm in java.library.path'?
- using java to read data from serial port in Tiny OS
- Unable to compile TinyOs applications with avr-gcc 4.2.1 but able to compile with avr-gcc 3.3
- Why does this TinyOS C code file appear obfuscated?
- what is the meaning of base code in TinyOS
- C application programs for tinyos
- TinyOS UDP support?
Trending Questions
- UIImageView Frame Doesn't Reflect Constraints
- Is it possible to use adb commands to click on a view by finding its ID?
- How to create a new web character symbol recognizable by html/javascript?
- Why isn't my CSS3 animation smooth in Google Chrome (but very smooth on other browsers)?
- Heap Gives Page Fault
- Connect ffmpeg to Visual Studio 2008
- Both Object- and ValueAnimator jumps when Duration is set above API LvL 24
- How to avoid default initialization of objects in std::vector?
- second argument of the command line arguments in a format other than char** argv or char* argv[]
- How to improve efficiency of algorithm which generates next lexicographic permutation?
- Navigating to the another actvity app getting crash in android
- How to read the particular message format in android and store in sqlite database?
- Resetting inventory status after order is cancelled
- Efficiently compute powers of X in SSE/AVX
- Insert into an external database using ajax and php : POST 500 (Internal Server Error)
Popular Questions
- How do I undo the most recent local commits in Git?
- How can I remove a specific item from an array in JavaScript?
- How do I delete a Git branch locally and remotely?
- Find all files containing a specific text (string) on Linux?
- How do I revert a Git repository to a previous commit?
- How do I create an HTML button that acts like a link?
- How do I check out a remote Git branch?
- How do I force "git pull" to overwrite local files?
- How do I list all files of a directory?
- How to check whether a string contains a substring in JavaScript?
- How do I redirect to another webpage?
- How can I iterate over rows in a Pandas DataFrame?
- How do I convert a String to an int in Java?
- Does Python have a string 'contains' substring method?
- How do I check if a string contains a specific word?
Yes the distribution is over 50MB but that is the total size of both the operating system source code along with probably over a hundred full working TinyOS applications. This is pretty much similar to any Embedded C application where the source code is usually a lot bigger that any compiled application that will be eventually uploaded to the microcontroller.
When you write a TinyOS application and then compile it into C code, the actual code base will be a lot smaller. The compiled code code will be a mixture of i) the application logic that you wrote, ii) TinyOS code for interfacing with the radio and with various other components and iii) core TinyOS logic for handling core OS operations such as task scheduling.
The vast majority of the core TinyOS system components are in the 'tos/system' directory. The folder has the TinyOS system's scheduler and also has the system's
mainfile, which is calledRealMainPand is the first point of entry of the TinyOS application. This main file is usually never edited though, your application will usually listen for theBoot.Booted()event and start there.The first resource you should read in my opinion when starting off with TinyOS is the TinyOS programming book found in the '/doc/pdf/' directory of the TinyOS distribution.