Creating a New Platform in TInyOS

-

What is aTinyOS Platform?

    A physical platform is comprised of a set of chips. Similarly a TinyOS platform is nothing but  collection of components representing these chips(drivers of the chips)..

How to create a New Platform?


  If the chips of the new platform are already present in the exixsting platform then implementing a new platform simply means wiring existing components. If the chips of the new platform are not present in any existing platforms then implementing the new platform consists of implementing components (drivers) for those chips and then wiring them.

Things Required For a New Platform:

    A new platform definition requires three things:

  1. Defintion of chips that creates the platform
  2. Definition of the Platform(Combining chips to platform) and
  3. Tool Chain or make definition

Chips Defintions:(tos/chips/chipX)


    Each chip will be assigned a specific directory under tos/chips.

   Each of the chips that provide software accessible functionality should have defintion in chips directory such as sensors,radios and microcontrollers.

Eg: msp430 chip has its defintion in tos/chips/msp430

Here defintions means chip specific interfaces and their implementations

Some chips such as MCU have subsystems such as ADC,SPI,UART and  Timer. then these subsystems should be placed in the subdirectory of it.for example tos/chips/chipX/timer....


If a platform is using some feature of the chip then the platform directory should contain the code that is specific to the combination of  chip and platform such as pin assignments and Interrupt assignments. It should be placed in tos/platforms/platformX/chips/chipX  for the platformX.

Eg:mica2 uses the cc1000 chips. So the platform folder of mica2 has chips directory which contains the code that is the combination of both chips and platform.

Platform Defintions:(tos/chips/PlatformX)

      A platform directory will be placed in tos/platform.
A TinyOS platform is a collection of components corresponding to physical devices.
Eg: mica2 uses the cc1000radio +Atmega128.
     The platform directory will join the components of the physical chips(drivers) together to form a platform.This is done by
  1. including the code of each of the chips
  2. providing any additional code that is specific to this particular platform.
tos/platforms/platformX should contains mainly 3 elements.

  1. .platform file which contains the include paths and other arguments for nesC.
  2. PlatformP/PlatformC file which has the Platform Boot procedure.
  3. Platform specific code such as PlatformLedsC, and code that is specific to the combination of chip and platform such as pin assignments and modifications etc
  4. hardware.h file which has hardware specific functions

Tool-Chain(Make System)


     Build system controls the process from pre-processing a TinyOS application to a single C file and will pass the file to the appropriate compiler and other tools.

We require two files:

  1. .rules file which should be placed in /support/make/MCUx
  2. .target file in the /support/make folder.


These are the files which are required to create a platform.

You can see the null platform in tos/platforms/null for reference.... There is also a TEP131 on this.. 







Comments

  1. sam27 October 2013 at 05:16

    How can we add a new radio chip to it, what all things do i need. i want to add cc3000 to my MSP430 and design a application for tinyos.

    ReplyDelete

Post a Comment

Popular posts from this blog

bb.utils.contains yocto

-
Image
bb.utils.contains  is most commonly used function in Yocto. grep in poky directory returned with 696 count. $ grep -nr 'bb.utils.contains' poky/ | wc -l 696 It's definition is present in 'poky/bitbake/lib/bb/utils.py' file This function returns third argument if the second argument is subset of the first argument else returns fourth argument Let's take an example to understand this. You can see from the above screenshot, when the second argument is a subset of first argument, "present" was returned, else "notpresent" was returned We can also use bb.utils.contains inside if loop. This we can use inside a recipe. if ${@bb.utils.contains('SOMEFLAG','NEWVALUE3','true','false',d)}; then     FOO = 'HELLO' fi
Read more

Difference between RDEPENDS and DEPENDS in Yocto

-
We normally observe these two (RDEPENDS and DEPENDS) whenever we open any recipe. What should we choose when we write our own recipe. DEPENDS -> Build Time Dependency RDEPENDS -> Run Time Dependency DEPENDS: When a recipe 'A' is DEPENDS on recipe 'B'. In this case, Bitbake first builds recipe 'B' and then recipe 'A' E.g. You need 'dbus' to be built before 'wpa_supplicant'. RDEPENDS: When a recipe 'A' is RDEPENDS on recipe 'B'. In this case, Bitbake deploys 'B' on the target system when it deploys 'A'.  E.g. 'perf' RDEPENDS on 'bash' In other words, DEPENDS are those set of packages that should be available while building package, whereas RDEPENDS are set of packages that should be available during execution of the program.
Read more

make config vs oldconfig vs defconfig vs menuconfig vs savedefconfig

-
Image
Building the Linux Kernel is a two-step process: Configuring the Kernel options Building the Kernel with those options. There are many methods available for configuring the kernel. make config: Text-based Configuration.  Options are prompted one after another. All options need to be answered Access to former options is not possible make menuconfig: Menu-driven user interface Allows to navigate forwards and backward directly between features Allows to load and save files with filenames different from ".config" Provides search feature It uses ncurses library for GUI. If the ncurses library is not installed, make menuconfig option fails. To install ncurses library on Ubuntu: sudo apt-get install libncurses5-dev make defconfig: Creates a ".config" file with default options from the ARCH supplied defconfig Configurations are generally stored in the directory: arch/$(ARCH)/configs $ ls arch/x86/configs/ i386_defconfi
Read more