The Raspberry pi is a device which uses the Broadcom controller chip which is a SoC (System on Chip). This SoC has the powerful ARM11 processor which runs on 700 MHz at its core. This powerful processor and the controller having the peripherals like timers, interrupt controller, GPIO, PCM / I2S, DMA controller, I2C, SPI slave, PWM, UART, USB, graphical processing unit (GPU) which includes VideoCore, MPEG-2 and MPEG-4 and a 512 MB SDRAM makes it a mini-computer.
The Raspberrypi board is powerful enough to run large operating systems like Linux, Mac and Windows. Linux operating systems especially Ubuntu is preferred for all kind of programming and development. The operating systems like Archlinux ARM, OpenELEC, Pidora, Raspbmc, RISC OS and the Raspbian and also Ubuntu versions are available for the Raspberrypi board. The immediate advantage of having an Operating System like Ubuntu running on an embedded system device like Raspberrypi is Multi-User-Multitasking.
In this project the Raspberrypi board is loaded with Ubuntu and is remotely accessed using VNC. The Raspberrypi board is also connected to the internet. There are 26 connectors which can be taken out from the connector port of the Raspberrypi board. All the connector pins are taken out using 13*2 pin female connectors and at the other end of their wire 26 pin Burg stick male connectors are attached. The Burg stick male connectors allow each pin out from the Raspberrypi board to be plugged into the holes of a breadboard. To access the pins that coming out of the Broadcom controller of the Raspberrypi board using C language, a C library is available called “bcm2835” which has been downloaded and installed.
A signal is sent for the purpose of notifying the process about something that required immediate attention. Different signals are used to notify different events and the signals are differentiated by their signal numbers. The list of all the available signals in the OS and their signal numbers can be obtained using the following command;
The following table gives a list of the most common signals that a process might encounter in an Operating System;
|SIGHUP||1||Linux sends a process this signal when it becomes disconnected from a terminal.|
|SIGINT||2||Linux sends a process this signal when the user tries to end it by
|SIGILL||4||Linux sends a process this signal when it attempts to execute an illegal instruction.|
|SIGABRT||6||Linux sends a process this signal to the process when the process calls the ‘abort ()’ function|
|SIGFPE||8||Linux sends a process this signal when it has executed an invalid floating-point math instruction|
|SIGKILL||9||Linux sends a process this signal to end it immediately|
|SIGUSR1||10||User programs can send this signal to other process|
|SIGUSR2||12||User programs can send this signal to other process|
|SIGSEGV||11||Linux sends a process this signal when the program has attempted an invalid memory access|
|SIGPIPE||13||Linux sends a process this signal when the program has attempted to access a broken data stream, such as a socket connection that has been already closed|
|SIGALRM||14||A process can receive this signal from the Linux using the function alarm(), after a time period mentioned in its argument.|
|SIGTERM||15||Linux sends a process this signal requesting it to terminate|
|SIGCHLD||17||Linux sends a process this signal when a child process exits|
|SIGXCPU||24||Linux sends a process this signal when it exceeds the limit of
CPU time that it can consume.
|SIGVTALRM||26||A process can receive this signal from the Linux using the function setitimer (), after a time period mentioned in its argument.|
This particular project is based on continuously receiving and handling the signal number 14, the SIGALRM. A process can receive the SIGALRM signal from the OS by calling a function named ‘alarm ()’, the prototype of which is defined in the header file <signal.h>.
The OS will send the SIGALRM to the process after a time period mentioned in the parameter passed to the function during the function call. A single call to the alarm () will receive a single SIGALRM signal only. To receive a SIGALRM at continuous interval of time, the same function needs to be called after receiving each SIGALRM. The better method is to use set a timer which can continuously generate the SIGALRM signals at specified intervals of time.
The ‘set interval timer’ function can be used to set a timer which can continuously generate the SIGALRM signals at specified intervals of time.
For mroe detail: How to Use Timer in Raspberry Pi
Current Project / Post can also be found using:
- how to run timer in raspberry pi
- https://yandex ru/clck/jsredir?from=yandex ru;search;web;;&text=&etext=1836 LHZ0LzhdmHFnNmiT8mKoQm0OTEifuQTIYKDEQP2phNWTClsMl3Qc5GbJl0Ngprjb 6131e577db46e71fc9cb2937b22578fb45bc4432&uuid=&state=_BLhILn4SxNIvvL0W45KSic66uCIg23qh8iRG98qeIXme
- raspberry internal timer
- sigalrm raspberry pi