Booting Process in TinyOS

-
In our programs we always be wiring in our configuration file Boot interface to MainC

 component.Boot->MainC.Boot;

 So from this MainC is the component which is providing the Boot Interface. But when you look at the code in the MainC component. You will find that Boot=RealMainP. It means whenever you call MainC.Boot it automatically goes to RealMainP.Boot.. It means that RealMainP  signals the event booted() of the Boot interface.

 Now we will see what are the steps before it signals the booted() event of Boot interface.

 Step1: Platform_bootstrap();
          call Scheduler.init();
Here he is initializing the scheduler so that any components can posts tasks and initializing all the other hardware related stuff.

 Step2: call PlatformInit.init();
       while(call Scheduler.runNextTask());

 Initializing the platform. Then spinning on the scheduler to check whether all the tasks are completed. If all the  tasks are completed runNextTask() will return FALSE .

 Step3: call SoftwareInit.init();
          while(call Scheduler.runNextTask());

 Initializing the software and waiting until all the tasks to complete by spinning on the scheduler. If no tasks remain it means that the system has successfully booted.

 Step4: __nesc_enable_interrupts();
        signal Boot.booted();

    Enabling Interrupts and signal the booted event that the system has successfully booted.

 So RealMainP component will signal the booted() event after initializing the scheduler,platform,software and enabling the interrupts....

Comments

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