Skip to main content

Notes of Raspberry Pi

Currently, there are several models of Raspberry Pi i.e. A/B, A+/B+, 2, 3 and zero. The differences are on their provided interfaces, RAM size, processor model, processing power, AV jack, etc. Pi 3 uses Broadcom BCM2837 SoC with 64-bit support. Unlike earlier models, Pi 3 has built in wireless support, including 2.4GHz Wi-Fi and bluetooth. There is a Display Serial Interface (DSI) port near GPIO port. There is also Camera Serial Interface (CSI) near HDMI port which provides a high-speed connection to the Raspberry Pi Camera Module. The Pi 3 can draw up up to 1.2A so we need power adapter that can provide 2A of current.

Warning: When handling the Pi, always avoid touching GPIO pins, and never connect anything to them while Pi is switched on. GPIO port is powerful but fragile.


Raspberry Pi Fondation supplies a software tool known as NOOBS (New Out-Of Box Software) which helps user to install standard operating system for Raspberry Pi like Raspbian and others. We can download it from There are two types of installation methods.
  1. NOOBS. It is installation software. We can download it then extract and copy it to SD card. For the first time use of Raspberry Pi, you need to follow instalation steps provided by this software.
  2. Raspbian. It is operating system image. We can export this image to SD card using any image extractor software like win32diskimager in Windows or dd in Linux. 
    # list existing disk
    $ diskutil list
    # unmount SD card if it is mounted by default
    $ diskutil unmountdisk /dev/diskX
    # write image to disk
    $ sudo dd if=imageflename.img of=/dev/sdX bs=2M
Main storage of Raspberry is the SD card. We can expand the Pi storage capacity by external drive.
# list all disks
$ sudo fdisk -l

# create directory as mounting location
$ sudo mkdir /media/externaldrive1
$ sudo chgrp -R users /media/externaldrive1
$ sudo chmod -R g+w /media/externaldrive1

# mount the drive to new directory
$ sudo mount /dev/sdXN /media/externaldrive -o=rw
Raspbian is based on Debian. The default directories in Raspbian distribution are as follows.
  • boot - contains Linux kernel and other packages to start the Pi
  • bin - stores OS-related binary files i.e. GUI files
  • dev - a virtual directory. All devices connected to the system can be found here.
  • etc - miscellaneous configuration files
  • home - stores users files
  • lib - locates bits of code required by numerous applications
  • lost+found - stores file fragments if the system crashes
  • media - locates removable storage devices
  • mnt - used to manually mount storage devices e.g. external HDD
  • opt - stores optional software that is not part of OS
  • proc - a virtual directory contains information about running programs (processes)
  • run - used by various daemons (processes which run in the background)
  • root - root user directory
  • sbin - stores special binary files primarily used by superuser account
  • srv - stores data served by OS but empty in Raspbian
  • sys - a virtual directory storing system information used by Linux kernel
  • tmp - temporary files storing
  • usr - storage for user-accessible programs
  • var - used by programs to store changing values or variables 
There is a powerfull tool which is provided by Raspian to set some basic configuration of Raspberry Pi. This tool can be run by raspi-config command. We can configure hostname, enable SSH, change boot setting, and many others.


In networking, by default the Pi will query DHCP server on the network for dynamic configuration information. We can also change its configuration to static in /etc/dhcpcd.conf. We can set static configuration for all available interfaces such as eth0, wlan0, etc. After the changes are applied, we need to restart the networking service: $ service networking restart. For wireless networking, we can run this following command to scan available connection.
$ sudo iwlist scan | less
The status of the established wireless connection can be showed by iwconfig command. There are several modes of the wireless adapter i.e. managed (standard wireless network),  ad-hoc (device-to-device), monitor (the card listens for all traffics), repeater, and secondary (backup repeater). The Pi wireless network configuration is handled by wpasupplicant tool. Using this tool, we can connect our Pi to any wireless network, WPA, WPA2, or WEP, in any mode, AES or TKIP. This tool configuration is located in /etc/wpa_supplicant/wpa_supplicant.conf. All accessed network records are stored here. If the Pi is in WPA/WPA2 encrypted connection, we will see configuration likes the following.
If it uses unsecured connection without password, there will be only ssid and key_mgmt=NONE fields. If it uses WEP secured connection, the configuration should be key_mgmt=NONE and wep_key0="<your-WEP-key>". To enable the changes, we can restart the Pi or run this command: $ sudo ifup wlan0.

If you think this article is usefull, please share it with your colleagues.


Popular posts from this blog

Rangkaian Sensor Infrared dengan Photo Dioda

Keunggulan photodioda dibandingkan LDR adalah photodioda lebih tidak rentan terhadap noise karena hanya menerima sinar infrared, sedangkan LDR menerima seluruh cahaya yang ada termasuk infrared. Rangkaian yang akan kita gunakan adalah seperti gambar di bawah ini. Pada saat intensitas Infrared yang diterima Photodiode besar maka tahanan Photodiode menjadi kecil, sedangkan jika intensitas Infrared yang diterima Photodiode kecil maka tahanan yang dimiliki photodiode besar. Jika  tahanan photodiode kecil  maka tegangan  V- akan kecil . Misal tahanan photodiode mengecil menjadi 10kOhm. Maka dengan teorema pembagi tegangan: V- = Rrx/(Rrx + R2) x Vcc V- = 10 / (10+10) x Vcc V- = (1/2) x 5 Volt V- = 2.5 Volt Sedangkan jika  tahanan photodiode besar  maka tegangan  V- akan besar  (mendekati nilai Vcc). Misal tahanan photodiode menjadi 150kOhm. Maka dengan teorema pembagi tegangan: V- = Rrx/(Rrx + R2) x Vcc V- = 150 / (150+10) x Vcc V- = (150/160) x 5

Setting Up Next.js Project With ESLint, Typescript, and AirBnB Configuration

If we initiate a Next.js project using the  create-next-app tool, our project will be included with ESLint configuration that we can apply using yarn run lint . By default, the tool installs eslint-config-next and extends next/core-web-vitals in the ESLint configuration. The Next.js configuration has been integrated with linting rules for React and several other libraries and tools. yarn create next-app --typescript For additional configuration such as AirBnB, it is also possible. First, we need to install the peer dependencies of eslint-config-airbnb . We also add support for Typescript using eslint-config-airbnb-typescript . yarn add --dev eslint-config-airbnb eslint-plugin-import eslint-plugin-jsx-a11y eslint-plugin-react eslint-plugin-react-hooks yarn add --dev eslint-config-airbnb-typescript @typescript-eslint/eslint-plugin @typescript-eslint/parser After that, we can update the .eslintrc.json file for the new configuration. { "extends": [ "airb

Configuring Swap Memory on Ubuntu Using Ansible

If we maintain a Linux machine with a low memory capacity while we are required to run an application with high memory consumption, enabling swap memory is an option. Ansible can be utilized as a helper tool to automate the creation of swap memory. A swap file can be allocated in the available storage of the machine. The swap file then can be assigned as a swap memory. Firstly, we should prepare the inventory file. The following snippet is an example, you must provide your own configuration. [server] [server:vars] ansible_user=root ansible_ssh_private_key_file=~/.ssh/id_rsa Secondly, we need to prepare the task file that contains not only the tasks but also some variables and connection information. For instance, we set /swapfile  as the name of our swap file. We also set the swap memory size to 2GB and the swappiness level to 60. - hosts: server become: true vars: swap_vars: size: 2G swappiness: 60 For simplicity, we only check the exi

Managing MongoDB Records Using NestJS and Mongoose

NestJS is a framework for developing Node.js-based applications. It provides an additional abstraction layer on top of Express or other HTTP handlers and gives developers a stable foundation to build applications with structured procedures. Meanwhile, Mongoose is a schema modeling helper based on Node.js for MongoDB. There are several main steps to be performed for allowing our program to handle MongoDB records. First, we need to add the dependencies which are @nestjs/mongoose , mongoose , and @types/mongoose . Then, we need to define the connection configuration on the application module decorator. import { MongooseModule } from '@nestjs/mongoose'; @Module({ imports: [ MongooseModule.forRoot('mongodb://localhost:27017/mydb'), ], controllers: [AppController], providers: [AppService], }) Next, we create the schema definition using helpers provided by NestJS and Mongoose. The following snippet is an example with a declaration of index setting and an o

Enabling Single Webcam for Multiple Applications Access in Linux

A webcam can not be accessed by two or more applications simultaneously. The solution is you can duplicate the video stream and make it available for any application. In short, you create a virtual webcam. First, a webcam is commonly detected on  /dev/video* . Before you go through the steps to duplicate video stream, you should check whether your webcam is working. You can try to capture video using VLC by this command. (For example, your webcam is on  /dev/video0 ) $ vlc v4l2:///dev/video0 If it doesn't work, you can try to change its mode to 0777 and make sure there are no other applications accessing it. If it still doesn't work, you can buy a new webcam. Seriously. Don't buy a cheap and unknown-brand webcam. I have $5 webcam and it had wasted my time. $ apt-get install ffmpeg linux-generic v4l2loopback-dkms FFmpeg is the main application that will access your webcam and duplicate its video stream. V4L2loopback is needed to create multiple virtual capture devic

Configure Gitlab SMTP Setting

Gitlab CE or EE is shipped with the capability to send messages through SMTP service as the basic feature to send notifications or updates to the users. The configuration parameters are available in /etc/gitlab/gitlab.rb . Each SMTP service provider has a different configuration, therefore the Gitlab configuration parameters should be adjusted according to the requirements. Some examples have been provided by Gitlab here . This is an example if you use the Zoho service. gitlab_rails['smtp_enable'] = true gitlab_rails['smtp_address'] = "" gitlab_rails['smtp_port'] = 587 gitlab_rails['smtp_authentication'] = "plain" gitlab_rails['smtp_enable_starttls_auto'] = true gitlab_rails['smtp_user_name'] = "" gitlab_rails['smtp_password'] = "mypassword" gitlab_rails['smtp_domain'] = "" This is another example of using Amazon SES w