Olimex - User contributions [en]

PIC32-MAXI-WEB

2025-02-12T08:16:25Z

LubOlimex: /* Customer projects */

== Documents ==
Under construction

== Hardware ==
Under construction

== Software ==
Under construction

== Archived projects ==
Latest project is available at the main page of the device. In the wiki one can only find older projects, that still might be helpful. These projects are no longer officially supported. The best practice is to use the EXACT same compiler as mentioned and in most cases the exact same MPLAB version as mentioned.

Older projects released by Olimex for PIC32-MAXI-WEB:

1)PIC32-MAXI-WEB v1.01 for MPLABX 1.10 and XC32 1.20 (old) - https://www.olimex.com/Products/PIC/Development/PIC32-MAXI-WEB/resources/DemoSoftPIC32-MAXI-WEBv1_01.zip

2)PIC32-MAXI-WEB v1.01 for MPLAB 8.xx and C32 1.10B (old) - https://www.olimex.com/Products/PIC/Development/PIC32-MAXI-WEB/resources/DemoSoftPIC32-MAXI-WEBv1_01.zip

== Customer projects ==
Under construction

== FAQ ==
Under construction

[[Category:PIC_Development_Boards]]

PIC32-MAXI-WEB

2025-02-12T08:15:47Z

LubOlimex: /* Customer projects */

== Documents ==
Under construction

== Hardware ==
Under construction

== Software ==
Under construction

== Archived projects ==
Latest project is available at the main page of the device. In the wiki one can only find older projects, that still might be helpful. These projects are no longer officially supported. The best practice is to use the EXACT same compiler as mentioned and in most cases the exact same MPLAB version as mentioned.

Older projects released by Olimex for PIC32-MAXI-WEB:

1)PIC32-MAXI-WEB v1.01 for MPLABX 1.10 and XC32 1.20 (old) - https://www.olimex.com/Products/PIC/Development/PIC32-MAXI-WEB/resources/DemoSoftPIC32-MAXI-WEBv1_01.zip

2)PIC32-MAXI-WEB v1.01 for MPLAB 8.xx and C32 1.10B (old) - https://www.olimex.com/Products/PIC/Development/PIC32-MAXI-WEB/resources/DemoSoftPIC32-MAXI-WEBv1_01.zip

== Customer projects ==

== FAQ ==
Under construction

[[Category:PIC_Development_Boards]]

MOD-RFID1356MIFARE

2025-01-23T12:03:15Z

LubOlimex: /* Bootloader mode (firmware upgrade) */

= MOD-RFID1356MIFARE =

== Description ==
MOD-RFID1356MIFARE is an Olimex device that allows you to read and write NFC / MIFARE RFID tags operating at 13.56Mhz.
MOD-RFID1356MIFARE uses NXP PN532 to read and write NFC / MIFARE RFID cards. In addition we put second microcontroller on the board which allow 3 additional ways to communicate with host device: USB HID keyboard, USB CDC serial communication, and UART CMOS level for boards with UEXT.

Notice! The firmware supports Classic and Ultralight tags.

== Operation ==

Plug the board to your personal computer via mini USB cable. The red LED would start to blink.

The board can operate in the following user modes:
* USB-HID - acts as QWERTY keyboard, prints the ID of the read tags in a text field
* UART - allows connection to equipment via the serial cable at the UEXT, allows usage of different commands at fixed baud rate of 38400
* USB-CDC - same as above but via the mini USB port and can work up to 115200

Additionally there is another "service" mode:
* Bootloader mode - used to upgrade the firmware

Once the board is powered you can change the user mode of operation.

Press and hold the button. All modes would cycle and each mode is identified by a different LED behavior. Wait until you reach the desired mode of operation and release the button to set the unit in that mode. The modes change cyclically after 2-3 seconds in the following order HID-CDC-UART. The combinations of LED behavior during a button press and board mode after button release are:

* Only '''red''' led is blinking: USB-HID mode
* Only '''green''' led is blinking: USB-CDC mode
* Both '''green''' and '''red''' leds are blinking: UART mode

The mode selected is saved, in the event of power down and power up, the last mode selected gets loaded.

The blinking would remain after the new mode is entered to indicate the current mode. You can disable the LEDs (e.g. to save power) with ml0 command.

If you have disabled the LEDs with ml1 command - you can check the current mode with a brief button press and release - this would show the indication for the current mode of operation.

=== Bootloader mode (firmware upgrade) ===

In order to enter bootloader mode:

1. Disconnect the board from the USB cable;

2. Press and hold the button;

3. Apply the USB cable to the mini USB connector;

4. Wait at least 2 seconds and release the button.

After that you'll see both LEDs blinking one after another for a few seconds. In this mode you can upload new firmware.

==== Uploading new firmware ====
New versions of the firmware can be downloaded to the board via the mini USB connector from your personal computer with the help of a serial terminal software without the need of additional hardware.

To update the firmware we need a couple of software resources:

1.1. First install serial terminal software that is capable of sending files via the serial connection. We used the open source TeraTerm software here, and this is the terminal software that I would recommend under Windows. The web-page of TeraTerm is here: https://teratermproject.github.io/index-en.html

Linux guys should use software terminal that supports XMODEM transfer.

The serial baud rate for updating the firmware should be 19200.

1.2. Download the archive with the latest firmware that is provided by Olimex. In the archive you can find this description, the firmware img and some pictures. Link to the archive:

https://drive.google.com/open?id=1Fl1wAhNq9U5F0fSRMPaNGsKUO5fVeJWO

At this point all software requirements are already available at the PC! Proceed:

2.1. Enter the MOD-RFID1356MIFARE board in bootloader mode as described in the previous chapter.

2.2. Open "Windows Device Manager" and identify the COM port that the board created. It is in the "Ports (COM & LPT)" section. Remember the COM port number or keep the manager open for a quick reference.

2.3. (optional) If the board is listed in "Ports (COM & LPT)" but reports that the it is unrecognized, then you would need to install a driver. The driver files are located in folder "2.WINDOWS_DRIVER" - in order to install the driver point manually to to folder inf file. It usually goes like this: right-click over the entry for the unit in "Windows Device Manager" –> "Update Driver Software" –> "Browse My Computer For Driver Software" –> "Let me pick from a list of device drivers on my computer" –> mark the entry of the RFID unit –> "Have Disk" –> "Browse" –> point to olimexvirser.inf –> "Open" –> "OK" –> "Next" –> if a warning pops-up ignore it –> "Finish". You might need to disable "Windows Driver Signature" enforcement if the unit still gets blocked.

2.4. Start TeraTerm

2.5. Select the bottom radio button "Serial" and select the COM port identified in point 2.2. Click "OK"

2.6. You would establish a connection with the board and you would see "CCCC..." coming from the board. This means that the board is ready to receive new firmware.

2.7. Navigate to "File" -> "Transfer" -> "XMODEM" -> "Send..."; this would bring an explorer window and we have to point to the img file that contains the firmware. It is located in folder "FIRMWARE IMAGES" of the folder that you downloaded in point 1.2.

2.8. Once the download is complete, wait for a few seconds and power cycle the board (remove the USB cable, wait a few seconds, plug it back in). Your board now has the latest firmware.

=== Firmware releases download ===

220 - Latest release [recommended] - Added new commands: for locking key for reading; unlocking performs key reset; Fixed bash issue - now space character can also be used as separator (in addition to comma): [https://drive.google.com/open?id=1Fl1wAhNq9U5F0fSRMPaNGsKUO5fVeJWO download link 2.20]

219 - Eight release - fixed update bug preventing certain version of the firmware from successful update; added EEPROM format before firmware update; this update deletes the EEPROM contents so if you have stored important data to the MIFARE make sure to back it up before upgrading to version 219: [https://drive.google.com/file/d/1ZRUlnqpZ--S6VCTQYENmKuAcfmPT8nK0/view?usp=sharing download link 2.19]

218 - Seventh release - fixed bug - hang in CDC mode due to large string of data after printing the response to "i", "?", "h".: [https://drive.google.com/file/d/1NJQ7HW4KRrxgWmxxphnbZR3HUQiCJ1v4/view?usp=sharing download link]

216 - Sixth release - fixed two major bugs - 7 byte cards reading in CDC mode and setting saving between power downs: [https://drive.google.com/open?id=1q-9w5CbUwuigC_wTy6PdHD0-xtbRwWtn download link]

200 - Fifth release - complete re-write of the original firmware; also separate images for each mode available: [https://drive.google.com/open?id=1yp6Xmiqg5jBiMKPBvrl4Jesp89A1HV3d download link]

103 - Fourth release - fixed delay bug; several minor improvements: [https://drive.google.com/open?id=0BwplT87k9SCgcWs4VzJTeDhTcUU download link]

102 - Third release - added compatibility for MIFARE Ultralight and MIFARE Ultralight EV1 tags; several other improvements: [https://drive.google.com/file/d/0BwplT87k9SCgNkVTRkgwc0Z6QUU/view?usp=sharing download link]

101 - Second release - several improvements and fixes over release 100; most notably fixed unavailability for reading tags with EEPROM different from FF:FF:FF:FF:FF:FF:FF:FF: [https://drive.google.com/file/d/0BwplT87k9SCgNEtqOEx4dFkzelE/view?usp=sharing download link]

100 - Initial release (not recommended): [https://drive.google.com/open?id=0BwplT87k9SCgS1BkS1lwWjZjV28 download link]

=== USB-HID mode ===

The device is shown as keyboard. In this mode only the red LED blinks. On Linux machine you should see something like this:

# dmesg

usb 3-2: new full-speed USB device number 5 using ohci-pci
usb 3-2: New USB device found, idVendor=15ba, idProduct=0039
usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=220
usb 3-2: Product: MOD-RFID1356MIFARE
usb 3-2: Manufacturer: Olimex Ltd
usb 3-2: SerialNumber: 95xxxxxxxxx0C1D0
input: Olimex Ltd MOD-RFID1356MIFARE as /devices/pci0000:00/0000:00:13.0/usb4/4-4/4-4:1.0/0003:15BA:0039.0003/input/input11
hid-generic hid-generic 0003:15BA:0039.0003: input,hidraw2: USB HID v1.11 Keyboard [Olimex Ltd MOD-RFID1356MIFARE] on usb-0000:00:13.0-4/

How to use it?

Open some text editor and approach card to the reader, you will see RFID-card UUID typed as if entered by keyboard.

Note that state of your keyboard CAPSLOCK, SHIFT, CONTROL etc buttons will affect what is typen. For instance if the tag info is '''74bc3eb7''' and you press CAPSLOCK the reader will type '''74BC3EB7''', if SHIFT is pressed the reader will type '''&$BC#EB&'''

Note that there is a separate firmware that has ONLY this mode enabled.

=== USB-CDC mode ===
When you switch to this mode, only green LED is blinking, and in the terminal you'll see something like:
# dmesg

usb 3-2: new full-speed USB device number 5 using ohci-pci
usb 3-2: New USB device found, idVendor=15ba, idProduct=003a
usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=4
usb 3-2: Product: MOD-RFID1356MIFARE
usb 3-2: Manufacturer: Olimex Ltd
usb 3-2: SerialNumber: xxxxxxxxxxxxxxx
cdc_acm 3-2:1.0: ttyACM0: USB ACM device

As you can see a new device '''/dev/ttyACM0''' was created. If can be opened by any terminal emulator such as putty, minicom, etc. Since the device is USB-CDC it supports various baud rates - up to 115200.

Open device:
# picocom -b 115200 /dev/ttyACM0

Press '''Enter''' and you'll see cursor marker:
>
>
To see firmware info enter '''i''':
>i
MOD-RFID1356MIFARE
FRev: 2.00
Read WIKI at https://www.olimex.com/wiki/MOD-RFID1356MIFARE

==== COMMAND SET FOR CDC AND UART MODE ====

Note that there is no command line help in the latest firmware (no space available for help); however we introduced error messages, that can be seen! The switch to bootloader mode command was also removed. The commands available are described below follows:

i - shows information about the firmware;
erB - Read data in block B;
erS,E - Read data from block S to block E;
ewB,X - Write data to block B. X must be hex, maximum 16 bytes. If mkl enabled - should be preceded by muA;
e0 - Disable eeprom read;
e1 - Enable eeprom read;
mlE - Set led mode to disabled (E=0) or enabled (E=1);
mtF - Set scan interval. Values between 1 and 30000 are accepted;
mkK - Set work key, (K=a) for Key_A or (K=b) for Key_B;
kA - Read current key, where A is 'a', 'b' or '?'. Will not work if locked with mkl;
mkl - Locks the reading of all keys for security reasons. Disables key read kA command. The only way to disable is the mku command;
muA - set UID of target card for next write operation (A=UID);
mku - Unlocks read command and resets keys to ka=000000000000 and kb=FFFFFFFFFFFF;
kA,X - Set new key, where A is 'a' or 'b'. X is 6 bytes in hex format.

Usage if the commands is as follow:

*'''erB''' - Read data in block B. This will read 16 bytes from block B. Usually card have up to 64 blocks. For example to read what is stored in block 10 type:

>er0,7

Next time when you check card this will pop:
-1E68EFA6
Block 0 : 1E 68 EF A6 3F 88 04 00 47 B9 94 D6 45 30 36 09
Block 1 : 12 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
Block 2 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Block 3 : 00 00 00 00 00 00 FF 07 80 69 FF FF FF FF FF FF
Block 4 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Block 5 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Block 6 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Block 7 : 00 00 00 00 00 00 FF 07 80 69 FF FF FF FF FF FF
OK
>

*'''eWB,X''' - Write data to block B. X must be hex, maximum 16 bytes. This will write hex number to EEPROM. Again your card should '''NOT''' be locked. To write 0x1234 to block 9:
>ew9,1234
OK

Write will be executed only once. When you check card:
>er9
-1E68EFA6
Block 9 : 12 34 FF FF FF FF FF FF FF FF FF FF FF FF FF FF
OK

The remaining unused bytes are replaced with F.

*'''e0''' - Disable eeprom read.
-74BC3EB72
Block 9 : 12 34 FF FF FF FF FF FF FF FF FF FF FF FF FF FF
OK
>e0
>
-74BC3EB7
-74BC3EB7
-74BC3EB7
*'''e1''' - Enable eeprom read.

>e1
>
-74BC3EB72
Block 9 : 12 34 FF FF FF FF FF FF FF FF FF FF FF FF FF FF
OK
-74BC3EB72
Block 9 : 12 34 FF FF FF FF FF FF FF FF FF FF FF FF FF FF
OK
*'''mlE''' - Set led mode to disabled (E=0) or enabled (E=1) To enable leds:

>ml1
OK

To disable leds:
>ml0
OK

The blinking would remain after the new mode is entered to indicate the current mode. You can disable the LEDs (e.g. to save power) with ml0 command. You can enable them with ml1 command.

If you have disabled the LEDs with ml0 command - you can check the current mode with a brief button press and release - this would show the indication for the current mode of operation.

*'''mtF''' - Set scan interval. Values between 1 and 30000 are accepted Defines scanning interval for near cards. If you want 1 second between scans:

>mt1000
OK

* '''mkA''' - mkK - Set work key, (K=a) for Key_A or (K=b) for Key_B. Key B is optional for some cards.

>mka
OK

* '''kA,X''' - Set new key, where A is 'a' or 'b'. X is 6 bits in hex format
>ka,112233445566
OK

* '''kA''' - Read current key, where A is 'a' or 'b'.
>ka
Key A : 112233445566
OK

* '''k?''' - Shows the currently selected key and the value stored, unless locked with mkl

>k?
Key B : FFFFFFFFFFFF
OK
>

* '''mkl''' - Locks the reading of all keys for security reasons. Disables key read kA command. The only way to disable is the mku command
>mkl
ok
>ka 112233445566
ok
>k?
ERR:0x7f
>ka
ERR:0x7f
>er6 7
OK
>-AA0E012C-
Block 6 : 12 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
Block 7 : 00 00 00 00 00 00 FF 07 80 69 FF FF FF FF FF FF
OK

* '''muA''' - set UID of target card for next write operation (A=UID)
>muaa0e012c
OK
>ew6 223344
OK
>-AA0E012C-
SAVED
>-AA0E012C-
Block 6 : 22 33 44 FF FF FF FF FF FF FF FF FF FF FF FF FF
OK

* '''mku''' - Unlocks read command and resets keys to ka=000000000000 and kb=FFFFFFFFFFFF
>mku
OK
>ka
Key A : 000000000000
OK
>kb
Key B : FFFFFFFFFFFF
OK
>

==== ERROR SET FOR CDC AND UART MODE ====

Error messages are now shown in the following command:

ERR:0xXX

for easier processing using scripts.

Error codes:

0x01 Time Out, the target has not answered
0x02 A CRC error has been detected by the contactless UART
0x03 A Parity error has been detected by the contactless UART
0x04 During a MIFARE anticollision/select operation, an erroneous Bit Count has been detected
0x05 Framing error during MIFARE operation
0x06 An abnormal bit-collision has been detected during bit wise anticollision at 106 kbps
0x07 Communication buffer size insufficient
0x09 RF Buffer overflow has been detected by the contactless UART (bit BufferOvfl of the
register CL_ERROR)
0x0a In active communication mode, the RF field has not been switched on in time by the
counterpart (as defined in NFCIP-1 standard)
0x0b RF Protocol error (cf. reference [4], description of the CL_ERROR register)
0x0d Temperature error: the internal temperature sensor has detected overheating, and therefore
has automatically switched off the antenna drivers
0x0e Internal buffer overflow
0x10 Invalid parameter (range, format, ...)
0x12 DEP Protocol: The the PN532 configured in target mode does not support the command received
from the initiator (the command received is not one of the following: ATR_REQ, WUP_REQ, PSL_REQ,
DEP_REQ, DSL_REQ, RLS_REQ
0x13 DEP Protocol / Mifare / ISO/IEC 14443-4: The data format does not match to the
specification.
0x14 Mifare: Authentication error (improper Key used); make sure EEPROM is present and readable
0x23 ISO/IEC 14443-3: UID Check byte is wrong
0x7f unknown command

==== Recognition problem and solution ====

In some cases, while in CDC mode, the board might get mis-recognized by the operating system. Under Linux create udev rule to ignore it, create file /etc/udev/rules.d/99-mifare.rules and inside it type:

ATTRS{idVendor}=="15ba" ATTRS{idProduct}=="003a", ENV{ID_MM_DEVICE_IGNORE}="1"

=== UART mode ===

This mode is usually meant for embedded connection. The commands and error messages are the same as in USB-CDC mode (refer to the previous section). The difference is connection method and fixed baud-rate.

Connect the USB serial converter as follows:

* UEXT pin 2 (GND) -> GND
* UEXT pin 3 (RX) -> Convertor TX
* UEXT pin 4 (TX) -> Convertor RX
 
Open serial port at baud-rate '''38400'''.

== Change log ==

=== Version 2.2.0 (26 FEB 2020) ===

* Added new commands: for locking key for reading; unlocking performs key reset
* Fixed bash issue - now space can also be used as separator (in addition to comma)

=== Version 2.1.9 (11 MAR 2019) ===

* Before updating backup any EEPROM data since the EEPROM would be formatted clean!
* Included EEPROM format before firmware upgrade, else certain version couldn't upgrade.

=== Version 2.1.8 (17 OCT 2018) ===

* Fixed hang in CDC mode due to large string of data after printing the response to "i", "?", "h".

=== Version 2.1.6 (29 AUG 2018) ===

* Fixed command saving between power-downs.
* Fixed the ID truncation of 7 byte cards.

=== Version 2.0.0 (06 SEP 2017) ===

* Completely re-written. A lot of improvements.

=== Version 1.0.3 (27 APR 2017) ===

* Fixed delay bug

=== Version 1.0.2 (3 APR 2017) ===

* Added support for Ultralight tags
* Fixed some typos

=== Version 1.0.1 (29 SEP 2016) ===

* Increased UART baudrate to 38400
* Added option for selecting authentication key

=== Version 1.0.0 (24 MAY 2016) ===

* Initial release

[[Category:RFID]]

A13-OLinuXino

2024-12-02T13:33:20Z

LubOlimex: /* Android for microSD card */

[[File:A13-OLinuXino-MAXI-WIFI-1.jpg|thumb| A13-OlinuXino-WIFI]]

[[File:A13-OLinuXino-MICRO.jpg|thumb| A13-OlinuXino-MICRO]]

The A13 processor from Allwinner runs at 1GHz with a Mali400 GPU. It was designed for integration into tablets. Olimex has made several development board designs based around this chip. This wiki page contains information about hardware and software to help make use of these development boards.

The A13 based boards currently available are 
*[https://www.olimex.com/Products/OLinuXino/A13/A13-OLinuXino-WIFI/ A13-OLinuXino-WIFI] - Recommended if your developing software for the A13 for the first time as its the only one with network connectivity.
*[https://www.olimex.com/Products/OLinuXino/A13/A13-OLinuXino/ A13-OLinuXino] - This is the same as the WIFI version but without WIFI module and NAND flash. Note: Android requires NAND flash to run, so this board can't run Android.
*[https://www.olimex.com/Products/OLinuXino/A13/A13-OLinuXino-MICRO/ A13-OLinuXino-MICRO] - Similar to the A13-OlinuXino but with less extras
*[https://www.olimex.com/Products/SOM/A13/A13-SOM-512/ A13-SOM-512] - System-on-Module A13 board recommended for users with experience in Allwinner development. Allows developing custom extensions with only the peripherals needed.
 
== Official Images from OLIMEX ==

=== Linux ===

The official Debian images are suitable only for microSD card. Information on booting Debian from the NAND might be found at the forum.

Download methods and locations might be found below!

'''Please note that you might need different Debian Linux images for different boards with different hardware - you would need to inspect the DDR3 RAM memory and use the image suitable for your board. We use either HYNIX H5TQ2G83CFR, or SAMSUNG K4B2G0846Q.'''

'''Newest official Debian release (recommended):'''

Direct download for Debian release 11.3 suitable for boards with SAMSUNG K4B2G0846Q DDR3 RAM memory: [https://ftp.olimex.com/Allwinner_Images/A13-OLinuXino/2.legacy_images_kernel_3.4.x/A13_debian_34_90_mainline_u-boot_release_11_3.7z A13 Debian Linux with kernel 3.4.90+, suitable for boards with SAMSUNG DDR3 RAM]

Direct download Debian release 10 suitable for boards with HYNIX H5TQ2G83CFR DDR3 RAM memory: [https://ftp.olimex.com/Allwinner_Images/A13-OLinuXino/2.legacy_images_kernel_3.4.x/A13_debian_34_90_WIFI_RALINK_GCC_GPIO_X_I2C_100KHz_UVC_TS_FTDI_3G_video_accell_release_10.7z Debian A13 Linux with kernel 3.4.90+, suitable for HYNIX DDR3 RAM]

'''Instructions and required files for preparing the Debian images: [https://github.com/OLIMEX/OLINUXINO/tree/master/SOFTWARE/A13/A13-build building Linux for A13-OLinuXino and A13-OLinuXino-WIFI]'''

The images include the following:
*Linux Kernel 3.4.90+
*LXDE desktop environment
*GCC 4.6
*dpkg
*git
*i2c-tools
*perl
*xorg
*Python 2.7
*vlc
*mplayer
*smplayer
*midori browser
*usb-modeswitch
*sshfs
*wvdial
*LCD and touchscreen support
*GPIO
*I2C
*SPI
*USB WIFI RTL8188CU, Ethernet AX88772B
*Audio
*PyA13 python module with GPIO,I2C,SPI support
*Default Login: '''root/olimex'''

'''Note:''' the A13-OLinuXino-SD card which we have on our webshop contain same image on 4GB Class10 fast micro sd-card, if you want to use this image please use Class10 fast card or the performance of Linux will slow down

The file A13_debian_34_75_WIFI_RALINK_GCC_GPIO_X_I2C_100KHz_UVC_TS_FTDI_video_release_9.7z is an archive of A13_debian_34_75_WIFI_RALINK_GCC_GPIO_X_I2C_100KHz_UVC_TS_FTDI_video_release_9.7z file.

So in order to write the image on SD card you have to unzip A13_debian_34_75_WIFI_RALINK_GCC_GPIO_X_I2C_100KHz_UVC_TS_FTDI_video_release_9.7z file:

For Windows use 7zip and then use Win32DiskImager.exe (http://sourceforge.net/projects/win32diskimager/) for image writing

For Linux use p7zip package. If you have no installed 7zip then type

#apt-get install p7zip

Copy A13_debian_34_75_WIFI_RALINK_GCC_GPIO_X_I2C_100KHz_UVC_TS_FTDI_video_release_9.7z file in your directory and unzip it with

#7za e A13_debian_34_75_WIFI_RALINK_GCC_GPIO_X_I2C_100KHz_UVC_TS_FTDI_video_release_9.7z

The output should be a new 4GB file named A13_debian_34_75_WIFI_RALINK_GCC_GPIO_X_I2C_100KHz_UVC_TS_FTDI_video_release_9.7z
Put 4GB SD card in your card reader and type

# ls /dev/sd

Then press two times <TAB> you will see a list of your sd devices like sda sdb sdc note that some of these devices may be your hard disk so make sure you know which one is your sd card before you proceed as you can damage your HDD if you choose the wrong sd-device. You can do this by unplugging your sd card reader and identify which "sd" devices remove from the list.
Once you know which device is your sdcard like sda use this text instead of the sdX name in the references below:

#dd if=A13_debian_34_75_WIFI_RALINK_GCC_GPIO_X_I2C_100KHz_UVC_TS_FTDI_video_release_9.7z of=/dev/sdX

The main tested onboard hardware modules are:

'''GPIO''' - they are located in /sys/class/gpio directory. Note that first you have to export GPIOs.
For example: to add PB03

root@A10:~# echo 1 > /sys/class/gpio/export

to make PB03 output

root@A10:~# echo out > /sys/class/gpio/gpio1_pb3/direction

to make PB03 high level(3.3V)

root@A10:~# echo 1 > /sys/class/gpio/gpio1_pb3/value

to make PB03 low level(0V)

root@A10:~# echo 0 > /sys/class/gpio/gpio1_pb3/value

Full list with supported GPIOs is:

gpio12_pg9 gpio1_pb3 gpio4_pe4 gpio7_pe7
gpio10_pe10 gpio13_pg10 gpio2_pb4 gpio5_pe5 gpio8_pe8
gpio11_pe11 gpio14_pg11 gpio3_pb10 gpio6_pe6 gpio9_pe9

note that:

gpio12_pg9(GPIO2/pin10) is connected to on board LED and it is multiplexed with UART3_TX and gpio13_pg10(GPIO2/pin8) is multiplexed with UART3_RX
Therfore if you want to use these ports like GPIO then UART3_TX and UART3_RX will not be available.

'''LCD''' - 4.3"(480x272), 7"(800x480), 10"(1024x600)

'''VGA''' - 800x600, 1024x768

'''Touch_screen''' - you need calibrate LCD touch screen usi it. Note that by default the X environment does not start like root user. In our case the X starts with user named olimex

Therefore if you want to use the touch screen in X environment then you have to run calibrate procedure like olimex user. For example type:

#su olimex

enter the olimex password:olimex

#sudo ts_calibrate

calibrate the touch screen and reboot the board

#sudo reboot

ASIX8877 USB-LAN - https://www.olimex.com/Products/OLinuXino/A13/USB-ETHERNET-AX88772B/

WEB camera A4TECH

MOD-WIFI-RTL8188 - https://www.olimex.com/Products/Modules/Ethernet/MOD-WIFI-RTL8188/ instructions on how to enable it might be found here: [[How_to_configure_MOD-RTL8188_on_official_OLinuXino_Debian_releases]]

USB_OTG - low/full/high USB host

USB_HOST_up - low/full/high USB host

USB_HOST_down - low/full/high USB host

mico_SD_card

I2C2(100KHz) - /dev/i2c-2

I2C1(100KHz) - /dev/i2c-1

UART3 - /dev/ttyS1

'''[https://drive.google.com/file/d/0B-bAEPML8fwlYnUwdnpkUllVNFU/edit?usp=sharing A13 Debian 4GB SD-card image armel (softfloat) with: MONO complete]'''
*Linux Kernel 3.4.67+
*XFCE4 desktop environment
*Mplayer CLI
*GCC 4.6
*iceweasel WEB browser
*LCD and touchscreen support
*GPIO
*I2C
*SPI
*USB WIFI RTL8188CU, Ethernet AX88772B
*Audio
*apache2
*dpkg
*git
*i2c-tools
*perl
*vlc
*xorg
*Scratch
*GCC
*Python 2.7.3
*PyA13 python module with GPIO,I2C,SPI support
*OpenCV
*mono-complete
*Default Login: '''root/olimex'''

 

=== Android ===

====Android for NAND====
 

There are different images depending on the screen output settings. Also there are different images depending on the WIFI module placed. Latest hardware revisions use MOD-WIFI-RTL8188ETV and an updated image.

'''
'''A13 Android NAND images with LCD 4.3" 480x272 and touchscreen:'''

[https://ftp.olimex.com/Allwinner_Images/A13-OLinuXino/4.%D0%B0ndroid_images/nand/A13_android_8G_NAND_LCD_480x272_EN_fifth_release.img A13-OLinuXino Android for NAND memory with video settings for 480x272 display output + MOD-WIFI-RTL8188ETV module]

*Android_version - 4.0.3
*Baseband version - 1.2
*Kernel version 3.0.8+
*MOD-WIFI-RTL8188ETV wifi module
*LCD 4.3" 480x272 pixels with backlight
*Touchscreen support

[https://ftp.olimex.com/Allwinner_Images/A13-OLinuXino/4.%D0%B0ndroid_images/nand/A13_android_NAND_LCD_480x272_EN_first_release.img A13-OLinuXino Android for NAND memory with video settings for 480x272 display output + MOD-WIFI-RTL8188 module]

'''
*Android_version - 4.0.3
*Baseband version - 1.2
*Kernel version 3.0.8+
*MOD-WIFI-RTL8188 wifi module
*LCD 4.3" 480x272 pixels with backlight
*Touchscreen support

'''
'''A13 Android NAND images with LCD 7" 800x480 and touchscreen support:'''

[https://ftp.olimex.com/Allwinner_Images/A13-OLinuXino/4.%D0%B0ndroid_images/nand/A13_android_8G_NAND_LCD_800x480_EN_fifh_release.img A13-OLinuXino Android for NAND memory with video settings for LCD 7" 800x480 and touchscreen]
'''

*Android_version - 4.0.3
*Baseband version - 1.2
*Kernel version 3.0.8+
*MOD-WIFI-RTL8188-ETV wifi module
*LCD 7" 800x480 pixels with backlight
*touchscreen support

[https://ftp.olimex.com/Allwinner_Images/A13-OLinuXino/4.%D0%B0ndroid_images/nand/A13_android_8G_NAND_LCD_800x480_EN_third_release.img A13-OLinuXino Android for NAND memory with video settings for LCD 7" 800x480 and touchscreen]
'''

*Android_version - 4.0.3
*Baseband version - 1.2
*Kernel version 3.0.8+
*MOD-WIFI-RTL8188 wifi module
*LCD 7" 800x480 pixels with backlight
*Touchscreen support

'''

'''A13 Android NAND images with LCD 10" 1024x600 and touchscreen support:'''

[https://ftp.olimex.com/Allwinner_Images/A13-OLinuXino/4.%D0%B0ndroid_images/nand/A13_android_8G_NAND_LCD_1024x600_EN_fifth_release.img A13-OLinuXino Android for NAND memory with video settings for LCD 10" 1024x600 and touchscreen]

'''

*Android_version - 4.0.3
*Baseband version - 1.2
*Kernel version 3.0.8+
*MOD-WIFI-RTL8188-ETV wifi module
*LCD 10" 1024x600 pixels with backlight
*Touchscreen support

'''A13 Android NAND image with VGA 800x600 support, torrents:'''

[https://ftp.olimex.com/Allwinner_Images/A13-OLinuXino/4.%D0%B0ndroid_images/nand/A13_android_8G_NAND_VGA_800x600_EN_fifth_release.img A13-OLinuXino Android for NAND memory with VGA 800x600 support]
'''
*Android_version - 4.0.3
*Baseband version - 1.2
*Kernel version 3.0.8+
*MOD-WIFI-RTL8188ETV wifi module
*VGA 800x600 pixels

[https://ftp.olimex.com/Allwinner_Images/A13-OLinuXino/4.%D0%B0ndroid_images/nand/A13_android_8G_NAND_VGA_800x600_EN_third_release.img A13-OLinuXino Android for NAND memory with VGA 800x600 support]
'''
*Android_version - 4.0.3
*Baseband version - 1.2
*Kernel version 3.0.8+
*MOD-WIFI-RTL8188 wifi module
*VGA 800x600 pixels

----

====Android for microSD card====
 

'''Torrent of Android release 3 with LCD support for microSD card (recommended):

[https://ftp.olimex.com/Allwinner_Images/A13-OLinuXino/4.%d0%b0ndroid_images/sd/a13_android_sd_800x480_USB_OTG_8G_third_release.7z A13-OLinuXino A13 Android for microSD card with video support for 800x480 LCD, release 3]

*Android_version - 4.0.3
*Baseband version - 1.2
*Kernel version 3.0.8+
*Only LCD support - 800x480 pixels

'''Older (not recommended) releases:'''

Torrent of Android release 2 with LCD support for microSD card (not recommended, the USB OTG does not work properly due to fex error): [https://ftp.olimex.com/Allwinner_Images/A13-OLinuXino/4.%d0%b0ndroid_images/sd/a13_android_sd_800x480_second_release.7z A13-OLinuXino A13 Android for microSD card with video support for 800x480 LCD, release 2]

 

==HOWTOs==

===General===

'''How to write the Debain image to a microSD card?'''

To write a Linux image to an SD card under Windows we use Win32 Disk Imager):

*Download Win32 Disk Imager [http://sourceforge.net/projects/win32diskimager/ Win32 Disk Imager]
*Insert card
*Start program
*Select file
*Click "write"

To write a Linux image to an SD card under Linux:

For instance you have an image with the file name of "debian_2g.img". It would be downloaded to the SD card connected to a Linux machine using one of the following commands:

* # dd bs=4M oflag=sync if=debian_2g.img of=/dev/sdX
or
* # cp debian_2g.img /dev/sdX

where X is the uSD card.

'''How to change VGA and LCD resolutions under Debian?'''

The default SD card setup is made with settings for 800x600 VGA video output. If you want to change to some other LCD or VGA resolution then you have to start change_display.sh script file in /root directory.

Type:

./change_display* (press 'TAB' to auto-complete)
or
./change_display_A13.sh

and press "Enter".

Then choose the resolution and the interface(LCD or VGA). Note that the selection of a specific resolution is done by navigating with the arrow keys and pressing "space" button. Make sure the asterisk marks your selection properly.

The supported resolutions are:

'''For LCD:'''

*1. 4.3" (480x272)
*2. 7" (800x480)
*3. 10" (1024x600)
 
Important: initially the boards are calibrated for a specific display. If you re-write the image (no matter whether the SD card or the NAND memory) you might need to use a mouse to calibrate the display initially. It might be impossible to calibrate it via touching the display.

'''For VGA:'''
 
*1. 800x600
*2. 1024x768
 

===Linux related===
'''How to build latest official Debian release'''

The latest official instructions might be found here:
[https://github.com/OLIMEX/OLINUXINO/tree/master/SOFTWARE/A13/A13-build building the latest official Debian release, at Olimex GitHub]

There are a number of unofficial guides to building the Debian, among them:

[https://github.com/OLIMEX/OLINUXINO/blob/master/SOFTWARE/A13/olinuxino-debian.pdf How to build Debian for A13-OLinuXino-WIFI by Marcin Twardak]

[https://github.com/linux-sunxi/u-boot-sunxi/wiki Sunxi u-boot loader] The linux-sunxi git page contains a lot of sources for all Olimex Allwinner boards.

'''How to edit my MAC address?'''

However, it is very easy to change MAC under Debian.

All you have to do is:

1. turn off the network interface (it is off by default, can be turned off by “ifdown eth0”)
2. open /etc/network/interfaces with a text editor (for instance “nano /etc/network/interfaces”)
3. add the following line under eth0 definitions: “hwaddress ether 00:11:22:33:44:55”, where 00:11:22:33:44:55 is the desired MAC address.
4. save and turn on the network interface (“ifup eth0”)

You can think of own way implementing own MAC address (for instance storing a consecutive number in the small EEPROM and then loading it).

'''How to enable WIFI?'''

Note: in the previous Debian releases the Ethernet was auto-detected and initialized during boot BUT this was causing big delays in the start-up of the board if you didn't want to use Ethernet or if there wasn't Ethernet cable connected.

You can enable it by following these two steps:

1. To check under what name the LAN is associated write "ifconfig –a"

2. If, for example, it is under eth0 name, then write: "dhclient eth0"

This should enable the Ethernet and then SSH would also be available.

'''How to enable Ethernet?'''

Note: in the previous Debian releases the Ethernet was auto-detected and initialized during boot BUT this was causing big delays in the start-up of the board if you didn't want to use Ethernet or if there wasn't Ethernet cable connected.

You can enable it by following these two steps:

1. To check under what name the LAN is associated write "ifconfig –a"

2. If, for example, it is under eth0 name, then write: "dhclient eth0"

This should enable the Ethernet and then SSH would also be available.

===Android related===
'''How to compile new Android image?'''

Good guide shared by Akshay Mathur might be found here: [https://github.com/OLIMEX/OLINUXINO/tree/master/SOFTWARE/A13/Android-JellyBean pdf instructions available at GitHub]

'''How to make code to run on power up?'''

You would need an application that works in kiosk mode. There is a lot of information available online on how to write an application capable of autostart.

'''How to access GPIOs?'''

There is an application we wrote to demonstrate how this can be done under Android. Please check the following two links:

[http://www.youtube.com/watch?v=fBydZn8FylE YouTube video of relay control via MOD-IO under Android]

[https://github.com/OLIMEX/OLINUXINO/tree/master/SOFTWARE/A13/ANDROID-MOD-IO Source code of the above example]

'''How to add PWM support?'''

There is a separate article on the subject here: [[how to add pwm]]

===Python===

The Debian Linux Python package for A13-OLinuXino is called pyA13. It is installed in the default Debian image. More information and examples on how it can be used might be found here:

[https://pypi.python.org/pypi/pyA13 Link to pyA13 package at python.org]

===Scratch===

There are a number of SCRATCH resources we have published. The following might be of interested for you if you are interested in SCRATCH or OpenCV:

[http://www.youtube.com/watch?v=Pyidx-zOsm4 YouTube video of A13-OLinuXino running SCRATCH + OPENCV interractive project with web camera]

[http://www.youtube.com/watch?v=DzmvqlQodac YouTube video of A13-OLinuXino-WIFI + SCRATCH animation of GPIO-2 connector with buttons and LEDs]

[https://github.com/OLIMEX/OLINUXINO/tree/master/SOFTWARE/A13 source code and other scratch-related project available at Github]

===How to edit board configurations and definitions in the official Debian Linux? ===

Do you want a custom video resolution output? Do you need a different port definition? Do you need to change the hardware defitions of the board?

You would need to edit the board's script.bin/script.fex file. How to do it is described in a separate article: [[How_to_edit_board_configurations_and_definitions_in_the_official_Debian_Linux]].

===How to add STK1160 video capture driver support in Kernel 3.4===

[https://www.olimex.com/wiki/STK1160-howto-linux-sunxi-3_4 STK1160] driver backport by Dimitar Tomov

==Hardware==

[https://github.com/OLIMEX/OLINUXINO/tree/master/HARDWARE/A13-OLinuXino A13-OLinuXino schematic in PDF format and Eagle CAD files]

[https://github.com/OLIMEX/OLINUXINO/tree/master/HARDWARE/A13-PDFs A13 datasheet and user manual PDFs]

[http://linux-sunxi.org/A13_Register_guide A13 Registers Guide]

GPIOs

UEXT

LCD

RTC

[[Serial connection to A13]] description of how to connect a computer to the A13 board over serial cable.

===Power supply===

The A13-OLinuXino can be partially powered over Micro USB, but to power all peripherals, a 6+ watt DC power supply between 6 and 16 volts can be used. The connector is a positive-center 2.5mm barrel plug. There is also an on-board connector for a Li-PO battery.
'''Important note: A13-OLinuXino-MICRO works with +5V only! If you apply more than 5V you will damage the board.'''

==Software==

===Linux Commands===

[[Linux-Commands]] Brief Linux Command reference

[http://linux-sunxi.org/Main_Page A generic wiki for the Allwinner devices might be found here. It contains some great detailed info]
 

=== Bare Metal programming - no OS ===

It is possible to program and debug code written directly on the chip without an OS such as linux or android. 
The advantage is no kernel overhead and tighter control of the CPU operation.

[[Bare Metal programming A13]]

=== Using an operating system - Nand flash ===

The Wifi version of the A13 board comes preprogrammed with android, which is held in the Nand flash.

The image in the Nand flash can be updated using the tools found at the following links:

[https://docs.google.com/file/d/0B7WHuNCASY8cWlZ2djh4X0QtV0U/edit?usp=sharing LiveSuit for Windows]

[http://linux-sunxi.org/LiveSuit LiveSuit for loading images]

to the NAND flash; to activate A13 bootloader do as follows: run Livesuit, disconnect the power supply and USB cable, then press HOME button, apply power supply, attach USB cable and release the button, Livesuit will detect the bootloader and will ask which file to program to the NAND flash.

Prebuilt images that can be programmed into the Nand flash can be found here.

=== Using an operating system - SD card ===
The A13 board can boot from an SD card. Just plug it in an imaged uSD card and connect power.

Note: The SD card can easily be corrupted if power is removed while the system is booting or writing to system files.
To avoid this do not remove power while it is booting and shut the system down properly before disconnecting power.

==== Prebuilt images ====

Some prebuilt images have been created, follow the link below for details.

[[Prebuilt SD card images running debian]]

==== Build your own kernel and image onto SD card ====

Some developers want more control over the kernel and modules that are included. The link below shows directions to build your own kernel and image it onto an SD card.

[[Build Bootable SD Card with Debian]] Step by step instructions how to make SD card image with above Kernel and U-boot

====Setup and configure the installed debian image====

There are several settings that can be made for a particular hardware configuration in the script file.

The following link explains the script file as well as wifi or ethernet setup and GPIO settings

[[Configuration of hardware in the debian image]]

====Installing UsbVideoClass(UVC) on A13-OLinuXino board====

To work with USB Video Cameras you have to enable the UVC support in the kernel. The link below explains how to do it.

[[UVC support]]

====Setup VLC player for video streaming on A13-OLinuXino board====

To setup video streaming you should first have installed UVC support so you can connect USB cameras to A13-OLinuXino.

[[VLC streaming]]

=== Creating a program to run on the A13-OlinuXino board ===

[[Programming for A13 in debian]] Step by step instructions to make your first hello world program run on the A13 board running debian.

=== Software links ===

[http://linux-sunxi.org/Sunxi-tools Tools to hack A13-OLinuXino]

[http://olimex.wordpress.com/2012/11/23/running-debian-with-xfce4-on-a13-olinuxino/ Installing Xfce4 graphical interface on Debian] How to install XFCE4 on A13-OLinuXino

=== A13-SDK Android 4.0.3 ICS ===

The official Allwinner repository contains all official files, including the files required to build Android ACS 4.0.3 NAND image for A13-OLinuXino-WIFI.

[https://github.com/allwinner-dev-team Allwinner's official GitHub]

=== A13-SDK Android 4.1 JB ===

This is version 1.5 of A13-SDK which builds Android 4.1 Jelly Beans image. It works slower than 4.0.3 and we personally do not see any advantage to use 4.1 vs 4.0.3

[http://emicrotec.at/public/ Andreas Auer kindly offered to host this 4GB image]

== Projects ==
Projects people from the olinuxino community are working on or have finished and how they did it.

'''LINUX:''' 
[[Build Bootable SD Card with Debian]] Run Debian and u-boot, Step by step instructions how to make SD card image. 
[[Prebuilt SD card images running debian]]

[http://olimex.wordpress.com/2014/03/06/bootling-linux-on-a13-for-less-than-1-second/ Booting Linux for less than 1 second] optimization made by Miroslav Bendik.

[http://olimex.wordpress.com/2012/10/23/a13-olinuxino-playing-with-gpios/ Change GPIOs using scripts in linux]

[https://www.olimex.com/forum/index.php?topic=436.msg4066#msg4066 A13 OLinuXino fast GPIO with /dev/mem now achieve up to 2 Mhz toggle]

[https://www.olimex.com/forum/index.php?topic=899.0 A13 kernel module for direct support of UEXT MOD-IO board, adding ADC, relays etc, cool project can be used as reference how to make your own kernel modules]

[https://docs.google.com/open?id=0B7WHuNCASY8cWnRrQ0tGVFMybFk Instructions how to run MOD-BT with A13-OLinuXino]

[https://github.com/asfluido/olinuxino/ Customer project of A13-OLinuXino communication via SPI with MOD-MRF89-868]

[http://olimex.wordpress.com/2013/04/18/a13-olinuxino-wifi-and-opencv-face-detection-project/ A13-Olinuxino-WIFI and opencv face detection]

[http://olimex.wordpress.com/2013/04/02/scratch-control-for-mod-io/ Controlling Relays, Switching ON/OFF of 220V appliances and home automation]

[http://olimex.wordpress.com/2013/03/28/make-door-security-logger-with-a13-olinuxino-wifi-opencv/ Door security logger, image capture]

[http://olimex.wordpress.com/2013/03/08/gps-logger-with-google-maps-viewer-made-with-a13-olinuxino-and-mod-gps/ GPS logger with google maps viewer, MOD-GPS module on UEXT]

[http://olimex.wordpress.com/2013/02/25/a13-olinuxino-web-server-with-mod-rgb-controlling-rgb-led-stripe-over-internet/ Web server with MOD-RGB controlling RGB LED strip]

'''ANDROID:''' 
[http://olimex.wordpress.com/2012/10/24/a13-olinuxino-project-control-relays-and-read-adcs-and-ios-with-android/ Interface MOD-IO board with I2C under Android ]

[http://olimex.wordpress.com/2013/03/13/mame4droid-is-running-on-a13-olinuxino/ Run old games on android mame4droid]

'''No OS''' 
[[Bare Metal programming A13]] Programming directly for the chip without an OS

'''FreedomBox:''' 
[https://wiki.debian.org/FreedomBox/UniLeipzigPractical FreedomBox/UniLeipzigPractical is the documentation of a freedom box related practical course at the AKSW Research Group at the University of Leipzig]

== List of Contributors ==

'''Henrik Nordstrom''' - a.k.a. hno, uboot for A13 development, A1X guru, Linux-Sunxi maintainer

'''Dimitar Gamishev''' - a.k.a. HEHOPMAJIEH, Linux kernel configuration for OLinuXino, Android images, LCD touchscreen

'''Alexandro Mery''' - a.k.a. mnemoc, Linux-Sunxi maintainer

'''Davide Fabbri''' - Linaro kernel and lubuntu image

'''Scott Anderson''' - A13 wiki maintainer

'''Jeffrey Wischkaemper''' - a.k.a. jwischka, A13-OLinuXino Debian image with X

'''Maxime Ripard''' - ARM Linux patches

'''Jason Plum''' - Arch Linux support

[[Main_Page]]

A13-OLinuXino

2024-12-02T13:31:51Z

LubOlimex: /* Android for NAND */

[[File:A13-OLinuXino-MAXI-WIFI-1.jpg|thumb| A13-OlinuXino-WIFI]]

[[File:A13-OLinuXino-MICRO.jpg|thumb| A13-OlinuXino-MICRO]]

The A13 processor from Allwinner runs at 1GHz with a Mali400 GPU. It was designed for integration into tablets. Olimex has made several development board designs based around this chip. This wiki page contains information about hardware and software to help make use of these development boards.

The A13 based boards currently available are 
*[https://www.olimex.com/Products/OLinuXino/A13/A13-OLinuXino-WIFI/ A13-OLinuXino-WIFI] - Recommended if your developing software for the A13 for the first time as its the only one with network connectivity.
*[https://www.olimex.com/Products/OLinuXino/A13/A13-OLinuXino/ A13-OLinuXino] - This is the same as the WIFI version but without WIFI module and NAND flash. Note: Android requires NAND flash to run, so this board can't run Android.
*[https://www.olimex.com/Products/OLinuXino/A13/A13-OLinuXino-MICRO/ A13-OLinuXino-MICRO] - Similar to the A13-OlinuXino but with less extras
*[https://www.olimex.com/Products/SOM/A13/A13-SOM-512/ A13-SOM-512] - System-on-Module A13 board recommended for users with experience in Allwinner development. Allows developing custom extensions with only the peripherals needed.
 
== Official Images from OLIMEX ==

=== Linux ===

The official Debian images are suitable only for microSD card. Information on booting Debian from the NAND might be found at the forum.

Download methods and locations might be found below!

'''Please note that you might need different Debian Linux images for different boards with different hardware - you would need to inspect the DDR3 RAM memory and use the image suitable for your board. We use either HYNIX H5TQ2G83CFR, or SAMSUNG K4B2G0846Q.'''

'''Newest official Debian release (recommended):'''

Direct download for Debian release 11.3 suitable for boards with SAMSUNG K4B2G0846Q DDR3 RAM memory: [https://ftp.olimex.com/Allwinner_Images/A13-OLinuXino/2.legacy_images_kernel_3.4.x/A13_debian_34_90_mainline_u-boot_release_11_3.7z A13 Debian Linux with kernel 3.4.90+, suitable for boards with SAMSUNG DDR3 RAM]

Direct download Debian release 10 suitable for boards with HYNIX H5TQ2G83CFR DDR3 RAM memory: [https://ftp.olimex.com/Allwinner_Images/A13-OLinuXino/2.legacy_images_kernel_3.4.x/A13_debian_34_90_WIFI_RALINK_GCC_GPIO_X_I2C_100KHz_UVC_TS_FTDI_3G_video_accell_release_10.7z Debian A13 Linux with kernel 3.4.90+, suitable for HYNIX DDR3 RAM]

'''Instructions and required files for preparing the Debian images: [https://github.com/OLIMEX/OLINUXINO/tree/master/SOFTWARE/A13/A13-build building Linux for A13-OLinuXino and A13-OLinuXino-WIFI]'''

The images include the following:
*Linux Kernel 3.4.90+
*LXDE desktop environment
*GCC 4.6
*dpkg
*git
*i2c-tools
*perl
*xorg
*Python 2.7
*vlc
*mplayer
*smplayer
*midori browser
*usb-modeswitch
*sshfs
*wvdial
*LCD and touchscreen support
*GPIO
*I2C
*SPI
*USB WIFI RTL8188CU, Ethernet AX88772B
*Audio
*PyA13 python module with GPIO,I2C,SPI support
*Default Login: '''root/olimex'''

'''Note:''' the A13-OLinuXino-SD card which we have on our webshop contain same image on 4GB Class10 fast micro sd-card, if you want to use this image please use Class10 fast card or the performance of Linux will slow down

The file A13_debian_34_75_WIFI_RALINK_GCC_GPIO_X_I2C_100KHz_UVC_TS_FTDI_video_release_9.7z is an archive of A13_debian_34_75_WIFI_RALINK_GCC_GPIO_X_I2C_100KHz_UVC_TS_FTDI_video_release_9.7z file.

So in order to write the image on SD card you have to unzip A13_debian_34_75_WIFI_RALINK_GCC_GPIO_X_I2C_100KHz_UVC_TS_FTDI_video_release_9.7z file:

For Windows use 7zip and then use Win32DiskImager.exe (http://sourceforge.net/projects/win32diskimager/) for image writing

For Linux use p7zip package. If you have no installed 7zip then type

#apt-get install p7zip

Copy A13_debian_34_75_WIFI_RALINK_GCC_GPIO_X_I2C_100KHz_UVC_TS_FTDI_video_release_9.7z file in your directory and unzip it with

#7za e A13_debian_34_75_WIFI_RALINK_GCC_GPIO_X_I2C_100KHz_UVC_TS_FTDI_video_release_9.7z

The output should be a new 4GB file named A13_debian_34_75_WIFI_RALINK_GCC_GPIO_X_I2C_100KHz_UVC_TS_FTDI_video_release_9.7z
Put 4GB SD card in your card reader and type

# ls /dev/sd

Then press two times <TAB> you will see a list of your sd devices like sda sdb sdc note that some of these devices may be your hard disk so make sure you know which one is your sd card before you proceed as you can damage your HDD if you choose the wrong sd-device. You can do this by unplugging your sd card reader and identify which "sd" devices remove from the list.
Once you know which device is your sdcard like sda use this text instead of the sdX name in the references below:

#dd if=A13_debian_34_75_WIFI_RALINK_GCC_GPIO_X_I2C_100KHz_UVC_TS_FTDI_video_release_9.7z of=/dev/sdX

The main tested onboard hardware modules are:

'''GPIO''' - they are located in /sys/class/gpio directory. Note that first you have to export GPIOs.
For example: to add PB03

root@A10:~# echo 1 > /sys/class/gpio/export

to make PB03 output

root@A10:~# echo out > /sys/class/gpio/gpio1_pb3/direction

to make PB03 high level(3.3V)

root@A10:~# echo 1 > /sys/class/gpio/gpio1_pb3/value

to make PB03 low level(0V)

root@A10:~# echo 0 > /sys/class/gpio/gpio1_pb3/value

Full list with supported GPIOs is:

gpio12_pg9 gpio1_pb3 gpio4_pe4 gpio7_pe7
gpio10_pe10 gpio13_pg10 gpio2_pb4 gpio5_pe5 gpio8_pe8
gpio11_pe11 gpio14_pg11 gpio3_pb10 gpio6_pe6 gpio9_pe9

note that:

gpio12_pg9(GPIO2/pin10) is connected to on board LED and it is multiplexed with UART3_TX and gpio13_pg10(GPIO2/pin8) is multiplexed with UART3_RX
Therfore if you want to use these ports like GPIO then UART3_TX and UART3_RX will not be available.

'''LCD''' - 4.3"(480x272), 7"(800x480), 10"(1024x600)

'''VGA''' - 800x600, 1024x768

'''Touch_screen''' - you need calibrate LCD touch screen usi it. Note that by default the X environment does not start like root user. In our case the X starts with user named olimex

Therefore if you want to use the touch screen in X environment then you have to run calibrate procedure like olimex user. For example type:

#su olimex

enter the olimex password:olimex

#sudo ts_calibrate

calibrate the touch screen and reboot the board

#sudo reboot

ASIX8877 USB-LAN - https://www.olimex.com/Products/OLinuXino/A13/USB-ETHERNET-AX88772B/

WEB camera A4TECH

MOD-WIFI-RTL8188 - https://www.olimex.com/Products/Modules/Ethernet/MOD-WIFI-RTL8188/ instructions on how to enable it might be found here: [[How_to_configure_MOD-RTL8188_on_official_OLinuXino_Debian_releases]]

USB_OTG - low/full/high USB host

USB_HOST_up - low/full/high USB host

USB_HOST_down - low/full/high USB host

mico_SD_card

I2C2(100KHz) - /dev/i2c-2

I2C1(100KHz) - /dev/i2c-1

UART3 - /dev/ttyS1

'''[https://drive.google.com/file/d/0B-bAEPML8fwlYnUwdnpkUllVNFU/edit?usp=sharing A13 Debian 4GB SD-card image armel (softfloat) with: MONO complete]'''
*Linux Kernel 3.4.67+
*XFCE4 desktop environment
*Mplayer CLI
*GCC 4.6
*iceweasel WEB browser
*LCD and touchscreen support
*GPIO
*I2C
*SPI
*USB WIFI RTL8188CU, Ethernet AX88772B
*Audio
*apache2
*dpkg
*git
*i2c-tools
*perl
*vlc
*xorg
*Scratch
*GCC
*Python 2.7.3
*PyA13 python module with GPIO,I2C,SPI support
*OpenCV
*mono-complete
*Default Login: '''root/olimex'''

 

=== Android ===

====Android for NAND====
 

There are different images depending on the screen output settings. Also there are different images depending on the WIFI module placed. Latest hardware revisions use MOD-WIFI-RTL8188ETV and an updated image.

'''
'''A13 Android NAND images with LCD 4.3" 480x272 and touchscreen:'''

[https://ftp.olimex.com/Allwinner_Images/A13-OLinuXino/4.%D0%B0ndroid_images/nand/A13_android_8G_NAND_LCD_480x272_EN_fifth_release.img A13-OLinuXino Android for NAND memory with video settings for 480x272 display output + MOD-WIFI-RTL8188ETV module]

*Android_version - 4.0.3
*Baseband version - 1.2
*Kernel version 3.0.8+
*MOD-WIFI-RTL8188ETV wifi module
*LCD 4.3" 480x272 pixels with backlight
*Touchscreen support

[https://ftp.olimex.com/Allwinner_Images/A13-OLinuXino/4.%D0%B0ndroid_images/nand/A13_android_NAND_LCD_480x272_EN_first_release.img A13-OLinuXino Android for NAND memory with video settings for 480x272 display output + MOD-WIFI-RTL8188 module]

'''
*Android_version - 4.0.3
*Baseband version - 1.2
*Kernel version 3.0.8+
*MOD-WIFI-RTL8188 wifi module
*LCD 4.3" 480x272 pixels with backlight
*Touchscreen support

'''
'''A13 Android NAND images with LCD 7" 800x480 and touchscreen support:'''

[https://ftp.olimex.com/Allwinner_Images/A13-OLinuXino/4.%D0%B0ndroid_images/nand/A13_android_8G_NAND_LCD_800x480_EN_fifh_release.img A13-OLinuXino Android for NAND memory with video settings for LCD 7" 800x480 and touchscreen]
'''

*Android_version - 4.0.3
*Baseband version - 1.2
*Kernel version 3.0.8+
*MOD-WIFI-RTL8188-ETV wifi module
*LCD 7" 800x480 pixels with backlight
*touchscreen support

[https://ftp.olimex.com/Allwinner_Images/A13-OLinuXino/4.%D0%B0ndroid_images/nand/A13_android_8G_NAND_LCD_800x480_EN_third_release.img A13-OLinuXino Android for NAND memory with video settings for LCD 7" 800x480 and touchscreen]
'''

*Android_version - 4.0.3
*Baseband version - 1.2
*Kernel version 3.0.8+
*MOD-WIFI-RTL8188 wifi module
*LCD 7" 800x480 pixels with backlight
*Touchscreen support

'''

'''A13 Android NAND images with LCD 10" 1024x600 and touchscreen support:'''

[https://ftp.olimex.com/Allwinner_Images/A13-OLinuXino/4.%D0%B0ndroid_images/nand/A13_android_8G_NAND_LCD_1024x600_EN_fifth_release.img A13-OLinuXino Android for NAND memory with video settings for LCD 10" 1024x600 and touchscreen]

'''

*Android_version - 4.0.3
*Baseband version - 1.2
*Kernel version 3.0.8+
*MOD-WIFI-RTL8188-ETV wifi module
*LCD 10" 1024x600 pixels with backlight
*Touchscreen support

'''A13 Android NAND image with VGA 800x600 support, torrents:'''

[https://ftp.olimex.com/Allwinner_Images/A13-OLinuXino/4.%D0%B0ndroid_images/nand/A13_android_8G_NAND_VGA_800x600_EN_fifth_release.img A13-OLinuXino Android for NAND memory with VGA 800x600 support]
'''
*Android_version - 4.0.3
*Baseband version - 1.2
*Kernel version 3.0.8+
*MOD-WIFI-RTL8188ETV wifi module
*VGA 800x600 pixels

[https://ftp.olimex.com/Allwinner_Images/A13-OLinuXino/4.%D0%B0ndroid_images/nand/A13_android_8G_NAND_VGA_800x600_EN_third_release.img A13-OLinuXino Android for NAND memory with VGA 800x600 support]
'''
*Android_version - 4.0.3
*Baseband version - 1.2
*Kernel version 3.0.8+
*MOD-WIFI-RTL8188 wifi module
*VGA 800x600 pixels

----

====Android for microSD card====
 

'''Torrent of Android release 3 with LCD support for microSD card (recommended):

[[Media:A13_android_sd_800x480_USB_OTG_8G_third_release.torrent‎‎|A13-OLinuXino A13 Android for microSD card with video support for 800x480 LCD, release 3]]

*Android_version - 4.0.3
*Baseband version - 1.2
*Kernel version 3.0.8+
*Only LCD support - 800x480 pixels

'''Older (not recommended) releases:'''

Torrent of Android release 2 with LCD support for microSD card (not recommended, the USB OTG does not work properly due to fex error): [[Media:A13_android_sd_800x480_second_release.torrent‎|A13-OLinuXino A13 Android for microSD card with video support for 800x480 LCD, release 2]]

 

==HOWTOs==

===General===

'''How to write the Debain image to a microSD card?'''

To write a Linux image to an SD card under Windows we use Win32 Disk Imager):

*Download Win32 Disk Imager [http://sourceforge.net/projects/win32diskimager/ Win32 Disk Imager]
*Insert card
*Start program
*Select file
*Click "write"

To write a Linux image to an SD card under Linux:

For instance you have an image with the file name of "debian_2g.img". It would be downloaded to the SD card connected to a Linux machine using one of the following commands:

* # dd bs=4M oflag=sync if=debian_2g.img of=/dev/sdX
or
* # cp debian_2g.img /dev/sdX

where X is the uSD card.

'''How to change VGA and LCD resolutions under Debian?'''

The default SD card setup is made with settings for 800x600 VGA video output. If you want to change to some other LCD or VGA resolution then you have to start change_display.sh script file in /root directory.

Type:

./change_display* (press 'TAB' to auto-complete)
or
./change_display_A13.sh

and press "Enter".

Then choose the resolution and the interface(LCD or VGA). Note that the selection of a specific resolution is done by navigating with the arrow keys and pressing "space" button. Make sure the asterisk marks your selection properly.

The supported resolutions are:

'''For LCD:'''

*1. 4.3" (480x272)
*2. 7" (800x480)
*3. 10" (1024x600)
 
Important: initially the boards are calibrated for a specific display. If you re-write the image (no matter whether the SD card or the NAND memory) you might need to use a mouse to calibrate the display initially. It might be impossible to calibrate it via touching the display.

'''For VGA:'''
 
*1. 800x600
*2. 1024x768
 

===Linux related===
'''How to build latest official Debian release'''

The latest official instructions might be found here:
[https://github.com/OLIMEX/OLINUXINO/tree/master/SOFTWARE/A13/A13-build building the latest official Debian release, at Olimex GitHub]

There are a number of unofficial guides to building the Debian, among them:

[https://github.com/OLIMEX/OLINUXINO/blob/master/SOFTWARE/A13/olinuxino-debian.pdf How to build Debian for A13-OLinuXino-WIFI by Marcin Twardak]

[https://github.com/linux-sunxi/u-boot-sunxi/wiki Sunxi u-boot loader] The linux-sunxi git page contains a lot of sources for all Olimex Allwinner boards.

'''How to edit my MAC address?'''

However, it is very easy to change MAC under Debian.

All you have to do is:

1. turn off the network interface (it is off by default, can be turned off by “ifdown eth0”)
2. open /etc/network/interfaces with a text editor (for instance “nano /etc/network/interfaces”)
3. add the following line under eth0 definitions: “hwaddress ether 00:11:22:33:44:55”, where 00:11:22:33:44:55 is the desired MAC address.
4. save and turn on the network interface (“ifup eth0”)

You can think of own way implementing own MAC address (for instance storing a consecutive number in the small EEPROM and then loading it).

'''How to enable WIFI?'''

Note: in the previous Debian releases the Ethernet was auto-detected and initialized during boot BUT this was causing big delays in the start-up of the board if you didn't want to use Ethernet or if there wasn't Ethernet cable connected.

You can enable it by following these two steps:

1. To check under what name the LAN is associated write "ifconfig –a"

2. If, for example, it is under eth0 name, then write: "dhclient eth0"

This should enable the Ethernet and then SSH would also be available.

'''How to enable Ethernet?'''

Note: in the previous Debian releases the Ethernet was auto-detected and initialized during boot BUT this was causing big delays in the start-up of the board if you didn't want to use Ethernet or if there wasn't Ethernet cable connected.

You can enable it by following these two steps:

1. To check under what name the LAN is associated write "ifconfig –a"

2. If, for example, it is under eth0 name, then write: "dhclient eth0"

This should enable the Ethernet and then SSH would also be available.

===Android related===
'''How to compile new Android image?'''

Good guide shared by Akshay Mathur might be found here: [https://github.com/OLIMEX/OLINUXINO/tree/master/SOFTWARE/A13/Android-JellyBean pdf instructions available at GitHub]

'''How to make code to run on power up?'''

You would need an application that works in kiosk mode. There is a lot of information available online on how to write an application capable of autostart.

'''How to access GPIOs?'''

There is an application we wrote to demonstrate how this can be done under Android. Please check the following two links:

[http://www.youtube.com/watch?v=fBydZn8FylE YouTube video of relay control via MOD-IO under Android]

[https://github.com/OLIMEX/OLINUXINO/tree/master/SOFTWARE/A13/ANDROID-MOD-IO Source code of the above example]

'''How to add PWM support?'''

There is a separate article on the subject here: [[how to add pwm]]

===Python===

The Debian Linux Python package for A13-OLinuXino is called pyA13. It is installed in the default Debian image. More information and examples on how it can be used might be found here:

[https://pypi.python.org/pypi/pyA13 Link to pyA13 package at python.org]

===Scratch===

There are a number of SCRATCH resources we have published. The following might be of interested for you if you are interested in SCRATCH or OpenCV:

[http://www.youtube.com/watch?v=Pyidx-zOsm4 YouTube video of A13-OLinuXino running SCRATCH + OPENCV interractive project with web camera]

[http://www.youtube.com/watch?v=DzmvqlQodac YouTube video of A13-OLinuXino-WIFI + SCRATCH animation of GPIO-2 connector with buttons and LEDs]

[https://github.com/OLIMEX/OLINUXINO/tree/master/SOFTWARE/A13 source code and other scratch-related project available at Github]

===How to edit board configurations and definitions in the official Debian Linux? ===

Do you want a custom video resolution output? Do you need a different port definition? Do you need to change the hardware defitions of the board?

You would need to edit the board's script.bin/script.fex file. How to do it is described in a separate article: [[How_to_edit_board_configurations_and_definitions_in_the_official_Debian_Linux]].

===How to add STK1160 video capture driver support in Kernel 3.4===

[https://www.olimex.com/wiki/STK1160-howto-linux-sunxi-3_4 STK1160] driver backport by Dimitar Tomov

==Hardware==

[https://github.com/OLIMEX/OLINUXINO/tree/master/HARDWARE/A13-OLinuXino A13-OLinuXino schematic in PDF format and Eagle CAD files]

[https://github.com/OLIMEX/OLINUXINO/tree/master/HARDWARE/A13-PDFs A13 datasheet and user manual PDFs]

[http://linux-sunxi.org/A13_Register_guide A13 Registers Guide]

GPIOs

UEXT

LCD

RTC

[[Serial connection to A13]] description of how to connect a computer to the A13 board over serial cable.

===Power supply===

The A13-OLinuXino can be partially powered over Micro USB, but to power all peripherals, a 6+ watt DC power supply between 6 and 16 volts can be used. The connector is a positive-center 2.5mm barrel plug. There is also an on-board connector for a Li-PO battery.
'''Important note: A13-OLinuXino-MICRO works with +5V only! If you apply more than 5V you will damage the board.'''

==Software==

===Linux Commands===

[[Linux-Commands]] Brief Linux Command reference

[http://linux-sunxi.org/Main_Page A generic wiki for the Allwinner devices might be found here. It contains some great detailed info]
 

=== Bare Metal programming - no OS ===

It is possible to program and debug code written directly on the chip without an OS such as linux or android. 
The advantage is no kernel overhead and tighter control of the CPU operation.

[[Bare Metal programming A13]]

=== Using an operating system - Nand flash ===

The Wifi version of the A13 board comes preprogrammed with android, which is held in the Nand flash.

The image in the Nand flash can be updated using the tools found at the following links:

[https://docs.google.com/file/d/0B7WHuNCASY8cWlZ2djh4X0QtV0U/edit?usp=sharing LiveSuit for Windows]

[http://linux-sunxi.org/LiveSuit LiveSuit for loading images]

to the NAND flash; to activate A13 bootloader do as follows: run Livesuit, disconnect the power supply and USB cable, then press HOME button, apply power supply, attach USB cable and release the button, Livesuit will detect the bootloader and will ask which file to program to the NAND flash.

Prebuilt images that can be programmed into the Nand flash can be found here.

=== Using an operating system - SD card ===
The A13 board can boot from an SD card. Just plug it in an imaged uSD card and connect power.

Note: The SD card can easily be corrupted if power is removed while the system is booting or writing to system files.
To avoid this do not remove power while it is booting and shut the system down properly before disconnecting power.

==== Prebuilt images ====

Some prebuilt images have been created, follow the link below for details.

[[Prebuilt SD card images running debian]]

==== Build your own kernel and image onto SD card ====

Some developers want more control over the kernel and modules that are included. The link below shows directions to build your own kernel and image it onto an SD card.

[[Build Bootable SD Card with Debian]] Step by step instructions how to make SD card image with above Kernel and U-boot

====Setup and configure the installed debian image====

There are several settings that can be made for a particular hardware configuration in the script file.

The following link explains the script file as well as wifi or ethernet setup and GPIO settings

[[Configuration of hardware in the debian image]]

====Installing UsbVideoClass(UVC) on A13-OLinuXino board====

To work with USB Video Cameras you have to enable the UVC support in the kernel. The link below explains how to do it.

[[UVC support]]

====Setup VLC player for video streaming on A13-OLinuXino board====

To setup video streaming you should first have installed UVC support so you can connect USB cameras to A13-OLinuXino.

[[VLC streaming]]

=== Creating a program to run on the A13-OlinuXino board ===

[[Programming for A13 in debian]] Step by step instructions to make your first hello world program run on the A13 board running debian.

=== Software links ===

[http://linux-sunxi.org/Sunxi-tools Tools to hack A13-OLinuXino]

[http://olimex.wordpress.com/2012/11/23/running-debian-with-xfce4-on-a13-olinuxino/ Installing Xfce4 graphical interface on Debian] How to install XFCE4 on A13-OLinuXino

=== A13-SDK Android 4.0.3 ICS ===

The official Allwinner repository contains all official files, including the files required to build Android ACS 4.0.3 NAND image for A13-OLinuXino-WIFI.

[https://github.com/allwinner-dev-team Allwinner's official GitHub]

=== A13-SDK Android 4.1 JB ===

This is version 1.5 of A13-SDK which builds Android 4.1 Jelly Beans image. It works slower than 4.0.3 and we personally do not see any advantage to use 4.1 vs 4.0.3

[http://emicrotec.at/public/ Andreas Auer kindly offered to host this 4GB image]

== Projects ==
Projects people from the olinuxino community are working on or have finished and how they did it.

'''LINUX:''' 
[[Build Bootable SD Card with Debian]] Run Debian and u-boot, Step by step instructions how to make SD card image. 
[[Prebuilt SD card images running debian]]

[http://olimex.wordpress.com/2014/03/06/bootling-linux-on-a13-for-less-than-1-second/ Booting Linux for less than 1 second] optimization made by Miroslav Bendik.

[http://olimex.wordpress.com/2012/10/23/a13-olinuxino-playing-with-gpios/ Change GPIOs using scripts in linux]

[https://www.olimex.com/forum/index.php?topic=436.msg4066#msg4066 A13 OLinuXino fast GPIO with /dev/mem now achieve up to 2 Mhz toggle]

[https://www.olimex.com/forum/index.php?topic=899.0 A13 kernel module for direct support of UEXT MOD-IO board, adding ADC, relays etc, cool project can be used as reference how to make your own kernel modules]

[https://docs.google.com/open?id=0B7WHuNCASY8cWnRrQ0tGVFMybFk Instructions how to run MOD-BT with A13-OLinuXino]

[https://github.com/asfluido/olinuxino/ Customer project of A13-OLinuXino communication via SPI with MOD-MRF89-868]

[http://olimex.wordpress.com/2013/04/18/a13-olinuxino-wifi-and-opencv-face-detection-project/ A13-Olinuxino-WIFI and opencv face detection]

[http://olimex.wordpress.com/2013/04/02/scratch-control-for-mod-io/ Controlling Relays, Switching ON/OFF of 220V appliances and home automation]

[http://olimex.wordpress.com/2013/03/28/make-door-security-logger-with-a13-olinuxino-wifi-opencv/ Door security logger, image capture]

[http://olimex.wordpress.com/2013/03/08/gps-logger-with-google-maps-viewer-made-with-a13-olinuxino-and-mod-gps/ GPS logger with google maps viewer, MOD-GPS module on UEXT]

[http://olimex.wordpress.com/2013/02/25/a13-olinuxino-web-server-with-mod-rgb-controlling-rgb-led-stripe-over-internet/ Web server with MOD-RGB controlling RGB LED strip]

'''ANDROID:''' 
[http://olimex.wordpress.com/2012/10/24/a13-olinuxino-project-control-relays-and-read-adcs-and-ios-with-android/ Interface MOD-IO board with I2C under Android ]

[http://olimex.wordpress.com/2013/03/13/mame4droid-is-running-on-a13-olinuxino/ Run old games on android mame4droid]

'''No OS''' 
[[Bare Metal programming A13]] Programming directly for the chip without an OS

'''FreedomBox:''' 
[https://wiki.debian.org/FreedomBox/UniLeipzigPractical FreedomBox/UniLeipzigPractical is the documentation of a freedom box related practical course at the AKSW Research Group at the University of Leipzig]

== List of Contributors ==

'''Henrik Nordstrom''' - a.k.a. hno, uboot for A13 development, A1X guru, Linux-Sunxi maintainer

'''Dimitar Gamishev''' - a.k.a. HEHOPMAJIEH, Linux kernel configuration for OLinuXino, Android images, LCD touchscreen

'''Alexandro Mery''' - a.k.a. mnemoc, Linux-Sunxi maintainer

'''Davide Fabbri''' - Linaro kernel and lubuntu image

'''Scott Anderson''' - A13 wiki maintainer

'''Jeffrey Wischkaemper''' - a.k.a. jwischka, A13-OLinuXino Debian image with X

'''Maxime Ripard''' - ARM Linux patches

'''Jason Plum''' - Arch Linux support

[[Main_Page]]

A13-OLinuXino

2024-12-02T06:57:46Z

LubOlimex: /* Android for NAND */

[[File:A13-OLinuXino-MAXI-WIFI-1.jpg|thumb| A13-OlinuXino-WIFI]]

[[File:A13-OLinuXino-MICRO.jpg|thumb| A13-OlinuXino-MICRO]]

The A13 processor from Allwinner runs at 1GHz with a Mali400 GPU. It was designed for integration into tablets. Olimex has made several development board designs based around this chip. This wiki page contains information about hardware and software to help make use of these development boards.

The A13 based boards currently available are 
*[https://www.olimex.com/Products/OLinuXino/A13/A13-OLinuXino-WIFI/ A13-OLinuXino-WIFI] - Recommended if your developing software for the A13 for the first time as its the only one with network connectivity.
*[https://www.olimex.com/Products/OLinuXino/A13/A13-OLinuXino/ A13-OLinuXino] - This is the same as the WIFI version but without WIFI module and NAND flash. Note: Android requires NAND flash to run, so this board can't run Android.
*[https://www.olimex.com/Products/OLinuXino/A13/A13-OLinuXino-MICRO/ A13-OLinuXino-MICRO] - Similar to the A13-OlinuXino but with less extras
*[https://www.olimex.com/Products/SOM/A13/A13-SOM-512/ A13-SOM-512] - System-on-Module A13 board recommended for users with experience in Allwinner development. Allows developing custom extensions with only the peripherals needed.
 
== Official Images from OLIMEX ==

=== Linux ===

The official Debian images are suitable only for microSD card. Information on booting Debian from the NAND might be found at the forum.

Download methods and locations might be found below!

'''Please note that you might need different Debian Linux images for different boards with different hardware - you would need to inspect the DDR3 RAM memory and use the image suitable for your board. We use either HYNIX H5TQ2G83CFR, or SAMSUNG K4B2G0846Q.'''

'''Newest official Debian release (recommended):'''

Direct download for Debian release 11.3 suitable for boards with SAMSUNG K4B2G0846Q DDR3 RAM memory: [https://ftp.olimex.com/Allwinner_Images/A13-OLinuXino/2.legacy_images_kernel_3.4.x/A13_debian_34_90_mainline_u-boot_release_11_3.7z A13 Debian Linux with kernel 3.4.90+, suitable for boards with SAMSUNG DDR3 RAM]

Direct download Debian release 10 suitable for boards with HYNIX H5TQ2G83CFR DDR3 RAM memory: [https://ftp.olimex.com/Allwinner_Images/A13-OLinuXino/2.legacy_images_kernel_3.4.x/A13_debian_34_90_WIFI_RALINK_GCC_GPIO_X_I2C_100KHz_UVC_TS_FTDI_3G_video_accell_release_10.7z Debian A13 Linux with kernel 3.4.90+, suitable for HYNIX DDR3 RAM]

'''Instructions and required files for preparing the Debian images: [https://github.com/OLIMEX/OLINUXINO/tree/master/SOFTWARE/A13/A13-build building Linux for A13-OLinuXino and A13-OLinuXino-WIFI]'''

The images include the following:
*Linux Kernel 3.4.90+
*LXDE desktop environment
*GCC 4.6
*dpkg
*git
*i2c-tools
*perl
*xorg
*Python 2.7
*vlc
*mplayer
*smplayer
*midori browser
*usb-modeswitch
*sshfs
*wvdial
*LCD and touchscreen support
*GPIO
*I2C
*SPI
*USB WIFI RTL8188CU, Ethernet AX88772B
*Audio
*PyA13 python module with GPIO,I2C,SPI support
*Default Login: '''root/olimex'''

'''Note:''' the A13-OLinuXino-SD card which we have on our webshop contain same image on 4GB Class10 fast micro sd-card, if you want to use this image please use Class10 fast card or the performance of Linux will slow down

The file A13_debian_34_75_WIFI_RALINK_GCC_GPIO_X_I2C_100KHz_UVC_TS_FTDI_video_release_9.7z is an archive of A13_debian_34_75_WIFI_RALINK_GCC_GPIO_X_I2C_100KHz_UVC_TS_FTDI_video_release_9.7z file.

So in order to write the image on SD card you have to unzip A13_debian_34_75_WIFI_RALINK_GCC_GPIO_X_I2C_100KHz_UVC_TS_FTDI_video_release_9.7z file:

For Windows use 7zip and then use Win32DiskImager.exe (http://sourceforge.net/projects/win32diskimager/) for image writing

For Linux use p7zip package. If you have no installed 7zip then type

#apt-get install p7zip

Copy A13_debian_34_75_WIFI_RALINK_GCC_GPIO_X_I2C_100KHz_UVC_TS_FTDI_video_release_9.7z file in your directory and unzip it with

#7za e A13_debian_34_75_WIFI_RALINK_GCC_GPIO_X_I2C_100KHz_UVC_TS_FTDI_video_release_9.7z

The output should be a new 4GB file named A13_debian_34_75_WIFI_RALINK_GCC_GPIO_X_I2C_100KHz_UVC_TS_FTDI_video_release_9.7z
Put 4GB SD card in your card reader and type

# ls /dev/sd

Then press two times <TAB> you will see a list of your sd devices like sda sdb sdc note that some of these devices may be your hard disk so make sure you know which one is your sd card before you proceed as you can damage your HDD if you choose the wrong sd-device. You can do this by unplugging your sd card reader and identify which "sd" devices remove from the list.
Once you know which device is your sdcard like sda use this text instead of the sdX name in the references below:

#dd if=A13_debian_34_75_WIFI_RALINK_GCC_GPIO_X_I2C_100KHz_UVC_TS_FTDI_video_release_9.7z of=/dev/sdX

The main tested onboard hardware modules are:

'''GPIO''' - they are located in /sys/class/gpio directory. Note that first you have to export GPIOs.
For example: to add PB03

root@A10:~# echo 1 > /sys/class/gpio/export

to make PB03 output

root@A10:~# echo out > /sys/class/gpio/gpio1_pb3/direction

to make PB03 high level(3.3V)

root@A10:~# echo 1 > /sys/class/gpio/gpio1_pb3/value

to make PB03 low level(0V)

root@A10:~# echo 0 > /sys/class/gpio/gpio1_pb3/value

Full list with supported GPIOs is:

gpio12_pg9 gpio1_pb3 gpio4_pe4 gpio7_pe7
gpio10_pe10 gpio13_pg10 gpio2_pb4 gpio5_pe5 gpio8_pe8
gpio11_pe11 gpio14_pg11 gpio3_pb10 gpio6_pe6 gpio9_pe9

note that:

gpio12_pg9(GPIO2/pin10) is connected to on board LED and it is multiplexed with UART3_TX and gpio13_pg10(GPIO2/pin8) is multiplexed with UART3_RX
Therfore if you want to use these ports like GPIO then UART3_TX and UART3_RX will not be available.

'''LCD''' - 4.3"(480x272), 7"(800x480), 10"(1024x600)

'''VGA''' - 800x600, 1024x768

'''Touch_screen''' - you need calibrate LCD touch screen usi it. Note that by default the X environment does not start like root user. In our case the X starts with user named olimex

Therefore if you want to use the touch screen in X environment then you have to run calibrate procedure like olimex user. For example type:

#su olimex

enter the olimex password:olimex

#sudo ts_calibrate

calibrate the touch screen and reboot the board

#sudo reboot

ASIX8877 USB-LAN - https://www.olimex.com/Products/OLinuXino/A13/USB-ETHERNET-AX88772B/

WEB camera A4TECH

MOD-WIFI-RTL8188 - https://www.olimex.com/Products/Modules/Ethernet/MOD-WIFI-RTL8188/ instructions on how to enable it might be found here: [[How_to_configure_MOD-RTL8188_on_official_OLinuXino_Debian_releases]]

USB_OTG - low/full/high USB host

USB_HOST_up - low/full/high USB host

USB_HOST_down - low/full/high USB host

mico_SD_card

I2C2(100KHz) - /dev/i2c-2

I2C1(100KHz) - /dev/i2c-1

UART3 - /dev/ttyS1

'''[https://drive.google.com/file/d/0B-bAEPML8fwlYnUwdnpkUllVNFU/edit?usp=sharing A13 Debian 4GB SD-card image armel (softfloat) with: MONO complete]'''
*Linux Kernel 3.4.67+
*XFCE4 desktop environment
*Mplayer CLI
*GCC 4.6
*iceweasel WEB browser
*LCD and touchscreen support
*GPIO
*I2C
*SPI
*USB WIFI RTL8188CU, Ethernet AX88772B
*Audio
*apache2
*dpkg
*git
*i2c-tools
*perl
*vlc
*xorg
*Scratch
*GCC
*Python 2.7.3
*PyA13 python module with GPIO,I2C,SPI support
*OpenCV
*mono-complete
*Default Login: '''root/olimex'''

 

=== Android ===

====Android for NAND====
 

There are different images depending on the screen output settings. Also there are different images depending on the WIFI module placed. Latest hardware revisions use MOD-WIFI-RTL8188ETV and an updated image.

'''
'''A13 Android NAND images with LCD 4.3" 480x272 and touchscreen:'''

[https://ftp.olimex.com/Allwinner_Images/A13-OLinuXino/4.%D0%B0ndroid_images/nand/A13_android_8G_NAND_LCD_480x272_EN_fifth_release.img A13-OLinuXino Android for NAND memory with video settings for 480x272 display output + MOD-WIFI-RTL8188ETV module]

*Android_version - 4.0.3
*Baseband version - 1.2
*Kernel version 3.0.8+
*MOD-WIFI-RTL8188ETV wifi module
*LCD 4.3" 480x272 pixels with backlight
*Touchscreen support

[https://ftp.olimex.com/Allwinner_Images/A13-OLinuXino/4.%D0%B0ndroid_images/nand/A13_android_NAND_LCD_480x272_EN_first_release.img A13-OLinuXino Android for NAND memory with video settings for 480x272 display output + MOD-WIFI-RTL8188 module]

'''
*Android_version - 4.0.3
*Baseband version - 1.2
*Kernel version 3.0.8+
*MOD-WIFI-RTL8188 wifi module
*LCD 4.3" 480x272 pixels with backlight
*Touchscreen support

'''
'''A13 Android NAND images with LCD 7" 800x480 and touchscreen support:'''

[https://ftp.olimex.com/Allwinner_Images/A13-OLinuXino/4.%D0%B0ndroid_images/nand/A13_android_8G_NAND_LCD_800x480_EN_fifh_release.img A13-OLinuXino Android for NAND memory with video settings for LCD 7" 800x480 and touchscreen]
'''

*Android_version - 4.0.3
*Baseband version - 1.2
*Kernel version 3.0.8+
*MOD-WIFI-RTL8188-ETV wifi module
*LCD 7" 800x480 pixels with backlight
*touchscreen support

[https://ftp.olimex.com/Allwinner_Images/A13-OLinuXino/4.%D0%B0ndroid_images/nand/A13_android_8G_NAND_LCD_800x480_EN_third_release.img A13-OLinuXino Android for NAND memory with video settings for LCD 7" 800x480 and touchscreen]
'''

*Android_version - 4.0.3
*Baseband version - 1.2
*Kernel version 3.0.8+
*MOD-WIFI-RTL8188 wifi module
*LCD 7" 800x480 pixels with backlight
*Touchscreen support

'''

'''A13 Android NAND images with LCD 10" 1024x600 and touchscreen support:'''

[https://ftp.olimex.com/Allwinner_Images/A13-OLinuXino/4.%D0%B0ndroid_images/nand/A13_android_8G_NAND_LCD_1024x600_EN_fifth_release.img A13-OLinuXino Android for NAND memory with video settings for LCD 10" 1024x600 and touchscreen]

'''

*Android_version - 4.0.3
*Baseband version - 1.2
*Kernel version 3.0.8+
*MOD-WIFI-RTL8188-ETV wifi module
*LCD 10" 1024x600 pixels with backlight
*Touchscreen support

'''A13 Android NAND image with VGA 800x600 support, torrents:'''

[https://ftp.olimex.com/Allwinner_Images/A13-OLinuXino/4.%D0%B0ndroid_images/nand/A13_android_8G_NAND_VGA_800x600_EN_fifth_release.img A13-OLinuXino Android for NAND memory with VGA 800x600 support]
'''
*Android_version - 4.0.3
*Baseband version - 1.2
*Kernel version 3.0.8+
*MOD-WIFI-RTL8188ETV wifi module
*VGA 800x600 pixels

[[Media:A13_android_8G_NAND_VGA_800x600_EN_third_release.torrent‎‎|A13-OLinuXino Android for NAND memory with VGA 800x600 support]]
'''
*Android_version - 4.0.3
*Baseband version - 1.2
*Kernel version 3.0.8+
*MOD-WIFI-RTL8188 wifi module
*VGA 800x600 pixels

----

====Android for microSD card====
 

'''Torrent of Android release 3 with LCD support for microSD card (recommended):

[[Media:A13_android_sd_800x480_USB_OTG_8G_third_release.torrent‎‎|A13-OLinuXino A13 Android for microSD card with video support for 800x480 LCD, release 3]]

*Android_version - 4.0.3
*Baseband version - 1.2
*Kernel version 3.0.8+
*Only LCD support - 800x480 pixels

'''Older (not recommended) releases:'''

Torrent of Android release 2 with LCD support for microSD card (not recommended, the USB OTG does not work properly due to fex error): [[Media:A13_android_sd_800x480_second_release.torrent‎|A13-OLinuXino A13 Android for microSD card with video support for 800x480 LCD, release 2]]

 

==HOWTOs==

===General===

'''How to write the Debain image to a microSD card?'''

To write a Linux image to an SD card under Windows we use Win32 Disk Imager):

*Download Win32 Disk Imager [http://sourceforge.net/projects/win32diskimager/ Win32 Disk Imager]
*Insert card
*Start program
*Select file
*Click "write"

To write a Linux image to an SD card under Linux:

For instance you have an image with the file name of "debian_2g.img". It would be downloaded to the SD card connected to a Linux machine using one of the following commands:

* # dd bs=4M oflag=sync if=debian_2g.img of=/dev/sdX
or
* # cp debian_2g.img /dev/sdX

where X is the uSD card.

'''How to change VGA and LCD resolutions under Debian?'''

The default SD card setup is made with settings for 800x600 VGA video output. If you want to change to some other LCD or VGA resolution then you have to start change_display.sh script file in /root directory.

Type:

./change_display* (press 'TAB' to auto-complete)
or
./change_display_A13.sh

and press "Enter".

Then choose the resolution and the interface(LCD or VGA). Note that the selection of a specific resolution is done by navigating with the arrow keys and pressing "space" button. Make sure the asterisk marks your selection properly.

The supported resolutions are:

'''For LCD:'''

*1. 4.3" (480x272)
*2. 7" (800x480)
*3. 10" (1024x600)
 
Important: initially the boards are calibrated for a specific display. If you re-write the image (no matter whether the SD card or the NAND memory) you might need to use a mouse to calibrate the display initially. It might be impossible to calibrate it via touching the display.

'''For VGA:'''
 
*1. 800x600
*2. 1024x768
 

===Linux related===
'''How to build latest official Debian release'''

The latest official instructions might be found here:
[https://github.com/OLIMEX/OLINUXINO/tree/master/SOFTWARE/A13/A13-build building the latest official Debian release, at Olimex GitHub]

There are a number of unofficial guides to building the Debian, among them:

[https://github.com/OLIMEX/OLINUXINO/blob/master/SOFTWARE/A13/olinuxino-debian.pdf How to build Debian for A13-OLinuXino-WIFI by Marcin Twardak]

[https://github.com/linux-sunxi/u-boot-sunxi/wiki Sunxi u-boot loader] The linux-sunxi git page contains a lot of sources for all Olimex Allwinner boards.

'''How to edit my MAC address?'''

However, it is very easy to change MAC under Debian.

All you have to do is:

1. turn off the network interface (it is off by default, can be turned off by “ifdown eth0”)
2. open /etc/network/interfaces with a text editor (for instance “nano /etc/network/interfaces”)
3. add the following line under eth0 definitions: “hwaddress ether 00:11:22:33:44:55”, where 00:11:22:33:44:55 is the desired MAC address.
4. save and turn on the network interface (“ifup eth0”)

You can think of own way implementing own MAC address (for instance storing a consecutive number in the small EEPROM and then loading it).

'''How to enable WIFI?'''

Note: in the previous Debian releases the Ethernet was auto-detected and initialized during boot BUT this was causing big delays in the start-up of the board if you didn't want to use Ethernet or if there wasn't Ethernet cable connected.

You can enable it by following these two steps:

1. To check under what name the LAN is associated write "ifconfig –a"

2. If, for example, it is under eth0 name, then write: "dhclient eth0"

This should enable the Ethernet and then SSH would also be available.

'''How to enable Ethernet?'''

Note: in the previous Debian releases the Ethernet was auto-detected and initialized during boot BUT this was causing big delays in the start-up of the board if you didn't want to use Ethernet or if there wasn't Ethernet cable connected.

You can enable it by following these two steps:

1. To check under what name the LAN is associated write "ifconfig –a"

2. If, for example, it is under eth0 name, then write: "dhclient eth0"

This should enable the Ethernet and then SSH would also be available.

===Android related===
'''How to compile new Android image?'''

Good guide shared by Akshay Mathur might be found here: [https://github.com/OLIMEX/OLINUXINO/tree/master/SOFTWARE/A13/Android-JellyBean pdf instructions available at GitHub]

'''How to make code to run on power up?'''

You would need an application that works in kiosk mode. There is a lot of information available online on how to write an application capable of autostart.

'''How to access GPIOs?'''

There is an application we wrote to demonstrate how this can be done under Android. Please check the following two links:

[http://www.youtube.com/watch?v=fBydZn8FylE YouTube video of relay control via MOD-IO under Android]

[https://github.com/OLIMEX/OLINUXINO/tree/master/SOFTWARE/A13/ANDROID-MOD-IO Source code of the above example]

'''How to add PWM support?'''

There is a separate article on the subject here: [[how to add pwm]]

===Python===

The Debian Linux Python package for A13-OLinuXino is called pyA13. It is installed in the default Debian image. More information and examples on how it can be used might be found here:

[https://pypi.python.org/pypi/pyA13 Link to pyA13 package at python.org]

===Scratch===

There are a number of SCRATCH resources we have published. The following might be of interested for you if you are interested in SCRATCH or OpenCV:

[http://www.youtube.com/watch?v=Pyidx-zOsm4 YouTube video of A13-OLinuXino running SCRATCH + OPENCV interractive project with web camera]

[http://www.youtube.com/watch?v=DzmvqlQodac YouTube video of A13-OLinuXino-WIFI + SCRATCH animation of GPIO-2 connector with buttons and LEDs]

[https://github.com/OLIMEX/OLINUXINO/tree/master/SOFTWARE/A13 source code and other scratch-related project available at Github]

===How to edit board configurations and definitions in the official Debian Linux? ===

Do you want a custom video resolution output? Do you need a different port definition? Do you need to change the hardware defitions of the board?

You would need to edit the board's script.bin/script.fex file. How to do it is described in a separate article: [[How_to_edit_board_configurations_and_definitions_in_the_official_Debian_Linux]].

===How to add STK1160 video capture driver support in Kernel 3.4===

[https://www.olimex.com/wiki/STK1160-howto-linux-sunxi-3_4 STK1160] driver backport by Dimitar Tomov

==Hardware==

[https://github.com/OLIMEX/OLINUXINO/tree/master/HARDWARE/A13-OLinuXino A13-OLinuXino schematic in PDF format and Eagle CAD files]

[https://github.com/OLIMEX/OLINUXINO/tree/master/HARDWARE/A13-PDFs A13 datasheet and user manual PDFs]

[http://linux-sunxi.org/A13_Register_guide A13 Registers Guide]

GPIOs

UEXT

LCD

RTC

[[Serial connection to A13]] description of how to connect a computer to the A13 board over serial cable.

===Power supply===

The A13-OLinuXino can be partially powered over Micro USB, but to power all peripherals, a 6+ watt DC power supply between 6 and 16 volts can be used. The connector is a positive-center 2.5mm barrel plug. There is also an on-board connector for a Li-PO battery.
'''Important note: A13-OLinuXino-MICRO works with +5V only! If you apply more than 5V you will damage the board.'''

==Software==

===Linux Commands===

[[Linux-Commands]] Brief Linux Command reference

[http://linux-sunxi.org/Main_Page A generic wiki for the Allwinner devices might be found here. It contains some great detailed info]
 

=== Bare Metal programming - no OS ===

It is possible to program and debug code written directly on the chip without an OS such as linux or android. 
The advantage is no kernel overhead and tighter control of the CPU operation.

[[Bare Metal programming A13]]

=== Using an operating system - Nand flash ===

The Wifi version of the A13 board comes preprogrammed with android, which is held in the Nand flash.

The image in the Nand flash can be updated using the tools found at the following links:

[https://docs.google.com/file/d/0B7WHuNCASY8cWlZ2djh4X0QtV0U/edit?usp=sharing LiveSuit for Windows]

[http://linux-sunxi.org/LiveSuit LiveSuit for loading images]

to the NAND flash; to activate A13 bootloader do as follows: run Livesuit, disconnect the power supply and USB cable, then press HOME button, apply power supply, attach USB cable and release the button, Livesuit will detect the bootloader and will ask which file to program to the NAND flash.

Prebuilt images that can be programmed into the Nand flash can be found here.

=== Using an operating system - SD card ===
The A13 board can boot from an SD card. Just plug it in an imaged uSD card and connect power.

Note: The SD card can easily be corrupted if power is removed while the system is booting or writing to system files.
To avoid this do not remove power while it is booting and shut the system down properly before disconnecting power.

==== Prebuilt images ====

Some prebuilt images have been created, follow the link below for details.

[[Prebuilt SD card images running debian]]

==== Build your own kernel and image onto SD card ====

Some developers want more control over the kernel and modules that are included. The link below shows directions to build your own kernel and image it onto an SD card.

[[Build Bootable SD Card with Debian]] Step by step instructions how to make SD card image with above Kernel and U-boot

====Setup and configure the installed debian image====

There are several settings that can be made for a particular hardware configuration in the script file.

The following link explains the script file as well as wifi or ethernet setup and GPIO settings

[[Configuration of hardware in the debian image]]

====Installing UsbVideoClass(UVC) on A13-OLinuXino board====

To work with USB Video Cameras you have to enable the UVC support in the kernel. The link below explains how to do it.

[[UVC support]]

====Setup VLC player for video streaming on A13-OLinuXino board====

To setup video streaming you should first have installed UVC support so you can connect USB cameras to A13-OLinuXino.

[[VLC streaming]]

=== Creating a program to run on the A13-OlinuXino board ===

[[Programming for A13 in debian]] Step by step instructions to make your first hello world program run on the A13 board running debian.

=== Software links ===

[http://linux-sunxi.org/Sunxi-tools Tools to hack A13-OLinuXino]

[http://olimex.wordpress.com/2012/11/23/running-debian-with-xfce4-on-a13-olinuxino/ Installing Xfce4 graphical interface on Debian] How to install XFCE4 on A13-OLinuXino

=== A13-SDK Android 4.0.3 ICS ===

The official Allwinner repository contains all official files, including the files required to build Android ACS 4.0.3 NAND image for A13-OLinuXino-WIFI.

[https://github.com/allwinner-dev-team Allwinner's official GitHub]

=== A13-SDK Android 4.1 JB ===

This is version 1.5 of A13-SDK which builds Android 4.1 Jelly Beans image. It works slower than 4.0.3 and we personally do not see any advantage to use 4.1 vs 4.0.3

[http://emicrotec.at/public/ Andreas Auer kindly offered to host this 4GB image]

== Projects ==
Projects people from the olinuxino community are working on or have finished and how they did it.

'''LINUX:''' 
[[Build Bootable SD Card with Debian]] Run Debian and u-boot, Step by step instructions how to make SD card image. 
[[Prebuilt SD card images running debian]]

[http://olimex.wordpress.com/2014/03/06/bootling-linux-on-a13-for-less-than-1-second/ Booting Linux for less than 1 second] optimization made by Miroslav Bendik.

[http://olimex.wordpress.com/2012/10/23/a13-olinuxino-playing-with-gpios/ Change GPIOs using scripts in linux]

[https://www.olimex.com/forum/index.php?topic=436.msg4066#msg4066 A13 OLinuXino fast GPIO with /dev/mem now achieve up to 2 Mhz toggle]

[https://www.olimex.com/forum/index.php?topic=899.0 A13 kernel module for direct support of UEXT MOD-IO board, adding ADC, relays etc, cool project can be used as reference how to make your own kernel modules]

[https://docs.google.com/open?id=0B7WHuNCASY8cWnRrQ0tGVFMybFk Instructions how to run MOD-BT with A13-OLinuXino]

[https://github.com/asfluido/olinuxino/ Customer project of A13-OLinuXino communication via SPI with MOD-MRF89-868]

[http://olimex.wordpress.com/2013/04/18/a13-olinuxino-wifi-and-opencv-face-detection-project/ A13-Olinuxino-WIFI and opencv face detection]

[http://olimex.wordpress.com/2013/04/02/scratch-control-for-mod-io/ Controlling Relays, Switching ON/OFF of 220V appliances and home automation]

[http://olimex.wordpress.com/2013/03/28/make-door-security-logger-with-a13-olinuxino-wifi-opencv/ Door security logger, image capture]

[http://olimex.wordpress.com/2013/03/08/gps-logger-with-google-maps-viewer-made-with-a13-olinuxino-and-mod-gps/ GPS logger with google maps viewer, MOD-GPS module on UEXT]

[http://olimex.wordpress.com/2013/02/25/a13-olinuxino-web-server-with-mod-rgb-controlling-rgb-led-stripe-over-internet/ Web server with MOD-RGB controlling RGB LED strip]

'''ANDROID:''' 
[http://olimex.wordpress.com/2012/10/24/a13-olinuxino-project-control-relays-and-read-adcs-and-ios-with-android/ Interface MOD-IO board with I2C under Android ]

[http://olimex.wordpress.com/2013/03/13/mame4droid-is-running-on-a13-olinuxino/ Run old games on android mame4droid]

'''No OS''' 
[[Bare Metal programming A13]] Programming directly for the chip without an OS

'''FreedomBox:''' 
[https://wiki.debian.org/FreedomBox/UniLeipzigPractical FreedomBox/UniLeipzigPractical is the documentation of a freedom box related practical course at the AKSW Research Group at the University of Leipzig]

== List of Contributors ==

'''Henrik Nordstrom''' - a.k.a. hno, uboot for A13 development, A1X guru, Linux-Sunxi maintainer

'''Dimitar Gamishev''' - a.k.a. HEHOPMAJIEH, Linux kernel configuration for OLinuXino, Android images, LCD touchscreen

'''Alexandro Mery''' - a.k.a. mnemoc, Linux-Sunxi maintainer

'''Davide Fabbri''' - Linaro kernel and lubuntu image

'''Scott Anderson''' - A13 wiki maintainer

'''Jeffrey Wischkaemper''' - a.k.a. jwischka, A13-OLinuXino Debian image with X

'''Maxime Ripard''' - ARM Linux patches

'''Jason Plum''' - Arch Linux support

[[Main_Page]]

A13-OLinuXino

2024-11-29T08:28:23Z

LubOlimex: /* Android for NAND */

[[File:A13-OLinuXino-MAXI-WIFI-1.jpg|thumb| A13-OlinuXino-WIFI]]

[[File:A13-OLinuXino-MICRO.jpg|thumb| A13-OlinuXino-MICRO]]

The A13 processor from Allwinner runs at 1GHz with a Mali400 GPU. It was designed for integration into tablets. Olimex has made several development board designs based around this chip. This wiki page contains information about hardware and software to help make use of these development boards.

The A13 based boards currently available are 
*[https://www.olimex.com/Products/OLinuXino/A13/A13-OLinuXino-WIFI/ A13-OLinuXino-WIFI] - Recommended if your developing software for the A13 for the first time as its the only one with network connectivity.
*[https://www.olimex.com/Products/OLinuXino/A13/A13-OLinuXino/ A13-OLinuXino] - This is the same as the WIFI version but without WIFI module and NAND flash. Note: Android requires NAND flash to run, so this board can't run Android.
*[https://www.olimex.com/Products/OLinuXino/A13/A13-OLinuXino-MICRO/ A13-OLinuXino-MICRO] - Similar to the A13-OlinuXino but with less extras
*[https://www.olimex.com/Products/SOM/A13/A13-SOM-512/ A13-SOM-512] - System-on-Module A13 board recommended for users with experience in Allwinner development. Allows developing custom extensions with only the peripherals needed.
 
== Official Images from OLIMEX ==

=== Linux ===

The official Debian images are suitable only for microSD card. Information on booting Debian from the NAND might be found at the forum.

Download methods and locations might be found below!

'''Please note that you might need different Debian Linux images for different boards with different hardware - you would need to inspect the DDR3 RAM memory and use the image suitable for your board. We use either HYNIX H5TQ2G83CFR, or SAMSUNG K4B2G0846Q.'''

'''Newest official Debian release (recommended):'''

Direct download for Debian release 11.3 suitable for boards with SAMSUNG K4B2G0846Q DDR3 RAM memory: [https://ftp.olimex.com/Allwinner_Images/A13-OLinuXino/2.legacy_images_kernel_3.4.x/A13_debian_34_90_mainline_u-boot_release_11_3.7z A13 Debian Linux with kernel 3.4.90+, suitable for boards with SAMSUNG DDR3 RAM]

Direct download Debian release 10 suitable for boards with HYNIX H5TQ2G83CFR DDR3 RAM memory: [https://ftp.olimex.com/Allwinner_Images/A13-OLinuXino/2.legacy_images_kernel_3.4.x/A13_debian_34_90_WIFI_RALINK_GCC_GPIO_X_I2C_100KHz_UVC_TS_FTDI_3G_video_accell_release_10.7z Debian A13 Linux with kernel 3.4.90+, suitable for HYNIX DDR3 RAM]

'''Instructions and required files for preparing the Debian images: [https://github.com/OLIMEX/OLINUXINO/tree/master/SOFTWARE/A13/A13-build building Linux for A13-OLinuXino and A13-OLinuXino-WIFI]'''

The images include the following:
*Linux Kernel 3.4.90+
*LXDE desktop environment
*GCC 4.6
*dpkg
*git
*i2c-tools
*perl
*xorg
*Python 2.7
*vlc
*mplayer
*smplayer
*midori browser
*usb-modeswitch
*sshfs
*wvdial
*LCD and touchscreen support
*GPIO
*I2C
*SPI
*USB WIFI RTL8188CU, Ethernet AX88772B
*Audio
*PyA13 python module with GPIO,I2C,SPI support
*Default Login: '''root/olimex'''

'''Note:''' the A13-OLinuXino-SD card which we have on our webshop contain same image on 4GB Class10 fast micro sd-card, if you want to use this image please use Class10 fast card or the performance of Linux will slow down

The file A13_debian_34_75_WIFI_RALINK_GCC_GPIO_X_I2C_100KHz_UVC_TS_FTDI_video_release_9.7z is an archive of A13_debian_34_75_WIFI_RALINK_GCC_GPIO_X_I2C_100KHz_UVC_TS_FTDI_video_release_9.7z file.

So in order to write the image on SD card you have to unzip A13_debian_34_75_WIFI_RALINK_GCC_GPIO_X_I2C_100KHz_UVC_TS_FTDI_video_release_9.7z file:

For Windows use 7zip and then use Win32DiskImager.exe (http://sourceforge.net/projects/win32diskimager/) for image writing

For Linux use p7zip package. If you have no installed 7zip then type

#apt-get install p7zip

Copy A13_debian_34_75_WIFI_RALINK_GCC_GPIO_X_I2C_100KHz_UVC_TS_FTDI_video_release_9.7z file in your directory and unzip it with

#7za e A13_debian_34_75_WIFI_RALINK_GCC_GPIO_X_I2C_100KHz_UVC_TS_FTDI_video_release_9.7z

The output should be a new 4GB file named A13_debian_34_75_WIFI_RALINK_GCC_GPIO_X_I2C_100KHz_UVC_TS_FTDI_video_release_9.7z
Put 4GB SD card in your card reader and type

# ls /dev/sd

Then press two times <TAB> you will see a list of your sd devices like sda sdb sdc note that some of these devices may be your hard disk so make sure you know which one is your sd card before you proceed as you can damage your HDD if you choose the wrong sd-device. You can do this by unplugging your sd card reader and identify which "sd" devices remove from the list.
Once you know which device is your sdcard like sda use this text instead of the sdX name in the references below:

#dd if=A13_debian_34_75_WIFI_RALINK_GCC_GPIO_X_I2C_100KHz_UVC_TS_FTDI_video_release_9.7z of=/dev/sdX

The main tested onboard hardware modules are:

'''GPIO''' - they are located in /sys/class/gpio directory. Note that first you have to export GPIOs.
For example: to add PB03

root@A10:~# echo 1 > /sys/class/gpio/export

to make PB03 output

root@A10:~# echo out > /sys/class/gpio/gpio1_pb3/direction

to make PB03 high level(3.3V)

root@A10:~# echo 1 > /sys/class/gpio/gpio1_pb3/value

to make PB03 low level(0V)

root@A10:~# echo 0 > /sys/class/gpio/gpio1_pb3/value

Full list with supported GPIOs is:

gpio12_pg9 gpio1_pb3 gpio4_pe4 gpio7_pe7
gpio10_pe10 gpio13_pg10 gpio2_pb4 gpio5_pe5 gpio8_pe8
gpio11_pe11 gpio14_pg11 gpio3_pb10 gpio6_pe6 gpio9_pe9

note that:

gpio12_pg9(GPIO2/pin10) is connected to on board LED and it is multiplexed with UART3_TX and gpio13_pg10(GPIO2/pin8) is multiplexed with UART3_RX
Therfore if you want to use these ports like GPIO then UART3_TX and UART3_RX will not be available.

'''LCD''' - 4.3"(480x272), 7"(800x480), 10"(1024x600)

'''VGA''' - 800x600, 1024x768

'''Touch_screen''' - you need calibrate LCD touch screen usi it. Note that by default the X environment does not start like root user. In our case the X starts with user named olimex

Therefore if you want to use the touch screen in X environment then you have to run calibrate procedure like olimex user. For example type:

#su olimex

enter the olimex password:olimex

#sudo ts_calibrate

calibrate the touch screen and reboot the board

#sudo reboot

ASIX8877 USB-LAN - https://www.olimex.com/Products/OLinuXino/A13/USB-ETHERNET-AX88772B/

WEB camera A4TECH

MOD-WIFI-RTL8188 - https://www.olimex.com/Products/Modules/Ethernet/MOD-WIFI-RTL8188/ instructions on how to enable it might be found here: [[How_to_configure_MOD-RTL8188_on_official_OLinuXino_Debian_releases]]

USB_OTG - low/full/high USB host

USB_HOST_up - low/full/high USB host

USB_HOST_down - low/full/high USB host

mico_SD_card

I2C2(100KHz) - /dev/i2c-2

I2C1(100KHz) - /dev/i2c-1

UART3 - /dev/ttyS1

'''[https://drive.google.com/file/d/0B-bAEPML8fwlYnUwdnpkUllVNFU/edit?usp=sharing A13 Debian 4GB SD-card image armel (softfloat) with: MONO complete]'''
*Linux Kernel 3.4.67+
*XFCE4 desktop environment
*Mplayer CLI
*GCC 4.6
*iceweasel WEB browser
*LCD and touchscreen support
*GPIO
*I2C
*SPI
*USB WIFI RTL8188CU, Ethernet AX88772B
*Audio
*apache2
*dpkg
*git
*i2c-tools
*perl
*vlc
*xorg
*Scratch
*GCC
*Python 2.7.3
*PyA13 python module with GPIO,I2C,SPI support
*OpenCV
*mono-complete
*Default Login: '''root/olimex'''

 

=== Android ===

====Android for NAND====
 

There are different images depending on the screen output settings. Also there are different images depending on the WIFI module placed. Latest hardware revisions use MOD-WIFI-RTL8188ETV and an updated image.

'''
'''A13 Android NAND images with LCD 4.3" 480x272 and touchscreen (torrents):'''

[https://ftp.olimex.com/Allwinner_Images/A13-OLinuXino/4.%D0%B0ndroid_images/nand/A13_android_8G_NAND_LCD_480x272_EN_fifth_release.img A13-OLinuXino Android for NAND memory with video settings for 480x272 display output + MOD-WIFI-RTL8188ETV module]

*Android_version - 4.0.3
*Baseband version - 1.2
*Kernel version 3.0.8+
*MOD-WIFI-RTL8188ETV wifi module
*LCD 4.3" 480x272 pixels with backlight
*Touchscreen support

[[Media:A13_android_NAND_LCD_480x272_EN_first_release.torrent‎‎|A13-OLinuXino Android for NAND memory with video settings for 480x272 display output + MOD-WIFI-RTL8188 module]]

'''
*Android_version - 4.0.3
*Baseband version - 1.2
*Kernel version 3.0.8+
*MOD-WIFI-RTL8188 wifi module
*LCD 4.3" 480x272 pixels with backlight
*Touchscreen support

'''
'''A13 Android NAND images with LCD 7" 800x480 and touchscreen support (torrents):'''

[https://ftp.olimex.com/Allwinner_Images/A13-OLinuXino/4.%D0%B0ndroid_images/nand/A13_android_8G_NAND_LCD_800x480_EN_fifh_release.img A13-OLinuXino Android for NAND memory with video settings for LCD 7" 800x480 and touchscreen]
'''

*Android_version - 4.0.3
*Baseband version - 1.2
*Kernel version 3.0.8+
*MOD-WIFI-RTL8188-ETV wifi module
*LCD 7" 800x480 pixels with backlight
*touchscreen support

[[Media:A13_android_8G_NAND_LCD_800x480_EN_third_release.torrent|A13-OLinuXino Android for NAND memory with video settings for LCD 7" 800x480 and touchscreen]]
'''

*Android_version - 4.0.3
*Baseband version - 1.2
*Kernel version 3.0.8+
*MOD-WIFI-RTL8188 wifi module
*LCD 7" 800x480 pixels with backlight
*Touchscreen support

'''

'''A13 Android NAND images with LCD 10" 1024x600 and touchscreen support:'''

[https://ftp.olimex.com/Allwinner_Images/A13-OLinuXino/4.%D0%B0ndroid_images/nand/A13_android_8G_NAND_LCD_1024x600_EN_fifth_release.img A13-OLinuXino Android for NAND memory with video settings for LCD 10" 1024x600 and touchscreen]

'''

*Android_version - 4.0.3
*Baseband version - 1.2
*Kernel version 3.0.8+
*MOD-WIFI-RTL8188-ETV wifi module
*LCD 10" 1024x600 pixels with backlight
*Touchscreen support

'''A13 Android NAND image with VGA 800x600 support, torrents:'''

[https://ftp.olimex.com/Allwinner_Images/A13-OLinuXino/4.%D0%B0ndroid_images/nand/A13_android_8G_NAND_VGA_800x600_EN_fifth_release.img A13-OLinuXino Android for NAND memory with VGA 800x600 support]
'''
*Android_version - 4.0.3
*Baseband version - 1.2
*Kernel version 3.0.8+
*MOD-WIFI-RTL8188ETV wifi module
*VGA 800x600 pixels

[[Media:A13_android_8G_NAND_VGA_800x600_EN_third_release.torrent‎‎|A13-OLinuXino Android for NAND memory with VGA 800x600 support]]
'''
*Android_version - 4.0.3
*Baseband version - 1.2
*Kernel version 3.0.8+
*MOD-WIFI-RTL8188 wifi module
*VGA 800x600 pixels

----

====Android for microSD card====
 

'''Torrent of Android release 3 with LCD support for microSD card (recommended):

[[Media:A13_android_sd_800x480_USB_OTG_8G_third_release.torrent‎‎|A13-OLinuXino A13 Android for microSD card with video support for 800x480 LCD, release 3]]

*Android_version - 4.0.3
*Baseband version - 1.2
*Kernel version 3.0.8+
*Only LCD support - 800x480 pixels

'''Older (not recommended) releases:'''

Torrent of Android release 2 with LCD support for microSD card (not recommended, the USB OTG does not work properly due to fex error): [[Media:A13_android_sd_800x480_second_release.torrent‎|A13-OLinuXino A13 Android for microSD card with video support for 800x480 LCD, release 2]]

 

==HOWTOs==

===General===

'''How to write the Debain image to a microSD card?'''

To write a Linux image to an SD card under Windows we use Win32 Disk Imager):

*Download Win32 Disk Imager [http://sourceforge.net/projects/win32diskimager/ Win32 Disk Imager]
*Insert card
*Start program
*Select file
*Click "write"

To write a Linux image to an SD card under Linux:

For instance you have an image with the file name of "debian_2g.img". It would be downloaded to the SD card connected to a Linux machine using one of the following commands:

* # dd bs=4M oflag=sync if=debian_2g.img of=/dev/sdX
or
* # cp debian_2g.img /dev/sdX

where X is the uSD card.

'''How to change VGA and LCD resolutions under Debian?'''

The default SD card setup is made with settings for 800x600 VGA video output. If you want to change to some other LCD or VGA resolution then you have to start change_display.sh script file in /root directory.

Type:

./change_display* (press 'TAB' to auto-complete)
or
./change_display_A13.sh

and press "Enter".

Then choose the resolution and the interface(LCD or VGA). Note that the selection of a specific resolution is done by navigating with the arrow keys and pressing "space" button. Make sure the asterisk marks your selection properly.

The supported resolutions are:

'''For LCD:'''

*1. 4.3" (480x272)
*2. 7" (800x480)
*3. 10" (1024x600)
 
Important: initially the boards are calibrated for a specific display. If you re-write the image (no matter whether the SD card or the NAND memory) you might need to use a mouse to calibrate the display initially. It might be impossible to calibrate it via touching the display.

'''For VGA:'''
 
*1. 800x600
*2. 1024x768
 

===Linux related===
'''How to build latest official Debian release'''

The latest official instructions might be found here:
[https://github.com/OLIMEX/OLINUXINO/tree/master/SOFTWARE/A13/A13-build building the latest official Debian release, at Olimex GitHub]

There are a number of unofficial guides to building the Debian, among them:

[https://github.com/OLIMEX/OLINUXINO/blob/master/SOFTWARE/A13/olinuxino-debian.pdf How to build Debian for A13-OLinuXino-WIFI by Marcin Twardak]

[https://github.com/linux-sunxi/u-boot-sunxi/wiki Sunxi u-boot loader] The linux-sunxi git page contains a lot of sources for all Olimex Allwinner boards.

'''How to edit my MAC address?'''

However, it is very easy to change MAC under Debian.

All you have to do is:

1. turn off the network interface (it is off by default, can be turned off by “ifdown eth0”)
2. open /etc/network/interfaces with a text editor (for instance “nano /etc/network/interfaces”)
3. add the following line under eth0 definitions: “hwaddress ether 00:11:22:33:44:55”, where 00:11:22:33:44:55 is the desired MAC address.
4. save and turn on the network interface (“ifup eth0”)

You can think of own way implementing own MAC address (for instance storing a consecutive number in the small EEPROM and then loading it).

'''How to enable WIFI?'''

Note: in the previous Debian releases the Ethernet was auto-detected and initialized during boot BUT this was causing big delays in the start-up of the board if you didn't want to use Ethernet or if there wasn't Ethernet cable connected.

You can enable it by following these two steps:

1. To check under what name the LAN is associated write "ifconfig –a"

2. If, for example, it is under eth0 name, then write: "dhclient eth0"

This should enable the Ethernet and then SSH would also be available.

'''How to enable Ethernet?'''

Note: in the previous Debian releases the Ethernet was auto-detected and initialized during boot BUT this was causing big delays in the start-up of the board if you didn't want to use Ethernet or if there wasn't Ethernet cable connected.

You can enable it by following these two steps:

1. To check under what name the LAN is associated write "ifconfig –a"

2. If, for example, it is under eth0 name, then write: "dhclient eth0"

This should enable the Ethernet and then SSH would also be available.

===Android related===
'''How to compile new Android image?'''

Good guide shared by Akshay Mathur might be found here: [https://github.com/OLIMEX/OLINUXINO/tree/master/SOFTWARE/A13/Android-JellyBean pdf instructions available at GitHub]

'''How to make code to run on power up?'''

You would need an application that works in kiosk mode. There is a lot of information available online on how to write an application capable of autostart.

'''How to access GPIOs?'''

There is an application we wrote to demonstrate how this can be done under Android. Please check the following two links:

[http://www.youtube.com/watch?v=fBydZn8FylE YouTube video of relay control via MOD-IO under Android]

[https://github.com/OLIMEX/OLINUXINO/tree/master/SOFTWARE/A13/ANDROID-MOD-IO Source code of the above example]

'''How to add PWM support?'''

There is a separate article on the subject here: [[how to add pwm]]

===Python===

The Debian Linux Python package for A13-OLinuXino is called pyA13. It is installed in the default Debian image. More information and examples on how it can be used might be found here:

[https://pypi.python.org/pypi/pyA13 Link to pyA13 package at python.org]

===Scratch===

There are a number of SCRATCH resources we have published. The following might be of interested for you if you are interested in SCRATCH or OpenCV:

[http://www.youtube.com/watch?v=Pyidx-zOsm4 YouTube video of A13-OLinuXino running SCRATCH + OPENCV interractive project with web camera]

[http://www.youtube.com/watch?v=DzmvqlQodac YouTube video of A13-OLinuXino-WIFI + SCRATCH animation of GPIO-2 connector with buttons and LEDs]

[https://github.com/OLIMEX/OLINUXINO/tree/master/SOFTWARE/A13 source code and other scratch-related project available at Github]

===How to edit board configurations and definitions in the official Debian Linux? ===

Do you want a custom video resolution output? Do you need a different port definition? Do you need to change the hardware defitions of the board?

You would need to edit the board's script.bin/script.fex file. How to do it is described in a separate article: [[How_to_edit_board_configurations_and_definitions_in_the_official_Debian_Linux]].

===How to add STK1160 video capture driver support in Kernel 3.4===

[https://www.olimex.com/wiki/STK1160-howto-linux-sunxi-3_4 STK1160] driver backport by Dimitar Tomov

==Hardware==

[https://github.com/OLIMEX/OLINUXINO/tree/master/HARDWARE/A13-OLinuXino A13-OLinuXino schematic in PDF format and Eagle CAD files]

[https://github.com/OLIMEX/OLINUXINO/tree/master/HARDWARE/A13-PDFs A13 datasheet and user manual PDFs]

[http://linux-sunxi.org/A13_Register_guide A13 Registers Guide]

GPIOs

UEXT

LCD

RTC

[[Serial connection to A13]] description of how to connect a computer to the A13 board over serial cable.

===Power supply===

The A13-OLinuXino can be partially powered over Micro USB, but to power all peripherals, a 6+ watt DC power supply between 6 and 16 volts can be used. The connector is a positive-center 2.5mm barrel plug. There is also an on-board connector for a Li-PO battery.
'''Important note: A13-OLinuXino-MICRO works with +5V only! If you apply more than 5V you will damage the board.'''

==Software==

===Linux Commands===

[[Linux-Commands]] Brief Linux Command reference

[http://linux-sunxi.org/Main_Page A generic wiki for the Allwinner devices might be found here. It contains some great detailed info]
 

=== Bare Metal programming - no OS ===

It is possible to program and debug code written directly on the chip without an OS such as linux or android. 
The advantage is no kernel overhead and tighter control of the CPU operation.

[[Bare Metal programming A13]]

=== Using an operating system - Nand flash ===

The Wifi version of the A13 board comes preprogrammed with android, which is held in the Nand flash.

The image in the Nand flash can be updated using the tools found at the following links:

[https://docs.google.com/file/d/0B7WHuNCASY8cWlZ2djh4X0QtV0U/edit?usp=sharing LiveSuit for Windows]

[http://linux-sunxi.org/LiveSuit LiveSuit for loading images]

to the NAND flash; to activate A13 bootloader do as follows: run Livesuit, disconnect the power supply and USB cable, then press HOME button, apply power supply, attach USB cable and release the button, Livesuit will detect the bootloader and will ask which file to program to the NAND flash.

Prebuilt images that can be programmed into the Nand flash can be found here.

=== Using an operating system - SD card ===
The A13 board can boot from an SD card. Just plug it in an imaged uSD card and connect power.

Note: The SD card can easily be corrupted if power is removed while the system is booting or writing to system files.
To avoid this do not remove power while it is booting and shut the system down properly before disconnecting power.

==== Prebuilt images ====

Some prebuilt images have been created, follow the link below for details.

[[Prebuilt SD card images running debian]]

==== Build your own kernel and image onto SD card ====

Some developers want more control over the kernel and modules that are included. The link below shows directions to build your own kernel and image it onto an SD card.

[[Build Bootable SD Card with Debian]] Step by step instructions how to make SD card image with above Kernel and U-boot

====Setup and configure the installed debian image====

There are several settings that can be made for a particular hardware configuration in the script file.

The following link explains the script file as well as wifi or ethernet setup and GPIO settings

[[Configuration of hardware in the debian image]]

====Installing UsbVideoClass(UVC) on A13-OLinuXino board====

To work with USB Video Cameras you have to enable the UVC support in the kernel. The link below explains how to do it.

[[UVC support]]

====Setup VLC player for video streaming on A13-OLinuXino board====

To setup video streaming you should first have installed UVC support so you can connect USB cameras to A13-OLinuXino.

[[VLC streaming]]

=== Creating a program to run on the A13-OlinuXino board ===

[[Programming for A13 in debian]] Step by step instructions to make your first hello world program run on the A13 board running debian.

=== Software links ===

[http://linux-sunxi.org/Sunxi-tools Tools to hack A13-OLinuXino]

[http://olimex.wordpress.com/2012/11/23/running-debian-with-xfce4-on-a13-olinuxino/ Installing Xfce4 graphical interface on Debian] How to install XFCE4 on A13-OLinuXino

=== A13-SDK Android 4.0.3 ICS ===

The official Allwinner repository contains all official files, including the files required to build Android ACS 4.0.3 NAND image for A13-OLinuXino-WIFI.

[https://github.com/allwinner-dev-team Allwinner's official GitHub]

=== A13-SDK Android 4.1 JB ===

This is version 1.5 of A13-SDK which builds Android 4.1 Jelly Beans image. It works slower than 4.0.3 and we personally do not see any advantage to use 4.1 vs 4.0.3

[http://emicrotec.at/public/ Andreas Auer kindly offered to host this 4GB image]

== Projects ==
Projects people from the olinuxino community are working on or have finished and how they did it.

'''LINUX:''' 
[[Build Bootable SD Card with Debian]] Run Debian and u-boot, Step by step instructions how to make SD card image. 
[[Prebuilt SD card images running debian]]

[http://olimex.wordpress.com/2014/03/06/bootling-linux-on-a13-for-less-than-1-second/ Booting Linux for less than 1 second] optimization made by Miroslav Bendik.

[http://olimex.wordpress.com/2012/10/23/a13-olinuxino-playing-with-gpios/ Change GPIOs using scripts in linux]

[https://www.olimex.com/forum/index.php?topic=436.msg4066#msg4066 A13 OLinuXino fast GPIO with /dev/mem now achieve up to 2 Mhz toggle]

[https://www.olimex.com/forum/index.php?topic=899.0 A13 kernel module for direct support of UEXT MOD-IO board, adding ADC, relays etc, cool project can be used as reference how to make your own kernel modules]

[https://docs.google.com/open?id=0B7WHuNCASY8cWnRrQ0tGVFMybFk Instructions how to run MOD-BT with A13-OLinuXino]

[https://github.com/asfluido/olinuxino/ Customer project of A13-OLinuXino communication via SPI with MOD-MRF89-868]

[http://olimex.wordpress.com/2013/04/18/a13-olinuxino-wifi-and-opencv-face-detection-project/ A13-Olinuxino-WIFI and opencv face detection]

[http://olimex.wordpress.com/2013/04/02/scratch-control-for-mod-io/ Controlling Relays, Switching ON/OFF of 220V appliances and home automation]

[http://olimex.wordpress.com/2013/03/28/make-door-security-logger-with-a13-olinuxino-wifi-opencv/ Door security logger, image capture]

[http://olimex.wordpress.com/2013/03/08/gps-logger-with-google-maps-viewer-made-with-a13-olinuxino-and-mod-gps/ GPS logger with google maps viewer, MOD-GPS module on UEXT]

[http://olimex.wordpress.com/2013/02/25/a13-olinuxino-web-server-with-mod-rgb-controlling-rgb-led-stripe-over-internet/ Web server with MOD-RGB controlling RGB LED strip]

'''ANDROID:''' 
[http://olimex.wordpress.com/2012/10/24/a13-olinuxino-project-control-relays-and-read-adcs-and-ios-with-android/ Interface MOD-IO board with I2C under Android ]

[http://olimex.wordpress.com/2013/03/13/mame4droid-is-running-on-a13-olinuxino/ Run old games on android mame4droid]

'''No OS''' 
[[Bare Metal programming A13]] Programming directly for the chip without an OS

'''FreedomBox:''' 
[https://wiki.debian.org/FreedomBox/UniLeipzigPractical FreedomBox/UniLeipzigPractical is the documentation of a freedom box related practical course at the AKSW Research Group at the University of Leipzig]

== List of Contributors ==

'''Henrik Nordstrom''' - a.k.a. hno, uboot for A13 development, A1X guru, Linux-Sunxi maintainer

'''Dimitar Gamishev''' - a.k.a. HEHOPMAJIEH, Linux kernel configuration for OLinuXino, Android images, LCD touchscreen

'''Alexandro Mery''' - a.k.a. mnemoc, Linux-Sunxi maintainer

'''Davide Fabbri''' - Linaro kernel and lubuntu image

'''Scott Anderson''' - A13 wiki maintainer

'''Jeffrey Wischkaemper''' - a.k.a. jwischka, A13-OLinuXino Debian image with X

'''Maxime Ripard''' - ARM Linux patches

'''Jason Plum''' - Arch Linux support

[[Main_Page]]

A13-OLinuXino

2024-11-29T08:27:37Z

LubOlimex: /* Android for NAND */

[[File:A13-OLinuXino-MAXI-WIFI-1.jpg|thumb| A13-OlinuXino-WIFI]]

[[File:A13-OLinuXino-MICRO.jpg|thumb| A13-OlinuXino-MICRO]]

The A13 processor from Allwinner runs at 1GHz with a Mali400 GPU. It was designed for integration into tablets. Olimex has made several development board designs based around this chip. This wiki page contains information about hardware and software to help make use of these development boards.

The A13 based boards currently available are 
*[https://www.olimex.com/Products/OLinuXino/A13/A13-OLinuXino-WIFI/ A13-OLinuXino-WIFI] - Recommended if your developing software for the A13 for the first time as its the only one with network connectivity.
*[https://www.olimex.com/Products/OLinuXino/A13/A13-OLinuXino/ A13-OLinuXino] - This is the same as the WIFI version but without WIFI module and NAND flash. Note: Android requires NAND flash to run, so this board can't run Android.
*[https://www.olimex.com/Products/OLinuXino/A13/A13-OLinuXino-MICRO/ A13-OLinuXino-MICRO] - Similar to the A13-OlinuXino but with less extras
*[https://www.olimex.com/Products/SOM/A13/A13-SOM-512/ A13-SOM-512] - System-on-Module A13 board recommended for users with experience in Allwinner development. Allows developing custom extensions with only the peripherals needed.
 
== Official Images from OLIMEX ==

=== Linux ===

The official Debian images are suitable only for microSD card. Information on booting Debian from the NAND might be found at the forum.

Download methods and locations might be found below!

'''Please note that you might need different Debian Linux images for different boards with different hardware - you would need to inspect the DDR3 RAM memory and use the image suitable for your board. We use either HYNIX H5TQ2G83CFR, or SAMSUNG K4B2G0846Q.'''

'''Newest official Debian release (recommended):'''

Direct download for Debian release 11.3 suitable for boards with SAMSUNG K4B2G0846Q DDR3 RAM memory: [https://ftp.olimex.com/Allwinner_Images/A13-OLinuXino/2.legacy_images_kernel_3.4.x/A13_debian_34_90_mainline_u-boot_release_11_3.7z A13 Debian Linux with kernel 3.4.90+, suitable for boards with SAMSUNG DDR3 RAM]

Direct download Debian release 10 suitable for boards with HYNIX H5TQ2G83CFR DDR3 RAM memory: [https://ftp.olimex.com/Allwinner_Images/A13-OLinuXino/2.legacy_images_kernel_3.4.x/A13_debian_34_90_WIFI_RALINK_GCC_GPIO_X_I2C_100KHz_UVC_TS_FTDI_3G_video_accell_release_10.7z Debian A13 Linux with kernel 3.4.90+, suitable for HYNIX DDR3 RAM]

'''Instructions and required files for preparing the Debian images: [https://github.com/OLIMEX/OLINUXINO/tree/master/SOFTWARE/A13/A13-build building Linux for A13-OLinuXino and A13-OLinuXino-WIFI]'''

The images include the following:
*Linux Kernel 3.4.90+
*LXDE desktop environment
*GCC 4.6
*dpkg
*git
*i2c-tools
*perl
*xorg
*Python 2.7
*vlc
*mplayer
*smplayer
*midori browser
*usb-modeswitch
*sshfs
*wvdial
*LCD and touchscreen support
*GPIO
*I2C
*SPI
*USB WIFI RTL8188CU, Ethernet AX88772B
*Audio
*PyA13 python module with GPIO,I2C,SPI support
*Default Login: '''root/olimex'''

'''Note:''' the A13-OLinuXino-SD card which we have on our webshop contain same image on 4GB Class10 fast micro sd-card, if you want to use this image please use Class10 fast card or the performance of Linux will slow down

The file A13_debian_34_75_WIFI_RALINK_GCC_GPIO_X_I2C_100KHz_UVC_TS_FTDI_video_release_9.7z is an archive of A13_debian_34_75_WIFI_RALINK_GCC_GPIO_X_I2C_100KHz_UVC_TS_FTDI_video_release_9.7z file.

So in order to write the image on SD card you have to unzip A13_debian_34_75_WIFI_RALINK_GCC_GPIO_X_I2C_100KHz_UVC_TS_FTDI_video_release_9.7z file:

For Windows use 7zip and then use Win32DiskImager.exe (http://sourceforge.net/projects/win32diskimager/) for image writing

For Linux use p7zip package. If you have no installed 7zip then type

#apt-get install p7zip

Copy A13_debian_34_75_WIFI_RALINK_GCC_GPIO_X_I2C_100KHz_UVC_TS_FTDI_video_release_9.7z file in your directory and unzip it with

#7za e A13_debian_34_75_WIFI_RALINK_GCC_GPIO_X_I2C_100KHz_UVC_TS_FTDI_video_release_9.7z

The output should be a new 4GB file named A13_debian_34_75_WIFI_RALINK_GCC_GPIO_X_I2C_100KHz_UVC_TS_FTDI_video_release_9.7z
Put 4GB SD card in your card reader and type

# ls /dev/sd

Then press two times <TAB> you will see a list of your sd devices like sda sdb sdc note that some of these devices may be your hard disk so make sure you know which one is your sd card before you proceed as you can damage your HDD if you choose the wrong sd-device. You can do this by unplugging your sd card reader and identify which "sd" devices remove from the list.
Once you know which device is your sdcard like sda use this text instead of the sdX name in the references below:

#dd if=A13_debian_34_75_WIFI_RALINK_GCC_GPIO_X_I2C_100KHz_UVC_TS_FTDI_video_release_9.7z of=/dev/sdX

The main tested onboard hardware modules are:

'''GPIO''' - they are located in /sys/class/gpio directory. Note that first you have to export GPIOs.
For example: to add PB03

root@A10:~# echo 1 > /sys/class/gpio/export

to make PB03 output

root@A10:~# echo out > /sys/class/gpio/gpio1_pb3/direction

to make PB03 high level(3.3V)

root@A10:~# echo 1 > /sys/class/gpio/gpio1_pb3/value

to make PB03 low level(0V)

root@A10:~# echo 0 > /sys/class/gpio/gpio1_pb3/value

Full list with supported GPIOs is:

gpio12_pg9 gpio1_pb3 gpio4_pe4 gpio7_pe7
gpio10_pe10 gpio13_pg10 gpio2_pb4 gpio5_pe5 gpio8_pe8
gpio11_pe11 gpio14_pg11 gpio3_pb10 gpio6_pe6 gpio9_pe9

note that:

gpio12_pg9(GPIO2/pin10) is connected to on board LED and it is multiplexed with UART3_TX and gpio13_pg10(GPIO2/pin8) is multiplexed with UART3_RX
Therfore if you want to use these ports like GPIO then UART3_TX and UART3_RX will not be available.

'''LCD''' - 4.3"(480x272), 7"(800x480), 10"(1024x600)

'''VGA''' - 800x600, 1024x768

'''Touch_screen''' - you need calibrate LCD touch screen usi it. Note that by default the X environment does not start like root user. In our case the X starts with user named olimex

Therefore if you want to use the touch screen in X environment then you have to run calibrate procedure like olimex user. For example type:

#su olimex

enter the olimex password:olimex

#sudo ts_calibrate

calibrate the touch screen and reboot the board

#sudo reboot

ASIX8877 USB-LAN - https://www.olimex.com/Products/OLinuXino/A13/USB-ETHERNET-AX88772B/

WEB camera A4TECH

MOD-WIFI-RTL8188 - https://www.olimex.com/Products/Modules/Ethernet/MOD-WIFI-RTL8188/ instructions on how to enable it might be found here: [[How_to_configure_MOD-RTL8188_on_official_OLinuXino_Debian_releases]]

USB_OTG - low/full/high USB host

USB_HOST_up - low/full/high USB host

USB_HOST_down - low/full/high USB host

mico_SD_card

I2C2(100KHz) - /dev/i2c-2

I2C1(100KHz) - /dev/i2c-1

UART3 - /dev/ttyS1

'''[https://drive.google.com/file/d/0B-bAEPML8fwlYnUwdnpkUllVNFU/edit?usp=sharing A13 Debian 4GB SD-card image armel (softfloat) with: MONO complete]'''
*Linux Kernel 3.4.67+
*XFCE4 desktop environment
*Mplayer CLI
*GCC 4.6
*iceweasel WEB browser
*LCD and touchscreen support
*GPIO
*I2C
*SPI
*USB WIFI RTL8188CU, Ethernet AX88772B
*Audio
*apache2
*dpkg
*git
*i2c-tools
*perl
*vlc
*xorg
*Scratch
*GCC
*Python 2.7.3
*PyA13 python module with GPIO,I2C,SPI support
*OpenCV
*mono-complete
*Default Login: '''root/olimex'''

 

=== Android ===

====Android for NAND====
 

There are different images depending on the screen output settings. Also there are different images depending on the WIFI module placed. Latest hardware revisions use MOD-WIFI-RTL8188ETV and an updated image.

'''
'''A13 Android NAND images with LCD 4.3" 480x272 and touchscreen (torrents):'''

[https://ftp.olimex.com/Allwinner_Images/A13-OLinuXino/4.%D0%B0ndroid_images/nand/A13_android_8G_NAND_LCD_480x272_EN_fifth_release.img A13-OLinuXino Android for NAND memory with video settings for 480x272 display output + MOD-WIFI-RTL8188ETV module]

*Android_version - 4.0.3
*Baseband version - 1.2
*Kernel version 3.0.8+
*MOD-WIFI-RTL8188ETV wifi module
*LCD 4.3" 480x272 pixels with backlight
*Touchscreen support

[[Media:A13_android_NAND_LCD_480x272_EN_first_release.torrent‎‎|A13-OLinuXino Android for NAND memory with video settings for 480x272 display output + MOD-WIFI-RTL8188 module]]

'''
*Android_version - 4.0.3
*Baseband version - 1.2
*Kernel version 3.0.8+
*MOD-WIFI-RTL8188 wifi module
*LCD 4.3" 480x272 pixels with backlight
*Touchscreen support

'''
'''A13 Android NAND images with LCD 7" 800x480 and touchscreen support (torrents):'''

[ftp://staging.olimex.com/Allwinner_Images/A13-OLinuXino/4.%D0%B0ndroid_images/nand/A13_android_8G_NAND_LCD_800x480_EN_fifh_release.img A13-OLinuXino Android for NAND memory with video settings for LCD 7" 800x480 and touchscreen]
'''

*Android_version - 4.0.3
*Baseband version - 1.2
*Kernel version 3.0.8+
*MOD-WIFI-RTL8188-ETV wifi module
*LCD 7" 800x480 pixels with backlight
*touchscreen support

[[Media:A13_android_8G_NAND_LCD_800x480_EN_third_release.torrent|A13-OLinuXino Android for NAND memory with video settings for LCD 7" 800x480 and touchscreen]]
'''

*Android_version - 4.0.3
*Baseband version - 1.2
*Kernel version 3.0.8+
*MOD-WIFI-RTL8188 wifi module
*LCD 7" 800x480 pixels with backlight
*Touchscreen support

'''

'''A13 Android NAND images with LCD 10" 1024x600 and touchscreen support:'''

[ftp://staging.olimex.com/Allwinner_Images/A13-OLinuXino/4.%D0%B0ndroid_images/nand/A13_android_8G_NAND_LCD_1024x600_EN_fifth_release.img A13-OLinuXino Android for NAND memory with video settings for LCD 10" 1024x600 and touchscreen]

'''

*Android_version - 4.0.3
*Baseband version - 1.2
*Kernel version 3.0.8+
*MOD-WIFI-RTL8188-ETV wifi module
*LCD 10" 1024x600 pixels with backlight
*Touchscreen support

'''A13 Android NAND image with VGA 800x600 support, torrents:'''

[ftp://staging.olimex.com/Allwinner_Images/A13-OLinuXino/4.%D0%B0ndroid_images/nand/A13_android_8G_NAND_VGA_800x600_EN_fifth_release.img A13-OLinuXino Android for NAND memory with VGA 800x600 support]
'''
*Android_version - 4.0.3
*Baseband version - 1.2
*Kernel version 3.0.8+
*MOD-WIFI-RTL8188ETV wifi module
*VGA 800x600 pixels

[[Media:A13_android_8G_NAND_VGA_800x600_EN_third_release.torrent‎‎|A13-OLinuXino Android for NAND memory with VGA 800x600 support]]
'''
*Android_version - 4.0.3
*Baseband version - 1.2
*Kernel version 3.0.8+
*MOD-WIFI-RTL8188 wifi module
*VGA 800x600 pixels

----

====Android for microSD card====
 

'''Torrent of Android release 3 with LCD support for microSD card (recommended):

[[Media:A13_android_sd_800x480_USB_OTG_8G_third_release.torrent‎‎|A13-OLinuXino A13 Android for microSD card with video support for 800x480 LCD, release 3]]

*Android_version - 4.0.3
*Baseband version - 1.2
*Kernel version 3.0.8+
*Only LCD support - 800x480 pixels

'''Older (not recommended) releases:'''

Torrent of Android release 2 with LCD support for microSD card (not recommended, the USB OTG does not work properly due to fex error): [[Media:A13_android_sd_800x480_second_release.torrent‎|A13-OLinuXino A13 Android for microSD card with video support for 800x480 LCD, release 2]]

 

==HOWTOs==

===General===

'''How to write the Debain image to a microSD card?'''

To write a Linux image to an SD card under Windows we use Win32 Disk Imager):

*Download Win32 Disk Imager [http://sourceforge.net/projects/win32diskimager/ Win32 Disk Imager]
*Insert card
*Start program
*Select file
*Click "write"

To write a Linux image to an SD card under Linux:

For instance you have an image with the file name of "debian_2g.img". It would be downloaded to the SD card connected to a Linux machine using one of the following commands:

* # dd bs=4M oflag=sync if=debian_2g.img of=/dev/sdX
or
* # cp debian_2g.img /dev/sdX

where X is the uSD card.

'''How to change VGA and LCD resolutions under Debian?'''

The default SD card setup is made with settings for 800x600 VGA video output. If you want to change to some other LCD or VGA resolution then you have to start change_display.sh script file in /root directory.

Type:

./change_display* (press 'TAB' to auto-complete)
or
./change_display_A13.sh

and press "Enter".

Then choose the resolution and the interface(LCD or VGA). Note that the selection of a specific resolution is done by navigating with the arrow keys and pressing "space" button. Make sure the asterisk marks your selection properly.

The supported resolutions are:

'''For LCD:'''

*1. 4.3" (480x272)
*2. 7" (800x480)
*3. 10" (1024x600)
 
Important: initially the boards are calibrated for a specific display. If you re-write the image (no matter whether the SD card or the NAND memory) you might need to use a mouse to calibrate the display initially. It might be impossible to calibrate it via touching the display.

'''For VGA:'''
 
*1. 800x600
*2. 1024x768
 

===Linux related===
'''How to build latest official Debian release'''

The latest official instructions might be found here:
[https://github.com/OLIMEX/OLINUXINO/tree/master/SOFTWARE/A13/A13-build building the latest official Debian release, at Olimex GitHub]

There are a number of unofficial guides to building the Debian, among them:

[https://github.com/OLIMEX/OLINUXINO/blob/master/SOFTWARE/A13/olinuxino-debian.pdf How to build Debian for A13-OLinuXino-WIFI by Marcin Twardak]

[https://github.com/linux-sunxi/u-boot-sunxi/wiki Sunxi u-boot loader] The linux-sunxi git page contains a lot of sources for all Olimex Allwinner boards.

'''How to edit my MAC address?'''

However, it is very easy to change MAC under Debian.

All you have to do is:

1. turn off the network interface (it is off by default, can be turned off by “ifdown eth0”)
2. open /etc/network/interfaces with a text editor (for instance “nano /etc/network/interfaces”)
3. add the following line under eth0 definitions: “hwaddress ether 00:11:22:33:44:55”, where 00:11:22:33:44:55 is the desired MAC address.
4. save and turn on the network interface (“ifup eth0”)

You can think of own way implementing own MAC address (for instance storing a consecutive number in the small EEPROM and then loading it).

'''How to enable WIFI?'''

Note: in the previous Debian releases the Ethernet was auto-detected and initialized during boot BUT this was causing big delays in the start-up of the board if you didn't want to use Ethernet or if there wasn't Ethernet cable connected.

You can enable it by following these two steps:

1. To check under what name the LAN is associated write "ifconfig –a"

2. If, for example, it is under eth0 name, then write: "dhclient eth0"

This should enable the Ethernet and then SSH would also be available.

'''How to enable Ethernet?'''

Note: in the previous Debian releases the Ethernet was auto-detected and initialized during boot BUT this was causing big delays in the start-up of the board if you didn't want to use Ethernet or if there wasn't Ethernet cable connected.

You can enable it by following these two steps:

1. To check under what name the LAN is associated write "ifconfig –a"

2. If, for example, it is under eth0 name, then write: "dhclient eth0"

This should enable the Ethernet and then SSH would also be available.

===Android related===
'''How to compile new Android image?'''

Good guide shared by Akshay Mathur might be found here: [https://github.com/OLIMEX/OLINUXINO/tree/master/SOFTWARE/A13/Android-JellyBean pdf instructions available at GitHub]

'''How to make code to run on power up?'''

You would need an application that works in kiosk mode. There is a lot of information available online on how to write an application capable of autostart.

'''How to access GPIOs?'''

There is an application we wrote to demonstrate how this can be done under Android. Please check the following two links:

[http://www.youtube.com/watch?v=fBydZn8FylE YouTube video of relay control via MOD-IO under Android]

[https://github.com/OLIMEX/OLINUXINO/tree/master/SOFTWARE/A13/ANDROID-MOD-IO Source code of the above example]

'''How to add PWM support?'''

There is a separate article on the subject here: [[how to add pwm]]

===Python===

The Debian Linux Python package for A13-OLinuXino is called pyA13. It is installed in the default Debian image. More information and examples on how it can be used might be found here:

[https://pypi.python.org/pypi/pyA13 Link to pyA13 package at python.org]

===Scratch===

There are a number of SCRATCH resources we have published. The following might be of interested for you if you are interested in SCRATCH or OpenCV:

[http://www.youtube.com/watch?v=Pyidx-zOsm4 YouTube video of A13-OLinuXino running SCRATCH + OPENCV interractive project with web camera]

[http://www.youtube.com/watch?v=DzmvqlQodac YouTube video of A13-OLinuXino-WIFI + SCRATCH animation of GPIO-2 connector with buttons and LEDs]

[https://github.com/OLIMEX/OLINUXINO/tree/master/SOFTWARE/A13 source code and other scratch-related project available at Github]

===How to edit board configurations and definitions in the official Debian Linux? ===

Do you want a custom video resolution output? Do you need a different port definition? Do you need to change the hardware defitions of the board?

You would need to edit the board's script.bin/script.fex file. How to do it is described in a separate article: [[How_to_edit_board_configurations_and_definitions_in_the_official_Debian_Linux]].

===How to add STK1160 video capture driver support in Kernel 3.4===

[https://www.olimex.com/wiki/STK1160-howto-linux-sunxi-3_4 STK1160] driver backport by Dimitar Tomov

==Hardware==

[https://github.com/OLIMEX/OLINUXINO/tree/master/HARDWARE/A13-OLinuXino A13-OLinuXino schematic in PDF format and Eagle CAD files]

[https://github.com/OLIMEX/OLINUXINO/tree/master/HARDWARE/A13-PDFs A13 datasheet and user manual PDFs]

[http://linux-sunxi.org/A13_Register_guide A13 Registers Guide]

GPIOs

UEXT

LCD

RTC

[[Serial connection to A13]] description of how to connect a computer to the A13 board over serial cable.

===Power supply===

The A13-OLinuXino can be partially powered over Micro USB, but to power all peripherals, a 6+ watt DC power supply between 6 and 16 volts can be used. The connector is a positive-center 2.5mm barrel plug. There is also an on-board connector for a Li-PO battery.
'''Important note: A13-OLinuXino-MICRO works with +5V only! If you apply more than 5V you will damage the board.'''

==Software==

===Linux Commands===

[[Linux-Commands]] Brief Linux Command reference

[http://linux-sunxi.org/Main_Page A generic wiki for the Allwinner devices might be found here. It contains some great detailed info]
 

=== Bare Metal programming - no OS ===

It is possible to program and debug code written directly on the chip without an OS such as linux or android. 
The advantage is no kernel overhead and tighter control of the CPU operation.

[[Bare Metal programming A13]]

=== Using an operating system - Nand flash ===

The Wifi version of the A13 board comes preprogrammed with android, which is held in the Nand flash.

The image in the Nand flash can be updated using the tools found at the following links:

[https://docs.google.com/file/d/0B7WHuNCASY8cWlZ2djh4X0QtV0U/edit?usp=sharing LiveSuit for Windows]

[http://linux-sunxi.org/LiveSuit LiveSuit for loading images]

to the NAND flash; to activate A13 bootloader do as follows: run Livesuit, disconnect the power supply and USB cable, then press HOME button, apply power supply, attach USB cable and release the button, Livesuit will detect the bootloader and will ask which file to program to the NAND flash.

Prebuilt images that can be programmed into the Nand flash can be found here.

=== Using an operating system - SD card ===
The A13 board can boot from an SD card. Just plug it in an imaged uSD card and connect power.

Note: The SD card can easily be corrupted if power is removed while the system is booting or writing to system files.
To avoid this do not remove power while it is booting and shut the system down properly before disconnecting power.

==== Prebuilt images ====

Some prebuilt images have been created, follow the link below for details.

[[Prebuilt SD card images running debian]]

==== Build your own kernel and image onto SD card ====

Some developers want more control over the kernel and modules that are included. The link below shows directions to build your own kernel and image it onto an SD card.

[[Build Bootable SD Card with Debian]] Step by step instructions how to make SD card image with above Kernel and U-boot

====Setup and configure the installed debian image====

There are several settings that can be made for a particular hardware configuration in the script file.

The following link explains the script file as well as wifi or ethernet setup and GPIO settings

[[Configuration of hardware in the debian image]]

====Installing UsbVideoClass(UVC) on A13-OLinuXino board====

To work with USB Video Cameras you have to enable the UVC support in the kernel. The link below explains how to do it.

[[UVC support]]

====Setup VLC player for video streaming on A13-OLinuXino board====

To setup video streaming you should first have installed UVC support so you can connect USB cameras to A13-OLinuXino.

[[VLC streaming]]

=== Creating a program to run on the A13-OlinuXino board ===

[[Programming for A13 in debian]] Step by step instructions to make your first hello world program run on the A13 board running debian.

=== Software links ===

[http://linux-sunxi.org/Sunxi-tools Tools to hack A13-OLinuXino]

[http://olimex.wordpress.com/2012/11/23/running-debian-with-xfce4-on-a13-olinuxino/ Installing Xfce4 graphical interface on Debian] How to install XFCE4 on A13-OLinuXino

=== A13-SDK Android 4.0.3 ICS ===

The official Allwinner repository contains all official files, including the files required to build Android ACS 4.0.3 NAND image for A13-OLinuXino-WIFI.

[https://github.com/allwinner-dev-team Allwinner's official GitHub]

=== A13-SDK Android 4.1 JB ===

This is version 1.5 of A13-SDK which builds Android 4.1 Jelly Beans image. It works slower than 4.0.3 and we personally do not see any advantage to use 4.1 vs 4.0.3

[http://emicrotec.at/public/ Andreas Auer kindly offered to host this 4GB image]

== Projects ==
Projects people from the olinuxino community are working on or have finished and how they did it.

'''LINUX:''' 
[[Build Bootable SD Card with Debian]] Run Debian and u-boot, Step by step instructions how to make SD card image. 
[[Prebuilt SD card images running debian]]

[http://olimex.wordpress.com/2014/03/06/bootling-linux-on-a13-for-less-than-1-second/ Booting Linux for less than 1 second] optimization made by Miroslav Bendik.

[http://olimex.wordpress.com/2012/10/23/a13-olinuxino-playing-with-gpios/ Change GPIOs using scripts in linux]

[https://www.olimex.com/forum/index.php?topic=436.msg4066#msg4066 A13 OLinuXino fast GPIO with /dev/mem now achieve up to 2 Mhz toggle]

[https://www.olimex.com/forum/index.php?topic=899.0 A13 kernel module for direct support of UEXT MOD-IO board, adding ADC, relays etc, cool project can be used as reference how to make your own kernel modules]

[https://docs.google.com/open?id=0B7WHuNCASY8cWnRrQ0tGVFMybFk Instructions how to run MOD-BT with A13-OLinuXino]

[https://github.com/asfluido/olinuxino/ Customer project of A13-OLinuXino communication via SPI with MOD-MRF89-868]

[http://olimex.wordpress.com/2013/04/18/a13-olinuxino-wifi-and-opencv-face-detection-project/ A13-Olinuxino-WIFI and opencv face detection]

[http://olimex.wordpress.com/2013/04/02/scratch-control-for-mod-io/ Controlling Relays, Switching ON/OFF of 220V appliances and home automation]

[http://olimex.wordpress.com/2013/03/28/make-door-security-logger-with-a13-olinuxino-wifi-opencv/ Door security logger, image capture]

[http://olimex.wordpress.com/2013/03/08/gps-logger-with-google-maps-viewer-made-with-a13-olinuxino-and-mod-gps/ GPS logger with google maps viewer, MOD-GPS module on UEXT]

[http://olimex.wordpress.com/2013/02/25/a13-olinuxino-web-server-with-mod-rgb-controlling-rgb-led-stripe-over-internet/ Web server with MOD-RGB controlling RGB LED strip]

'''ANDROID:''' 
[http://olimex.wordpress.com/2012/10/24/a13-olinuxino-project-control-relays-and-read-adcs-and-ios-with-android/ Interface MOD-IO board with I2C under Android ]

[http://olimex.wordpress.com/2013/03/13/mame4droid-is-running-on-a13-olinuxino/ Run old games on android mame4droid]

'''No OS''' 
[[Bare Metal programming A13]] Programming directly for the chip without an OS

'''FreedomBox:''' 
[https://wiki.debian.org/FreedomBox/UniLeipzigPractical FreedomBox/UniLeipzigPractical is the documentation of a freedom box related practical course at the AKSW Research Group at the University of Leipzig]

== List of Contributors ==

'''Henrik Nordstrom''' - a.k.a. hno, uboot for A13 development, A1X guru, Linux-Sunxi maintainer

'''Dimitar Gamishev''' - a.k.a. HEHOPMAJIEH, Linux kernel configuration for OLinuXino, Android images, LCD touchscreen

'''Alexandro Mery''' - a.k.a. mnemoc, Linux-Sunxi maintainer

'''Davide Fabbri''' - Linaro kernel and lubuntu image

'''Scott Anderson''' - A13 wiki maintainer

'''Jeffrey Wischkaemper''' - a.k.a. jwischka, A13-OLinuXino Debian image with X

'''Maxime Ripard''' - ARM Linux patches

'''Jason Plum''' - Arch Linux support

[[Main_Page]]

A20-OLinuXino-LIME2

2024-09-30T07:59:29Z

LubOlimex: /* Official Images from OLIMEX */

[[File:A20-OLinuXino-LIME2.jpg|600px]]

A20-OLinuXino-LIME2 looks similar to both [[A20-OLinuXino-LIME]] and [[A10-OLinuXino-LIME]]. The major differences between A20-OLinuXino-LIME2 and A20-OLinuXino-LIME are:

*LIME2 has gigabit Ethernet (GbE), compared to the standard 100Mb Ethernet of the LIME
*LIME2 design provides double the RAM memory, compared to the LIME design (1024 vs 512)
*Much better routing of DDR3 memory.
*Increased the number of layers from 6 in LIME to 8 in LIME2
*Corrected pinout of the LCD and GPIO connectors (shields designed for the LIME layout are not compatible with the LIME2 layout)

The A10 and the A20 processors are pin-to-pin compatible. Because of the processor, software-wise the board is closer to [[A20-OLinuXino-LIME]] than to the [[A10-OLinuXino-LIME]]. This resemblance to other designs definitely might speed the development on the board - a lot of software written for A20-OLinuXino-LIME might work out-of-the-box with A20-OLinuXino-LIME2. Additionally, pinout tables, GPIO maps, etc released for A20-OLinuXino-LIME would apply to A20-OLinuXino-LIME2 (except for the 0.05" step connectors - LCD display and all the GPIOs connectors, which have a different layout compared to both A20-OLinuXino-LIME and A10-OLinuXino-LIME).

A20-OLinuXino-LIME2 features:
*A20 Cortex-A7 dual-core ARM Cortex-A7 CPU and dual-core Mali 400 GPU
*'''1GB DDR3 RAM memory'''
*'''1 gigabit native Ethernet'''
*optional 4GB NAND FLASH memory
*SATA connector with 5V SATA power jack
*HDMI FullHD 1080p
*2x USB Low-Full-High-Speed hosts with power control and current limiter
*USB-OTG with power control and current limiter
*LiPo Battery connector with battery-charging capabilities
*LCD connector compatible with with 4.3", 7.0", 10.1" LCD modules from Olimex
*160 GPIOs on three GPIO connectors
*MicroSD card connector
*DEBUG-UART connector for console debug with USB-SERIAL-CABLE-F
*status LED
*Battery charge status LED
*Power LED
*2KB EEPROM for MAC address storage and more
*2 BUTTONS with ANDROID functionality + RESET button
*2 mount holes
*5V input power supply, noise immune design
*PCB dimensions: 84 x 60 mm

== Official Images from OLIMEX ==

'''The recommended image for most of Olimex-made Linux boards is Olimage Linux, you can find information about it in the document here:'''

https://github.com/OLIMEX/OLINUXINO/blob/master/DOCUMENTS/OLIMAGE/Olimage-guide.pdf

'''Notice this wiki article refers to outdated images and practices, if using Olimage Linux, use the information only as a reference (do not take it literally)!'''

In this chapter you would find links to FTP locations with sunxi Linux images Debian images and Android images. The images in this chapter were compiled by Olimex. They are recommended for beginners and first time users since they include full hardware support. If you are experienced Linux professional you might find useful our build instructions also published here.

The downloaded file xxxx.7z is an archive of xxx.img file. In order to write the image on SD card you have to extract the xxx.7z file.

*For Windows: use 7zip and then use Win32DiskImager.exe (http://sourceforge.net/projects/win32diskimager/) to write the image

*For Linux: use p7zip package. If you don't have 7zip installed first install it 

#apt-get install p7zip
Copy a20_Lime2_debian_second_release.7z file in your directory and unzip the archive with
#7za e a20_Lime2_debian_second_release.7z
where a20_Lime2_debian_second_release.7z
The output should be a new 4GB file with extension img
Put 4GB SD card in your card reader and type
# ls /dev/sd
Then press two times <TAB> you will see a list of your sd devices like sda sdb sdc note that some of these devices may be your hard disk so make sure you know which one is your sd card before you proceed as you can damage your HDD if you choose the wrong sd-device. You can do this by unplugging your sd card reader and identify which "sd" devices remove from the list.
Once you know which device is your sdcard like sda use this text instead of the sdX name in the references below:
#dd if=a20_Lime2_debian_second_release.img of=/dev/sdX

The Debian Linux image is 4GB and the file system can be extended to suit a bigger card. Use the following three commands to execute a script that would use all the free space of your card:

sudo su
./resize_sd.sh /dev/mmcblk0 2
reboot

=== Linux images ===

These official Debian images should be downloaded to a microSD card. Older sunxi images can be found as direct downloads at our FTP. You can install the Debian to the NAND or the eMMC of your board (if it comes with one). Information on booting Debian from the NAND might be found in these wiki articles: [[how to install Debian to NAND]]; [[how to install Debian to eMMC]]. Download locations for the official images might be found below:

'''ALWAYS FIRST TEST WITH LATEST OFFICIAL IMAGE, NEWER HARDWARE REVISIONS OF THE BOARD MIGHT NOT WORK WITH OLDER IMAGES!!!'''

----

'''Latest stable official images - Debian 8 (Jessie)''' '''Both images are suitable for the standard version A20-OLinuXino-LIME2. However A20-OLinuXino-LIME2-n4GB and A20-OLinuXino-LIME2-n8GB have different image compared to A20-OLinuXino-LIME2-e4GB''':'''

FTP location for official Debian Jessie release #13 for A20-OLinuXino-LIME2, A20-OLinuXino-LIME2-n4GB, and A20-OLinuXino-LIME2-n8GB (not suitable for boards with eMMC flash): [https://ftp.olimex.com/Allwinner_Images/A20-OLinuXino-LIME2/Debian/sd/a20-lime2_mainline_uboot_sunxi_kernel_3.4.103_jessie_NAND_rel_13.img.7z A20-OLinuXino-LIME2 Debian Jessie with kernel 3.4.103+ release 13]

FTP location for official Debian Jessie release #16 for A20-OLinuXino-LIME2, A20-OLinuXino-LIME2-e4GB (not suitable for boards with NAND flash): [https://ftp.olimex.com/Allwinner_Images/A20-OLinuXino-LIME2/Debian/sd/a20-lime2_mainline_uboot_sunxi_kernel_3.4.103_jessie_eMMC_rel_16.zip A20 lime2 mainline uboot sunxi kernel 3.4.103 jessie eMMC rel 16]

Image description and typical interfacing: [https://github.com/OLIMEX/OLINUXINO/blob/master/SOFTWARE/A20/A20-build-3.4.103-release-7/USAGE-AND-COMMON-PRACTICEs-A20-Olimex_kernel_3.4.103%2B_Jessie_rel_3.txt description and basic usage of different peripherals at at the GitHub page]

Image build instructions and required files for latest Debian Jessie release might be found here: [https://github.com/OLIMEX/OLINUXINO/blob/master/SOFTWARE/A20/A20-build-3.4.103-release-8/BUILD_DESCRIPTION_A20_Olimex_kernel_3.4.103%2B_Jessie_rel_8.txt build instructions and required files at the GitHub page]

You can find some older releases and older build instructions (older image revisions might be used as a reference, for testing purposes, or if you own old hardware revision of the board) at the following article: [[A20-OLinuXino-LIME2-older-releases|older releases and older build instructions]]

----

Note: the A20-LIME2-DEBIAN-SD card which we have in our web store contains the image suitable for board with no flash or board with NAND memory on a 8GB Class10 fast microSD card. The A20-LIME2-eMMC-DEBIAN-SD contains the image suitable for boards with extra eMMC memory. If you want to use our images, please, use card with speed Class10 or higher. Else the Linux performance would be very slow.

Note: in the previous Debian releases the Ethernet was auto-detected and initialized during boot BUT this was causing big delays in the start-up of the board if you didn't want to use Ethernet or if there wasn't Ethernet cable connected.

You can enable it by following these two steps:

1. To check under what name the LAN is associated write "ifconfig –a"

2. If, for example, it is under eth0 name, then write: "dhclient eth0"

This should enable the Ethernet and then SSH would also be available.

=== Android images ===

Links to FTP location of official Android releases are below. Please read description of the image carefully.

'''Newest official release (recommended):'''

For the NAND flash memory:

FTP location of Android 4.2.2 release 1 for NAND memory (with HDMI and 7 inch 800x480 support - LCD-OLinuXino-7TS): [https://ftp.olimex.com/Allwinner_Images/A20-OLinuXino-LIME2/Android/nand/A20_Lime2_android_4_22_NAND_LCD7_HDMI_release1.img A20-OLinuXino-Lime2 Android for NAND with HDMI and 7 inch display support]

FTP location of Android 4.2.2 release 1 for NAND memory (with HDMI and 10 inch 1024x600 support - LCD-OLinuXino-10TS): [https://ftp.olimex.com/Allwinner_Images/A20-OLinuXino-LIME2/Android/nand/A20_Lime2_android_4_22_NAND_LCD10_HDMI_release1.img A20-OLinuXino-Lime2 Android for NAND with HDMI and 10 inch display support]

For microSD card:

FTP location of Android 4.2.2 release 2 for 8GB microSD card (with HDMI and 800x480 support): [https://ftp.olimex.com/Allwinner_Images/A20-OLinuXino-LIME2/Android/sd/A20_Lime2_Android_4.22_SD_card_LCD_800x480_HDMI_8GB_release_2.img.7z A20-OLinuXino-Lime2 Android for 8GB microSD card with HDMI and 7 inch display support]

FTP location of Android 4.2.2 release 2 for 16GB microSD card (with HDMI and 1024x600 support):
[https://ftp.olimex.com/Allwinner_Images/A20-OLinuXino-LIME2/Android/sd/A20-LIME2-ANDROID-SD-expanded-16GB_LCD10_cfg0_0.zip A20-OLinuXino-Lime2 Android for 16GB microSD card with HDMI and 10 inch display support, this image requires loading via PhoenixSuit, refer to the FAQ section at the end of this page]

Build instructions and source files for the official Android images for A20 boards in this repository: https://github.com/hehopmajieh/olinuxino_configs

== Notable unofficial images ==

Below you would find locations to images released by the community. These are not officially supported by Olimex, however, some of these releases are pretty good and worth a try:

*A number of very good and optimized A20-OLinuXino-LIME2 Armbian images: [https://www.armbian.com/olimex-lime-2/ link to LIME2 article at Armbian's web-site]

*A20-OLinuXino-LIME2 is supported by openSUSE Factory, installation instructions might be found here: [https://en.opensuse.org/HCL:A20-OLinuXIno-LIME2 openSUSE wiki link]

*A20-OLinuXino-LIME2 is recognized by the Devuan community and there are official releases here might be found here: [https://files.devuan.org/devuan_ascii/embedded/ Devuan list of files link]
 

== Documents ==

===A20-OLinuXino-LIME2 user's manual===
[https://www.olimex.com/Products/OLinuXino/A20/A20-OLinuXIno-LIME2/resources/A20-OLinuXino-LIME2-UM.pdf User's manual for A20-OLinuXino-LIME2 and A20-OLinuXino-LIME2-4GB]

=== A20 Brief ===
[https://github.com/OLIMEX/OLINUXINO/blob/master/HARDWARE/A20-PDFs/A20%20brief%2020130407.pdf A20 brief]

=== A20 Datasheet ===

[https://github.com/OLIMEX/OLINUXINO/blob/master/HARDWARE/A20-PDFs/A20%20Datasheet%20v1.0%2020130227.pdf A20 Datasheet]

=== A20 User Manual ===

[https://github.com/OLIMEX/OLINUXINO/blob/master/HARDWARE/A20-PDFs/A20%20User%20Manual%202013-03-22.pdf A20 user's manual]

== Hardware ==

===LIME2 shield templates===
[https://github.com/OLIMEX/OLINUXINO/tree/master/HARDWARE/A20-OLinuXino-LIME2 Eagle and KiCAD shield templates for LIME2]

===GPIO description===

[https://github.com/OLIMEX/OLINUXINO/blob/master/HARDWARE/A20-OLinuXino-LIME2/3.%20Templates%20and%20more/A20_LIME2_GPIOs.pdf A20-OLinuXino-LIME2 GPIO description]

A template that might be used to create custom shields or own adapters might be downloaded for Eagle or KiCad at the GitHub here: [https://github.com/OLIMEX/OLINUXINO/tree/master/HARDWARE/A20-OLinuXino-LIME2 shield template]

===Power supply and consumption===

A20-OLinuXino-LIME2 requires 5V regulated power supply external source. regulated means that the power supply adapter should provide exactly 5V no matter loaded or unloaded (some cheap wallwart adapters are not regulated and under no load their power supply may be higher than 5V although marked as 5V power supply, please measure with voltmeter if your power supply provide 5V as if you connect more than 5V to LIME it will be damaged!!!)

The power jack is standard [https://www.olimex.com/wiki/PWRJACK OLIMEX power jack].

A20-OLinuXino-LIME can be powered from three sources:
*+5VDC voltage applied PWR jack
*+3.7V from LiPo re-chargable battery connected to LiPo board connector
*+5V applied to USB-OTG connector

Power consumption is as follows:
*LiPo 3.7V power battery: 1.2W
*+5VDC input power: 1.3W

Comparison table of power consumption might be found at the following [https://www.olimex.com/Products/OLinuXino/_resources/OLinuXino-Consumption.pdf link].

LiPo battery allow backup power supply when main power is interrupted. A20-OLinuXino-LIME2 has power managment IC which charge the battery when main power is present, when power is interrupted the LiPo battery automatically provide backup power supply. Step-up converter prvide 5V for the USB peripherials too. For LiPo batteries we recommend these:
*[https://www.olimex.com/Products/Power/BATTERY-LIPO1400mAh/ 1400mAh]
*[https://www.olimex.com/Products/Power/BATTERY-LIPO3000mAh/ 3000mAh]
*[https://www.olimex.com/Products/Power/BATTERY-LIPO4400mAh/ 4400mAh]
*[https://www.olimex.com/Products/Power/BATTERY-LIPO6600mAh/ 6600mAh]
 

===Board dimensions===

A20-OLinuXino-LIME2 basic dimensions in mils: 3305.5 x 2347.0

Some additional measures might be seen in the image of A10-OLinuXino-LIME which has almost identical layout. It is available as .png here:
[https://www.olimex.com/Products/OLinuXino/A10/A10-OLinuXino-LIME/resources/A10-LIME-dimensions.png link]

===CAD files===

A20-OLinuXino-LIME2 is an Open Source Hardware, CAD files are available at [https://github.com/OLIMEX/OLINUXINO/tree/master/HARDWARE/A20-OLinuXino-LIME2 GitHub]

The CAD product used to design OLinuXino is Eagle and you can download evaluation free version from their [http://www.cadsoftusa.com/ web].

===Board Layout===

[[File:A20-OLinuXino-LIME2_top_naming_extras.jpg|650px]]

[[File:A20-OLinuXino-LIME2 bottom naming.jpg|650px]]

== Software ==

===Linux Commands===

[[Linux-Commands]] Brief Linux Command reference

===Python library for GPIO, I2C and SPI control===

The Debian Linux Python package for A20-OLinuXino-LIME2 is called pyA20Lime2. It makes the access to GPIO, I2C and SPI considerably easier. It is installed in the default Debian image. More information and examples on how it can be used might be found here:

[https://pypi.python.org/pypi/pyA20Lime2 Link to pyA20Lime2 package at python.org]

===GPIO under Linux===

GPIOs are located in /sys/class/gpio directory. Note that first you have to export GPIOs. For example:

add gpioPH2

root@A20:~# echo 20 > /sys/class/gpio/export

make PH2 output

root@A20:~# echo out > //sys/class/gpio/gpio20_ph2/direction

turn on onboard LED(connected to PH2)

root@A20:~# echo 1 > /sys/class/gpio/gpio20_ph2/value

turn off onboard LED(connected to PH2)

root@A20:~# echo 0 > /sys/class/gpio/gpio20_ph2/value

Full list with supported GPIOs is:

gpio21_ph7 gpio33_ph20 gpio45_pb12 gpio57_pi2 gpio69_pi14
gpio10_pg11 gpio22_ph9 gpio34_ph21 gpio46_pb13 gpio58_pi3 gpio6_pg5
gpio11_pc3 gpio23_ph10 gpio35_ph22 gpio47_pb14 gpio59_pi4 gpio70_pi15
gpio12_pc18 gpio24_ph11 gpio36_ph23 gpio48_pb15 gpio5_pg4 gpio71_pi16
gpio13_pc19 gpio25_ph12 gpio37_pb3 gpio49_pb16 gpio60_pi5 gpio72_pi17
gpio14_pc20 gpio26_ph13 gpio38_pb4 gpio4_pg3 gpio61_pi6 gpio73_pi18
gpio15_pc21 gpio27_ph14 gpio39_pb5 gpio50_pb17 gpio62_pi7 gpio74_pi19
gpio16_pc22 gpio28_ph15 gpio3_pg2 gpio51_ph24 gpio63_pi8 gpio75_pi20
gpio17_pc23 gpio29_ph16 gpio40_pb6 gpio52_ph25 gpio64_pi9 gpio7_pg6
gpio18_pc24 gpio2_pg1 gpio41_pb7 gpio53_ph26 gpio65_pi10 gpio8_pg7
gpio19_ph0 gpio30_ph17 gpio42_pb8 gpio54_ph27 gpio66_pi11 gpio9_pg8
gpio1_pg0 gpio31_ph18 gpio43_pb10 gpio55_pi0 gpio67_pi12 gpiochip1
gpio20_ph2 gpio32_ph19 gpio44_pb11 gpio56_pi1 gpio68_pi13

===Add Voice to your OLinuXino project===

[http://olimex.wordpress.com/2013/10/03/make-things-talk-with-olinuxino/ Installation of Festival on OLinuXino]
 

== How To? ==
===How to generate boot-able SD-card Debian Linux image for A20-OLinuXino-LIME2? ===

Build instructions and required files for the latest Debian images: [https://github.com/OLIMEX/OLINUXINO/tree/master/SOFTWARE/A20 instructions and files at the GitHub page]

Note that Linux-Sunxi Kernel is a work-in-progress, this means you can try the current stage/sunxi-x.x branch but if something is broken and doesn't work just revert to the git tags we give in the blog and they would work for sure.

[https://github.com/linux-sunxi/u-boot-sunxi/wiki Sunxi u-boot loader] The linux-sunxi git page contains a lot of sources for all Olimex Allwinner boards.

===How to connect a display and adjust the video output resolution?===
There is a separate article on the subject: [[how to connect display to a Lime board]]
 

=== Is it possible to boot Debian from NAND? Do you provide such image?===

Yes, it is possible. Use the latest Debian Jessie image and write "nandinstall". More information can be found in this wiki article: [[How_to_install_Debian_to_NAND| installing Debian Jessie to the 4GB NAND memory]]

There are other people who are also successful in booting Debian from the NAND. Make sure to check on the forum. Make sure to check the number of very good and optimized A20-OLinuXino Debian images by Igor Pečovnik. There are also his instructions for NAND installation of Debian: [http://www.armbian.com/download/ link to his web-site]

===How to detect and enable the Ethernet controller (if it is disabled by default)? ===

Note: in the previous Debian releases the Ethernet was auto-detected and initialized during boot BUT this was causing big delays in the start-up of the board if you didn't want to use Ethernet or if there wasn't Ethernet cable connected.

You can enable it by following these two steps:

1. To check under what name the LAN is associated write "ifconfig –a"

2. If, for example, it is under eth0 name, then write: "dhclient eth0"

This should enable the Ethernet and then SSH would also be available.

===How to download new Android image to the NAND memory of my A20 board?===

Follow these steps to download the image to the NAND memory:

*1. Install and run PhoenixSuit (can be found here: [https://drive.google.com/file/d/0BwplT87k9SCgaTFTZnVST05ONzA/view?usp=sharing download from google drive]).

*2. Go to firmware tab of the program and point to a valid Android image (the latest official one may also be downloaded above).

*3. Disconnect the power supply and USB cable from the A20 board.

*4. Press and hold RECOVERY button, apply power supply 5V, release RECOVERY button.

*5. Connect USB cable to the mini USB connector.

*6. You will be asked for drivers for the bootloader. Navigate to the folder where you extracted the PhoenixSuit and install the drivers from the respective executables (or manually point the installer to the drivers folder in the PhoenixSuit installation path).

*7. PhoenixSuit will detect the board and would ask for the method of writing the image. Choose method of writing the image and confirm your wish to write the image.

*8. Wait till upgrade succeeds

Note that it is not recommended to have your mini USB connected to an external USB hub. This might cause delays and might distort the signal levels. Always test with the USB connected straight to the USB ports of your computer.

===How to generate Arch Linux image?===

Recent forum post by user progmetalbg here: [https://www.olimex.com/forum/index.php?topic=4261.0| at Olimex forums]

[http://alarma20.wordpress.com/2013/09/13/howto-build-arch-linux-arm-for-a20-olinuxino-micro/ Older step by step instructions on how to build Arch Linux image for another A20 board]

===How do I write the official Android image to a micro SD card for my A20 board?===
A: First download one of the official Android images, which might be found in the Android section above.

Make sure that the download link you visit clearly indicates that the image is suitable for the microSD card since there are images suitable for NAND memory also. The images suitable for the microSD memory and those suitable for NAND card are different. However, the upload method is almost identical – using PhoenixSuit.

There are two types of Android images for microSD card that we usually provide and each of them has to be downloaded to a microSD card using a different method. The image provided for microSD card is either the native Android image that can be downloaded to the card via a software tool like PhoenixSuit (through the board) or an image taken from an already prepared microSD card that requires to simply write the image (through a microSD card reader).

'''It is more likely that you have an Android image that requires a simple copy to a card. If that is the case you can follow the exact steps as for Linux (e.g. using "Win32 Disk Imager" or "dd" command).'''

In order to prepare a microSD card with a native Android you will need a software tool called PhoenixSuit and then:

• Install and run PhoenixSuit (can be found here: [https://drive.google.com/file/d/0BwplT87k9SCgaTFTZnVST05ONzA/view?usp=sharing download from google drive])

• Go to the firmware tab of the program and point to a valid Android image (note that the
images on Gdrive are compressed and you have to extract them to .img files to be able write
them with PhoenixSuit)

• Disconnect the power supply and USB cable from the A20 board. Put an SD card in micro SD
holder. We recommend either a 4GB or a 8GB class 10 card.

• Press and hold RECOVERY button, apply power supply 5V, release RECOVERY button.

• Connect USB cable to the mini USB connector.

• You will be asked for drivers for the boot-loader. Navigate to the folder where you extracted the PhoenixSuit and install the drivers from the respective executables (or manually point the installer to the drivers folder in the PhoenixSuit installation path).

• PhoenixSuit will detect the board and would ask for the method of writing the image. Choose
method of writing the image and confirm your wish to write the image.

• Wait till upgrade succeeds

Note that it is not recommended to have your mini USB connected to an external USB hub. This
might cause delays and might distort the signal levels. Always test with the USB connected straight to the USB ports of your computer.

Important: When Android runs for very first time it takes several minutes to initialize all files and buffers please do not cut the power supply during this process! Also when fresh image is installed fast boot may be disabled, which means that when you apply power supply after few seconds Android will go in sleep mode and you have to press POWER button to start it, you can change to fast boot when you power off there is dialog box asking you if you want next boot to be fast boot, you have to check this box before you power off. Also note that you must do touch screen calibration when you run Android for very first time which might require a mouse.

===I don't have neither serial cable, nor HDMI monitor. I also can't access the local Ethernet network. Can I somehow access the board anyway?===

The latest official Debian Linux image allows the use the USB_OTG connector for SSH connection without the need of a LAN cable or a serial cable. You can use a mini USB cable connected between your host PC and the on-board mini USB connector. For connection convenience there is a DHCP server running specifically for USB0 interface. The DHCP server should give IP address to the new USB0 interface of your host PC so you can make SSH connection from your PC to the default board IP address of the USB0 interface – 192.168.2.1.

You can connect to the board using a mini USB cable and an SSH client (if you use Windows you might use "puTTY", for example) at address 192.168.2.1.

For Windows operating system - upon connection, the board should show up in "Windows Device Manager" as "RNDIS Ethernet Gadget". You might be asked to install a driver. The drivers can be found online as "RNDIS driver" (Remote Network Driver Interface Specification). The drivers are provided by Microsoft and they should be available for every Windows distribution - refer to the respective files and articles provided by Microsoft on how to install the required drivers.

===How to edit board configurations and definitions in the official Debian Linux? ===

Do you want a custom video resolution output? Do you need a different port definition? Do you need to change the hardware defitions of the board?

You would need to edit the board's script.bin/script.fex file. How to do it is described in another separate article: [[how to edit board configurations and definitions in the official Debian Linux]].

===How to add STK1160 video capture driver support in Kernel 3.4===

[https://www.olimex.com/wiki/STK1160-howto-linux-sunxi-3_4 STK1160] driver backport by Dimitar Tomov
[[Main_Page]]

A20-OLinuXino-LIME2

2024-09-30T07:58:48Z

LubOlimex: /* Official Images from OLIMEX */

[[File:A20-OLinuXino-LIME2.jpg|600px]]

A20-OLinuXino-LIME2 looks similar to both [[A20-OLinuXino-LIME]] and [[A10-OLinuXino-LIME]]. The major differences between A20-OLinuXino-LIME2 and A20-OLinuXino-LIME are:

*LIME2 has gigabit Ethernet (GbE), compared to the standard 100Mb Ethernet of the LIME
*LIME2 design provides double the RAM memory, compared to the LIME design (1024 vs 512)
*Much better routing of DDR3 memory.
*Increased the number of layers from 6 in LIME to 8 in LIME2
*Corrected pinout of the LCD and GPIO connectors (shields designed for the LIME layout are not compatible with the LIME2 layout)

The A10 and the A20 processors are pin-to-pin compatible. Because of the processor, software-wise the board is closer to [[A20-OLinuXino-LIME]] than to the [[A10-OLinuXino-LIME]]. This resemblance to other designs definitely might speed the development on the board - a lot of software written for A20-OLinuXino-LIME might work out-of-the-box with A20-OLinuXino-LIME2. Additionally, pinout tables, GPIO maps, etc released for A20-OLinuXino-LIME would apply to A20-OLinuXino-LIME2 (except for the 0.05" step connectors - LCD display and all the GPIOs connectors, which have a different layout compared to both A20-OLinuXino-LIME and A10-OLinuXino-LIME).

A20-OLinuXino-LIME2 features:
*A20 Cortex-A7 dual-core ARM Cortex-A7 CPU and dual-core Mali 400 GPU
*'''1GB DDR3 RAM memory'''
*'''1 gigabit native Ethernet'''
*optional 4GB NAND FLASH memory
*SATA connector with 5V SATA power jack
*HDMI FullHD 1080p
*2x USB Low-Full-High-Speed hosts with power control and current limiter
*USB-OTG with power control and current limiter
*LiPo Battery connector with battery-charging capabilities
*LCD connector compatible with with 4.3", 7.0", 10.1" LCD modules from Olimex
*160 GPIOs on three GPIO connectors
*MicroSD card connector
*DEBUG-UART connector for console debug with USB-SERIAL-CABLE-F
*status LED
*Battery charge status LED
*Power LED
*2KB EEPROM for MAC address storage and more
*2 BUTTONS with ANDROID functionality + RESET button
*2 mount holes
*5V input power supply, noise immune design
*PCB dimensions: 84 x 60 mm

== Official Images from OLIMEX ==

'''The recommended image for most of Olimex-made Linux boards is Olimage Linux, you can find information about it in the document here:'''

https://github.com/OLIMEX/OLINUXINO/blob/master/DOCUMENTS/OLIMAGE/Olimage-guide.pdf

'''Notice this wiki article refers to outdated images and practices, if using Olimage Linux, use the information only as a reference (do not take it literally)!'''

In this chapter you would find links to FTP location with the official Debian and Android images. The images in this chapter were compiled by Olimex. They are recommended for beginners and first time users since they include full hardware support. If you are experienced Linux professional you might find useful our build instructions also published here.

The downloaded file xxxx.7z is an archive of xxx.img file. In order to write the image on SD card you have to extract the xxx.7z file.

*For Windows: use 7zip and then use Win32DiskImager.exe (http://sourceforge.net/projects/win32diskimager/) to write the image

*For Linux: use p7zip package. If you don't have 7zip installed first install it 

#apt-get install p7zip
Copy a20_Lime2_debian_second_release.7z file in your directory and unzip the archive with
#7za e a20_Lime2_debian_second_release.7z
where a20_Lime2_debian_second_release.7z
The output should be a new 4GB file with extension img
Put 4GB SD card in your card reader and type
# ls /dev/sd
Then press two times <TAB> you will see a list of your sd devices like sda sdb sdc note that some of these devices may be your hard disk so make sure you know which one is your sd card before you proceed as you can damage your HDD if you choose the wrong sd-device. You can do this by unplugging your sd card reader and identify which "sd" devices remove from the list.
Once you know which device is your sdcard like sda use this text instead of the sdX name in the references below:
#dd if=a20_Lime2_debian_second_release.img of=/dev/sdX

The Debian Linux image is 4GB and the file system can be extended to suit a bigger card. Use the following three commands to execute a script that would use all the free space of your card:

sudo su
./resize_sd.sh /dev/mmcblk0 2
reboot

=== Linux images ===

These official Debian images should be downloaded to a microSD card. Older sunxi images can be found as direct downloads at our FTP. You can install the Debian to the NAND or the eMMC of your board (if it comes with one). Information on booting Debian from the NAND might be found in these wiki articles: [[how to install Debian to NAND]]; [[how to install Debian to eMMC]]. Download locations for the official images might be found below:

'''ALWAYS FIRST TEST WITH LATEST OFFICIAL IMAGE, NEWER HARDWARE REVISIONS OF THE BOARD MIGHT NOT WORK WITH OLDER IMAGES!!!'''

----

'''Latest stable official images - Debian 8 (Jessie)''' '''Both images are suitable for the standard version A20-OLinuXino-LIME2. However A20-OLinuXino-LIME2-n4GB and A20-OLinuXino-LIME2-n8GB have different image compared to A20-OLinuXino-LIME2-e4GB''':'''

FTP location for official Debian Jessie release #13 for A20-OLinuXino-LIME2, A20-OLinuXino-LIME2-n4GB, and A20-OLinuXino-LIME2-n8GB (not suitable for boards with eMMC flash): [https://ftp.olimex.com/Allwinner_Images/A20-OLinuXino-LIME2/Debian/sd/a20-lime2_mainline_uboot_sunxi_kernel_3.4.103_jessie_NAND_rel_13.img.7z A20-OLinuXino-LIME2 Debian Jessie with kernel 3.4.103+ release 13]

FTP location for official Debian Jessie release #16 for A20-OLinuXino-LIME2, A20-OLinuXino-LIME2-e4GB (not suitable for boards with NAND flash): [https://ftp.olimex.com/Allwinner_Images/A20-OLinuXino-LIME2/Debian/sd/a20-lime2_mainline_uboot_sunxi_kernel_3.4.103_jessie_eMMC_rel_16.zip A20 lime2 mainline uboot sunxi kernel 3.4.103 jessie eMMC rel 16]

Image description and typical interfacing: [https://github.com/OLIMEX/OLINUXINO/blob/master/SOFTWARE/A20/A20-build-3.4.103-release-7/USAGE-AND-COMMON-PRACTICEs-A20-Olimex_kernel_3.4.103%2B_Jessie_rel_3.txt description and basic usage of different peripherals at at the GitHub page]

Image build instructions and required files for latest Debian Jessie release might be found here: [https://github.com/OLIMEX/OLINUXINO/blob/master/SOFTWARE/A20/A20-build-3.4.103-release-8/BUILD_DESCRIPTION_A20_Olimex_kernel_3.4.103%2B_Jessie_rel_8.txt build instructions and required files at the GitHub page]

You can find some older releases and older build instructions (older image revisions might be used as a reference, for testing purposes, or if you own old hardware revision of the board) at the following article: [[A20-OLinuXino-LIME2-older-releases|older releases and older build instructions]]

----

Note: the A20-LIME2-DEBIAN-SD card which we have in our web store contains the image suitable for board with no flash or board with NAND memory on a 8GB Class10 fast microSD card. The A20-LIME2-eMMC-DEBIAN-SD contains the image suitable for boards with extra eMMC memory. If you want to use our images, please, use card with speed Class10 or higher. Else the Linux performance would be very slow.

Note: in the previous Debian releases the Ethernet was auto-detected and initialized during boot BUT this was causing big delays in the start-up of the board if you didn't want to use Ethernet or if there wasn't Ethernet cable connected.

You can enable it by following these two steps:

1. To check under what name the LAN is associated write "ifconfig –a"

2. If, for example, it is under eth0 name, then write: "dhclient eth0"

This should enable the Ethernet and then SSH would also be available.

=== Android images ===

Links to FTP location of official Android releases are below. Please read description of the image carefully.

'''Newest official release (recommended):'''

For the NAND flash memory:

FTP location of Android 4.2.2 release 1 for NAND memory (with HDMI and 7 inch 800x480 support - LCD-OLinuXino-7TS): [https://ftp.olimex.com/Allwinner_Images/A20-OLinuXino-LIME2/Android/nand/A20_Lime2_android_4_22_NAND_LCD7_HDMI_release1.img A20-OLinuXino-Lime2 Android for NAND with HDMI and 7 inch display support]

FTP location of Android 4.2.2 release 1 for NAND memory (with HDMI and 10 inch 1024x600 support - LCD-OLinuXino-10TS): [https://ftp.olimex.com/Allwinner_Images/A20-OLinuXino-LIME2/Android/nand/A20_Lime2_android_4_22_NAND_LCD10_HDMI_release1.img A20-OLinuXino-Lime2 Android for NAND with HDMI and 10 inch display support]

For microSD card:

FTP location of Android 4.2.2 release 2 for 8GB microSD card (with HDMI and 800x480 support): [https://ftp.olimex.com/Allwinner_Images/A20-OLinuXino-LIME2/Android/sd/A20_Lime2_Android_4.22_SD_card_LCD_800x480_HDMI_8GB_release_2.img.7z A20-OLinuXino-Lime2 Android for 8GB microSD card with HDMI and 7 inch display support]

FTP location of Android 4.2.2 release 2 for 16GB microSD card (with HDMI and 1024x600 support):
[https://ftp.olimex.com/Allwinner_Images/A20-OLinuXino-LIME2/Android/sd/A20-LIME2-ANDROID-SD-expanded-16GB_LCD10_cfg0_0.zip A20-OLinuXino-Lime2 Android for 16GB microSD card with HDMI and 10 inch display support, this image requires loading via PhoenixSuit, refer to the FAQ section at the end of this page]

Build instructions and source files for the official Android images for A20 boards in this repository: https://github.com/hehopmajieh/olinuxino_configs

== Notable unofficial images ==

Below you would find locations to images released by the community. These are not officially supported by Olimex, however, some of these releases are pretty good and worth a try:

*A number of very good and optimized A20-OLinuXino-LIME2 Armbian images: [https://www.armbian.com/olimex-lime-2/ link to LIME2 article at Armbian's web-site]

*A20-OLinuXino-LIME2 is supported by openSUSE Factory, installation instructions might be found here: [https://en.opensuse.org/HCL:A20-OLinuXIno-LIME2 openSUSE wiki link]

*A20-OLinuXino-LIME2 is recognized by the Devuan community and there are official releases here might be found here: [https://files.devuan.org/devuan_ascii/embedded/ Devuan list of files link]
 

== Documents ==

===A20-OLinuXino-LIME2 user's manual===
[https://www.olimex.com/Products/OLinuXino/A20/A20-OLinuXIno-LIME2/resources/A20-OLinuXino-LIME2-UM.pdf User's manual for A20-OLinuXino-LIME2 and A20-OLinuXino-LIME2-4GB]

=== A20 Brief ===
[https://github.com/OLIMEX/OLINUXINO/blob/master/HARDWARE/A20-PDFs/A20%20brief%2020130407.pdf A20 brief]

=== A20 Datasheet ===

[https://github.com/OLIMEX/OLINUXINO/blob/master/HARDWARE/A20-PDFs/A20%20Datasheet%20v1.0%2020130227.pdf A20 Datasheet]

=== A20 User Manual ===

[https://github.com/OLIMEX/OLINUXINO/blob/master/HARDWARE/A20-PDFs/A20%20User%20Manual%202013-03-22.pdf A20 user's manual]

== Hardware ==

===LIME2 shield templates===
[https://github.com/OLIMEX/OLINUXINO/tree/master/HARDWARE/A20-OLinuXino-LIME2 Eagle and KiCAD shield templates for LIME2]

===GPIO description===

[https://github.com/OLIMEX/OLINUXINO/blob/master/HARDWARE/A20-OLinuXino-LIME2/3.%20Templates%20and%20more/A20_LIME2_GPIOs.pdf A20-OLinuXino-LIME2 GPIO description]

A template that might be used to create custom shields or own adapters might be downloaded for Eagle or KiCad at the GitHub here: [https://github.com/OLIMEX/OLINUXINO/tree/master/HARDWARE/A20-OLinuXino-LIME2 shield template]

===Power supply and consumption===

A20-OLinuXino-LIME2 requires 5V regulated power supply external source. regulated means that the power supply adapter should provide exactly 5V no matter loaded or unloaded (some cheap wallwart adapters are not regulated and under no load their power supply may be higher than 5V although marked as 5V power supply, please measure with voltmeter if your power supply provide 5V as if you connect more than 5V to LIME it will be damaged!!!)

The power jack is standard [https://www.olimex.com/wiki/PWRJACK OLIMEX power jack].

A20-OLinuXino-LIME can be powered from three sources:
*+5VDC voltage applied PWR jack
*+3.7V from LiPo re-chargable battery connected to LiPo board connector
*+5V applied to USB-OTG connector

Power consumption is as follows:
*LiPo 3.7V power battery: 1.2W
*+5VDC input power: 1.3W

Comparison table of power consumption might be found at the following [https://www.olimex.com/Products/OLinuXino/_resources/OLinuXino-Consumption.pdf link].

LiPo battery allow backup power supply when main power is interrupted. A20-OLinuXino-LIME2 has power managment IC which charge the battery when main power is present, when power is interrupted the LiPo battery automatically provide backup power supply. Step-up converter prvide 5V for the USB peripherials too. For LiPo batteries we recommend these:
*[https://www.olimex.com/Products/Power/BATTERY-LIPO1400mAh/ 1400mAh]
*[https://www.olimex.com/Products/Power/BATTERY-LIPO3000mAh/ 3000mAh]
*[https://www.olimex.com/Products/Power/BATTERY-LIPO4400mAh/ 4400mAh]
*[https://www.olimex.com/Products/Power/BATTERY-LIPO6600mAh/ 6600mAh]
 

===Board dimensions===

A20-OLinuXino-LIME2 basic dimensions in mils: 3305.5 x 2347.0

Some additional measures might be seen in the image of A10-OLinuXino-LIME which has almost identical layout. It is available as .png here:
[https://www.olimex.com/Products/OLinuXino/A10/A10-OLinuXino-LIME/resources/A10-LIME-dimensions.png link]

===CAD files===

A20-OLinuXino-LIME2 is an Open Source Hardware, CAD files are available at [https://github.com/OLIMEX/OLINUXINO/tree/master/HARDWARE/A20-OLinuXino-LIME2 GitHub]

The CAD product used to design OLinuXino is Eagle and you can download evaluation free version from their [http://www.cadsoftusa.com/ web].

===Board Layout===

[[File:A20-OLinuXino-LIME2_top_naming_extras.jpg|650px]]

[[File:A20-OLinuXino-LIME2 bottom naming.jpg|650px]]

== Software ==

===Linux Commands===

[[Linux-Commands]] Brief Linux Command reference

===Python library for GPIO, I2C and SPI control===

The Debian Linux Python package for A20-OLinuXino-LIME2 is called pyA20Lime2. It makes the access to GPIO, I2C and SPI considerably easier. It is installed in the default Debian image. More information and examples on how it can be used might be found here:

[https://pypi.python.org/pypi/pyA20Lime2 Link to pyA20Lime2 package at python.org]

===GPIO under Linux===

GPIOs are located in /sys/class/gpio directory. Note that first you have to export GPIOs. For example:

add gpioPH2

root@A20:~# echo 20 > /sys/class/gpio/export

make PH2 output

root@A20:~# echo out > //sys/class/gpio/gpio20_ph2/direction

turn on onboard LED(connected to PH2)

root@A20:~# echo 1 > /sys/class/gpio/gpio20_ph2/value

turn off onboard LED(connected to PH2)

root@A20:~# echo 0 > /sys/class/gpio/gpio20_ph2/value

Full list with supported GPIOs is:

gpio21_ph7 gpio33_ph20 gpio45_pb12 gpio57_pi2 gpio69_pi14
gpio10_pg11 gpio22_ph9 gpio34_ph21 gpio46_pb13 gpio58_pi3 gpio6_pg5
gpio11_pc3 gpio23_ph10 gpio35_ph22 gpio47_pb14 gpio59_pi4 gpio70_pi15
gpio12_pc18 gpio24_ph11 gpio36_ph23 gpio48_pb15 gpio5_pg4 gpio71_pi16
gpio13_pc19 gpio25_ph12 gpio37_pb3 gpio49_pb16 gpio60_pi5 gpio72_pi17
gpio14_pc20 gpio26_ph13 gpio38_pb4 gpio4_pg3 gpio61_pi6 gpio73_pi18
gpio15_pc21 gpio27_ph14 gpio39_pb5 gpio50_pb17 gpio62_pi7 gpio74_pi19
gpio16_pc22 gpio28_ph15 gpio3_pg2 gpio51_ph24 gpio63_pi8 gpio75_pi20
gpio17_pc23 gpio29_ph16 gpio40_pb6 gpio52_ph25 gpio64_pi9 gpio7_pg6
gpio18_pc24 gpio2_pg1 gpio41_pb7 gpio53_ph26 gpio65_pi10 gpio8_pg7
gpio19_ph0 gpio30_ph17 gpio42_pb8 gpio54_ph27 gpio66_pi11 gpio9_pg8
gpio1_pg0 gpio31_ph18 gpio43_pb10 gpio55_pi0 gpio67_pi12 gpiochip1
gpio20_ph2 gpio32_ph19 gpio44_pb11 gpio56_pi1 gpio68_pi13

===Add Voice to your OLinuXino project===

[http://olimex.wordpress.com/2013/10/03/make-things-talk-with-olinuxino/ Installation of Festival on OLinuXino]
 

== How To? ==
===How to generate boot-able SD-card Debian Linux image for A20-OLinuXino-LIME2? ===

Build instructions and required files for the latest Debian images: [https://github.com/OLIMEX/OLINUXINO/tree/master/SOFTWARE/A20 instructions and files at the GitHub page]

Note that Linux-Sunxi Kernel is a work-in-progress, this means you can try the current stage/sunxi-x.x branch but if something is broken and doesn't work just revert to the git tags we give in the blog and they would work for sure.

[https://github.com/linux-sunxi/u-boot-sunxi/wiki Sunxi u-boot loader] The linux-sunxi git page contains a lot of sources for all Olimex Allwinner boards.

===How to connect a display and adjust the video output resolution?===
There is a separate article on the subject: [[how to connect display to a Lime board]]
 

=== Is it possible to boot Debian from NAND? Do you provide such image?===

Yes, it is possible. Use the latest Debian Jessie image and write "nandinstall". More information can be found in this wiki article: [[How_to_install_Debian_to_NAND| installing Debian Jessie to the 4GB NAND memory]]

There are other people who are also successful in booting Debian from the NAND. Make sure to check on the forum. Make sure to check the number of very good and optimized A20-OLinuXino Debian images by Igor Pečovnik. There are also his instructions for NAND installation of Debian: [http://www.armbian.com/download/ link to his web-site]

===How to detect and enable the Ethernet controller (if it is disabled by default)? ===

Note: in the previous Debian releases the Ethernet was auto-detected and initialized during boot BUT this was causing big delays in the start-up of the board if you didn't want to use Ethernet or if there wasn't Ethernet cable connected.

You can enable it by following these two steps:

1. To check under what name the LAN is associated write "ifconfig –a"

2. If, for example, it is under eth0 name, then write: "dhclient eth0"

This should enable the Ethernet and then SSH would also be available.

===How to download new Android image to the NAND memory of my A20 board?===

Follow these steps to download the image to the NAND memory:

*1. Install and run PhoenixSuit (can be found here: [https://drive.google.com/file/d/0BwplT87k9SCgaTFTZnVST05ONzA/view?usp=sharing download from google drive]).

*2. Go to firmware tab of the program and point to a valid Android image (the latest official one may also be downloaded above).

*3. Disconnect the power supply and USB cable from the A20 board.

*4. Press and hold RECOVERY button, apply power supply 5V, release RECOVERY button.

*5. Connect USB cable to the mini USB connector.

*6. You will be asked for drivers for the bootloader. Navigate to the folder where you extracted the PhoenixSuit and install the drivers from the respective executables (or manually point the installer to the drivers folder in the PhoenixSuit installation path).

*7. PhoenixSuit will detect the board and would ask for the method of writing the image. Choose method of writing the image and confirm your wish to write the image.

*8. Wait till upgrade succeeds

Note that it is not recommended to have your mini USB connected to an external USB hub. This might cause delays and might distort the signal levels. Always test with the USB connected straight to the USB ports of your computer.

===How to generate Arch Linux image?===

Recent forum post by user progmetalbg here: [https://www.olimex.com/forum/index.php?topic=4261.0| at Olimex forums]

[http://alarma20.wordpress.com/2013/09/13/howto-build-arch-linux-arm-for-a20-olinuxino-micro/ Older step by step instructions on how to build Arch Linux image for another A20 board]

===How do I write the official Android image to a micro SD card for my A20 board?===
A: First download one of the official Android images, which might be found in the Android section above.

Make sure that the download link you visit clearly indicates that the image is suitable for the microSD card since there are images suitable for NAND memory also. The images suitable for the microSD memory and those suitable for NAND card are different. However, the upload method is almost identical – using PhoenixSuit.

There are two types of Android images for microSD card that we usually provide and each of them has to be downloaded to a microSD card using a different method. The image provided for microSD card is either the native Android image that can be downloaded to the card via a software tool like PhoenixSuit (through the board) or an image taken from an already prepared microSD card that requires to simply write the image (through a microSD card reader).

'''It is more likely that you have an Android image that requires a simple copy to a card. If that is the case you can follow the exact steps as for Linux (e.g. using "Win32 Disk Imager" or "dd" command).'''

In order to prepare a microSD card with a native Android you will need a software tool called PhoenixSuit and then:

• Install and run PhoenixSuit (can be found here: [https://drive.google.com/file/d/0BwplT87k9SCgaTFTZnVST05ONzA/view?usp=sharing download from google drive])

• Go to the firmware tab of the program and point to a valid Android image (note that the
images on Gdrive are compressed and you have to extract them to .img files to be able write
them with PhoenixSuit)

• Disconnect the power supply and USB cable from the A20 board. Put an SD card in micro SD
holder. We recommend either a 4GB or a 8GB class 10 card.

• Press and hold RECOVERY button, apply power supply 5V, release RECOVERY button.

• Connect USB cable to the mini USB connector.

• You will be asked for drivers for the boot-loader. Navigate to the folder where you extracted the PhoenixSuit and install the drivers from the respective executables (or manually point the installer to the drivers folder in the PhoenixSuit installation path).

• PhoenixSuit will detect the board and would ask for the method of writing the image. Choose
method of writing the image and confirm your wish to write the image.

• Wait till upgrade succeeds

Note that it is not recommended to have your mini USB connected to an external USB hub. This
might cause delays and might distort the signal levels. Always test with the USB connected straight to the USB ports of your computer.

Important: When Android runs for very first time it takes several minutes to initialize all files and buffers please do not cut the power supply during this process! Also when fresh image is installed fast boot may be disabled, which means that when you apply power supply after few seconds Android will go in sleep mode and you have to press POWER button to start it, you can change to fast boot when you power off there is dialog box asking you if you want next boot to be fast boot, you have to check this box before you power off. Also note that you must do touch screen calibration when you run Android for very first time which might require a mouse.

===I don't have neither serial cable, nor HDMI monitor. I also can't access the local Ethernet network. Can I somehow access the board anyway?===

The latest official Debian Linux image allows the use the USB_OTG connector for SSH connection without the need of a LAN cable or a serial cable. You can use a mini USB cable connected between your host PC and the on-board mini USB connector. For connection convenience there is a DHCP server running specifically for USB0 interface. The DHCP server should give IP address to the new USB0 interface of your host PC so you can make SSH connection from your PC to the default board IP address of the USB0 interface – 192.168.2.1.

You can connect to the board using a mini USB cable and an SSH client (if you use Windows you might use "puTTY", for example) at address 192.168.2.1.

For Windows operating system - upon connection, the board should show up in "Windows Device Manager" as "RNDIS Ethernet Gadget". You might be asked to install a driver. The drivers can be found online as "RNDIS driver" (Remote Network Driver Interface Specification). The drivers are provided by Microsoft and they should be available for every Windows distribution - refer to the respective files and articles provided by Microsoft on how to install the required drivers.

===How to edit board configurations and definitions in the official Debian Linux? ===

Do you want a custom video resolution output? Do you need a different port definition? Do you need to change the hardware defitions of the board?

You would need to edit the board's script.bin/script.fex file. How to do it is described in another separate article: [[how to edit board configurations and definitions in the official Debian Linux]].

===How to add STK1160 video capture driver support in Kernel 3.4===

[https://www.olimex.com/wiki/STK1160-howto-linux-sunxi-3_4 STK1160] driver backport by Dimitar Tomov
[[Main_Page]]

A20-OLinuXino-LIME2

2024-09-30T07:57:34Z

LubOlimex: /* Android images */

[[File:A20-OLinuXino-LIME2.jpg|600px]]

A20-OLinuXino-LIME2 looks similar to both [[A20-OLinuXino-LIME]] and [[A10-OLinuXino-LIME]]. The major differences between A20-OLinuXino-LIME2 and A20-OLinuXino-LIME are:

*LIME2 has gigabit Ethernet (GbE), compared to the standard 100Mb Ethernet of the LIME
*LIME2 design provides double the RAM memory, compared to the LIME design (1024 vs 512)
*Much better routing of DDR3 memory.
*Increased the number of layers from 6 in LIME to 8 in LIME2
*Corrected pinout of the LCD and GPIO connectors (shields designed for the LIME layout are not compatible with the LIME2 layout)

The A10 and the A20 processors are pin-to-pin compatible. Because of the processor, software-wise the board is closer to [[A20-OLinuXino-LIME]] than to the [[A10-OLinuXino-LIME]]. This resemblance to other designs definitely might speed the development on the board - a lot of software written for A20-OLinuXino-LIME might work out-of-the-box with A20-OLinuXino-LIME2. Additionally, pinout tables, GPIO maps, etc released for A20-OLinuXino-LIME would apply to A20-OLinuXino-LIME2 (except for the 0.05" step connectors - LCD display and all the GPIOs connectors, which have a different layout compared to both A20-OLinuXino-LIME and A10-OLinuXino-LIME).

A20-OLinuXino-LIME2 features:
*A20 Cortex-A7 dual-core ARM Cortex-A7 CPU and dual-core Mali 400 GPU
*'''1GB DDR3 RAM memory'''
*'''1 gigabit native Ethernet'''
*optional 4GB NAND FLASH memory
*SATA connector with 5V SATA power jack
*HDMI FullHD 1080p
*2x USB Low-Full-High-Speed hosts with power control and current limiter
*USB-OTG with power control and current limiter
*LiPo Battery connector with battery-charging capabilities
*LCD connector compatible with with 4.3", 7.0", 10.1" LCD modules from Olimex
*160 GPIOs on three GPIO connectors
*MicroSD card connector
*DEBUG-UART connector for console debug with USB-SERIAL-CABLE-F
*status LED
*Battery charge status LED
*Power LED
*2KB EEPROM for MAC address storage and more
*2 BUTTONS with ANDROID functionality + RESET button
*2 mount holes
*5V input power supply, noise immune design
*PCB dimensions: 84 x 60 mm

== Official Images from OLIMEX ==

In this chapter you would find links to FTP location with the official Debian and Android images. The images in this chapter were compiled by Olimex. They are recommended for beginners and first time users since they include full hardware support. If you are experienced Linux professional you might find useful our build instructions also published here.

The downloaded file xxxx.7z is an archive of xxx.img file. In order to write the image on SD card you have to extract the xxx.7z file.

*For Windows: use 7zip and then use Win32DiskImager.exe (http://sourceforge.net/projects/win32diskimager/) to write the image

*For Linux: use p7zip package. If you don't have 7zip installed first install it 

#apt-get install p7zip
Copy a20_Lime2_debian_second_release.7z file in your directory and unzip the archive with
#7za e a20_Lime2_debian_second_release.7z
where a20_Lime2_debian_second_release.7z
The output should be a new 4GB file with extension img
Put 4GB SD card in your card reader and type
# ls /dev/sd
Then press two times <TAB> you will see a list of your sd devices like sda sdb sdc note that some of these devices may be your hard disk so make sure you know which one is your sd card before you proceed as you can damage your HDD if you choose the wrong sd-device. You can do this by unplugging your sd card reader and identify which "sd" devices remove from the list.
Once you know which device is your sdcard like sda use this text instead of the sdX name in the references below:
#dd if=a20_Lime2_debian_second_release.img of=/dev/sdX

The Debian Linux image is 4GB and the file system can be extended to suit a bigger card. Use the following three commands to execute a script that would use all the free space of your card:

sudo su
./resize_sd.sh /dev/mmcblk0 2
reboot

=== Linux images ===

These official Debian images should be downloaded to a microSD card. Older sunxi images can be found as direct downloads at our FTP. You can install the Debian to the NAND or the eMMC of your board (if it comes with one). Information on booting Debian from the NAND might be found in these wiki articles: [[how to install Debian to NAND]]; [[how to install Debian to eMMC]]. Download locations for the official images might be found below:

'''ALWAYS FIRST TEST WITH LATEST OFFICIAL IMAGE, NEWER HARDWARE REVISIONS OF THE BOARD MIGHT NOT WORK WITH OLDER IMAGES!!!'''

----

'''Latest stable official images - Debian 8 (Jessie)''' '''Both images are suitable for the standard version A20-OLinuXino-LIME2. However A20-OLinuXino-LIME2-n4GB and A20-OLinuXino-LIME2-n8GB have different image compared to A20-OLinuXino-LIME2-e4GB''':'''

FTP location for official Debian Jessie release #13 for A20-OLinuXino-LIME2, A20-OLinuXino-LIME2-n4GB, and A20-OLinuXino-LIME2-n8GB (not suitable for boards with eMMC flash): [https://ftp.olimex.com/Allwinner_Images/A20-OLinuXino-LIME2/Debian/sd/a20-lime2_mainline_uboot_sunxi_kernel_3.4.103_jessie_NAND_rel_13.img.7z A20-OLinuXino-LIME2 Debian Jessie with kernel 3.4.103+ release 13]

FTP location for official Debian Jessie release #16 for A20-OLinuXino-LIME2, A20-OLinuXino-LIME2-e4GB (not suitable for boards with NAND flash): [https://ftp.olimex.com/Allwinner_Images/A20-OLinuXino-LIME2/Debian/sd/a20-lime2_mainline_uboot_sunxi_kernel_3.4.103_jessie_eMMC_rel_16.zip A20 lime2 mainline uboot sunxi kernel 3.4.103 jessie eMMC rel 16]

Image description and typical interfacing: [https://github.com/OLIMEX/OLINUXINO/blob/master/SOFTWARE/A20/A20-build-3.4.103-release-7/USAGE-AND-COMMON-PRACTICEs-A20-Olimex_kernel_3.4.103%2B_Jessie_rel_3.txt description and basic usage of different peripherals at at the GitHub page]

Image build instructions and required files for latest Debian Jessie release might be found here: [https://github.com/OLIMEX/OLINUXINO/blob/master/SOFTWARE/A20/A20-build-3.4.103-release-8/BUILD_DESCRIPTION_A20_Olimex_kernel_3.4.103%2B_Jessie_rel_8.txt build instructions and required files at the GitHub page]

You can find some older releases and older build instructions (older image revisions might be used as a reference, for testing purposes, or if you own old hardware revision of the board) at the following article: [[A20-OLinuXino-LIME2-older-releases|older releases and older build instructions]]

----

Note: the A20-LIME2-DEBIAN-SD card which we have in our web store contains the image suitable for board with no flash or board with NAND memory on a 8GB Class10 fast microSD card. The A20-LIME2-eMMC-DEBIAN-SD contains the image suitable for boards with extra eMMC memory. If you want to use our images, please, use card with speed Class10 or higher. Else the Linux performance would be very slow.

Note: in the previous Debian releases the Ethernet was auto-detected and initialized during boot BUT this was causing big delays in the start-up of the board if you didn't want to use Ethernet or if there wasn't Ethernet cable connected.

You can enable it by following these two steps:

1. To check under what name the LAN is associated write "ifconfig –a"

2. If, for example, it is under eth0 name, then write: "dhclient eth0"

This should enable the Ethernet and then SSH would also be available.

=== Android images ===

Links to FTP location of official Android releases are below. Please read description of the image carefully.

'''Newest official release (recommended):'''

For the NAND flash memory:

FTP location of Android 4.2.2 release 1 for NAND memory (with HDMI and 7 inch 800x480 support - LCD-OLinuXino-7TS): [https://ftp.olimex.com/Allwinner_Images/A20-OLinuXino-LIME2/Android/nand/A20_Lime2_android_4_22_NAND_LCD7_HDMI_release1.img A20-OLinuXino-Lime2 Android for NAND with HDMI and 7 inch display support]

FTP location of Android 4.2.2 release 1 for NAND memory (with HDMI and 10 inch 1024x600 support - LCD-OLinuXino-10TS): [https://ftp.olimex.com/Allwinner_Images/A20-OLinuXino-LIME2/Android/nand/A20_Lime2_android_4_22_NAND_LCD10_HDMI_release1.img A20-OLinuXino-Lime2 Android for NAND with HDMI and 10 inch display support]

For microSD card:

FTP location of Android 4.2.2 release 2 for 8GB microSD card (with HDMI and 800x480 support): [https://ftp.olimex.com/Allwinner_Images/A20-OLinuXino-LIME2/Android/sd/A20_Lime2_Android_4.22_SD_card_LCD_800x480_HDMI_8GB_release_2.img.7z A20-OLinuXino-Lime2 Android for 8GB microSD card with HDMI and 7 inch display support]

FTP location of Android 4.2.2 release 2 for 16GB microSD card (with HDMI and 1024x600 support):
[https://ftp.olimex.com/Allwinner_Images/A20-OLinuXino-LIME2/Android/sd/A20-LIME2-ANDROID-SD-expanded-16GB_LCD10_cfg0_0.zip A20-OLinuXino-Lime2 Android for 16GB microSD card with HDMI and 10 inch display support, this image requires loading via PhoenixSuit, refer to the FAQ section at the end of this page]

Build instructions and source files for the official Android images for A20 boards in this repository: https://github.com/hehopmajieh/olinuxino_configs

== Notable unofficial images ==

Below you would find locations to images released by the community. These are not officially supported by Olimex, however, some of these releases are pretty good and worth a try:

*A number of very good and optimized A20-OLinuXino-LIME2 Armbian images: [https://www.armbian.com/olimex-lime-2/ link to LIME2 article at Armbian's web-site]

*A20-OLinuXino-LIME2 is supported by openSUSE Factory, installation instructions might be found here: [https://en.opensuse.org/HCL:A20-OLinuXIno-LIME2 openSUSE wiki link]

*A20-OLinuXino-LIME2 is recognized by the Devuan community and there are official releases here might be found here: [https://files.devuan.org/devuan_ascii/embedded/ Devuan list of files link]
 

== Documents ==

===A20-OLinuXino-LIME2 user's manual===
[https://www.olimex.com/Products/OLinuXino/A20/A20-OLinuXIno-LIME2/resources/A20-OLinuXino-LIME2-UM.pdf User's manual for A20-OLinuXino-LIME2 and A20-OLinuXino-LIME2-4GB]

=== A20 Brief ===
[https://github.com/OLIMEX/OLINUXINO/blob/master/HARDWARE/A20-PDFs/A20%20brief%2020130407.pdf A20 brief]

=== A20 Datasheet ===

[https://github.com/OLIMEX/OLINUXINO/blob/master/HARDWARE/A20-PDFs/A20%20Datasheet%20v1.0%2020130227.pdf A20 Datasheet]

=== A20 User Manual ===

[https://github.com/OLIMEX/OLINUXINO/blob/master/HARDWARE/A20-PDFs/A20%20User%20Manual%202013-03-22.pdf A20 user's manual]

== Hardware ==

===LIME2 shield templates===
[https://github.com/OLIMEX/OLINUXINO/tree/master/HARDWARE/A20-OLinuXino-LIME2 Eagle and KiCAD shield templates for LIME2]

===GPIO description===

[https://github.com/OLIMEX/OLINUXINO/blob/master/HARDWARE/A20-OLinuXino-LIME2/3.%20Templates%20and%20more/A20_LIME2_GPIOs.pdf A20-OLinuXino-LIME2 GPIO description]

A template that might be used to create custom shields or own adapters might be downloaded for Eagle or KiCad at the GitHub here: [https://github.com/OLIMEX/OLINUXINO/tree/master/HARDWARE/A20-OLinuXino-LIME2 shield template]

===Power supply and consumption===

A20-OLinuXino-LIME2 requires 5V regulated power supply external source. regulated means that the power supply adapter should provide exactly 5V no matter loaded or unloaded (some cheap wallwart adapters are not regulated and under no load their power supply may be higher than 5V although marked as 5V power supply, please measure with voltmeter if your power supply provide 5V as if you connect more than 5V to LIME it will be damaged!!!)

The power jack is standard [https://www.olimex.com/wiki/PWRJACK OLIMEX power jack].

A20-OLinuXino-LIME can be powered from three sources:
*+5VDC voltage applied PWR jack
*+3.7V from LiPo re-chargable battery connected to LiPo board connector
*+5V applied to USB-OTG connector

Power consumption is as follows:
*LiPo 3.7V power battery: 1.2W
*+5VDC input power: 1.3W

Comparison table of power consumption might be found at the following [https://www.olimex.com/Products/OLinuXino/_resources/OLinuXino-Consumption.pdf link].

LiPo battery allow backup power supply when main power is interrupted. A20-OLinuXino-LIME2 has power managment IC which charge the battery when main power is present, when power is interrupted the LiPo battery automatically provide backup power supply. Step-up converter prvide 5V for the USB peripherials too. For LiPo batteries we recommend these:
*[https://www.olimex.com/Products/Power/BATTERY-LIPO1400mAh/ 1400mAh]
*[https://www.olimex.com/Products/Power/BATTERY-LIPO3000mAh/ 3000mAh]
*[https://www.olimex.com/Products/Power/BATTERY-LIPO4400mAh/ 4400mAh]
*[https://www.olimex.com/Products/Power/BATTERY-LIPO6600mAh/ 6600mAh]
 

===Board dimensions===

A20-OLinuXino-LIME2 basic dimensions in mils: 3305.5 x 2347.0

Some additional measures might be seen in the image of A10-OLinuXino-LIME which has almost identical layout. It is available as .png here:
[https://www.olimex.com/Products/OLinuXino/A10/A10-OLinuXino-LIME/resources/A10-LIME-dimensions.png link]

===CAD files===

A20-OLinuXino-LIME2 is an Open Source Hardware, CAD files are available at [https://github.com/OLIMEX/OLINUXINO/tree/master/HARDWARE/A20-OLinuXino-LIME2 GitHub]

The CAD product used to design OLinuXino is Eagle and you can download evaluation free version from their [http://www.cadsoftusa.com/ web].

===Board Layout===

[[File:A20-OLinuXino-LIME2_top_naming_extras.jpg|650px]]

[[File:A20-OLinuXino-LIME2 bottom naming.jpg|650px]]

== Software ==

===Linux Commands===

[[Linux-Commands]] Brief Linux Command reference

===Python library for GPIO, I2C and SPI control===

The Debian Linux Python package for A20-OLinuXino-LIME2 is called pyA20Lime2. It makes the access to GPIO, I2C and SPI considerably easier. It is installed in the default Debian image. More information and examples on how it can be used might be found here:

[https://pypi.python.org/pypi/pyA20Lime2 Link to pyA20Lime2 package at python.org]

===GPIO under Linux===

GPIOs are located in /sys/class/gpio directory. Note that first you have to export GPIOs. For example:

add gpioPH2

root@A20:~# echo 20 > /sys/class/gpio/export

make PH2 output

root@A20:~# echo out > //sys/class/gpio/gpio20_ph2/direction

turn on onboard LED(connected to PH2)

root@A20:~# echo 1 > /sys/class/gpio/gpio20_ph2/value

turn off onboard LED(connected to PH2)

root@A20:~# echo 0 > /sys/class/gpio/gpio20_ph2/value

Full list with supported GPIOs is:

gpio21_ph7 gpio33_ph20 gpio45_pb12 gpio57_pi2 gpio69_pi14
gpio10_pg11 gpio22_ph9 gpio34_ph21 gpio46_pb13 gpio58_pi3 gpio6_pg5
gpio11_pc3 gpio23_ph10 gpio35_ph22 gpio47_pb14 gpio59_pi4 gpio70_pi15
gpio12_pc18 gpio24_ph11 gpio36_ph23 gpio48_pb15 gpio5_pg4 gpio71_pi16
gpio13_pc19 gpio25_ph12 gpio37_pb3 gpio49_pb16 gpio60_pi5 gpio72_pi17
gpio14_pc20 gpio26_ph13 gpio38_pb4 gpio4_pg3 gpio61_pi6 gpio73_pi18
gpio15_pc21 gpio27_ph14 gpio39_pb5 gpio50_pb17 gpio62_pi7 gpio74_pi19
gpio16_pc22 gpio28_ph15 gpio3_pg2 gpio51_ph24 gpio63_pi8 gpio75_pi20
gpio17_pc23 gpio29_ph16 gpio40_pb6 gpio52_ph25 gpio64_pi9 gpio7_pg6
gpio18_pc24 gpio2_pg1 gpio41_pb7 gpio53_ph26 gpio65_pi10 gpio8_pg7
gpio19_ph0 gpio30_ph17 gpio42_pb8 gpio54_ph27 gpio66_pi11 gpio9_pg8
gpio1_pg0 gpio31_ph18 gpio43_pb10 gpio55_pi0 gpio67_pi12 gpiochip1
gpio20_ph2 gpio32_ph19 gpio44_pb11 gpio56_pi1 gpio68_pi13

===Add Voice to your OLinuXino project===

[http://olimex.wordpress.com/2013/10/03/make-things-talk-with-olinuxino/ Installation of Festival on OLinuXino]
 

== How To? ==
===How to generate boot-able SD-card Debian Linux image for A20-OLinuXino-LIME2? ===

Build instructions and required files for the latest Debian images: [https://github.com/OLIMEX/OLINUXINO/tree/master/SOFTWARE/A20 instructions and files at the GitHub page]

Note that Linux-Sunxi Kernel is a work-in-progress, this means you can try the current stage/sunxi-x.x branch but if something is broken and doesn't work just revert to the git tags we give in the blog and they would work for sure.

[https://github.com/linux-sunxi/u-boot-sunxi/wiki Sunxi u-boot loader] The linux-sunxi git page contains a lot of sources for all Olimex Allwinner boards.

===How to connect a display and adjust the video output resolution?===
There is a separate article on the subject: [[how to connect display to a Lime board]]
 

=== Is it possible to boot Debian from NAND? Do you provide such image?===

Yes, it is possible. Use the latest Debian Jessie image and write "nandinstall". More information can be found in this wiki article: [[How_to_install_Debian_to_NAND| installing Debian Jessie to the 4GB NAND memory]]

There are other people who are also successful in booting Debian from the NAND. Make sure to check on the forum. Make sure to check the number of very good and optimized A20-OLinuXino Debian images by Igor Pečovnik. There are also his instructions for NAND installation of Debian: [http://www.armbian.com/download/ link to his web-site]

===How to detect and enable the Ethernet controller (if it is disabled by default)? ===

Note: in the previous Debian releases the Ethernet was auto-detected and initialized during boot BUT this was causing big delays in the start-up of the board if you didn't want to use Ethernet or if there wasn't Ethernet cable connected.

You can enable it by following these two steps:

1. To check under what name the LAN is associated write "ifconfig –a"

2. If, for example, it is under eth0 name, then write: "dhclient eth0"

This should enable the Ethernet and then SSH would also be available.

===How to download new Android image to the NAND memory of my A20 board?===

Follow these steps to download the image to the NAND memory:

*1. Install and run PhoenixSuit (can be found here: [https://drive.google.com/file/d/0BwplT87k9SCgaTFTZnVST05ONzA/view?usp=sharing download from google drive]).

*2. Go to firmware tab of the program and point to a valid Android image (the latest official one may also be downloaded above).

*3. Disconnect the power supply and USB cable from the A20 board.

*4. Press and hold RECOVERY button, apply power supply 5V, release RECOVERY button.

*5. Connect USB cable to the mini USB connector.

*6. You will be asked for drivers for the bootloader. Navigate to the folder where you extracted the PhoenixSuit and install the drivers from the respective executables (or manually point the installer to the drivers folder in the PhoenixSuit installation path).

*7. PhoenixSuit will detect the board and would ask for the method of writing the image. Choose method of writing the image and confirm your wish to write the image.

*8. Wait till upgrade succeeds

Note that it is not recommended to have your mini USB connected to an external USB hub. This might cause delays and might distort the signal levels. Always test with the USB connected straight to the USB ports of your computer.

===How to generate Arch Linux image?===

Recent forum post by user progmetalbg here: [https://www.olimex.com/forum/index.php?topic=4261.0| at Olimex forums]

[http://alarma20.wordpress.com/2013/09/13/howto-build-arch-linux-arm-for-a20-olinuxino-micro/ Older step by step instructions on how to build Arch Linux image for another A20 board]

===How do I write the official Android image to a micro SD card for my A20 board?===
A: First download one of the official Android images, which might be found in the Android section above.

Make sure that the download link you visit clearly indicates that the image is suitable for the microSD card since there are images suitable for NAND memory also. The images suitable for the microSD memory and those suitable for NAND card are different. However, the upload method is almost identical – using PhoenixSuit.

There are two types of Android images for microSD card that we usually provide and each of them has to be downloaded to a microSD card using a different method. The image provided for microSD card is either the native Android image that can be downloaded to the card via a software tool like PhoenixSuit (through the board) or an image taken from an already prepared microSD card that requires to simply write the image (through a microSD card reader).

'''It is more likely that you have an Android image that requires a simple copy to a card. If that is the case you can follow the exact steps as for Linux (e.g. using "Win32 Disk Imager" or "dd" command).'''

In order to prepare a microSD card with a native Android you will need a software tool called PhoenixSuit and then:

• Install and run PhoenixSuit (can be found here: [https://drive.google.com/file/d/0BwplT87k9SCgaTFTZnVST05ONzA/view?usp=sharing download from google drive])

• Go to the firmware tab of the program and point to a valid Android image (note that the
images on Gdrive are compressed and you have to extract them to .img files to be able write
them with PhoenixSuit)

• Disconnect the power supply and USB cable from the A20 board. Put an SD card in micro SD
holder. We recommend either a 4GB or a 8GB class 10 card.

• Press and hold RECOVERY button, apply power supply 5V, release RECOVERY button.

• Connect USB cable to the mini USB connector.

• You will be asked for drivers for the boot-loader. Navigate to the folder where you extracted the PhoenixSuit and install the drivers from the respective executables (or manually point the installer to the drivers folder in the PhoenixSuit installation path).

• PhoenixSuit will detect the board and would ask for the method of writing the image. Choose
method of writing the image and confirm your wish to write the image.

• Wait till upgrade succeeds

Note that it is not recommended to have your mini USB connected to an external USB hub. This
might cause delays and might distort the signal levels. Always test with the USB connected straight to the USB ports of your computer.

Important: When Android runs for very first time it takes several minutes to initialize all files and buffers please do not cut the power supply during this process! Also when fresh image is installed fast boot may be disabled, which means that when you apply power supply after few seconds Android will go in sleep mode and you have to press POWER button to start it, you can change to fast boot when you power off there is dialog box asking you if you want next boot to be fast boot, you have to check this box before you power off. Also note that you must do touch screen calibration when you run Android for very first time which might require a mouse.

===I don't have neither serial cable, nor HDMI monitor. I also can't access the local Ethernet network. Can I somehow access the board anyway?===

The latest official Debian Linux image allows the use the USB_OTG connector for SSH connection without the need of a LAN cable or a serial cable. You can use a mini USB cable connected between your host PC and the on-board mini USB connector. For connection convenience there is a DHCP server running specifically for USB0 interface. The DHCP server should give IP address to the new USB0 interface of your host PC so you can make SSH connection from your PC to the default board IP address of the USB0 interface – 192.168.2.1.

You can connect to the board using a mini USB cable and an SSH client (if you use Windows you might use "puTTY", for example) at address 192.168.2.1.

For Windows operating system - upon connection, the board should show up in "Windows Device Manager" as "RNDIS Ethernet Gadget". You might be asked to install a driver. The drivers can be found online as "RNDIS driver" (Remote Network Driver Interface Specification). The drivers are provided by Microsoft and they should be available for every Windows distribution - refer to the respective files and articles provided by Microsoft on how to install the required drivers.

===How to edit board configurations and definitions in the official Debian Linux? ===

Do you want a custom video resolution output? Do you need a different port definition? Do you need to change the hardware defitions of the board?

You would need to edit the board's script.bin/script.fex file. How to do it is described in another separate article: [[how to edit board configurations and definitions in the official Debian Linux]].

===How to add STK1160 video capture driver support in Kernel 3.4===

[https://www.olimex.com/wiki/STK1160-howto-linux-sunxi-3_4 STK1160] driver backport by Dimitar Tomov
[[Main_Page]]

A20-OLinuXino-LIME2

2024-09-30T07:57:17Z

LubOlimex: /* Official Images from OLIMEX */

[[File:A20-OLinuXino-LIME2.jpg|600px]]

A20-OLinuXino-LIME2 looks similar to both [[A20-OLinuXino-LIME]] and [[A10-OLinuXino-LIME]]. The major differences between A20-OLinuXino-LIME2 and A20-OLinuXino-LIME are:

*LIME2 has gigabit Ethernet (GbE), compared to the standard 100Mb Ethernet of the LIME
*LIME2 design provides double the RAM memory, compared to the LIME design (1024 vs 512)
*Much better routing of DDR3 memory.
*Increased the number of layers from 6 in LIME to 8 in LIME2
*Corrected pinout of the LCD and GPIO connectors (shields designed for the LIME layout are not compatible with the LIME2 layout)

The A10 and the A20 processors are pin-to-pin compatible. Because of the processor, software-wise the board is closer to [[A20-OLinuXino-LIME]] than to the [[A10-OLinuXino-LIME]]. This resemblance to other designs definitely might speed the development on the board - a lot of software written for A20-OLinuXino-LIME might work out-of-the-box with A20-OLinuXino-LIME2. Additionally, pinout tables, GPIO maps, etc released for A20-OLinuXino-LIME would apply to A20-OLinuXino-LIME2 (except for the 0.05" step connectors - LCD display and all the GPIOs connectors, which have a different layout compared to both A20-OLinuXino-LIME and A10-OLinuXino-LIME).

A20-OLinuXino-LIME2 features:
*A20 Cortex-A7 dual-core ARM Cortex-A7 CPU and dual-core Mali 400 GPU
*'''1GB DDR3 RAM memory'''
*'''1 gigabit native Ethernet'''
*optional 4GB NAND FLASH memory
*SATA connector with 5V SATA power jack
*HDMI FullHD 1080p
*2x USB Low-Full-High-Speed hosts with power control and current limiter
*USB-OTG with power control and current limiter
*LiPo Battery connector with battery-charging capabilities
*LCD connector compatible with with 4.3", 7.0", 10.1" LCD modules from Olimex
*160 GPIOs on three GPIO connectors
*MicroSD card connector
*DEBUG-UART connector for console debug with USB-SERIAL-CABLE-F
*status LED
*Battery charge status LED
*Power LED
*2KB EEPROM for MAC address storage and more
*2 BUTTONS with ANDROID functionality + RESET button
*2 mount holes
*5V input power supply, noise immune design
*PCB dimensions: 84 x 60 mm

== Official Images from OLIMEX ==

In this chapter you would find links to FTP location with the official Debian and Android images. The images in this chapter were compiled by Olimex. They are recommended for beginners and first time users since they include full hardware support. If you are experienced Linux professional you might find useful our build instructions also published here.

The downloaded file xxxx.7z is an archive of xxx.img file. In order to write the image on SD card you have to extract the xxx.7z file.

*For Windows: use 7zip and then use Win32DiskImager.exe (http://sourceforge.net/projects/win32diskimager/) to write the image

*For Linux: use p7zip package. If you don't have 7zip installed first install it 

#apt-get install p7zip
Copy a20_Lime2_debian_second_release.7z file in your directory and unzip the archive with
#7za e a20_Lime2_debian_second_release.7z
where a20_Lime2_debian_second_release.7z
The output should be a new 4GB file with extension img
Put 4GB SD card in your card reader and type
# ls /dev/sd
Then press two times <TAB> you will see a list of your sd devices like sda sdb sdc note that some of these devices may be your hard disk so make sure you know which one is your sd card before you proceed as you can damage your HDD if you choose the wrong sd-device. You can do this by unplugging your sd card reader and identify which "sd" devices remove from the list.
Once you know which device is your sdcard like sda use this text instead of the sdX name in the references below:
#dd if=a20_Lime2_debian_second_release.img of=/dev/sdX

The Debian Linux image is 4GB and the file system can be extended to suit a bigger card. Use the following three commands to execute a script that would use all the free space of your card:

sudo su
./resize_sd.sh /dev/mmcblk0 2
reboot

=== Linux images ===

These official Debian images should be downloaded to a microSD card. Older sunxi images can be found as direct downloads at our FTP. You can install the Debian to the NAND or the eMMC of your board (if it comes with one). Information on booting Debian from the NAND might be found in these wiki articles: [[how to install Debian to NAND]]; [[how to install Debian to eMMC]]. Download locations for the official images might be found below:

'''ALWAYS FIRST TEST WITH LATEST OFFICIAL IMAGE, NEWER HARDWARE REVISIONS OF THE BOARD MIGHT NOT WORK WITH OLDER IMAGES!!!'''

----

'''Latest stable official images - Debian 8 (Jessie)''' '''Both images are suitable for the standard version A20-OLinuXino-LIME2. However A20-OLinuXino-LIME2-n4GB and A20-OLinuXino-LIME2-n8GB have different image compared to A20-OLinuXino-LIME2-e4GB''':'''

FTP location for official Debian Jessie release #13 for A20-OLinuXino-LIME2, A20-OLinuXino-LIME2-n4GB, and A20-OLinuXino-LIME2-n8GB (not suitable for boards with eMMC flash): [https://ftp.olimex.com/Allwinner_Images/A20-OLinuXino-LIME2/Debian/sd/a20-lime2_mainline_uboot_sunxi_kernel_3.4.103_jessie_NAND_rel_13.img.7z A20-OLinuXino-LIME2 Debian Jessie with kernel 3.4.103+ release 13]

FTP location for official Debian Jessie release #16 for A20-OLinuXino-LIME2, A20-OLinuXino-LIME2-e4GB (not suitable for boards with NAND flash): [https://ftp.olimex.com/Allwinner_Images/A20-OLinuXino-LIME2/Debian/sd/a20-lime2_mainline_uboot_sunxi_kernel_3.4.103_jessie_eMMC_rel_16.zip A20 lime2 mainline uboot sunxi kernel 3.4.103 jessie eMMC rel 16]

Image description and typical interfacing: [https://github.com/OLIMEX/OLINUXINO/blob/master/SOFTWARE/A20/A20-build-3.4.103-release-7/USAGE-AND-COMMON-PRACTICEs-A20-Olimex_kernel_3.4.103%2B_Jessie_rel_3.txt description and basic usage of different peripherals at at the GitHub page]

Image build instructions and required files for latest Debian Jessie release might be found here: [https://github.com/OLIMEX/OLINUXINO/blob/master/SOFTWARE/A20/A20-build-3.4.103-release-8/BUILD_DESCRIPTION_A20_Olimex_kernel_3.4.103%2B_Jessie_rel_8.txt build instructions and required files at the GitHub page]

You can find some older releases and older build instructions (older image revisions might be used as a reference, for testing purposes, or if you own old hardware revision of the board) at the following article: [[A20-OLinuXino-LIME2-older-releases|older releases and older build instructions]]

----

Note: the A20-LIME2-DEBIAN-SD card which we have in our web store contains the image suitable for board with no flash or board with NAND memory on a 8GB Class10 fast microSD card. The A20-LIME2-eMMC-DEBIAN-SD contains the image suitable for boards with extra eMMC memory. If you want to use our images, please, use card with speed Class10 or higher. Else the Linux performance would be very slow.

Note: in the previous Debian releases the Ethernet was auto-detected and initialized during boot BUT this was causing big delays in the start-up of the board if you didn't want to use Ethernet or if there wasn't Ethernet cable connected.

You can enable it by following these two steps:

1. To check under what name the LAN is associated write "ifconfig –a"

2. If, for example, it is under eth0 name, then write: "dhclient eth0"

This should enable the Ethernet and then SSH would also be available.

=== Android images ===

Torrents of official Android releases are below. Please read description of the image carefully.

'''Newest official release (recommended):'''

For the NAND flash memory:

FTP location of Android 4.2.2 release 1 for NAND memory (with HDMI and 7 inch 800x480 support - LCD-OLinuXino-7TS): [https://ftp.olimex.com/Allwinner_Images/A20-OLinuXino-LIME2/Android/nand/A20_Lime2_android_4_22_NAND_LCD7_HDMI_release1.img A20-OLinuXino-Lime2 Android for NAND with HDMI and 7 inch display support]

FTP location of Android 4.2.2 release 1 for NAND memory (with HDMI and 10 inch 1024x600 support - LCD-OLinuXino-10TS): [https://ftp.olimex.com/Allwinner_Images/A20-OLinuXino-LIME2/Android/nand/A20_Lime2_android_4_22_NAND_LCD10_HDMI_release1.img A20-OLinuXino-Lime2 Android for NAND with HDMI and 10 inch display support]

For microSD card:

FTP location of Android 4.2.2 release 2 for 8GB microSD card (with HDMI and 800x480 support): [https://ftp.olimex.com/Allwinner_Images/A20-OLinuXino-LIME2/Android/sd/A20_Lime2_Android_4.22_SD_card_LCD_800x480_HDMI_8GB_release_2.img.7z A20-OLinuXino-Lime2 Android for 8GB microSD card with HDMI and 7 inch display support]

FTP location of Android 4.2.2 release 2 for 16GB microSD card (with HDMI and 1024x600 support):
[https://ftp.olimex.com/Allwinner_Images/A20-OLinuXino-LIME2/Android/sd/A20-LIME2-ANDROID-SD-expanded-16GB_LCD10_cfg0_0.zip A20-OLinuXino-Lime2 Android for 16GB microSD card with HDMI and 10 inch display support, this image requires loading via PhoenixSuit, refer to the FAQ section at the end of this page]

Build instructions and source files for the official Android images for A20 boards in this repository: https://github.com/hehopmajieh/olinuxino_configs

== Notable unofficial images ==

Below you would find locations to images released by the community. These are not officially supported by Olimex, however, some of these releases are pretty good and worth a try:

*A number of very good and optimized A20-OLinuXino-LIME2 Armbian images: [https://www.armbian.com/olimex-lime-2/ link to LIME2 article at Armbian's web-site]

*A20-OLinuXino-LIME2 is supported by openSUSE Factory, installation instructions might be found here: [https://en.opensuse.org/HCL:A20-OLinuXIno-LIME2 openSUSE wiki link]

*A20-OLinuXino-LIME2 is recognized by the Devuan community and there are official releases here might be found here: [https://files.devuan.org/devuan_ascii/embedded/ Devuan list of files link]
 

== Documents ==

===A20-OLinuXino-LIME2 user's manual===
[https://www.olimex.com/Products/OLinuXino/A20/A20-OLinuXIno-LIME2/resources/A20-OLinuXino-LIME2-UM.pdf User's manual for A20-OLinuXino-LIME2 and A20-OLinuXino-LIME2-4GB]

=== A20 Brief ===
[https://github.com/OLIMEX/OLINUXINO/blob/master/HARDWARE/A20-PDFs/A20%20brief%2020130407.pdf A20 brief]

=== A20 Datasheet ===

[https://github.com/OLIMEX/OLINUXINO/blob/master/HARDWARE/A20-PDFs/A20%20Datasheet%20v1.0%2020130227.pdf A20 Datasheet]

=== A20 User Manual ===

[https://github.com/OLIMEX/OLINUXINO/blob/master/HARDWARE/A20-PDFs/A20%20User%20Manual%202013-03-22.pdf A20 user's manual]

== Hardware ==

===LIME2 shield templates===
[https://github.com/OLIMEX/OLINUXINO/tree/master/HARDWARE/A20-OLinuXino-LIME2 Eagle and KiCAD shield templates for LIME2]

===GPIO description===

[https://github.com/OLIMEX/OLINUXINO/blob/master/HARDWARE/A20-OLinuXino-LIME2/3.%20Templates%20and%20more/A20_LIME2_GPIOs.pdf A20-OLinuXino-LIME2 GPIO description]

A template that might be used to create custom shields or own adapters might be downloaded for Eagle or KiCad at the GitHub here: [https://github.com/OLIMEX/OLINUXINO/tree/master/HARDWARE/A20-OLinuXino-LIME2 shield template]

===Power supply and consumption===

A20-OLinuXino-LIME2 requires 5V regulated power supply external source. regulated means that the power supply adapter should provide exactly 5V no matter loaded or unloaded (some cheap wallwart adapters are not regulated and under no load their power supply may be higher than 5V although marked as 5V power supply, please measure with voltmeter if your power supply provide 5V as if you connect more than 5V to LIME it will be damaged!!!)

The power jack is standard [https://www.olimex.com/wiki/PWRJACK OLIMEX power jack].

A20-OLinuXino-LIME can be powered from three sources:
*+5VDC voltage applied PWR jack
*+3.7V from LiPo re-chargable battery connected to LiPo board connector
*+5V applied to USB-OTG connector

Power consumption is as follows:
*LiPo 3.7V power battery: 1.2W
*+5VDC input power: 1.3W

Comparison table of power consumption might be found at the following [https://www.olimex.com/Products/OLinuXino/_resources/OLinuXino-Consumption.pdf link].

LiPo battery allow backup power supply when main power is interrupted. A20-OLinuXino-LIME2 has power managment IC which charge the battery when main power is present, when power is interrupted the LiPo battery automatically provide backup power supply. Step-up converter prvide 5V for the USB peripherials too. For LiPo batteries we recommend these:
*[https://www.olimex.com/Products/Power/BATTERY-LIPO1400mAh/ 1400mAh]
*[https://www.olimex.com/Products/Power/BATTERY-LIPO3000mAh/ 3000mAh]
*[https://www.olimex.com/Products/Power/BATTERY-LIPO4400mAh/ 4400mAh]
*[https://www.olimex.com/Products/Power/BATTERY-LIPO6600mAh/ 6600mAh]
 

===Board dimensions===

A20-OLinuXino-LIME2 basic dimensions in mils: 3305.5 x 2347.0

Some additional measures might be seen in the image of A10-OLinuXino-LIME which has almost identical layout. It is available as .png here:
[https://www.olimex.com/Products/OLinuXino/A10/A10-OLinuXino-LIME/resources/A10-LIME-dimensions.png link]

===CAD files===

A20-OLinuXino-LIME2 is an Open Source Hardware, CAD files are available at [https://github.com/OLIMEX/OLINUXINO/tree/master/HARDWARE/A20-OLinuXino-LIME2 GitHub]

The CAD product used to design OLinuXino is Eagle and you can download evaluation free version from their [http://www.cadsoftusa.com/ web].

===Board Layout===

[[File:A20-OLinuXino-LIME2_top_naming_extras.jpg|650px]]

[[File:A20-OLinuXino-LIME2 bottom naming.jpg|650px]]

== Software ==

===Linux Commands===

[[Linux-Commands]] Brief Linux Command reference

===Python library for GPIO, I2C and SPI control===

The Debian Linux Python package for A20-OLinuXino-LIME2 is called pyA20Lime2. It makes the access to GPIO, I2C and SPI considerably easier. It is installed in the default Debian image. More information and examples on how it can be used might be found here:

[https://pypi.python.org/pypi/pyA20Lime2 Link to pyA20Lime2 package at python.org]

===GPIO under Linux===

GPIOs are located in /sys/class/gpio directory. Note that first you have to export GPIOs. For example:

add gpioPH2

root@A20:~# echo 20 > /sys/class/gpio/export

make PH2 output

root@A20:~# echo out > //sys/class/gpio/gpio20_ph2/direction

turn on onboard LED(connected to PH2)

root@A20:~# echo 1 > /sys/class/gpio/gpio20_ph2/value

turn off onboard LED(connected to PH2)

root@A20:~# echo 0 > /sys/class/gpio/gpio20_ph2/value

Full list with supported GPIOs is:

gpio21_ph7 gpio33_ph20 gpio45_pb12 gpio57_pi2 gpio69_pi14
gpio10_pg11 gpio22_ph9 gpio34_ph21 gpio46_pb13 gpio58_pi3 gpio6_pg5
gpio11_pc3 gpio23_ph10 gpio35_ph22 gpio47_pb14 gpio59_pi4 gpio70_pi15
gpio12_pc18 gpio24_ph11 gpio36_ph23 gpio48_pb15 gpio5_pg4 gpio71_pi16
gpio13_pc19 gpio25_ph12 gpio37_pb3 gpio49_pb16 gpio60_pi5 gpio72_pi17
gpio14_pc20 gpio26_ph13 gpio38_pb4 gpio4_pg3 gpio61_pi6 gpio73_pi18
gpio15_pc21 gpio27_ph14 gpio39_pb5 gpio50_pb17 gpio62_pi7 gpio74_pi19
gpio16_pc22 gpio28_ph15 gpio3_pg2 gpio51_ph24 gpio63_pi8 gpio75_pi20
gpio17_pc23 gpio29_ph16 gpio40_pb6 gpio52_ph25 gpio64_pi9 gpio7_pg6
gpio18_pc24 gpio2_pg1 gpio41_pb7 gpio53_ph26 gpio65_pi10 gpio8_pg7
gpio19_ph0 gpio30_ph17 gpio42_pb8 gpio54_ph27 gpio66_pi11 gpio9_pg8
gpio1_pg0 gpio31_ph18 gpio43_pb10 gpio55_pi0 gpio67_pi12 gpiochip1
gpio20_ph2 gpio32_ph19 gpio44_pb11 gpio56_pi1 gpio68_pi13

===Add Voice to your OLinuXino project===

[http://olimex.wordpress.com/2013/10/03/make-things-talk-with-olinuxino/ Installation of Festival on OLinuXino]
 

== How To? ==
===How to generate boot-able SD-card Debian Linux image for A20-OLinuXino-LIME2? ===

Build instructions and required files for the latest Debian images: [https://github.com/OLIMEX/OLINUXINO/tree/master/SOFTWARE/A20 instructions and files at the GitHub page]

Note that Linux-Sunxi Kernel is a work-in-progress, this means you can try the current stage/sunxi-x.x branch but if something is broken and doesn't work just revert to the git tags we give in the blog and they would work for sure.

[https://github.com/linux-sunxi/u-boot-sunxi/wiki Sunxi u-boot loader] The linux-sunxi git page contains a lot of sources for all Olimex Allwinner boards.

===How to connect a display and adjust the video output resolution?===
There is a separate article on the subject: [[how to connect display to a Lime board]]
 

=== Is it possible to boot Debian from NAND? Do you provide such image?===

Yes, it is possible. Use the latest Debian Jessie image and write "nandinstall". More information can be found in this wiki article: [[How_to_install_Debian_to_NAND| installing Debian Jessie to the 4GB NAND memory]]

There are other people who are also successful in booting Debian from the NAND. Make sure to check on the forum. Make sure to check the number of very good and optimized A20-OLinuXino Debian images by Igor Pečovnik. There are also his instructions for NAND installation of Debian: [http://www.armbian.com/download/ link to his web-site]

===How to detect and enable the Ethernet controller (if it is disabled by default)? ===

Note: in the previous Debian releases the Ethernet was auto-detected and initialized during boot BUT this was causing big delays in the start-up of the board if you didn't want to use Ethernet or if there wasn't Ethernet cable connected.

You can enable it by following these two steps:

1. To check under what name the LAN is associated write "ifconfig –a"

2. If, for example, it is under eth0 name, then write: "dhclient eth0"

This should enable the Ethernet and then SSH would also be available.

===How to download new Android image to the NAND memory of my A20 board?===

Follow these steps to download the image to the NAND memory:

*1. Install and run PhoenixSuit (can be found here: [https://drive.google.com/file/d/0BwplT87k9SCgaTFTZnVST05ONzA/view?usp=sharing download from google drive]).

*2. Go to firmware tab of the program and point to a valid Android image (the latest official one may also be downloaded above).

*3. Disconnect the power supply and USB cable from the A20 board.

*4. Press and hold RECOVERY button, apply power supply 5V, release RECOVERY button.

*5. Connect USB cable to the mini USB connector.

*6. You will be asked for drivers for the bootloader. Navigate to the folder where you extracted the PhoenixSuit and install the drivers from the respective executables (or manually point the installer to the drivers folder in the PhoenixSuit installation path).

*7. PhoenixSuit will detect the board and would ask for the method of writing the image. Choose method of writing the image and confirm your wish to write the image.

*8. Wait till upgrade succeeds

Note that it is not recommended to have your mini USB connected to an external USB hub. This might cause delays and might distort the signal levels. Always test with the USB connected straight to the USB ports of your computer.

===How to generate Arch Linux image?===

Recent forum post by user progmetalbg here: [https://www.olimex.com/forum/index.php?topic=4261.0| at Olimex forums]

[http://alarma20.wordpress.com/2013/09/13/howto-build-arch-linux-arm-for-a20-olinuxino-micro/ Older step by step instructions on how to build Arch Linux image for another A20 board]

===How do I write the official Android image to a micro SD card for my A20 board?===
A: First download one of the official Android images, which might be found in the Android section above.

Make sure that the download link you visit clearly indicates that the image is suitable for the microSD card since there are images suitable for NAND memory also. The images suitable for the microSD memory and those suitable for NAND card are different. However, the upload method is almost identical – using PhoenixSuit.

There are two types of Android images for microSD card that we usually provide and each of them has to be downloaded to a microSD card using a different method. The image provided for microSD card is either the native Android image that can be downloaded to the card via a software tool like PhoenixSuit (through the board) or an image taken from an already prepared microSD card that requires to simply write the image (through a microSD card reader).

'''It is more likely that you have an Android image that requires a simple copy to a card. If that is the case you can follow the exact steps as for Linux (e.g. using "Win32 Disk Imager" or "dd" command).'''

In order to prepare a microSD card with a native Android you will need a software tool called PhoenixSuit and then:

• Install and run PhoenixSuit (can be found here: [https://drive.google.com/file/d/0BwplT87k9SCgaTFTZnVST05ONzA/view?usp=sharing download from google drive])

• Go to the firmware tab of the program and point to a valid Android image (note that the
images on Gdrive are compressed and you have to extract them to .img files to be able write
them with PhoenixSuit)

• Disconnect the power supply and USB cable from the A20 board. Put an SD card in micro SD
holder. We recommend either a 4GB or a 8GB class 10 card.

• Press and hold RECOVERY button, apply power supply 5V, release RECOVERY button.

• Connect USB cable to the mini USB connector.

• You will be asked for drivers for the boot-loader. Navigate to the folder where you extracted the PhoenixSuit and install the drivers from the respective executables (or manually point the installer to the drivers folder in the PhoenixSuit installation path).

• PhoenixSuit will detect the board and would ask for the method of writing the image. Choose
method of writing the image and confirm your wish to write the image.

• Wait till upgrade succeeds

Note that it is not recommended to have your mini USB connected to an external USB hub. This
might cause delays and might distort the signal levels. Always test with the USB connected straight to the USB ports of your computer.

Important: When Android runs for very first time it takes several minutes to initialize all files and buffers please do not cut the power supply during this process! Also when fresh image is installed fast boot may be disabled, which means that when you apply power supply after few seconds Android will go in sleep mode and you have to press POWER button to start it, you can change to fast boot when you power off there is dialog box asking you if you want next boot to be fast boot, you have to check this box before you power off. Also note that you must do touch screen calibration when you run Android for very first time which might require a mouse.

===I don't have neither serial cable, nor HDMI monitor. I also can't access the local Ethernet network. Can I somehow access the board anyway?===

The latest official Debian Linux image allows the use the USB_OTG connector for SSH connection without the need of a LAN cable or a serial cable. You can use a mini USB cable connected between your host PC and the on-board mini USB connector. For connection convenience there is a DHCP server running specifically for USB0 interface. The DHCP server should give IP address to the new USB0 interface of your host PC so you can make SSH connection from your PC to the default board IP address of the USB0 interface – 192.168.2.1.

You can connect to the board using a mini USB cable and an SSH client (if you use Windows you might use "puTTY", for example) at address 192.168.2.1.

For Windows operating system - upon connection, the board should show up in "Windows Device Manager" as "RNDIS Ethernet Gadget". You might be asked to install a driver. The drivers can be found online as "RNDIS driver" (Remote Network Driver Interface Specification). The drivers are provided by Microsoft and they should be available for every Windows distribution - refer to the respective files and articles provided by Microsoft on how to install the required drivers.

===How to edit board configurations and definitions in the official Debian Linux? ===

Do you want a custom video resolution output? Do you need a different port definition? Do you need to change the hardware defitions of the board?

You would need to edit the board's script.bin/script.fex file. How to do it is described in another separate article: [[how to edit board configurations and definitions in the official Debian Linux]].

===How to add STK1160 video capture driver support in Kernel 3.4===

[https://www.olimex.com/wiki/STK1160-howto-linux-sunxi-3_4 STK1160] driver backport by Dimitar Tomov
[[Main_Page]]

A20-OLinuXino-LIME2

2024-09-30T07:56:55Z

LubOlimex: /* Android images */

[[File:A20-OLinuXino-LIME2.jpg|600px]]

A20-OLinuXino-LIME2 looks similar to both [[A20-OLinuXino-LIME]] and [[A10-OLinuXino-LIME]]. The major differences between A20-OLinuXino-LIME2 and A20-OLinuXino-LIME are:

*LIME2 has gigabit Ethernet (GbE), compared to the standard 100Mb Ethernet of the LIME
*LIME2 design provides double the RAM memory, compared to the LIME design (1024 vs 512)
*Much better routing of DDR3 memory.
*Increased the number of layers from 6 in LIME to 8 in LIME2
*Corrected pinout of the LCD and GPIO connectors (shields designed for the LIME layout are not compatible with the LIME2 layout)

The A10 and the A20 processors are pin-to-pin compatible. Because of the processor, software-wise the board is closer to [[A20-OLinuXino-LIME]] than to the [[A10-OLinuXino-LIME]]. This resemblance to other designs definitely might speed the development on the board - a lot of software written for A20-OLinuXino-LIME might work out-of-the-box with A20-OLinuXino-LIME2. Additionally, pinout tables, GPIO maps, etc released for A20-OLinuXino-LIME would apply to A20-OLinuXino-LIME2 (except for the 0.05" step connectors - LCD display and all the GPIOs connectors, which have a different layout compared to both A20-OLinuXino-LIME and A10-OLinuXino-LIME).

A20-OLinuXino-LIME2 features:
*A20 Cortex-A7 dual-core ARM Cortex-A7 CPU and dual-core Mali 400 GPU
*'''1GB DDR3 RAM memory'''
*'''1 gigabit native Ethernet'''
*optional 4GB NAND FLASH memory
*SATA connector with 5V SATA power jack
*HDMI FullHD 1080p
*2x USB Low-Full-High-Speed hosts with power control and current limiter
*USB-OTG with power control and current limiter
*LiPo Battery connector with battery-charging capabilities
*LCD connector compatible with with 4.3", 7.0", 10.1" LCD modules from Olimex
*160 GPIOs on three GPIO connectors
*MicroSD card connector
*DEBUG-UART connector for console debug with USB-SERIAL-CABLE-F
*status LED
*Battery charge status LED
*Power LED
*2KB EEPROM for MAC address storage and more
*2 BUTTONS with ANDROID functionality + RESET button
*2 mount holes
*5V input power supply, noise immune design
*PCB dimensions: 84 x 60 mm

== Official Images from OLIMEX ==

In this chapter you would find links to torrents with the official Debian and Android images. The images in this chapter were compiled by Olimex. They are recommended for beginners and first time users since they include full hardware support. If you are experienced Linux professional you might find useful our build instructions also published here.

The downloaded file xxxx.7z is an archive of xxx.img file. In order to write the image on SD card you have to extract the xxx.7z file.

*For Windows: use 7zip and then use Win32DiskImager.exe (http://sourceforge.net/projects/win32diskimager/) to write the image

*For Linux: use p7zip package. If you don't have 7zip installed first install it 

#apt-get install p7zip
Copy a20_Lime2_debian_second_release.7z file in your directory and unzip the archive with
#7za e a20_Lime2_debian_second_release.7z
where a20_Lime2_debian_second_release.7z
The output should be a new 4GB file with extension img
Put 4GB SD card in your card reader and type
# ls /dev/sd
Then press two times <TAB> you will see a list of your sd devices like sda sdb sdc note that some of these devices may be your hard disk so make sure you know which one is your sd card before you proceed as you can damage your HDD if you choose the wrong sd-device. You can do this by unplugging your sd card reader and identify which "sd" devices remove from the list.
Once you know which device is your sdcard like sda use this text instead of the sdX name in the references below:
#dd if=a20_Lime2_debian_second_release.img of=/dev/sdX

The Debian Linux image is 4GB and the file system can be extended to suit a bigger card. Use the following three commands to execute a script that would use all the free space of your card:

sudo su
./resize_sd.sh /dev/mmcblk0 2
reboot

=== Linux images ===

These official Debian images should be downloaded to a microSD card. Older sunxi images can be found as direct downloads at our FTP. You can install the Debian to the NAND or the eMMC of your board (if it comes with one). Information on booting Debian from the NAND might be found in these wiki articles: [[how to install Debian to NAND]]; [[how to install Debian to eMMC]]. Download locations for the official images might be found below:

'''ALWAYS FIRST TEST WITH LATEST OFFICIAL IMAGE, NEWER HARDWARE REVISIONS OF THE BOARD MIGHT NOT WORK WITH OLDER IMAGES!!!'''

----

'''Latest stable official images - Debian 8 (Jessie)''' '''Both images are suitable for the standard version A20-OLinuXino-LIME2. However A20-OLinuXino-LIME2-n4GB and A20-OLinuXino-LIME2-n8GB have different image compared to A20-OLinuXino-LIME2-e4GB''':'''

FTP location for official Debian Jessie release #13 for A20-OLinuXino-LIME2, A20-OLinuXino-LIME2-n4GB, and A20-OLinuXino-LIME2-n8GB (not suitable for boards with eMMC flash): [https://ftp.olimex.com/Allwinner_Images/A20-OLinuXino-LIME2/Debian/sd/a20-lime2_mainline_uboot_sunxi_kernel_3.4.103_jessie_NAND_rel_13.img.7z A20-OLinuXino-LIME2 Debian Jessie with kernel 3.4.103+ release 13]

FTP location for official Debian Jessie release #16 for A20-OLinuXino-LIME2, A20-OLinuXino-LIME2-e4GB (not suitable for boards with NAND flash): [https://ftp.olimex.com/Allwinner_Images/A20-OLinuXino-LIME2/Debian/sd/a20-lime2_mainline_uboot_sunxi_kernel_3.4.103_jessie_eMMC_rel_16.zip A20 lime2 mainline uboot sunxi kernel 3.4.103 jessie eMMC rel 16]

Image description and typical interfacing: [https://github.com/OLIMEX/OLINUXINO/blob/master/SOFTWARE/A20/A20-build-3.4.103-release-7/USAGE-AND-COMMON-PRACTICEs-A20-Olimex_kernel_3.4.103%2B_Jessie_rel_3.txt description and basic usage of different peripherals at at the GitHub page]

Image build instructions and required files for latest Debian Jessie release might be found here: [https://github.com/OLIMEX/OLINUXINO/blob/master/SOFTWARE/A20/A20-build-3.4.103-release-8/BUILD_DESCRIPTION_A20_Olimex_kernel_3.4.103%2B_Jessie_rel_8.txt build instructions and required files at the GitHub page]

You can find some older releases and older build instructions (older image revisions might be used as a reference, for testing purposes, or if you own old hardware revision of the board) at the following article: [[A20-OLinuXino-LIME2-older-releases|older releases and older build instructions]]

----

Note: the A20-LIME2-DEBIAN-SD card which we have in our web store contains the image suitable for board with no flash or board with NAND memory on a 8GB Class10 fast microSD card. The A20-LIME2-eMMC-DEBIAN-SD contains the image suitable for boards with extra eMMC memory. If you want to use our images, please, use card with speed Class10 or higher. Else the Linux performance would be very slow.

Note: in the previous Debian releases the Ethernet was auto-detected and initialized during boot BUT this was causing big delays in the start-up of the board if you didn't want to use Ethernet or if there wasn't Ethernet cable connected.

You can enable it by following these two steps:

1. To check under what name the LAN is associated write "ifconfig –a"

2. If, for example, it is under eth0 name, then write: "dhclient eth0"

This should enable the Ethernet and then SSH would also be available.

=== Android images ===

Torrents of official Android releases are below. Please read description of the image carefully.

'''Newest official release (recommended):'''

For the NAND flash memory:

FTP location of Android 4.2.2 release 1 for NAND memory (with HDMI and 7 inch 800x480 support - LCD-OLinuXino-7TS): [https://ftp.olimex.com/Allwinner_Images/A20-OLinuXino-LIME2/Android/nand/A20_Lime2_android_4_22_NAND_LCD7_HDMI_release1.img A20-OLinuXino-Lime2 Android for NAND with HDMI and 7 inch display support]

FTP location of Android 4.2.2 release 1 for NAND memory (with HDMI and 10 inch 1024x600 support - LCD-OLinuXino-10TS): [https://ftp.olimex.com/Allwinner_Images/A20-OLinuXino-LIME2/Android/nand/A20_Lime2_android_4_22_NAND_LCD10_HDMI_release1.img A20-OLinuXino-Lime2 Android for NAND with HDMI and 10 inch display support]

For microSD card:

FTP location of Android 4.2.2 release 2 for 8GB microSD card (with HDMI and 800x480 support): [https://ftp.olimex.com/Allwinner_Images/A20-OLinuXino-LIME2/Android/sd/A20_Lime2_Android_4.22_SD_card_LCD_800x480_HDMI_8GB_release_2.img.7z A20-OLinuXino-Lime2 Android for 8GB microSD card with HDMI and 7 inch display support]

FTP location of Android 4.2.2 release 2 for 16GB microSD card (with HDMI and 1024x600 support):
[https://ftp.olimex.com/Allwinner_Images/A20-OLinuXino-LIME2/Android/sd/A20-LIME2-ANDROID-SD-expanded-16GB_LCD10_cfg0_0.zip A20-OLinuXino-Lime2 Android for 16GB microSD card with HDMI and 10 inch display support, this image requires loading via PhoenixSuit, refer to the FAQ section at the end of this page]

Build instructions and source files for the official Android images for A20 boards in this repository: https://github.com/hehopmajieh/olinuxino_configs

== Notable unofficial images ==

Below you would find locations to images released by the community. These are not officially supported by Olimex, however, some of these releases are pretty good and worth a try:

*A number of very good and optimized A20-OLinuXino-LIME2 Armbian images: [https://www.armbian.com/olimex-lime-2/ link to LIME2 article at Armbian's web-site]

*A20-OLinuXino-LIME2 is supported by openSUSE Factory, installation instructions might be found here: [https://en.opensuse.org/HCL:A20-OLinuXIno-LIME2 openSUSE wiki link]

*A20-OLinuXino-LIME2 is recognized by the Devuan community and there are official releases here might be found here: [https://files.devuan.org/devuan_ascii/embedded/ Devuan list of files link]
 

== Documents ==

===A20-OLinuXino-LIME2 user's manual===
[https://www.olimex.com/Products/OLinuXino/A20/A20-OLinuXIno-LIME2/resources/A20-OLinuXino-LIME2-UM.pdf User's manual for A20-OLinuXino-LIME2 and A20-OLinuXino-LIME2-4GB]

=== A20 Brief ===
[https://github.com/OLIMEX/OLINUXINO/blob/master/HARDWARE/A20-PDFs/A20%20brief%2020130407.pdf A20 brief]

=== A20 Datasheet ===

[https://github.com/OLIMEX/OLINUXINO/blob/master/HARDWARE/A20-PDFs/A20%20Datasheet%20v1.0%2020130227.pdf A20 Datasheet]

=== A20 User Manual ===

[https://github.com/OLIMEX/OLINUXINO/blob/master/HARDWARE/A20-PDFs/A20%20User%20Manual%202013-03-22.pdf A20 user's manual]

== Hardware ==

===LIME2 shield templates===
[https://github.com/OLIMEX/OLINUXINO/tree/master/HARDWARE/A20-OLinuXino-LIME2 Eagle and KiCAD shield templates for LIME2]

===GPIO description===

[https://github.com/OLIMEX/OLINUXINO/blob/master/HARDWARE/A20-OLinuXino-LIME2/3.%20Templates%20and%20more/A20_LIME2_GPIOs.pdf A20-OLinuXino-LIME2 GPIO description]

A template that might be used to create custom shields or own adapters might be downloaded for Eagle or KiCad at the GitHub here: [https://github.com/OLIMEX/OLINUXINO/tree/master/HARDWARE/A20-OLinuXino-LIME2 shield template]

===Power supply and consumption===

A20-OLinuXino-LIME2 requires 5V regulated power supply external source. regulated means that the power supply adapter should provide exactly 5V no matter loaded or unloaded (some cheap wallwart adapters are not regulated and under no load their power supply may be higher than 5V although marked as 5V power supply, please measure with voltmeter if your power supply provide 5V as if you connect more than 5V to LIME it will be damaged!!!)

The power jack is standard [https://www.olimex.com/wiki/PWRJACK OLIMEX power jack].

A20-OLinuXino-LIME can be powered from three sources:
*+5VDC voltage applied PWR jack
*+3.7V from LiPo re-chargable battery connected to LiPo board connector
*+5V applied to USB-OTG connector

Power consumption is as follows:
*LiPo 3.7V power battery: 1.2W
*+5VDC input power: 1.3W

Comparison table of power consumption might be found at the following [https://www.olimex.com/Products/OLinuXino/_resources/OLinuXino-Consumption.pdf link].

LiPo battery allow backup power supply when main power is interrupted. A20-OLinuXino-LIME2 has power managment IC which charge the battery when main power is present, when power is interrupted the LiPo battery automatically provide backup power supply. Step-up converter prvide 5V for the USB peripherials too. For LiPo batteries we recommend these:
*[https://www.olimex.com/Products/Power/BATTERY-LIPO1400mAh/ 1400mAh]
*[https://www.olimex.com/Products/Power/BATTERY-LIPO3000mAh/ 3000mAh]
*[https://www.olimex.com/Products/Power/BATTERY-LIPO4400mAh/ 4400mAh]
*[https://www.olimex.com/Products/Power/BATTERY-LIPO6600mAh/ 6600mAh]
 

===Board dimensions===

A20-OLinuXino-LIME2 basic dimensions in mils: 3305.5 x 2347.0

Some additional measures might be seen in the image of A10-OLinuXino-LIME which has almost identical layout. It is available as .png here:
[https://www.olimex.com/Products/OLinuXino/A10/A10-OLinuXino-LIME/resources/A10-LIME-dimensions.png link]

===CAD files===

A20-OLinuXino-LIME2 is an Open Source Hardware, CAD files are available at [https://github.com/OLIMEX/OLINUXINO/tree/master/HARDWARE/A20-OLinuXino-LIME2 GitHub]

The CAD product used to design OLinuXino is Eagle and you can download evaluation free version from their [http://www.cadsoftusa.com/ web].

===Board Layout===

[[File:A20-OLinuXino-LIME2_top_naming_extras.jpg|650px]]

[[File:A20-OLinuXino-LIME2 bottom naming.jpg|650px]]

== Software ==

===Linux Commands===

[[Linux-Commands]] Brief Linux Command reference

===Python library for GPIO, I2C and SPI control===

The Debian Linux Python package for A20-OLinuXino-LIME2 is called pyA20Lime2. It makes the access to GPIO, I2C and SPI considerably easier. It is installed in the default Debian image. More information and examples on how it can be used might be found here:

[https://pypi.python.org/pypi/pyA20Lime2 Link to pyA20Lime2 package at python.org]

===GPIO under Linux===

GPIOs are located in /sys/class/gpio directory. Note that first you have to export GPIOs. For example:

add gpioPH2

root@A20:~# echo 20 > /sys/class/gpio/export

make PH2 output

root@A20:~# echo out > //sys/class/gpio/gpio20_ph2/direction

turn on onboard LED(connected to PH2)

root@A20:~# echo 1 > /sys/class/gpio/gpio20_ph2/value

turn off onboard LED(connected to PH2)

root@A20:~# echo 0 > /sys/class/gpio/gpio20_ph2/value

Full list with supported GPIOs is:

gpio21_ph7 gpio33_ph20 gpio45_pb12 gpio57_pi2 gpio69_pi14
gpio10_pg11 gpio22_ph9 gpio34_ph21 gpio46_pb13 gpio58_pi3 gpio6_pg5
gpio11_pc3 gpio23_ph10 gpio35_ph22 gpio47_pb14 gpio59_pi4 gpio70_pi15
gpio12_pc18 gpio24_ph11 gpio36_ph23 gpio48_pb15 gpio5_pg4 gpio71_pi16
gpio13_pc19 gpio25_ph12 gpio37_pb3 gpio49_pb16 gpio60_pi5 gpio72_pi17
gpio14_pc20 gpio26_ph13 gpio38_pb4 gpio4_pg3 gpio61_pi6 gpio73_pi18
gpio15_pc21 gpio27_ph14 gpio39_pb5 gpio50_pb17 gpio62_pi7 gpio74_pi19
gpio16_pc22 gpio28_ph15 gpio3_pg2 gpio51_ph24 gpio63_pi8 gpio75_pi20
gpio17_pc23 gpio29_ph16 gpio40_pb6 gpio52_ph25 gpio64_pi9 gpio7_pg6
gpio18_pc24 gpio2_pg1 gpio41_pb7 gpio53_ph26 gpio65_pi10 gpio8_pg7
gpio19_ph0 gpio30_ph17 gpio42_pb8 gpio54_ph27 gpio66_pi11 gpio9_pg8
gpio1_pg0 gpio31_ph18 gpio43_pb10 gpio55_pi0 gpio67_pi12 gpiochip1
gpio20_ph2 gpio32_ph19 gpio44_pb11 gpio56_pi1 gpio68_pi13

===Add Voice to your OLinuXino project===

[http://olimex.wordpress.com/2013/10/03/make-things-talk-with-olinuxino/ Installation of Festival on OLinuXino]
 

== How To? ==
===How to generate boot-able SD-card Debian Linux image for A20-OLinuXino-LIME2? ===

Build instructions and required files for the latest Debian images: [https://github.com/OLIMEX/OLINUXINO/tree/master/SOFTWARE/A20 instructions and files at the GitHub page]

Note that Linux-Sunxi Kernel is a work-in-progress, this means you can try the current stage/sunxi-x.x branch but if something is broken and doesn't work just revert to the git tags we give in the blog and they would work for sure.

[https://github.com/linux-sunxi/u-boot-sunxi/wiki Sunxi u-boot loader] The linux-sunxi git page contains a lot of sources for all Olimex Allwinner boards.

===How to connect a display and adjust the video output resolution?===
There is a separate article on the subject: [[how to connect display to a Lime board]]
 

=== Is it possible to boot Debian from NAND? Do you provide such image?===

Yes, it is possible. Use the latest Debian Jessie image and write "nandinstall". More information can be found in this wiki article: [[How_to_install_Debian_to_NAND| installing Debian Jessie to the 4GB NAND memory]]

There are other people who are also successful in booting Debian from the NAND. Make sure to check on the forum. Make sure to check the number of very good and optimized A20-OLinuXino Debian images by Igor Pečovnik. There are also his instructions for NAND installation of Debian: [http://www.armbian.com/download/ link to his web-site]

===How to detect and enable the Ethernet controller (if it is disabled by default)? ===

Note: in the previous Debian releases the Ethernet was auto-detected and initialized during boot BUT this was causing big delays in the start-up of the board if you didn't want to use Ethernet or if there wasn't Ethernet cable connected.

You can enable it by following these two steps:

1. To check under what name the LAN is associated write "ifconfig –a"

2. If, for example, it is under eth0 name, then write: "dhclient eth0"

This should enable the Ethernet and then SSH would also be available.

===How to download new Android image to the NAND memory of my A20 board?===

Follow these steps to download the image to the NAND memory:

*1. Install and run PhoenixSuit (can be found here: [https://drive.google.com/file/d/0BwplT87k9SCgaTFTZnVST05ONzA/view?usp=sharing download from google drive]).

*2. Go to firmware tab of the program and point to a valid Android image (the latest official one may also be downloaded above).

*3. Disconnect the power supply and USB cable from the A20 board.

*4. Press and hold RECOVERY button, apply power supply 5V, release RECOVERY button.

*5. Connect USB cable to the mini USB connector.

*6. You will be asked for drivers for the bootloader. Navigate to the folder where you extracted the PhoenixSuit and install the drivers from the respective executables (or manually point the installer to the drivers folder in the PhoenixSuit installation path).

*7. PhoenixSuit will detect the board and would ask for the method of writing the image. Choose method of writing the image and confirm your wish to write the image.

*8. Wait till upgrade succeeds

Note that it is not recommended to have your mini USB connected to an external USB hub. This might cause delays and might distort the signal levels. Always test with the USB connected straight to the USB ports of your computer.

===How to generate Arch Linux image?===

Recent forum post by user progmetalbg here: [https://www.olimex.com/forum/index.php?topic=4261.0| at Olimex forums]

[http://alarma20.wordpress.com/2013/09/13/howto-build-arch-linux-arm-for-a20-olinuxino-micro/ Older step by step instructions on how to build Arch Linux image for another A20 board]

===How do I write the official Android image to a micro SD card for my A20 board?===
A: First download one of the official Android images, which might be found in the Android section above.

Make sure that the download link you visit clearly indicates that the image is suitable for the microSD card since there are images suitable for NAND memory also. The images suitable for the microSD memory and those suitable for NAND card are different. However, the upload method is almost identical – using PhoenixSuit.

There are two types of Android images for microSD card that we usually provide and each of them has to be downloaded to a microSD card using a different method. The image provided for microSD card is either the native Android image that can be downloaded to the card via a software tool like PhoenixSuit (through the board) or an image taken from an already prepared microSD card that requires to simply write the image (through a microSD card reader).

'''It is more likely that you have an Android image that requires a simple copy to a card. If that is the case you can follow the exact steps as for Linux (e.g. using "Win32 Disk Imager" or "dd" command).'''

In order to prepare a microSD card with a native Android you will need a software tool called PhoenixSuit and then:

• Install and run PhoenixSuit (can be found here: [https://drive.google.com/file/d/0BwplT87k9SCgaTFTZnVST05ONzA/view?usp=sharing download from google drive])

• Go to the firmware tab of the program and point to a valid Android image (note that the
images on Gdrive are compressed and you have to extract them to .img files to be able write
them with PhoenixSuit)

• Disconnect the power supply and USB cable from the A20 board. Put an SD card in micro SD
holder. We recommend either a 4GB or a 8GB class 10 card.

• Press and hold RECOVERY button, apply power supply 5V, release RECOVERY button.

• Connect USB cable to the mini USB connector.

• You will be asked for drivers for the boot-loader. Navigate to the folder where you extracted the PhoenixSuit and install the drivers from the respective executables (or manually point the installer to the drivers folder in the PhoenixSuit installation path).

• PhoenixSuit will detect the board and would ask for the method of writing the image. Choose
method of writing the image and confirm your wish to write the image.

• Wait till upgrade succeeds

Note that it is not recommended to have your mini USB connected to an external USB hub. This
might cause delays and might distort the signal levels. Always test with the USB connected straight to the USB ports of your computer.

Important: When Android runs for very first time it takes several minutes to initialize all files and buffers please do not cut the power supply during this process! Also when fresh image is installed fast boot may be disabled, which means that when you apply power supply after few seconds Android will go in sleep mode and you have to press POWER button to start it, you can change to fast boot when you power off there is dialog box asking you if you want next boot to be fast boot, you have to check this box before you power off. Also note that you must do touch screen calibration when you run Android for very first time which might require a mouse.

===I don't have neither serial cable, nor HDMI monitor. I also can't access the local Ethernet network. Can I somehow access the board anyway?===

The latest official Debian Linux image allows the use the USB_OTG connector for SSH connection without the need of a LAN cable or a serial cable. You can use a mini USB cable connected between your host PC and the on-board mini USB connector. For connection convenience there is a DHCP server running specifically for USB0 interface. The DHCP server should give IP address to the new USB0 interface of your host PC so you can make SSH connection from your PC to the default board IP address of the USB0 interface – 192.168.2.1.

You can connect to the board using a mini USB cable and an SSH client (if you use Windows you might use "puTTY", for example) at address 192.168.2.1.

For Windows operating system - upon connection, the board should show up in "Windows Device Manager" as "RNDIS Ethernet Gadget". You might be asked to install a driver. The drivers can be found online as "RNDIS driver" (Remote Network Driver Interface Specification). The drivers are provided by Microsoft and they should be available for every Windows distribution - refer to the respective files and articles provided by Microsoft on how to install the required drivers.

===How to edit board configurations and definitions in the official Debian Linux? ===

Do you want a custom video resolution output? Do you need a different port definition? Do you need to change the hardware defitions of the board?

You would need to edit the board's script.bin/script.fex file. How to do it is described in another separate article: [[how to edit board configurations and definitions in the official Debian Linux]].

===How to add STK1160 video capture driver support in Kernel 3.4===

[https://www.olimex.com/wiki/STK1160-howto-linux-sunxi-3_4 STK1160] driver backport by Dimitar Tomov
[[Main_Page]]

A20-OLinuXino-LIME2

2024-09-30T07:54:47Z

LubOlimex: /* Android images */

[[File:A20-OLinuXino-LIME2.jpg|600px]]

A20-OLinuXino-LIME2 looks similar to both [[A20-OLinuXino-LIME]] and [[A10-OLinuXino-LIME]]. The major differences between A20-OLinuXino-LIME2 and A20-OLinuXino-LIME are:

*LIME2 has gigabit Ethernet (GbE), compared to the standard 100Mb Ethernet of the LIME
*LIME2 design provides double the RAM memory, compared to the LIME design (1024 vs 512)
*Much better routing of DDR3 memory.
*Increased the number of layers from 6 in LIME to 8 in LIME2
*Corrected pinout of the LCD and GPIO connectors (shields designed for the LIME layout are not compatible with the LIME2 layout)

The A10 and the A20 processors are pin-to-pin compatible. Because of the processor, software-wise the board is closer to [[A20-OLinuXino-LIME]] than to the [[A10-OLinuXino-LIME]]. This resemblance to other designs definitely might speed the development on the board - a lot of software written for A20-OLinuXino-LIME might work out-of-the-box with A20-OLinuXino-LIME2. Additionally, pinout tables, GPIO maps, etc released for A20-OLinuXino-LIME would apply to A20-OLinuXino-LIME2 (except for the 0.05" step connectors - LCD display and all the GPIOs connectors, which have a different layout compared to both A20-OLinuXino-LIME and A10-OLinuXino-LIME).

A20-OLinuXino-LIME2 features:
*A20 Cortex-A7 dual-core ARM Cortex-A7 CPU and dual-core Mali 400 GPU
*'''1GB DDR3 RAM memory'''
*'''1 gigabit native Ethernet'''
*optional 4GB NAND FLASH memory
*SATA connector with 5V SATA power jack
*HDMI FullHD 1080p
*2x USB Low-Full-High-Speed hosts with power control and current limiter
*USB-OTG with power control and current limiter
*LiPo Battery connector with battery-charging capabilities
*LCD connector compatible with with 4.3", 7.0", 10.1" LCD modules from Olimex
*160 GPIOs on three GPIO connectors
*MicroSD card connector
*DEBUG-UART connector for console debug with USB-SERIAL-CABLE-F
*status LED
*Battery charge status LED
*Power LED
*2KB EEPROM for MAC address storage and more
*2 BUTTONS with ANDROID functionality + RESET button
*2 mount holes
*5V input power supply, noise immune design
*PCB dimensions: 84 x 60 mm

== Official Images from OLIMEX ==

In this chapter you would find links to torrents with the official Debian and Android images. The images in this chapter were compiled by Olimex. They are recommended for beginners and first time users since they include full hardware support. If you are experienced Linux professional you might find useful our build instructions also published here.

The downloaded file xxxx.7z is an archive of xxx.img file. In order to write the image on SD card you have to extract the xxx.7z file.

*For Windows: use 7zip and then use Win32DiskImager.exe (http://sourceforge.net/projects/win32diskimager/) to write the image

*For Linux: use p7zip package. If you don't have 7zip installed first install it 

#apt-get install p7zip
Copy a20_Lime2_debian_second_release.7z file in your directory and unzip the archive with
#7za e a20_Lime2_debian_second_release.7z
where a20_Lime2_debian_second_release.7z
The output should be a new 4GB file with extension img
Put 4GB SD card in your card reader and type
# ls /dev/sd
Then press two times <TAB> you will see a list of your sd devices like sda sdb sdc note that some of these devices may be your hard disk so make sure you know which one is your sd card before you proceed as you can damage your HDD if you choose the wrong sd-device. You can do this by unplugging your sd card reader and identify which "sd" devices remove from the list.
Once you know which device is your sdcard like sda use this text instead of the sdX name in the references below:
#dd if=a20_Lime2_debian_second_release.img of=/dev/sdX

The Debian Linux image is 4GB and the file system can be extended to suit a bigger card. Use the following three commands to execute a script that would use all the free space of your card:

sudo su
./resize_sd.sh /dev/mmcblk0 2
reboot

=== Linux images ===

These official Debian images should be downloaded to a microSD card. Older sunxi images can be found as direct downloads at our FTP. You can install the Debian to the NAND or the eMMC of your board (if it comes with one). Information on booting Debian from the NAND might be found in these wiki articles: [[how to install Debian to NAND]]; [[how to install Debian to eMMC]]. Download locations for the official images might be found below:

'''ALWAYS FIRST TEST WITH LATEST OFFICIAL IMAGE, NEWER HARDWARE REVISIONS OF THE BOARD MIGHT NOT WORK WITH OLDER IMAGES!!!'''

----

'''Latest stable official images - Debian 8 (Jessie)''' '''Both images are suitable for the standard version A20-OLinuXino-LIME2. However A20-OLinuXino-LIME2-n4GB and A20-OLinuXino-LIME2-n8GB have different image compared to A20-OLinuXino-LIME2-e4GB''':'''

FTP location for official Debian Jessie release #13 for A20-OLinuXino-LIME2, A20-OLinuXino-LIME2-n4GB, and A20-OLinuXino-LIME2-n8GB (not suitable for boards with eMMC flash): [https://ftp.olimex.com/Allwinner_Images/A20-OLinuXino-LIME2/Debian/sd/a20-lime2_mainline_uboot_sunxi_kernel_3.4.103_jessie_NAND_rel_13.img.7z A20-OLinuXino-LIME2 Debian Jessie with kernel 3.4.103+ release 13]

FTP location for official Debian Jessie release #16 for A20-OLinuXino-LIME2, A20-OLinuXino-LIME2-e4GB (not suitable for boards with NAND flash): [https://ftp.olimex.com/Allwinner_Images/A20-OLinuXino-LIME2/Debian/sd/a20-lime2_mainline_uboot_sunxi_kernel_3.4.103_jessie_eMMC_rel_16.zip A20 lime2 mainline uboot sunxi kernel 3.4.103 jessie eMMC rel 16]

Image description and typical interfacing: [https://github.com/OLIMEX/OLINUXINO/blob/master/SOFTWARE/A20/A20-build-3.4.103-release-7/USAGE-AND-COMMON-PRACTICEs-A20-Olimex_kernel_3.4.103%2B_Jessie_rel_3.txt description and basic usage of different peripherals at at the GitHub page]

Image build instructions and required files for latest Debian Jessie release might be found here: [https://github.com/OLIMEX/OLINUXINO/blob/master/SOFTWARE/A20/A20-build-3.4.103-release-8/BUILD_DESCRIPTION_A20_Olimex_kernel_3.4.103%2B_Jessie_rel_8.txt build instructions and required files at the GitHub page]

You can find some older releases and older build instructions (older image revisions might be used as a reference, for testing purposes, or if you own old hardware revision of the board) at the following article: [[A20-OLinuXino-LIME2-older-releases|older releases and older build instructions]]

----

Note: the A20-LIME2-DEBIAN-SD card which we have in our web store contains the image suitable for board with no flash or board with NAND memory on a 8GB Class10 fast microSD card. The A20-LIME2-eMMC-DEBIAN-SD contains the image suitable for boards with extra eMMC memory. If you want to use our images, please, use card with speed Class10 or higher. Else the Linux performance would be very slow.

Note: in the previous Debian releases the Ethernet was auto-detected and initialized during boot BUT this was causing big delays in the start-up of the board if you didn't want to use Ethernet or if there wasn't Ethernet cable connected.

You can enable it by following these two steps:

1. To check under what name the LAN is associated write "ifconfig –a"

2. If, for example, it is under eth0 name, then write: "dhclient eth0"

This should enable the Ethernet and then SSH would also be available.

=== Android images ===

Torrents of official Android releases are below. Please read description of the image carefully.

'''Newest official release (recommended):'''

For the NAND flash memory:

FTP location of Android 4.2.2 release 1 for NAND memory (with HDMI and 7 inch 800x480 support - LCD-OLinuXino-7TS): [https://ftp.olimex.com/Allwinner_Images/A20-OLinuXino-LIME2/Android/nand/A20_Lime2_android_4_22_NAND_LCD7_HDMI_release1.img A20-OLinuXino-Lime2 Android for NAND with HDMI and 7 inch display support]]

Torrent of Android 4.2.2 release 1 for NAND memory (with HDMI and 10 inch 1024x600 support - LCD-OLinuXino-10TS): [https://ftp.olimex.com/Allwinner_Images/A20-OLinuXino-LIME2/Android/nand/A20_Lime2_android_4_22_NAND_LCD10_HDMI_release1.img A20-OLinuXino-Lime2 Android for NAND with HDMI and 10 inch display support]]

For microSD card:

Torrent of Android 4.2.2 release 2 for 8GB microSD card (with HDMI and 800x480 support): [[Media:A20_Lime2_Android_4.22_SD_card_LCD_800x480_HDMI_8GB_release_2.torrent‎‎‎‎|A20-OLinuXino-Lime2 Android for 8GB microSD card with HDMI and 7 inch display support]]

Torrent of Android 4.2.2 release 2 for 8GB microSD card (with HDMI and 1024x600 support):
[[Media:A20_Lime2_Android_4.22_SD_card_LCD_1024x600_HDMI.torrent|A20-OLinuXino-Lime2 Android for 8GB microSD card with HDMI and 10 inch display support, this image requires loading via PhoenixSuit, refer to the FAQ section at the end of this page]]

Torrent of Android 4.2.2 release 1 for 4GB microSD card (with HDMI and 800x480 support): [[Media:A20_Lime2_Android_4.22_SD_card_LCD_800x480_HDMI_release_1.torrent‎‎‎‎|A20-OLinuXino-Lime2 Android for 4GB microSD card with HDMI and 7 inch display support]]

Build instructions and source files for the official Android images for A20 boards in this repository: https://github.com/hehopmajieh/olinuxino_configs

== Notable unofficial images ==

Below you would find locations to images released by the community. These are not officially supported by Olimex, however, some of these releases are pretty good and worth a try:

*A number of very good and optimized A20-OLinuXino-LIME2 Armbian images: [https://www.armbian.com/olimex-lime-2/ link to LIME2 article at Armbian's web-site]

*A20-OLinuXino-LIME2 is supported by openSUSE Factory, installation instructions might be found here: [https://en.opensuse.org/HCL:A20-OLinuXIno-LIME2 openSUSE wiki link]

*A20-OLinuXino-LIME2 is recognized by the Devuan community and there are official releases here might be found here: [https://files.devuan.org/devuan_ascii/embedded/ Devuan list of files link]
 

== Documents ==

===A20-OLinuXino-LIME2 user's manual===
[https://www.olimex.com/Products/OLinuXino/A20/A20-OLinuXIno-LIME2/resources/A20-OLinuXino-LIME2-UM.pdf User's manual for A20-OLinuXino-LIME2 and A20-OLinuXino-LIME2-4GB]

=== A20 Brief ===
[https://github.com/OLIMEX/OLINUXINO/blob/master/HARDWARE/A20-PDFs/A20%20brief%2020130407.pdf A20 brief]

=== A20 Datasheet ===

[https://github.com/OLIMEX/OLINUXINO/blob/master/HARDWARE/A20-PDFs/A20%20Datasheet%20v1.0%2020130227.pdf A20 Datasheet]

=== A20 User Manual ===

[https://github.com/OLIMEX/OLINUXINO/blob/master/HARDWARE/A20-PDFs/A20%20User%20Manual%202013-03-22.pdf A20 user's manual]

== Hardware ==

===LIME2 shield templates===
[https://github.com/OLIMEX/OLINUXINO/tree/master/HARDWARE/A20-OLinuXino-LIME2 Eagle and KiCAD shield templates for LIME2]

===GPIO description===

[https://github.com/OLIMEX/OLINUXINO/blob/master/HARDWARE/A20-OLinuXino-LIME2/3.%20Templates%20and%20more/A20_LIME2_GPIOs.pdf A20-OLinuXino-LIME2 GPIO description]

A template that might be used to create custom shields or own adapters might be downloaded for Eagle or KiCad at the GitHub here: [https://github.com/OLIMEX/OLINUXINO/tree/master/HARDWARE/A20-OLinuXino-LIME2 shield template]

===Power supply and consumption===

A20-OLinuXino-LIME2 requires 5V regulated power supply external source. regulated means that the power supply adapter should provide exactly 5V no matter loaded or unloaded (some cheap wallwart adapters are not regulated and under no load their power supply may be higher than 5V although marked as 5V power supply, please measure with voltmeter if your power supply provide 5V as if you connect more than 5V to LIME it will be damaged!!!)

The power jack is standard [https://www.olimex.com/wiki/PWRJACK OLIMEX power jack].

A20-OLinuXino-LIME can be powered from three sources:
*+5VDC voltage applied PWR jack
*+3.7V from LiPo re-chargable battery connected to LiPo board connector
*+5V applied to USB-OTG connector

Power consumption is as follows:
*LiPo 3.7V power battery: 1.2W
*+5VDC input power: 1.3W

Comparison table of power consumption might be found at the following [https://www.olimex.com/Products/OLinuXino/_resources/OLinuXino-Consumption.pdf link].

LiPo battery allow backup power supply when main power is interrupted. A20-OLinuXino-LIME2 has power managment IC which charge the battery when main power is present, when power is interrupted the LiPo battery automatically provide backup power supply. Step-up converter prvide 5V for the USB peripherials too. For LiPo batteries we recommend these:
*[https://www.olimex.com/Products/Power/BATTERY-LIPO1400mAh/ 1400mAh]
*[https://www.olimex.com/Products/Power/BATTERY-LIPO3000mAh/ 3000mAh]
*[https://www.olimex.com/Products/Power/BATTERY-LIPO4400mAh/ 4400mAh]
*[https://www.olimex.com/Products/Power/BATTERY-LIPO6600mAh/ 6600mAh]
 

===Board dimensions===

A20-OLinuXino-LIME2 basic dimensions in mils: 3305.5 x 2347.0

Some additional measures might be seen in the image of A10-OLinuXino-LIME which has almost identical layout. It is available as .png here:
[https://www.olimex.com/Products/OLinuXino/A10/A10-OLinuXino-LIME/resources/A10-LIME-dimensions.png link]

===CAD files===

A20-OLinuXino-LIME2 is an Open Source Hardware, CAD files are available at [https://github.com/OLIMEX/OLINUXINO/tree/master/HARDWARE/A20-OLinuXino-LIME2 GitHub]

The CAD product used to design OLinuXino is Eagle and you can download evaluation free version from their [http://www.cadsoftusa.com/ web].

===Board Layout===

[[File:A20-OLinuXino-LIME2_top_naming_extras.jpg|650px]]

[[File:A20-OLinuXino-LIME2 bottom naming.jpg|650px]]

== Software ==

===Linux Commands===

[[Linux-Commands]] Brief Linux Command reference

===Python library for GPIO, I2C and SPI control===

The Debian Linux Python package for A20-OLinuXino-LIME2 is called pyA20Lime2. It makes the access to GPIO, I2C and SPI considerably easier. It is installed in the default Debian image. More information and examples on how it can be used might be found here:

[https://pypi.python.org/pypi/pyA20Lime2 Link to pyA20Lime2 package at python.org]

===GPIO under Linux===

GPIOs are located in /sys/class/gpio directory. Note that first you have to export GPIOs. For example:

add gpioPH2

root@A20:~# echo 20 > /sys/class/gpio/export

make PH2 output

root@A20:~# echo out > //sys/class/gpio/gpio20_ph2/direction

turn on onboard LED(connected to PH2)

root@A20:~# echo 1 > /sys/class/gpio/gpio20_ph2/value

turn off onboard LED(connected to PH2)

root@A20:~# echo 0 > /sys/class/gpio/gpio20_ph2/value

Full list with supported GPIOs is:

gpio21_ph7 gpio33_ph20 gpio45_pb12 gpio57_pi2 gpio69_pi14
gpio10_pg11 gpio22_ph9 gpio34_ph21 gpio46_pb13 gpio58_pi3 gpio6_pg5
gpio11_pc3 gpio23_ph10 gpio35_ph22 gpio47_pb14 gpio59_pi4 gpio70_pi15
gpio12_pc18 gpio24_ph11 gpio36_ph23 gpio48_pb15 gpio5_pg4 gpio71_pi16
gpio13_pc19 gpio25_ph12 gpio37_pb3 gpio49_pb16 gpio60_pi5 gpio72_pi17
gpio14_pc20 gpio26_ph13 gpio38_pb4 gpio4_pg3 gpio61_pi6 gpio73_pi18
gpio15_pc21 gpio27_ph14 gpio39_pb5 gpio50_pb17 gpio62_pi7 gpio74_pi19
gpio16_pc22 gpio28_ph15 gpio3_pg2 gpio51_ph24 gpio63_pi8 gpio75_pi20
gpio17_pc23 gpio29_ph16 gpio40_pb6 gpio52_ph25 gpio64_pi9 gpio7_pg6
gpio18_pc24 gpio2_pg1 gpio41_pb7 gpio53_ph26 gpio65_pi10 gpio8_pg7
gpio19_ph0 gpio30_ph17 gpio42_pb8 gpio54_ph27 gpio66_pi11 gpio9_pg8
gpio1_pg0 gpio31_ph18 gpio43_pb10 gpio55_pi0 gpio67_pi12 gpiochip1
gpio20_ph2 gpio32_ph19 gpio44_pb11 gpio56_pi1 gpio68_pi13

===Add Voice to your OLinuXino project===

[http://olimex.wordpress.com/2013/10/03/make-things-talk-with-olinuxino/ Installation of Festival on OLinuXino]
 

== How To? ==
===How to generate boot-able SD-card Debian Linux image for A20-OLinuXino-LIME2? ===

Build instructions and required files for the latest Debian images: [https://github.com/OLIMEX/OLINUXINO/tree/master/SOFTWARE/A20 instructions and files at the GitHub page]

Note that Linux-Sunxi Kernel is a work-in-progress, this means you can try the current stage/sunxi-x.x branch but if something is broken and doesn't work just revert to the git tags we give in the blog and they would work for sure.

[https://github.com/linux-sunxi/u-boot-sunxi/wiki Sunxi u-boot loader] The linux-sunxi git page contains a lot of sources for all Olimex Allwinner boards.

===How to connect a display and adjust the video output resolution?===
There is a separate article on the subject: [[how to connect display to a Lime board]]
 

=== Is it possible to boot Debian from NAND? Do you provide such image?===

Yes, it is possible. Use the latest Debian Jessie image and write "nandinstall". More information can be found in this wiki article: [[How_to_install_Debian_to_NAND| installing Debian Jessie to the 4GB NAND memory]]

There are other people who are also successful in booting Debian from the NAND. Make sure to check on the forum. Make sure to check the number of very good and optimized A20-OLinuXino Debian images by Igor Pečovnik. There are also his instructions for NAND installation of Debian: [http://www.armbian.com/download/ link to his web-site]

===How to detect and enable the Ethernet controller (if it is disabled by default)? ===

Note: in the previous Debian releases the Ethernet was auto-detected and initialized during boot BUT this was causing big delays in the start-up of the board if you didn't want to use Ethernet or if there wasn't Ethernet cable connected.

You can enable it by following these two steps:

1. To check under what name the LAN is associated write "ifconfig –a"

2. If, for example, it is under eth0 name, then write: "dhclient eth0"

This should enable the Ethernet and then SSH would also be available.

===How to download new Android image to the NAND memory of my A20 board?===

Follow these steps to download the image to the NAND memory:

*1. Install and run PhoenixSuit (can be found here: [https://drive.google.com/file/d/0BwplT87k9SCgaTFTZnVST05ONzA/view?usp=sharing download from google drive]).

*2. Go to firmware tab of the program and point to a valid Android image (the latest official one may also be downloaded above).

*3. Disconnect the power supply and USB cable from the A20 board.

*4. Press and hold RECOVERY button, apply power supply 5V, release RECOVERY button.

*5. Connect USB cable to the mini USB connector.

*6. You will be asked for drivers for the bootloader. Navigate to the folder where you extracted the PhoenixSuit and install the drivers from the respective executables (or manually point the installer to the drivers folder in the PhoenixSuit installation path).

*7. PhoenixSuit will detect the board and would ask for the method of writing the image. Choose method of writing the image and confirm your wish to write the image.

*8. Wait till upgrade succeeds

Note that it is not recommended to have your mini USB connected to an external USB hub. This might cause delays and might distort the signal levels. Always test with the USB connected straight to the USB ports of your computer.

===How to generate Arch Linux image?===

Recent forum post by user progmetalbg here: [https://www.olimex.com/forum/index.php?topic=4261.0| at Olimex forums]

[http://alarma20.wordpress.com/2013/09/13/howto-build-arch-linux-arm-for-a20-olinuxino-micro/ Older step by step instructions on how to build Arch Linux image for another A20 board]

===How do I write the official Android image to a micro SD card for my A20 board?===
A: First download one of the official Android images, which might be found in the Android section above.

Make sure that the download link you visit clearly indicates that the image is suitable for the microSD card since there are images suitable for NAND memory also. The images suitable for the microSD memory and those suitable for NAND card are different. However, the upload method is almost identical – using PhoenixSuit.

There are two types of Android images for microSD card that we usually provide and each of them has to be downloaded to a microSD card using a different method. The image provided for microSD card is either the native Android image that can be downloaded to the card via a software tool like PhoenixSuit (through the board) or an image taken from an already prepared microSD card that requires to simply write the image (through a microSD card reader).

'''It is more likely that you have an Android image that requires a simple copy to a card. If that is the case you can follow the exact steps as for Linux (e.g. using "Win32 Disk Imager" or "dd" command).'''

In order to prepare a microSD card with a native Android you will need a software tool called PhoenixSuit and then:

• Install and run PhoenixSuit (can be found here: [https://drive.google.com/file/d/0BwplT87k9SCgaTFTZnVST05ONzA/view?usp=sharing download from google drive])

• Go to the firmware tab of the program and point to a valid Android image (note that the
images on Gdrive are compressed and you have to extract them to .img files to be able write
them with PhoenixSuit)

• Disconnect the power supply and USB cable from the A20 board. Put an SD card in micro SD
holder. We recommend either a 4GB or a 8GB class 10 card.

• Press and hold RECOVERY button, apply power supply 5V, release RECOVERY button.

• Connect USB cable to the mini USB connector.

• You will be asked for drivers for the boot-loader. Navigate to the folder where you extracted the PhoenixSuit and install the drivers from the respective executables (or manually point the installer to the drivers folder in the PhoenixSuit installation path).

• PhoenixSuit will detect the board and would ask for the method of writing the image. Choose
method of writing the image and confirm your wish to write the image.

• Wait till upgrade succeeds

Note that it is not recommended to have your mini USB connected to an external USB hub. This
might cause delays and might distort the signal levels. Always test with the USB connected straight to the USB ports of your computer.

Important: When Android runs for very first time it takes several minutes to initialize all files and buffers please do not cut the power supply during this process! Also when fresh image is installed fast boot may be disabled, which means that when you apply power supply after few seconds Android will go in sleep mode and you have to press POWER button to start it, you can change to fast boot when you power off there is dialog box asking you if you want next boot to be fast boot, you have to check this box before you power off. Also note that you must do touch screen calibration when you run Android for very first time which might require a mouse.

===I don't have neither serial cable, nor HDMI monitor. I also can't access the local Ethernet network. Can I somehow access the board anyway?===

The latest official Debian Linux image allows the use the USB_OTG connector for SSH connection without the need of a LAN cable or a serial cable. You can use a mini USB cable connected between your host PC and the on-board mini USB connector. For connection convenience there is a DHCP server running specifically for USB0 interface. The DHCP server should give IP address to the new USB0 interface of your host PC so you can make SSH connection from your PC to the default board IP address of the USB0 interface – 192.168.2.1.

You can connect to the board using a mini USB cable and an SSH client (if you use Windows you might use "puTTY", for example) at address 192.168.2.1.

For Windows operating system - upon connection, the board should show up in "Windows Device Manager" as "RNDIS Ethernet Gadget". You might be asked to install a driver. The drivers can be found online as "RNDIS driver" (Remote Network Driver Interface Specification). The drivers are provided by Microsoft and they should be available for every Windows distribution - refer to the respective files and articles provided by Microsoft on how to install the required drivers.

===How to edit board configurations and definitions in the official Debian Linux? ===

Do you want a custom video resolution output? Do you need a different port definition? Do you need to change the hardware defitions of the board?

You would need to edit the board's script.bin/script.fex file. How to do it is described in another separate article: [[how to edit board configurations and definitions in the official Debian Linux]].

===How to add STK1160 video capture driver support in Kernel 3.4===

[https://www.olimex.com/wiki/STK1160-howto-linux-sunxi-3_4 STK1160] driver backport by Dimitar Tomov
[[Main_Page]]

A20-OLinuXino-LIME2

2024-09-30T07:45:25Z

LubOlimex: /* Linux images */

[[File:A20-OLinuXino-LIME2.jpg|600px]]

A20-OLinuXino-LIME2 looks similar to both [[A20-OLinuXino-LIME]] and [[A10-OLinuXino-LIME]]. The major differences between A20-OLinuXino-LIME2 and A20-OLinuXino-LIME are:

*LIME2 has gigabit Ethernet (GbE), compared to the standard 100Mb Ethernet of the LIME
*LIME2 design provides double the RAM memory, compared to the LIME design (1024 vs 512)
*Much better routing of DDR3 memory.
*Increased the number of layers from 6 in LIME to 8 in LIME2
*Corrected pinout of the LCD and GPIO connectors (shields designed for the LIME layout are not compatible with the LIME2 layout)

The A10 and the A20 processors are pin-to-pin compatible. Because of the processor, software-wise the board is closer to [[A20-OLinuXino-LIME]] than to the [[A10-OLinuXino-LIME]]. This resemblance to other designs definitely might speed the development on the board - a lot of software written for A20-OLinuXino-LIME might work out-of-the-box with A20-OLinuXino-LIME2. Additionally, pinout tables, GPIO maps, etc released for A20-OLinuXino-LIME would apply to A20-OLinuXino-LIME2 (except for the 0.05" step connectors - LCD display and all the GPIOs connectors, which have a different layout compared to both A20-OLinuXino-LIME and A10-OLinuXino-LIME).

A20-OLinuXino-LIME2 features:
*A20 Cortex-A7 dual-core ARM Cortex-A7 CPU and dual-core Mali 400 GPU
*'''1GB DDR3 RAM memory'''
*'''1 gigabit native Ethernet'''
*optional 4GB NAND FLASH memory
*SATA connector with 5V SATA power jack
*HDMI FullHD 1080p
*2x USB Low-Full-High-Speed hosts with power control and current limiter
*USB-OTG with power control and current limiter
*LiPo Battery connector with battery-charging capabilities
*LCD connector compatible with with 4.3", 7.0", 10.1" LCD modules from Olimex
*160 GPIOs on three GPIO connectors
*MicroSD card connector
*DEBUG-UART connector for console debug with USB-SERIAL-CABLE-F
*status LED
*Battery charge status LED
*Power LED
*2KB EEPROM for MAC address storage and more
*2 BUTTONS with ANDROID functionality + RESET button
*2 mount holes
*5V input power supply, noise immune design
*PCB dimensions: 84 x 60 mm

== Official Images from OLIMEX ==

In this chapter you would find links to torrents with the official Debian and Android images. The images in this chapter were compiled by Olimex. They are recommended for beginners and first time users since they include full hardware support. If you are experienced Linux professional you might find useful our build instructions also published here.

The downloaded file xxxx.7z is an archive of xxx.img file. In order to write the image on SD card you have to extract the xxx.7z file.

*For Windows: use 7zip and then use Win32DiskImager.exe (http://sourceforge.net/projects/win32diskimager/) to write the image

*For Linux: use p7zip package. If you don't have 7zip installed first install it 

#apt-get install p7zip
Copy a20_Lime2_debian_second_release.7z file in your directory and unzip the archive with
#7za e a20_Lime2_debian_second_release.7z
where a20_Lime2_debian_second_release.7z
The output should be a new 4GB file with extension img
Put 4GB SD card in your card reader and type
# ls /dev/sd
Then press two times <TAB> you will see a list of your sd devices like sda sdb sdc note that some of these devices may be your hard disk so make sure you know which one is your sd card before you proceed as you can damage your HDD if you choose the wrong sd-device. You can do this by unplugging your sd card reader and identify which "sd" devices remove from the list.
Once you know which device is your sdcard like sda use this text instead of the sdX name in the references below:
#dd if=a20_Lime2_debian_second_release.img of=/dev/sdX

The Debian Linux image is 4GB and the file system can be extended to suit a bigger card. Use the following three commands to execute a script that would use all the free space of your card:

sudo su
./resize_sd.sh /dev/mmcblk0 2
reboot

=== Linux images ===

These official Debian images should be downloaded to a microSD card. Older sunxi images can be found as direct downloads at our FTP. You can install the Debian to the NAND or the eMMC of your board (if it comes with one). Information on booting Debian from the NAND might be found in these wiki articles: [[how to install Debian to NAND]]; [[how to install Debian to eMMC]]. Download locations for the official images might be found below:

'''ALWAYS FIRST TEST WITH LATEST OFFICIAL IMAGE, NEWER HARDWARE REVISIONS OF THE BOARD MIGHT NOT WORK WITH OLDER IMAGES!!!'''

----

'''Latest stable official images - Debian 8 (Jessie)''' '''Both images are suitable for the standard version A20-OLinuXino-LIME2. However A20-OLinuXino-LIME2-n4GB and A20-OLinuXino-LIME2-n8GB have different image compared to A20-OLinuXino-LIME2-e4GB''':'''

FTP location for official Debian Jessie release #13 for A20-OLinuXino-LIME2, A20-OLinuXino-LIME2-n4GB, and A20-OLinuXino-LIME2-n8GB (not suitable for boards with eMMC flash): [https://ftp.olimex.com/Allwinner_Images/A20-OLinuXino-LIME2/Debian/sd/a20-lime2_mainline_uboot_sunxi_kernel_3.4.103_jessie_NAND_rel_13.img.7z A20-OLinuXino-LIME2 Debian Jessie with kernel 3.4.103+ release 13]

FTP location for official Debian Jessie release #16 for A20-OLinuXino-LIME2, A20-OLinuXino-LIME2-e4GB (not suitable for boards with NAND flash): [https://ftp.olimex.com/Allwinner_Images/A20-OLinuXino-LIME2/Debian/sd/a20-lime2_mainline_uboot_sunxi_kernel_3.4.103_jessie_eMMC_rel_16.zip A20 lime2 mainline uboot sunxi kernel 3.4.103 jessie eMMC rel 16]

Image description and typical interfacing: [https://github.com/OLIMEX/OLINUXINO/blob/master/SOFTWARE/A20/A20-build-3.4.103-release-7/USAGE-AND-COMMON-PRACTICEs-A20-Olimex_kernel_3.4.103%2B_Jessie_rel_3.txt description and basic usage of different peripherals at at the GitHub page]

Image build instructions and required files for latest Debian Jessie release might be found here: [https://github.com/OLIMEX/OLINUXINO/blob/master/SOFTWARE/A20/A20-build-3.4.103-release-8/BUILD_DESCRIPTION_A20_Olimex_kernel_3.4.103%2B_Jessie_rel_8.txt build instructions and required files at the GitHub page]

You can find some older releases and older build instructions (older image revisions might be used as a reference, for testing purposes, or if you own old hardware revision of the board) at the following article: [[A20-OLinuXino-LIME2-older-releases|older releases and older build instructions]]

----

Note: the A20-LIME2-DEBIAN-SD card which we have in our web store contains the image suitable for board with no flash or board with NAND memory on a 8GB Class10 fast microSD card. The A20-LIME2-eMMC-DEBIAN-SD contains the image suitable for boards with extra eMMC memory. If you want to use our images, please, use card with speed Class10 or higher. Else the Linux performance would be very slow.

Note: in the previous Debian releases the Ethernet was auto-detected and initialized during boot BUT this was causing big delays in the start-up of the board if you didn't want to use Ethernet or if there wasn't Ethernet cable connected.

You can enable it by following these two steps:

1. To check under what name the LAN is associated write "ifconfig –a"

2. If, for example, it is under eth0 name, then write: "dhclient eth0"

This should enable the Ethernet and then SSH would also be available.

=== Android images ===

Torrents of official Android releases are below. Please read description of the image carefully.

'''Newest official release (recommended):'''

For the NAND flash memory:

Torrent of Android 4.2.2 release 1 for NAND memory (with HDMI and 7 inch 800x480 support - LCD-OLinuXino-7TS): [[Media:A20_Lime2_android_4_22_NAND_LCD7_HDMI_release1.torrent‎|A20-OLinuXino-Lime2 Android for NAND with HDMI and 7 inch display support]]

Torrent of Android 4.2.2 release 1 for NAND memory (with HDMI and 10 inch 1024x600 support - LCD-OLinuXino-10TS): [[Media:A20_Lime2_android_4_22_NAND_LCD10_HDMI_release1.torrent‎‎|A20-OLinuXino-Lime2 Android for NAND with HDMI and 10 inch display support]]

For microSD card:

Torrent of Android 4.2.2 release 2 for 8GB microSD card (with HDMI and 800x480 support): [[Media:A20_Lime2_Android_4.22_SD_card_LCD_800x480_HDMI_8GB_release_2.torrent‎‎‎‎|A20-OLinuXino-Lime2 Android for 8GB microSD card with HDMI and 7 inch display support]]

Torrent of Android 4.2.2 release 2 for 8GB microSD card (with HDMI and 1024x600 support):
[[Media:A20_Lime2_Android_4.22_SD_card_LCD_1024x600_HDMI.torrent|A20-OLinuXino-Lime2 Android for 8GB microSD card with HDMI and 10 inch display support, this image requires loading via PhoenixSuit, refer to the FAQ section at the end of this page]]

Torrent of Android 4.2.2 release 1 for 4GB microSD card (with HDMI and 800x480 support): [[Media:A20_Lime2_Android_4.22_SD_card_LCD_800x480_HDMI_release_1.torrent‎‎‎‎|A20-OLinuXino-Lime2 Android for 4GB microSD card with HDMI and 7 inch display support]]

Build instructions and source files for the official Android images for A20 boards in this repository: https://github.com/hehopmajieh/olinuxino_configs

== Notable unofficial images ==

Below you would find locations to images released by the community. These are not officially supported by Olimex, however, some of these releases are pretty good and worth a try:

*A number of very good and optimized A20-OLinuXino-LIME2 Armbian images: [https://www.armbian.com/olimex-lime-2/ link to LIME2 article at Armbian's web-site]

*A20-OLinuXino-LIME2 is supported by openSUSE Factory, installation instructions might be found here: [https://en.opensuse.org/HCL:A20-OLinuXIno-LIME2 openSUSE wiki link]

*A20-OLinuXino-LIME2 is recognized by the Devuan community and there are official releases here might be found here: [https://files.devuan.org/devuan_ascii/embedded/ Devuan list of files link]
 

== Documents ==

===A20-OLinuXino-LIME2 user's manual===
[https://www.olimex.com/Products/OLinuXino/A20/A20-OLinuXIno-LIME2/resources/A20-OLinuXino-LIME2-UM.pdf User's manual for A20-OLinuXino-LIME2 and A20-OLinuXino-LIME2-4GB]

=== A20 Brief ===
[https://github.com/OLIMEX/OLINUXINO/blob/master/HARDWARE/A20-PDFs/A20%20brief%2020130407.pdf A20 brief]

=== A20 Datasheet ===

[https://github.com/OLIMEX/OLINUXINO/blob/master/HARDWARE/A20-PDFs/A20%20Datasheet%20v1.0%2020130227.pdf A20 Datasheet]

=== A20 User Manual ===

[https://github.com/OLIMEX/OLINUXINO/blob/master/HARDWARE/A20-PDFs/A20%20User%20Manual%202013-03-22.pdf A20 user's manual]

== Hardware ==

===LIME2 shield templates===
[https://github.com/OLIMEX/OLINUXINO/tree/master/HARDWARE/A20-OLinuXino-LIME2 Eagle and KiCAD shield templates for LIME2]

===GPIO description===

[https://github.com/OLIMEX/OLINUXINO/blob/master/HARDWARE/A20-OLinuXino-LIME2/3.%20Templates%20and%20more/A20_LIME2_GPIOs.pdf A20-OLinuXino-LIME2 GPIO description]

A template that might be used to create custom shields or own adapters might be downloaded for Eagle or KiCad at the GitHub here: [https://github.com/OLIMEX/OLINUXINO/tree/master/HARDWARE/A20-OLinuXino-LIME2 shield template]

===Power supply and consumption===

A20-OLinuXino-LIME2 requires 5V regulated power supply external source. regulated means that the power supply adapter should provide exactly 5V no matter loaded or unloaded (some cheap wallwart adapters are not regulated and under no load their power supply may be higher than 5V although marked as 5V power supply, please measure with voltmeter if your power supply provide 5V as if you connect more than 5V to LIME it will be damaged!!!)

The power jack is standard [https://www.olimex.com/wiki/PWRJACK OLIMEX power jack].

A20-OLinuXino-LIME can be powered from three sources:
*+5VDC voltage applied PWR jack
*+3.7V from LiPo re-chargable battery connected to LiPo board connector
*+5V applied to USB-OTG connector

Power consumption is as follows:
*LiPo 3.7V power battery: 1.2W
*+5VDC input power: 1.3W

Comparison table of power consumption might be found at the following [https://www.olimex.com/Products/OLinuXino/_resources/OLinuXino-Consumption.pdf link].

LiPo battery allow backup power supply when main power is interrupted. A20-OLinuXino-LIME2 has power managment IC which charge the battery when main power is present, when power is interrupted the LiPo battery automatically provide backup power supply. Step-up converter prvide 5V for the USB peripherials too. For LiPo batteries we recommend these:
*[https://www.olimex.com/Products/Power/BATTERY-LIPO1400mAh/ 1400mAh]
*[https://www.olimex.com/Products/Power/BATTERY-LIPO3000mAh/ 3000mAh]
*[https://www.olimex.com/Products/Power/BATTERY-LIPO4400mAh/ 4400mAh]
*[https://www.olimex.com/Products/Power/BATTERY-LIPO6600mAh/ 6600mAh]
 

===Board dimensions===

A20-OLinuXino-LIME2 basic dimensions in mils: 3305.5 x 2347.0

Some additional measures might be seen in the image of A10-OLinuXino-LIME which has almost identical layout. It is available as .png here:
[https://www.olimex.com/Products/OLinuXino/A10/A10-OLinuXino-LIME/resources/A10-LIME-dimensions.png link]

===CAD files===

A20-OLinuXino-LIME2 is an Open Source Hardware, CAD files are available at [https://github.com/OLIMEX/OLINUXINO/tree/master/HARDWARE/A20-OLinuXino-LIME2 GitHub]

The CAD product used to design OLinuXino is Eagle and you can download evaluation free version from their [http://www.cadsoftusa.com/ web].

===Board Layout===

[[File:A20-OLinuXino-LIME2_top_naming_extras.jpg|650px]]

[[File:A20-OLinuXino-LIME2 bottom naming.jpg|650px]]

== Software ==

===Linux Commands===

[[Linux-Commands]] Brief Linux Command reference

===Python library for GPIO, I2C and SPI control===

The Debian Linux Python package for A20-OLinuXino-LIME2 is called pyA20Lime2. It makes the access to GPIO, I2C and SPI considerably easier. It is installed in the default Debian image. More information and examples on how it can be used might be found here:

[https://pypi.python.org/pypi/pyA20Lime2 Link to pyA20Lime2 package at python.org]

===GPIO under Linux===

GPIOs are located in /sys/class/gpio directory. Note that first you have to export GPIOs. For example:

add gpioPH2

root@A20:~# echo 20 > /sys/class/gpio/export

make PH2 output

root@A20:~# echo out > //sys/class/gpio/gpio20_ph2/direction

turn on onboard LED(connected to PH2)

root@A20:~# echo 1 > /sys/class/gpio/gpio20_ph2/value

turn off onboard LED(connected to PH2)

root@A20:~# echo 0 > /sys/class/gpio/gpio20_ph2/value

Full list with supported GPIOs is:

gpio21_ph7 gpio33_ph20 gpio45_pb12 gpio57_pi2 gpio69_pi14
gpio10_pg11 gpio22_ph9 gpio34_ph21 gpio46_pb13 gpio58_pi3 gpio6_pg5
gpio11_pc3 gpio23_ph10 gpio35_ph22 gpio47_pb14 gpio59_pi4 gpio70_pi15
gpio12_pc18 gpio24_ph11 gpio36_ph23 gpio48_pb15 gpio5_pg4 gpio71_pi16
gpio13_pc19 gpio25_ph12 gpio37_pb3 gpio49_pb16 gpio60_pi5 gpio72_pi17
gpio14_pc20 gpio26_ph13 gpio38_pb4 gpio4_pg3 gpio61_pi6 gpio73_pi18
gpio15_pc21 gpio27_ph14 gpio39_pb5 gpio50_pb17 gpio62_pi7 gpio74_pi19
gpio16_pc22 gpio28_ph15 gpio3_pg2 gpio51_ph24 gpio63_pi8 gpio75_pi20
gpio17_pc23 gpio29_ph16 gpio40_pb6 gpio52_ph25 gpio64_pi9 gpio7_pg6
gpio18_pc24 gpio2_pg1 gpio41_pb7 gpio53_ph26 gpio65_pi10 gpio8_pg7
gpio19_ph0 gpio30_ph17 gpio42_pb8 gpio54_ph27 gpio66_pi11 gpio9_pg8
gpio1_pg0 gpio31_ph18 gpio43_pb10 gpio55_pi0 gpio67_pi12 gpiochip1
gpio20_ph2 gpio32_ph19 gpio44_pb11 gpio56_pi1 gpio68_pi13

===Add Voice to your OLinuXino project===

[http://olimex.wordpress.com/2013/10/03/make-things-talk-with-olinuxino/ Installation of Festival on OLinuXino]
 

== How To? ==
===How to generate boot-able SD-card Debian Linux image for A20-OLinuXino-LIME2? ===

Build instructions and required files for the latest Debian images: [https://github.com/OLIMEX/OLINUXINO/tree/master/SOFTWARE/A20 instructions and files at the GitHub page]

Note that Linux-Sunxi Kernel is a work-in-progress, this means you can try the current stage/sunxi-x.x branch but if something is broken and doesn't work just revert to the git tags we give in the blog and they would work for sure.

[https://github.com/linux-sunxi/u-boot-sunxi/wiki Sunxi u-boot loader] The linux-sunxi git page contains a lot of sources for all Olimex Allwinner boards.

===How to connect a display and adjust the video output resolution?===
There is a separate article on the subject: [[how to connect display to a Lime board]]
 

=== Is it possible to boot Debian from NAND? Do you provide such image?===

Yes, it is possible. Use the latest Debian Jessie image and write "nandinstall". More information can be found in this wiki article: [[How_to_install_Debian_to_NAND| installing Debian Jessie to the 4GB NAND memory]]

There are other people who are also successful in booting Debian from the NAND. Make sure to check on the forum. Make sure to check the number of very good and optimized A20-OLinuXino Debian images by Igor Pečovnik. There are also his instructions for NAND installation of Debian: [http://www.armbian.com/download/ link to his web-site]

===How to detect and enable the Ethernet controller (if it is disabled by default)? ===

Note: in the previous Debian releases the Ethernet was auto-detected and initialized during boot BUT this was causing big delays in the start-up of the board if you didn't want to use Ethernet or if there wasn't Ethernet cable connected.

You can enable it by following these two steps:

1. To check under what name the LAN is associated write "ifconfig –a"

2. If, for example, it is under eth0 name, then write: "dhclient eth0"

This should enable the Ethernet and then SSH would also be available.

===How to download new Android image to the NAND memory of my A20 board?===

Follow these steps to download the image to the NAND memory:

*1. Install and run PhoenixSuit (can be found here: [https://drive.google.com/file/d/0BwplT87k9SCgaTFTZnVST05ONzA/view?usp=sharing download from google drive]).

*2. Go to firmware tab of the program and point to a valid Android image (the latest official one may also be downloaded above).

*3. Disconnect the power supply and USB cable from the A20 board.

*4. Press and hold RECOVERY button, apply power supply 5V, release RECOVERY button.

*5. Connect USB cable to the mini USB connector.

*6. You will be asked for drivers for the bootloader. Navigate to the folder where you extracted the PhoenixSuit and install the drivers from the respective executables (or manually point the installer to the drivers folder in the PhoenixSuit installation path).

*7. PhoenixSuit will detect the board and would ask for the method of writing the image. Choose method of writing the image and confirm your wish to write the image.

*8. Wait till upgrade succeeds

Note that it is not recommended to have your mini USB connected to an external USB hub. This might cause delays and might distort the signal levels. Always test with the USB connected straight to the USB ports of your computer.

===How to generate Arch Linux image?===

Recent forum post by user progmetalbg here: [https://www.olimex.com/forum/index.php?topic=4261.0| at Olimex forums]

[http://alarma20.wordpress.com/2013/09/13/howto-build-arch-linux-arm-for-a20-olinuxino-micro/ Older step by step instructions on how to build Arch Linux image for another A20 board]

===How do I write the official Android image to a micro SD card for my A20 board?===
A: First download one of the official Android images, which might be found in the Android section above.

Make sure that the download link you visit clearly indicates that the image is suitable for the microSD card since there are images suitable for NAND memory also. The images suitable for the microSD memory and those suitable for NAND card are different. However, the upload method is almost identical – using PhoenixSuit.

There are two types of Android images for microSD card that we usually provide and each of them has to be downloaded to a microSD card using a different method. The image provided for microSD card is either the native Android image that can be downloaded to the card via a software tool like PhoenixSuit (through the board) or an image taken from an already prepared microSD card that requires to simply write the image (through a microSD card reader).

'''It is more likely that you have an Android image that requires a simple copy to a card. If that is the case you can follow the exact steps as for Linux (e.g. using "Win32 Disk Imager" or "dd" command).'''

In order to prepare a microSD card with a native Android you will need a software tool called PhoenixSuit and then:

• Install and run PhoenixSuit (can be found here: [https://drive.google.com/file/d/0BwplT87k9SCgaTFTZnVST05ONzA/view?usp=sharing download from google drive])

• Go to the firmware tab of the program and point to a valid Android image (note that the
images on Gdrive are compressed and you have to extract them to .img files to be able write
them with PhoenixSuit)

• Disconnect the power supply and USB cable from the A20 board. Put an SD card in micro SD
holder. We recommend either a 4GB or a 8GB class 10 card.

• Press and hold RECOVERY button, apply power supply 5V, release RECOVERY button.

• Connect USB cable to the mini USB connector.

• You will be asked for drivers for the boot-loader. Navigate to the folder where you extracted the PhoenixSuit and install the drivers from the respective executables (or manually point the installer to the drivers folder in the PhoenixSuit installation path).

• PhoenixSuit will detect the board and would ask for the method of writing the image. Choose
method of writing the image and confirm your wish to write the image.

• Wait till upgrade succeeds

Note that it is not recommended to have your mini USB connected to an external USB hub. This
might cause delays and might distort the signal levels. Always test with the USB connected straight to the USB ports of your computer.

Important: When Android runs for very first time it takes several minutes to initialize all files and buffers please do not cut the power supply during this process! Also when fresh image is installed fast boot may be disabled, which means that when you apply power supply after few seconds Android will go in sleep mode and you have to press POWER button to start it, you can change to fast boot when you power off there is dialog box asking you if you want next boot to be fast boot, you have to check this box before you power off. Also note that you must do touch screen calibration when you run Android for very first time which might require a mouse.

===I don't have neither serial cable, nor HDMI monitor. I also can't access the local Ethernet network. Can I somehow access the board anyway?===

The latest official Debian Linux image allows the use the USB_OTG connector for SSH connection without the need of a LAN cable or a serial cable. You can use a mini USB cable connected between your host PC and the on-board mini USB connector. For connection convenience there is a DHCP server running specifically for USB0 interface. The DHCP server should give IP address to the new USB0 interface of your host PC so you can make SSH connection from your PC to the default board IP address of the USB0 interface – 192.168.2.1.

You can connect to the board using a mini USB cable and an SSH client (if you use Windows you might use "puTTY", for example) at address 192.168.2.1.

For Windows operating system - upon connection, the board should show up in "Windows Device Manager" as "RNDIS Ethernet Gadget". You might be asked to install a driver. The drivers can be found online as "RNDIS driver" (Remote Network Driver Interface Specification). The drivers are provided by Microsoft and they should be available for every Windows distribution - refer to the respective files and articles provided by Microsoft on how to install the required drivers.

===How to edit board configurations and definitions in the official Debian Linux? ===

Do you want a custom video resolution output? Do you need a different port definition? Do you need to change the hardware defitions of the board?

You would need to edit the board's script.bin/script.fex file. How to do it is described in another separate article: [[how to edit board configurations and definitions in the official Debian Linux]].

===How to add STK1160 video capture driver support in Kernel 3.4===

[https://www.olimex.com/wiki/STK1160-howto-linux-sunxi-3_4 STK1160] driver backport by Dimitar Tomov
[[Main_Page]]

A20-OLinuXino-LIME2

2024-09-30T07:44:36Z

LubOlimex: /* Linux images */

[[File:A20-OLinuXino-LIME2.jpg|600px]]

A20-OLinuXino-LIME2 looks similar to both [[A20-OLinuXino-LIME]] and [[A10-OLinuXino-LIME]]. The major differences between A20-OLinuXino-LIME2 and A20-OLinuXino-LIME are:

*LIME2 has gigabit Ethernet (GbE), compared to the standard 100Mb Ethernet of the LIME
*LIME2 design provides double the RAM memory, compared to the LIME design (1024 vs 512)
*Much better routing of DDR3 memory.
*Increased the number of layers from 6 in LIME to 8 in LIME2
*Corrected pinout of the LCD and GPIO connectors (shields designed for the LIME layout are not compatible with the LIME2 layout)

The A10 and the A20 processors are pin-to-pin compatible. Because of the processor, software-wise the board is closer to [[A20-OLinuXino-LIME]] than to the [[A10-OLinuXino-LIME]]. This resemblance to other designs definitely might speed the development on the board - a lot of software written for A20-OLinuXino-LIME might work out-of-the-box with A20-OLinuXino-LIME2. Additionally, pinout tables, GPIO maps, etc released for A20-OLinuXino-LIME would apply to A20-OLinuXino-LIME2 (except for the 0.05" step connectors - LCD display and all the GPIOs connectors, which have a different layout compared to both A20-OLinuXino-LIME and A10-OLinuXino-LIME).

A20-OLinuXino-LIME2 features:
*A20 Cortex-A7 dual-core ARM Cortex-A7 CPU and dual-core Mali 400 GPU
*'''1GB DDR3 RAM memory'''
*'''1 gigabit native Ethernet'''
*optional 4GB NAND FLASH memory
*SATA connector with 5V SATA power jack
*HDMI FullHD 1080p
*2x USB Low-Full-High-Speed hosts with power control and current limiter
*USB-OTG with power control and current limiter
*LiPo Battery connector with battery-charging capabilities
*LCD connector compatible with with 4.3", 7.0", 10.1" LCD modules from Olimex
*160 GPIOs on three GPIO connectors
*MicroSD card connector
*DEBUG-UART connector for console debug with USB-SERIAL-CABLE-F
*status LED
*Battery charge status LED
*Power LED
*2KB EEPROM for MAC address storage and more
*2 BUTTONS with ANDROID functionality + RESET button
*2 mount holes
*5V input power supply, noise immune design
*PCB dimensions: 84 x 60 mm

== Official Images from OLIMEX ==

In this chapter you would find links to torrents with the official Debian and Android images. The images in this chapter were compiled by Olimex. They are recommended for beginners and first time users since they include full hardware support. If you are experienced Linux professional you might find useful our build instructions also published here.

The downloaded file xxxx.7z is an archive of xxx.img file. In order to write the image on SD card you have to extract the xxx.7z file.

*For Windows: use 7zip and then use Win32DiskImager.exe (http://sourceforge.net/projects/win32diskimager/) to write the image

*For Linux: use p7zip package. If you don't have 7zip installed first install it 

#apt-get install p7zip
Copy a20_Lime2_debian_second_release.7z file in your directory and unzip the archive with
#7za e a20_Lime2_debian_second_release.7z
where a20_Lime2_debian_second_release.7z
The output should be a new 4GB file with extension img
Put 4GB SD card in your card reader and type
# ls /dev/sd
Then press two times <TAB> you will see a list of your sd devices like sda sdb sdc note that some of these devices may be your hard disk so make sure you know which one is your sd card before you proceed as you can damage your HDD if you choose the wrong sd-device. You can do this by unplugging your sd card reader and identify which "sd" devices remove from the list.
Once you know which device is your sdcard like sda use this text instead of the sdX name in the references below:
#dd if=a20_Lime2_debian_second_release.img of=/dev/sdX

The Debian Linux image is 4GB and the file system can be extended to suit a bigger card. Use the following three commands to execute a script that would use all the free space of your card:

sudo su
./resize_sd.sh /dev/mmcblk0 2
reboot

=== Linux images ===

These official Debian images should be downloaded to a microSD card. Older sunxi images can be found as direct downloads at our FTP. You can install the Debian to the NAND or the eMMC of your board (if it comes with one). Information on booting Debian from the NAND might be found in these wiki articles: [[how to install Debian to NAND]]; [[how to install Debian to eMMC]]. Download locations for the official images might be found below:

'''ALWAYS FIRST TEST WITH LATEST OFFICIAL IMAGE, NEWER HARDWARE REVISIONS OF THE BOARD MIGHT NOT WORK WITH OLDER IMAGES!!!'''

----

'''Latest stable official images - Debian 8 (Jessie)''' '''Both images are suitable for the standard version A20-OLinuXino-LIME2. However A20-OLinuXino-LIME2-n4GB and A20-OLinuXino-LIME2-n8GB have different image compared to A20-OLinuXino-LIME2-e4GB''':'''

FTP location for official Debian Jessie release #13 for A20-OLinuXino-LIME2, A20-OLinuXino-LIME2-n4GB, and A20-OLinuXino-LIME2-n8GB (not suitable for boards with eMMC flash): [https://ftp.olimex.com/Allwinner_Images/A20-OLinuXino-LIME2/Debian/sd/a20-lime2_mainline_uboot_sunxi_kernel_3.4.103_jessie_NAND_rel_13.img.7z A20-OLinuXino-LIME2 Debian Jessie with kernel 3.4.103+ release 13]

Torrent of official Debian Jessie release #15 for A20-OLinuXino-LIME2, A20-OLinuXino-LIME2-e4GB (not suitable for boards with NAND flash): [[Media:A20-lime2_mainline_uboot_sunxi_kernel_3.4.103_jessie_eMMC_rel_16.torrent|A20 lime2 mainline uboot sunxi kernel 3.4.103 jessie eMMC rel 16]]

Image description and typical interfacing: [https://github.com/OLIMEX/OLINUXINO/blob/master/SOFTWARE/A20/A20-build-3.4.103-release-7/USAGE-AND-COMMON-PRACTICEs-A20-Olimex_kernel_3.4.103%2B_Jessie_rel_3.txt description and basic usage of different peripherals at at the GitHub page]

Image build instructions and required files for latest Debian Jessie release might be found here: [https://github.com/OLIMEX/OLINUXINO/blob/master/SOFTWARE/A20/A20-build-3.4.103-release-8/BUILD_DESCRIPTION_A20_Olimex_kernel_3.4.103%2B_Jessie_rel_8.txt build instructions and required files at the GitHub page]

You can find some older releases and older build instructions (older image revisions might be used as a reference, for testing purposes, or if you own old hardware revision of the board) at the following article: [[A20-OLinuXino-LIME2-older-releases|older releases and older build instructions]]

----

Note: the A20-LIME2-DEBIAN-SD card which we have in our web store contains the image suitable for board with no flash or board with NAND memory on a 8GB Class10 fast microSD card. The A20-LIME2-eMMC-DEBIAN-SD contains the image suitable for boards with extra eMMC memory. If you want to use our images, please, use card with speed Class10 or higher. Else the Linux performance would be very slow.

Note: in the previous Debian releases the Ethernet was auto-detected and initialized during boot BUT this was causing big delays in the start-up of the board if you didn't want to use Ethernet or if there wasn't Ethernet cable connected.

You can enable it by following these two steps:

1. To check under what name the LAN is associated write "ifconfig –a"

2. If, for example, it is under eth0 name, then write: "dhclient eth0"

This should enable the Ethernet and then SSH would also be available.

=== Android images ===

Torrents of official Android releases are below. Please read description of the image carefully.

'''Newest official release (recommended):'''

For the NAND flash memory:

Torrent of Android 4.2.2 release 1 for NAND memory (with HDMI and 7 inch 800x480 support - LCD-OLinuXino-7TS): [[Media:A20_Lime2_android_4_22_NAND_LCD7_HDMI_release1.torrent‎|A20-OLinuXino-Lime2 Android for NAND with HDMI and 7 inch display support]]

Torrent of Android 4.2.2 release 1 for NAND memory (with HDMI and 10 inch 1024x600 support - LCD-OLinuXino-10TS): [[Media:A20_Lime2_android_4_22_NAND_LCD10_HDMI_release1.torrent‎‎|A20-OLinuXino-Lime2 Android for NAND with HDMI and 10 inch display support]]

For microSD card:

Torrent of Android 4.2.2 release 2 for 8GB microSD card (with HDMI and 800x480 support): [[Media:A20_Lime2_Android_4.22_SD_card_LCD_800x480_HDMI_8GB_release_2.torrent‎‎‎‎|A20-OLinuXino-Lime2 Android for 8GB microSD card with HDMI and 7 inch display support]]

Torrent of Android 4.2.2 release 2 for 8GB microSD card (with HDMI and 1024x600 support):
[[Media:A20_Lime2_Android_4.22_SD_card_LCD_1024x600_HDMI.torrent|A20-OLinuXino-Lime2 Android for 8GB microSD card with HDMI and 10 inch display support, this image requires loading via PhoenixSuit, refer to the FAQ section at the end of this page]]

Torrent of Android 4.2.2 release 1 for 4GB microSD card (with HDMI and 800x480 support): [[Media:A20_Lime2_Android_4.22_SD_card_LCD_800x480_HDMI_release_1.torrent‎‎‎‎|A20-OLinuXino-Lime2 Android for 4GB microSD card with HDMI and 7 inch display support]]

Build instructions and source files for the official Android images for A20 boards in this repository: https://github.com/hehopmajieh/olinuxino_configs

== Notable unofficial images ==

Below you would find locations to images released by the community. These are not officially supported by Olimex, however, some of these releases are pretty good and worth a try:

*A number of very good and optimized A20-OLinuXino-LIME2 Armbian images: [https://www.armbian.com/olimex-lime-2/ link to LIME2 article at Armbian's web-site]

*A20-OLinuXino-LIME2 is supported by openSUSE Factory, installation instructions might be found here: [https://en.opensuse.org/HCL:A20-OLinuXIno-LIME2 openSUSE wiki link]

*A20-OLinuXino-LIME2 is recognized by the Devuan community and there are official releases here might be found here: [https://files.devuan.org/devuan_ascii/embedded/ Devuan list of files link]
 

== Documents ==

===A20-OLinuXino-LIME2 user's manual===
[https://www.olimex.com/Products/OLinuXino/A20/A20-OLinuXIno-LIME2/resources/A20-OLinuXino-LIME2-UM.pdf User's manual for A20-OLinuXino-LIME2 and A20-OLinuXino-LIME2-4GB]

=== A20 Brief ===
[https://github.com/OLIMEX/OLINUXINO/blob/master/HARDWARE/A20-PDFs/A20%20brief%2020130407.pdf A20 brief]

=== A20 Datasheet ===

[https://github.com/OLIMEX/OLINUXINO/blob/master/HARDWARE/A20-PDFs/A20%20Datasheet%20v1.0%2020130227.pdf A20 Datasheet]

=== A20 User Manual ===

[https://github.com/OLIMEX/OLINUXINO/blob/master/HARDWARE/A20-PDFs/A20%20User%20Manual%202013-03-22.pdf A20 user's manual]

== Hardware ==

===LIME2 shield templates===
[https://github.com/OLIMEX/OLINUXINO/tree/master/HARDWARE/A20-OLinuXino-LIME2 Eagle and KiCAD shield templates for LIME2]

===GPIO description===

[https://github.com/OLIMEX/OLINUXINO/blob/master/HARDWARE/A20-OLinuXino-LIME2/3.%20Templates%20and%20more/A20_LIME2_GPIOs.pdf A20-OLinuXino-LIME2 GPIO description]

A template that might be used to create custom shields or own adapters might be downloaded for Eagle or KiCad at the GitHub here: [https://github.com/OLIMEX/OLINUXINO/tree/master/HARDWARE/A20-OLinuXino-LIME2 shield template]

===Power supply and consumption===

A20-OLinuXino-LIME2 requires 5V regulated power supply external source. regulated means that the power supply adapter should provide exactly 5V no matter loaded or unloaded (some cheap wallwart adapters are not regulated and under no load their power supply may be higher than 5V although marked as 5V power supply, please measure with voltmeter if your power supply provide 5V as if you connect more than 5V to LIME it will be damaged!!!)

The power jack is standard [https://www.olimex.com/wiki/PWRJACK OLIMEX power jack].

A20-OLinuXino-LIME can be powered from three sources:
*+5VDC voltage applied PWR jack
*+3.7V from LiPo re-chargable battery connected to LiPo board connector
*+5V applied to USB-OTG connector

Power consumption is as follows:
*LiPo 3.7V power battery: 1.2W
*+5VDC input power: 1.3W

Comparison table of power consumption might be found at the following [https://www.olimex.com/Products/OLinuXino/_resources/OLinuXino-Consumption.pdf link].

LiPo battery allow backup power supply when main power is interrupted. A20-OLinuXino-LIME2 has power managment IC which charge the battery when main power is present, when power is interrupted the LiPo battery automatically provide backup power supply. Step-up converter prvide 5V for the USB peripherials too. For LiPo batteries we recommend these:
*[https://www.olimex.com/Products/Power/BATTERY-LIPO1400mAh/ 1400mAh]
*[https://www.olimex.com/Products/Power/BATTERY-LIPO3000mAh/ 3000mAh]
*[https://www.olimex.com/Products/Power/BATTERY-LIPO4400mAh/ 4400mAh]
*[https://www.olimex.com/Products/Power/BATTERY-LIPO6600mAh/ 6600mAh]
 

===Board dimensions===

A20-OLinuXino-LIME2 basic dimensions in mils: 3305.5 x 2347.0

Some additional measures might be seen in the image of A10-OLinuXino-LIME which has almost identical layout. It is available as .png here:
[https://www.olimex.com/Products/OLinuXino/A10/A10-OLinuXino-LIME/resources/A10-LIME-dimensions.png link]

===CAD files===

A20-OLinuXino-LIME2 is an Open Source Hardware, CAD files are available at [https://github.com/OLIMEX/OLINUXINO/tree/master/HARDWARE/A20-OLinuXino-LIME2 GitHub]

The CAD product used to design OLinuXino is Eagle and you can download evaluation free version from their [http://www.cadsoftusa.com/ web].

===Board Layout===

[[File:A20-OLinuXino-LIME2_top_naming_extras.jpg|650px]]

[[File:A20-OLinuXino-LIME2 bottom naming.jpg|650px]]

== Software ==

===Linux Commands===

[[Linux-Commands]] Brief Linux Command reference

===Python library for GPIO, I2C and SPI control===

The Debian Linux Python package for A20-OLinuXino-LIME2 is called pyA20Lime2. It makes the access to GPIO, I2C and SPI considerably easier. It is installed in the default Debian image. More information and examples on how it can be used might be found here:

[https://pypi.python.org/pypi/pyA20Lime2 Link to pyA20Lime2 package at python.org]

===GPIO under Linux===

GPIOs are located in /sys/class/gpio directory. Note that first you have to export GPIOs. For example:

add gpioPH2

root@A20:~# echo 20 > /sys/class/gpio/export

make PH2 output

root@A20:~# echo out > //sys/class/gpio/gpio20_ph2/direction

turn on onboard LED(connected to PH2)

root@A20:~# echo 1 > /sys/class/gpio/gpio20_ph2/value

turn off onboard LED(connected to PH2)

root@A20:~# echo 0 > /sys/class/gpio/gpio20_ph2/value

Full list with supported GPIOs is:

gpio21_ph7 gpio33_ph20 gpio45_pb12 gpio57_pi2 gpio69_pi14
gpio10_pg11 gpio22_ph9 gpio34_ph21 gpio46_pb13 gpio58_pi3 gpio6_pg5
gpio11_pc3 gpio23_ph10 gpio35_ph22 gpio47_pb14 gpio59_pi4 gpio70_pi15
gpio12_pc18 gpio24_ph11 gpio36_ph23 gpio48_pb15 gpio5_pg4 gpio71_pi16
gpio13_pc19 gpio25_ph12 gpio37_pb3 gpio49_pb16 gpio60_pi5 gpio72_pi17
gpio14_pc20 gpio26_ph13 gpio38_pb4 gpio4_pg3 gpio61_pi6 gpio73_pi18
gpio15_pc21 gpio27_ph14 gpio39_pb5 gpio50_pb17 gpio62_pi7 gpio74_pi19
gpio16_pc22 gpio28_ph15 gpio3_pg2 gpio51_ph24 gpio63_pi8 gpio75_pi20
gpio17_pc23 gpio29_ph16 gpio40_pb6 gpio52_ph25 gpio64_pi9 gpio7_pg6
gpio18_pc24 gpio2_pg1 gpio41_pb7 gpio53_ph26 gpio65_pi10 gpio8_pg7
gpio19_ph0 gpio30_ph17 gpio42_pb8 gpio54_ph27 gpio66_pi11 gpio9_pg8
gpio1_pg0 gpio31_ph18 gpio43_pb10 gpio55_pi0 gpio67_pi12 gpiochip1
gpio20_ph2 gpio32_ph19 gpio44_pb11 gpio56_pi1 gpio68_pi13

===Add Voice to your OLinuXino project===

[http://olimex.wordpress.com/2013/10/03/make-things-talk-with-olinuxino/ Installation of Festival on OLinuXino]
 

== How To? ==
===How to generate boot-able SD-card Debian Linux image for A20-OLinuXino-LIME2? ===

Build instructions and required files for the latest Debian images: [https://github.com/OLIMEX/OLINUXINO/tree/master/SOFTWARE/A20 instructions and files at the GitHub page]

Note that Linux-Sunxi Kernel is a work-in-progress, this means you can try the current stage/sunxi-x.x branch but if something is broken and doesn't work just revert to the git tags we give in the blog and they would work for sure.

[https://github.com/linux-sunxi/u-boot-sunxi/wiki Sunxi u-boot loader] The linux-sunxi git page contains a lot of sources for all Olimex Allwinner boards.

===How to connect a display and adjust the video output resolution?===
There is a separate article on the subject: [[how to connect display to a Lime board]]
 

=== Is it possible to boot Debian from NAND? Do you provide such image?===

Yes, it is possible. Use the latest Debian Jessie image and write "nandinstall". More information can be found in this wiki article: [[How_to_install_Debian_to_NAND| installing Debian Jessie to the 4GB NAND memory]]

There are other people who are also successful in booting Debian from the NAND. Make sure to check on the forum. Make sure to check the number of very good and optimized A20-OLinuXino Debian images by Igor Pečovnik. There are also his instructions for NAND installation of Debian: [http://www.armbian.com/download/ link to his web-site]

===How to detect and enable the Ethernet controller (if it is disabled by default)? ===

Note: in the previous Debian releases the Ethernet was auto-detected and initialized during boot BUT this was causing big delays in the start-up of the board if you didn't want to use Ethernet or if there wasn't Ethernet cable connected.

You can enable it by following these two steps:

1. To check under what name the LAN is associated write "ifconfig –a"

2. If, for example, it is under eth0 name, then write: "dhclient eth0"

This should enable the Ethernet and then SSH would also be available.

===How to download new Android image to the NAND memory of my A20 board?===

Follow these steps to download the image to the NAND memory:

*1. Install and run PhoenixSuit (can be found here: [https://drive.google.com/file/d/0BwplT87k9SCgaTFTZnVST05ONzA/view?usp=sharing download from google drive]).

*2. Go to firmware tab of the program and point to a valid Android image (the latest official one may also be downloaded above).

*3. Disconnect the power supply and USB cable from the A20 board.

*4. Press and hold RECOVERY button, apply power supply 5V, release RECOVERY button.

*5. Connect USB cable to the mini USB connector.

*6. You will be asked for drivers for the bootloader. Navigate to the folder where you extracted the PhoenixSuit and install the drivers from the respective executables (or manually point the installer to the drivers folder in the PhoenixSuit installation path).

*7. PhoenixSuit will detect the board and would ask for the method of writing the image. Choose method of writing the image and confirm your wish to write the image.

*8. Wait till upgrade succeeds

Note that it is not recommended to have your mini USB connected to an external USB hub. This might cause delays and might distort the signal levels. Always test with the USB connected straight to the USB ports of your computer.

===How to generate Arch Linux image?===

Recent forum post by user progmetalbg here: [https://www.olimex.com/forum/index.php?topic=4261.0| at Olimex forums]

[http://alarma20.wordpress.com/2013/09/13/howto-build-arch-linux-arm-for-a20-olinuxino-micro/ Older step by step instructions on how to build Arch Linux image for another A20 board]

===How do I write the official Android image to a micro SD card for my A20 board?===
A: First download one of the official Android images, which might be found in the Android section above.

Make sure that the download link you visit clearly indicates that the image is suitable for the microSD card since there are images suitable for NAND memory also. The images suitable for the microSD memory and those suitable for NAND card are different. However, the upload method is almost identical – using PhoenixSuit.

There are two types of Android images for microSD card that we usually provide and each of them has to be downloaded to a microSD card using a different method. The image provided for microSD card is either the native Android image that can be downloaded to the card via a software tool like PhoenixSuit (through the board) or an image taken from an already prepared microSD card that requires to simply write the image (through a microSD card reader).

'''It is more likely that you have an Android image that requires a simple copy to a card. If that is the case you can follow the exact steps as for Linux (e.g. using "Win32 Disk Imager" or "dd" command).'''

In order to prepare a microSD card with a native Android you will need a software tool called PhoenixSuit and then:

• Install and run PhoenixSuit (can be found here: [https://drive.google.com/file/d/0BwplT87k9SCgaTFTZnVST05ONzA/view?usp=sharing download from google drive])

• Go to the firmware tab of the program and point to a valid Android image (note that the
images on Gdrive are compressed and you have to extract them to .img files to be able write
them with PhoenixSuit)

• Disconnect the power supply and USB cable from the A20 board. Put an SD card in micro SD
holder. We recommend either a 4GB or a 8GB class 10 card.

• Press and hold RECOVERY button, apply power supply 5V, release RECOVERY button.

• Connect USB cable to the mini USB connector.

• You will be asked for drivers for the boot-loader. Navigate to the folder where you extracted the PhoenixSuit and install the drivers from the respective executables (or manually point the installer to the drivers folder in the PhoenixSuit installation path).

• PhoenixSuit will detect the board and would ask for the method of writing the image. Choose
method of writing the image and confirm your wish to write the image.

• Wait till upgrade succeeds

Note that it is not recommended to have your mini USB connected to an external USB hub. This
might cause delays and might distort the signal levels. Always test with the USB connected straight to the USB ports of your computer.

Important: When Android runs for very first time it takes several minutes to initialize all files and buffers please do not cut the power supply during this process! Also when fresh image is installed fast boot may be disabled, which means that when you apply power supply after few seconds Android will go in sleep mode and you have to press POWER button to start it, you can change to fast boot when you power off there is dialog box asking you if you want next boot to be fast boot, you have to check this box before you power off. Also note that you must do touch screen calibration when you run Android for very first time which might require a mouse.

===I don't have neither serial cable, nor HDMI monitor. I also can't access the local Ethernet network. Can I somehow access the board anyway?===

The latest official Debian Linux image allows the use the USB_OTG connector for SSH connection without the need of a LAN cable or a serial cable. You can use a mini USB cable connected between your host PC and the on-board mini USB connector. For connection convenience there is a DHCP server running specifically for USB0 interface. The DHCP server should give IP address to the new USB0 interface of your host PC so you can make SSH connection from your PC to the default board IP address of the USB0 interface – 192.168.2.1.

You can connect to the board using a mini USB cable and an SSH client (if you use Windows you might use "puTTY", for example) at address 192.168.2.1.

For Windows operating system - upon connection, the board should show up in "Windows Device Manager" as "RNDIS Ethernet Gadget". You might be asked to install a driver. The drivers can be found online as "RNDIS driver" (Remote Network Driver Interface Specification). The drivers are provided by Microsoft and they should be available for every Windows distribution - refer to the respective files and articles provided by Microsoft on how to install the required drivers.

===How to edit board configurations and definitions in the official Debian Linux? ===

Do you want a custom video resolution output? Do you need a different port definition? Do you need to change the hardware defitions of the board?

You would need to edit the board's script.bin/script.fex file. How to do it is described in another separate article: [[how to edit board configurations and definitions in the official Debian Linux]].

===How to add STK1160 video capture driver support in Kernel 3.4===

[https://www.olimex.com/wiki/STK1160-howto-linux-sunxi-3_4 STK1160] driver backport by Dimitar Tomov
[[Main_Page]]

A20-OLinuXino-LIME2

2024-09-30T07:44:16Z

LubOlimex: /* Linux images */

[[File:A20-OLinuXino-LIME2.jpg|600px]]

A20-OLinuXino-LIME2 looks similar to both [[A20-OLinuXino-LIME]] and [[A10-OLinuXino-LIME]]. The major differences between A20-OLinuXino-LIME2 and A20-OLinuXino-LIME are:

*LIME2 has gigabit Ethernet (GbE), compared to the standard 100Mb Ethernet of the LIME
*LIME2 design provides double the RAM memory, compared to the LIME design (1024 vs 512)
*Much better routing of DDR3 memory.
*Increased the number of layers from 6 in LIME to 8 in LIME2
*Corrected pinout of the LCD and GPIO connectors (shields designed for the LIME layout are not compatible with the LIME2 layout)

The A10 and the A20 processors are pin-to-pin compatible. Because of the processor, software-wise the board is closer to [[A20-OLinuXino-LIME]] than to the [[A10-OLinuXino-LIME]]. This resemblance to other designs definitely might speed the development on the board - a lot of software written for A20-OLinuXino-LIME might work out-of-the-box with A20-OLinuXino-LIME2. Additionally, pinout tables, GPIO maps, etc released for A20-OLinuXino-LIME would apply to A20-OLinuXino-LIME2 (except for the 0.05" step connectors - LCD display and all the GPIOs connectors, which have a different layout compared to both A20-OLinuXino-LIME and A10-OLinuXino-LIME).

A20-OLinuXino-LIME2 features:
*A20 Cortex-A7 dual-core ARM Cortex-A7 CPU and dual-core Mali 400 GPU
*'''1GB DDR3 RAM memory'''
*'''1 gigabit native Ethernet'''
*optional 4GB NAND FLASH memory
*SATA connector with 5V SATA power jack
*HDMI FullHD 1080p
*2x USB Low-Full-High-Speed hosts with power control and current limiter
*USB-OTG with power control and current limiter
*LiPo Battery connector with battery-charging capabilities
*LCD connector compatible with with 4.3", 7.0", 10.1" LCD modules from Olimex
*160 GPIOs on three GPIO connectors
*MicroSD card connector
*DEBUG-UART connector for console debug with USB-SERIAL-CABLE-F
*status LED
*Battery charge status LED
*Power LED
*2KB EEPROM for MAC address storage and more
*2 BUTTONS with ANDROID functionality + RESET button
*2 mount holes
*5V input power supply, noise immune design
*PCB dimensions: 84 x 60 mm

== Official Images from OLIMEX ==

In this chapter you would find links to torrents with the official Debian and Android images. The images in this chapter were compiled by Olimex. They are recommended for beginners and first time users since they include full hardware support. If you are experienced Linux professional you might find useful our build instructions also published here.

The downloaded file xxxx.7z is an archive of xxx.img file. In order to write the image on SD card you have to extract the xxx.7z file.

*For Windows: use 7zip and then use Win32DiskImager.exe (http://sourceforge.net/projects/win32diskimager/) to write the image

*For Linux: use p7zip package. If you don't have 7zip installed first install it 

#apt-get install p7zip
Copy a20_Lime2_debian_second_release.7z file in your directory and unzip the archive with
#7za e a20_Lime2_debian_second_release.7z
where a20_Lime2_debian_second_release.7z
The output should be a new 4GB file with extension img
Put 4GB SD card in your card reader and type
# ls /dev/sd
Then press two times <TAB> you will see a list of your sd devices like sda sdb sdc note that some of these devices may be your hard disk so make sure you know which one is your sd card before you proceed as you can damage your HDD if you choose the wrong sd-device. You can do this by unplugging your sd card reader and identify which "sd" devices remove from the list.
Once you know which device is your sdcard like sda use this text instead of the sdX name in the references below:
#dd if=a20_Lime2_debian_second_release.img of=/dev/sdX

The Debian Linux image is 4GB and the file system can be extended to suit a bigger card. Use the following three commands to execute a script that would use all the free space of your card:

sudo su
./resize_sd.sh /dev/mmcblk0 2
reboot

=== Linux images ===

These official Debian images should be downloaded to a microSD card. Older sunxi images can be found as direct downloads at our FTP. You can install the Debian to the NAND or the eMMC of your board (if it comes with one). Information on booting Debian from the NAND might be found in these wiki articles: [[how to install Debian to NAND]]; [[how to install Debian to eMMC]]. Download locations for the official images might be found below:

'''ALWAYS FIRST TEST WITH LATEST OFFICIAL IMAGE, NEWER HARDWARE REVISIONS OF THE BOARD MIGHT NOT WORK WITH OLDER IMAGES!!!'''

----

'''Latest stable official images - Debian 8 (Jessie)''' '''Both images are suitable for the standard version A20-OLinuXino-LIME2. However A20-OLinuXino-LIME2-n4GB and A20-OLinuXino-LIME2-n8GB have different image compared to A20-OLinuXino-LIME2-e4GB''':'''

FTP location for official Debian Jessie release #13 for A20-OLinuXino-LIME2, A20-OLinuXino-LIME2-n4GB, and A20-OLinuXino-LIME2-n8GB (not suitable for boards with eMMC flash): [[Media:https://ftp.olimex.com/Allwinner_Images/A20-OLinuXino-LIME2/Debian/sd/a20-lime2_mainline_uboot_sunxi_kernel_3.4.103_jessie_NAND_rel_13.img.7z A20-OLinuXino-LIME2 Debian Jessie with kernel 3.4.103+ release 13]]

Torrent of official Debian Jessie release #15 for A20-OLinuXino-LIME2, A20-OLinuXino-LIME2-e4GB (not suitable for boards with NAND flash): [[Media:A20-lime2_mainline_uboot_sunxi_kernel_3.4.103_jessie_eMMC_rel_16.torrent|A20 lime2 mainline uboot sunxi kernel 3.4.103 jessie eMMC rel 16]]

Image description and typical interfacing: [https://github.com/OLIMEX/OLINUXINO/blob/master/SOFTWARE/A20/A20-build-3.4.103-release-7/USAGE-AND-COMMON-PRACTICEs-A20-Olimex_kernel_3.4.103%2B_Jessie_rel_3.txt description and basic usage of different peripherals at at the GitHub page]

Image build instructions and required files for latest Debian Jessie release might be found here: [https://github.com/OLIMEX/OLINUXINO/blob/master/SOFTWARE/A20/A20-build-3.4.103-release-8/BUILD_DESCRIPTION_A20_Olimex_kernel_3.4.103%2B_Jessie_rel_8.txt build instructions and required files at the GitHub page]

You can find some older releases and older build instructions (older image revisions might be used as a reference, for testing purposes, or if you own old hardware revision of the board) at the following article: [[A20-OLinuXino-LIME2-older-releases|older releases and older build instructions]]

----

Note: the A20-LIME2-DEBIAN-SD card which we have in our web store contains the image suitable for board with no flash or board with NAND memory on a 8GB Class10 fast microSD card. The A20-LIME2-eMMC-DEBIAN-SD contains the image suitable for boards with extra eMMC memory. If you want to use our images, please, use card with speed Class10 or higher. Else the Linux performance would be very slow.

Note: in the previous Debian releases the Ethernet was auto-detected and initialized during boot BUT this was causing big delays in the start-up of the board if you didn't want to use Ethernet or if there wasn't Ethernet cable connected.

You can enable it by following these two steps:

1. To check under what name the LAN is associated write "ifconfig –a"

2. If, for example, it is under eth0 name, then write: "dhclient eth0"

This should enable the Ethernet and then SSH would also be available.

=== Android images ===

Torrents of official Android releases are below. Please read description of the image carefully.

'''Newest official release (recommended):'''

For the NAND flash memory:

Torrent of Android 4.2.2 release 1 for NAND memory (with HDMI and 7 inch 800x480 support - LCD-OLinuXino-7TS): [[Media:A20_Lime2_android_4_22_NAND_LCD7_HDMI_release1.torrent‎|A20-OLinuXino-Lime2 Android for NAND with HDMI and 7 inch display support]]

Torrent of Android 4.2.2 release 1 for NAND memory (with HDMI and 10 inch 1024x600 support - LCD-OLinuXino-10TS): [[Media:A20_Lime2_android_4_22_NAND_LCD10_HDMI_release1.torrent‎‎|A20-OLinuXino-Lime2 Android for NAND with HDMI and 10 inch display support]]

For microSD card:

Torrent of Android 4.2.2 release 2 for 8GB microSD card (with HDMI and 800x480 support): [[Media:A20_Lime2_Android_4.22_SD_card_LCD_800x480_HDMI_8GB_release_2.torrent‎‎‎‎|A20-OLinuXino-Lime2 Android for 8GB microSD card with HDMI and 7 inch display support]]

Torrent of Android 4.2.2 release 2 for 8GB microSD card (with HDMI and 1024x600 support):
[[Media:A20_Lime2_Android_4.22_SD_card_LCD_1024x600_HDMI.torrent|A20-OLinuXino-Lime2 Android for 8GB microSD card with HDMI and 10 inch display support, this image requires loading via PhoenixSuit, refer to the FAQ section at the end of this page]]

Torrent of Android 4.2.2 release 1 for 4GB microSD card (with HDMI and 800x480 support): [[Media:A20_Lime2_Android_4.22_SD_card_LCD_800x480_HDMI_release_1.torrent‎‎‎‎|A20-OLinuXino-Lime2 Android for 4GB microSD card with HDMI and 7 inch display support]]

Build instructions and source files for the official Android images for A20 boards in this repository: https://github.com/hehopmajieh/olinuxino_configs

== Notable unofficial images ==

Below you would find locations to images released by the community. These are not officially supported by Olimex, however, some of these releases are pretty good and worth a try:

*A number of very good and optimized A20-OLinuXino-LIME2 Armbian images: [https://www.armbian.com/olimex-lime-2/ link to LIME2 article at Armbian's web-site]

*A20-OLinuXino-LIME2 is supported by openSUSE Factory, installation instructions might be found here: [https://en.opensuse.org/HCL:A20-OLinuXIno-LIME2 openSUSE wiki link]

*A20-OLinuXino-LIME2 is recognized by the Devuan community and there are official releases here might be found here: [https://files.devuan.org/devuan_ascii/embedded/ Devuan list of files link]
 

== Documents ==

===A20-OLinuXino-LIME2 user's manual===
[https://www.olimex.com/Products/OLinuXino/A20/A20-OLinuXIno-LIME2/resources/A20-OLinuXino-LIME2-UM.pdf User's manual for A20-OLinuXino-LIME2 and A20-OLinuXino-LIME2-4GB]

=== A20 Brief ===
[https://github.com/OLIMEX/OLINUXINO/blob/master/HARDWARE/A20-PDFs/A20%20brief%2020130407.pdf A20 brief]

=== A20 Datasheet ===

[https://github.com/OLIMEX/OLINUXINO/blob/master/HARDWARE/A20-PDFs/A20%20Datasheet%20v1.0%2020130227.pdf A20 Datasheet]

=== A20 User Manual ===

[https://github.com/OLIMEX/OLINUXINO/blob/master/HARDWARE/A20-PDFs/A20%20User%20Manual%202013-03-22.pdf A20 user's manual]

== Hardware ==

===LIME2 shield templates===
[https://github.com/OLIMEX/OLINUXINO/tree/master/HARDWARE/A20-OLinuXino-LIME2 Eagle and KiCAD shield templates for LIME2]

===GPIO description===

[https://github.com/OLIMEX/OLINUXINO/blob/master/HARDWARE/A20-OLinuXino-LIME2/3.%20Templates%20and%20more/A20_LIME2_GPIOs.pdf A20-OLinuXino-LIME2 GPIO description]

A template that might be used to create custom shields or own adapters might be downloaded for Eagle or KiCad at the GitHub here: [https://github.com/OLIMEX/OLINUXINO/tree/master/HARDWARE/A20-OLinuXino-LIME2 shield template]

===Power supply and consumption===

A20-OLinuXino-LIME2 requires 5V regulated power supply external source. regulated means that the power supply adapter should provide exactly 5V no matter loaded or unloaded (some cheap wallwart adapters are not regulated and under no load their power supply may be higher than 5V although marked as 5V power supply, please measure with voltmeter if your power supply provide 5V as if you connect more than 5V to LIME it will be damaged!!!)

The power jack is standard [https://www.olimex.com/wiki/PWRJACK OLIMEX power jack].

A20-OLinuXino-LIME can be powered from three sources:
*+5VDC voltage applied PWR jack
*+3.7V from LiPo re-chargable battery connected to LiPo board connector
*+5V applied to USB-OTG connector

Power consumption is as follows:
*LiPo 3.7V power battery: 1.2W
*+5VDC input power: 1.3W

Comparison table of power consumption might be found at the following [https://www.olimex.com/Products/OLinuXino/_resources/OLinuXino-Consumption.pdf link].

LiPo battery allow backup power supply when main power is interrupted. A20-OLinuXino-LIME2 has power managment IC which charge the battery when main power is present, when power is interrupted the LiPo battery automatically provide backup power supply. Step-up converter prvide 5V for the USB peripherials too. For LiPo batteries we recommend these:
*[https://www.olimex.com/Products/Power/BATTERY-LIPO1400mAh/ 1400mAh]
*[https://www.olimex.com/Products/Power/BATTERY-LIPO3000mAh/ 3000mAh]
*[https://www.olimex.com/Products/Power/BATTERY-LIPO4400mAh/ 4400mAh]
*[https://www.olimex.com/Products/Power/BATTERY-LIPO6600mAh/ 6600mAh]
 

===Board dimensions===

A20-OLinuXino-LIME2 basic dimensions in mils: 3305.5 x 2347.0

Some additional measures might be seen in the image of A10-OLinuXino-LIME which has almost identical layout. It is available as .png here:
[https://www.olimex.com/Products/OLinuXino/A10/A10-OLinuXino-LIME/resources/A10-LIME-dimensions.png link]

===CAD files===

A20-OLinuXino-LIME2 is an Open Source Hardware, CAD files are available at [https://github.com/OLIMEX/OLINUXINO/tree/master/HARDWARE/A20-OLinuXino-LIME2 GitHub]

The CAD product used to design OLinuXino is Eagle and you can download evaluation free version from their [http://www.cadsoftusa.com/ web].

===Board Layout===

[[File:A20-OLinuXino-LIME2_top_naming_extras.jpg|650px]]

[[File:A20-OLinuXino-LIME2 bottom naming.jpg|650px]]

== Software ==

===Linux Commands===

[[Linux-Commands]] Brief Linux Command reference

===Python library for GPIO, I2C and SPI control===

The Debian Linux Python package for A20-OLinuXino-LIME2 is called pyA20Lime2. It makes the access to GPIO, I2C and SPI considerably easier. It is installed in the default Debian image. More information and examples on how it can be used might be found here:

[https://pypi.python.org/pypi/pyA20Lime2 Link to pyA20Lime2 package at python.org]

===GPIO under Linux===

GPIOs are located in /sys/class/gpio directory. Note that first you have to export GPIOs. For example:

add gpioPH2

root@A20:~# echo 20 > /sys/class/gpio/export

make PH2 output

root@A20:~# echo out > //sys/class/gpio/gpio20_ph2/direction

turn on onboard LED(connected to PH2)

root@A20:~# echo 1 > /sys/class/gpio/gpio20_ph2/value

turn off onboard LED(connected to PH2)

root@A20:~# echo 0 > /sys/class/gpio/gpio20_ph2/value

Full list with supported GPIOs is:

gpio21_ph7 gpio33_ph20 gpio45_pb12 gpio57_pi2 gpio69_pi14
gpio10_pg11 gpio22_ph9 gpio34_ph21 gpio46_pb13 gpio58_pi3 gpio6_pg5
gpio11_pc3 gpio23_ph10 gpio35_ph22 gpio47_pb14 gpio59_pi4 gpio70_pi15
gpio12_pc18 gpio24_ph11 gpio36_ph23 gpio48_pb15 gpio5_pg4 gpio71_pi16
gpio13_pc19 gpio25_ph12 gpio37_pb3 gpio49_pb16 gpio60_pi5 gpio72_pi17
gpio14_pc20 gpio26_ph13 gpio38_pb4 gpio4_pg3 gpio61_pi6 gpio73_pi18
gpio15_pc21 gpio27_ph14 gpio39_pb5 gpio50_pb17 gpio62_pi7 gpio74_pi19
gpio16_pc22 gpio28_ph15 gpio3_pg2 gpio51_ph24 gpio63_pi8 gpio75_pi20
gpio17_pc23 gpio29_ph16 gpio40_pb6 gpio52_ph25 gpio64_pi9 gpio7_pg6
gpio18_pc24 gpio2_pg1 gpio41_pb7 gpio53_ph26 gpio65_pi10 gpio8_pg7
gpio19_ph0 gpio30_ph17 gpio42_pb8 gpio54_ph27 gpio66_pi11 gpio9_pg8
gpio1_pg0 gpio31_ph18 gpio43_pb10 gpio55_pi0 gpio67_pi12 gpiochip1
gpio20_ph2 gpio32_ph19 gpio44_pb11 gpio56_pi1 gpio68_pi13

===Add Voice to your OLinuXino project===

[http://olimex.wordpress.com/2013/10/03/make-things-talk-with-olinuxino/ Installation of Festival on OLinuXino]
 

== How To? ==
===How to generate boot-able SD-card Debian Linux image for A20-OLinuXino-LIME2? ===

Build instructions and required files for the latest Debian images: [https://github.com/OLIMEX/OLINUXINO/tree/master/SOFTWARE/A20 instructions and files at the GitHub page]

Note that Linux-Sunxi Kernel is a work-in-progress, this means you can try the current stage/sunxi-x.x branch but if something is broken and doesn't work just revert to the git tags we give in the blog and they would work for sure.

[https://github.com/linux-sunxi/u-boot-sunxi/wiki Sunxi u-boot loader] The linux-sunxi git page contains a lot of sources for all Olimex Allwinner boards.

===How to connect a display and adjust the video output resolution?===
There is a separate article on the subject: [[how to connect display to a Lime board]]
 

=== Is it possible to boot Debian from NAND? Do you provide such image?===

Yes, it is possible. Use the latest Debian Jessie image and write "nandinstall". More information can be found in this wiki article: [[How_to_install_Debian_to_NAND| installing Debian Jessie to the 4GB NAND memory]]

There are other people who are also successful in booting Debian from the NAND. Make sure to check on the forum. Make sure to check the number of very good and optimized A20-OLinuXino Debian images by Igor Pečovnik. There are also his instructions for NAND installation of Debian: [http://www.armbian.com/download/ link to his web-site]

===How to detect and enable the Ethernet controller (if it is disabled by default)? ===

Note: in the previous Debian releases the Ethernet was auto-detected and initialized during boot BUT this was causing big delays in the start-up of the board if you didn't want to use Ethernet or if there wasn't Ethernet cable connected.

You can enable it by following these two steps:

1. To check under what name the LAN is associated write "ifconfig –a"

2. If, for example, it is under eth0 name, then write: "dhclient eth0"

This should enable the Ethernet and then SSH would also be available.

===How to download new Android image to the NAND memory of my A20 board?===

Follow these steps to download the image to the NAND memory:

*1. Install and run PhoenixSuit (can be found here: [https://drive.google.com/file/d/0BwplT87k9SCgaTFTZnVST05ONzA/view?usp=sharing download from google drive]).

*2. Go to firmware tab of the program and point to a valid Android image (the latest official one may also be downloaded above).

*3. Disconnect the power supply and USB cable from the A20 board.

*4. Press and hold RECOVERY button, apply power supply 5V, release RECOVERY button.

*5. Connect USB cable to the mini USB connector.

*6. You will be asked for drivers for the bootloader. Navigate to the folder where you extracted the PhoenixSuit and install the drivers from the respective executables (or manually point the installer to the drivers folder in the PhoenixSuit installation path).

*7. PhoenixSuit will detect the board and would ask for the method of writing the image. Choose method of writing the image and confirm your wish to write the image.

*8. Wait till upgrade succeeds

Note that it is not recommended to have your mini USB connected to an external USB hub. This might cause delays and might distort the signal levels. Always test with the USB connected straight to the USB ports of your computer.

===How to generate Arch Linux image?===

Recent forum post by user progmetalbg here: [https://www.olimex.com/forum/index.php?topic=4261.0| at Olimex forums]

[http://alarma20.wordpress.com/2013/09/13/howto-build-arch-linux-arm-for-a20-olinuxino-micro/ Older step by step instructions on how to build Arch Linux image for another A20 board]

===How do I write the official Android image to a micro SD card for my A20 board?===
A: First download one of the official Android images, which might be found in the Android section above.

Make sure that the download link you visit clearly indicates that the image is suitable for the microSD card since there are images suitable for NAND memory also. The images suitable for the microSD memory and those suitable for NAND card are different. However, the upload method is almost identical – using PhoenixSuit.

There are two types of Android images for microSD card that we usually provide and each of them has to be downloaded to a microSD card using a different method. The image provided for microSD card is either the native Android image that can be downloaded to the card via a software tool like PhoenixSuit (through the board) or an image taken from an already prepared microSD card that requires to simply write the image (through a microSD card reader).

'''It is more likely that you have an Android image that requires a simple copy to a card. If that is the case you can follow the exact steps as for Linux (e.g. using "Win32 Disk Imager" or "dd" command).'''

In order to prepare a microSD card with a native Android you will need a software tool called PhoenixSuit and then:

• Install and run PhoenixSuit (can be found here: [https://drive.google.com/file/d/0BwplT87k9SCgaTFTZnVST05ONzA/view?usp=sharing download from google drive])

• Go to the firmware tab of the program and point to a valid Android image (note that the
images on Gdrive are compressed and you have to extract them to .img files to be able write
them with PhoenixSuit)

• Disconnect the power supply and USB cable from the A20 board. Put an SD card in micro SD
holder. We recommend either a 4GB or a 8GB class 10 card.

• Press and hold RECOVERY button, apply power supply 5V, release RECOVERY button.

• Connect USB cable to the mini USB connector.

• You will be asked for drivers for the boot-loader. Navigate to the folder where you extracted the PhoenixSuit and install the drivers from the respective executables (or manually point the installer to the drivers folder in the PhoenixSuit installation path).

• PhoenixSuit will detect the board and would ask for the method of writing the image. Choose
method of writing the image and confirm your wish to write the image.

• Wait till upgrade succeeds

Note that it is not recommended to have your mini USB connected to an external USB hub. This
might cause delays and might distort the signal levels. Always test with the USB connected straight to the USB ports of your computer.

Important: When Android runs for very first time it takes several minutes to initialize all files and buffers please do not cut the power supply during this process! Also when fresh image is installed fast boot may be disabled, which means that when you apply power supply after few seconds Android will go in sleep mode and you have to press POWER button to start it, you can change to fast boot when you power off there is dialog box asking you if you want next boot to be fast boot, you have to check this box before you power off. Also note that you must do touch screen calibration when you run Android for very first time which might require a mouse.

===I don't have neither serial cable, nor HDMI monitor. I also can't access the local Ethernet network. Can I somehow access the board anyway?===

The latest official Debian Linux image allows the use the USB_OTG connector for SSH connection without the need of a LAN cable or a serial cable. You can use a mini USB cable connected between your host PC and the on-board mini USB connector. For connection convenience there is a DHCP server running specifically for USB0 interface. The DHCP server should give IP address to the new USB0 interface of your host PC so you can make SSH connection from your PC to the default board IP address of the USB0 interface – 192.168.2.1.

You can connect to the board using a mini USB cable and an SSH client (if you use Windows you might use "puTTY", for example) at address 192.168.2.1.

For Windows operating system - upon connection, the board should show up in "Windows Device Manager" as "RNDIS Ethernet Gadget". You might be asked to install a driver. The drivers can be found online as "RNDIS driver" (Remote Network Driver Interface Specification). The drivers are provided by Microsoft and they should be available for every Windows distribution - refer to the respective files and articles provided by Microsoft on how to install the required drivers.

===How to edit board configurations and definitions in the official Debian Linux? ===

Do you want a custom video resolution output? Do you need a different port definition? Do you need to change the hardware defitions of the board?

You would need to edit the board's script.bin/script.fex file. How to do it is described in another separate article: [[how to edit board configurations and definitions in the official Debian Linux]].

===How to add STK1160 video capture driver support in Kernel 3.4===

[https://www.olimex.com/wiki/STK1160-howto-linux-sunxi-3_4 STK1160] driver backport by Dimitar Tomov
[[Main_Page]]

MOD-IO2

2024-07-18T07:48:05Z

LubOlimex: /* Archive firmware */

== Documents ==
Latest manual revision, suitable for MOD-IO2 hardware revision C and newer: [https://www.olimex.com/Products/Modules/IO/MOD-IO2/resources/MOD-IO2.pdf available here]

User manual revision F, suitable for MOD-IO2 hardware revisions A and B: [https://www.olimex.com/Products/Modules/IO/MOD-IO2/resources/MOD-IO_manual_F.pdf available here]

== Hardware ==
Design files for older hardware revisions:

Hardware revision B schematic: [https://www.olimex.com/Products/Modules/IO/MOD-IO2/resources/MOD-IO2-Rev-B-schematic.pdf click for PDF export]

Hardware revision B sources for Eagle CAD: [https://www.olimex.com/Products/Modules/IO/MOD-IO2/resources/MOD-IO2_brd_sch_eagle.zip click to download ZIP archive]

== Software ==
Older software, compatible with board hardware revisions up to B:

Demo with OLIMEXINO-STM32: [https://www.olimex.com/Products/Duino/STM32/OLIMEXINO-STM32/resources/OLIMEXINO-STM32_MOD-IO2_relay.zip click to download ZIP archive]

== Archive firmware ==
'''Latest firmware is available at the main page of the device.''' In the wiki one can only find older firmware, that still might be helpful. The projects listed below are no longer officially supported. The best practice is to use the EXACT same compiler as mentioned and in most cases the exact same IDE version as mentioned.

Older firmware released by Olimex for MOD-IO2:

1) MOD-IO2 v4.3 - binary, source, and how-to - [https://www.olimex.com/Products/Modules/IO/MOD-IO2/resources/MOD-IO2_firmware_v43.zip click to download] - this is the last firmware suitable for boards with PIC16 (before revision C changed main chip to CH32V003), which was added in its newer 4.3 version

2) MOD-IO2 v3.2/3.02 - binary, source, and how-to - [https://www.olimex.com/Products/Modules/IO/MOD-IO2/resources/MOD-IO2_firmware_v_3_02.zip click to download] - this lacked analog out (DAC), which was added in its newer 4.3 version

3) MOD-IO2 v3.1/3.01 firmware - binary, source, and how-to - [https://www.olimex.com/Products/Modules/IO/MOD-IO2/resources/MOD-IO2_firmware_v_3_1.zip click to download] - it lacked several functions which are now added, refer to the readme in the folder of the newest 3.02 firmware

4) MOD-IO2 v3 firmware - binary, source, and how-to - [https://www.olimex.com/Products/Modules/IO/MOD-IO2/resources/MOD-IO2_firmware_v3.zip click to download] - it has a bug with the internal weak pull-ups

5) MOD-IO2 v2 firmware - binary, source, and how-to - [https://www.olimex.com/Products/Modules/IO/MOD-IO2/resources/MOD-IO2+OLinuXino.zip click to download] - protocol fixes

6) MOD-IO2 v1 firmware - C source and HEX for I2C control - [https://www.olimex.com/Products/Modules/IO/MOD-IO2/resources/MOD-IO2_demo_and_firmware.zip click to download] - initial release

== Projects ==
Under construction

== FAQ ==
Under construction

[[Category:IO]]

MOD-IO2

2024-07-18T07:47:10Z

LubOlimex: /* Documents */

== Documents ==
Latest manual revision, suitable for MOD-IO2 hardware revision C and newer: [https://www.olimex.com/Products/Modules/IO/MOD-IO2/resources/MOD-IO2.pdf available here]

User manual revision F, suitable for MOD-IO2 hardware revisions A and B: [https://www.olimex.com/Products/Modules/IO/MOD-IO2/resources/MOD-IO_manual_F.pdf available here]

== Hardware ==
Design files for older hardware revisions:

Hardware revision B schematic: [https://www.olimex.com/Products/Modules/IO/MOD-IO2/resources/MOD-IO2-Rev-B-schematic.pdf click for PDF export]

Hardware revision B sources for Eagle CAD: [https://www.olimex.com/Products/Modules/IO/MOD-IO2/resources/MOD-IO2_brd_sch_eagle.zip click to download ZIP archive]

== Software ==
Older software, compatible with board hardware revisions up to B:

Demo with OLIMEXINO-STM32: [https://www.olimex.com/Products/Duino/STM32/OLIMEXINO-STM32/resources/OLIMEXINO-STM32_MOD-IO2_relay.zip click to download ZIP archive]

== Archive firmware ==
'''Latest firmware is available at the main page of the device.''' In the wiki one can only find older firmware, that still might be helpful. The projects listed below are no longer officially supported. The best practice is to use the EXACT same compiler as mentioned and in most cases the exact same IDE version as mentioned.

Older firmware released by Olimex for MOD-IO2:

1) MOD-IO2 v4.3 - binary, source, and how-to - [https://www.olimex.com/Products/Modules/IO/MOD-IO2/resources/MOD-IO2_firmware_v43.zip click to download] - this is the last firmware suitable for boards with PIC16 (before revision C changed main chip to CH32V003), which was added in its newer 4.3 version

1) MOD-IO2 v3.2/3.02 - binary, source, and how-to - [https://www.olimex.com/Products/Modules/IO/MOD-IO2/resources/MOD-IO2_firmware_v_3_02.zip click to download] - this lacked analog out (DAC), which was added in its newer 4.3 version

2) MOD-IO2 v3.1/3.01 firmware - binary, source, and how-to - [https://www.olimex.com/Products/Modules/IO/MOD-IO2/resources/MOD-IO2_firmware_v_3_1.zip click to download] - it lacked several functions which are now added, refer to the readme in the folder of the newest 3.02 firmware

3) MOD-IO2 v3 firmware - binary, source, and how-to - [https://www.olimex.com/Products/Modules/IO/MOD-IO2/resources/MOD-IO2_firmware_v3.zip click to download] - it has a bug with the internal weak pull-ups

4) MOD-IO2 v2 firmware - binary, source, and how-to - [https://www.olimex.com/Products/Modules/IO/MOD-IO2/resources/MOD-IO2+OLinuXino.zip click to download] - protocol fixes

5) MOD-IO2 v1 firmware - C source and HEX for I2C control - [https://www.olimex.com/Products/Modules/IO/MOD-IO2/resources/MOD-IO2_demo_and_firmware.zip click to download] - initial release

== Projects ==
Under construction

== FAQ ==
Under construction

[[Category:IO]]

MOD-IO2

2024-07-17T06:00:45Z

LubOlimex: /* Software */

== Documents ==
Under construction

== Hardware ==
Design files for older hardware revisions:

Hardware revision B schematic: [https://www.olimex.com/Products/Modules/IO/MOD-IO2/resources/MOD-IO2-Rev-B-schematic.pdf click for PDF export]

Hardware revision B sources for Eagle CAD: [https://www.olimex.com/Products/Modules/IO/MOD-IO2/resources/MOD-IO2_brd_sch_eagle.zip click to download ZIP archive]

== Software ==
Older software, compatible with board hardware revisions up to B:

Demo with OLIMEXINO-STM32: [https://www.olimex.com/Products/Duino/STM32/OLIMEXINO-STM32/resources/OLIMEXINO-STM32_MOD-IO2_relay.zip click to download ZIP archive]

== Archive firmware ==
'''Latest firmware is available at the main page of the device.''' In the wiki one can only find older firmware, that still might be helpful. The projects listed below are no longer officially supported. The best practice is to use the EXACT same compiler as mentioned and in most cases the exact same IDE version as mentioned.

Older firmware released by Olimex for MOD-IO2:

1) MOD-IO2 v4.3 - binary, source, and how-to - [https://www.olimex.com/Products/Modules/IO/MOD-IO2/resources/MOD-IO2_firmware_v43.zip click to download] - this is the last firmware suitable for boards with PIC16 (before revision C changed main chip to CH32V003), which was added in its newer 4.3 version

1) MOD-IO2 v3.2/3.02 - binary, source, and how-to - [https://www.olimex.com/Products/Modules/IO/MOD-IO2/resources/MOD-IO2_firmware_v_3_02.zip click to download] - this lacked analog out (DAC), which was added in its newer 4.3 version

2) MOD-IO2 v3.1/3.01 firmware - binary, source, and how-to - [https://www.olimex.com/Products/Modules/IO/MOD-IO2/resources/MOD-IO2_firmware_v_3_1.zip click to download] - it lacked several functions which are now added, refer to the readme in the folder of the newest 3.02 firmware

3) MOD-IO2 v3 firmware - binary, source, and how-to - [https://www.olimex.com/Products/Modules/IO/MOD-IO2/resources/MOD-IO2_firmware_v3.zip click to download] - it has a bug with the internal weak pull-ups

4) MOD-IO2 v2 firmware - binary, source, and how-to - [https://www.olimex.com/Products/Modules/IO/MOD-IO2/resources/MOD-IO2+OLinuXino.zip click to download] - protocol fixes

5) MOD-IO2 v1 firmware - C source and HEX for I2C control - [https://www.olimex.com/Products/Modules/IO/MOD-IO2/resources/MOD-IO2_demo_and_firmware.zip click to download] - initial release

== Projects ==
Under construction

== FAQ ==
Under construction

[[Category:IO]]

MOD-IO2

2024-07-17T06:00:23Z

LubOlimex: /* Hardware */

== Documents ==
Under construction

== Hardware ==
Design files for older hardware revisions:

Hardware revision B schematic: [https://www.olimex.com/Products/Modules/IO/MOD-IO2/resources/MOD-IO2-Rev-B-schematic.pdf click for PDF export]

Hardware revision B sources for Eagle CAD: [https://www.olimex.com/Products/Modules/IO/MOD-IO2/resources/MOD-IO2_brd_sch_eagle.zip click to download ZIP archive]

== Software ==
Older software, compatible with board hardware revisions up to B:

Demo with OLIMEXINO-STM32:

https://www.olimex.com/Products/Duino/STM32/OLIMEXINO-STM32/resources/OLIMEXINO-STM32_MOD-IO2_relay.zip

== Archive firmware ==
'''Latest firmware is available at the main page of the device.''' In the wiki one can only find older firmware, that still might be helpful. The projects listed below are no longer officially supported. The best practice is to use the EXACT same compiler as mentioned and in most cases the exact same IDE version as mentioned.

Older firmware released by Olimex for MOD-IO2:

1) MOD-IO2 v4.3 - binary, source, and how-to - [https://www.olimex.com/Products/Modules/IO/MOD-IO2/resources/MOD-IO2_firmware_v43.zip click to download] - this is the last firmware suitable for boards with PIC16 (before revision C changed main chip to CH32V003), which was added in its newer 4.3 version

1) MOD-IO2 v3.2/3.02 - binary, source, and how-to - [https://www.olimex.com/Products/Modules/IO/MOD-IO2/resources/MOD-IO2_firmware_v_3_02.zip click to download] - this lacked analog out (DAC), which was added in its newer 4.3 version

2) MOD-IO2 v3.1/3.01 firmware - binary, source, and how-to - [https://www.olimex.com/Products/Modules/IO/MOD-IO2/resources/MOD-IO2_firmware_v_3_1.zip click to download] - it lacked several functions which are now added, refer to the readme in the folder of the newest 3.02 firmware

3) MOD-IO2 v3 firmware - binary, source, and how-to - [https://www.olimex.com/Products/Modules/IO/MOD-IO2/resources/MOD-IO2_firmware_v3.zip click to download] - it has a bug with the internal weak pull-ups

4) MOD-IO2 v2 firmware - binary, source, and how-to - [https://www.olimex.com/Products/Modules/IO/MOD-IO2/resources/MOD-IO2+OLinuXino.zip click to download] - protocol fixes

5) MOD-IO2 v1 firmware - C source and HEX for I2C control - [https://www.olimex.com/Products/Modules/IO/MOD-IO2/resources/MOD-IO2_demo_and_firmware.zip click to download] - initial release

== Projects ==
Under construction

== FAQ ==
Under construction

[[Category:IO]]

MOD-IO2

2024-07-17T05:59:27Z

LubOlimex: /* Archive firmware */

== Documents ==
Under construction

== Hardware ==
Design files for older hardware revisions:

Hardware revision B schematic: https://www.olimex.com/Products/Modules/IO/MOD-IO2/resources/MOD-IO2-Rev-B-schematic.pdf

Hardware revision B sources for Eagle CAD: https://www.olimex.com/Products/Modules/IO/MOD-IO2/resources/MOD-IO2_brd_sch_eagle.zip

== Software ==
Older software, compatible with board hardware revisions up to B:

Demo with OLIMEXINO-STM32:

https://www.olimex.com/Products/Duino/STM32/OLIMEXINO-STM32/resources/OLIMEXINO-STM32_MOD-IO2_relay.zip

== Archive firmware ==
'''Latest firmware is available at the main page of the device.''' In the wiki one can only find older firmware, that still might be helpful. The projects listed below are no longer officially supported. The best practice is to use the EXACT same compiler as mentioned and in most cases the exact same IDE version as mentioned.

Older firmware released by Olimex for MOD-IO2:

1) MOD-IO2 v4.3 - binary, source, and how-to - [https://www.olimex.com/Products/Modules/IO/MOD-IO2/resources/MOD-IO2_firmware_v43.zip click to download] - this is the last firmware suitable for boards with PIC16 (before revision C changed main chip to CH32V003), which was added in its newer 4.3 version

1) MOD-IO2 v3.2/3.02 - binary, source, and how-to - [https://www.olimex.com/Products/Modules/IO/MOD-IO2/resources/MOD-IO2_firmware_v_3_02.zip click to download] - this lacked analog out (DAC), which was added in its newer 4.3 version

2) MOD-IO2 v3.1/3.01 firmware - binary, source, and how-to - [https://www.olimex.com/Products/Modules/IO/MOD-IO2/resources/MOD-IO2_firmware_v_3_1.zip click to download] - it lacked several functions which are now added, refer to the readme in the folder of the newest 3.02 firmware

3) MOD-IO2 v3 firmware - binary, source, and how-to - [https://www.olimex.com/Products/Modules/IO/MOD-IO2/resources/MOD-IO2_firmware_v3.zip click to download] - it has a bug with the internal weak pull-ups

4) MOD-IO2 v2 firmware - binary, source, and how-to - [https://www.olimex.com/Products/Modules/IO/MOD-IO2/resources/MOD-IO2+OLinuXino.zip click to download] - protocol fixes

5) MOD-IO2 v1 firmware - C source and HEX for I2C control - [https://www.olimex.com/Products/Modules/IO/MOD-IO2/resources/MOD-IO2_demo_and_firmware.zip click to download] - initial release

== Projects ==
Under construction

== FAQ ==
Under construction

[[Category:IO]]

MOD-IO2

2024-07-17T05:59:16Z

LubOlimex: /* Archive firmware */

== Documents ==
Under construction

== Hardware ==
Design files for older hardware revisions:

Hardware revision B schematic: https://www.olimex.com/Products/Modules/IO/MOD-IO2/resources/MOD-IO2-Rev-B-schematic.pdf

Hardware revision B sources for Eagle CAD: https://www.olimex.com/Products/Modules/IO/MOD-IO2/resources/MOD-IO2_brd_sch_eagle.zip

== Software ==
Older software, compatible with board hardware revisions up to B:

Demo with OLIMEXINO-STM32:

https://www.olimex.com/Products/Duino/STM32/OLIMEXINO-STM32/resources/OLIMEXINO-STM32_MOD-IO2_relay.zip

== Archive firmware ==
'''Latest firmware is available at the main page of the device.''' In the wiki one can only find older firmware, that still might be helpful. The projects listed below are no longer officially supported. The best practice is to use the EXACT same compiler as mentioned and in most cases the exact same IDE version as mentioned.

Older firmware released by Olimex for MOD-IO2:

1) MOD-IO2 v4.3 - binary, source, and how-to - [https://www.olimex.com/Products/Modules/IO/MOD-IO2/resources/MOD-IO2_firmware_v43.zip click to download] - this is the last firmware suitable for boards with PIC16 (before revision C changed main chip to CH32V003), which was added in its newer 4.3 version

1) MOD-IO2 v3.2/3.02 - binary, source, and how-to - [https://www.olimex.com/Products/Modules/IO/MOD-IO2/resources/MOD-IO2_firmware_v_3_02.zip click to download] - this lacked analog out (DAC), which was added in its newer 4.3 version

2) MOD-IO2 v3.1/3.01 firmware - binary, source, and how-to - [https://www.olimex.com/Products/Modules/IO/MOD-IO2/resources/MOD-IO2_firmware_v_3_1.zip click to download] - it lacked several functions which are now added, refer to the readme in the folder of the newest 3.02 firmware

3) MOD-IO2 v3 firmware - binary, source, and how-to - [https://www.olimex.com/Products/Modules/IO/MOD-IO2/resources/MOD-IO2_firmware_v3.zip click to download] - it has a bug with the internal weak pull-ups

4) MOD-IO2 v2 firmware - binary, source, and how-to - [https://www.olimex.com/Products/Modules/IO/MOD-IO2/resources/MOD-IO2+OLinuXino.zip click to download] - protocol fixes

5 )MOD-IO2 v1 firmware - C source and HEX for I2C control - [https://www.olimex.com/Products/Modules/IO/MOD-IO2/resources/MOD-IO2_demo_and_firmware.zip click to download] - initial release

== Projects ==
Under construction

== FAQ ==
Under construction

[[Category:IO]]

MOD-IO2

2024-07-17T05:58:50Z

LubOlimex: /* Hardware */

== Documents ==
Under construction

== Hardware ==
Design files for older hardware revisions:

Hardware revision B schematic: https://www.olimex.com/Products/Modules/IO/MOD-IO2/resources/MOD-IO2-Rev-B-schematic.pdf

Hardware revision B sources for Eagle CAD: https://www.olimex.com/Products/Modules/IO/MOD-IO2/resources/MOD-IO2_brd_sch_eagle.zip

== Software ==
Older software, compatible with board hardware revisions up to B:

Demo with OLIMEXINO-STM32:

https://www.olimex.com/Products/Duino/STM32/OLIMEXINO-STM32/resources/OLIMEXINO-STM32_MOD-IO2_relay.zip

== Archive firmware ==
'''Latest firmware is available at the main page of the device.''' In the wiki one can only find older firmware, that still might be helpful. The projects listed below are no longer officially supported. The best practice is to use the EXACT same compiler as mentioned and in most cases the exact same IDE version as mentioned.

Older firmware released by Olimex for MOD-IO2:

1)MOD-IO2 v4.3 - binary, source, and how-to - [https://www.olimex.com/Products/Modules/IO/MOD-IO2/resources/MOD-IO2_firmware_v43.zip click to download] - this is the last firmware suitable for boards with PIC16 (before revision C changed main chip to CH32V003), which was added in its newer 4.3 version

1)MOD-IO2 v3.2/3.02 - binary, source, and how-to - [https://www.olimex.com/Products/Modules/IO/MOD-IO2/resources/MOD-IO2_firmware_v_3_02.zip click to download] - this lacked analog out (DAC), which was added in its newer 4.3 version

2)MOD-IO2 v3.1/3.01 firmware - binary, source, and how-to - [https://www.olimex.com/Products/Modules/IO/MOD-IO2/resources/MOD-IO2_firmware_v_3_1.zip click to download] - it lacked several functions which are now added, refer to the readme in the folder of the newest 3.02 firmware

3)MOD-IO2 v3 firmware - binary, source, and how-to - [https://www.olimex.com/Products/Modules/IO/MOD-IO2/resources/MOD-IO2_firmware_v3.zip click to download] - it has a bug with the internal weak pull-ups

4)MOD-IO2 v2 firmware - binary, source, and how-to - [https://www.olimex.com/Products/Modules/IO/MOD-IO2/resources/MOD-IO2+OLinuXino.zip click to download] - protocol fixes

5)MOD-IO2 v1 firmware - C source and HEX for I2C control - [https://www.olimex.com/Products/Modules/IO/MOD-IO2/resources/MOD-IO2_demo_and_firmware.zip click to download] - initial release

== Projects ==
Under construction

== FAQ ==
Under construction

[[Category:IO]]

MOD-IO2

2024-07-17T05:57:59Z

LubOlimex: /* Software */

== Documents ==
Under construction

== Hardware ==
Design files for older hardware revisions:

Hardware revision B shcematic: https://www.olimex.com/Products/Modules/IO/MOD-IO2/resources/MOD-IO2-Rev-B-schematic.pdf

Hardware revision B souyrces for Eagle CAD: https://www.olimex.com/Products/Modules/IO/MOD-IO2/resources/MOD-IO2_brd_sch_eagle.zip

== Software ==
Older software, compatible with board hardware revisions up to B:

Demo with OLIMEXINO-STM32:

https://www.olimex.com/Products/Duino/STM32/OLIMEXINO-STM32/resources/OLIMEXINO-STM32_MOD-IO2_relay.zip

== Archive firmware ==
'''Latest firmware is available at the main page of the device.''' In the wiki one can only find older firmware, that still might be helpful. The projects listed below are no longer officially supported. The best practice is to use the EXACT same compiler as mentioned and in most cases the exact same IDE version as mentioned.

Older firmware released by Olimex for MOD-IO2:

1)MOD-IO2 v4.3 - binary, source, and how-to - [https://www.olimex.com/Products/Modules/IO/MOD-IO2/resources/MOD-IO2_firmware_v43.zip click to download] - this is the last firmware suitable for boards with PIC16 (before revision C changed main chip to CH32V003), which was added in its newer 4.3 version

1)MOD-IO2 v3.2/3.02 - binary, source, and how-to - [https://www.olimex.com/Products/Modules/IO/MOD-IO2/resources/MOD-IO2_firmware_v_3_02.zip click to download] - this lacked analog out (DAC), which was added in its newer 4.3 version

2)MOD-IO2 v3.1/3.01 firmware - binary, source, and how-to - [https://www.olimex.com/Products/Modules/IO/MOD-IO2/resources/MOD-IO2_firmware_v_3_1.zip click to download] - it lacked several functions which are now added, refer to the readme in the folder of the newest 3.02 firmware

3)MOD-IO2 v3 firmware - binary, source, and how-to - [https://www.olimex.com/Products/Modules/IO/MOD-IO2/resources/MOD-IO2_firmware_v3.zip click to download] - it has a bug with the internal weak pull-ups

4)MOD-IO2 v2 firmware - binary, source, and how-to - [https://www.olimex.com/Products/Modules/IO/MOD-IO2/resources/MOD-IO2+OLinuXino.zip click to download] - protocol fixes

5)MOD-IO2 v1 firmware - C source and HEX for I2C control - [https://www.olimex.com/Products/Modules/IO/MOD-IO2/resources/MOD-IO2_demo_and_firmware.zip click to download] - initial release

== Projects ==
Under construction

== FAQ ==
Under construction

[[Category:IO]]

MOD-IO2

2024-07-17T05:57:47Z

LubOlimex: /* Software */

== Documents ==
Under construction

== Hardware ==
Design files for older hardware revisions:

Hardware revision B shcematic: https://www.olimex.com/Products/Modules/IO/MOD-IO2/resources/MOD-IO2-Rev-B-schematic.pdf

Hardware revision B souyrces for Eagle CAD: https://www.olimex.com/Products/Modules/IO/MOD-IO2/resources/MOD-IO2_brd_sch_eagle.zip

== Software ==
Older software, compatible with board hardware revisions up to B:

OLIMEXINO-STM32:

https://www.olimex.com/Products/Duino/STM32/OLIMEXINO-STM32/resources/OLIMEXINO-STM32_MOD-IO2_relay.zip

== Archive firmware ==
'''Latest firmware is available at the main page of the device.''' In the wiki one can only find older firmware, that still might be helpful. The projects listed below are no longer officially supported. The best practice is to use the EXACT same compiler as mentioned and in most cases the exact same IDE version as mentioned.

Older firmware released by Olimex for MOD-IO2:

1)MOD-IO2 v4.3 - binary, source, and how-to - [https://www.olimex.com/Products/Modules/IO/MOD-IO2/resources/MOD-IO2_firmware_v43.zip click to download] - this is the last firmware suitable for boards with PIC16 (before revision C changed main chip to CH32V003), which was added in its newer 4.3 version

1)MOD-IO2 v3.2/3.02 - binary, source, and how-to - [https://www.olimex.com/Products/Modules/IO/MOD-IO2/resources/MOD-IO2_firmware_v_3_02.zip click to download] - this lacked analog out (DAC), which was added in its newer 4.3 version

2)MOD-IO2 v3.1/3.01 firmware - binary, source, and how-to - [https://www.olimex.com/Products/Modules/IO/MOD-IO2/resources/MOD-IO2_firmware_v_3_1.zip click to download] - it lacked several functions which are now added, refer to the readme in the folder of the newest 3.02 firmware

3)MOD-IO2 v3 firmware - binary, source, and how-to - [https://www.olimex.com/Products/Modules/IO/MOD-IO2/resources/MOD-IO2_firmware_v3.zip click to download] - it has a bug with the internal weak pull-ups

4)MOD-IO2 v2 firmware - binary, source, and how-to - [https://www.olimex.com/Products/Modules/IO/MOD-IO2/resources/MOD-IO2+OLinuXino.zip click to download] - protocol fixes

5)MOD-IO2 v1 firmware - C source and HEX for I2C control - [https://www.olimex.com/Products/Modules/IO/MOD-IO2/resources/MOD-IO2_demo_and_firmware.zip click to download] - initial release

== Projects ==
Under construction

== FAQ ==
Under construction

[[Category:IO]]

MOD-IO2

2024-07-17T05:57:03Z

LubOlimex: /* Hardware */

== Documents ==
Under construction

== Hardware ==
Design files for older hardware revisions:

Hardware revision B shcematic: https://www.olimex.com/Products/Modules/IO/MOD-IO2/resources/MOD-IO2-Rev-B-schematic.pdf

Hardware revision B souyrces for Eagle CAD: https://www.olimex.com/Products/Modules/IO/MOD-IO2/resources/MOD-IO2_brd_sch_eagle.zip

== Software ==
Under construction

== Archive firmware ==
'''Latest firmware is available at the main page of the device.''' In the wiki one can only find older firmware, that still might be helpful. The projects listed below are no longer officially supported. The best practice is to use the EXACT same compiler as mentioned and in most cases the exact same IDE version as mentioned.

Older firmware released by Olimex for MOD-IO2:

1)MOD-IO2 v4.3 - binary, source, and how-to - [https://www.olimex.com/Products/Modules/IO/MOD-IO2/resources/MOD-IO2_firmware_v43.zip click to download] - this is the last firmware suitable for boards with PIC16 (before revision C changed main chip to CH32V003), which was added in its newer 4.3 version

1)MOD-IO2 v3.2/3.02 - binary, source, and how-to - [https://www.olimex.com/Products/Modules/IO/MOD-IO2/resources/MOD-IO2_firmware_v_3_02.zip click to download] - this lacked analog out (DAC), which was added in its newer 4.3 version

2)MOD-IO2 v3.1/3.01 firmware - binary, source, and how-to - [https://www.olimex.com/Products/Modules/IO/MOD-IO2/resources/MOD-IO2_firmware_v_3_1.zip click to download] - it lacked several functions which are now added, refer to the readme in the folder of the newest 3.02 firmware

3)MOD-IO2 v3 firmware - binary, source, and how-to - [https://www.olimex.com/Products/Modules/IO/MOD-IO2/resources/MOD-IO2_firmware_v3.zip click to download] - it has a bug with the internal weak pull-ups

4)MOD-IO2 v2 firmware - binary, source, and how-to - [https://www.olimex.com/Products/Modules/IO/MOD-IO2/resources/MOD-IO2+OLinuXino.zip click to download] - protocol fixes

5)MOD-IO2 v1 firmware - C source and HEX for I2C control - [https://www.olimex.com/Products/Modules/IO/MOD-IO2/resources/MOD-IO2_demo_and_firmware.zip click to download] - initial release

== Projects ==
Under construction

== FAQ ==
Under construction

[[Category:IO]]

MOD-IO2

2024-07-17T05:35:17Z

LubOlimex: /* Archive firmware */

== Documents ==
Under construction

== Hardware ==
Under construction

== Software ==
Under construction

== Archive firmware ==
'''Latest firmware is available at the main page of the device.''' In the wiki one can only find older firmware, that still might be helpful. The projects listed below are no longer officially supported. The best practice is to use the EXACT same compiler as mentioned and in most cases the exact same IDE version as mentioned.

Older firmware released by Olimex for MOD-IO2:

1)MOD-IO2 v4.3 - binary, source, and how-to - [https://www.olimex.com/Products/Modules/IO/MOD-IO2/resources/MOD-IO2_firmware_v43.zip click to download] - this is the last firmware suitable for boards with PIC16 (before revision C changed main chip to CH32V003), which was added in its newer 4.3 version

1)MOD-IO2 v3.2/3.02 - binary, source, and how-to - [https://www.olimex.com/Products/Modules/IO/MOD-IO2/resources/MOD-IO2_firmware_v_3_02.zip click to download] - this lacked analog out (DAC), which was added in its newer 4.3 version

2)MOD-IO2 v3.1/3.01 firmware - binary, source, and how-to - [https://www.olimex.com/Products/Modules/IO/MOD-IO2/resources/MOD-IO2_firmware_v_3_1.zip click to download] - it lacked several functions which are now added, refer to the readme in the folder of the newest 3.02 firmware

3)MOD-IO2 v3 firmware - binary, source, and how-to - [https://www.olimex.com/Products/Modules/IO/MOD-IO2/resources/MOD-IO2_firmware_v3.zip click to download] - it has a bug with the internal weak pull-ups

4)MOD-IO2 v2 firmware - binary, source, and how-to - [https://www.olimex.com/Products/Modules/IO/MOD-IO2/resources/MOD-IO2+OLinuXino.zip click to download] - protocol fixes

5)MOD-IO2 v1 firmware - C source and HEX for I2C control - [https://www.olimex.com/Products/Modules/IO/MOD-IO2/resources/MOD-IO2_demo_and_firmware.zip click to download] - initial release

== Projects ==
Under construction

== FAQ ==
Under construction

[[Category:IO]]

RK3188-SOM

2024-05-15T12:06:23Z

LubOlimex: /* Debian for NAND memory */

== Overview ==

[[File:Rk3188-som-resized.png|650px]]

RK3188-SOM board is a very productive small beast compared to the previous Olimex board designs. If we compare RockChip RK3188 and Allwinner A20: RK3188 has 4x Cortex-A9, while A20 only 2x Cortex-A7. It runs at 1.6 GHz vs. the 1.0 GHz frequency of the A20. RK3188 reaches a total of 16000 DMPIS vs. the 3800 DMIPS for the A20 (RK3188 is 4.2 times faster). For comparison, the RaspberryPi has 965 DMIPS (RK3188 is 16.6 times faster).

The RK3188-SOM design has the following features:

*Rockchip RK3188 quad core Cortex-A9 processor, each core typically running at 1.6GHz
*1GB DDR3 memory
*Integrated power management unit
*Optional 4GB NAND flash memory for Linux or Android boot
*Micro SD-card for Linux or Android boot
*Three buttons - POWER, RESET, RECOVERY
*Four LEDs (one for power and three user-programmable)
*UART console pins exposed for serial debug
*Five GPIO connectors 2×20 pins @ 0.05" step
*Dimensions: (3.2×1.8)" ~ (81×56)mm
 

== Ready-to-use Debian images ==
=== Debian for microSD card ===

'''Newest official release (recommended):'''

Direct download of Debian release #2:[https://ftp.olimex.com/RK3188_Images/RK3188_debian_3.0.36_SD_release2.img RK3188-SOM Debian for microSD card - kernel 3.0.36+ - release #2]

In the command line interface of image you are automatically logged as root. The default superuser username/password combination in the GUI (XFCE4) is: olimex/olimex.

Build instructions and links to required files for the latest Debian images might be found below in chapter "Building Linux for RK3188-SOM".

====How to prepare your microSD card with the suitable official Debian image?====
----
In order to download an official Linux image to a microSD card under Windows you can use Win32 Disk Imager: [http://sourceforge.net/projects/win32diskimager/ click here]

1. Download the latest official image suitable for a microSD card from the chapter above

2. Download Win32 Disk Imager from this link.

3. Insert card in your microSD card reader.

4. Launch the software.

5. Point the software to the image

6. Click "write"

Under Linux you can write the image image to the card with dd utility. This is how it can be done:

Let's say the name of the image is "debian_2g.img". It would be downloaded to the microSD card connected to a Linux machine using one of the following commands:

dd bs=4M oflag=sync if=debian_2g.img of=/dev/sdX

or

cp debian_2g.img /dev/sdX

where /dev/sdX is the uSD card as listed by the Linux.

=== Debian for NAND memory ===

'''Newest official release (recommended):'''

Direct download Debian for NAND release #1: [https://ftp.olimex.com/RK3188_Images/RK3188_debian_3.0.36_NAND_release1.img RK3188-SOM Debian for NAND memory - kernel 3.0.36+ - release #1]

Note that this image is suitable only for RK3188-SOM-4GB boards.

Build instructions and links to required files for the latest Debian images might be found below in chapter "Building Linux for RK3188-SOM"

====How to download the ready Debian image to the NAND memory of RK3188-SOM?====
----

'''IMPORTANT: RK3188-SOM-4GB comes with Debian already pre-loaded on the NAND memory. No need to perform this operation initially.'''

1. You need to download the software tools for your computer provided by Rockchip. If you use Windows download “Rockchip Batch Tool”. If you use Linux use either rkflashkit or upgrade_tool. These are the tools that I recommend but there are a lot of tools available. Get the Rockchip batch tool from here: [https://drive.google.com/file/d/0BwplT87k9SCgRDB4ZGY3SnMzd00/view?usp=sharing Rockchip Batch Tool]

For Windows:

2. Install the drivers that allows your computer to recognize the board (that is already set in bootloader mode) connected to it. The installer is called "Rockchip Driver Assistant" – download it here: [https://drive.google.com/file/d/0BwplT87k9SCgbkdXX1ByUW1RSW8/view?usp=sharing Rockchip Driver Assistant]

3. You need to download and extract the latest image suitable for the NAND from our wiki. It is available as a direct download here: [https://ftp.olimex.com/RK3188_Images/RK3188_debian_3.0.36_NAND_release1.img RK3188 Debian 3.0.36 for NAND memory]

4. You need enter bootloader mode with the board to be able to establish connection between the board and the software provided by Rockchip. You would also need a mini USB cable. To enter bootloader mode you need to press and hold down the recovery button before powering the board (then connect the board to the PC via the mini USB cable). After the board is powered you can release the button.

5. Start the tool for uploading the firmware and point it to the extracted image.

6. Click button "Upgrade".

7. Test with a serial cable.

== Ready-to-use Android images ==
TODO

== Documents ==

[https://www.olimex.com/Products/SOM/RK3188/RK3188-SOM/resources/RK3188-SOM-UM.pdf OLIMEX RK3188-SOM user's manual]

[https://www.olimex.com/Products/SOM/RK3188/RK3188-SOM-EVB/resources/RK3188-SOM-EVB-UM.pdf OLIMEX RK3188-SOM-EVB user's manual]

[https://github.com/OLIMEX/OLINUXINO/raw/master/HARDWARE/RK3188-PDFs/Rockchip%20RK3188%20datasheet%20V1.0.pdf Processor (Rockchip RK3188) datasheet in pdf format]

[https://www.olimex.com/Products/SOM/RK3188/RK3188-SOM/resources/RK3188_SOM_GPIOs.pdf RK3188-SOM connectors' pinout and GPIO table]

=== CAD files ===

RK3188-SOM is considered commercial, proprietary design. The board file is not available to the customer. A pdf extracted from the original schematic is available at GitHub: [https://github.com/OLIMEX/SOM/tree/master/RK3188/RK3188-SOM RK3188-SOM schematics]

RK3188-SOM-EVB is considered Open Source Hardware, Eagle CAD files are available also at GitHub: [https://github.com/OLIMEX/SOM/tree/master/RK3188/RK3188-EVB RK3188-SOM-EVB sources]

The CAD product used to design OLinuXino is Eagle and you can download evaluation free version from their [http://www.cadsoftusa.com/ web site]. The evaluation version allows you to inspect the schematic and the board file sources.

==Board Layout==

[[File:Rk3188-som-resized-TOP-NAMED.png|650px]]

[[File:Rk3188-som-resized-BOTTOM-NAMED.png|650px]]

== Building Linux for RK3188-SOM ==
=== Building the parameter file ===
----
The parameter file describes many board parameters as firmware version, machine id, manufacturer name, etc.

For the user the most important parameter is '''CMDLINE'''. This is the command that is passed to the kernel. It looks something like this:
CMDLINE:console=ttyFIQ0,115200 console=tty0 root=/dev/mmcblk0p1 rw rootfstype=ext4 init=/sbin/init initrd=0x62000000,0x00800000 \
mtdparts=rk29xxnand:0x00008000@0x00002000(boot),-@0x0000A000(linuxroot)

Define serial port at 115200:
console=ttyFIQ0,115200

Define location of the rootfs:
root=/dev/mmcblk0p1

Define rootfs file system as ext4:
rootfstype=ext4

Define the address of the kernel and size:
0x00008000@0x00002000

Define start address of the rootfs:
-@0x0000A000

Additionally, you can set static MAC address with:
mac_addr=xx:xx:xx:xx:xx:xx

Once you're ready with the file, make the parameter image

* Get rkutils:
https://github.com/naobsd/rkutils
cd rkutils
gcc rkcrc.c -o rkcrc
If you're getting error try to comment ''''#include <err.h>'''' in ''''rkcrc.c''''

* Encrypt parameter file:
./rkcrc -p you_parameter_file parameter

The parameter file is ready for further use.

=== Building the kernel ===
----
* Fist prepare the toolchain:
apt-get update
apt-get install gcc-4.7-arm-linux-gnueabihf ncurses-dev uboot-mkimage build-essential git

* Get the sources:
git clone -b olimex/stable-3.0 https://github.com/StefanMavrodiev/RK3188-SOM.git

* Get the default configuration:
cd RK3188-SOM/
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- '''olimex_rk3188_defconfig'''

* You can modify defconfig with (for additional modules):
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- menuconfig

'''Note!''' The default config will set hdmi to 1080p. You can change it from:
Device Drivers --->
Graphics support --->
<*> Frame buffer support for Rockchip --->
LCD Panel Select --->
'''''Choose one of the following:'''''
HDMI framebuffer size and timing is 1080p <--- '''Set HDMI to 1080p'''
HDMI framebuffer size and timing is 720p <--- '''Set HDMI to 720p'''
HDMI framebuffer size and timing is 480p <--- '''Set HDMI to 480p'''
RGB AT070TN90 <--- [https://www.olimex.com/Products/OLinuXino/LCD/LCD-OLinuXino-7/open-source-hardware LCD-OLinuXino-7]
RGB AR010H05N <--- [https://www.olimex.com/Products/OLinuXino/LCD/LCD-OLinuXino-10/open-source-hardware LCD-OLinuXino-10]
RGB BT043DCNNHHP <--- [https://www.olimex.com/Products/OLinuXino/LCD/LCD-OLinuXino-4.3TS/open-source-hardware LCD-OLinuXino-4.3TS]

* Build the kernel:
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- -j4 kernel.img
After the build is finish you will have '''RK3188-SOM/kernel.img''' and '''RK3188-SOM/arch/arm/boot/Image'''. The first one can be uploaded to the kernel partition (if you have one). The second file is raw binary. It can be combined with ramdisk to get boot.img.

* Generate ramdisk
cd ../
git clone https://github.com/radxa/initrd.git
cd initrd/
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- -j4
cd ../

* Make mkbootimg
git clone https://github.com/neo-technologies/rockchip-mkbootimg.git
cd rockchip-mkbootimg
make
make install
cd ../

* Make boot.img
mkbootimg --kernel RK3188-SOM/arch/arm/boot/Image --ramdisk initrd.img -o boot.img

=== Creating the root filesystem ===
==== Debian Wheezy ====
----
In this post we will explain how you can create your own Debian rootfs with pre-installed packages of your choice, which to allow tiny Linux images to be created. All steps below should work on any Debian host (Debian/Ubuntu etc) and are verified with Ubuntu 12.04LTS. First of all you need to install the support packages on your pc:

* Install the needed packages:
sudo apt-get install qemu-user-static debootstrap binfmt-support

* Define some variables:
targetdir=rootfs
distro=wheezy

* Build first stage:
mkdir $targetdir
sudo debootstrap --arch=armhf --foreign $distro $targetdir

* Copy needed files from host to the target:
sudo cp /usr/bin/qemu-arm-static $targetdir/usr/bin/
sudo cp /etc/resolv.conf $targetdir/etc

We should now have a minimal Debian Rootfs.
* Login into the new filesystem:
sudo chroot $targetdir

* Inside the chroot we need to set up the environment again:
distro=wheezy
export LANG=C

* Now we would run the setup for the second stage of debootstrap needs to run install the packages downloaded earlier
/debootstrap/debootstrap --second-stage

* Once the package installation has finished, setup some support files and apt configuration.
cat <<EOT > /etc/apt/sources.list
deb http://ftp.uk.debian.org/debian $distro main contrib non-free
deb-src http://ftp.uk.debian.org/debian $distro main contrib non-free
deb http://ftp.uk.debian.org/debian $distro-updates main contrib non-free
deb-src http://ftp.uk.debian.org/debian $distro-updates main contrib non-free<
deb http://security.debian.org/debian-security $distro/updates main contrib non-free
deb-src http://security.debian.org/debian-security $distro/updates main contrib non-free

EOT

* Update Debian package database:
apt-get update

* Set up locales dpkg scripts since it tends to complain otherwise; note in Debian Jessie you will also need to install the dialog package as well:
apt-get install locales dialog sudo
dpkg-reconfigure locales

* Fix permission for sudo:
chmod u+s /usr/bin/sudo

* Fix ownership of man forlder
chown -R man /var/cache/man

* Install some useful packages inside the chroot:
apt-get install openssh-server ntpdate

* Set a root password so you can login:
passwd

* Build a basic network interface file:
vi /etc/network/interfaces
Add the following to get static ip:
allow-hotplug eth0
iface eth0 inet static
address 192.168.1.254
netmask 255.255.255.248
gateway 192.168.1.1
Or if you want dhcp
allow-hotplug eth0
iface eth0 inet dhcp

Note: Your board will be accessible over SSH on IP address defined above!

* Set the hostname
echo '''myhost'''> /etc/hostname
echo "127.0.0.1 '''myhost'''" >> /etc/hosts

* Enable the serial console, Debian sysvinit way
echo T0:2345:respawn:/sbin/getty -L ttyFIQ0 115200 vt100 >> /etc/inittab

This way you'll get login prompt at startup. By default you cannot login as root. To do this you should make another user, add him to the sudo group, login at startup and then login as root. To skip all this replace the line above with:
echo T0:2345:respawn:/sbin/getty -L ttyFIQ0 -a root 115200 vt100 >> /etc/inittab

* We are done inside the chroot, so quit the chroot shell
exit

* Tidy up the support files
sudo rm $targetdir/etc/resolv.conf
sudo rm $targetdir/usr/bin/qemu-arm-static

===== Installing X =====
----
You cannot run X as root (actually it's possible, but it's a bad practice), so you have to add new user to run X.

* Edit default useradd settings
vi /etc/default/useradd
Modify '''SHELL''' variable:
SHELL=/bin/bash

* Add new user
useradd '''myuser'''

* Add the user to the sudo group
adduser '''myuser''' sudo

* Make home folder
mkdir /home/'''myuser'''
chown -R '''myuser''':'''myuser''' /home/'''myuser'''

* Install xfce4 and lightdm
apt-get update
apt-get install lightdm xfce4

* Modify lightdm configuration to enable autologin:
vi /etc/lightdm/lightdm.conf
autologin-user='''myuser'''
autologin-user-timeout=0
Make sure that the right lines are uncommented. If you don't want autologin just skip the step above.

* Reboot the system
reboot
After the system loads, you should see the default desktop of xfce4.

==== Ubuntu ====
----

You can download prebuild rootfs from [http://releases.linaro.org/ linaro] site or you can build it yourself.

===== Prebuild linaro images =====
----

You can download prebuild images from https://releases.linaro.org/.
In most cases the builds are separated in:
*'''nano'''
*'''developer'''
*'''server'''
*'''alip'''

You can read additional information from [https://wiki.linaro.org/Platform/DevPlatform/Rootfs here].

In this tutorial we will build Ubuntu 14.10 ALIP rootfs.

* Make empty image file:
dd if=/dev/zero of=linaro_alip_rootfs.img bs=1M count=1024

* Format the new image file:
mkfs.ext4 -F -L linuxroot linaro_alip_rootfs.img

* Create mount point:
mkdir mnt
mount -o loop linaro_alip_rootfs.img ./mnt

* Download prebuild image:
wget https://releases.linaro.org/14.10/ubuntu/trusty-images/alip/linaro-trusty-alip-20141024-684.tar.gz

* Make sure that the archive is downloaded:
md5sum linaro-trusty-alip-20141024-684.tar.gz

* Extract is into the mounted image file:
tar -zxvf linaro-trusty-alip-20141024-684.tar.gz
mv binary/* ./mnt

* Copy any modules that are generated with the kernel:
cp -rvf /'''path/to/modules'''/lib/modules ./mnt/lib/

* Chroot into the new rootfs:
cp /usr/bin/qemu-arm-static ./mnt/usr/bin
cp /etc/resolv.conf ./mnt/etc
chroot ./mnt

* Update repository
apt-get update
'''Note!''' If you have a problem with the update, try changing '''sources.list''' to:
deb http://old-releases.ubuntu.com/ubuntu/ raring main universe restricted multiverse
deb-src http://old-releases.ubuntu.com/ubuntu/ raring main universe restricted multiverse
deb http://old-releases.ubuntu.com/ubuntu/ raring-security main universe restricted multiverse
deb-src http://old-releases.ubuntu.com/ubuntu/ raring-security main universe restricted multiverse
deb http://old-releases.ubuntu.com/ubuntu/ raring-updates main universe restricted multiverse
deb-src http://old-releases.ubuntu.com/ubuntu/ raring-updates main universe restricted multiverse
deb http://old-releases.ubuntu.com/ubuntu/ raring-backports main restricted universe multiverse
deb-src http://old-releases.ubuntu.com/ubuntu/ raring-backports main restricted universe multiverse
deb http://old-releases.ubuntu.com/ubuntu/ raring-proposed main restricted universe multiverse
deb-src http://old-releases.ubuntu.com/ubuntu/ raring-proposed main restricted universe multiverse

* Install some useful packages:
apt-get install ssh nano wpasupplicant wireless-tools

* Set root password:
passwd

Linaro prebuild images comes with default use '''linaro'''.
* Set password for user:
passwd linaro

* Add '''linaro''' to sudo group:
adduser linaro sudo

* Configure network. Create new file for loopback, wlan and eth device:
vi /etc/network/interfaces.d/lo
Inside paste:
auto lo
iface lo inet loopback

Do the same for eth:
vi /etc/network/interfaces.d/eth
If you're using dhcp:
auto eth0
iface eth0 inet dhcp
Or for static ip:
auto eth0
iface eth0 inet static
address <your.ip.here>
netmask <your.netmask.here>
gateway <your.gateway.here>

And another for wireless devices:
vi /etc/network/interfaces.d/wlan
auto wlan0
iface lo inet dhcp
wpa-ssid <your.router.ssid>
wpa-pak <your.ssid.password>

'''Note!''' All connections are '''auto'''. If you don't want to use them all the time remove '''auto''' line.

You can do some additional work before exit.
When you are ready to exit from the target filesystem:
exit

Your rootfs is ready. The next step is to create image for nand or sdcard.

===== Manual build using debootstrap =====
----
The procedure is almost identical to the one used for the Debin image.

* First of all you need to install the support packages on your pc
sudo apt-get install qemu-user-static debootstrap binfmt-support ubuntu-archive-keyring

* We will build latest trusty Ubuntu image:
targetdir=ubuntu
distro=trusty

* Now we will build first stage of Ubuntu rootfs:
mkdir $targetdir
sudo debootstrap --arch=armhf --keyring=/usr/share/keyrings/ubuntu-archive-keyring.gpg --foreign $distro $targetdir

* Login into the new filesystem
sudo cp /usr/bin/qemu-arm-static $targetdir/usr/bin/
sudo cp /etc/resolv.conf $targetdir/etc
sudo chroot $targetdir

* Inside the chroot we need to set up the environment again
distro=trusty
export LANG=C

* Now we are setup the second stage of debootstrap needs to run install the packages downloaded earlier
/debootstrap/debootstrap --second-stage

* Configure apt-sources:
cat <<EOT > /etc/apt/sources.list
###### Ubuntu Main Repos
deb http://ports.ubuntu.com/ubuntu-ports/ $distro main restricted universe multiverse
deb-src http://ports.ubuntu.com/ubuntu-ports/ $distro main restricted universe multiverse
###### Ubuntu Update Repos
deb http://ports.ubuntu.com/ubuntu-ports/ $distro-security main restricted universe multiverse
deb http://ports.ubuntu.com/ubuntu-ports/ $distro-updates main restricted universe multiverse
deb-src http://ports.ubuntu.com/ubuntu-ports/ $distro-security main restricted universe multiverse
deb-src http://ports.ubuntu.com/ubuntu-ports/ $distro-updates main restricted universe multiverse
EOT

* Update Ubuntu package database:
apt-get update

* Set a root password so you can login
passwd

* Set the hostname
echo '''myhost'''> /etc/hostname
echo "127.0.0.1 '''myhost'''" >> /etc/hosts

* Build a basic network interface file so that the board will DHCP on eth0
echo <<EOT >> /etc/network/interfaces
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet dhcp
EOT

* Enable the serial console, Debian sysvinit way
echo T0:2345:respawn:/sbin/getty -L ttyFIQ0 115200 vt100 >> /etc/inittab

This way you'll get login prompt at startup. By default you cannot login as root. To do this you should make another user,
add him to the sudo group, login at startup and then login as root. To skip all this replace the line above with:
echo T0:2345:respawn:/sbin/getty -L ttyFIQ0 -a root 115200 vt100 >> /etc/inittab

* We are done inside the chroot, so quit the chroot shell
exit

* Tidy up the support files
sudo rm $targetdir/etc/resolv.conf
sudo rm $targetdir/usr/bin/qemu-arm-static

==== Make rootfs image ====
----

Once you are ready with the rootfs you can make image file. Later it can be used for NAND or SD image. Go to parent directory of you rootfs.

* See how big the image should be:
# du -khs <roofs_folder>
For example this will return 600MB. So we will make 1GB image.

* Make empty image:
# dd if=/dev/zero of=rootfs.img bs=1M count=1024

* Format the image:
# mkfs.ex4 -F -L linuxroot rootfs.img

* Mount the image:
# mount -o loop rootfs.img /mnt

* Copy rootfs files into the image:
# cp -prf <root_folder>/* /mnt/
''''Note!''' Use -p option to keep the permissions for the files and folders.

* Unmount the image:
# umount /mnt

=== Booting from NAND ===
----
* Get rk-tools:
git clone https://github.com/goodybag/rk-tools
cd rk-tools
make

*You will need the following files:
**bootloader --> This is RockChip RK3188Loader
**[[#Building parameter file|parameter]] --> Parameter file with crc encryption
**[[#Building kernel|boot]] --> Kernel with ramdisk compiled as shown here
**[[#Creating root filesystem|linux]] --> Rootfs image file
'''CMDLINE''' in parameter file should look something like this:
CMDLINE:console=ttyFIQ0,115200 console=tty0 root=/dev/block/mtd/by-name/linuxroot rw rootfstype=ext4 init=/sbin/init initrd=0x62000000,0x00800000 mtdparts=rk29xxnand:0x00008000@0x00002000(boot),-@0x0000A000(linuxroot)

* Copy all files in '''rk-tools''' folder

* Edit '''package-file'''. It should be:
#nano package-file

# NAME Relative path
#
#HWDEF HWDEF
package-file package-file
bootloader RK3188Loader
parameter parameter
boot boot.img
linuxroot rootfs.img
backup RESERVED
update-script update-script
recover-script recover-script

* Pack the image:
./afptool -pack . update_tmp.img

* Update the image:
./img_maker -rk31 RK3188Loader 1 0 0 update_tmp.img update.img

The image should be ready. What's left is flashing the image.

*Important: to flash the image the board needs to be in bootloader mode. To enter bootloader mode you need to press and hold down the recovery button before connecting the board to the PC. After the connection is established you can release the button.

 

=== Booting from SD-card ===
----
You'll need at least 512MB sd-card. Depending on rootfs needed size can grow to 4GB.

*You will need the following files:
**sdboot_rk3188.img --> RK3188Loader for booting from SDcard
**[[#Building parameter file|parameter]] --> Parameter file with crc encryption
**[[#Building kernel|boot]] --> Kernel with ramdisk compiled as shown here
**[[#Creating root filesystem|linux]] --> Rootfs image file

'''CMDLINE''' in parameter file should look something like this:
CMDLINE:console=ttyFIQ0,115200 console=tty0 root=/dev/mmcblk0p1 rw rootfstype=ext4 init=/sbin/init initrd=0x62000000,0x00800000 mtdparts=rk29xxnand:0x00008000@0x00002000(boot),-@0x0000A000(linuxroot)

Insert sd-card. Lets say that your device is '''/dev/sdc'''.

* Write Rockchip loader:
dd if=sdboot_rk3188.img of=/dev/sdc conv=sync,fsync

* Write parameter file:
dd if=parameter.img of=/dev/sdc conv=sync,fsync seek=$((0x2000))

* Write kernel:
dd if=boot.img of=/dev/sdc conv=sync,fsync seek=$((0x2000+0x2000))

* Write rootfs:
dd if=rootfs.img of=/dev/sdc conv=sync,fsync seek=$((0x2000+0xA000))

You can do this also on image file:
dd if=/dev/zero of=sd.img bs=1M count=1024
If 1GB is not enough increase count number.

* Write Rockchip loader:
dd if=sdboot_rk3188.img of=sd.img conv=sync,fsync

* Write parameter file:
dd if=parameter.img of=sd.img conv=sync,fsync seek=$((0x2000))

* Write kernel:
dd if=boot.img of=sd.img conv=sync,fsync seek=$((0x2000+0x2000))

* Write rootfs:
dd if=rootfs.img of=sd.img conv=sync,fsync seek=$((0x2000+0xA000))

* Format image:
fdisk sd.img << EOF
n
p
1
49152

w
EOF

=== Calibrate touchscreen ===
If you want to use LCD panel with touchscreen, you should perform a screen calibration.

==== Calibrate using tslib ====
----

* Install the required packages:
apt-get update
apt-get install xorg-dev xserver-xorg-dev x11proto-core-dev git automake make libtool

* Download tslib:
git clone https://github.com/kergoth/tslib.git
cd tslib

* Download patch:
cd plugin
wget https://dl.dropbox.com/u/40057/patches/input-raw.c
cd ../

* Compile the library:
autoreconf -vi
./configure --prefix=/usr
make
make install
ldconfig

* Modify tslib configuration
vi /usr/etc/ts.conf
Uncomment the following line:
module_raw input

* Export tslib needed variables:
export TSLIB_TSEVENTTYPE=raw
export TSLIB_CONSOLEDEVICE=none
export TSLIB_FBDEVICE=/dev/fb0
export TSLIB_TSDEVICE=/dev/input/event0
export TSLIB_CALIBFILE=/usr/etc/pointercal
export TSLIB_CONFFILE=/usr/etc/ts.conf
export TSLIB_PLUGINDIR=/usr/lib/ts

* Now tslib is working but still it should be set as default driver in the X:
wget http://ftp.de.debian.org/debian/pool/main/x/xf86-input-tslib/xf86-input-tslib_0.0.6.orig.tar.gz
tar zxfv xf86-input-tslib_0.0.6.orig.tar.gz
cd xf86-input-tslib-0.0.6/
Replace tslib.c file with patched one:
cd src/
rm -f tslib.c
wget https://dl.dropbox.com/u/40057/patches/tslib.c
cd ..
Build and install package:
./configure --prefix=/usr
make
make install

* Add tslib configuration:
cd /usr/share/X11/xorg.conf.d/
Make new file:
nano 20-touchscreen.conf
Add the following text inside:
Section "InputClass"
Identifier "AR1020"
MatchDevicePath "/dev/input/event0"
Driver "tslib"
Option "Device" "/dev/input/event0"
Option "ScreenNumber" "0"
Option "Rotate" "NONE"
Option "Width" "'''800'''"
Option "Height" "'''480'''"
Option "SendCoreEvents" "yes"
Option "Type" "touchscreen"
EndSection
Note! Resolution in this example is set for 7 inch LCD.

* Do the actual calibration:
service lightdm stop
ts_calibrate
service lightdm start
After lightdm start you could check if everything is running smoothly.

* Save tslib variables:
vi /etc/environment
Paste the following:
TSLIB_TSEVENTTYPE=raw
TSLIB_CONSOLEDEVICE=none
TSLIB_FBDEVICE=/dev/fb0
TSLIB_TSDEVICE=/dev/input/event0
TSLIB_CALIBFILE=/etc/pointercal
TSLIB_CONFFILE=/usr/etc/ts.conf
TSLIB_PLUGINDIR=/usr/lib/ts

If you change the LCD panel run ts_calibrate to configure touchscreen for the new LCD.

==== Calibrate using AR1021 driver ====
TODO

=== Enabling wireless modules ===
==== RTL8188CUS ====
----
[[File:MOD-WIFI-RTL8188-1.jpg|thumb|[https://www.olimex.com/Products/USB-Modules/MOD-WIFI-RTL8188/ MOD-WIFI-RTL8188]]]
To connect OLinuXino board with wireless, you could use [https://www.olimex.com/Products/USB-Modules/MOD-WIFI-RTL8188/ MOD-WIFI-RTL8188] dongle. Also you can use another one with the same chip.

[https://www.olimex.com/Products/USB-Modules/MOD-WIFI-RTL8188/ MOD-WIFI-RTL8188] has the following features:
* Has WM-294 module with RTL8188
* Operates in 2.4 GHz frequency bands
* 1x1 MIMO technology improves effective throughput and range over existing 802.11 b/g products
* Data rates: up to 150Mbps
* 802.11e-compatible bursting and I standards BPSK, QPSK, 16 QAM, 64 QAM modulation schemes WEP, TKIP, and AES, WPA, WPA2 hardware encryption schemes
* Standard USB type A connector
* On-board antenna
* 5V/3.3V operation modes via SMD jumper
* 4 test pads for easy tracking the supply, d-, d+, and GND
* PCB: FR-4, 1.00 mm (0,039"), solder mask, silkscreen component print
* Dimensions: 65.15x20.38 mm (2.56x0.80")
----

The kernel module is prebuild. You should just get it loaded and then plug the dongle.
* Load the module:
modprobe 8192cu

* Plug the device and check if it is available:
ifconfig -a

==== RT5370 ====
----
[[File:MOD-WIFI-R5370-ANT-1.jpg|border|thumb|[https://www.olimex.com/Products/USB-Modules/MOD-WIFI-R5370-ANT/ MOD-WIFI-R5370-ANT]]]

To use one this wifi dongle (like [https://www.olimex.com/Products/USB-Modules/MOD-WIFI-R5370/ MOD-WIFI-R5370] or [https://www.olimex.com/Products/USB-Modules/MOD-WIFI-R5370-ANT/ MOD-WIFI-R5370-ANT]) additional files are required.

[https://www.olimex.com/Products/USB-Modules/MOD-WIFI-R5370-ANT/ MOD-WIFI-R5370-ANT] has the following features:

* 2.4GHz with 150Mbps PHY data rate
*External antenna for extended range
*USB 2.0 interface
*Security: WEP/TKIP/AES/WPA/WPA2/WAPI
*CMOS single chip with RF, baseband, and MAC integration
*QoS: WMM & WMM-PS support
*Multiple BSSID support
*Maximum likelihood decoding support
*Cisco CCX 5.0 support
*Low-power usage with advanced power management
----

*First a make new directory and navigate to it. This is where the module will search for files.
mkdir -p /etc/Wireless/RT2870STA
cd /etc/Wireless/RT2870STA/

*Download the files from Github
wget https://raw.githubusercontent.com/SelfDestroyer/RK3188-SOM/olimex/stable-3.0/drivers/net/wireless/rtxx7x/RT2870STA.dat
wget https://raw.githubusercontent.com/SelfDestroyer/RK3188-SOM/olimex/stable-3.0/drivers/net/wireless/rtxx7x/RT2870STACard.dat

*Load module
modprobe rt5370sta

*Plug the device and run:
ifconfig -a
*You should see this:
wlan0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

*Configure your new device:
vi /etc/network/interfaces
*Add configuration. Here we will show DHCP configuration.
iface wlan0 inet dhcp
wpa-ssid "'''your ssid'''"
wpa-psk "'''your password'''"

*Save the configuration and up the interface:
ifup wlan0

*If everything is working and this module to be loaded on boot:
echo rt5370sta >> /etc/modules

== Android ==

RK3188-SOM

2024-05-15T11:52:07Z

LubOlimex: /* How to download the ready Debian image to the NAND memory of RK3188-SOM? */

== Overview ==

[[File:Rk3188-som-resized.png|650px]]

RK3188-SOM board is a very productive small beast compared to the previous Olimex board designs. If we compare RockChip RK3188 and Allwinner A20: RK3188 has 4x Cortex-A9, while A20 only 2x Cortex-A7. It runs at 1.6 GHz vs. the 1.0 GHz frequency of the A20. RK3188 reaches a total of 16000 DMPIS vs. the 3800 DMIPS for the A20 (RK3188 is 4.2 times faster). For comparison, the RaspberryPi has 965 DMIPS (RK3188 is 16.6 times faster).

The RK3188-SOM design has the following features:

*Rockchip RK3188 quad core Cortex-A9 processor, each core typically running at 1.6GHz
*1GB DDR3 memory
*Integrated power management unit
*Optional 4GB NAND flash memory for Linux or Android boot
*Micro SD-card for Linux or Android boot
*Three buttons - POWER, RESET, RECOVERY
*Four LEDs (one for power and three user-programmable)
*UART console pins exposed for serial debug
*Five GPIO connectors 2×20 pins @ 0.05" step
*Dimensions: (3.2×1.8)" ~ (81×56)mm
 

== Ready-to-use Debian images ==
=== Debian for microSD card ===

'''Newest official release (recommended):'''

Direct download of Debian release #2:[https://ftp.olimex.com/RK3188_Images/RK3188_debian_3.0.36_SD_release2.img RK3188-SOM Debian for microSD card - kernel 3.0.36+ - release #2]

In the command line interface of image you are automatically logged as root. The default superuser username/password combination in the GUI (XFCE4) is: olimex/olimex.

Build instructions and links to required files for the latest Debian images might be found below in chapter "Building Linux for RK3188-SOM".

====How to prepare your microSD card with the suitable official Debian image?====
----
In order to download an official Linux image to a microSD card under Windows you can use Win32 Disk Imager: [http://sourceforge.net/projects/win32diskimager/ click here]

1. Download the latest official image suitable for a microSD card from the chapter above

2. Download Win32 Disk Imager from this link.

3. Insert card in your microSD card reader.

4. Launch the software.

5. Point the software to the image

6. Click "write"

Under Linux you can write the image image to the card with dd utility. This is how it can be done:

Let's say the name of the image is "debian_2g.img". It would be downloaded to the microSD card connected to a Linux machine using one of the following commands:

dd bs=4M oflag=sync if=debian_2g.img of=/dev/sdX

or

cp debian_2g.img /dev/sdX

where /dev/sdX is the uSD card as listed by the Linux.

=== Debian for NAND memory ===

'''Newest official release (recommended):'''

Direct download Debian for NAND release #1: [https://ftp.olimex.com/RK3188_Images/RK3188_debian_3.0.36_NAND_release1.img|RK3188-SOM Debian for NAND memory - kernel 3.0.36+ - release #1]

Note that this image is suitable only for RK3188-SOM-4GB boards.

Build instructions and links to required files for the latest Debian images might be found below in chapter "Building Linux for RK3188-SOM"

====How to download the ready Debian image to the NAND memory of RK3188-SOM?====
----

'''IMPORTANT: RK3188-SOM-4GB comes with Debian already pre-loaded on the NAND memory. No need to perform this operation initially.'''

1. You need to download the software tools for your computer provided by Rockchip. If you use Windows download “Rockchip Batch Tool”. If you use Linux use either rkflashkit or upgrade_tool. These are the tools that I recommend but there are a lot of tools available. Get the Rockchip batch tool from here: [https://drive.google.com/file/d/0BwplT87k9SCgRDB4ZGY3SnMzd00/view?usp=sharing Rockchip Batch Tool]

For Windows:

2. Install the drivers that allows your computer to recognize the board (that is already set in bootloader mode) connected to it. The installer is called "Rockchip Driver Assistant" – download it here: [https://drive.google.com/file/d/0BwplT87k9SCgbkdXX1ByUW1RSW8/view?usp=sharing Rockchip Driver Assistant]

3. You need to download and extract the latest image suitable for the NAND from our wiki. It is available as a direct download here: [https://ftp.olimex.com/RK3188_Images/RK3188_debian_3.0.36_NAND_release1.img RK3188 Debian 3.0.36 for NAND memory]

4. You need enter bootloader mode with the board to be able to establish connection between the board and the software provided by Rockchip. You would also need a mini USB cable. To enter bootloader mode you need to press and hold down the recovery button before powering the board (then connect the board to the PC via the mini USB cable). After the board is powered you can release the button.

5. Start the tool for uploading the firmware and point it to the extracted image.

6. Click button "Upgrade".

7. Test with a serial cable.

== Ready-to-use Android images ==
TODO

== Documents ==

[https://www.olimex.com/Products/SOM/RK3188/RK3188-SOM/resources/RK3188-SOM-UM.pdf OLIMEX RK3188-SOM user's manual]

[https://www.olimex.com/Products/SOM/RK3188/RK3188-SOM-EVB/resources/RK3188-SOM-EVB-UM.pdf OLIMEX RK3188-SOM-EVB user's manual]

[https://github.com/OLIMEX/OLINUXINO/raw/master/HARDWARE/RK3188-PDFs/Rockchip%20RK3188%20datasheet%20V1.0.pdf Processor (Rockchip RK3188) datasheet in pdf format]

[https://www.olimex.com/Products/SOM/RK3188/RK3188-SOM/resources/RK3188_SOM_GPIOs.pdf RK3188-SOM connectors' pinout and GPIO table]

=== CAD files ===

RK3188-SOM is considered commercial, proprietary design. The board file is not available to the customer. A pdf extracted from the original schematic is available at GitHub: [https://github.com/OLIMEX/SOM/tree/master/RK3188/RK3188-SOM RK3188-SOM schematics]

RK3188-SOM-EVB is considered Open Source Hardware, Eagle CAD files are available also at GitHub: [https://github.com/OLIMEX/SOM/tree/master/RK3188/RK3188-EVB RK3188-SOM-EVB sources]

The CAD product used to design OLinuXino is Eagle and you can download evaluation free version from their [http://www.cadsoftusa.com/ web site]. The evaluation version allows you to inspect the schematic and the board file sources.

==Board Layout==

[[File:Rk3188-som-resized-TOP-NAMED.png|650px]]

[[File:Rk3188-som-resized-BOTTOM-NAMED.png|650px]]

== Building Linux for RK3188-SOM ==
=== Building the parameter file ===
----
The parameter file describes many board parameters as firmware version, machine id, manufacturer name, etc.

For the user the most important parameter is '''CMDLINE'''. This is the command that is passed to the kernel. It looks something like this:
CMDLINE:console=ttyFIQ0,115200 console=tty0 root=/dev/mmcblk0p1 rw rootfstype=ext4 init=/sbin/init initrd=0x62000000,0x00800000 \
mtdparts=rk29xxnand:0x00008000@0x00002000(boot),-@0x0000A000(linuxroot)

Define serial port at 115200:
console=ttyFIQ0,115200

Define location of the rootfs:
root=/dev/mmcblk0p1

Define rootfs file system as ext4:
rootfstype=ext4

Define the address of the kernel and size:
0x00008000@0x00002000

Define start address of the rootfs:
-@0x0000A000

Additionally, you can set static MAC address with:
mac_addr=xx:xx:xx:xx:xx:xx

Once you're ready with the file, make the parameter image

* Get rkutils:
https://github.com/naobsd/rkutils
cd rkutils
gcc rkcrc.c -o rkcrc
If you're getting error try to comment ''''#include <err.h>'''' in ''''rkcrc.c''''

* Encrypt parameter file:
./rkcrc -p you_parameter_file parameter

The parameter file is ready for further use.

=== Building the kernel ===
----
* Fist prepare the toolchain:
apt-get update
apt-get install gcc-4.7-arm-linux-gnueabihf ncurses-dev uboot-mkimage build-essential git

* Get the sources:
git clone -b olimex/stable-3.0 https://github.com/StefanMavrodiev/RK3188-SOM.git

* Get the default configuration:
cd RK3188-SOM/
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- '''olimex_rk3188_defconfig'''

* You can modify defconfig with (for additional modules):
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- menuconfig

'''Note!''' The default config will set hdmi to 1080p. You can change it from:
Device Drivers --->
Graphics support --->
<*> Frame buffer support for Rockchip --->
LCD Panel Select --->
'''''Choose one of the following:'''''
HDMI framebuffer size and timing is 1080p <--- '''Set HDMI to 1080p'''
HDMI framebuffer size and timing is 720p <--- '''Set HDMI to 720p'''
HDMI framebuffer size and timing is 480p <--- '''Set HDMI to 480p'''
RGB AT070TN90 <--- [https://www.olimex.com/Products/OLinuXino/LCD/LCD-OLinuXino-7/open-source-hardware LCD-OLinuXino-7]
RGB AR010H05N <--- [https://www.olimex.com/Products/OLinuXino/LCD/LCD-OLinuXino-10/open-source-hardware LCD-OLinuXino-10]
RGB BT043DCNNHHP <--- [https://www.olimex.com/Products/OLinuXino/LCD/LCD-OLinuXino-4.3TS/open-source-hardware LCD-OLinuXino-4.3TS]

* Build the kernel:
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- -j4 kernel.img
After the build is finish you will have '''RK3188-SOM/kernel.img''' and '''RK3188-SOM/arch/arm/boot/Image'''. The first one can be uploaded to the kernel partition (if you have one). The second file is raw binary. It can be combined with ramdisk to get boot.img.

* Generate ramdisk
cd ../
git clone https://github.com/radxa/initrd.git
cd initrd/
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- -j4
cd ../

* Make mkbootimg
git clone https://github.com/neo-technologies/rockchip-mkbootimg.git
cd rockchip-mkbootimg
make
make install
cd ../

* Make boot.img
mkbootimg --kernel RK3188-SOM/arch/arm/boot/Image --ramdisk initrd.img -o boot.img

=== Creating the root filesystem ===
==== Debian Wheezy ====
----
In this post we will explain how you can create your own Debian rootfs with pre-installed packages of your choice, which to allow tiny Linux images to be created. All steps below should work on any Debian host (Debian/Ubuntu etc) and are verified with Ubuntu 12.04LTS. First of all you need to install the support packages on your pc:

* Install the needed packages:
sudo apt-get install qemu-user-static debootstrap binfmt-support

* Define some variables:
targetdir=rootfs
distro=wheezy

* Build first stage:
mkdir $targetdir
sudo debootstrap --arch=armhf --foreign $distro $targetdir

* Copy needed files from host to the target:
sudo cp /usr/bin/qemu-arm-static $targetdir/usr/bin/
sudo cp /etc/resolv.conf $targetdir/etc

We should now have a minimal Debian Rootfs.
* Login into the new filesystem:
sudo chroot $targetdir

* Inside the chroot we need to set up the environment again:
distro=wheezy
export LANG=C

* Now we would run the setup for the second stage of debootstrap needs to run install the packages downloaded earlier
/debootstrap/debootstrap --second-stage

* Once the package installation has finished, setup some support files and apt configuration.
cat <<EOT > /etc/apt/sources.list
deb http://ftp.uk.debian.org/debian $distro main contrib non-free
deb-src http://ftp.uk.debian.org/debian $distro main contrib non-free
deb http://ftp.uk.debian.org/debian $distro-updates main contrib non-free
deb-src http://ftp.uk.debian.org/debian $distro-updates main contrib non-free<
deb http://security.debian.org/debian-security $distro/updates main contrib non-free
deb-src http://security.debian.org/debian-security $distro/updates main contrib non-free

EOT

* Update Debian package database:
apt-get update

* Set up locales dpkg scripts since it tends to complain otherwise; note in Debian Jessie you will also need to install the dialog package as well:
apt-get install locales dialog sudo
dpkg-reconfigure locales

* Fix permission for sudo:
chmod u+s /usr/bin/sudo

* Fix ownership of man forlder
chown -R man /var/cache/man

* Install some useful packages inside the chroot:
apt-get install openssh-server ntpdate

* Set a root password so you can login:
passwd

* Build a basic network interface file:
vi /etc/network/interfaces
Add the following to get static ip:
allow-hotplug eth0
iface eth0 inet static
address 192.168.1.254
netmask 255.255.255.248
gateway 192.168.1.1
Or if you want dhcp
allow-hotplug eth0
iface eth0 inet dhcp

Note: Your board will be accessible over SSH on IP address defined above!

* Set the hostname
echo '''myhost'''> /etc/hostname
echo "127.0.0.1 '''myhost'''" >> /etc/hosts

* Enable the serial console, Debian sysvinit way
echo T0:2345:respawn:/sbin/getty -L ttyFIQ0 115200 vt100 >> /etc/inittab

This way you'll get login prompt at startup. By default you cannot login as root. To do this you should make another user, add him to the sudo group, login at startup and then login as root. To skip all this replace the line above with:
echo T0:2345:respawn:/sbin/getty -L ttyFIQ0 -a root 115200 vt100 >> /etc/inittab

* We are done inside the chroot, so quit the chroot shell
exit

* Tidy up the support files
sudo rm $targetdir/etc/resolv.conf
sudo rm $targetdir/usr/bin/qemu-arm-static

===== Installing X =====
----
You cannot run X as root (actually it's possible, but it's a bad practice), so you have to add new user to run X.

* Edit default useradd settings
vi /etc/default/useradd
Modify '''SHELL''' variable:
SHELL=/bin/bash

* Add new user
useradd '''myuser'''

* Add the user to the sudo group
adduser '''myuser''' sudo

* Make home folder
mkdir /home/'''myuser'''
chown -R '''myuser''':'''myuser''' /home/'''myuser'''

* Install xfce4 and lightdm
apt-get update
apt-get install lightdm xfce4

* Modify lightdm configuration to enable autologin:
vi /etc/lightdm/lightdm.conf
autologin-user='''myuser'''
autologin-user-timeout=0
Make sure that the right lines are uncommented. If you don't want autologin just skip the step above.

* Reboot the system
reboot
After the system loads, you should see the default desktop of xfce4.

==== Ubuntu ====
----

You can download prebuild rootfs from [http://releases.linaro.org/ linaro] site or you can build it yourself.

===== Prebuild linaro images =====
----

You can download prebuild images from https://releases.linaro.org/.
In most cases the builds are separated in:
*'''nano'''
*'''developer'''
*'''server'''
*'''alip'''

You can read additional information from [https://wiki.linaro.org/Platform/DevPlatform/Rootfs here].

In this tutorial we will build Ubuntu 14.10 ALIP rootfs.

* Make empty image file:
dd if=/dev/zero of=linaro_alip_rootfs.img bs=1M count=1024

* Format the new image file:
mkfs.ext4 -F -L linuxroot linaro_alip_rootfs.img

* Create mount point:
mkdir mnt
mount -o loop linaro_alip_rootfs.img ./mnt

* Download prebuild image:
wget https://releases.linaro.org/14.10/ubuntu/trusty-images/alip/linaro-trusty-alip-20141024-684.tar.gz

* Make sure that the archive is downloaded:
md5sum linaro-trusty-alip-20141024-684.tar.gz

* Extract is into the mounted image file:
tar -zxvf linaro-trusty-alip-20141024-684.tar.gz
mv binary/* ./mnt

* Copy any modules that are generated with the kernel:
cp -rvf /'''path/to/modules'''/lib/modules ./mnt/lib/

* Chroot into the new rootfs:
cp /usr/bin/qemu-arm-static ./mnt/usr/bin
cp /etc/resolv.conf ./mnt/etc
chroot ./mnt

* Update repository
apt-get update
'''Note!''' If you have a problem with the update, try changing '''sources.list''' to:
deb http://old-releases.ubuntu.com/ubuntu/ raring main universe restricted multiverse
deb-src http://old-releases.ubuntu.com/ubuntu/ raring main universe restricted multiverse
deb http://old-releases.ubuntu.com/ubuntu/ raring-security main universe restricted multiverse
deb-src http://old-releases.ubuntu.com/ubuntu/ raring-security main universe restricted multiverse
deb http://old-releases.ubuntu.com/ubuntu/ raring-updates main universe restricted multiverse
deb-src http://old-releases.ubuntu.com/ubuntu/ raring-updates main universe restricted multiverse
deb http://old-releases.ubuntu.com/ubuntu/ raring-backports main restricted universe multiverse
deb-src http://old-releases.ubuntu.com/ubuntu/ raring-backports main restricted universe multiverse
deb http://old-releases.ubuntu.com/ubuntu/ raring-proposed main restricted universe multiverse
deb-src http://old-releases.ubuntu.com/ubuntu/ raring-proposed main restricted universe multiverse

* Install some useful packages:
apt-get install ssh nano wpasupplicant wireless-tools

* Set root password:
passwd

Linaro prebuild images comes with default use '''linaro'''.
* Set password for user:
passwd linaro

* Add '''linaro''' to sudo group:
adduser linaro sudo

* Configure network. Create new file for loopback, wlan and eth device:
vi /etc/network/interfaces.d/lo
Inside paste:
auto lo
iface lo inet loopback

Do the same for eth:
vi /etc/network/interfaces.d/eth
If you're using dhcp:
auto eth0
iface eth0 inet dhcp
Or for static ip:
auto eth0
iface eth0 inet static
address <your.ip.here>
netmask <your.netmask.here>
gateway <your.gateway.here>

And another for wireless devices:
vi /etc/network/interfaces.d/wlan
auto wlan0
iface lo inet dhcp
wpa-ssid <your.router.ssid>
wpa-pak <your.ssid.password>

'''Note!''' All connections are '''auto'''. If you don't want to use them all the time remove '''auto''' line.

You can do some additional work before exit.
When you are ready to exit from the target filesystem:
exit

Your rootfs is ready. The next step is to create image for nand or sdcard.

===== Manual build using debootstrap =====
----
The procedure is almost identical to the one used for the Debin image.

* First of all you need to install the support packages on your pc
sudo apt-get install qemu-user-static debootstrap binfmt-support ubuntu-archive-keyring

* We will build latest trusty Ubuntu image:
targetdir=ubuntu
distro=trusty

* Now we will build first stage of Ubuntu rootfs:
mkdir $targetdir
sudo debootstrap --arch=armhf --keyring=/usr/share/keyrings/ubuntu-archive-keyring.gpg --foreign $distro $targetdir

* Login into the new filesystem
sudo cp /usr/bin/qemu-arm-static $targetdir/usr/bin/
sudo cp /etc/resolv.conf $targetdir/etc
sudo chroot $targetdir

* Inside the chroot we need to set up the environment again
distro=trusty
export LANG=C

* Now we are setup the second stage of debootstrap needs to run install the packages downloaded earlier
/debootstrap/debootstrap --second-stage

* Configure apt-sources:
cat <<EOT > /etc/apt/sources.list
###### Ubuntu Main Repos
deb http://ports.ubuntu.com/ubuntu-ports/ $distro main restricted universe multiverse
deb-src http://ports.ubuntu.com/ubuntu-ports/ $distro main restricted universe multiverse
###### Ubuntu Update Repos
deb http://ports.ubuntu.com/ubuntu-ports/ $distro-security main restricted universe multiverse
deb http://ports.ubuntu.com/ubuntu-ports/ $distro-updates main restricted universe multiverse
deb-src http://ports.ubuntu.com/ubuntu-ports/ $distro-security main restricted universe multiverse
deb-src http://ports.ubuntu.com/ubuntu-ports/ $distro-updates main restricted universe multiverse
EOT

* Update Ubuntu package database:
apt-get update

* Set a root password so you can login
passwd

* Set the hostname
echo '''myhost'''> /etc/hostname
echo "127.0.0.1 '''myhost'''" >> /etc/hosts

* Build a basic network interface file so that the board will DHCP on eth0
echo <<EOT >> /etc/network/interfaces
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet dhcp
EOT

* Enable the serial console, Debian sysvinit way
echo T0:2345:respawn:/sbin/getty -L ttyFIQ0 115200 vt100 >> /etc/inittab

This way you'll get login prompt at startup. By default you cannot login as root. To do this you should make another user,
add him to the sudo group, login at startup and then login as root. To skip all this replace the line above with:
echo T0:2345:respawn:/sbin/getty -L ttyFIQ0 -a root 115200 vt100 >> /etc/inittab

* We are done inside the chroot, so quit the chroot shell
exit

* Tidy up the support files
sudo rm $targetdir/etc/resolv.conf
sudo rm $targetdir/usr/bin/qemu-arm-static

==== Make rootfs image ====
----

Once you are ready with the rootfs you can make image file. Later it can be used for NAND or SD image. Go to parent directory of you rootfs.

* See how big the image should be:
# du -khs <roofs_folder>
For example this will return 600MB. So we will make 1GB image.

* Make empty image:
# dd if=/dev/zero of=rootfs.img bs=1M count=1024

* Format the image:
# mkfs.ex4 -F -L linuxroot rootfs.img

* Mount the image:
# mount -o loop rootfs.img /mnt

* Copy rootfs files into the image:
# cp -prf <root_folder>/* /mnt/
''''Note!''' Use -p option to keep the permissions for the files and folders.

* Unmount the image:
# umount /mnt

=== Booting from NAND ===
----
* Get rk-tools:
git clone https://github.com/goodybag/rk-tools
cd rk-tools
make

*You will need the following files:
**bootloader --> This is RockChip RK3188Loader
**[[#Building parameter file|parameter]] --> Parameter file with crc encryption
**[[#Building kernel|boot]] --> Kernel with ramdisk compiled as shown here
**[[#Creating root filesystem|linux]] --> Rootfs image file
'''CMDLINE''' in parameter file should look something like this:
CMDLINE:console=ttyFIQ0,115200 console=tty0 root=/dev/block/mtd/by-name/linuxroot rw rootfstype=ext4 init=/sbin/init initrd=0x62000000,0x00800000 mtdparts=rk29xxnand:0x00008000@0x00002000(boot),-@0x0000A000(linuxroot)

* Copy all files in '''rk-tools''' folder

* Edit '''package-file'''. It should be:
#nano package-file

# NAME Relative path
#
#HWDEF HWDEF
package-file package-file
bootloader RK3188Loader
parameter parameter
boot boot.img
linuxroot rootfs.img
backup RESERVED
update-script update-script
recover-script recover-script

* Pack the image:
./afptool -pack . update_tmp.img

* Update the image:
./img_maker -rk31 RK3188Loader 1 0 0 update_tmp.img update.img

The image should be ready. What's left is flashing the image.

*Important: to flash the image the board needs to be in bootloader mode. To enter bootloader mode you need to press and hold down the recovery button before connecting the board to the PC. After the connection is established you can release the button.

 

=== Booting from SD-card ===
----
You'll need at least 512MB sd-card. Depending on rootfs needed size can grow to 4GB.

*You will need the following files:
**sdboot_rk3188.img --> RK3188Loader for booting from SDcard
**[[#Building parameter file|parameter]] --> Parameter file with crc encryption
**[[#Building kernel|boot]] --> Kernel with ramdisk compiled as shown here
**[[#Creating root filesystem|linux]] --> Rootfs image file

'''CMDLINE''' in parameter file should look something like this:
CMDLINE:console=ttyFIQ0,115200 console=tty0 root=/dev/mmcblk0p1 rw rootfstype=ext4 init=/sbin/init initrd=0x62000000,0x00800000 mtdparts=rk29xxnand:0x00008000@0x00002000(boot),-@0x0000A000(linuxroot)

Insert sd-card. Lets say that your device is '''/dev/sdc'''.

* Write Rockchip loader:
dd if=sdboot_rk3188.img of=/dev/sdc conv=sync,fsync

* Write parameter file:
dd if=parameter.img of=/dev/sdc conv=sync,fsync seek=$((0x2000))

* Write kernel:
dd if=boot.img of=/dev/sdc conv=sync,fsync seek=$((0x2000+0x2000))

* Write rootfs:
dd if=rootfs.img of=/dev/sdc conv=sync,fsync seek=$((0x2000+0xA000))

You can do this also on image file:
dd if=/dev/zero of=sd.img bs=1M count=1024
If 1GB is not enough increase count number.

* Write Rockchip loader:
dd if=sdboot_rk3188.img of=sd.img conv=sync,fsync

* Write parameter file:
dd if=parameter.img of=sd.img conv=sync,fsync seek=$((0x2000))

* Write kernel:
dd if=boot.img of=sd.img conv=sync,fsync seek=$((0x2000+0x2000))

* Write rootfs:
dd if=rootfs.img of=sd.img conv=sync,fsync seek=$((0x2000+0xA000))

* Format image:
fdisk sd.img << EOF
n
p
1
49152

w
EOF

=== Calibrate touchscreen ===
If you want to use LCD panel with touchscreen, you should perform a screen calibration.

==== Calibrate using tslib ====
----

* Install the required packages:
apt-get update
apt-get install xorg-dev xserver-xorg-dev x11proto-core-dev git automake make libtool

* Download tslib:
git clone https://github.com/kergoth/tslib.git
cd tslib

* Download patch:
cd plugin
wget https://dl.dropbox.com/u/40057/patches/input-raw.c
cd ../

* Compile the library:
autoreconf -vi
./configure --prefix=/usr
make
make install
ldconfig

* Modify tslib configuration
vi /usr/etc/ts.conf
Uncomment the following line:
module_raw input

* Export tslib needed variables:
export TSLIB_TSEVENTTYPE=raw
export TSLIB_CONSOLEDEVICE=none
export TSLIB_FBDEVICE=/dev/fb0
export TSLIB_TSDEVICE=/dev/input/event0
export TSLIB_CALIBFILE=/usr/etc/pointercal
export TSLIB_CONFFILE=/usr/etc/ts.conf
export TSLIB_PLUGINDIR=/usr/lib/ts

* Now tslib is working but still it should be set as default driver in the X:
wget http://ftp.de.debian.org/debian/pool/main/x/xf86-input-tslib/xf86-input-tslib_0.0.6.orig.tar.gz
tar zxfv xf86-input-tslib_0.0.6.orig.tar.gz
cd xf86-input-tslib-0.0.6/
Replace tslib.c file with patched one:
cd src/
rm -f tslib.c
wget https://dl.dropbox.com/u/40057/patches/tslib.c
cd ..
Build and install package:
./configure --prefix=/usr
make
make install

* Add tslib configuration:
cd /usr/share/X11/xorg.conf.d/
Make new file:
nano 20-touchscreen.conf
Add the following text inside:
Section "InputClass"
Identifier "AR1020"
MatchDevicePath "/dev/input/event0"
Driver "tslib"
Option "Device" "/dev/input/event0"
Option "ScreenNumber" "0"
Option "Rotate" "NONE"
Option "Width" "'''800'''"
Option "Height" "'''480'''"
Option "SendCoreEvents" "yes"
Option "Type" "touchscreen"
EndSection
Note! Resolution in this example is set for 7 inch LCD.

* Do the actual calibration:
service lightdm stop
ts_calibrate
service lightdm start
After lightdm start you could check if everything is running smoothly.

* Save tslib variables:
vi /etc/environment
Paste the following:
TSLIB_TSEVENTTYPE=raw
TSLIB_CONSOLEDEVICE=none
TSLIB_FBDEVICE=/dev/fb0
TSLIB_TSDEVICE=/dev/input/event0
TSLIB_CALIBFILE=/etc/pointercal
TSLIB_CONFFILE=/usr/etc/ts.conf
TSLIB_PLUGINDIR=/usr/lib/ts

If you change the LCD panel run ts_calibrate to configure touchscreen for the new LCD.

==== Calibrate using AR1021 driver ====
TODO

=== Enabling wireless modules ===
==== RTL8188CUS ====
----
[[File:MOD-WIFI-RTL8188-1.jpg|thumb|[https://www.olimex.com/Products/USB-Modules/MOD-WIFI-RTL8188/ MOD-WIFI-RTL8188]]]
To connect OLinuXino board with wireless, you could use [https://www.olimex.com/Products/USB-Modules/MOD-WIFI-RTL8188/ MOD-WIFI-RTL8188] dongle. Also you can use another one with the same chip.

[https://www.olimex.com/Products/USB-Modules/MOD-WIFI-RTL8188/ MOD-WIFI-RTL8188] has the following features:
* Has WM-294 module with RTL8188
* Operates in 2.4 GHz frequency bands
* 1x1 MIMO technology improves effective throughput and range over existing 802.11 b/g products
* Data rates: up to 150Mbps
* 802.11e-compatible bursting and I standards BPSK, QPSK, 16 QAM, 64 QAM modulation schemes WEP, TKIP, and AES, WPA, WPA2 hardware encryption schemes
* Standard USB type A connector
* On-board antenna
* 5V/3.3V operation modes via SMD jumper
* 4 test pads for easy tracking the supply, d-, d+, and GND
* PCB: FR-4, 1.00 mm (0,039"), solder mask, silkscreen component print
* Dimensions: 65.15x20.38 mm (2.56x0.80")
----

The kernel module is prebuild. You should just get it loaded and then plug the dongle.
* Load the module:
modprobe 8192cu

* Plug the device and check if it is available:
ifconfig -a

==== RT5370 ====
----
[[File:MOD-WIFI-R5370-ANT-1.jpg|border|thumb|[https://www.olimex.com/Products/USB-Modules/MOD-WIFI-R5370-ANT/ MOD-WIFI-R5370-ANT]]]

To use one this wifi dongle (like [https://www.olimex.com/Products/USB-Modules/MOD-WIFI-R5370/ MOD-WIFI-R5370] or [https://www.olimex.com/Products/USB-Modules/MOD-WIFI-R5370-ANT/ MOD-WIFI-R5370-ANT]) additional files are required.

[https://www.olimex.com/Products/USB-Modules/MOD-WIFI-R5370-ANT/ MOD-WIFI-R5370-ANT] has the following features:

* 2.4GHz with 150Mbps PHY data rate
*External antenna for extended range
*USB 2.0 interface
*Security: WEP/TKIP/AES/WPA/WPA2/WAPI
*CMOS single chip with RF, baseband, and MAC integration
*QoS: WMM & WMM-PS support
*Multiple BSSID support
*Maximum likelihood decoding support
*Cisco CCX 5.0 support
*Low-power usage with advanced power management
----

*First a make new directory and navigate to it. This is where the module will search for files.
mkdir -p /etc/Wireless/RT2870STA
cd /etc/Wireless/RT2870STA/

*Download the files from Github
wget https://raw.githubusercontent.com/SelfDestroyer/RK3188-SOM/olimex/stable-3.0/drivers/net/wireless/rtxx7x/RT2870STA.dat
wget https://raw.githubusercontent.com/SelfDestroyer/RK3188-SOM/olimex/stable-3.0/drivers/net/wireless/rtxx7x/RT2870STACard.dat

*Load module
modprobe rt5370sta

*Plug the device and run:
ifconfig -a
*You should see this:
wlan0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

*Configure your new device:
vi /etc/network/interfaces
*Add configuration. Here we will show DHCP configuration.
iface wlan0 inet dhcp
wpa-ssid "'''your ssid'''"
wpa-psk "'''your password'''"

*Save the configuration and up the interface:
ifup wlan0

*If everything is working and this module to be loaded on boot:
echo rt5370sta >> /etc/modules

== Android ==

RK3188-SOM

2024-05-15T11:51:34Z

LubOlimex: /* How to download the ready Debian image to the NAND memory of RK3188-SOM? */

== Overview ==

[[File:Rk3188-som-resized.png|650px]]

RK3188-SOM board is a very productive small beast compared to the previous Olimex board designs. If we compare RockChip RK3188 and Allwinner A20: RK3188 has 4x Cortex-A9, while A20 only 2x Cortex-A7. It runs at 1.6 GHz vs. the 1.0 GHz frequency of the A20. RK3188 reaches a total of 16000 DMPIS vs. the 3800 DMIPS for the A20 (RK3188 is 4.2 times faster). For comparison, the RaspberryPi has 965 DMIPS (RK3188 is 16.6 times faster).

The RK3188-SOM design has the following features:

*Rockchip RK3188 quad core Cortex-A9 processor, each core typically running at 1.6GHz
*1GB DDR3 memory
*Integrated power management unit
*Optional 4GB NAND flash memory for Linux or Android boot
*Micro SD-card for Linux or Android boot
*Three buttons - POWER, RESET, RECOVERY
*Four LEDs (one for power and three user-programmable)
*UART console pins exposed for serial debug
*Five GPIO connectors 2×20 pins @ 0.05" step
*Dimensions: (3.2×1.8)" ~ (81×56)mm
 

== Ready-to-use Debian images ==
=== Debian for microSD card ===

'''Newest official release (recommended):'''

Direct download of Debian release #2:[https://ftp.olimex.com/RK3188_Images/RK3188_debian_3.0.36_SD_release2.img RK3188-SOM Debian for microSD card - kernel 3.0.36+ - release #2]

In the command line interface of image you are automatically logged as root. The default superuser username/password combination in the GUI (XFCE4) is: olimex/olimex.

Build instructions and links to required files for the latest Debian images might be found below in chapter "Building Linux for RK3188-SOM".

====How to prepare your microSD card with the suitable official Debian image?====
----
In order to download an official Linux image to a microSD card under Windows you can use Win32 Disk Imager: [http://sourceforge.net/projects/win32diskimager/ click here]

1. Download the latest official image suitable for a microSD card from the chapter above

2. Download Win32 Disk Imager from this link.

3. Insert card in your microSD card reader.

4. Launch the software.

5. Point the software to the image

6. Click "write"

Under Linux you can write the image image to the card with dd utility. This is how it can be done:

Let's say the name of the image is "debian_2g.img". It would be downloaded to the microSD card connected to a Linux machine using one of the following commands:

dd bs=4M oflag=sync if=debian_2g.img of=/dev/sdX

or

cp debian_2g.img /dev/sdX

where /dev/sdX is the uSD card as listed by the Linux.

=== Debian for NAND memory ===

'''Newest official release (recommended):'''

Direct download Debian for NAND release #1: [https://ftp.olimex.com/RK3188_Images/RK3188_debian_3.0.36_NAND_release1.img|RK3188-SOM Debian for NAND memory - kernel 3.0.36+ - release #1]

Note that this image is suitable only for RK3188-SOM-4GB boards.

Build instructions and links to required files for the latest Debian images might be found below in chapter "Building Linux for RK3188-SOM"

====How to download the ready Debian image to the NAND memory of RK3188-SOM?====
----

'''IMPORTANT: RK3188-SOM-4GB comes with Debian already pre-loaded on the NAND memory. No need to perform this operation initially.'''

1. You need to download the software tools for your computer provided by Rockchip. If you use Windows download “Rockchip Batch Tool”. If you use Linux use either rkflashkit or upgrade_tool. These are the tools that I recommend but there are a lot of tools available. Get the Rockchip batch tool from here: [https://drive.google.com/file/d/0BwplT87k9SCgRDB4ZGY3SnMzd00/view?usp=sharing Rockchip Batch Tool]

For Windows:

2. Install the drivers that allows your computer to recognize the board (that is already set in bootloader mode) connected to it. The installer is called "Rockchip Driver Assistant" – download it here: [https://drive.google.com/file/d/0BwplT87k9SCgbkdXX1ByUW1RSW8/view?usp=sharing Rockchip Driver Assistant]

3. You need to download and extract the latest image suitable for the NAND from our wiki. It is available as a direct download here: [https://ftp.olimex.com/RK3188_Images/RK3188_debian_3.0.36_NAND_release1.img|RK3188 Debian 3.0.36 for NAND memory]

4. You need enter bootloader mode with the board to be able to establish connection between the board and the software provided by Rockchip. You would also need a mini USB cable. To enter bootloader mode you need to press and hold down the recovery button before powering the board (then connect the board to the PC via the mini USB cable). After the board is powered you can release the button.

5. Start the tool for uploading the firmware and point it to the extracted image.

6. Click button "Upgrade".

7. Test with a serial cable.

== Ready-to-use Android images ==
TODO

== Documents ==

[https://www.olimex.com/Products/SOM/RK3188/RK3188-SOM/resources/RK3188-SOM-UM.pdf OLIMEX RK3188-SOM user's manual]

[https://www.olimex.com/Products/SOM/RK3188/RK3188-SOM-EVB/resources/RK3188-SOM-EVB-UM.pdf OLIMEX RK3188-SOM-EVB user's manual]

[https://github.com/OLIMEX/OLINUXINO/raw/master/HARDWARE/RK3188-PDFs/Rockchip%20RK3188%20datasheet%20V1.0.pdf Processor (Rockchip RK3188) datasheet in pdf format]

[https://www.olimex.com/Products/SOM/RK3188/RK3188-SOM/resources/RK3188_SOM_GPIOs.pdf RK3188-SOM connectors' pinout and GPIO table]

=== CAD files ===

RK3188-SOM is considered commercial, proprietary design. The board file is not available to the customer. A pdf extracted from the original schematic is available at GitHub: [https://github.com/OLIMEX/SOM/tree/master/RK3188/RK3188-SOM RK3188-SOM schematics]

RK3188-SOM-EVB is considered Open Source Hardware, Eagle CAD files are available also at GitHub: [https://github.com/OLIMEX/SOM/tree/master/RK3188/RK3188-EVB RK3188-SOM-EVB sources]

The CAD product used to design OLinuXino is Eagle and you can download evaluation free version from their [http://www.cadsoftusa.com/ web site]. The evaluation version allows you to inspect the schematic and the board file sources.

==Board Layout==

[[File:Rk3188-som-resized-TOP-NAMED.png|650px]]

[[File:Rk3188-som-resized-BOTTOM-NAMED.png|650px]]

== Building Linux for RK3188-SOM ==
=== Building the parameter file ===
----
The parameter file describes many board parameters as firmware version, machine id, manufacturer name, etc.

For the user the most important parameter is '''CMDLINE'''. This is the command that is passed to the kernel. It looks something like this:
CMDLINE:console=ttyFIQ0,115200 console=tty0 root=/dev/mmcblk0p1 rw rootfstype=ext4 init=/sbin/init initrd=0x62000000,0x00800000 \
mtdparts=rk29xxnand:0x00008000@0x00002000(boot),-@0x0000A000(linuxroot)

Define serial port at 115200:
console=ttyFIQ0,115200

Define location of the rootfs:
root=/dev/mmcblk0p1

Define rootfs file system as ext4:
rootfstype=ext4

Define the address of the kernel and size:
0x00008000@0x00002000

Define start address of the rootfs:
-@0x0000A000

Additionally, you can set static MAC address with:
mac_addr=xx:xx:xx:xx:xx:xx

Once you're ready with the file, make the parameter image

* Get rkutils:
https://github.com/naobsd/rkutils
cd rkutils
gcc rkcrc.c -o rkcrc
If you're getting error try to comment ''''#include <err.h>'''' in ''''rkcrc.c''''

* Encrypt parameter file:
./rkcrc -p you_parameter_file parameter

The parameter file is ready for further use.

=== Building the kernel ===
----
* Fist prepare the toolchain:
apt-get update
apt-get install gcc-4.7-arm-linux-gnueabihf ncurses-dev uboot-mkimage build-essential git

* Get the sources:
git clone -b olimex/stable-3.0 https://github.com/StefanMavrodiev/RK3188-SOM.git

* Get the default configuration:
cd RK3188-SOM/
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- '''olimex_rk3188_defconfig'''

* You can modify defconfig with (for additional modules):
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- menuconfig

'''Note!''' The default config will set hdmi to 1080p. You can change it from:
Device Drivers --->
Graphics support --->
<*> Frame buffer support for Rockchip --->
LCD Panel Select --->
'''''Choose one of the following:'''''
HDMI framebuffer size and timing is 1080p <--- '''Set HDMI to 1080p'''
HDMI framebuffer size and timing is 720p <--- '''Set HDMI to 720p'''
HDMI framebuffer size and timing is 480p <--- '''Set HDMI to 480p'''
RGB AT070TN90 <--- [https://www.olimex.com/Products/OLinuXino/LCD/LCD-OLinuXino-7/open-source-hardware LCD-OLinuXino-7]
RGB AR010H05N <--- [https://www.olimex.com/Products/OLinuXino/LCD/LCD-OLinuXino-10/open-source-hardware LCD-OLinuXino-10]
RGB BT043DCNNHHP <--- [https://www.olimex.com/Products/OLinuXino/LCD/LCD-OLinuXino-4.3TS/open-source-hardware LCD-OLinuXino-4.3TS]

* Build the kernel:
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- -j4 kernel.img
After the build is finish you will have '''RK3188-SOM/kernel.img''' and '''RK3188-SOM/arch/arm/boot/Image'''. The first one can be uploaded to the kernel partition (if you have one). The second file is raw binary. It can be combined with ramdisk to get boot.img.

* Generate ramdisk
cd ../
git clone https://github.com/radxa/initrd.git
cd initrd/
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- -j4
cd ../

* Make mkbootimg
git clone https://github.com/neo-technologies/rockchip-mkbootimg.git
cd rockchip-mkbootimg
make
make install
cd ../

* Make boot.img
mkbootimg --kernel RK3188-SOM/arch/arm/boot/Image --ramdisk initrd.img -o boot.img

=== Creating the root filesystem ===
==== Debian Wheezy ====
----
In this post we will explain how you can create your own Debian rootfs with pre-installed packages of your choice, which to allow tiny Linux images to be created. All steps below should work on any Debian host (Debian/Ubuntu etc) and are verified with Ubuntu 12.04LTS. First of all you need to install the support packages on your pc:

* Install the needed packages:
sudo apt-get install qemu-user-static debootstrap binfmt-support

* Define some variables:
targetdir=rootfs
distro=wheezy

* Build first stage:
mkdir $targetdir
sudo debootstrap --arch=armhf --foreign $distro $targetdir

* Copy needed files from host to the target:
sudo cp /usr/bin/qemu-arm-static $targetdir/usr/bin/
sudo cp /etc/resolv.conf $targetdir/etc

We should now have a minimal Debian Rootfs.
* Login into the new filesystem:
sudo chroot $targetdir

* Inside the chroot we need to set up the environment again:
distro=wheezy
export LANG=C

* Now we would run the setup for the second stage of debootstrap needs to run install the packages downloaded earlier
/debootstrap/debootstrap --second-stage

* Once the package installation has finished, setup some support files and apt configuration.
cat <<EOT > /etc/apt/sources.list
deb http://ftp.uk.debian.org/debian $distro main contrib non-free
deb-src http://ftp.uk.debian.org/debian $distro main contrib non-free
deb http://ftp.uk.debian.org/debian $distro-updates main contrib non-free
deb-src http://ftp.uk.debian.org/debian $distro-updates main contrib non-free<
deb http://security.debian.org/debian-security $distro/updates main contrib non-free
deb-src http://security.debian.org/debian-security $distro/updates main contrib non-free

EOT

* Update Debian package database:
apt-get update

* Set up locales dpkg scripts since it tends to complain otherwise; note in Debian Jessie you will also need to install the dialog package as well:
apt-get install locales dialog sudo
dpkg-reconfigure locales

* Fix permission for sudo:
chmod u+s /usr/bin/sudo

* Fix ownership of man forlder
chown -R man /var/cache/man

* Install some useful packages inside the chroot:
apt-get install openssh-server ntpdate

* Set a root password so you can login:
passwd

* Build a basic network interface file:
vi /etc/network/interfaces
Add the following to get static ip:
allow-hotplug eth0
iface eth0 inet static
address 192.168.1.254
netmask 255.255.255.248
gateway 192.168.1.1
Or if you want dhcp
allow-hotplug eth0
iface eth0 inet dhcp

Note: Your board will be accessible over SSH on IP address defined above!

* Set the hostname
echo '''myhost'''> /etc/hostname
echo "127.0.0.1 '''myhost'''" >> /etc/hosts

* Enable the serial console, Debian sysvinit way
echo T0:2345:respawn:/sbin/getty -L ttyFIQ0 115200 vt100 >> /etc/inittab

This way you'll get login prompt at startup. By default you cannot login as root. To do this you should make another user, add him to the sudo group, login at startup and then login as root. To skip all this replace the line above with:
echo T0:2345:respawn:/sbin/getty -L ttyFIQ0 -a root 115200 vt100 >> /etc/inittab

* We are done inside the chroot, so quit the chroot shell
exit

* Tidy up the support files
sudo rm $targetdir/etc/resolv.conf
sudo rm $targetdir/usr/bin/qemu-arm-static

===== Installing X =====
----
You cannot run X as root (actually it's possible, but it's a bad practice), so you have to add new user to run X.

* Edit default useradd settings
vi /etc/default/useradd
Modify '''SHELL''' variable:
SHELL=/bin/bash

* Add new user
useradd '''myuser'''

* Add the user to the sudo group
adduser '''myuser''' sudo

* Make home folder
mkdir /home/'''myuser'''
chown -R '''myuser''':'''myuser''' /home/'''myuser'''

* Install xfce4 and lightdm
apt-get update
apt-get install lightdm xfce4

* Modify lightdm configuration to enable autologin:
vi /etc/lightdm/lightdm.conf
autologin-user='''myuser'''
autologin-user-timeout=0
Make sure that the right lines are uncommented. If you don't want autologin just skip the step above.

* Reboot the system
reboot
After the system loads, you should see the default desktop of xfce4.

==== Ubuntu ====
----

You can download prebuild rootfs from [http://releases.linaro.org/ linaro] site or you can build it yourself.

===== Prebuild linaro images =====
----

You can download prebuild images from https://releases.linaro.org/.
In most cases the builds are separated in:
*'''nano'''
*'''developer'''
*'''server'''
*'''alip'''

You can read additional information from [https://wiki.linaro.org/Platform/DevPlatform/Rootfs here].

In this tutorial we will build Ubuntu 14.10 ALIP rootfs.

* Make empty image file:
dd if=/dev/zero of=linaro_alip_rootfs.img bs=1M count=1024

* Format the new image file:
mkfs.ext4 -F -L linuxroot linaro_alip_rootfs.img

* Create mount point:
mkdir mnt
mount -o loop linaro_alip_rootfs.img ./mnt

* Download prebuild image:
wget https://releases.linaro.org/14.10/ubuntu/trusty-images/alip/linaro-trusty-alip-20141024-684.tar.gz

* Make sure that the archive is downloaded:
md5sum linaro-trusty-alip-20141024-684.tar.gz

* Extract is into the mounted image file:
tar -zxvf linaro-trusty-alip-20141024-684.tar.gz
mv binary/* ./mnt

* Copy any modules that are generated with the kernel:
cp -rvf /'''path/to/modules'''/lib/modules ./mnt/lib/

* Chroot into the new rootfs:
cp /usr/bin/qemu-arm-static ./mnt/usr/bin
cp /etc/resolv.conf ./mnt/etc
chroot ./mnt

* Update repository
apt-get update
'''Note!''' If you have a problem with the update, try changing '''sources.list''' to:
deb http://old-releases.ubuntu.com/ubuntu/ raring main universe restricted multiverse
deb-src http://old-releases.ubuntu.com/ubuntu/ raring main universe restricted multiverse
deb http://old-releases.ubuntu.com/ubuntu/ raring-security main universe restricted multiverse
deb-src http://old-releases.ubuntu.com/ubuntu/ raring-security main universe restricted multiverse
deb http://old-releases.ubuntu.com/ubuntu/ raring-updates main universe restricted multiverse
deb-src http://old-releases.ubuntu.com/ubuntu/ raring-updates main universe restricted multiverse
deb http://old-releases.ubuntu.com/ubuntu/ raring-backports main restricted universe multiverse
deb-src http://old-releases.ubuntu.com/ubuntu/ raring-backports main restricted universe multiverse
deb http://old-releases.ubuntu.com/ubuntu/ raring-proposed main restricted universe multiverse
deb-src http://old-releases.ubuntu.com/ubuntu/ raring-proposed main restricted universe multiverse

* Install some useful packages:
apt-get install ssh nano wpasupplicant wireless-tools

* Set root password:
passwd

Linaro prebuild images comes with default use '''linaro'''.
* Set password for user:
passwd linaro

* Add '''linaro''' to sudo group:
adduser linaro sudo

* Configure network. Create new file for loopback, wlan and eth device:
vi /etc/network/interfaces.d/lo
Inside paste:
auto lo
iface lo inet loopback

Do the same for eth:
vi /etc/network/interfaces.d/eth
If you're using dhcp:
auto eth0
iface eth0 inet dhcp
Or for static ip:
auto eth0
iface eth0 inet static
address <your.ip.here>
netmask <your.netmask.here>
gateway <your.gateway.here>

And another for wireless devices:
vi /etc/network/interfaces.d/wlan
auto wlan0
iface lo inet dhcp
wpa-ssid <your.router.ssid>
wpa-pak <your.ssid.password>

'''Note!''' All connections are '''auto'''. If you don't want to use them all the time remove '''auto''' line.

You can do some additional work before exit.
When you are ready to exit from the target filesystem:
exit

Your rootfs is ready. The next step is to create image for nand or sdcard.

===== Manual build using debootstrap =====
----
The procedure is almost identical to the one used for the Debin image.

* First of all you need to install the support packages on your pc
sudo apt-get install qemu-user-static debootstrap binfmt-support ubuntu-archive-keyring

* We will build latest trusty Ubuntu image:
targetdir=ubuntu
distro=trusty

* Now we will build first stage of Ubuntu rootfs:
mkdir $targetdir
sudo debootstrap --arch=armhf --keyring=/usr/share/keyrings/ubuntu-archive-keyring.gpg --foreign $distro $targetdir

* Login into the new filesystem
sudo cp /usr/bin/qemu-arm-static $targetdir/usr/bin/
sudo cp /etc/resolv.conf $targetdir/etc
sudo chroot $targetdir

* Inside the chroot we need to set up the environment again
distro=trusty
export LANG=C

* Now we are setup the second stage of debootstrap needs to run install the packages downloaded earlier
/debootstrap/debootstrap --second-stage

* Configure apt-sources:
cat <<EOT > /etc/apt/sources.list
###### Ubuntu Main Repos
deb http://ports.ubuntu.com/ubuntu-ports/ $distro main restricted universe multiverse
deb-src http://ports.ubuntu.com/ubuntu-ports/ $distro main restricted universe multiverse
###### Ubuntu Update Repos
deb http://ports.ubuntu.com/ubuntu-ports/ $distro-security main restricted universe multiverse
deb http://ports.ubuntu.com/ubuntu-ports/ $distro-updates main restricted universe multiverse
deb-src http://ports.ubuntu.com/ubuntu-ports/ $distro-security main restricted universe multiverse
deb-src http://ports.ubuntu.com/ubuntu-ports/ $distro-updates main restricted universe multiverse
EOT

* Update Ubuntu package database:
apt-get update

* Set a root password so you can login
passwd

* Set the hostname
echo '''myhost'''> /etc/hostname
echo "127.0.0.1 '''myhost'''" >> /etc/hosts

* Build a basic network interface file so that the board will DHCP on eth0
echo <<EOT >> /etc/network/interfaces
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet dhcp
EOT

* Enable the serial console, Debian sysvinit way
echo T0:2345:respawn:/sbin/getty -L ttyFIQ0 115200 vt100 >> /etc/inittab

This way you'll get login prompt at startup. By default you cannot login as root. To do this you should make another user,
add him to the sudo group, login at startup and then login as root. To skip all this replace the line above with:
echo T0:2345:respawn:/sbin/getty -L ttyFIQ0 -a root 115200 vt100 >> /etc/inittab

* We are done inside the chroot, so quit the chroot shell
exit

* Tidy up the support files
sudo rm $targetdir/etc/resolv.conf
sudo rm $targetdir/usr/bin/qemu-arm-static

==== Make rootfs image ====
----

Once you are ready with the rootfs you can make image file. Later it can be used for NAND or SD image. Go to parent directory of you rootfs.

* See how big the image should be:
# du -khs <roofs_folder>
For example this will return 600MB. So we will make 1GB image.

* Make empty image:
# dd if=/dev/zero of=rootfs.img bs=1M count=1024

* Format the image:
# mkfs.ex4 -F -L linuxroot rootfs.img

* Mount the image:
# mount -o loop rootfs.img /mnt

* Copy rootfs files into the image:
# cp -prf <root_folder>/* /mnt/
''''Note!''' Use -p option to keep the permissions for the files and folders.

* Unmount the image:
# umount /mnt

=== Booting from NAND ===
----
* Get rk-tools:
git clone https://github.com/goodybag/rk-tools
cd rk-tools
make

*You will need the following files:
**bootloader --> This is RockChip RK3188Loader
**[[#Building parameter file|parameter]] --> Parameter file with crc encryption
**[[#Building kernel|boot]] --> Kernel with ramdisk compiled as shown here
**[[#Creating root filesystem|linux]] --> Rootfs image file
'''CMDLINE''' in parameter file should look something like this:
CMDLINE:console=ttyFIQ0,115200 console=tty0 root=/dev/block/mtd/by-name/linuxroot rw rootfstype=ext4 init=/sbin/init initrd=0x62000000,0x00800000 mtdparts=rk29xxnand:0x00008000@0x00002000(boot),-@0x0000A000(linuxroot)

* Copy all files in '''rk-tools''' folder

* Edit '''package-file'''. It should be:
#nano package-file

# NAME Relative path
#
#HWDEF HWDEF
package-file package-file
bootloader RK3188Loader
parameter parameter
boot boot.img
linuxroot rootfs.img
backup RESERVED
update-script update-script
recover-script recover-script

* Pack the image:
./afptool -pack . update_tmp.img

* Update the image:
./img_maker -rk31 RK3188Loader 1 0 0 update_tmp.img update.img

The image should be ready. What's left is flashing the image.

*Important: to flash the image the board needs to be in bootloader mode. To enter bootloader mode you need to press and hold down the recovery button before connecting the board to the PC. After the connection is established you can release the button.

 

=== Booting from SD-card ===
----
You'll need at least 512MB sd-card. Depending on rootfs needed size can grow to 4GB.

*You will need the following files:
**sdboot_rk3188.img --> RK3188Loader for booting from SDcard
**[[#Building parameter file|parameter]] --> Parameter file with crc encryption
**[[#Building kernel|boot]] --> Kernel with ramdisk compiled as shown here
**[[#Creating root filesystem|linux]] --> Rootfs image file

'''CMDLINE''' in parameter file should look something like this:
CMDLINE:console=ttyFIQ0,115200 console=tty0 root=/dev/mmcblk0p1 rw rootfstype=ext4 init=/sbin/init initrd=0x62000000,0x00800000 mtdparts=rk29xxnand:0x00008000@0x00002000(boot),-@0x0000A000(linuxroot)

Insert sd-card. Lets say that your device is '''/dev/sdc'''.

* Write Rockchip loader:
dd if=sdboot_rk3188.img of=/dev/sdc conv=sync,fsync

* Write parameter file:
dd if=parameter.img of=/dev/sdc conv=sync,fsync seek=$((0x2000))

* Write kernel:
dd if=boot.img of=/dev/sdc conv=sync,fsync seek=$((0x2000+0x2000))

* Write rootfs:
dd if=rootfs.img of=/dev/sdc conv=sync,fsync seek=$((0x2000+0xA000))

You can do this also on image file:
dd if=/dev/zero of=sd.img bs=1M count=1024
If 1GB is not enough increase count number.

* Write Rockchip loader:
dd if=sdboot_rk3188.img of=sd.img conv=sync,fsync

* Write parameter file:
dd if=parameter.img of=sd.img conv=sync,fsync seek=$((0x2000))

* Write kernel:
dd if=boot.img of=sd.img conv=sync,fsync seek=$((0x2000+0x2000))

* Write rootfs:
dd if=rootfs.img of=sd.img conv=sync,fsync seek=$((0x2000+0xA000))

* Format image:
fdisk sd.img << EOF
n
p
1
49152

w
EOF

=== Calibrate touchscreen ===
If you want to use LCD panel with touchscreen, you should perform a screen calibration.

==== Calibrate using tslib ====
----

* Install the required packages:
apt-get update
apt-get install xorg-dev xserver-xorg-dev x11proto-core-dev git automake make libtool

* Download tslib:
git clone https://github.com/kergoth/tslib.git
cd tslib

* Download patch:
cd plugin
wget https://dl.dropbox.com/u/40057/patches/input-raw.c
cd ../

* Compile the library:
autoreconf -vi
./configure --prefix=/usr
make
make install
ldconfig

* Modify tslib configuration
vi /usr/etc/ts.conf
Uncomment the following line:
module_raw input

* Export tslib needed variables:
export TSLIB_TSEVENTTYPE=raw
export TSLIB_CONSOLEDEVICE=none
export TSLIB_FBDEVICE=/dev/fb0
export TSLIB_TSDEVICE=/dev/input/event0
export TSLIB_CALIBFILE=/usr/etc/pointercal
export TSLIB_CONFFILE=/usr/etc/ts.conf
export TSLIB_PLUGINDIR=/usr/lib/ts

* Now tslib is working but still it should be set as default driver in the X:
wget http://ftp.de.debian.org/debian/pool/main/x/xf86-input-tslib/xf86-input-tslib_0.0.6.orig.tar.gz
tar zxfv xf86-input-tslib_0.0.6.orig.tar.gz
cd xf86-input-tslib-0.0.6/
Replace tslib.c file with patched one:
cd src/
rm -f tslib.c
wget https://dl.dropbox.com/u/40057/patches/tslib.c
cd ..
Build and install package:
./configure --prefix=/usr
make
make install

* Add tslib configuration:
cd /usr/share/X11/xorg.conf.d/
Make new file:
nano 20-touchscreen.conf
Add the following text inside:
Section "InputClass"
Identifier "AR1020"
MatchDevicePath "/dev/input/event0"
Driver "tslib"
Option "Device" "/dev/input/event0"
Option "ScreenNumber" "0"
Option "Rotate" "NONE"
Option "Width" "'''800'''"
Option "Height" "'''480'''"
Option "SendCoreEvents" "yes"
Option "Type" "touchscreen"
EndSection
Note! Resolution in this example is set for 7 inch LCD.

* Do the actual calibration:
service lightdm stop
ts_calibrate
service lightdm start
After lightdm start you could check if everything is running smoothly.

* Save tslib variables:
vi /etc/environment
Paste the following:
TSLIB_TSEVENTTYPE=raw
TSLIB_CONSOLEDEVICE=none
TSLIB_FBDEVICE=/dev/fb0
TSLIB_TSDEVICE=/dev/input/event0
TSLIB_CALIBFILE=/etc/pointercal
TSLIB_CONFFILE=/usr/etc/ts.conf
TSLIB_PLUGINDIR=/usr/lib/ts

If you change the LCD panel run ts_calibrate to configure touchscreen for the new LCD.

==== Calibrate using AR1021 driver ====
TODO

=== Enabling wireless modules ===
==== RTL8188CUS ====
----
[[File:MOD-WIFI-RTL8188-1.jpg|thumb|[https://www.olimex.com/Products/USB-Modules/MOD-WIFI-RTL8188/ MOD-WIFI-RTL8188]]]
To connect OLinuXino board with wireless, you could use [https://www.olimex.com/Products/USB-Modules/MOD-WIFI-RTL8188/ MOD-WIFI-RTL8188] dongle. Also you can use another one with the same chip.

[https://www.olimex.com/Products/USB-Modules/MOD-WIFI-RTL8188/ MOD-WIFI-RTL8188] has the following features:
* Has WM-294 module with RTL8188
* Operates in 2.4 GHz frequency bands
* 1x1 MIMO technology improves effective throughput and range over existing 802.11 b/g products
* Data rates: up to 150Mbps
* 802.11e-compatible bursting and I standards BPSK, QPSK, 16 QAM, 64 QAM modulation schemes WEP, TKIP, and AES, WPA, WPA2 hardware encryption schemes
* Standard USB type A connector
* On-board antenna
* 5V/3.3V operation modes via SMD jumper
* 4 test pads for easy tracking the supply, d-, d+, and GND
* PCB: FR-4, 1.00 mm (0,039"), solder mask, silkscreen component print
* Dimensions: 65.15x20.38 mm (2.56x0.80")
----

The kernel module is prebuild. You should just get it loaded and then plug the dongle.
* Load the module:
modprobe 8192cu

* Plug the device and check if it is available:
ifconfig -a

==== RT5370 ====
----
[[File:MOD-WIFI-R5370-ANT-1.jpg|border|thumb|[https://www.olimex.com/Products/USB-Modules/MOD-WIFI-R5370-ANT/ MOD-WIFI-R5370-ANT]]]

To use one this wifi dongle (like [https://www.olimex.com/Products/USB-Modules/MOD-WIFI-R5370/ MOD-WIFI-R5370] or [https://www.olimex.com/Products/USB-Modules/MOD-WIFI-R5370-ANT/ MOD-WIFI-R5370-ANT]) additional files are required.

[https://www.olimex.com/Products/USB-Modules/MOD-WIFI-R5370-ANT/ MOD-WIFI-R5370-ANT] has the following features:

* 2.4GHz with 150Mbps PHY data rate
*External antenna for extended range
*USB 2.0 interface
*Security: WEP/TKIP/AES/WPA/WPA2/WAPI
*CMOS single chip with RF, baseband, and MAC integration
*QoS: WMM & WMM-PS support
*Multiple BSSID support
*Maximum likelihood decoding support
*Cisco CCX 5.0 support
*Low-power usage with advanced power management
----

*First a make new directory and navigate to it. This is where the module will search for files.
mkdir -p /etc/Wireless/RT2870STA
cd /etc/Wireless/RT2870STA/

*Download the files from Github
wget https://raw.githubusercontent.com/SelfDestroyer/RK3188-SOM/olimex/stable-3.0/drivers/net/wireless/rtxx7x/RT2870STA.dat
wget https://raw.githubusercontent.com/SelfDestroyer/RK3188-SOM/olimex/stable-3.0/drivers/net/wireless/rtxx7x/RT2870STACard.dat

*Load module
modprobe rt5370sta

*Plug the device and run:
ifconfig -a
*You should see this:
wlan0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

*Configure your new device:
vi /etc/network/interfaces
*Add configuration. Here we will show DHCP configuration.
iface wlan0 inet dhcp
wpa-ssid "'''your ssid'''"
wpa-psk "'''your password'''"

*Save the configuration and up the interface:
ifup wlan0

*If everything is working and this module to be loaded on boot:
echo rt5370sta >> /etc/modules

== Android ==

RK3188-SOM

2024-05-15T11:51:14Z

LubOlimex: /* Debian for NAND memory */

== Overview ==

[[File:Rk3188-som-resized.png|650px]]

RK3188-SOM board is a very productive small beast compared to the previous Olimex board designs. If we compare RockChip RK3188 and Allwinner A20: RK3188 has 4x Cortex-A9, while A20 only 2x Cortex-A7. It runs at 1.6 GHz vs. the 1.0 GHz frequency of the A20. RK3188 reaches a total of 16000 DMPIS vs. the 3800 DMIPS for the A20 (RK3188 is 4.2 times faster). For comparison, the RaspberryPi has 965 DMIPS (RK3188 is 16.6 times faster).

The RK3188-SOM design has the following features:

*Rockchip RK3188 quad core Cortex-A9 processor, each core typically running at 1.6GHz
*1GB DDR3 memory
*Integrated power management unit
*Optional 4GB NAND flash memory for Linux or Android boot
*Micro SD-card for Linux or Android boot
*Three buttons - POWER, RESET, RECOVERY
*Four LEDs (one for power and three user-programmable)
*UART console pins exposed for serial debug
*Five GPIO connectors 2×20 pins @ 0.05" step
*Dimensions: (3.2×1.8)" ~ (81×56)mm
 

== Ready-to-use Debian images ==
=== Debian for microSD card ===

'''Newest official release (recommended):'''

Direct download of Debian release #2:[https://ftp.olimex.com/RK3188_Images/RK3188_debian_3.0.36_SD_release2.img RK3188-SOM Debian for microSD card - kernel 3.0.36+ - release #2]

In the command line interface of image you are automatically logged as root. The default superuser username/password combination in the GUI (XFCE4) is: olimex/olimex.

Build instructions and links to required files for the latest Debian images might be found below in chapter "Building Linux for RK3188-SOM".

====How to prepare your microSD card with the suitable official Debian image?====
----
In order to download an official Linux image to a microSD card under Windows you can use Win32 Disk Imager: [http://sourceforge.net/projects/win32diskimager/ click here]

1. Download the latest official image suitable for a microSD card from the chapter above

2. Download Win32 Disk Imager from this link.

3. Insert card in your microSD card reader.

4. Launch the software.

5. Point the software to the image

6. Click "write"

Under Linux you can write the image image to the card with dd utility. This is how it can be done:

Let's say the name of the image is "debian_2g.img". It would be downloaded to the microSD card connected to a Linux machine using one of the following commands:

dd bs=4M oflag=sync if=debian_2g.img of=/dev/sdX

or

cp debian_2g.img /dev/sdX

where /dev/sdX is the uSD card as listed by the Linux.

=== Debian for NAND memory ===

'''Newest official release (recommended):'''

Direct download Debian for NAND release #1: [https://ftp.olimex.com/RK3188_Images/RK3188_debian_3.0.36_NAND_release1.img|RK3188-SOM Debian for NAND memory - kernel 3.0.36+ - release #1]

Note that this image is suitable only for RK3188-SOM-4GB boards.

Build instructions and links to required files for the latest Debian images might be found below in chapter "Building Linux for RK3188-SOM"

====How to download the ready Debian image to the NAND memory of RK3188-SOM?====
----

'''IMPORTANT: RK3188-SOM-4GB comes with Debian already pre-loaded on the NAND memory. No need to perform this operation initially.'''

1. You need to download the software tools for your computer provided by Rockchip. If you use Windows download “Rockchip Batch Tool”. If you use Linux use either rkflashkit or upgrade_tool. These are the tools that I recommend but there are a lot of tools available. Get the Rockchip batch tool from here: [https://drive.google.com/file/d/0BwplT87k9SCgRDB4ZGY3SnMzd00/view?usp=sharing Rockchip Batch Tool]

For Windows:

2. Install the drivers that allows your computer to recognize the board (that is already set in bootloader mode) connected to it. The installer is called "Rockchip Driver Assistant" – download it here: [https://drive.google.com/file/d/0BwplT87k9SCgbkdXX1ByUW1RSW8/view?usp=sharing Rockchip Driver Assistant]

3. You need to download and extract the latest image suitable for the NAND from our wiki. It is available as a direct download here: [<nowiki>https://ftp.olimex.com/RK3188_Images/RK3188_debian_3.0.36_NAND_release1.img</nowiki> | RK3188 Debian 3.0.36 for NAND memory]

4. You need enter bootloader mode with the board to be able to establish connection between the board and the software provided by Rockchip. You would also need a mini USB cable. To enter bootloader mode you need to press and hold down the recovery button before powering the board (then connect the board to the PC via the mini USB cable). After the board is powered you can release the button.

5. Start the tool for uploading the firmware and point it to the extracted image.

6. Click button "Upgrade".

7. Test with a serial cable.

== Ready-to-use Android images ==
TODO

== Documents ==

[https://www.olimex.com/Products/SOM/RK3188/RK3188-SOM/resources/RK3188-SOM-UM.pdf OLIMEX RK3188-SOM user's manual]

[https://www.olimex.com/Products/SOM/RK3188/RK3188-SOM-EVB/resources/RK3188-SOM-EVB-UM.pdf OLIMEX RK3188-SOM-EVB user's manual]

[https://github.com/OLIMEX/OLINUXINO/raw/master/HARDWARE/RK3188-PDFs/Rockchip%20RK3188%20datasheet%20V1.0.pdf Processor (Rockchip RK3188) datasheet in pdf format]

[https://www.olimex.com/Products/SOM/RK3188/RK3188-SOM/resources/RK3188_SOM_GPIOs.pdf RK3188-SOM connectors' pinout and GPIO table]

=== CAD files ===

RK3188-SOM is considered commercial, proprietary design. The board file is not available to the customer. A pdf extracted from the original schematic is available at GitHub: [https://github.com/OLIMEX/SOM/tree/master/RK3188/RK3188-SOM RK3188-SOM schematics]

RK3188-SOM-EVB is considered Open Source Hardware, Eagle CAD files are available also at GitHub: [https://github.com/OLIMEX/SOM/tree/master/RK3188/RK3188-EVB RK3188-SOM-EVB sources]

The CAD product used to design OLinuXino is Eagle and you can download evaluation free version from their [http://www.cadsoftusa.com/ web site]. The evaluation version allows you to inspect the schematic and the board file sources.

==Board Layout==

[[File:Rk3188-som-resized-TOP-NAMED.png|650px]]

[[File:Rk3188-som-resized-BOTTOM-NAMED.png|650px]]

== Building Linux for RK3188-SOM ==
=== Building the parameter file ===
----
The parameter file describes many board parameters as firmware version, machine id, manufacturer name, etc.

For the user the most important parameter is '''CMDLINE'''. This is the command that is passed to the kernel. It looks something like this:
CMDLINE:console=ttyFIQ0,115200 console=tty0 root=/dev/mmcblk0p1 rw rootfstype=ext4 init=/sbin/init initrd=0x62000000,0x00800000 \
mtdparts=rk29xxnand:0x00008000@0x00002000(boot),-@0x0000A000(linuxroot)

Define serial port at 115200:
console=ttyFIQ0,115200

Define location of the rootfs:
root=/dev/mmcblk0p1

Define rootfs file system as ext4:
rootfstype=ext4

Define the address of the kernel and size:
0x00008000@0x00002000

Define start address of the rootfs:
-@0x0000A000

Additionally, you can set static MAC address with:
mac_addr=xx:xx:xx:xx:xx:xx

Once you're ready with the file, make the parameter image

* Get rkutils:
https://github.com/naobsd/rkutils
cd rkutils
gcc rkcrc.c -o rkcrc
If you're getting error try to comment ''''#include <err.h>'''' in ''''rkcrc.c''''

* Encrypt parameter file:
./rkcrc -p you_parameter_file parameter

The parameter file is ready for further use.

=== Building the kernel ===
----
* Fist prepare the toolchain:
apt-get update
apt-get install gcc-4.7-arm-linux-gnueabihf ncurses-dev uboot-mkimage build-essential git

* Get the sources:
git clone -b olimex/stable-3.0 https://github.com/StefanMavrodiev/RK3188-SOM.git

* Get the default configuration:
cd RK3188-SOM/
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- '''olimex_rk3188_defconfig'''

* You can modify defconfig with (for additional modules):
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- menuconfig

'''Note!''' The default config will set hdmi to 1080p. You can change it from:
Device Drivers --->
Graphics support --->
<*> Frame buffer support for Rockchip --->
LCD Panel Select --->
'''''Choose one of the following:'''''
HDMI framebuffer size and timing is 1080p <--- '''Set HDMI to 1080p'''
HDMI framebuffer size and timing is 720p <--- '''Set HDMI to 720p'''
HDMI framebuffer size and timing is 480p <--- '''Set HDMI to 480p'''
RGB AT070TN90 <--- [https://www.olimex.com/Products/OLinuXino/LCD/LCD-OLinuXino-7/open-source-hardware LCD-OLinuXino-7]
RGB AR010H05N <--- [https://www.olimex.com/Products/OLinuXino/LCD/LCD-OLinuXino-10/open-source-hardware LCD-OLinuXino-10]
RGB BT043DCNNHHP <--- [https://www.olimex.com/Products/OLinuXino/LCD/LCD-OLinuXino-4.3TS/open-source-hardware LCD-OLinuXino-4.3TS]

* Build the kernel:
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- -j4 kernel.img
After the build is finish you will have '''RK3188-SOM/kernel.img''' and '''RK3188-SOM/arch/arm/boot/Image'''. The first one can be uploaded to the kernel partition (if you have one). The second file is raw binary. It can be combined with ramdisk to get boot.img.

* Generate ramdisk
cd ../
git clone https://github.com/radxa/initrd.git
cd initrd/
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- -j4
cd ../

* Make mkbootimg
git clone https://github.com/neo-technologies/rockchip-mkbootimg.git
cd rockchip-mkbootimg
make
make install
cd ../

* Make boot.img
mkbootimg --kernel RK3188-SOM/arch/arm/boot/Image --ramdisk initrd.img -o boot.img

=== Creating the root filesystem ===
==== Debian Wheezy ====
----
In this post we will explain how you can create your own Debian rootfs with pre-installed packages of your choice, which to allow tiny Linux images to be created. All steps below should work on any Debian host (Debian/Ubuntu etc) and are verified with Ubuntu 12.04LTS. First of all you need to install the support packages on your pc:

* Install the needed packages:
sudo apt-get install qemu-user-static debootstrap binfmt-support

* Define some variables:
targetdir=rootfs
distro=wheezy

* Build first stage:
mkdir $targetdir
sudo debootstrap --arch=armhf --foreign $distro $targetdir

* Copy needed files from host to the target:
sudo cp /usr/bin/qemu-arm-static $targetdir/usr/bin/
sudo cp /etc/resolv.conf $targetdir/etc

We should now have a minimal Debian Rootfs.
* Login into the new filesystem:
sudo chroot $targetdir

* Inside the chroot we need to set up the environment again:
distro=wheezy
export LANG=C

* Now we would run the setup for the second stage of debootstrap needs to run install the packages downloaded earlier
/debootstrap/debootstrap --second-stage

* Once the package installation has finished, setup some support files and apt configuration.
cat <<EOT > /etc/apt/sources.list
deb http://ftp.uk.debian.org/debian $distro main contrib non-free
deb-src http://ftp.uk.debian.org/debian $distro main contrib non-free
deb http://ftp.uk.debian.org/debian $distro-updates main contrib non-free
deb-src http://ftp.uk.debian.org/debian $distro-updates main contrib non-free<
deb http://security.debian.org/debian-security $distro/updates main contrib non-free
deb-src http://security.debian.org/debian-security $distro/updates main contrib non-free

EOT

* Update Debian package database:
apt-get update

* Set up locales dpkg scripts since it tends to complain otherwise; note in Debian Jessie you will also need to install the dialog package as well:
apt-get install locales dialog sudo
dpkg-reconfigure locales

* Fix permission for sudo:
chmod u+s /usr/bin/sudo

* Fix ownership of man forlder
chown -R man /var/cache/man

* Install some useful packages inside the chroot:
apt-get install openssh-server ntpdate

* Set a root password so you can login:
passwd

* Build a basic network interface file:
vi /etc/network/interfaces
Add the following to get static ip:
allow-hotplug eth0
iface eth0 inet static
address 192.168.1.254
netmask 255.255.255.248
gateway 192.168.1.1
Or if you want dhcp
allow-hotplug eth0
iface eth0 inet dhcp

Note: Your board will be accessible over SSH on IP address defined above!

* Set the hostname
echo '''myhost'''> /etc/hostname
echo "127.0.0.1 '''myhost'''" >> /etc/hosts

* Enable the serial console, Debian sysvinit way
echo T0:2345:respawn:/sbin/getty -L ttyFIQ0 115200 vt100 >> /etc/inittab

This way you'll get login prompt at startup. By default you cannot login as root. To do this you should make another user, add him to the sudo group, login at startup and then login as root. To skip all this replace the line above with:
echo T0:2345:respawn:/sbin/getty -L ttyFIQ0 -a root 115200 vt100 >> /etc/inittab

* We are done inside the chroot, so quit the chroot shell
exit

* Tidy up the support files
sudo rm $targetdir/etc/resolv.conf
sudo rm $targetdir/usr/bin/qemu-arm-static

===== Installing X =====
----
You cannot run X as root (actually it's possible, but it's a bad practice), so you have to add new user to run X.

* Edit default useradd settings
vi /etc/default/useradd
Modify '''SHELL''' variable:
SHELL=/bin/bash

* Add new user
useradd '''myuser'''

* Add the user to the sudo group
adduser '''myuser''' sudo

* Make home folder
mkdir /home/'''myuser'''
chown -R '''myuser''':'''myuser''' /home/'''myuser'''

* Install xfce4 and lightdm
apt-get update
apt-get install lightdm xfce4

* Modify lightdm configuration to enable autologin:
vi /etc/lightdm/lightdm.conf
autologin-user='''myuser'''
autologin-user-timeout=0
Make sure that the right lines are uncommented. If you don't want autologin just skip the step above.

* Reboot the system
reboot
After the system loads, you should see the default desktop of xfce4.

==== Ubuntu ====
----

You can download prebuild rootfs from [http://releases.linaro.org/ linaro] site or you can build it yourself.

===== Prebuild linaro images =====
----

You can download prebuild images from https://releases.linaro.org/.
In most cases the builds are separated in:
*'''nano'''
*'''developer'''
*'''server'''
*'''alip'''

You can read additional information from [https://wiki.linaro.org/Platform/DevPlatform/Rootfs here].

In this tutorial we will build Ubuntu 14.10 ALIP rootfs.

* Make empty image file:
dd if=/dev/zero of=linaro_alip_rootfs.img bs=1M count=1024

* Format the new image file:
mkfs.ext4 -F -L linuxroot linaro_alip_rootfs.img

* Create mount point:
mkdir mnt
mount -o loop linaro_alip_rootfs.img ./mnt

* Download prebuild image:
wget https://releases.linaro.org/14.10/ubuntu/trusty-images/alip/linaro-trusty-alip-20141024-684.tar.gz

* Make sure that the archive is downloaded:
md5sum linaro-trusty-alip-20141024-684.tar.gz

* Extract is into the mounted image file:
tar -zxvf linaro-trusty-alip-20141024-684.tar.gz
mv binary/* ./mnt

* Copy any modules that are generated with the kernel:
cp -rvf /'''path/to/modules'''/lib/modules ./mnt/lib/

* Chroot into the new rootfs:
cp /usr/bin/qemu-arm-static ./mnt/usr/bin
cp /etc/resolv.conf ./mnt/etc
chroot ./mnt

* Update repository
apt-get update
'''Note!''' If you have a problem with the update, try changing '''sources.list''' to:
deb http://old-releases.ubuntu.com/ubuntu/ raring main universe restricted multiverse
deb-src http://old-releases.ubuntu.com/ubuntu/ raring main universe restricted multiverse
deb http://old-releases.ubuntu.com/ubuntu/ raring-security main universe restricted multiverse
deb-src http://old-releases.ubuntu.com/ubuntu/ raring-security main universe restricted multiverse
deb http://old-releases.ubuntu.com/ubuntu/ raring-updates main universe restricted multiverse
deb-src http://old-releases.ubuntu.com/ubuntu/ raring-updates main universe restricted multiverse
deb http://old-releases.ubuntu.com/ubuntu/ raring-backports main restricted universe multiverse
deb-src http://old-releases.ubuntu.com/ubuntu/ raring-backports main restricted universe multiverse
deb http://old-releases.ubuntu.com/ubuntu/ raring-proposed main restricted universe multiverse
deb-src http://old-releases.ubuntu.com/ubuntu/ raring-proposed main restricted universe multiverse

* Install some useful packages:
apt-get install ssh nano wpasupplicant wireless-tools

* Set root password:
passwd

Linaro prebuild images comes with default use '''linaro'''.
* Set password for user:
passwd linaro

* Add '''linaro''' to sudo group:
adduser linaro sudo

* Configure network. Create new file for loopback, wlan and eth device:
vi /etc/network/interfaces.d/lo
Inside paste:
auto lo
iface lo inet loopback

Do the same for eth:
vi /etc/network/interfaces.d/eth
If you're using dhcp:
auto eth0
iface eth0 inet dhcp
Or for static ip:
auto eth0
iface eth0 inet static
address <your.ip.here>
netmask <your.netmask.here>
gateway <your.gateway.here>

And another for wireless devices:
vi /etc/network/interfaces.d/wlan
auto wlan0
iface lo inet dhcp
wpa-ssid <your.router.ssid>
wpa-pak <your.ssid.password>

'''Note!''' All connections are '''auto'''. If you don't want to use them all the time remove '''auto''' line.

You can do some additional work before exit.
When you are ready to exit from the target filesystem:
exit

Your rootfs is ready. The next step is to create image for nand or sdcard.

===== Manual build using debootstrap =====
----
The procedure is almost identical to the one used for the Debin image.

* First of all you need to install the support packages on your pc
sudo apt-get install qemu-user-static debootstrap binfmt-support ubuntu-archive-keyring

* We will build latest trusty Ubuntu image:
targetdir=ubuntu
distro=trusty

* Now we will build first stage of Ubuntu rootfs:
mkdir $targetdir
sudo debootstrap --arch=armhf --keyring=/usr/share/keyrings/ubuntu-archive-keyring.gpg --foreign $distro $targetdir

* Login into the new filesystem
sudo cp /usr/bin/qemu-arm-static $targetdir/usr/bin/
sudo cp /etc/resolv.conf $targetdir/etc
sudo chroot $targetdir

* Inside the chroot we need to set up the environment again
distro=trusty
export LANG=C

* Now we are setup the second stage of debootstrap needs to run install the packages downloaded earlier
/debootstrap/debootstrap --second-stage

* Configure apt-sources:
cat <<EOT > /etc/apt/sources.list
###### Ubuntu Main Repos
deb http://ports.ubuntu.com/ubuntu-ports/ $distro main restricted universe multiverse
deb-src http://ports.ubuntu.com/ubuntu-ports/ $distro main restricted universe multiverse
###### Ubuntu Update Repos
deb http://ports.ubuntu.com/ubuntu-ports/ $distro-security main restricted universe multiverse
deb http://ports.ubuntu.com/ubuntu-ports/ $distro-updates main restricted universe multiverse
deb-src http://ports.ubuntu.com/ubuntu-ports/ $distro-security main restricted universe multiverse
deb-src http://ports.ubuntu.com/ubuntu-ports/ $distro-updates main restricted universe multiverse
EOT

* Update Ubuntu package database:
apt-get update

* Set a root password so you can login
passwd

* Set the hostname
echo '''myhost'''> /etc/hostname
echo "127.0.0.1 '''myhost'''" >> /etc/hosts

* Build a basic network interface file so that the board will DHCP on eth0
echo <<EOT >> /etc/network/interfaces
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet dhcp
EOT

* Enable the serial console, Debian sysvinit way
echo T0:2345:respawn:/sbin/getty -L ttyFIQ0 115200 vt100 >> /etc/inittab

This way you'll get login prompt at startup. By default you cannot login as root. To do this you should make another user,
add him to the sudo group, login at startup and then login as root. To skip all this replace the line above with:
echo T0:2345:respawn:/sbin/getty -L ttyFIQ0 -a root 115200 vt100 >> /etc/inittab

* We are done inside the chroot, so quit the chroot shell
exit

* Tidy up the support files
sudo rm $targetdir/etc/resolv.conf
sudo rm $targetdir/usr/bin/qemu-arm-static

==== Make rootfs image ====
----

Once you are ready with the rootfs you can make image file. Later it can be used for NAND or SD image. Go to parent directory of you rootfs.

* See how big the image should be:
# du -khs <roofs_folder>
For example this will return 600MB. So we will make 1GB image.

* Make empty image:
# dd if=/dev/zero of=rootfs.img bs=1M count=1024

* Format the image:
# mkfs.ex4 -F -L linuxroot rootfs.img

* Mount the image:
# mount -o loop rootfs.img /mnt

* Copy rootfs files into the image:
# cp -prf <root_folder>/* /mnt/
''''Note!''' Use -p option to keep the permissions for the files and folders.

* Unmount the image:
# umount /mnt

=== Booting from NAND ===
----
* Get rk-tools:
git clone https://github.com/goodybag/rk-tools
cd rk-tools
make

*You will need the following files:
**bootloader --> This is RockChip RK3188Loader
**[[#Building parameter file|parameter]] --> Parameter file with crc encryption
**[[#Building kernel|boot]] --> Kernel with ramdisk compiled as shown here
**[[#Creating root filesystem|linux]] --> Rootfs image file
'''CMDLINE''' in parameter file should look something like this:
CMDLINE:console=ttyFIQ0,115200 console=tty0 root=/dev/block/mtd/by-name/linuxroot rw rootfstype=ext4 init=/sbin/init initrd=0x62000000,0x00800000 mtdparts=rk29xxnand:0x00008000@0x00002000(boot),-@0x0000A000(linuxroot)

* Copy all files in '''rk-tools''' folder

* Edit '''package-file'''. It should be:
#nano package-file

# NAME Relative path
#
#HWDEF HWDEF
package-file package-file
bootloader RK3188Loader
parameter parameter
boot boot.img
linuxroot rootfs.img
backup RESERVED
update-script update-script
recover-script recover-script

* Pack the image:
./afptool -pack . update_tmp.img

* Update the image:
./img_maker -rk31 RK3188Loader 1 0 0 update_tmp.img update.img

The image should be ready. What's left is flashing the image.

*Important: to flash the image the board needs to be in bootloader mode. To enter bootloader mode you need to press and hold down the recovery button before connecting the board to the PC. After the connection is established you can release the button.

 

=== Booting from SD-card ===
----
You'll need at least 512MB sd-card. Depending on rootfs needed size can grow to 4GB.

*You will need the following files:
**sdboot_rk3188.img --> RK3188Loader for booting from SDcard
**[[#Building parameter file|parameter]] --> Parameter file with crc encryption
**[[#Building kernel|boot]] --> Kernel with ramdisk compiled as shown here
**[[#Creating root filesystem|linux]] --> Rootfs image file

'''CMDLINE''' in parameter file should look something like this:
CMDLINE:console=ttyFIQ0,115200 console=tty0 root=/dev/mmcblk0p1 rw rootfstype=ext4 init=/sbin/init initrd=0x62000000,0x00800000 mtdparts=rk29xxnand:0x00008000@0x00002000(boot),-@0x0000A000(linuxroot)

Insert sd-card. Lets say that your device is '''/dev/sdc'''.

* Write Rockchip loader:
dd if=sdboot_rk3188.img of=/dev/sdc conv=sync,fsync

* Write parameter file:
dd if=parameter.img of=/dev/sdc conv=sync,fsync seek=$((0x2000))

* Write kernel:
dd if=boot.img of=/dev/sdc conv=sync,fsync seek=$((0x2000+0x2000))

* Write rootfs:
dd if=rootfs.img of=/dev/sdc conv=sync,fsync seek=$((0x2000+0xA000))

You can do this also on image file:
dd if=/dev/zero of=sd.img bs=1M count=1024
If 1GB is not enough increase count number.

* Write Rockchip loader:
dd if=sdboot_rk3188.img of=sd.img conv=sync,fsync

* Write parameter file:
dd if=parameter.img of=sd.img conv=sync,fsync seek=$((0x2000))

* Write kernel:
dd if=boot.img of=sd.img conv=sync,fsync seek=$((0x2000+0x2000))

* Write rootfs:
dd if=rootfs.img of=sd.img conv=sync,fsync seek=$((0x2000+0xA000))

* Format image:
fdisk sd.img << EOF
n
p
1
49152

w
EOF

=== Calibrate touchscreen ===
If you want to use LCD panel with touchscreen, you should perform a screen calibration.

==== Calibrate using tslib ====
----

* Install the required packages:
apt-get update
apt-get install xorg-dev xserver-xorg-dev x11proto-core-dev git automake make libtool

* Download tslib:
git clone https://github.com/kergoth/tslib.git
cd tslib

* Download patch:
cd plugin
wget https://dl.dropbox.com/u/40057/patches/input-raw.c
cd ../

* Compile the library:
autoreconf -vi
./configure --prefix=/usr
make
make install
ldconfig

* Modify tslib configuration
vi /usr/etc/ts.conf
Uncomment the following line:
module_raw input

* Export tslib needed variables:
export TSLIB_TSEVENTTYPE=raw
export TSLIB_CONSOLEDEVICE=none
export TSLIB_FBDEVICE=/dev/fb0
export TSLIB_TSDEVICE=/dev/input/event0
export TSLIB_CALIBFILE=/usr/etc/pointercal
export TSLIB_CONFFILE=/usr/etc/ts.conf
export TSLIB_PLUGINDIR=/usr/lib/ts

* Now tslib is working but still it should be set as default driver in the X:
wget http://ftp.de.debian.org/debian/pool/main/x/xf86-input-tslib/xf86-input-tslib_0.0.6.orig.tar.gz
tar zxfv xf86-input-tslib_0.0.6.orig.tar.gz
cd xf86-input-tslib-0.0.6/
Replace tslib.c file with patched one:
cd src/
rm -f tslib.c
wget https://dl.dropbox.com/u/40057/patches/tslib.c
cd ..
Build and install package:
./configure --prefix=/usr
make
make install

* Add tslib configuration:
cd /usr/share/X11/xorg.conf.d/
Make new file:
nano 20-touchscreen.conf
Add the following text inside:
Section "InputClass"
Identifier "AR1020"
MatchDevicePath "/dev/input/event0"
Driver "tslib"
Option "Device" "/dev/input/event0"
Option "ScreenNumber" "0"
Option "Rotate" "NONE"
Option "Width" "'''800'''"
Option "Height" "'''480'''"
Option "SendCoreEvents" "yes"
Option "Type" "touchscreen"
EndSection
Note! Resolution in this example is set for 7 inch LCD.

* Do the actual calibration:
service lightdm stop
ts_calibrate
service lightdm start
After lightdm start you could check if everything is running smoothly.

* Save tslib variables:
vi /etc/environment
Paste the following:
TSLIB_TSEVENTTYPE=raw
TSLIB_CONSOLEDEVICE=none
TSLIB_FBDEVICE=/dev/fb0
TSLIB_TSDEVICE=/dev/input/event0
TSLIB_CALIBFILE=/etc/pointercal
TSLIB_CONFFILE=/usr/etc/ts.conf
TSLIB_PLUGINDIR=/usr/lib/ts

If you change the LCD panel run ts_calibrate to configure touchscreen for the new LCD.

==== Calibrate using AR1021 driver ====
TODO

=== Enabling wireless modules ===
==== RTL8188CUS ====
----
[[File:MOD-WIFI-RTL8188-1.jpg|thumb|[https://www.olimex.com/Products/USB-Modules/MOD-WIFI-RTL8188/ MOD-WIFI-RTL8188]]]
To connect OLinuXino board with wireless, you could use [https://www.olimex.com/Products/USB-Modules/MOD-WIFI-RTL8188/ MOD-WIFI-RTL8188] dongle. Also you can use another one with the same chip.

[https://www.olimex.com/Products/USB-Modules/MOD-WIFI-RTL8188/ MOD-WIFI-RTL8188] has the following features:
* Has WM-294 module with RTL8188
* Operates in 2.4 GHz frequency bands
* 1x1 MIMO technology improves effective throughput and range over existing 802.11 b/g products
* Data rates: up to 150Mbps
* 802.11e-compatible bursting and I standards BPSK, QPSK, 16 QAM, 64 QAM modulation schemes WEP, TKIP, and AES, WPA, WPA2 hardware encryption schemes
* Standard USB type A connector
* On-board antenna
* 5V/3.3V operation modes via SMD jumper
* 4 test pads for easy tracking the supply, d-, d+, and GND
* PCB: FR-4, 1.00 mm (0,039"), solder mask, silkscreen component print
* Dimensions: 65.15x20.38 mm (2.56x0.80")
----

The kernel module is prebuild. You should just get it loaded and then plug the dongle.
* Load the module:
modprobe 8192cu

* Plug the device and check if it is available:
ifconfig -a

==== RT5370 ====
----
[[File:MOD-WIFI-R5370-ANT-1.jpg|border|thumb|[https://www.olimex.com/Products/USB-Modules/MOD-WIFI-R5370-ANT/ MOD-WIFI-R5370-ANT]]]

To use one this wifi dongle (like [https://www.olimex.com/Products/USB-Modules/MOD-WIFI-R5370/ MOD-WIFI-R5370] or [https://www.olimex.com/Products/USB-Modules/MOD-WIFI-R5370-ANT/ MOD-WIFI-R5370-ANT]) additional files are required.

[https://www.olimex.com/Products/USB-Modules/MOD-WIFI-R5370-ANT/ MOD-WIFI-R5370-ANT] has the following features:

* 2.4GHz with 150Mbps PHY data rate
*External antenna for extended range
*USB 2.0 interface
*Security: WEP/TKIP/AES/WPA/WPA2/WAPI
*CMOS single chip with RF, baseband, and MAC integration
*QoS: WMM & WMM-PS support
*Multiple BSSID support
*Maximum likelihood decoding support
*Cisco CCX 5.0 support
*Low-power usage with advanced power management
----

*First a make new directory and navigate to it. This is where the module will search for files.
mkdir -p /etc/Wireless/RT2870STA
cd /etc/Wireless/RT2870STA/

*Download the files from Github
wget https://raw.githubusercontent.com/SelfDestroyer/RK3188-SOM/olimex/stable-3.0/drivers/net/wireless/rtxx7x/RT2870STA.dat
wget https://raw.githubusercontent.com/SelfDestroyer/RK3188-SOM/olimex/stable-3.0/drivers/net/wireless/rtxx7x/RT2870STACard.dat

*Load module
modprobe rt5370sta

*Plug the device and run:
ifconfig -a
*You should see this:
wlan0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

*Configure your new device:
vi /etc/network/interfaces
*Add configuration. Here we will show DHCP configuration.
iface wlan0 inet dhcp
wpa-ssid "'''your ssid'''"
wpa-psk "'''your password'''"

*Save the configuration and up the interface:
ifup wlan0

*If everything is working and this module to be loaded on boot:
echo rt5370sta >> /etc/modules

== Android ==

RK3188-SOM

2024-05-15T11:44:49Z

LubOlimex: /* Debian for NAND memory */

== Overview ==

[[File:Rk3188-som-resized.png|650px]]

RK3188-SOM board is a very productive small beast compared to the previous Olimex board designs. If we compare RockChip RK3188 and Allwinner A20: RK3188 has 4x Cortex-A9, while A20 only 2x Cortex-A7. It runs at 1.6 GHz vs. the 1.0 GHz frequency of the A20. RK3188 reaches a total of 16000 DMPIS vs. the 3800 DMIPS for the A20 (RK3188 is 4.2 times faster). For comparison, the RaspberryPi has 965 DMIPS (RK3188 is 16.6 times faster).

The RK3188-SOM design has the following features:

*Rockchip RK3188 quad core Cortex-A9 processor, each core typically running at 1.6GHz
*1GB DDR3 memory
*Integrated power management unit
*Optional 4GB NAND flash memory for Linux or Android boot
*Micro SD-card for Linux or Android boot
*Three buttons - POWER, RESET, RECOVERY
*Four LEDs (one for power and three user-programmable)
*UART console pins exposed for serial debug
*Five GPIO connectors 2×20 pins @ 0.05" step
*Dimensions: (3.2×1.8)" ~ (81×56)mm
 

== Ready-to-use Debian images ==
=== Debian for microSD card ===

'''Newest official release (recommended):'''

Direct download of Debian release #2:[https://ftp.olimex.com/RK3188_Images/RK3188_debian_3.0.36_SD_release2.img RK3188-SOM Debian for microSD card - kernel 3.0.36+ - release #2]

In the command line interface of image you are automatically logged as root. The default superuser username/password combination in the GUI (XFCE4) is: olimex/olimex.

Build instructions and links to required files for the latest Debian images might be found below in chapter "Building Linux for RK3188-SOM".

====How to prepare your microSD card with the suitable official Debian image?====
----
In order to download an official Linux image to a microSD card under Windows you can use Win32 Disk Imager: [http://sourceforge.net/projects/win32diskimager/ click here]

1. Download the latest official image suitable for a microSD card from the chapter above

2. Download Win32 Disk Imager from this link.

3. Insert card in your microSD card reader.

4. Launch the software.

5. Point the software to the image

6. Click "write"

Under Linux you can write the image image to the card with dd utility. This is how it can be done:

Let's say the name of the image is "debian_2g.img". It would be downloaded to the microSD card connected to a Linux machine using one of the following commands:

dd bs=4M oflag=sync if=debian_2g.img of=/dev/sdX

or

cp debian_2g.img /dev/sdX

where /dev/sdX is the uSD card as listed by the Linux.

=== Debian for NAND memory ===

'''Newest official release (recommended):'''

Direct download Debian for NAND release #1: [https://ftp.olimex.com/RK3188_Images/RK3188_debian_3.0.36_NAND_release1.img|RK3188-SOM Debian for NAND memory - kernel 3.0.36+ - release #1]

Note that this image is suitable only for RK3188-SOM-4GB boards.

Build instructions and links to required files for the latest Debian images might be found below in chapter "Building Linux for RK3188-SOM"

====How to download the ready Debian image to the NAND memory of RK3188-SOM?====
----

'''IMPORTANT: RK3188-SOM-4GB comes with Debian already pre-loaded on the NAND memory. No need to perform this operation initially.'''

1. You need to download the software tools for your computer provided by Rockchip. If you use Windows download “Rockchip Batch Tool”. If you use Linux use either rkflashkit or upgrade_tool. These are the tools that I recommend but there are a lot of tools available. Get the Rockchip batch tool from here: [https://drive.google.com/file/d/0BwplT87k9SCgRDB4ZGY3SnMzd00/view?usp=sharing Rockchip Batch Tool]

For Windows:

2. Install the drivers that allows your computer to recognize the board (that is already set in bootloader mode) connected to it. The installer is called "Rockchip Driver Assistant" – download it here: [https://drive.google.com/file/d/0BwplT87k9SCgbkdXX1ByUW1RSW8/view?usp=sharing Rockchip Driver Assistant]

3. You need to download and extract the latest image suitable for the NAND from our wiki. It is available as a direct download here: [https://ftp.olimex.com/RK3188_Images/RK3188_debian_3.0.36_NAND_release1.img|RK3188 Debian 3.0.36 for NAND memory]

4. You need enter bootloader mode with the board to be able to establish connection between the board and the software provided by Rockchip. You would also need a mini USB cable. To enter bootloader mode you need to press and hold down the recovery button before powering the board (then connect the board to the PC via the mini USB cable). After the board is powered you can release the button.

5. Start the tool for uploading the firmware and point it to the extracted image.

6. Click button "Upgrade".

7. Test with a serial cable.

== Ready-to-use Android images ==
TODO

== Documents ==

[https://www.olimex.com/Products/SOM/RK3188/RK3188-SOM/resources/RK3188-SOM-UM.pdf OLIMEX RK3188-SOM user's manual]

[https://www.olimex.com/Products/SOM/RK3188/RK3188-SOM-EVB/resources/RK3188-SOM-EVB-UM.pdf OLIMEX RK3188-SOM-EVB user's manual]

[https://github.com/OLIMEX/OLINUXINO/raw/master/HARDWARE/RK3188-PDFs/Rockchip%20RK3188%20datasheet%20V1.0.pdf Processor (Rockchip RK3188) datasheet in pdf format]

[https://www.olimex.com/Products/SOM/RK3188/RK3188-SOM/resources/RK3188_SOM_GPIOs.pdf RK3188-SOM connectors' pinout and GPIO table]

=== CAD files ===

RK3188-SOM is considered commercial, proprietary design. The board file is not available to the customer. A pdf extracted from the original schematic is available at GitHub: [https://github.com/OLIMEX/SOM/tree/master/RK3188/RK3188-SOM RK3188-SOM schematics]

RK3188-SOM-EVB is considered Open Source Hardware, Eagle CAD files are available also at GitHub: [https://github.com/OLIMEX/SOM/tree/master/RK3188/RK3188-EVB RK3188-SOM-EVB sources]

The CAD product used to design OLinuXino is Eagle and you can download evaluation free version from their [http://www.cadsoftusa.com/ web site]. The evaluation version allows you to inspect the schematic and the board file sources.

==Board Layout==

[[File:Rk3188-som-resized-TOP-NAMED.png|650px]]

[[File:Rk3188-som-resized-BOTTOM-NAMED.png|650px]]

== Building Linux for RK3188-SOM ==
=== Building the parameter file ===
----
The parameter file describes many board parameters as firmware version, machine id, manufacturer name, etc.

For the user the most important parameter is '''CMDLINE'''. This is the command that is passed to the kernel. It looks something like this:
CMDLINE:console=ttyFIQ0,115200 console=tty0 root=/dev/mmcblk0p1 rw rootfstype=ext4 init=/sbin/init initrd=0x62000000,0x00800000 \
mtdparts=rk29xxnand:0x00008000@0x00002000(boot),-@0x0000A000(linuxroot)

Define serial port at 115200:
console=ttyFIQ0,115200

Define location of the rootfs:
root=/dev/mmcblk0p1

Define rootfs file system as ext4:
rootfstype=ext4

Define the address of the kernel and size:
0x00008000@0x00002000

Define start address of the rootfs:
-@0x0000A000

Additionally, you can set static MAC address with:
mac_addr=xx:xx:xx:xx:xx:xx

Once you're ready with the file, make the parameter image

* Get rkutils:
https://github.com/naobsd/rkutils
cd rkutils
gcc rkcrc.c -o rkcrc
If you're getting error try to comment ''''#include <err.h>'''' in ''''rkcrc.c''''

* Encrypt parameter file:
./rkcrc -p you_parameter_file parameter

The parameter file is ready for further use.

=== Building the kernel ===
----
* Fist prepare the toolchain:
apt-get update
apt-get install gcc-4.7-arm-linux-gnueabihf ncurses-dev uboot-mkimage build-essential git

* Get the sources:
git clone -b olimex/stable-3.0 https://github.com/StefanMavrodiev/RK3188-SOM.git

* Get the default configuration:
cd RK3188-SOM/
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- '''olimex_rk3188_defconfig'''

* You can modify defconfig with (for additional modules):
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- menuconfig

'''Note!''' The default config will set hdmi to 1080p. You can change it from:
Device Drivers --->
Graphics support --->
<*> Frame buffer support for Rockchip --->
LCD Panel Select --->
'''''Choose one of the following:'''''
HDMI framebuffer size and timing is 1080p <--- '''Set HDMI to 1080p'''
HDMI framebuffer size and timing is 720p <--- '''Set HDMI to 720p'''
HDMI framebuffer size and timing is 480p <--- '''Set HDMI to 480p'''
RGB AT070TN90 <--- [https://www.olimex.com/Products/OLinuXino/LCD/LCD-OLinuXino-7/open-source-hardware LCD-OLinuXino-7]
RGB AR010H05N <--- [https://www.olimex.com/Products/OLinuXino/LCD/LCD-OLinuXino-10/open-source-hardware LCD-OLinuXino-10]
RGB BT043DCNNHHP <--- [https://www.olimex.com/Products/OLinuXino/LCD/LCD-OLinuXino-4.3TS/open-source-hardware LCD-OLinuXino-4.3TS]

* Build the kernel:
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- -j4 kernel.img
After the build is finish you will have '''RK3188-SOM/kernel.img''' and '''RK3188-SOM/arch/arm/boot/Image'''. The first one can be uploaded to the kernel partition (if you have one). The second file is raw binary. It can be combined with ramdisk to get boot.img.

* Generate ramdisk
cd ../
git clone https://github.com/radxa/initrd.git
cd initrd/
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- -j4
cd ../

* Make mkbootimg
git clone https://github.com/neo-technologies/rockchip-mkbootimg.git
cd rockchip-mkbootimg
make
make install
cd ../

* Make boot.img
mkbootimg --kernel RK3188-SOM/arch/arm/boot/Image --ramdisk initrd.img -o boot.img

=== Creating the root filesystem ===
==== Debian Wheezy ====
----
In this post we will explain how you can create your own Debian rootfs with pre-installed packages of your choice, which to allow tiny Linux images to be created. All steps below should work on any Debian host (Debian/Ubuntu etc) and are verified with Ubuntu 12.04LTS. First of all you need to install the support packages on your pc:

* Install the needed packages:
sudo apt-get install qemu-user-static debootstrap binfmt-support

* Define some variables:
targetdir=rootfs
distro=wheezy

* Build first stage:
mkdir $targetdir
sudo debootstrap --arch=armhf --foreign $distro $targetdir

* Copy needed files from host to the target:
sudo cp /usr/bin/qemu-arm-static $targetdir/usr/bin/
sudo cp /etc/resolv.conf $targetdir/etc

We should now have a minimal Debian Rootfs.
* Login into the new filesystem:
sudo chroot $targetdir

* Inside the chroot we need to set up the environment again:
distro=wheezy
export LANG=C

* Now we would run the setup for the second stage of debootstrap needs to run install the packages downloaded earlier
/debootstrap/debootstrap --second-stage

* Once the package installation has finished, setup some support files and apt configuration.
cat <<EOT > /etc/apt/sources.list
deb http://ftp.uk.debian.org/debian $distro main contrib non-free
deb-src http://ftp.uk.debian.org/debian $distro main contrib non-free
deb http://ftp.uk.debian.org/debian $distro-updates main contrib non-free
deb-src http://ftp.uk.debian.org/debian $distro-updates main contrib non-free<
deb http://security.debian.org/debian-security $distro/updates main contrib non-free
deb-src http://security.debian.org/debian-security $distro/updates main contrib non-free

EOT

* Update Debian package database:
apt-get update

* Set up locales dpkg scripts since it tends to complain otherwise; note in Debian Jessie you will also need to install the dialog package as well:
apt-get install locales dialog sudo
dpkg-reconfigure locales

* Fix permission for sudo:
chmod u+s /usr/bin/sudo

* Fix ownership of man forlder
chown -R man /var/cache/man

* Install some useful packages inside the chroot:
apt-get install openssh-server ntpdate

* Set a root password so you can login:
passwd

* Build a basic network interface file:
vi /etc/network/interfaces
Add the following to get static ip:
allow-hotplug eth0
iface eth0 inet static
address 192.168.1.254
netmask 255.255.255.248
gateway 192.168.1.1
Or if you want dhcp
allow-hotplug eth0
iface eth0 inet dhcp

Note: Your board will be accessible over SSH on IP address defined above!

* Set the hostname
echo '''myhost'''> /etc/hostname
echo "127.0.0.1 '''myhost'''" >> /etc/hosts

* Enable the serial console, Debian sysvinit way
echo T0:2345:respawn:/sbin/getty -L ttyFIQ0 115200 vt100 >> /etc/inittab

This way you'll get login prompt at startup. By default you cannot login as root. To do this you should make another user, add him to the sudo group, login at startup and then login as root. To skip all this replace the line above with:
echo T0:2345:respawn:/sbin/getty -L ttyFIQ0 -a root 115200 vt100 >> /etc/inittab

* We are done inside the chroot, so quit the chroot shell
exit

* Tidy up the support files
sudo rm $targetdir/etc/resolv.conf
sudo rm $targetdir/usr/bin/qemu-arm-static

===== Installing X =====
----
You cannot run X as root (actually it's possible, but it's a bad practice), so you have to add new user to run X.

* Edit default useradd settings
vi /etc/default/useradd
Modify '''SHELL''' variable:
SHELL=/bin/bash

* Add new user
useradd '''myuser'''

* Add the user to the sudo group
adduser '''myuser''' sudo

* Make home folder
mkdir /home/'''myuser'''
chown -R '''myuser''':'''myuser''' /home/'''myuser'''

* Install xfce4 and lightdm
apt-get update
apt-get install lightdm xfce4

* Modify lightdm configuration to enable autologin:
vi /etc/lightdm/lightdm.conf
autologin-user='''myuser'''
autologin-user-timeout=0
Make sure that the right lines are uncommented. If you don't want autologin just skip the step above.

* Reboot the system
reboot
After the system loads, you should see the default desktop of xfce4.

==== Ubuntu ====
----

You can download prebuild rootfs from [http://releases.linaro.org/ linaro] site or you can build it yourself.

===== Prebuild linaro images =====
----

You can download prebuild images from https://releases.linaro.org/.
In most cases the builds are separated in:
*'''nano'''
*'''developer'''
*'''server'''
*'''alip'''

You can read additional information from [https://wiki.linaro.org/Platform/DevPlatform/Rootfs here].

In this tutorial we will build Ubuntu 14.10 ALIP rootfs.

* Make empty image file:
dd if=/dev/zero of=linaro_alip_rootfs.img bs=1M count=1024

* Format the new image file:
mkfs.ext4 -F -L linuxroot linaro_alip_rootfs.img

* Create mount point:
mkdir mnt
mount -o loop linaro_alip_rootfs.img ./mnt

* Download prebuild image:
wget https://releases.linaro.org/14.10/ubuntu/trusty-images/alip/linaro-trusty-alip-20141024-684.tar.gz

* Make sure that the archive is downloaded:
md5sum linaro-trusty-alip-20141024-684.tar.gz

* Extract is into the mounted image file:
tar -zxvf linaro-trusty-alip-20141024-684.tar.gz
mv binary/* ./mnt

* Copy any modules that are generated with the kernel:
cp -rvf /'''path/to/modules'''/lib/modules ./mnt/lib/

* Chroot into the new rootfs:
cp /usr/bin/qemu-arm-static ./mnt/usr/bin
cp /etc/resolv.conf ./mnt/etc
chroot ./mnt

* Update repository
apt-get update
'''Note!''' If you have a problem with the update, try changing '''sources.list''' to:
deb http://old-releases.ubuntu.com/ubuntu/ raring main universe restricted multiverse
deb-src http://old-releases.ubuntu.com/ubuntu/ raring main universe restricted multiverse
deb http://old-releases.ubuntu.com/ubuntu/ raring-security main universe restricted multiverse
deb-src http://old-releases.ubuntu.com/ubuntu/ raring-security main universe restricted multiverse
deb http://old-releases.ubuntu.com/ubuntu/ raring-updates main universe restricted multiverse
deb-src http://old-releases.ubuntu.com/ubuntu/ raring-updates main universe restricted multiverse
deb http://old-releases.ubuntu.com/ubuntu/ raring-backports main restricted universe multiverse
deb-src http://old-releases.ubuntu.com/ubuntu/ raring-backports main restricted universe multiverse
deb http://old-releases.ubuntu.com/ubuntu/ raring-proposed main restricted universe multiverse
deb-src http://old-releases.ubuntu.com/ubuntu/ raring-proposed main restricted universe multiverse

* Install some useful packages:
apt-get install ssh nano wpasupplicant wireless-tools

* Set root password:
passwd

Linaro prebuild images comes with default use '''linaro'''.
* Set password for user:
passwd linaro

* Add '''linaro''' to sudo group:
adduser linaro sudo

* Configure network. Create new file for loopback, wlan and eth device:
vi /etc/network/interfaces.d/lo
Inside paste:
auto lo
iface lo inet loopback

Do the same for eth:
vi /etc/network/interfaces.d/eth
If you're using dhcp:
auto eth0
iface eth0 inet dhcp
Or for static ip:
auto eth0
iface eth0 inet static
address <your.ip.here>
netmask <your.netmask.here>
gateway <your.gateway.here>

And another for wireless devices:
vi /etc/network/interfaces.d/wlan
auto wlan0
iface lo inet dhcp
wpa-ssid <your.router.ssid>
wpa-pak <your.ssid.password>

'''Note!''' All connections are '''auto'''. If you don't want to use them all the time remove '''auto''' line.

You can do some additional work before exit.
When you are ready to exit from the target filesystem:
exit

Your rootfs is ready. The next step is to create image for nand or sdcard.

===== Manual build using debootstrap =====
----
The procedure is almost identical to the one used for the Debin image.

* First of all you need to install the support packages on your pc
sudo apt-get install qemu-user-static debootstrap binfmt-support ubuntu-archive-keyring

* We will build latest trusty Ubuntu image:
targetdir=ubuntu
distro=trusty

* Now we will build first stage of Ubuntu rootfs:
mkdir $targetdir
sudo debootstrap --arch=armhf --keyring=/usr/share/keyrings/ubuntu-archive-keyring.gpg --foreign $distro $targetdir

* Login into the new filesystem
sudo cp /usr/bin/qemu-arm-static $targetdir/usr/bin/
sudo cp /etc/resolv.conf $targetdir/etc
sudo chroot $targetdir

* Inside the chroot we need to set up the environment again
distro=trusty
export LANG=C

* Now we are setup the second stage of debootstrap needs to run install the packages downloaded earlier
/debootstrap/debootstrap --second-stage

* Configure apt-sources:
cat <<EOT > /etc/apt/sources.list
###### Ubuntu Main Repos
deb http://ports.ubuntu.com/ubuntu-ports/ $distro main restricted universe multiverse
deb-src http://ports.ubuntu.com/ubuntu-ports/ $distro main restricted universe multiverse
###### Ubuntu Update Repos
deb http://ports.ubuntu.com/ubuntu-ports/ $distro-security main restricted universe multiverse
deb http://ports.ubuntu.com/ubuntu-ports/ $distro-updates main restricted universe multiverse
deb-src http://ports.ubuntu.com/ubuntu-ports/ $distro-security main restricted universe multiverse
deb-src http://ports.ubuntu.com/ubuntu-ports/ $distro-updates main restricted universe multiverse
EOT

* Update Ubuntu package database:
apt-get update

* Set a root password so you can login
passwd

* Set the hostname
echo '''myhost'''> /etc/hostname
echo "127.0.0.1 '''myhost'''" >> /etc/hosts

* Build a basic network interface file so that the board will DHCP on eth0
echo <<EOT >> /etc/network/interfaces
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet dhcp
EOT

* Enable the serial console, Debian sysvinit way
echo T0:2345:respawn:/sbin/getty -L ttyFIQ0 115200 vt100 >> /etc/inittab

This way you'll get login prompt at startup. By default you cannot login as root. To do this you should make another user,
add him to the sudo group, login at startup and then login as root. To skip all this replace the line above with:
echo T0:2345:respawn:/sbin/getty -L ttyFIQ0 -a root 115200 vt100 >> /etc/inittab

* We are done inside the chroot, so quit the chroot shell
exit

* Tidy up the support files
sudo rm $targetdir/etc/resolv.conf
sudo rm $targetdir/usr/bin/qemu-arm-static

==== Make rootfs image ====
----

Once you are ready with the rootfs you can make image file. Later it can be used for NAND or SD image. Go to parent directory of you rootfs.

* See how big the image should be:
# du -khs <roofs_folder>
For example this will return 600MB. So we will make 1GB image.

* Make empty image:
# dd if=/dev/zero of=rootfs.img bs=1M count=1024

* Format the image:
# mkfs.ex4 -F -L linuxroot rootfs.img

* Mount the image:
# mount -o loop rootfs.img /mnt

* Copy rootfs files into the image:
# cp -prf <root_folder>/* /mnt/
''''Note!''' Use -p option to keep the permissions for the files and folders.

* Unmount the image:
# umount /mnt

=== Booting from NAND ===
----
* Get rk-tools:
git clone https://github.com/goodybag/rk-tools
cd rk-tools
make

*You will need the following files:
**bootloader --> This is RockChip RK3188Loader
**[[#Building parameter file|parameter]] --> Parameter file with crc encryption
**[[#Building kernel|boot]] --> Kernel with ramdisk compiled as shown here
**[[#Creating root filesystem|linux]] --> Rootfs image file
'''CMDLINE''' in parameter file should look something like this:
CMDLINE:console=ttyFIQ0,115200 console=tty0 root=/dev/block/mtd/by-name/linuxroot rw rootfstype=ext4 init=/sbin/init initrd=0x62000000,0x00800000 mtdparts=rk29xxnand:0x00008000@0x00002000(boot),-@0x0000A000(linuxroot)

* Copy all files in '''rk-tools''' folder

* Edit '''package-file'''. It should be:
#nano package-file

# NAME Relative path
#
#HWDEF HWDEF
package-file package-file
bootloader RK3188Loader
parameter parameter
boot boot.img
linuxroot rootfs.img
backup RESERVED
update-script update-script
recover-script recover-script

* Pack the image:
./afptool -pack . update_tmp.img

* Update the image:
./img_maker -rk31 RK3188Loader 1 0 0 update_tmp.img update.img

The image should be ready. What's left is flashing the image.

*Important: to flash the image the board needs to be in bootloader mode. To enter bootloader mode you need to press and hold down the recovery button before connecting the board to the PC. After the connection is established you can release the button.

 

=== Booting from SD-card ===
----
You'll need at least 512MB sd-card. Depending on rootfs needed size can grow to 4GB.

*You will need the following files:
**sdboot_rk3188.img --> RK3188Loader for booting from SDcard
**[[#Building parameter file|parameter]] --> Parameter file with crc encryption
**[[#Building kernel|boot]] --> Kernel with ramdisk compiled as shown here
**[[#Creating root filesystem|linux]] --> Rootfs image file

'''CMDLINE''' in parameter file should look something like this:
CMDLINE:console=ttyFIQ0,115200 console=tty0 root=/dev/mmcblk0p1 rw rootfstype=ext4 init=/sbin/init initrd=0x62000000,0x00800000 mtdparts=rk29xxnand:0x00008000@0x00002000(boot),-@0x0000A000(linuxroot)

Insert sd-card. Lets say that your device is '''/dev/sdc'''.

* Write Rockchip loader:
dd if=sdboot_rk3188.img of=/dev/sdc conv=sync,fsync

* Write parameter file:
dd if=parameter.img of=/dev/sdc conv=sync,fsync seek=$((0x2000))

* Write kernel:
dd if=boot.img of=/dev/sdc conv=sync,fsync seek=$((0x2000+0x2000))

* Write rootfs:
dd if=rootfs.img of=/dev/sdc conv=sync,fsync seek=$((0x2000+0xA000))

You can do this also on image file:
dd if=/dev/zero of=sd.img bs=1M count=1024
If 1GB is not enough increase count number.

* Write Rockchip loader:
dd if=sdboot_rk3188.img of=sd.img conv=sync,fsync

* Write parameter file:
dd if=parameter.img of=sd.img conv=sync,fsync seek=$((0x2000))

* Write kernel:
dd if=boot.img of=sd.img conv=sync,fsync seek=$((0x2000+0x2000))

* Write rootfs:
dd if=rootfs.img of=sd.img conv=sync,fsync seek=$((0x2000+0xA000))

* Format image:
fdisk sd.img << EOF
n
p
1
49152

w
EOF

=== Calibrate touchscreen ===
If you want to use LCD panel with touchscreen, you should perform a screen calibration.

==== Calibrate using tslib ====
----

* Install the required packages:
apt-get update
apt-get install xorg-dev xserver-xorg-dev x11proto-core-dev git automake make libtool

* Download tslib:
git clone https://github.com/kergoth/tslib.git
cd tslib

* Download patch:
cd plugin
wget https://dl.dropbox.com/u/40057/patches/input-raw.c
cd ../

* Compile the library:
autoreconf -vi
./configure --prefix=/usr
make
make install
ldconfig

* Modify tslib configuration
vi /usr/etc/ts.conf
Uncomment the following line:
module_raw input

* Export tslib needed variables:
export TSLIB_TSEVENTTYPE=raw
export TSLIB_CONSOLEDEVICE=none
export TSLIB_FBDEVICE=/dev/fb0
export TSLIB_TSDEVICE=/dev/input/event0
export TSLIB_CALIBFILE=/usr/etc/pointercal
export TSLIB_CONFFILE=/usr/etc/ts.conf
export TSLIB_PLUGINDIR=/usr/lib/ts

* Now tslib is working but still it should be set as default driver in the X:
wget http://ftp.de.debian.org/debian/pool/main/x/xf86-input-tslib/xf86-input-tslib_0.0.6.orig.tar.gz
tar zxfv xf86-input-tslib_0.0.6.orig.tar.gz
cd xf86-input-tslib-0.0.6/
Replace tslib.c file with patched one:
cd src/
rm -f tslib.c
wget https://dl.dropbox.com/u/40057/patches/tslib.c
cd ..
Build and install package:
./configure --prefix=/usr
make
make install

* Add tslib configuration:
cd /usr/share/X11/xorg.conf.d/
Make new file:
nano 20-touchscreen.conf
Add the following text inside:
Section "InputClass"
Identifier "AR1020"
MatchDevicePath "/dev/input/event0"
Driver "tslib"
Option "Device" "/dev/input/event0"
Option "ScreenNumber" "0"
Option "Rotate" "NONE"
Option "Width" "'''800'''"
Option "Height" "'''480'''"
Option "SendCoreEvents" "yes"
Option "Type" "touchscreen"
EndSection
Note! Resolution in this example is set for 7 inch LCD.

* Do the actual calibration:
service lightdm stop
ts_calibrate
service lightdm start
After lightdm start you could check if everything is running smoothly.

* Save tslib variables:
vi /etc/environment
Paste the following:
TSLIB_TSEVENTTYPE=raw
TSLIB_CONSOLEDEVICE=none
TSLIB_FBDEVICE=/dev/fb0
TSLIB_TSDEVICE=/dev/input/event0
TSLIB_CALIBFILE=/etc/pointercal
TSLIB_CONFFILE=/usr/etc/ts.conf
TSLIB_PLUGINDIR=/usr/lib/ts

If you change the LCD panel run ts_calibrate to configure touchscreen for the new LCD.

==== Calibrate using AR1021 driver ====
TODO

=== Enabling wireless modules ===
==== RTL8188CUS ====
----
[[File:MOD-WIFI-RTL8188-1.jpg|thumb|[https://www.olimex.com/Products/USB-Modules/MOD-WIFI-RTL8188/ MOD-WIFI-RTL8188]]]
To connect OLinuXino board with wireless, you could use [https://www.olimex.com/Products/USB-Modules/MOD-WIFI-RTL8188/ MOD-WIFI-RTL8188] dongle. Also you can use another one with the same chip.

[https://www.olimex.com/Products/USB-Modules/MOD-WIFI-RTL8188/ MOD-WIFI-RTL8188] has the following features:
* Has WM-294 module with RTL8188
* Operates in 2.4 GHz frequency bands
* 1x1 MIMO technology improves effective throughput and range over existing 802.11 b/g products
* Data rates: up to 150Mbps
* 802.11e-compatible bursting and I standards BPSK, QPSK, 16 QAM, 64 QAM modulation schemes WEP, TKIP, and AES, WPA, WPA2 hardware encryption schemes
* Standard USB type A connector
* On-board antenna
* 5V/3.3V operation modes via SMD jumper
* 4 test pads for easy tracking the supply, d-, d+, and GND
* PCB: FR-4, 1.00 mm (0,039"), solder mask, silkscreen component print
* Dimensions: 65.15x20.38 mm (2.56x0.80")
----

The kernel module is prebuild. You should just get it loaded and then plug the dongle.
* Load the module:
modprobe 8192cu

* Plug the device and check if it is available:
ifconfig -a

==== RT5370 ====
----
[[File:MOD-WIFI-R5370-ANT-1.jpg|border|thumb|[https://www.olimex.com/Products/USB-Modules/MOD-WIFI-R5370-ANT/ MOD-WIFI-R5370-ANT]]]

To use one this wifi dongle (like [https://www.olimex.com/Products/USB-Modules/MOD-WIFI-R5370/ MOD-WIFI-R5370] or [https://www.olimex.com/Products/USB-Modules/MOD-WIFI-R5370-ANT/ MOD-WIFI-R5370-ANT]) additional files are required.

[https://www.olimex.com/Products/USB-Modules/MOD-WIFI-R5370-ANT/ MOD-WIFI-R5370-ANT] has the following features:

* 2.4GHz with 150Mbps PHY data rate
*External antenna for extended range
*USB 2.0 interface
*Security: WEP/TKIP/AES/WPA/WPA2/WAPI
*CMOS single chip with RF, baseband, and MAC integration
*QoS: WMM & WMM-PS support
*Multiple BSSID support
*Maximum likelihood decoding support
*Cisco CCX 5.0 support
*Low-power usage with advanced power management
----

*First a make new directory and navigate to it. This is where the module will search for files.
mkdir -p /etc/Wireless/RT2870STA
cd /etc/Wireless/RT2870STA/

*Download the files from Github
wget https://raw.githubusercontent.com/SelfDestroyer/RK3188-SOM/olimex/stable-3.0/drivers/net/wireless/rtxx7x/RT2870STA.dat
wget https://raw.githubusercontent.com/SelfDestroyer/RK3188-SOM/olimex/stable-3.0/drivers/net/wireless/rtxx7x/RT2870STACard.dat

*Load module
modprobe rt5370sta

*Plug the device and run:
ifconfig -a
*You should see this:
wlan0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

*Configure your new device:
vi /etc/network/interfaces
*Add configuration. Here we will show DHCP configuration.
iface wlan0 inet dhcp
wpa-ssid "'''your ssid'''"
wpa-psk "'''your password'''"

*Save the configuration and up the interface:
ifup wlan0

*If everything is working and this module to be loaded on boot:
echo rt5370sta >> /etc/modules

== Android ==

RK3188-SOM

2024-05-15T11:43:54Z

LubOlimex: /* How to download the ready Debian image to the NAND memory of RK3188-SOM? */

== Overview ==

[[File:Rk3188-som-resized.png|650px]]

RK3188-SOM board is a very productive small beast compared to the previous Olimex board designs. If we compare RockChip RK3188 and Allwinner A20: RK3188 has 4x Cortex-A9, while A20 only 2x Cortex-A7. It runs at 1.6 GHz vs. the 1.0 GHz frequency of the A20. RK3188 reaches a total of 16000 DMPIS vs. the 3800 DMIPS for the A20 (RK3188 is 4.2 times faster). For comparison, the RaspberryPi has 965 DMIPS (RK3188 is 16.6 times faster).

The RK3188-SOM design has the following features:

*Rockchip RK3188 quad core Cortex-A9 processor, each core typically running at 1.6GHz
*1GB DDR3 memory
*Integrated power management unit
*Optional 4GB NAND flash memory for Linux or Android boot
*Micro SD-card for Linux or Android boot
*Three buttons - POWER, RESET, RECOVERY
*Four LEDs (one for power and three user-programmable)
*UART console pins exposed for serial debug
*Five GPIO connectors 2×20 pins @ 0.05" step
*Dimensions: (3.2×1.8)" ~ (81×56)mm
 

== Ready-to-use Debian images ==
=== Debian for microSD card ===

'''Newest official release (recommended):'''

Direct download of Debian release #2:[https://ftp.olimex.com/RK3188_Images/RK3188_debian_3.0.36_SD_release2.img RK3188-SOM Debian for microSD card - kernel 3.0.36+ - release #2]

In the command line interface of image you are automatically logged as root. The default superuser username/password combination in the GUI (XFCE4) is: olimex/olimex.

Build instructions and links to required files for the latest Debian images might be found below in chapter "Building Linux for RK3188-SOM".

====How to prepare your microSD card with the suitable official Debian image?====
----
In order to download an official Linux image to a microSD card under Windows you can use Win32 Disk Imager: [http://sourceforge.net/projects/win32diskimager/ click here]

1. Download the latest official image suitable for a microSD card from the chapter above

2. Download Win32 Disk Imager from this link.

3. Insert card in your microSD card reader.

4. Launch the software.

5. Point the software to the image

6. Click "write"

Under Linux you can write the image image to the card with dd utility. This is how it can be done:

Let's say the name of the image is "debian_2g.img". It would be downloaded to the microSD card connected to a Linux machine using one of the following commands:

dd bs=4M oflag=sync if=debian_2g.img of=/dev/sdX

or

cp debian_2g.img /dev/sdX

where /dev/sdX is the uSD card as listed by the Linux.

=== Debian for NAND memory ===

'''Newest official release (recommended):'''

Direct download Debian for NAND release #1: [https://ftp.olimex.com/Rockchip_images/nand/debian/RK3188_debian_3.0.36_NAND_release1.img.7z|RK3188-SOM Debian for NAND memory - kernel 3.0.36+ - release #1]

Note that this image is suitable only for RK3188-SOM-4GB boards.

Build instructions and links to required files for the latest Debian images might be found below in chapter "Building Linux for RK3188-SOM"

====How to download the ready Debian image to the NAND memory of RK3188-SOM?====
----

'''IMPORTANT: RK3188-SOM-4GB comes with Debian already pre-loaded on the NAND memory. No need to perform this operation initially.'''

1. You need to download the software tools for your computer provided by Rockchip. If you use Windows download “Rockchip Batch Tool”. If you use Linux use either rkflashkit or upgrade_tool. These are the tools that I recommend but there are a lot of tools available. Get the Rockchip batch tool from here: [https://drive.google.com/file/d/0BwplT87k9SCgRDB4ZGY3SnMzd00/view?usp=sharing Rockchip Batch Tool]

For Windows:

2. Install the drivers that allows your computer to recognize the board (that is already set in bootloader mode) connected to it. The installer is called "Rockchip Driver Assistant" – download it here: [https://drive.google.com/file/d/0BwplT87k9SCgbkdXX1ByUW1RSW8/view?usp=sharing Rockchip Driver Assistant]

3. You need to download and extract the latest image suitable for the NAND from our wiki. It is available as a direct download here: [https://ftp.olimex.com/RK3188_Images/RK3188_debian_3.0.36_NAND_release1.img|RK3188 Debian 3.0.36 for NAND memory]

4. You need enter bootloader mode with the board to be able to establish connection between the board and the software provided by Rockchip. You would also need a mini USB cable. To enter bootloader mode you need to press and hold down the recovery button before powering the board (then connect the board to the PC via the mini USB cable). After the board is powered you can release the button.

5. Start the tool for uploading the firmware and point it to the extracted image.

6. Click button "Upgrade".

7. Test with a serial cable.

== Ready-to-use Android images ==
TODO

== Documents ==

[https://www.olimex.com/Products/SOM/RK3188/RK3188-SOM/resources/RK3188-SOM-UM.pdf OLIMEX RK3188-SOM user's manual]

[https://www.olimex.com/Products/SOM/RK3188/RK3188-SOM-EVB/resources/RK3188-SOM-EVB-UM.pdf OLIMEX RK3188-SOM-EVB user's manual]

[https://github.com/OLIMEX/OLINUXINO/raw/master/HARDWARE/RK3188-PDFs/Rockchip%20RK3188%20datasheet%20V1.0.pdf Processor (Rockchip RK3188) datasheet in pdf format]

[https://www.olimex.com/Products/SOM/RK3188/RK3188-SOM/resources/RK3188_SOM_GPIOs.pdf RK3188-SOM connectors' pinout and GPIO table]

=== CAD files ===

RK3188-SOM is considered commercial, proprietary design. The board file is not available to the customer. A pdf extracted from the original schematic is available at GitHub: [https://github.com/OLIMEX/SOM/tree/master/RK3188/RK3188-SOM RK3188-SOM schematics]

RK3188-SOM-EVB is considered Open Source Hardware, Eagle CAD files are available also at GitHub: [https://github.com/OLIMEX/SOM/tree/master/RK3188/RK3188-EVB RK3188-SOM-EVB sources]

The CAD product used to design OLinuXino is Eagle and you can download evaluation free version from their [http://www.cadsoftusa.com/ web site]. The evaluation version allows you to inspect the schematic and the board file sources.

==Board Layout==

[[File:Rk3188-som-resized-TOP-NAMED.png|650px]]

[[File:Rk3188-som-resized-BOTTOM-NAMED.png|650px]]

== Building Linux for RK3188-SOM ==
=== Building the parameter file ===
----
The parameter file describes many board parameters as firmware version, machine id, manufacturer name, etc.

For the user the most important parameter is '''CMDLINE'''. This is the command that is passed to the kernel. It looks something like this:
CMDLINE:console=ttyFIQ0,115200 console=tty0 root=/dev/mmcblk0p1 rw rootfstype=ext4 init=/sbin/init initrd=0x62000000,0x00800000 \
mtdparts=rk29xxnand:0x00008000@0x00002000(boot),-@0x0000A000(linuxroot)

Define serial port at 115200:
console=ttyFIQ0,115200

Define location of the rootfs:
root=/dev/mmcblk0p1

Define rootfs file system as ext4:
rootfstype=ext4

Define the address of the kernel and size:
0x00008000@0x00002000

Define start address of the rootfs:
-@0x0000A000

Additionally, you can set static MAC address with:
mac_addr=xx:xx:xx:xx:xx:xx

Once you're ready with the file, make the parameter image

* Get rkutils:
https://github.com/naobsd/rkutils
cd rkutils
gcc rkcrc.c -o rkcrc
If you're getting error try to comment ''''#include <err.h>'''' in ''''rkcrc.c''''

* Encrypt parameter file:
./rkcrc -p you_parameter_file parameter

The parameter file is ready for further use.

=== Building the kernel ===
----
* Fist prepare the toolchain:
apt-get update
apt-get install gcc-4.7-arm-linux-gnueabihf ncurses-dev uboot-mkimage build-essential git

* Get the sources:
git clone -b olimex/stable-3.0 https://github.com/StefanMavrodiev/RK3188-SOM.git

* Get the default configuration:
cd RK3188-SOM/
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- '''olimex_rk3188_defconfig'''

* You can modify defconfig with (for additional modules):
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- menuconfig

'''Note!''' The default config will set hdmi to 1080p. You can change it from:
Device Drivers --->
Graphics support --->
<*> Frame buffer support for Rockchip --->
LCD Panel Select --->
'''''Choose one of the following:'''''
HDMI framebuffer size and timing is 1080p <--- '''Set HDMI to 1080p'''
HDMI framebuffer size and timing is 720p <--- '''Set HDMI to 720p'''
HDMI framebuffer size and timing is 480p <--- '''Set HDMI to 480p'''
RGB AT070TN90 <--- [https://www.olimex.com/Products/OLinuXino/LCD/LCD-OLinuXino-7/open-source-hardware LCD-OLinuXino-7]
RGB AR010H05N <--- [https://www.olimex.com/Products/OLinuXino/LCD/LCD-OLinuXino-10/open-source-hardware LCD-OLinuXino-10]
RGB BT043DCNNHHP <--- [https://www.olimex.com/Products/OLinuXino/LCD/LCD-OLinuXino-4.3TS/open-source-hardware LCD-OLinuXino-4.3TS]

* Build the kernel:
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- -j4 kernel.img
After the build is finish you will have '''RK3188-SOM/kernel.img''' and '''RK3188-SOM/arch/arm/boot/Image'''. The first one can be uploaded to the kernel partition (if you have one). The second file is raw binary. It can be combined with ramdisk to get boot.img.

* Generate ramdisk
cd ../
git clone https://github.com/radxa/initrd.git
cd initrd/
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- -j4
cd ../

* Make mkbootimg
git clone https://github.com/neo-technologies/rockchip-mkbootimg.git
cd rockchip-mkbootimg
make
make install
cd ../

* Make boot.img
mkbootimg --kernel RK3188-SOM/arch/arm/boot/Image --ramdisk initrd.img -o boot.img

=== Creating the root filesystem ===
==== Debian Wheezy ====
----
In this post we will explain how you can create your own Debian rootfs with pre-installed packages of your choice, which to allow tiny Linux images to be created. All steps below should work on any Debian host (Debian/Ubuntu etc) and are verified with Ubuntu 12.04LTS. First of all you need to install the support packages on your pc:

* Install the needed packages:
sudo apt-get install qemu-user-static debootstrap binfmt-support

* Define some variables:
targetdir=rootfs
distro=wheezy

* Build first stage:
mkdir $targetdir
sudo debootstrap --arch=armhf --foreign $distro $targetdir

* Copy needed files from host to the target:
sudo cp /usr/bin/qemu-arm-static $targetdir/usr/bin/
sudo cp /etc/resolv.conf $targetdir/etc

We should now have a minimal Debian Rootfs.
* Login into the new filesystem:
sudo chroot $targetdir

* Inside the chroot we need to set up the environment again:
distro=wheezy
export LANG=C

* Now we would run the setup for the second stage of debootstrap needs to run install the packages downloaded earlier
/debootstrap/debootstrap --second-stage

* Once the package installation has finished, setup some support files and apt configuration.
cat <<EOT > /etc/apt/sources.list
deb http://ftp.uk.debian.org/debian $distro main contrib non-free
deb-src http://ftp.uk.debian.org/debian $distro main contrib non-free
deb http://ftp.uk.debian.org/debian $distro-updates main contrib non-free
deb-src http://ftp.uk.debian.org/debian $distro-updates main contrib non-free<
deb http://security.debian.org/debian-security $distro/updates main contrib non-free
deb-src http://security.debian.org/debian-security $distro/updates main contrib non-free

EOT

* Update Debian package database:
apt-get update

* Set up locales dpkg scripts since it tends to complain otherwise; note in Debian Jessie you will also need to install the dialog package as well:
apt-get install locales dialog sudo
dpkg-reconfigure locales

* Fix permission for sudo:
chmod u+s /usr/bin/sudo

* Fix ownership of man forlder
chown -R man /var/cache/man

* Install some useful packages inside the chroot:
apt-get install openssh-server ntpdate

* Set a root password so you can login:
passwd

* Build a basic network interface file:
vi /etc/network/interfaces
Add the following to get static ip:
allow-hotplug eth0
iface eth0 inet static
address 192.168.1.254
netmask 255.255.255.248
gateway 192.168.1.1
Or if you want dhcp
allow-hotplug eth0
iface eth0 inet dhcp

Note: Your board will be accessible over SSH on IP address defined above!

* Set the hostname
echo '''myhost'''> /etc/hostname
echo "127.0.0.1 '''myhost'''" >> /etc/hosts

* Enable the serial console, Debian sysvinit way
echo T0:2345:respawn:/sbin/getty -L ttyFIQ0 115200 vt100 >> /etc/inittab

This way you'll get login prompt at startup. By default you cannot login as root. To do this you should make another user, add him to the sudo group, login at startup and then login as root. To skip all this replace the line above with:
echo T0:2345:respawn:/sbin/getty -L ttyFIQ0 -a root 115200 vt100 >> /etc/inittab

* We are done inside the chroot, so quit the chroot shell
exit

* Tidy up the support files
sudo rm $targetdir/etc/resolv.conf
sudo rm $targetdir/usr/bin/qemu-arm-static

===== Installing X =====
----
You cannot run X as root (actually it's possible, but it's a bad practice), so you have to add new user to run X.

* Edit default useradd settings
vi /etc/default/useradd
Modify '''SHELL''' variable:
SHELL=/bin/bash

* Add new user
useradd '''myuser'''

* Add the user to the sudo group
adduser '''myuser''' sudo

* Make home folder
mkdir /home/'''myuser'''
chown -R '''myuser''':'''myuser''' /home/'''myuser'''

* Install xfce4 and lightdm
apt-get update
apt-get install lightdm xfce4

* Modify lightdm configuration to enable autologin:
vi /etc/lightdm/lightdm.conf
autologin-user='''myuser'''
autologin-user-timeout=0
Make sure that the right lines are uncommented. If you don't want autologin just skip the step above.

* Reboot the system
reboot
After the system loads, you should see the default desktop of xfce4.

==== Ubuntu ====
----

You can download prebuild rootfs from [http://releases.linaro.org/ linaro] site or you can build it yourself.

===== Prebuild linaro images =====
----

You can download prebuild images from https://releases.linaro.org/.
In most cases the builds are separated in:
*'''nano'''
*'''developer'''
*'''server'''
*'''alip'''

You can read additional information from [https://wiki.linaro.org/Platform/DevPlatform/Rootfs here].

In this tutorial we will build Ubuntu 14.10 ALIP rootfs.

* Make empty image file:
dd if=/dev/zero of=linaro_alip_rootfs.img bs=1M count=1024

* Format the new image file:
mkfs.ext4 -F -L linuxroot linaro_alip_rootfs.img

* Create mount point:
mkdir mnt
mount -o loop linaro_alip_rootfs.img ./mnt

* Download prebuild image:
wget https://releases.linaro.org/14.10/ubuntu/trusty-images/alip/linaro-trusty-alip-20141024-684.tar.gz

* Make sure that the archive is downloaded:
md5sum linaro-trusty-alip-20141024-684.tar.gz

* Extract is into the mounted image file:
tar -zxvf linaro-trusty-alip-20141024-684.tar.gz
mv binary/* ./mnt

* Copy any modules that are generated with the kernel:
cp -rvf /'''path/to/modules'''/lib/modules ./mnt/lib/

* Chroot into the new rootfs:
cp /usr/bin/qemu-arm-static ./mnt/usr/bin
cp /etc/resolv.conf ./mnt/etc
chroot ./mnt

* Update repository
apt-get update
'''Note!''' If you have a problem with the update, try changing '''sources.list''' to:
deb http://old-releases.ubuntu.com/ubuntu/ raring main universe restricted multiverse
deb-src http://old-releases.ubuntu.com/ubuntu/ raring main universe restricted multiverse
deb http://old-releases.ubuntu.com/ubuntu/ raring-security main universe restricted multiverse
deb-src http://old-releases.ubuntu.com/ubuntu/ raring-security main universe restricted multiverse
deb http://old-releases.ubuntu.com/ubuntu/ raring-updates main universe restricted multiverse
deb-src http://old-releases.ubuntu.com/ubuntu/ raring-updates main universe restricted multiverse
deb http://old-releases.ubuntu.com/ubuntu/ raring-backports main restricted universe multiverse
deb-src http://old-releases.ubuntu.com/ubuntu/ raring-backports main restricted universe multiverse
deb http://old-releases.ubuntu.com/ubuntu/ raring-proposed main restricted universe multiverse
deb-src http://old-releases.ubuntu.com/ubuntu/ raring-proposed main restricted universe multiverse

* Install some useful packages:
apt-get install ssh nano wpasupplicant wireless-tools

* Set root password:
passwd

Linaro prebuild images comes with default use '''linaro'''.
* Set password for user:
passwd linaro

* Add '''linaro''' to sudo group:
adduser linaro sudo

* Configure network. Create new file for loopback, wlan and eth device:
vi /etc/network/interfaces.d/lo
Inside paste:
auto lo
iface lo inet loopback

Do the same for eth:
vi /etc/network/interfaces.d/eth
If you're using dhcp:
auto eth0
iface eth0 inet dhcp
Or for static ip:
auto eth0
iface eth0 inet static
address <your.ip.here>
netmask <your.netmask.here>
gateway <your.gateway.here>

And another for wireless devices:
vi /etc/network/interfaces.d/wlan
auto wlan0
iface lo inet dhcp
wpa-ssid <your.router.ssid>
wpa-pak <your.ssid.password>

'''Note!''' All connections are '''auto'''. If you don't want to use them all the time remove '''auto''' line.

You can do some additional work before exit.
When you are ready to exit from the target filesystem:
exit

Your rootfs is ready. The next step is to create image for nand or sdcard.

===== Manual build using debootstrap =====
----
The procedure is almost identical to the one used for the Debin image.

* First of all you need to install the support packages on your pc
sudo apt-get install qemu-user-static debootstrap binfmt-support ubuntu-archive-keyring

* We will build latest trusty Ubuntu image:
targetdir=ubuntu
distro=trusty

* Now we will build first stage of Ubuntu rootfs:
mkdir $targetdir
sudo debootstrap --arch=armhf --keyring=/usr/share/keyrings/ubuntu-archive-keyring.gpg --foreign $distro $targetdir

* Login into the new filesystem
sudo cp /usr/bin/qemu-arm-static $targetdir/usr/bin/
sudo cp /etc/resolv.conf $targetdir/etc
sudo chroot $targetdir

* Inside the chroot we need to set up the environment again
distro=trusty
export LANG=C

* Now we are setup the second stage of debootstrap needs to run install the packages downloaded earlier
/debootstrap/debootstrap --second-stage

* Configure apt-sources:
cat <<EOT > /etc/apt/sources.list
###### Ubuntu Main Repos
deb http://ports.ubuntu.com/ubuntu-ports/ $distro main restricted universe multiverse
deb-src http://ports.ubuntu.com/ubuntu-ports/ $distro main restricted universe multiverse
###### Ubuntu Update Repos
deb http://ports.ubuntu.com/ubuntu-ports/ $distro-security main restricted universe multiverse
deb http://ports.ubuntu.com/ubuntu-ports/ $distro-updates main restricted universe multiverse
deb-src http://ports.ubuntu.com/ubuntu-ports/ $distro-security main restricted universe multiverse
deb-src http://ports.ubuntu.com/ubuntu-ports/ $distro-updates main restricted universe multiverse
EOT

* Update Ubuntu package database:
apt-get update

* Set a root password so you can login
passwd

* Set the hostname
echo '''myhost'''> /etc/hostname
echo "127.0.0.1 '''myhost'''" >> /etc/hosts

* Build a basic network interface file so that the board will DHCP on eth0
echo <<EOT >> /etc/network/interfaces
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet dhcp
EOT

* Enable the serial console, Debian sysvinit way
echo T0:2345:respawn:/sbin/getty -L ttyFIQ0 115200 vt100 >> /etc/inittab

This way you'll get login prompt at startup. By default you cannot login as root. To do this you should make another user,
add him to the sudo group, login at startup and then login as root. To skip all this replace the line above with:
echo T0:2345:respawn:/sbin/getty -L ttyFIQ0 -a root 115200 vt100 >> /etc/inittab

* We are done inside the chroot, so quit the chroot shell
exit

* Tidy up the support files
sudo rm $targetdir/etc/resolv.conf
sudo rm $targetdir/usr/bin/qemu-arm-static

==== Make rootfs image ====
----

Once you are ready with the rootfs you can make image file. Later it can be used for NAND or SD image. Go to parent directory of you rootfs.

* See how big the image should be:
# du -khs <roofs_folder>
For example this will return 600MB. So we will make 1GB image.

* Make empty image:
# dd if=/dev/zero of=rootfs.img bs=1M count=1024

* Format the image:
# mkfs.ex4 -F -L linuxroot rootfs.img

* Mount the image:
# mount -o loop rootfs.img /mnt

* Copy rootfs files into the image:
# cp -prf <root_folder>/* /mnt/
''''Note!''' Use -p option to keep the permissions for the files and folders.

* Unmount the image:
# umount /mnt

=== Booting from NAND ===
----
* Get rk-tools:
git clone https://github.com/goodybag/rk-tools
cd rk-tools
make

*You will need the following files:
**bootloader --> This is RockChip RK3188Loader
**[[#Building parameter file|parameter]] --> Parameter file with crc encryption
**[[#Building kernel|boot]] --> Kernel with ramdisk compiled as shown here
**[[#Creating root filesystem|linux]] --> Rootfs image file
'''CMDLINE''' in parameter file should look something like this:
CMDLINE:console=ttyFIQ0,115200 console=tty0 root=/dev/block/mtd/by-name/linuxroot rw rootfstype=ext4 init=/sbin/init initrd=0x62000000,0x00800000 mtdparts=rk29xxnand:0x00008000@0x00002000(boot),-@0x0000A000(linuxroot)

* Copy all files in '''rk-tools''' folder

* Edit '''package-file'''. It should be:
#nano package-file

# NAME Relative path
#
#HWDEF HWDEF
package-file package-file
bootloader RK3188Loader
parameter parameter
boot boot.img
linuxroot rootfs.img
backup RESERVED
update-script update-script
recover-script recover-script

* Pack the image:
./afptool -pack . update_tmp.img

* Update the image:
./img_maker -rk31 RK3188Loader 1 0 0 update_tmp.img update.img

The image should be ready. What's left is flashing the image.

*Important: to flash the image the board needs to be in bootloader mode. To enter bootloader mode you need to press and hold down the recovery button before connecting the board to the PC. After the connection is established you can release the button.

 

=== Booting from SD-card ===
----
You'll need at least 512MB sd-card. Depending on rootfs needed size can grow to 4GB.

*You will need the following files:
**sdboot_rk3188.img --> RK3188Loader for booting from SDcard
**[[#Building parameter file|parameter]] --> Parameter file with crc encryption
**[[#Building kernel|boot]] --> Kernel with ramdisk compiled as shown here
**[[#Creating root filesystem|linux]] --> Rootfs image file

'''CMDLINE''' in parameter file should look something like this:
CMDLINE:console=ttyFIQ0,115200 console=tty0 root=/dev/mmcblk0p1 rw rootfstype=ext4 init=/sbin/init initrd=0x62000000,0x00800000 mtdparts=rk29xxnand:0x00008000@0x00002000(boot),-@0x0000A000(linuxroot)

Insert sd-card. Lets say that your device is '''/dev/sdc'''.

* Write Rockchip loader:
dd if=sdboot_rk3188.img of=/dev/sdc conv=sync,fsync

* Write parameter file:
dd if=parameter.img of=/dev/sdc conv=sync,fsync seek=$((0x2000))

* Write kernel:
dd if=boot.img of=/dev/sdc conv=sync,fsync seek=$((0x2000+0x2000))

* Write rootfs:
dd if=rootfs.img of=/dev/sdc conv=sync,fsync seek=$((0x2000+0xA000))

You can do this also on image file:
dd if=/dev/zero of=sd.img bs=1M count=1024
If 1GB is not enough increase count number.

* Write Rockchip loader:
dd if=sdboot_rk3188.img of=sd.img conv=sync,fsync

* Write parameter file:
dd if=parameter.img of=sd.img conv=sync,fsync seek=$((0x2000))

* Write kernel:
dd if=boot.img of=sd.img conv=sync,fsync seek=$((0x2000+0x2000))

* Write rootfs:
dd if=rootfs.img of=sd.img conv=sync,fsync seek=$((0x2000+0xA000))

* Format image:
fdisk sd.img << EOF
n
p
1
49152

w
EOF

=== Calibrate touchscreen ===
If you want to use LCD panel with touchscreen, you should perform a screen calibration.

==== Calibrate using tslib ====
----

* Install the required packages:
apt-get update
apt-get install xorg-dev xserver-xorg-dev x11proto-core-dev git automake make libtool

* Download tslib:
git clone https://github.com/kergoth/tslib.git
cd tslib

* Download patch:
cd plugin
wget https://dl.dropbox.com/u/40057/patches/input-raw.c
cd ../

* Compile the library:
autoreconf -vi
./configure --prefix=/usr
make
make install
ldconfig

* Modify tslib configuration
vi /usr/etc/ts.conf
Uncomment the following line:
module_raw input

* Export tslib needed variables:
export TSLIB_TSEVENTTYPE=raw
export TSLIB_CONSOLEDEVICE=none
export TSLIB_FBDEVICE=/dev/fb0
export TSLIB_TSDEVICE=/dev/input/event0
export TSLIB_CALIBFILE=/usr/etc/pointercal
export TSLIB_CONFFILE=/usr/etc/ts.conf
export TSLIB_PLUGINDIR=/usr/lib/ts

* Now tslib is working but still it should be set as default driver in the X:
wget http://ftp.de.debian.org/debian/pool/main/x/xf86-input-tslib/xf86-input-tslib_0.0.6.orig.tar.gz
tar zxfv xf86-input-tslib_0.0.6.orig.tar.gz
cd xf86-input-tslib-0.0.6/
Replace tslib.c file with patched one:
cd src/
rm -f tslib.c
wget https://dl.dropbox.com/u/40057/patches/tslib.c
cd ..
Build and install package:
./configure --prefix=/usr
make
make install

* Add tslib configuration:
cd /usr/share/X11/xorg.conf.d/
Make new file:
nano 20-touchscreen.conf
Add the following text inside:
Section "InputClass"
Identifier "AR1020"
MatchDevicePath "/dev/input/event0"
Driver "tslib"
Option "Device" "/dev/input/event0"
Option "ScreenNumber" "0"
Option "Rotate" "NONE"
Option "Width" "'''800'''"
Option "Height" "'''480'''"
Option "SendCoreEvents" "yes"
Option "Type" "touchscreen"
EndSection
Note! Resolution in this example is set for 7 inch LCD.

* Do the actual calibration:
service lightdm stop
ts_calibrate
service lightdm start
After lightdm start you could check if everything is running smoothly.

* Save tslib variables:
vi /etc/environment
Paste the following:
TSLIB_TSEVENTTYPE=raw
TSLIB_CONSOLEDEVICE=none
TSLIB_FBDEVICE=/dev/fb0
TSLIB_TSDEVICE=/dev/input/event0
TSLIB_CALIBFILE=/etc/pointercal
TSLIB_CONFFILE=/usr/etc/ts.conf
TSLIB_PLUGINDIR=/usr/lib/ts

If you change the LCD panel run ts_calibrate to configure touchscreen for the new LCD.

==== Calibrate using AR1021 driver ====
TODO

=== Enabling wireless modules ===
==== RTL8188CUS ====
----
[[File:MOD-WIFI-RTL8188-1.jpg|thumb|[https://www.olimex.com/Products/USB-Modules/MOD-WIFI-RTL8188/ MOD-WIFI-RTL8188]]]
To connect OLinuXino board with wireless, you could use [https://www.olimex.com/Products/USB-Modules/MOD-WIFI-RTL8188/ MOD-WIFI-RTL8188] dongle. Also you can use another one with the same chip.

[https://www.olimex.com/Products/USB-Modules/MOD-WIFI-RTL8188/ MOD-WIFI-RTL8188] has the following features:
* Has WM-294 module with RTL8188
* Operates in 2.4 GHz frequency bands
* 1x1 MIMO technology improves effective throughput and range over existing 802.11 b/g products
* Data rates: up to 150Mbps
* 802.11e-compatible bursting and I standards BPSK, QPSK, 16 QAM, 64 QAM modulation schemes WEP, TKIP, and AES, WPA, WPA2 hardware encryption schemes
* Standard USB type A connector
* On-board antenna
* 5V/3.3V operation modes via SMD jumper
* 4 test pads for easy tracking the supply, d-, d+, and GND
* PCB: FR-4, 1.00 mm (0,039"), solder mask, silkscreen component print
* Dimensions: 65.15x20.38 mm (2.56x0.80")
----

The kernel module is prebuild. You should just get it loaded and then plug the dongle.
* Load the module:
modprobe 8192cu

* Plug the device and check if it is available:
ifconfig -a

==== RT5370 ====
----
[[File:MOD-WIFI-R5370-ANT-1.jpg|border|thumb|[https://www.olimex.com/Products/USB-Modules/MOD-WIFI-R5370-ANT/ MOD-WIFI-R5370-ANT]]]

To use one this wifi dongle (like [https://www.olimex.com/Products/USB-Modules/MOD-WIFI-R5370/ MOD-WIFI-R5370] or [https://www.olimex.com/Products/USB-Modules/MOD-WIFI-R5370-ANT/ MOD-WIFI-R5370-ANT]) additional files are required.

[https://www.olimex.com/Products/USB-Modules/MOD-WIFI-R5370-ANT/ MOD-WIFI-R5370-ANT] has the following features:

* 2.4GHz with 150Mbps PHY data rate
*External antenna for extended range
*USB 2.0 interface
*Security: WEP/TKIP/AES/WPA/WPA2/WAPI
*CMOS single chip with RF, baseband, and MAC integration
*QoS: WMM & WMM-PS support
*Multiple BSSID support
*Maximum likelihood decoding support
*Cisco CCX 5.0 support
*Low-power usage with advanced power management
----

*First a make new directory and navigate to it. This is where the module will search for files.
mkdir -p /etc/Wireless/RT2870STA
cd /etc/Wireless/RT2870STA/

*Download the files from Github
wget https://raw.githubusercontent.com/SelfDestroyer/RK3188-SOM/olimex/stable-3.0/drivers/net/wireless/rtxx7x/RT2870STA.dat
wget https://raw.githubusercontent.com/SelfDestroyer/RK3188-SOM/olimex/stable-3.0/drivers/net/wireless/rtxx7x/RT2870STACard.dat

*Load module
modprobe rt5370sta

*Plug the device and run:
ifconfig -a
*You should see this:
wlan0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

*Configure your new device:
vi /etc/network/interfaces
*Add configuration. Here we will show DHCP configuration.
iface wlan0 inet dhcp
wpa-ssid "'''your ssid'''"
wpa-psk "'''your password'''"

*Save the configuration and up the interface:
ifup wlan0

*If everything is working and this module to be loaded on boot:
echo rt5370sta >> /etc/modules

== Android ==

RK3188-SOM

2024-05-15T11:10:57Z

LubOlimex: /* Debian for microSD card */

== Overview ==

[[File:Rk3188-som-resized.png|650px]]

RK3188-SOM board is a very productive small beast compared to the previous Olimex board designs. If we compare RockChip RK3188 and Allwinner A20: RK3188 has 4x Cortex-A9, while A20 only 2x Cortex-A7. It runs at 1.6 GHz vs. the 1.0 GHz frequency of the A20. RK3188 reaches a total of 16000 DMPIS vs. the 3800 DMIPS for the A20 (RK3188 is 4.2 times faster). For comparison, the RaspberryPi has 965 DMIPS (RK3188 is 16.6 times faster).

The RK3188-SOM design has the following features:

*Rockchip RK3188 quad core Cortex-A9 processor, each core typically running at 1.6GHz
*1GB DDR3 memory
*Integrated power management unit
*Optional 4GB NAND flash memory for Linux or Android boot
*Micro SD-card for Linux or Android boot
*Three buttons - POWER, RESET, RECOVERY
*Four LEDs (one for power and three user-programmable)
*UART console pins exposed for serial debug
*Five GPIO connectors 2×20 pins @ 0.05" step
*Dimensions: (3.2×1.8)" ~ (81×56)mm
 

== Ready-to-use Debian images ==
=== Debian for microSD card ===

'''Newest official release (recommended):'''

Direct download of Debian release #2:[https://ftp.olimex.com/RK3188_Images/RK3188_debian_3.0.36_SD_release2.img RK3188-SOM Debian for microSD card - kernel 3.0.36+ - release #2]

In the command line interface of image you are automatically logged as root. The default superuser username/password combination in the GUI (XFCE4) is: olimex/olimex.

Build instructions and links to required files for the latest Debian images might be found below in chapter "Building Linux for RK3188-SOM".

====How to prepare your microSD card with the suitable official Debian image?====
----
In order to download an official Linux image to a microSD card under Windows you can use Win32 Disk Imager: [http://sourceforge.net/projects/win32diskimager/ click here]

1. Download the latest official image suitable for a microSD card from the chapter above

2. Download Win32 Disk Imager from this link.

3. Insert card in your microSD card reader.

4. Launch the software.

5. Point the software to the image

6. Click "write"

Under Linux you can write the image image to the card with dd utility. This is how it can be done:

Let's say the name of the image is "debian_2g.img". It would be downloaded to the microSD card connected to a Linux machine using one of the following commands:

dd bs=4M oflag=sync if=debian_2g.img of=/dev/sdX

or

cp debian_2g.img /dev/sdX

where /dev/sdX is the uSD card as listed by the Linux.

=== Debian for NAND memory ===

'''Newest official release (recommended):'''

Direct download Debian for NAND release #1: [https://ftp.olimex.com/Rockchip_images/nand/debian/RK3188_debian_3.0.36_NAND_release1.img.7z|RK3188-SOM Debian for NAND memory - kernel 3.0.36+ - release #1]

Note that this image is suitable only for RK3188-SOM-4GB boards.

Build instructions and links to required files for the latest Debian images might be found below in chapter "Building Linux for RK3188-SOM"

====How to download the ready Debian image to the NAND memory of RK3188-SOM?====
----

'''IMPORTANT: RK3188-SOM-4GB comes with Debian already pre-loaded on the NAND memory. No need to perform this operation initially.'''

1. You need to download the software tools for your computer provided by Rockchip. If you use Windows download “Rockchip Batch Tool”. If you use Linux use either rkflashkit or upgrade_tool. These are the tools that I recommend but there are a lot of tools available. Get the Rockchip batch tool from here: [https://drive.google.com/file/d/0BwplT87k9SCgRDB4ZGY3SnMzd00/view?usp=sharing Rockchip Batch Tool]

For Windows:

2. Install the drivers that allows your computer to recognize the board (that is already set in bootloader mode) connected to it. The installer is called "Rockchip Driver Assistant" – download it here: [https://drive.google.com/file/d/0BwplT87k9SCgbkdXX1ByUW1RSW8/view?usp=sharing Rockchip Driver Assistant]

3. You need to download and extract the latest image suitable for the NAND from our wiki. It is available as a direct download here: [https://ftp.olimex.com/Rockchip_images/nand/debian/RK3188_debian_3.0.36_NAND_release1.img.7z%7CRK3188-SOM|RK3188 Debian 3.0.36 for NAND memory]

4. You need enter bootloader mode with the board to be able to establish connection between the board and the software provided by Rockchip. You would also need a mini USB cable. To enter bootloader mode you need to press and hold down the recovery button before powering the board (then connect the board to the PC via the mini USB cable). After the board is powered you can release the button.

5. Start the tool for uploading the firmware and point it to the extracted image.

6. Click button "Upgrade".

7. Test with a serial cable.

== Ready-to-use Android images ==
TODO

== Documents ==

[https://www.olimex.com/Products/SOM/RK3188/RK3188-SOM/resources/RK3188-SOM-UM.pdf OLIMEX RK3188-SOM user's manual]

[https://www.olimex.com/Products/SOM/RK3188/RK3188-SOM-EVB/resources/RK3188-SOM-EVB-UM.pdf OLIMEX RK3188-SOM-EVB user's manual]

[https://github.com/OLIMEX/OLINUXINO/raw/master/HARDWARE/RK3188-PDFs/Rockchip%20RK3188%20datasheet%20V1.0.pdf Processor (Rockchip RK3188) datasheet in pdf format]

[https://www.olimex.com/Products/SOM/RK3188/RK3188-SOM/resources/RK3188_SOM_GPIOs.pdf RK3188-SOM connectors' pinout and GPIO table]

=== CAD files ===

RK3188-SOM is considered commercial, proprietary design. The board file is not available to the customer. A pdf extracted from the original schematic is available at GitHub: [https://github.com/OLIMEX/SOM/tree/master/RK3188/RK3188-SOM RK3188-SOM schematics]

RK3188-SOM-EVB is considered Open Source Hardware, Eagle CAD files are available also at GitHub: [https://github.com/OLIMEX/SOM/tree/master/RK3188/RK3188-EVB RK3188-SOM-EVB sources]

The CAD product used to design OLinuXino is Eagle and you can download evaluation free version from their [http://www.cadsoftusa.com/ web site]. The evaluation version allows you to inspect the schematic and the board file sources.

==Board Layout==

[[File:Rk3188-som-resized-TOP-NAMED.png|650px]]

[[File:Rk3188-som-resized-BOTTOM-NAMED.png|650px]]

== Building Linux for RK3188-SOM ==
=== Building the parameter file ===
----
The parameter file describes many board parameters as firmware version, machine id, manufacturer name, etc.

For the user the most important parameter is '''CMDLINE'''. This is the command that is passed to the kernel. It looks something like this:
CMDLINE:console=ttyFIQ0,115200 console=tty0 root=/dev/mmcblk0p1 rw rootfstype=ext4 init=/sbin/init initrd=0x62000000,0x00800000 \
mtdparts=rk29xxnand:0x00008000@0x00002000(boot),-@0x0000A000(linuxroot)

Define serial port at 115200:
console=ttyFIQ0,115200

Define location of the rootfs:
root=/dev/mmcblk0p1

Define rootfs file system as ext4:
rootfstype=ext4

Define the address of the kernel and size:
0x00008000@0x00002000

Define start address of the rootfs:
-@0x0000A000

Additionally, you can set static MAC address with:
mac_addr=xx:xx:xx:xx:xx:xx

Once you're ready with the file, make the parameter image

* Get rkutils:
https://github.com/naobsd/rkutils
cd rkutils
gcc rkcrc.c -o rkcrc
If you're getting error try to comment ''''#include <err.h>'''' in ''''rkcrc.c''''

* Encrypt parameter file:
./rkcrc -p you_parameter_file parameter

The parameter file is ready for further use.

=== Building the kernel ===
----
* Fist prepare the toolchain:
apt-get update
apt-get install gcc-4.7-arm-linux-gnueabihf ncurses-dev uboot-mkimage build-essential git

* Get the sources:
git clone -b olimex/stable-3.0 https://github.com/StefanMavrodiev/RK3188-SOM.git

* Get the default configuration:
cd RK3188-SOM/
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- '''olimex_rk3188_defconfig'''

* You can modify defconfig with (for additional modules):
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- menuconfig

'''Note!''' The default config will set hdmi to 1080p. You can change it from:
Device Drivers --->
Graphics support --->
<*> Frame buffer support for Rockchip --->
LCD Panel Select --->
'''''Choose one of the following:'''''
HDMI framebuffer size and timing is 1080p <--- '''Set HDMI to 1080p'''
HDMI framebuffer size and timing is 720p <--- '''Set HDMI to 720p'''
HDMI framebuffer size and timing is 480p <--- '''Set HDMI to 480p'''
RGB AT070TN90 <--- [https://www.olimex.com/Products/OLinuXino/LCD/LCD-OLinuXino-7/open-source-hardware LCD-OLinuXino-7]
RGB AR010H05N <--- [https://www.olimex.com/Products/OLinuXino/LCD/LCD-OLinuXino-10/open-source-hardware LCD-OLinuXino-10]
RGB BT043DCNNHHP <--- [https://www.olimex.com/Products/OLinuXino/LCD/LCD-OLinuXino-4.3TS/open-source-hardware LCD-OLinuXino-4.3TS]

* Build the kernel:
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- -j4 kernel.img
After the build is finish you will have '''RK3188-SOM/kernel.img''' and '''RK3188-SOM/arch/arm/boot/Image'''. The first one can be uploaded to the kernel partition (if you have one). The second file is raw binary. It can be combined with ramdisk to get boot.img.

* Generate ramdisk
cd ../
git clone https://github.com/radxa/initrd.git
cd initrd/
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- -j4
cd ../

* Make mkbootimg
git clone https://github.com/neo-technologies/rockchip-mkbootimg.git
cd rockchip-mkbootimg
make
make install
cd ../

* Make boot.img
mkbootimg --kernel RK3188-SOM/arch/arm/boot/Image --ramdisk initrd.img -o boot.img

=== Creating the root filesystem ===
==== Debian Wheezy ====
----
In this post we will explain how you can create your own Debian rootfs with pre-installed packages of your choice, which to allow tiny Linux images to be created. All steps below should work on any Debian host (Debian/Ubuntu etc) and are verified with Ubuntu 12.04LTS. First of all you need to install the support packages on your pc:

* Install the needed packages:
sudo apt-get install qemu-user-static debootstrap binfmt-support

* Define some variables:
targetdir=rootfs
distro=wheezy

* Build first stage:
mkdir $targetdir
sudo debootstrap --arch=armhf --foreign $distro $targetdir

* Copy needed files from host to the target:
sudo cp /usr/bin/qemu-arm-static $targetdir/usr/bin/
sudo cp /etc/resolv.conf $targetdir/etc

We should now have a minimal Debian Rootfs.
* Login into the new filesystem:
sudo chroot $targetdir

* Inside the chroot we need to set up the environment again:
distro=wheezy
export LANG=C

* Now we would run the setup for the second stage of debootstrap needs to run install the packages downloaded earlier
/debootstrap/debootstrap --second-stage

* Once the package installation has finished, setup some support files and apt configuration.
cat <<EOT > /etc/apt/sources.list
deb http://ftp.uk.debian.org/debian $distro main contrib non-free
deb-src http://ftp.uk.debian.org/debian $distro main contrib non-free
deb http://ftp.uk.debian.org/debian $distro-updates main contrib non-free
deb-src http://ftp.uk.debian.org/debian $distro-updates main contrib non-free<
deb http://security.debian.org/debian-security $distro/updates main contrib non-free
deb-src http://security.debian.org/debian-security $distro/updates main contrib non-free

EOT

* Update Debian package database:
apt-get update

* Set up locales dpkg scripts since it tends to complain otherwise; note in Debian Jessie you will also need to install the dialog package as well:
apt-get install locales dialog sudo
dpkg-reconfigure locales

* Fix permission for sudo:
chmod u+s /usr/bin/sudo

* Fix ownership of man forlder
chown -R man /var/cache/man

* Install some useful packages inside the chroot:
apt-get install openssh-server ntpdate

* Set a root password so you can login:
passwd

* Build a basic network interface file:
vi /etc/network/interfaces
Add the following to get static ip:
allow-hotplug eth0
iface eth0 inet static
address 192.168.1.254
netmask 255.255.255.248
gateway 192.168.1.1
Or if you want dhcp
allow-hotplug eth0
iface eth0 inet dhcp

Note: Your board will be accessible over SSH on IP address defined above!

* Set the hostname
echo '''myhost'''> /etc/hostname
echo "127.0.0.1 '''myhost'''" >> /etc/hosts

* Enable the serial console, Debian sysvinit way
echo T0:2345:respawn:/sbin/getty -L ttyFIQ0 115200 vt100 >> /etc/inittab

This way you'll get login prompt at startup. By default you cannot login as root. To do this you should make another user, add him to the sudo group, login at startup and then login as root. To skip all this replace the line above with:
echo T0:2345:respawn:/sbin/getty -L ttyFIQ0 -a root 115200 vt100 >> /etc/inittab

* We are done inside the chroot, so quit the chroot shell
exit

* Tidy up the support files
sudo rm $targetdir/etc/resolv.conf
sudo rm $targetdir/usr/bin/qemu-arm-static

===== Installing X =====
----
You cannot run X as root (actually it's possible, but it's a bad practice), so you have to add new user to run X.

* Edit default useradd settings
vi /etc/default/useradd
Modify '''SHELL''' variable:
SHELL=/bin/bash

* Add new user
useradd '''myuser'''

* Add the user to the sudo group
adduser '''myuser''' sudo

* Make home folder
mkdir /home/'''myuser'''
chown -R '''myuser''':'''myuser''' /home/'''myuser'''

* Install xfce4 and lightdm
apt-get update
apt-get install lightdm xfce4

* Modify lightdm configuration to enable autologin:
vi /etc/lightdm/lightdm.conf
autologin-user='''myuser'''
autologin-user-timeout=0
Make sure that the right lines are uncommented. If you don't want autologin just skip the step above.

* Reboot the system
reboot
After the system loads, you should see the default desktop of xfce4.

==== Ubuntu ====
----

You can download prebuild rootfs from [http://releases.linaro.org/ linaro] site or you can build it yourself.

===== Prebuild linaro images =====
----

You can download prebuild images from https://releases.linaro.org/.
In most cases the builds are separated in:
*'''nano'''
*'''developer'''
*'''server'''
*'''alip'''

You can read additional information from [https://wiki.linaro.org/Platform/DevPlatform/Rootfs here].

In this tutorial we will build Ubuntu 14.10 ALIP rootfs.

* Make empty image file:
dd if=/dev/zero of=linaro_alip_rootfs.img bs=1M count=1024

* Format the new image file:
mkfs.ext4 -F -L linuxroot linaro_alip_rootfs.img

* Create mount point:
mkdir mnt
mount -o loop linaro_alip_rootfs.img ./mnt

* Download prebuild image:
wget https://releases.linaro.org/14.10/ubuntu/trusty-images/alip/linaro-trusty-alip-20141024-684.tar.gz

* Make sure that the archive is downloaded:
md5sum linaro-trusty-alip-20141024-684.tar.gz

* Extract is into the mounted image file:
tar -zxvf linaro-trusty-alip-20141024-684.tar.gz
mv binary/* ./mnt

* Copy any modules that are generated with the kernel:
cp -rvf /'''path/to/modules'''/lib/modules ./mnt/lib/

* Chroot into the new rootfs:
cp /usr/bin/qemu-arm-static ./mnt/usr/bin
cp /etc/resolv.conf ./mnt/etc
chroot ./mnt

* Update repository
apt-get update
'''Note!''' If you have a problem with the update, try changing '''sources.list''' to:
deb http://old-releases.ubuntu.com/ubuntu/ raring main universe restricted multiverse
deb-src http://old-releases.ubuntu.com/ubuntu/ raring main universe restricted multiverse
deb http://old-releases.ubuntu.com/ubuntu/ raring-security main universe restricted multiverse
deb-src http://old-releases.ubuntu.com/ubuntu/ raring-security main universe restricted multiverse
deb http://old-releases.ubuntu.com/ubuntu/ raring-updates main universe restricted multiverse
deb-src http://old-releases.ubuntu.com/ubuntu/ raring-updates main universe restricted multiverse
deb http://old-releases.ubuntu.com/ubuntu/ raring-backports main restricted universe multiverse
deb-src http://old-releases.ubuntu.com/ubuntu/ raring-backports main restricted universe multiverse
deb http://old-releases.ubuntu.com/ubuntu/ raring-proposed main restricted universe multiverse
deb-src http://old-releases.ubuntu.com/ubuntu/ raring-proposed main restricted universe multiverse

* Install some useful packages:
apt-get install ssh nano wpasupplicant wireless-tools

* Set root password:
passwd

Linaro prebuild images comes with default use '''linaro'''.
* Set password for user:
passwd linaro

* Add '''linaro''' to sudo group:
adduser linaro sudo

* Configure network. Create new file for loopback, wlan and eth device:
vi /etc/network/interfaces.d/lo
Inside paste:
auto lo
iface lo inet loopback

Do the same for eth:
vi /etc/network/interfaces.d/eth
If you're using dhcp:
auto eth0
iface eth0 inet dhcp
Or for static ip:
auto eth0
iface eth0 inet static
address <your.ip.here>
netmask <your.netmask.here>
gateway <your.gateway.here>

And another for wireless devices:
vi /etc/network/interfaces.d/wlan
auto wlan0
iface lo inet dhcp
wpa-ssid <your.router.ssid>
wpa-pak <your.ssid.password>

'''Note!''' All connections are '''auto'''. If you don't want to use them all the time remove '''auto''' line.

You can do some additional work before exit.
When you are ready to exit from the target filesystem:
exit

Your rootfs is ready. The next step is to create image for nand or sdcard.

===== Manual build using debootstrap =====
----
The procedure is almost identical to the one used for the Debin image.

* First of all you need to install the support packages on your pc
sudo apt-get install qemu-user-static debootstrap binfmt-support ubuntu-archive-keyring

* We will build latest trusty Ubuntu image:
targetdir=ubuntu
distro=trusty

* Now we will build first stage of Ubuntu rootfs:
mkdir $targetdir
sudo debootstrap --arch=armhf --keyring=/usr/share/keyrings/ubuntu-archive-keyring.gpg --foreign $distro $targetdir

* Login into the new filesystem
sudo cp /usr/bin/qemu-arm-static $targetdir/usr/bin/
sudo cp /etc/resolv.conf $targetdir/etc
sudo chroot $targetdir

* Inside the chroot we need to set up the environment again
distro=trusty
export LANG=C

* Now we are setup the second stage of debootstrap needs to run install the packages downloaded earlier
/debootstrap/debootstrap --second-stage

* Configure apt-sources:
cat <<EOT > /etc/apt/sources.list
###### Ubuntu Main Repos
deb http://ports.ubuntu.com/ubuntu-ports/ $distro main restricted universe multiverse
deb-src http://ports.ubuntu.com/ubuntu-ports/ $distro main restricted universe multiverse
###### Ubuntu Update Repos
deb http://ports.ubuntu.com/ubuntu-ports/ $distro-security main restricted universe multiverse
deb http://ports.ubuntu.com/ubuntu-ports/ $distro-updates main restricted universe multiverse
deb-src http://ports.ubuntu.com/ubuntu-ports/ $distro-security main restricted universe multiverse
deb-src http://ports.ubuntu.com/ubuntu-ports/ $distro-updates main restricted universe multiverse
EOT

* Update Ubuntu package database:
apt-get update

* Set a root password so you can login
passwd

* Set the hostname
echo '''myhost'''> /etc/hostname
echo "127.0.0.1 '''myhost'''" >> /etc/hosts

* Build a basic network interface file so that the board will DHCP on eth0
echo <<EOT >> /etc/network/interfaces
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet dhcp
EOT

* Enable the serial console, Debian sysvinit way
echo T0:2345:respawn:/sbin/getty -L ttyFIQ0 115200 vt100 >> /etc/inittab

This way you'll get login prompt at startup. By default you cannot login as root. To do this you should make another user,
add him to the sudo group, login at startup and then login as root. To skip all this replace the line above with:
echo T0:2345:respawn:/sbin/getty -L ttyFIQ0 -a root 115200 vt100 >> /etc/inittab

* We are done inside the chroot, so quit the chroot shell
exit

* Tidy up the support files
sudo rm $targetdir/etc/resolv.conf
sudo rm $targetdir/usr/bin/qemu-arm-static

==== Make rootfs image ====
----

Once you are ready with the rootfs you can make image file. Later it can be used for NAND or SD image. Go to parent directory of you rootfs.

* See how big the image should be:
# du -khs <roofs_folder>
For example this will return 600MB. So we will make 1GB image.

* Make empty image:
# dd if=/dev/zero of=rootfs.img bs=1M count=1024

* Format the image:
# mkfs.ex4 -F -L linuxroot rootfs.img

* Mount the image:
# mount -o loop rootfs.img /mnt

* Copy rootfs files into the image:
# cp -prf <root_folder>/* /mnt/
''''Note!''' Use -p option to keep the permissions for the files and folders.

* Unmount the image:
# umount /mnt

=== Booting from NAND ===
----
* Get rk-tools:
git clone https://github.com/goodybag/rk-tools
cd rk-tools
make

*You will need the following files:
**bootloader --> This is RockChip RK3188Loader
**[[#Building parameter file|parameter]] --> Parameter file with crc encryption
**[[#Building kernel|boot]] --> Kernel with ramdisk compiled as shown here
**[[#Creating root filesystem|linux]] --> Rootfs image file
'''CMDLINE''' in parameter file should look something like this:
CMDLINE:console=ttyFIQ0,115200 console=tty0 root=/dev/block/mtd/by-name/linuxroot rw rootfstype=ext4 init=/sbin/init initrd=0x62000000,0x00800000 mtdparts=rk29xxnand:0x00008000@0x00002000(boot),-@0x0000A000(linuxroot)

* Copy all files in '''rk-tools''' folder

* Edit '''package-file'''. It should be:
#nano package-file

# NAME Relative path
#
#HWDEF HWDEF
package-file package-file
bootloader RK3188Loader
parameter parameter
boot boot.img
linuxroot rootfs.img
backup RESERVED
update-script update-script
recover-script recover-script

* Pack the image:
./afptool -pack . update_tmp.img

* Update the image:
./img_maker -rk31 RK3188Loader 1 0 0 update_tmp.img update.img

The image should be ready. What's left is flashing the image.

*Important: to flash the image the board needs to be in bootloader mode. To enter bootloader mode you need to press and hold down the recovery button before connecting the board to the PC. After the connection is established you can release the button.

 

=== Booting from SD-card ===
----
You'll need at least 512MB sd-card. Depending on rootfs needed size can grow to 4GB.

*You will need the following files:
**sdboot_rk3188.img --> RK3188Loader for booting from SDcard
**[[#Building parameter file|parameter]] --> Parameter file with crc encryption
**[[#Building kernel|boot]] --> Kernel with ramdisk compiled as shown here
**[[#Creating root filesystem|linux]] --> Rootfs image file

'''CMDLINE''' in parameter file should look something like this:
CMDLINE:console=ttyFIQ0,115200 console=tty0 root=/dev/mmcblk0p1 rw rootfstype=ext4 init=/sbin/init initrd=0x62000000,0x00800000 mtdparts=rk29xxnand:0x00008000@0x00002000(boot),-@0x0000A000(linuxroot)

Insert sd-card. Lets say that your device is '''/dev/sdc'''.

* Write Rockchip loader:
dd if=sdboot_rk3188.img of=/dev/sdc conv=sync,fsync

* Write parameter file:
dd if=parameter.img of=/dev/sdc conv=sync,fsync seek=$((0x2000))

* Write kernel:
dd if=boot.img of=/dev/sdc conv=sync,fsync seek=$((0x2000+0x2000))

* Write rootfs:
dd if=rootfs.img of=/dev/sdc conv=sync,fsync seek=$((0x2000+0xA000))

You can do this also on image file:
dd if=/dev/zero of=sd.img bs=1M count=1024
If 1GB is not enough increase count number.

* Write Rockchip loader:
dd if=sdboot_rk3188.img of=sd.img conv=sync,fsync

* Write parameter file:
dd if=parameter.img of=sd.img conv=sync,fsync seek=$((0x2000))

* Write kernel:
dd if=boot.img of=sd.img conv=sync,fsync seek=$((0x2000+0x2000))

* Write rootfs:
dd if=rootfs.img of=sd.img conv=sync,fsync seek=$((0x2000+0xA000))

* Format image:
fdisk sd.img << EOF
n
p
1
49152

w
EOF

=== Calibrate touchscreen ===
If you want to use LCD panel with touchscreen, you should perform a screen calibration.

==== Calibrate using tslib ====
----

* Install the required packages:
apt-get update
apt-get install xorg-dev xserver-xorg-dev x11proto-core-dev git automake make libtool

* Download tslib:
git clone https://github.com/kergoth/tslib.git
cd tslib

* Download patch:
cd plugin
wget https://dl.dropbox.com/u/40057/patches/input-raw.c
cd ../

* Compile the library:
autoreconf -vi
./configure --prefix=/usr
make
make install
ldconfig

* Modify tslib configuration
vi /usr/etc/ts.conf
Uncomment the following line:
module_raw input

* Export tslib needed variables:
export TSLIB_TSEVENTTYPE=raw
export TSLIB_CONSOLEDEVICE=none
export TSLIB_FBDEVICE=/dev/fb0
export TSLIB_TSDEVICE=/dev/input/event0
export TSLIB_CALIBFILE=/usr/etc/pointercal
export TSLIB_CONFFILE=/usr/etc/ts.conf
export TSLIB_PLUGINDIR=/usr/lib/ts

* Now tslib is working but still it should be set as default driver in the X:
wget http://ftp.de.debian.org/debian/pool/main/x/xf86-input-tslib/xf86-input-tslib_0.0.6.orig.tar.gz
tar zxfv xf86-input-tslib_0.0.6.orig.tar.gz
cd xf86-input-tslib-0.0.6/
Replace tslib.c file with patched one:
cd src/
rm -f tslib.c
wget https://dl.dropbox.com/u/40057/patches/tslib.c
cd ..
Build and install package:
./configure --prefix=/usr
make
make install

* Add tslib configuration:
cd /usr/share/X11/xorg.conf.d/
Make new file:
nano 20-touchscreen.conf
Add the following text inside:
Section "InputClass"
Identifier "AR1020"
MatchDevicePath "/dev/input/event0"
Driver "tslib"
Option "Device" "/dev/input/event0"
Option "ScreenNumber" "0"
Option "Rotate" "NONE"
Option "Width" "'''800'''"
Option "Height" "'''480'''"
Option "SendCoreEvents" "yes"
Option "Type" "touchscreen"
EndSection
Note! Resolution in this example is set for 7 inch LCD.

* Do the actual calibration:
service lightdm stop
ts_calibrate
service lightdm start
After lightdm start you could check if everything is running smoothly.

* Save tslib variables:
vi /etc/environment
Paste the following:
TSLIB_TSEVENTTYPE=raw
TSLIB_CONSOLEDEVICE=none
TSLIB_FBDEVICE=/dev/fb0
TSLIB_TSDEVICE=/dev/input/event0
TSLIB_CALIBFILE=/etc/pointercal
TSLIB_CONFFILE=/usr/etc/ts.conf
TSLIB_PLUGINDIR=/usr/lib/ts

If you change the LCD panel run ts_calibrate to configure touchscreen for the new LCD.

==== Calibrate using AR1021 driver ====
TODO

=== Enabling wireless modules ===
==== RTL8188CUS ====
----
[[File:MOD-WIFI-RTL8188-1.jpg|thumb|[https://www.olimex.com/Products/USB-Modules/MOD-WIFI-RTL8188/ MOD-WIFI-RTL8188]]]
To connect OLinuXino board with wireless, you could use [https://www.olimex.com/Products/USB-Modules/MOD-WIFI-RTL8188/ MOD-WIFI-RTL8188] dongle. Also you can use another one with the same chip.

[https://www.olimex.com/Products/USB-Modules/MOD-WIFI-RTL8188/ MOD-WIFI-RTL8188] has the following features:
* Has WM-294 module with RTL8188
* Operates in 2.4 GHz frequency bands
* 1x1 MIMO technology improves effective throughput and range over existing 802.11 b/g products
* Data rates: up to 150Mbps
* 802.11e-compatible bursting and I standards BPSK, QPSK, 16 QAM, 64 QAM modulation schemes WEP, TKIP, and AES, WPA, WPA2 hardware encryption schemes
* Standard USB type A connector
* On-board antenna
* 5V/3.3V operation modes via SMD jumper
* 4 test pads for easy tracking the supply, d-, d+, and GND
* PCB: FR-4, 1.00 mm (0,039"), solder mask, silkscreen component print
* Dimensions: 65.15x20.38 mm (2.56x0.80")
----

The kernel module is prebuild. You should just get it loaded and then plug the dongle.
* Load the module:
modprobe 8192cu

* Plug the device and check if it is available:
ifconfig -a

==== RT5370 ====
----
[[File:MOD-WIFI-R5370-ANT-1.jpg|border|thumb|[https://www.olimex.com/Products/USB-Modules/MOD-WIFI-R5370-ANT/ MOD-WIFI-R5370-ANT]]]

To use one this wifi dongle (like [https://www.olimex.com/Products/USB-Modules/MOD-WIFI-R5370/ MOD-WIFI-R5370] or [https://www.olimex.com/Products/USB-Modules/MOD-WIFI-R5370-ANT/ MOD-WIFI-R5370-ANT]) additional files are required.

[https://www.olimex.com/Products/USB-Modules/MOD-WIFI-R5370-ANT/ MOD-WIFI-R5370-ANT] has the following features:

* 2.4GHz with 150Mbps PHY data rate
*External antenna for extended range
*USB 2.0 interface
*Security: WEP/TKIP/AES/WPA/WPA2/WAPI
*CMOS single chip with RF, baseband, and MAC integration
*QoS: WMM & WMM-PS support
*Multiple BSSID support
*Maximum likelihood decoding support
*Cisco CCX 5.0 support
*Low-power usage with advanced power management
----

*First a make new directory and navigate to it. This is where the module will search for files.
mkdir -p /etc/Wireless/RT2870STA
cd /etc/Wireless/RT2870STA/

*Download the files from Github
wget https://raw.githubusercontent.com/SelfDestroyer/RK3188-SOM/olimex/stable-3.0/drivers/net/wireless/rtxx7x/RT2870STA.dat
wget https://raw.githubusercontent.com/SelfDestroyer/RK3188-SOM/olimex/stable-3.0/drivers/net/wireless/rtxx7x/RT2870STACard.dat

*Load module
modprobe rt5370sta

*Plug the device and run:
ifconfig -a
*You should see this:
wlan0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

*Configure your new device:
vi /etc/network/interfaces
*Add configuration. Here we will show DHCP configuration.
iface wlan0 inet dhcp
wpa-ssid "'''your ssid'''"
wpa-psk "'''your password'''"

*Save the configuration and up the interface:
ifup wlan0

*If everything is working and this module to be loaded on boot:
echo rt5370sta >> /etc/modules

== Android ==

A20-OLinuXino-MICRO

2023-12-06T08:45:01Z

LubOlimex: /* Download locations Linux images */

[[File:A20-OLinuXino.jpeg]]

A20-OLinuXino-MICRO features:
*A20 Cortex-A7 dual-core ARM Cortex-A7 CPU and dual-core Mali 400 GPU
*1GB DDR3 RAM memory
*Optional 4GB NAND FLASH memory
*SATA connector with 5V SATA power jack
*HDMI FullHD 1080p
*2x USB Low-Full-High-Speed hosts with power control and current limiter
*USB-OTG with power control and current limiter
*VGA output on 6-pin 1.25mm (0.05") step connector
*100MBit native Ethernet
*LiPo Battery connector with battery-charging capabilities
*Audio headphones output
*Microphone input on connector
*2x UEXT connectors
*LCD connector compatible with with 4.3", 7.0", 10.1" LCD modules from Olimex
*160 GPIOs on three GPIO connectors
*MicroSD card connector
*SD/MMC card connector
*DEBUG-UART connector for console debug with USB-SERIAL-CABLE-F
*status LED
*Battery charge status LED
*Power LED
*2KB EEPROM for MAC address storage and more
*10 BUTTONS with ANDROID functionality + RESET button
*4 mount holes
*6-16V input power supply, noise immune design
*PCB dimensions: 142 x 82 mm

== Official Images Released and Recommended by Olimex ==

Below you would find links to the official Debian and Android images. The images in this chapter were compiled by Olimex. They are recommended for beginners and first time users since they include full hardware support.

If you are an experienced embedded Linux professional you might also find build instructions to our images.

=== Linux Images ===

There are three different types of Olimex-made official Linux images:

* Recent kernel and u-boot Armbian-based Ubuntu Bionic and Debian Buster Linux images for general purpose Linux experience
* KODI images, LibreElec-based, if you wish to use your A20 board as TV box
* Debian 8 Jessie images with v3.4.x sunxi kernel

The official Linux images should be downloaded to a microSD card. Images can be downloaded either from our FTP or via torrent client. You can install the Debian to the NAND or the eMMC of your board (if it comes with one). Information on booting Debian from the NAND or eMMC might be found in these wiki article: [[how to install Debian to NAND]]; [[how to install Debian to eMMC]]. Download locations for the official images might be found below:

== Download locations Linux images ==

'''ALWAYS FIRST TEST WITH LATEST OFFICIAL IMAGE, NEWER HARDWARE REVISIONS OF THE BOARD MIGHT NOT WORK WITH OLDER IMAGES!!!'''

----

Main FTP hub folder for all Olimex-made A20 official images:

ftp://staging.olimex.com/Allwinner_Images/A20-OLinuXino/

'''Latest mainline kernel official images:'''

1. Latest Ubuntu Desktop Linux images can be found here: [ftp://staging.olimex.com/Allwinner_Images/A20-OLinuXino/1.latest_mainline_images/bionic/images/ FTP directory with latest Ubuntu Bionic images]

2. Latest Debian Server Linux images can be found here:
[ftp://staging.olimex.com/Allwinner_Images/A20-OLinuXino/1.latest_mainline_images/buster/images/ FTP directory with latest Debian Buster images]

'''Latest KODI player official images:'''

3. Latest KODI player LibreElec Linux images here:
[ftp://staging.olimex.com/Allwinner_Images/A20-OLinuXino/4.LibreELEC_KODI_images/ FTP directory with latest KODI/LibreElec images]

'''Latest sunxi kernel official images (not recommended):'''

Latest sunxi-kernel (v3.4.x) Debian 8 Jessie Linux images here: [ftp://staging.olimex.com/Allwinner_Images/A20-OLinuXino/2.legacy_images_kernel_3.4.x/ FTP location with all sunxi-kernel Debian 8 images here]

FTP link of official Debian Jessie release #18, suitable for boards with no extra flash memory or with extra eMMC flash memory (not suitable for boards with NAND memory): [https://ftp.olimex.com/Allwinner_Images/A20-OLinuXino-MICRO/Debian/sd/A20_OLinuxino_Micro_debian_Jessie_34_103_2G_eMMC_release_18.zip A20 OLinuxino Micro debian Jessie 34 103 2G eMMC release 18]

FTP link of official Debian Jessie release #15, suitable for boards with no extra flash memory or with extra NAND memory (not suitable for boards with eMMC memory): [https://ftp.olimex.com/Allwinner_Images/A20-OLinuXino-MICRO/Debian/sd/A20_OLinuxino_Micro_debian_Jessie_34_103_2G_NAND_release_15.7z A20-OLinuXino-MICRO Debian Jessie with kernel 3.4.103+ release 15]

Image description and typical interfacing: [https://raw.githubusercontent.com/OLIMEX/OLINUXINO/master/SOFTWARE/A20/A20-build-3.4.103-release-7/USAGE-AND-COMMON-PRACTICEs-A20-Olimex_kernel_3.4.103%2B_Jessie_rel_3.txt description and basic usage of different peripherals at at the GitHub page]

Image build instructions and required files for latest Debian Jessie release might be found here: [https://github.com/OLIMEX/OLINUXINO/raw/master/SOFTWARE/A20/A20-build-3.4.103-release-7/BUILD_DESCRIPTION_A20_Olimex_kernel_3.4.103%2B_Jessie_rel_6.txt build instructions and required files at the GitHub page]

You can find some older releases and older build instructions (older image revisions might be used as a reference, for testing purposes, or if you own old hardware revision of the board) at the following article: [[A20-OLinuXino-MICRO-older-releases|older releases and older build instructions]]

----

Note: in the previous Debian releases the Ethernet was auto-detected and initialized during boot BUT this caused big delays in the start-up of the board if you didn't want to use Ethernet or if there wasn't Ethernet cable connected.

You can enable it by following these two steps:

1. To check under what name the LAN is associated write "ifconfig –a"

2. If, for example, it is under eth0 name, then write: "dhclient eth0"

This should enable the Ethernet and then SSH would also be available.

=== Android images ===

FTP links of official Android releases are below. Please read description of the image carefully.

FTP link of Android release 3 for NAND memory with HDMI and 7 inch LCD (800x480) support: [https://ftp.olimex.com/Allwinner_Images/A20-OLinuXino-MICRO/Android/nand/A20_android_422_TS_USB_UART_I2C_WIFI_LAN_HDMI_LCD_800x480_release_3.img A20-OLinuXino Android for NAND with HDMI and 800x480 video support]

If you want to use it with our RTL8188ETV module then consider release #4:

[https://ftp.olimex.com/Allwinner_Images/A20-OLinuXino-MICRO/Android/nand/A20_android_422_TS_USB_UART_I2C_WIFI_LAN_HDMI_LCD_800x480_release_4.img A20-OLinuXino-MICRO Android for NAND memory with video settings for 800x480 display output + MOD-WIFI-RTL8188ETV module]]

FTP of Android release 3 for NAND memory with HDMI and 10 inch LCD (1024x600) support: [https://ftp.olimex.com/Allwinner_Images/A20-OLinuXino-MICRO/Android/nand/A20_android_422_TS_USB_UART_I2C_WIFI_LAN_HDMI_LCD_1024x600_release_3.img A20-OLinuXino Android for NAND with HDMI and 1024x600 video support]

Torrent of Android release 1 for microSD card with HDMI and 7 inch LCD (800x480) support: [[Media:A20_SD_4G_android_422_TS_USB_UART_I2C_WIFI_LAN_HDMI_LCD_800x480_release_1.torrent‎‎‎|A20-OLinuXino Android for microSD card with HDMI and 800x480 video support]]

Torrent of Android release 1 for microSD card with HDMI and 10 inch LCD (1024x600) support: [[Media:A20_SD_4G_android_422_TS_USB_UART_I2C_WIFI_LAN_HDMI_LCD_1024x600_release_1_fix.torrent‎‎|A20-OLinuXino Android for microSD card with HDMI and 1024x600 video support]]

Build instructions and source files for the official Android images for A20 boards in this repository: https://github.com/hehopmajieh/olinuxino_configs

The Android image has the following features:
*Android 4.2.2
*NAND image i.e. will work only on [https://www.olimex.com/Products/OLinuXino/A20/A20-OLinuXino-MICRO-4GB/ A20-OLinuXino-MICRO-4GB]
*Supports [https://www.olimex.com/Products/OLinuXino/A13/A13-LCD7-TS 7" LCD 800x480 pixels] and [https://www.olimex.com/Products/OLinuXino/A13/A13-LCD10TS 10" LCD 1024x600 pixels]
*HDMI support (720p default)
*both LCD and HDMI work together
*Touchscreen supported
*GPIO support
*Native Ethernet 100Mbit
*USB-Ethernet [https://www.olimex.com/Products/OLinuXino/A13/USB-ETHERNET-AX88772B/ ASIX 88772]
*USB-WIFI [https://www.olimex.com/Products/Modules/Ethernet/MOD-WIFI-RTL8188/ RTL8188]
*USB-OTG support USB device and USB host with Low/Full/High speed
*USB-HOST-top Low/Full/High speed
*USB-HOST-bottom Low/Full/High speed
*micro SD card
*Audio OUT
*Audio In
*I2C1
*I2C2
*UART6
*UART7
*Buttons

What is left unsupported in Android:
*SATA
*SD-MMC card on bottom

== Notable unofficial images ==

Below you would find locations to images released by the community. These are not officially supported by Olimex, however, some of these releases are pretty good and worth a try:

*A number of very good and optimized A20-OLinuXino-MICRO Armbian images: [https://www.armbian.com/olimex-micro/ link to LIME2 article at Armbian's web-site]

*A20-OLinuXino-MICRO is supported by openSUSE Factory, installation instructions might be found here: [https://en.opensuse.org/HCL:A20-OLinuXino-MICRO openSUSE wiki link]

*A20-OLinuXino-MICRO is recognized by the Devuan community and there are official releases here might be found here: [https://files.devuan.org/devuan_jessie_rc/embedded/ Devuan list of files link]
 

== Documents ==

===A20-OLinuXino Board User Manual===
[https://www.olimex.com/Products/OLinuXino/A20/A20-OLinuXino-MICRO-4GB/resources/A20-OLinuXino-Micro.pdf A20-OLinuXino user manual]

=== A20 Brief ===

[https://github.com/OLIMEX/OLINUXINO/blob/master/DOCUMENTS/A20-PDFs/A20%20brief%2020130407.pdf A20 brief description]

=== A20 Datasheet ===

[https://github.com/OLIMEX/OLINUXINO/blob/master/DOCUMENTS/A20-PDFs/A20%20Datasheet%20v1.0%2020130227.pdf A20 datasheet]

=== A20 User Manual ===
[https://github.com/OLIMEX/OLINUXINO/blob/master/DOCUMENTS/A20-PDFs/A20%20User%20Manual%202013-03-22.pdf A20 users manual]

== Hardware ==

[[File:Example.jpg|650px]]

 
===Power supply and consumption===

A20-OLinuXino can be powered from three sources:
*+6-16VDC voltage applied PWR jack
*+3.7V from LiPo re-chargable battery connected to LiPo board connector
*+5V applied to USB-OTG connector

Power consumption is as follows:
*LiPo 3.7V power battery: 0.17-0.25A depend on processor load
*+6VDC input power: 0.18-0.33A depend on processor load
*+16VDC input power: 0.11-0.17A depend on processor load

Comparison table of power consumption might be found at the following [https://www.olimex.com/Products/OLinuXino/_resources/OLinuXino-Consumption.pdf link].

LiPo battery allow backup power supply when main power is interrupted. A20-OLinuXino have power managment IC which charge the battery when main power is present, when power is interrupted the LiPo battery automatically provide backup power supply. Step-up converter prvide 5V for the USB peripherials too. For LiPo batteries we recommend these:
*[https://www.olimex.com/Products/Power/BATTERY-LIPO1400mAh/ 1400mAh]
*[https://www.olimex.com/Products/Power/BATTERY-LIPO3000mAh/ 3000mAh]
*[https://www.olimex.com/Products/Power/BATTERY-LIPO4400mAh/ 4400mAh]
*[https://www.olimex.com/Products/Power/BATTERY-LIPO6600mAh/ 6600mAh]

===Board dimensions===

A20-OLinuXino-MICRO hardware revision M dimensions in mils:[https://www.olimex.com/Products/OLinuXino/A20/A20-OLinuXino-MICRO/resources/A20-OLinuXino-MICRO-revsion-M-dimensions.png image in PNG format]

A20-OLinuXino-MICRO hardware revision D dimensions in mils: [https://www.olimex.com/Products/OLinuXino/A20/A20-OLinuXino-MICRO/resources/a20-dimensions.png image in PNG format]

===CAD files===

A20-OLinuXino-MICRO is Open Source Hardware, CAD files are available at [https://github.com/OLIMEX/OLINUXINO/tree/master/HARDWARE/A20-OLinuXino-MICRO GitHub]

The CAD product used to design OLinuXino is Eagle and you can download evaluation free version from their [http://www.cadsoftusa.com/ web].

===Board Layout===

[[File:A20-OLinuXino-FRONT.jpg]]

[[File:A20-OLinuXino-BACK.jpg]]

===Be careful with TV monitors without grounding===
[http://olimex.wordpress.com/2014/01/22/bevare-non-grounded-tv-monitors-can-damage-your-olinuxino/ Here] you can read how easy you can damage your OLinuXino if you connect it to TV without grounding.

== Software ==

===Linux Commands===

[[Linux-Commands]] Brief Linux Command reference

===Python===

[https://pypi.python.org/pypi/pyA20 pyA20 is Python library for access to A20-OLinuXino-MICRO GPIOs, I2C, SPI]

Use:

#!/usr/bin/env python

import A20_GPIO as GPIO

#init module
GPIO.init()

#configure module
GPIO.setcfg(GPIO.PIN#, GPIO.OUTPUT)
GPIO.setcfg(GPIO.PIN#, GPIO.INPUT)

#read the current GPIO configuration
config = GPIO.getcfg(GPIO.PIN#)

#set GPIO high
GPIO.output(GPIO.PIN#, GPIO.HIGH)

#set GPIO low
GPIO.output(GPIO.PIN#, GPIO.LOW)

#read input
state = GPIO.input(GPIO.PIN#)

#cleanup
GPIO.cleanup()

===GPIO under Linux===

A very good GPIO guide by Dr. Guido Pelz might be found here: [https://github.com/OLIMEX/OLINUXINO/raw/master/HARDWARE/A20-PDFs/A20-GPIO.pdf https://github.com/OLIMEX/OLINUXINO/raw/master/HARDWARE/A20-PDFs/A20-GPIO.pdf]

You can read data from a given GPIO port. The logical ranges are usually as follows: 0V-1V for LOW (or 0) and 2.4V-3.3V for HIGH (or 1). All voltages are measured against ground (GND).

If the input signal is to high, you will at least destroy the port!

In order to use A20 GPIO's first you have to export them. You can export a single GPIO:

root@A20:~# echo gpioXX > /sys/class/gpio/export

To export a range of GPIOs (from 1-230 in the example below) use:

root@A20:~# for i in `seq 1 1 230`; do echo $i > /sys/class/gpio/export; done

list of all available GPIO

root@A20:~# ls /sys/class/gpio/
export gpio21_pc3/ gpio33_pb8/ gpio45_ph27/ gpio57_ph17/ gpio69_pg5/
gpio10_pe9/ gpio22_pc7/ gpio34_pb10/ gpio46_ph0/ gpio58_ph18/ gpio6_pe5/
gpio11_pe10/ gpio23_pc16/ gpio35_pb11/ gpio47_ph2/ gpio59_ph19/ gpio70_pg6/
gpio12_pe11/ gpio24_pc17/ gpio36_pb12/ gpio48_ph7/ gpio5_pe4/ gpio71_pg7/
gpio13_pi14/ gpio25_pc18/ gpio37_pb13/ gpio49_ph9/ gpio60_ph20/ gpio72_pg8/
gpio14_pi15/ gpio26_pc23/ gpio38_pb14/ gpio4_pe3/ gpio61_ph21/ gpio73_pg9/
gpio15_pi0/ gpio27_pc24/ gpio39_pb15/ gpio50_ph10/ gpio62_ph22/ gpio74_pg10/
gpio16_pi1/ gpio28_pb3/ gpio3_pe2/ gpio51_ph11/ gpio63_ph23/ gpio75_pg11/
gpio17_pi2/ gpio29_pb4/ gpio40_pb16/ gpio52_ph12/ gpio64_pg0/ gpio7_pe6/
gpio18_pi3/ gpio2_pe1/ gpio41_pb17/ gpio53_ph13/ gpio65_pg1/ gpio8_pe7/
gpio19_pi10/ gpio30_pb5/ gpio42_ph24/ gpio54_ph14/ gpio66_pg2/ gpio9_pe8/
gpio1_pe0/ gpio31_pb6/ gpio43_ph25/ gpio55_ph15/ gpio67_pg3/ gpiochip1/
gpio20_pi11/ gpio32_pb7/ gpio44_ph26/ gpio56_ph16/ gpio68_pg4/ unexport

Example on how to write to a GPIO. For instance - toggle onboard LED. The LED is connected to PH2.

1. Export gpio47_ph2

root@A20:~# echo gpio47 > /sys/class/gpio/export

2. Set PH2 as output

root@A20:/sys/class/gpio/gpio47_ph2# echo out > direction

3. Set high position (1) of PH2 - LED is ON

root@A20:/sys/class/gpio/gpio47_ph2# echo 1 > value

4. Set low position (0) of PH2 - LED is OFF

root@A20:/sys/class/gpio/gpio47_ph2# echo 0 > value

Example on how to read GPIO (with GPIO #49):

1. Export GPIO 49

echo 49 > /sys/class/gpio/export

2. Set input

echo "in" > /sys/class/gpio/gpio49_ph9/direction

3. Read value GPIO 49

cat /sys/class/gpio/gpio49_ph9/value

4. Unexport GPIO 49 when finished

echo 49 > /sys/class/gpio/unexport

===Add Voice to your OLinuXino project===

[http://olimex.wordpress.com/2013/10/03/make-things-talk-with-olinuxino/ Installation of Festival on OLinuXino]

== How To? ==
 
===How to correctly power off OLinuXino running from NAND Flash===
[http://olimex.wordpress.com/2014/01/24/how-to-correctly-power-off-olinuxino-running-android/ In this Blog post] we explain what are the problems. This is common problem for all computers running OS. [http://www.linux-mtd.infradead.org/doc/ubifs.html#L_ubifs_mlc Here] you can read more about MLC NAND Flash and Linux file system.

=== Is it possible to boot Debian from NAND? Do you provide such image?===
Yes, it is possible. Use the latest Debian Jessie image and write "nandinstall". More information can be found in this wiki article: [[How_to_install_Debian_to_NAND| installing Debian Jessie to the 4GB NAND memory]]

There are other people who are also successful in booting Debian from the NAND. Make sure to check on the forum. Make sure to check the number of very good and optimized A20-OLinuXino Debian images by Igor Pečovnik. There are also his instructions for NAND installation of Debian: [http://www.armbian.com/download/ link to his web-site]

===How to generate boot-able SD-card Debian Linux image for A20-OLinuXino? ===

Build instructions and required files for the latest Debian images: [https://github.com/OLIMEX/OLINUXINO/tree/master/SOFTWARE/A20/A20-build-3.4.103-release-7 instructions and files at the GitHub page]

[http://olimex.wordpress.com/2014/03/07/building-a20-olinuxino-micro-debian-image-with-hardware-accelerated-video/ Official Olimex wordpress article on how to extend the previous build of Debian Linux 3.4 with hardware acceleration support, keep a look at the wordpress for more interesting articles]

[https://github.com/linux-sunxi/u-boot-sunxi/wiki Sunxi u-boot loader] The linux-sunxi git page contains a lot of sources for all Olimex Allwinner boards.

===How to download new Android image to the NAND memory of my A20 board?===

To repair the image on the NAND re-upload it following these steps:

*1. Install and run PhoenixSuit (can be found here: [https://drive.google.com/file/d/0BwplT87k9SCgaTFTZnVST05ONzA/view?usp=sharing download from google drive]).

*2. Go to firmware tab of the program and point to a valid Android image (the latest official one may also be downloaded above).

*3. Disconnect the power supply and USB cable from the A20 board.

*4. Press and hold RECOVERY button, apply power supply (6-16)V, release RECOVERY button.

*5. Connect USB cable to the mini USB connector.

*6. You will be asked for drivers for the bootloader. Navigate to the folder where you extracted the PhoenixSuit and install the drivers from the respective executables (or manually point the installer to the drivers folder in the PhoenixSuit installation path).

*7. PhoenixSuit will detect the board and would ask for the method of writing the image. Choose method of writing the image and confirm your wish to write the image.

*8. Wait till upgrade succeeds

Note that it is not recommended to have your mini USB connected to an external USB hub. This might cause delays and might distort the signal levels. Always test with the USB connected straight to the USB ports of your computer.

===How do I write the official Android image to a micro SD card for my A20 board?===
A: First download one of the official Android images, which might be found in the Android section above.

Make sure that the download link you visit clearly indicates that the image is suitable for the microSD card since there are images suitable for NAND memory also. The images suitable for the microSD memory and those suitable for NAND card are different. However, the upload method is almost identical – using PhoenixSuit.

There are two types of Android images for microSD card that we usually provide and each of them has to be downloaded to a microSD card using a different method. The image provided for microSD card is either the native Android image that can be downloaded to the card via a software tool like PhoenixSuit (through the board) or an image taken from an already prepared microSD card that requires to simply write the image (through a microSD card reader).

'''It is more likely that you have an Android image that requires a simple copy to a card. If that is the case you can follow the exact steps as for Linux (e.g. using "Win32 Disk Imager" or "dd" command).'''

In order to prepare a microSD card with a native Android you will need a software tool called PhoenixSuit and then:

• Install and run PhoenixSuit (can be found here: [https://drive.google.com/file/d/0BwplT87k9SCgaTFTZnVST05ONzA/view?usp=sharing download from google drive])

• Go to the firmware tab of the program and point to a valid Android image (note that the
images on Gdrive are compressed and you have to extract them to .img files to be able write
them with PhoenixSuit)

• Disconnect the power supply and USB cable from the A20 board. Put an SD card in micro SD
holder. We recommend 4GB class 10 card.

• Press and hold RECOVERY button, apply power supply (6-16)V, release RECOVERY button.

• Connect USB cable to the mini USB connector.

• You will be asked for drivers for the boot-loader. Navigate to the folder where you extracted the PhoenixSuit and install the drivers from the respective executables (or manually point the installer to the drivers folder in the PhoenixSuit installation path).

• PhoenixSuit will detect the board and would ask for the method of writing the image. Choose
method of writing the image and confirm your wish to write the image.

• Wait till upgrade succeeds

Note that it is not recommended to have your mini USB connected to an external USB hub. This
might cause delays and might distort the signal levels. Always test with the USB connected straight to the USB ports of your computer.

Important: When Android runs for very first time it takes several minutes to initialize all files and buffers please do not cut the power supply during this process! Also when fresh image is installed fast boot may be disabled, which means that when you apply power supply after few seconds Android will go in sleep mode and you have to press POWER button to start it, you can change to fast boot when you power off there is dialog box asking you if you want next boot to be fast boot, you have to check this box before you power off. Also note that you must do touch screen calibration when you run Android for very first time which might require a mouse.

===How do I write the Linux image to a micro SD card to use with my A20 board?===

To write a Linux image to an SD card under Windows we use Win32 Disk Imager):

*Download Win32 Disk Imager [http://sourceforge.net/projects/win32diskimager/ Win32 Disk Imager]
*Insert card
*Start program
*Select file
*Click "write"

To write a Linux image to an SD card under Linux:

For instance you have an image with the file name of "debian_2g.img". It would be downloaded to the SD card connected to a Linux machine using one of the following commands:

* # dd bs=4M oflag=sync if=debian_2g.img of=/dev/sdX
or
* # cp debian_2g.img /dev/sdX

where X is the uSD card.

===How to change HDMI, VGA and LCD resolutions in the official Debian image?===

The default SD card setup is made with settings for HDMI 720p/60Hz. If you want to change to some other LCD, VGA or HDMI resolution then you have to start change_display.sh script file in /root directory. When you are logged as super user in the board type:

For Debian Wheezy releases: ./change_display* (* = press 'tab')
For Debian Jessie releases: change_display* (* = press 'tab')

and press "Enter".

'''Note that the script should be executed as super user. Under the command line interface you are automatically logged as super user (user "root", password "olimex"). However, under the graphical environment you are not auto-logged as super user and you must type "sudo" before the command (in the GUI the super-user is "olimex" and the password is "olimex")'''

Then choose the resolution and the interface(LCD, HDMI or VGA). Note that the selection of a specific resolution is done by navigating with the arrow keys and pressing "space" button. Make sure the asterisk marks your selection properly.

The supported resolutions are:

'''For LCD:'''

*1. 4.3" (480x272)
*2. 7" (800x480)
*3. 10" (1024x600)
*4. 15.6" (1366x768)

Important: initially the boards are calibrated for a specific display. If you re-write the image (no matter whether the SD card or the NAND memory) you would need to use a mouse to calibrate the display initially. It might be impossible to calibrate it via touching the display.

'''For HDMI:'''

*0. 480i
*1. 576i
*2. 480p
*3. 576p
*4. 720p50
*5. 720p60
*6. 1080i50
*7. 1080i60
*8. 1080p24
*9. 1080p50
*10. 1080p60
 
'''For VGA:''' (note that the VGA signals are routed to custom 6 pin connector and you need from adapter to standard VGA connector)

*0. 1680x1050
*1. 1440x900
*2. 1360x768
*3. 1280x1024
*4. 1024x768
*5. 800x600
*6. 640x480
*7. 1920x1080
*8. 1280x720
 

===How to generate Arch Linux image?===

Recent forum post by user progmetalbg here: [https://www.olimex.com/forum/index.php?topic=4261.0| at Olimex forums]

[http://alarma20.wordpress.com/2013/09/13/howto-build-arch-linux-arm-for-a20-olinuxino-micro/ Older step by step instructions on how to build Arch Linux image]

===How to detect and enable the Ethernet controller (if it is disabled by default)? ===

Note: in the previous Debian releases the Ethernet was auto-detected and initialized during boot BUT this was causing big delays in the start-up of the board if you didn't want to use Ethernet or if there wasn't Ethernet cable connected.

You can enable it by following these two steps:

1. To check under what name the LAN is associated write "ifconfig –a"

2. If, for example, it is under eth0 name, then write: "dhclient eth0"

This should enable the Ethernet and then SSH would also be available.

===How to install Android on SD-card? ===

[http://olimex.wordpress.com/2013/10/02/android-4-2-2-images-for-a20-olinuxino-running-from-sd-card-is-updated-on-wiki/ Blog post about it]

===How to access UART, I2C, GPIOs under Android? ===

[http://olimex.wordpress.com/2013/10/02/a20-olinuxino-tools-for-android-released/ Use our Open Source OLinuXino A20-TOOLS]

===How to control PWM under Linux? ===

There is an article here: [[how to add pwm]]

===How to build the Android 4.2.2 image for A20-OLinuXino-MICRO? ===

First you need to Download the [http://dl.linux-sunxi.org/users/tsvetan/ANDROID-4.2.2-SDK2.0-KERNEL-3.4/ A20 SDK2.0 Linux Kernel 3.4]

Second you need to configure your environment read the instructions [http://source.android.com/source/initializing.html here]

Then Build the kernel, kernel modules and u-boot

cd lichee
./build.sh -psun7i_android

When done, continue with Bulding the android image:

cd ../android4.2
cd device/softwinner/
tar zxfv olinuxino-a20.tgz
cd ../../
source build/envsetup.sh
lunch #select olinuxino-a20_eng
extract-bsp
make -j4

Dave from Axon instruments wrote more detailed [http://axonjakarta.wordpress.com/2014/02/14/olimex-a20-android-building-4/ blog post] about how he generates the Android image

===I don't have neither serial cable, nor HDMI monitor. I also can't access the local Ethernet network. Can I somehow access the board anyway?===

The latest official Debian Linux image allows the use the USB_OTG connector for SSH connection without the need of a LAN cable or a serial cable. You can use a mini USB cable connected between your host PC and the on-board mini USB connector. For connection convenience there is a DHCP server running specifically for USB0 interface. The DHCP server should give IP address to the new USB0 interface of your host PC so you can make SSH connection from your PC to the default board IP address of the USB0 interface – 192.168.2.1.

You can connect to the board using a mini USB cable and an SSH client (if you use Windows you might use "puTTY", for example) at address 192.168.2.1.

For Windows operating system - upon connection, the board should show up in "Windows Device Manager" as "RNDIS Ethernet Gadget". You might be asked to install a driver. The drivers can be found online as "RNDIS driver" (Remote Network Driver Interface Specification). The drivers are provided by Microsoft and they should be available for every Windows distribution - refer to the respective files and articles provided by Microsoft on how to install the required drivers.

===How to edit board configurations and definitions in the official Debian Linux? ===

Do you want a custom video resolution output? Do you need a different port definition? Do you need to change the hardware defitions of the board?

You would need to edit the board's script.bin/script.fex file. How to do it is described in another separate article: [[How_to_edit_board_configurations_and_definitions_in_the_official_Debian_Linux]].

===How to properly calibrate a display under Debian===

Latest Debian Jessie images should be calibrated as detailed here: https://www.olimex.com/wiki/Touch_calibration_official_images

If using older Debian Wheezy image follow the algorithm below:

Make sure you are properly logged in the LXDE visual interface! Else applying calibration would not happen for the current user - if you are calibrating from the X graphical interface make sure that you are logged as user “olimex” (if calibrating without the X, the user is “root”).

#su olimex
enter the olimex password:olimex

#sudo ts_calibrate
calibrate the touch screen and reboot the board

#sudo reboot

It would be a good idea to test with Android or another Debian image also, it has a built-in calibration application by default.

===How to add STK1160 video capture driver support in Kernel 3.4===

[https://www.olimex.com/wiki/STK1160-howto-linux-sunxi-3_4 STK1160] driver backport by Dimitar Tomov

[[Main_Page]]

ICE40HX1K-EVB

2023-10-05T11:53:24Z

LubOlimex: /* Documents */

[[File:iCE40HX1K-EVB.jpg]]

== Documents ==
[https://www.latticesemi.com/~/media/LatticeSemi/Documents/ProductBrochures/NZ/ProductSelectorGuide.PDF Product Selection Guilde]

[https://www.latticesemi.com/~/media/LatticeSemi/Documents/Handbooks/iCE40FamilyHandbook.pdf iCE40 Family Handbook]

[https://www.latticesemi.com/~/media/LatticeSemi/Documents/DataSheets/iCE/iCE40LPHXFamilyDataSheet.pdf iCE40 datasheet]

[https://github.com/OLIMEX/iCE40HX1K-EVB/tree/master/gpio1-pcf GPIO headers and TCF]

== Hardware ==
[https://github.com/OLIMEX/iCE40HX1K-EVB GitHub repository with the hardware files]

iCE40HX1K-EVB programming connector

[[File:iCE40PGM.jpg|650px]]

iCE40HX1K-EVB 34-pin bus connector

[[File:iCE40BUS.jpg|650px]]

== Software ==

=== Get started under Linux ===

The hardware requirements to develop for the platform are:
- iCE40HX1K-EVB or iCE40HX8K-EVB
- 3.3V programmer board - OLIMEXINO-32U4 (customers have reported success using other Arduino compatible boards; and also RPi2, RPiB2+, RPi3, RPiB3+ - we have no first-hand experience with anything else than OLIMEXINNO-32U4)
- IDC10-15cm cable to connect iCE40HX1K-EVB with OLIMEXINO-32U4
- SY0605E 5V power supply adapter
- USB-MINI cable
- optional but recommended USB-ISO

====Installing Icestorm FOSS tools for iCE40====

First we need to install the tools necessary to build Icestorm:

sudo apt-get install build-essential clang bison flex libreadline-dev \
gawk tcl-dev libffi-dev git mercurial graphviz \
xdot pkg-config python python3 libftdi-dev

Installing the IceStorm Tools (icepack, icebox, iceprog, icetime, chip databases):

git clone https://github.com/cliffordwolf/icestorm.git icestorm
cd icestorm
make -j$(nproc)
sudo make install

Installing Arachne-PNR (the place&route tool):

git clone https://github.com/cseed/arachne-pnr.git arachne-pnr
cd arachne-pnr
make -j$(nproc)
sudo make install

Installing Yosys (Verilog synthesis):

git clone https://github.com/cliffordwolf/yosys.git yosys
cd yosys
make -j$(nproc)
sudo make install

The Arachne-PNR build converts the IceStorm text chip databases into the arachne-pnr binary chip databases. Always rebuild Arachne-PNR after updating your IceStorm installation.

Notes for Archlinux: just install icestorm-git, arachne-pnr-git and yosys-git from the Arch User Repository (no need to follow the install instructions above).

You might want to try a new alternative tool instead of arachne-pnr: nextpnr is new place and route tool from the IceStorm-project. It has improved capabilities like GUI to show the connections between cells of FPGA and support for TRISTATE buffer. You might want to check it here:

https://github.com/YosysHQ/nextpnr

====Preparing OLIMEXINO-32U4 as programmer====

Download latest [https://www.arduino.cc/en/Main/Software Arduino IDE] we recommend you to use the one from Arduino.cc current revision is 1.6.9.

Copy iceprog.ino sketch from GitHub/iCE40HX1K-EVB/programmer/olimexino-32u4 firmware to examples folder.

Plug the USB cable to OLIMEXINO-32U4 and start the Arduino IDE

cd arduino-1.6.9
sudo ./arduino

From Tools select 'Arduino Leonardo' as board.

From same menu select the PORT where the board is attached it will be something like: '/dev/ttyACM0 (Arduino Leonardo)' or '/dev/ttyUSB0 (Arduino Leonardo)'

Also install the SPIMemory library version 2.2.0 (formerly known as SPIFlash). Older versions can't be installed via the Arduino Library Manager so you need to do it manually, download the ZIP archive from here:

https://github.com/Marzogh/SPIMemory/releases/tag/v2.2.0

Load the library in Arduino from Sketch -> Include Library -> Add .ZIP library...

Open the iceprog.ino sketch

Compile and Upload the sketch.

If everything completes without errors now you have your OLIMEXINO-32U4 set as iCE40HX1K-EVB programmer!

==== Hardware connection between OLIMEXINO-32U4 and iCE40HX1K-EVB====

It is a pretty straight-forward - use a 10-pin UEXT compatible cable between the two boards (like CABLE-IDC10-15cm). However, also make sure that the switching button of OLIMEXINO-32U4 is set to position 3.3V!

The signals at the PGM1 connector of iCE40HX1K-EVB are at 3.3V DC! If you use a 5V-only board instead of OLIMEXINO-32U4 you need to drive all SPI signals to 3.3V DC externally. Else there might be a short-circuit or the connection would be unsuccessful.

====Add iceprogduino to IceStorm====

Copy iceprogduino folder from GitHub [https://github.com/OLIMEX/iCE40HX1K-EVB/tree/master/programmer programmer] to icestorm and build it

cd icestorm/iceprogduino
make clean
make
make install

====Make LED blink with IceStorm====

Copy from GitHub ice40hx1k-evb to icestorm/examples then

cd icestorm/examples/ice40hx1k-evb
make
make prog

LED1 and LED2 should start blink which means the code is successfully loaded

====Iceprog with Raspberry PI====

This section is contributed by Andreas Seltenreich

[[File:iceprog.jpg]]

If you have a raspberry PI around, you can use the flashrom utility with Linux’ /dev/spidev to program a bitstream to your ICE40HX1K-EVB or iCE40HX8K-EVB. The following table shows the wiring required for the Pi B+ or 2 (the connection is similar for RPi3 and RPi3B+). I used IDC connectors with a rainbow ribbon for convenient wiring (image above).

| Raspi 2/B+ | | ICE40-EVB | | comment |
|------------+----------+-----------+--------------+----------|
| 17 | =3v3= | 1 | =3v3= | |
| 18 | =gpio24= | 6 | =creset= | |
| 19 | =mosi= | 8 | =sdo= | |
| 20 | =gnd= | 2 | =gnd= | |
| 21 | =miso= | 7 | =sdi= | |
| 22 | =gpio25= | 5 | =cdone= | optional |
| 23 | =clk= | 9 | =sck= | |
| 24 | =ce0= | 10 | =#cd = ss_b= | |
| 25 | =gnd= | | | |
| 26 | =ce1= | | | |

enable SPI device on the Pi (needs reboot)
: echo dtparam=spi=on >> /boot/config.txt

build and install flashrom
: git clone https://www.flashrom.org/git/flashrom.git
: cd flashrom
: make CONFIG_ENABLE_LIBPCI_PROGRAMMERS=no CONFIG_ENABLE_LIBUSB0_PROGRAMMERS=no CONFIG_ENABLE_LIBUSB1_PROGRAMMERS=no install

Once you have enabled the SPI interface and once you have installed flashrom you you can use manual commands or check the scripts that easen it up below.

'''Manual operation:'''

claim GPIO24 for sysfs-control
: echo 24 > /sys/class/gpio/export

Pull GPIO24 low to put the ice40 into reset. The cdone-LED on the board should turn off.
: echo out > /sys/class/gpio/gpio24/direction

Read the flash chip at 20MHz (for short cabling)
: flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=20000 -r dump

Simply swap -r for -w to write the dump back
: flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=20000 -w dump

As generated bitstreams are smaller than size of the flash chip, you
need to add padding for flashrom to accept them as image. I used the
follwing commands to do that:
: tr '\0' '\377' < /dev/zero | dd bs=2M count=1 of=image
: dd if=my_bitstream conv=notrunc of=image

Deassert creset to let the ice40 read the configuration from the bus:
: echo in > /sys/class/gpio/gpio24/direction

'''Automated scripts:'''

Check Sagar Acharya's repo, he did some testing with RPi3 and RPi3B+ and made scripts that automate the process described above:

https://notabug.org/sagaracharya/swarajya/src/master/hdl_to_hx8k

=== Get started under Windows ===

== Projects ==
Under construction

== FAQ ==
Under construction

[[Category:FPGA]]

A20-SOM

2023-09-01T05:39:09Z

LubOlimex: /* Old Linux images */

[[File:A20-SOM-1 jpeg.jpg|675px]]

Features:

*A20 dual core Cortex-A7 processor
*1GB DDR3 memory
*AXP209 PMU IC
*MicroSD card
*UART console
*4GB NAND Flash
*Status LEDs
*RESET, RECOVERY buttons
*6 connectors x 40 pin 0.05" step
 
== Official Images from OLIMEX ==

'''The recommended image for most of Olimex-made Linux boards is Olimage Linux, you can find information about it in the document here:'''

https://github.com/OLIMEX/OLINUXINO/blob/master/DOCUMENTS/OLIMAGE/Olimage-guide.pdf

'''Notice this wiki article refers to outdated images and practices, if using Olimage Linux, use the information only as a reference (do not take it literally)!'''

Note that only the microSD connector is suitable for booting the desired operating system, the SD-MMC connector is not suitable for booting since it is not a part of the boot sequence (refer to A20 datasheet).

=== Old Linux images ===

These Debian images should be downloaded to a microSD card. You need a properly set torrent client to download the official images - they are available only as torrents. You can install the Debian to the NAND or the eMMC of your board (if it comes with one). Information on booting Debian from the NAND or eMMC might be found in these wiki article: [[how to install Debian to NAND]]; [[how to install Debian to eMMC]]. Download locations for the official images might be found below:

'''ALWAYS FIRST TEST WITH LATEST OFFICIAL IMAGE, NEWER HARDWARE REVISIONS OF THE BOARD MIGHT NOT WORK WITH OLDER IMAGES!!!'''

----

'''Latest stable official image - Debian 9 (Jessie)''' '''(recommended for all board revisions)''':'''

FTP download location for the official Debian Jessie release #10 (suitable for boards with NAND): [https://ftp.olimex.com/Allwinner_Images/A20-SOM/Debian/sd/a20-SOM_mainline_uboot_GMAC_master_sunxi_kernel_3.4.103_jessie_NAND_rel_10.img.7z A20-SOM Debian Jessie with kernel 3.4.103+ for boards with NAND flash memory release 10]

FTP download for A20-SOM (suitable for boards with eMMC): [https://ftp.olimex.com/Allwinner_Images/A20-OLinuXino/2.legacy_images_kernel_3.4.x/boards_with_eMMC/a20-SOM_mainline_uboot_GMAC_master_sunxi_kernel_3.4.103_jessie_eMMC_SPI_rel_13.zip A20-SOM Debian Jessie with kernel 3.4.103+ for boards with eMMC flash memory release 13] you might also want to check files and instructions in this folder on how to get boards boot from eMMC if you have troubles: [https://ftp.olimex.com/Allwinner_Images/A20-OLinuXino/2.legacy_images_kernel_3.4.x/boards_with_eMMC/sunxi-spi-emmc/ how to boot from eMMC with newer boards with 5.1 eMMC]

Image description and typical interfacing: [https://raw.githubusercontent.com/OLIMEX/OLINUXINO/master/SOFTWARE/A20/A20-build-3.4.103-release-7/USAGE-AND-COMMON-PRACTICEs-A20-Olimex_kernel_3.4.103%2B_Jessie_rel_3.txt description and basic usage of different peripherals at at the GitHub page]

Image build instructions and required files for latest Debian Jessie release might be found here: [https://github.com/OLIMEX/OLINUXINO/raw/master/SOFTWARE/A20/A20-build-3.4.103-release-7/BUILD_DESCRIPTION_A20_Olimex_kernel_3.4.103%2B_Jessie_rel_6.txt build instructions and required files at the GitHub page]

You can find some older releases and older build instructions (older image revisions might be used as a reference, for testing purposes, or if you own old hardware revision of the board) at the following article: [[A20-SOM-older-releases|older releases and older build instructions]]

----

Note: in the previous Debian releases the Ethernet was auto-detected and initialized during boot BUT this caused big delays in the start-up of the board if you didn't want to use Ethernet or if there wasn't Ethernet cable connected.

You can enable it by following these two steps:

1. To check under what name the LAN is associated write "ifconfig –a"

2. If, for example, it is under eth0 name, then write: "dhclient eth0"

This should enable the Ethernet and then SSH would also be available.

The Debian Linux file system can be extended to suit a bigger card. If the whole SD card is not used, use the following three commands to execute a script that would use all the free space of your card:

sudo su
resize_sd.sh /dev/mmcblk0 2
reboot

=== Android images ===

Links to official Android releases are below. Please read description of the image carefully.

Direct download of Android 4.2.2 release 1 for NAND memory (with HDMI and 800x480 support): [https://ftp.olimex.com/Allwinner_Images/A20-SOM/Android/nand/A20_SOM_camera_LCD7_HDMI_release1.img A20-SOM Android for NAND with HDMI and 7 inch display support]

Direct download of Android 4.2.2 release 1 for microSD card (with HDMI and 800x480 support):
[https://ftp.olimex.com/Allwinner_Images/A20-SOM/Android/sd/A20_SOM_Android_4.22_SD_card_LCD_800x480_HDMI_release_1.img.7z A20-SOM Android for NAND with HDMI and 7 inch display support]

Build instructions and source files for the official Android images for A20 boards in this repository: https://github.com/hehopmajieh/olinuxino_configs
 

== Documents ==

=== A20 Brief ===

[https://github.com/OLIMEX/OLINUXINO/blob/master/HARDWARE/A20-PDFs/A20%20brief%2020130407.pdf A20-Brief description]

=== A20 Datasheet ===

[https://github.com/OLIMEX/OLINUXINO/blob/master/HARDWARE/A20-PDFs/A20%20Datasheet%20v1.0%2020130227.pdf A20 datasheet]

=== A20 User Manual ===
[https://github.com/OLIMEX/OLINUXINO/blob/master/HARDWARE/A20-PDFs/A20%20User%20Manual%202013-03-22.pdf A20 Users manual]

== Hardware ==
 
===Board Layout===
[[File:A20-SOM-1_top_named.jpg|675px]]

 

===Board dimensions===

[[File:a20-som_dimensions.png|675px]]

A20-SOM and A20-SOM-4GB basic dimensions in mils: [https://www.olimex.com/Products/SOM/A20/A20-SOM/resources/a20-som_dimensions.png click]

A20-SOM-EVB basic dimension in mils: [https://www.olimex.com/Products/SOM/A20/A20-SOM-EVB/resources/a20-som-evb_dimensions.png click]

===Power supply and consumption===

*'''A20-SOM''' 
A20-SOM typically consumes between 0.20A and 0.25A when connected to a 5V
voltage source (provided at pins GND and 5VEXT).

During heavy load of the processor the consumption might raise up to 0.35A
(tested with 'top d0').

The current consumed might have peaks as high as 0.50A @ 5V during start-up when
different modules are initialized.

Make sure your supply is capable of providing at least half an ampere of
current at 5V of voltage.

*'''A20-SOM + A20-SOM-EVB''' 
The consumption of the combination A20-SOM + A20-SOM-EVB is betwen 0.10A and 0.15A when the A20-SOM-EVB is connected to a 12V voltage source (provided at the board's PWR jack).

During heavy load of the processor the consumption might raise up to 0.20A @ 12V
(tested with 'top d0').

The current consumed might have peaks as high as 0.25A @ 12V during start-up when
different modules are initialized.

===CAD files===

A20-SOM is considered commercial, proprietary design. The board file is not available to the customer. A pdf extracted from the original schematic is available at GitHub: [https://github.com/OLIMEX/SOM/tree/master/A20/A20-SOM A20-SOM schematics]

KiCAD files of the connectors of A20-SOM/A20-SOM-EVB that are perfect as a template for own design can be found here: [https://github.com/OLIMEX/SOM/tree/master/A20/A20-SOM/KiCAD%20connector%20library KiCAD templates A20-SOM]

A20-SOM-EVB is considered Open Source Hardware, Eagle CAD files are available here [https://www.olimex.com/Products/SOM/A20/A20-SOM-EVB/resources/A20-SOM-EVB_eagle_sources.zip A20-SOM-EVB sources]

The CAD product used to design OLinuXino is Eagle and you can download evaluation free version from their [http://www.cadsoftusa.com/ web site]. The evaluation version allows you to inspect the schematic and the board file sources.

== How To? ==
 

=== Is it possible to boot Debian from NAND? Do you provide such image?===
Yes, it is possible. Use the latest Debian Jessie image and write "nandinstall". More information can be found in this wiki article: [[How_to_install_Debian_to_NAND| installing Debian Jessie to the 4GB NAND memory]]

There are other people who are also successful in booting Debian from the NAND. Make sure to check on the forum. Make sure to check the number of very good and optimized A20-OLinuXino Debian images by Igor Pečovnik. There are also his instructions for NAND installation of Debian: [http://www.armbian.com/download/ link to his web-site]

===How to correctly power off OLinuXino running from NAND Flash===
[http://olimex.wordpress.com/2014/01/24/how-to-correctly-power-off-olinuxino-running-android/ In this Blog post] we explain what are the problems. This is common problem for all computers running OS. [http://www.linux-mtd.infradead.org/doc/ubifs.html#L_ubifs_mlc Here] you can read more about MLC NAND Flash and Linux file system.

===How to build the official Debian Linux image for A20-SOM? ===

Build instructions and required files for the latest Debian Jessie images: [https://github.com/OLIMEX/OLINUXINO/tree/master/SOFTWARE/A20/A20-build-3.4.103-release-2 build instructions and required files at the GitHub page]

Build instructions and required files for the latest Debian Wheezy images: [https://github.com/OLIMEX/OLINUXINO/tree/master/SOFTWARE/A20/A20-build-3.4.90 instructions and files at the GitHub page]

===How to download new Android image to the NAND memory of my A20-SOM-4GB board?===

In order to download the Android image to the NAND memory of the board follow these steps:

1. Install and run PhoenixSuit (can be found here: [https://drive.google.com/file/d/0BwplT87k9SCgaTFTZnVST05ONzA/view?usp=sharing google drive location]).

2. Download and extract the latest official image - can be found above in the Android section of this article. Make sure that the download link you visit clearly indicates that the image is suitable for the NAND memory since there are images suitable for microSD card also. The images suitable for the microSD memory and those suitable for microSD card are different. However, the upload method is almost identical – using PhoenixSuit.

3. Go to firmware tab of the program and point to the already downloaded and extracted Android image.

4. Disconnect the power supply and USB cable from the A20 board.

5. Press and hold RECOVERY button, apply power supply (the requirement various depending on whether you use the board stand-alone or on top of A20-SOM-EVB), release RECOVERY button.

6. Connect USB cable to the mini USB connector.

7. You will be asked for drivers for the bootloader. Navigate to the folder where you extracted the PhoenixSuit and install the drivers from the respective executable (or manually point the installer to the drivers folder in the PhoenixSuit installation path).

8. PhoenixSuit will detect the board and would ask whether you wish to also of writing the image. Choose method of writing the image and confirm your wish to write the image.

9. Wait till upgrade succeeds

Note that it is not recommended to have your mini USB connected to an external USB hub. This might cause delays and might distort the signal levels. Always test with the USB connected straight to the USB ports of your computer.

===How do I write the official Android image to a micro SD card for my A20 board?===
A: First download one of the official Android images, which might be found in the Android section above.

Make sure that the download link you visit clearly indicates that the image is suitable for the microSD card since there are images suitable for NAND memory also. The images suitable for the microSD memory and those suitable for NAND card are different. However, the upload method is almost identical – using PhoenixSuit.

There are two types of Android images for microSD card that we usually provide and each of them has to be downloaded to a microSD card using a different method. The image provided for microSD card is either the native Android image that can be downloaded to the card via a software tool like PhoenixSuit (through the board) or an image taken from an already prepared microSD card that requires to simply write the image (through a microSD card reader).

'''It is more likely that you have an Android image that requires a simple copy to a card. If that is the case you can follow the exact steps as for Linux (e.g. using "Win32 Disk Imager" or "dd" command).'''

In order to prepare a microSD card with a native Android you will need a software tool called PhoenixSuit and then:

1. Install and run PhoenixSuit (can be found here: [https://drive.google.com/file/d/0BwplT87k9SCgaTFTZnVST05ONzA/view?usp=sharing download from google drive])

2. Go to the firmware tab of the program and point to a valid Android image (note that the images on Google drive are compressed and you have to extract the archives to .img files to be able write them with PhoenixSuit)

3. Disconnect the power supply and USB cable from the A20 board. Put an SD card in micro SD holder. We recommend 4GB class 10 card.

4. Press and hold RECOVERY button, apply power supply (the requirement various depending on whether you use the board stand-alone or on top of A20-SOM-EVB), release RECOVERY button.

5. Connect USB cable to the mini USB connector.

6. You will be asked for drivers for the boot-loader. Navigate to the folder where you extracted the PhoenixSuit and install the drivers from the respective executables (or manually point the installer to the drivers folder in the PhoenixSuit installation path).

7. PhoenixSuit will detect the board and would ask for the method of writing the image. Choose method of writing the image and confirm your wish to write the image.

8. Wait till upgrade succeeds

Note that it is not recommended to have your mini USB connected to an external USB hub. This
might cause delays and might distort the signal levels. Always test with the USB connected straight to the USB ports of your computer.

Important: When Android runs for very first time it takes several minutes to initialize all files and buffers please do not cut the power supply during this process! Also when fresh image is installed fast boot may be disabled, which means that when you apply power supply after few seconds Android will go in sleep mode and you have to press POWER button to start it, you can change to fast boot when you power off there is dialog box asking you if you want next boot to be fast boot, you have to check this box before you power off. Also note that you must do touch screen calibration when you run Android for very first time which might require a mouse.

===How do I write the Linux image to a micro SD card to use with my A20 board?===

To write a Linux image to an SD card under Windows we use Win32 Disk Imager):

*Download Win32 Disk Imager [http://sourceforge.net/projects/win32diskimager/ Win32 Disk Imager]
*Insert card
*Start program
*Select file
*Click "write"

To write a Linux image to an SD card under Linux:

For instance you have an image with the file name of "debian_2g.img". It would be downloaded to the SD card connected to a Linux machine using one of the following commands:

* # dd bs=4M oflag=sync if=debian_2g.img of=/dev/sdX
or
* # cp debian_2g.img /dev/sdX

where X is the uSD card.

===I don't have neither serial cable, nor HDMI monitor. I also can't access the local Ethernet network. Can I somehow access the board anyway?===

The latest official Debian Linux image allows the use the USB_OTG connector for SSH connection without the need of a LAN cable or a serial cable. You can use a mini USB cable connected between your host PC and the on-board mini USB connector. For connection convenience there is a DHCP server running specifically for USB0 interface. The DHCP server should give IP address to the new USB0 interface of your host PC so you can make SSH connection from your PC to the default board IP address of the USB0 interface – 192.168.2.1.

You can connect to the board using a mini USB cable and an SSH client (if you use Windows you might use "puTTY", for example) at address 192.168.2.1.

For Windows operating system - upon connection, the board should show up in "Windows Device Manager" as "RNDIS Ethernet Gadget". You might be asked to install a driver. The drivers can be found online as "RNDIS driver" (Remote Network Driver Interface Specification). The drivers are provided by Microsoft and they should be available for every Windows distribution - refer to the respective files and articles provided by Microsoft on how to install the required drivers.

===How to change HDMI, VGA and LCD resolutions in the official Debian image?===

The default SD card setup is made with settings for HDMI 720p/60Hz. If you want to change to some other LCD, VGA or HDMI resolution then you have to start change_display.sh script file in /root directory. When you are logged as super user in the board type:

For Debian Wheezy releases: ./change_display* (* = press 'tab' to auto-complete)
For Debian Jessie releases: change_display* (* = press 'tab' to auto-complete)

and press "Enter".

'''Note that the script should be executed as super user. Under the command line interface you are automatically logged as super user (user "root", password "olimex"). However, under the graphical environment you are not auto-logged as super user and you must type "sudo" before the command (in the GUI the super-user is "olimex" and the password is "olimex")'''

Then choose the resolution and the interface(LCD, HDMI or VGA). Note that the selection of a specific resolution is done by navigating with the arrow keys and pressing "space" button. Make sure the asterisk marks your selection properly.

The supported resolutions are:

'''For LCD:'''

*1. 4.3" (480x272)
*2. 7" (800x480)
*3. 10" (1024x600)
*4. 15.6" (1366x768)

Important: initially the boards are calibrated for a specific display. If you re-write the image (no matter whether the SD card or the NAND memory) you would need to use a mouse to calibrate the display initially. It might be impossible to calibrate it via touching the display.

'''For HDMI:'''

*0. 480i
*1. 576i
*2. 480p
*3. 576p
*4. 720p50
*5. 720p60
*6. 1080i50
*7. 1080i60
*8. 1080p24
*9. 1080p50
*10. 1080p60
*11. pal
*14. ntsc

'''For VGA:'''

*0. 1680x1050
*1. 1440x900
*2. 1360x768
*3. 1280x1024
*4. 1024x768
*5. 800x600
*6. 640x480
*7. 1920x1080
*8. 1280x720
 

===How to edit board configurations and definitions in the official Debian Linux? ===

Do you want a custom video resolution output? Do you need a different port definition? Do you need to change the hardware defitions of the board?

You would need to edit the board's script.bin/script.fex file. How to do it is described in a separate article: [[How_to_edit_board_configurations_and_definitions_in_the_official_Debian_Linux]].

===How to generate Arch Linux image?===

Recent forum post by user progmetalbg here: [https://www.olimex.com/forum/index.php?topic=4261.0| at Olimex forums]

[http://alarma20.wordpress.com/2013/09/13/howto-build-arch-linux-arm-for-a20-olinuxino-micro/ Older step by step instructions on how to build Arch Linux image for another A20 board]

===How to detect and enable the Ethernet controller (if it is disabled by default)? ===

Note: in the previous Debian releases the Ethernet was auto-detected and initialized during boot BUT this was causing big delays in the start-up of the board if you didn't want to use Ethernet or if there wasn't Ethernet cable connected.

You can enable it by following these two steps:

1. To check under what name the LAN is associated write "ifconfig –a"

2. If, for example, it is under eth0 name, then write: "dhclient eth0"

This should enable the Ethernet and then SSH would also be available.

===How to install Android on SD-card? ===

[http://olimex.wordpress.com/2013/10/02/android-4-2-2-images-for-a20-olinuxino-running-from-sd-card-is-updated-on-wiki/ Blog post about it]

===How to access UART, I2C, GPIOs under Android? ===

[http://olimex.wordpress.com/2013/10/02/a20-olinuxino-tools-for-android-released/ Use our Open Source OLinuXino A20-TOOLS]

===How to control PWM under Linux? ===

There is an article here: [[how to add pwm]]

===How to build the Android 4.2.2 image for A20-OLinuXino-MICRO? ===

First you need to Download the [http://dl.linux-sunxi.org/users/tsvetan/ANDROID-4.2.2-SDK2.0-KERNEL-3.4/ A20 SDK2.0 Linux Kernel 3.4]

Second you need to configure your environment read the instructions [http://source.android.com/source/initializing.html here]

Then Build the kernel, kernel modules and u-boot

cd lichee
./build.sh -psun7i_android

When done, continue with Bulding the android image:

cd ../android4.2
cd device/softwinner/
tar zxfv olinuxino-a20.tgz
cd ../../
source build/envsetup.sh
lunch #select olinuxino-a20_eng
extract-bsp
make -j4

Dave from Axon instruments wrote more detailed [http://axonjakarta.wordpress.com/2014/02/14/olimex-a20-android-building-4/ blog post] about how he generates the Android image]

A20-SOM

2023-09-01T05:38:36Z

LubOlimex: /* Old Linux images */

[[File:A20-SOM-1 jpeg.jpg|675px]]

Features:

*A20 dual core Cortex-A7 processor
*1GB DDR3 memory
*AXP209 PMU IC
*MicroSD card
*UART console
*4GB NAND Flash
*Status LEDs
*RESET, RECOVERY buttons
*6 connectors x 40 pin 0.05" step
 
== Official Images from OLIMEX ==

'''The recommended image for most of Olimex-made Linux boards is Olimage Linux, you can find information about it in the document here:'''

https://github.com/OLIMEX/OLINUXINO/blob/master/DOCUMENTS/OLIMAGE/Olimage-guide.pdf

'''Notice this wiki article refers to outdated images and practices, if using Olimage Linux, use the information only as a reference (do not take it literally)!'''

Note that only the microSD connector is suitable for booting the desired operating system, the SD-MMC connector is not suitable for booting since it is not a part of the boot sequence (refer to A20 datasheet).

=== Old Linux images ===

These Debian images should be downloaded to a microSD card. You need a properly set torrent client to download the official images - they are available only as torrents. You can install the Debian to the NAND or the eMMC of your board (if it comes with one). Information on booting Debian from the NAND or eMMC might be found in these wiki article: [[how to install Debian to NAND]]; [[how to install Debian to eMMC]]. Download locations for the official images might be found below:

'''ALWAYS FIRST TEST WITH LATEST OFFICIAL IMAGE, NEWER HARDWARE REVISIONS OF THE BOARD MIGHT NOT WORK WITH OLDER IMAGES!!!'''

----

'''Latest stable official image - Debian 9 (Jessie)''' '''(recommended for all board revisions)''':'''

FTP download location for the official Debian Jessie release #10 (suitable for boards with NAND): [https://ftp.olimex.com/Allwinner_Images/A20-SOM/Debian/sd/a20-SOM_mainline_uboot_GMAC_master_sunxi_kernel_3.4.103_jessie_NAND_rel_10.img.7z A20-SOM Debian Jessie with kernel 3.4.103+ for boards with NAND flash memory release 10]

FTP download for A20-SOM (suitable for boards with eMMC): [https://ftp.olimex.com/Allwinner_Images/A20-OLinuXino/2.legacy_images_kernel_3.4.x/boards_with_eMMC/a20-SOM_mainline_uboot_GMAC_master_sunxi_kernel_3.4.103_jessie_eMMC_SPI_rel_13.zip A20-SOM Debian Jessie with kernel 3.4.103+ for boards with eMMC flash memory release 13] you might also want to check this document on how to get boards boot from eMMC if you have troubles: [https://ftp.olimex.com/Allwinner_Images/A20-OLinuXino/2.legacy_images_kernel_3.4.x/boards_with_eMMC/sunxi-spi-emmc/ how to boot from eMMC with newer boards with 5.1 eMMC]

Image description and typical interfacing: [https://raw.githubusercontent.com/OLIMEX/OLINUXINO/master/SOFTWARE/A20/A20-build-3.4.103-release-7/USAGE-AND-COMMON-PRACTICEs-A20-Olimex_kernel_3.4.103%2B_Jessie_rel_3.txt description and basic usage of different peripherals at at the GitHub page]

Image build instructions and required files for latest Debian Jessie release might be found here: [https://github.com/OLIMEX/OLINUXINO/raw/master/SOFTWARE/A20/A20-build-3.4.103-release-7/BUILD_DESCRIPTION_A20_Olimex_kernel_3.4.103%2B_Jessie_rel_6.txt build instructions and required files at the GitHub page]

You can find some older releases and older build instructions (older image revisions might be used as a reference, for testing purposes, or if you own old hardware revision of the board) at the following article: [[A20-SOM-older-releases|older releases and older build instructions]]

----

Note: in the previous Debian releases the Ethernet was auto-detected and initialized during boot BUT this caused big delays in the start-up of the board if you didn't want to use Ethernet or if there wasn't Ethernet cable connected.

You can enable it by following these two steps:

1. To check under what name the LAN is associated write "ifconfig –a"

2. If, for example, it is under eth0 name, then write: "dhclient eth0"

This should enable the Ethernet and then SSH would also be available.

The Debian Linux file system can be extended to suit a bigger card. If the whole SD card is not used, use the following three commands to execute a script that would use all the free space of your card:

sudo su
resize_sd.sh /dev/mmcblk0 2
reboot

=== Android images ===

Links to official Android releases are below. Please read description of the image carefully.

Direct download of Android 4.2.2 release 1 for NAND memory (with HDMI and 800x480 support): [https://ftp.olimex.com/Allwinner_Images/A20-SOM/Android/nand/A20_SOM_camera_LCD7_HDMI_release1.img A20-SOM Android for NAND with HDMI and 7 inch display support]

Direct download of Android 4.2.2 release 1 for microSD card (with HDMI and 800x480 support):
[https://ftp.olimex.com/Allwinner_Images/A20-SOM/Android/sd/A20_SOM_Android_4.22_SD_card_LCD_800x480_HDMI_release_1.img.7z A20-SOM Android for NAND with HDMI and 7 inch display support]

Build instructions and source files for the official Android images for A20 boards in this repository: https://github.com/hehopmajieh/olinuxino_configs
 

== Documents ==

=== A20 Brief ===

[https://github.com/OLIMEX/OLINUXINO/blob/master/HARDWARE/A20-PDFs/A20%20brief%2020130407.pdf A20-Brief description]

=== A20 Datasheet ===

[https://github.com/OLIMEX/OLINUXINO/blob/master/HARDWARE/A20-PDFs/A20%20Datasheet%20v1.0%2020130227.pdf A20 datasheet]

=== A20 User Manual ===
[https://github.com/OLIMEX/OLINUXINO/blob/master/HARDWARE/A20-PDFs/A20%20User%20Manual%202013-03-22.pdf A20 Users manual]

== Hardware ==
 
===Board Layout===
[[File:A20-SOM-1_top_named.jpg|675px]]

 

===Board dimensions===

[[File:a20-som_dimensions.png|675px]]

A20-SOM and A20-SOM-4GB basic dimensions in mils: [https://www.olimex.com/Products/SOM/A20/A20-SOM/resources/a20-som_dimensions.png click]

A20-SOM-EVB basic dimension in mils: [https://www.olimex.com/Products/SOM/A20/A20-SOM-EVB/resources/a20-som-evb_dimensions.png click]

===Power supply and consumption===

*'''A20-SOM''' 
A20-SOM typically consumes between 0.20A and 0.25A when connected to a 5V
voltage source (provided at pins GND and 5VEXT).

During heavy load of the processor the consumption might raise up to 0.35A
(tested with 'top d0').

The current consumed might have peaks as high as 0.50A @ 5V during start-up when
different modules are initialized.

Make sure your supply is capable of providing at least half an ampere of
current at 5V of voltage.

*'''A20-SOM + A20-SOM-EVB''' 
The consumption of the combination A20-SOM + A20-SOM-EVB is betwen 0.10A and 0.15A when the A20-SOM-EVB is connected to a 12V voltage source (provided at the board's PWR jack).

During heavy load of the processor the consumption might raise up to 0.20A @ 12V
(tested with 'top d0').

The current consumed might have peaks as high as 0.25A @ 12V during start-up when
different modules are initialized.

===CAD files===

A20-SOM is considered commercial, proprietary design. The board file is not available to the customer. A pdf extracted from the original schematic is available at GitHub: [https://github.com/OLIMEX/SOM/tree/master/A20/A20-SOM A20-SOM schematics]

KiCAD files of the connectors of A20-SOM/A20-SOM-EVB that are perfect as a template for own design can be found here: [https://github.com/OLIMEX/SOM/tree/master/A20/A20-SOM/KiCAD%20connector%20library KiCAD templates A20-SOM]

A20-SOM-EVB is considered Open Source Hardware, Eagle CAD files are available here [https://www.olimex.com/Products/SOM/A20/A20-SOM-EVB/resources/A20-SOM-EVB_eagle_sources.zip A20-SOM-EVB sources]

The CAD product used to design OLinuXino is Eagle and you can download evaluation free version from their [http://www.cadsoftusa.com/ web site]. The evaluation version allows you to inspect the schematic and the board file sources.

== How To? ==
 

=== Is it possible to boot Debian from NAND? Do you provide such image?===
Yes, it is possible. Use the latest Debian Jessie image and write "nandinstall". More information can be found in this wiki article: [[How_to_install_Debian_to_NAND| installing Debian Jessie to the 4GB NAND memory]]

There are other people who are also successful in booting Debian from the NAND. Make sure to check on the forum. Make sure to check the number of very good and optimized A20-OLinuXino Debian images by Igor Pečovnik. There are also his instructions for NAND installation of Debian: [http://www.armbian.com/download/ link to his web-site]

===How to correctly power off OLinuXino running from NAND Flash===
[http://olimex.wordpress.com/2014/01/24/how-to-correctly-power-off-olinuxino-running-android/ In this Blog post] we explain what are the problems. This is common problem for all computers running OS. [http://www.linux-mtd.infradead.org/doc/ubifs.html#L_ubifs_mlc Here] you can read more about MLC NAND Flash and Linux file system.

===How to build the official Debian Linux image for A20-SOM? ===

Build instructions and required files for the latest Debian Jessie images: [https://github.com/OLIMEX/OLINUXINO/tree/master/SOFTWARE/A20/A20-build-3.4.103-release-2 build instructions and required files at the GitHub page]

Build instructions and required files for the latest Debian Wheezy images: [https://github.com/OLIMEX/OLINUXINO/tree/master/SOFTWARE/A20/A20-build-3.4.90 instructions and files at the GitHub page]

===How to download new Android image to the NAND memory of my A20-SOM-4GB board?===

In order to download the Android image to the NAND memory of the board follow these steps:

1. Install and run PhoenixSuit (can be found here: [https://drive.google.com/file/d/0BwplT87k9SCgaTFTZnVST05ONzA/view?usp=sharing google drive location]).

2. Download and extract the latest official image - can be found above in the Android section of this article. Make sure that the download link you visit clearly indicates that the image is suitable for the NAND memory since there are images suitable for microSD card also. The images suitable for the microSD memory and those suitable for microSD card are different. However, the upload method is almost identical – using PhoenixSuit.

3. Go to firmware tab of the program and point to the already downloaded and extracted Android image.

4. Disconnect the power supply and USB cable from the A20 board.

5. Press and hold RECOVERY button, apply power supply (the requirement various depending on whether you use the board stand-alone or on top of A20-SOM-EVB), release RECOVERY button.

6. Connect USB cable to the mini USB connector.

7. You will be asked for drivers for the bootloader. Navigate to the folder where you extracted the PhoenixSuit and install the drivers from the respective executable (or manually point the installer to the drivers folder in the PhoenixSuit installation path).

8. PhoenixSuit will detect the board and would ask whether you wish to also of writing the image. Choose method of writing the image and confirm your wish to write the image.

9. Wait till upgrade succeeds

Note that it is not recommended to have your mini USB connected to an external USB hub. This might cause delays and might distort the signal levels. Always test with the USB connected straight to the USB ports of your computer.

===How do I write the official Android image to a micro SD card for my A20 board?===
A: First download one of the official Android images, which might be found in the Android section above.

Make sure that the download link you visit clearly indicates that the image is suitable for the microSD card since there are images suitable for NAND memory also. The images suitable for the microSD memory and those suitable for NAND card are different. However, the upload method is almost identical – using PhoenixSuit.

There are two types of Android images for microSD card that we usually provide and each of them has to be downloaded to a microSD card using a different method. The image provided for microSD card is either the native Android image that can be downloaded to the card via a software tool like PhoenixSuit (through the board) or an image taken from an already prepared microSD card that requires to simply write the image (through a microSD card reader).

'''It is more likely that you have an Android image that requires a simple copy to a card. If that is the case you can follow the exact steps as for Linux (e.g. using "Win32 Disk Imager" or "dd" command).'''

In order to prepare a microSD card with a native Android you will need a software tool called PhoenixSuit and then:

1. Install and run PhoenixSuit (can be found here: [https://drive.google.com/file/d/0BwplT87k9SCgaTFTZnVST05ONzA/view?usp=sharing download from google drive])

2. Go to the firmware tab of the program and point to a valid Android image (note that the images on Google drive are compressed and you have to extract the archives to .img files to be able write them with PhoenixSuit)

3. Disconnect the power supply and USB cable from the A20 board. Put an SD card in micro SD holder. We recommend 4GB class 10 card.

4. Press and hold RECOVERY button, apply power supply (the requirement various depending on whether you use the board stand-alone or on top of A20-SOM-EVB), release RECOVERY button.

5. Connect USB cable to the mini USB connector.

6. You will be asked for drivers for the boot-loader. Navigate to the folder where you extracted the PhoenixSuit and install the drivers from the respective executables (or manually point the installer to the drivers folder in the PhoenixSuit installation path).

7. PhoenixSuit will detect the board and would ask for the method of writing the image. Choose method of writing the image and confirm your wish to write the image.

8. Wait till upgrade succeeds

Note that it is not recommended to have your mini USB connected to an external USB hub. This
might cause delays and might distort the signal levels. Always test with the USB connected straight to the USB ports of your computer.

Important: When Android runs for very first time it takes several minutes to initialize all files and buffers please do not cut the power supply during this process! Also when fresh image is installed fast boot may be disabled, which means that when you apply power supply after few seconds Android will go in sleep mode and you have to press POWER button to start it, you can change to fast boot when you power off there is dialog box asking you if you want next boot to be fast boot, you have to check this box before you power off. Also note that you must do touch screen calibration when you run Android for very first time which might require a mouse.

===How do I write the Linux image to a micro SD card to use with my A20 board?===

To write a Linux image to an SD card under Windows we use Win32 Disk Imager):

*Download Win32 Disk Imager [http://sourceforge.net/projects/win32diskimager/ Win32 Disk Imager]
*Insert card
*Start program
*Select file
*Click "write"

To write a Linux image to an SD card under Linux:

For instance you have an image with the file name of "debian_2g.img". It would be downloaded to the SD card connected to a Linux machine using one of the following commands:

* # dd bs=4M oflag=sync if=debian_2g.img of=/dev/sdX
or
* # cp debian_2g.img /dev/sdX

where X is the uSD card.

===I don't have neither serial cable, nor HDMI monitor. I also can't access the local Ethernet network. Can I somehow access the board anyway?===

The latest official Debian Linux image allows the use the USB_OTG connector for SSH connection without the need of a LAN cable or a serial cable. You can use a mini USB cable connected between your host PC and the on-board mini USB connector. For connection convenience there is a DHCP server running specifically for USB0 interface. The DHCP server should give IP address to the new USB0 interface of your host PC so you can make SSH connection from your PC to the default board IP address of the USB0 interface – 192.168.2.1.

You can connect to the board using a mini USB cable and an SSH client (if you use Windows you might use "puTTY", for example) at address 192.168.2.1.

For Windows operating system - upon connection, the board should show up in "Windows Device Manager" as "RNDIS Ethernet Gadget". You might be asked to install a driver. The drivers can be found online as "RNDIS driver" (Remote Network Driver Interface Specification). The drivers are provided by Microsoft and they should be available for every Windows distribution - refer to the respective files and articles provided by Microsoft on how to install the required drivers.

===How to change HDMI, VGA and LCD resolutions in the official Debian image?===

The default SD card setup is made with settings for HDMI 720p/60Hz. If you want to change to some other LCD, VGA or HDMI resolution then you have to start change_display.sh script file in /root directory. When you are logged as super user in the board type:

For Debian Wheezy releases: ./change_display* (* = press 'tab' to auto-complete)
For Debian Jessie releases: change_display* (* = press 'tab' to auto-complete)

and press "Enter".

'''Note that the script should be executed as super user. Under the command line interface you are automatically logged as super user (user "root", password "olimex"). However, under the graphical environment you are not auto-logged as super user and you must type "sudo" before the command (in the GUI the super-user is "olimex" and the password is "olimex")'''

Then choose the resolution and the interface(LCD, HDMI or VGA). Note that the selection of a specific resolution is done by navigating with the arrow keys and pressing "space" button. Make sure the asterisk marks your selection properly.

The supported resolutions are:

'''For LCD:'''

*1. 4.3" (480x272)
*2. 7" (800x480)
*3. 10" (1024x600)
*4. 15.6" (1366x768)

Important: initially the boards are calibrated for a specific display. If you re-write the image (no matter whether the SD card or the NAND memory) you would need to use a mouse to calibrate the display initially. It might be impossible to calibrate it via touching the display.

'''For HDMI:'''

*0. 480i
*1. 576i
*2. 480p
*3. 576p
*4. 720p50
*5. 720p60
*6. 1080i50
*7. 1080i60
*8. 1080p24
*9. 1080p50
*10. 1080p60
*11. pal
*14. ntsc

'''For VGA:'''

*0. 1680x1050
*1. 1440x900
*2. 1360x768
*3. 1280x1024
*4. 1024x768
*5. 800x600
*6. 640x480
*7. 1920x1080
*8. 1280x720
 

===How to edit board configurations and definitions in the official Debian Linux? ===

Do you want a custom video resolution output? Do you need a different port definition? Do you need to change the hardware defitions of the board?

You would need to edit the board's script.bin/script.fex file. How to do it is described in a separate article: [[How_to_edit_board_configurations_and_definitions_in_the_official_Debian_Linux]].

===How to generate Arch Linux image?===

Recent forum post by user progmetalbg here: [https://www.olimex.com/forum/index.php?topic=4261.0| at Olimex forums]

[http://alarma20.wordpress.com/2013/09/13/howto-build-arch-linux-arm-for-a20-olinuxino-micro/ Older step by step instructions on how to build Arch Linux image for another A20 board]

===How to detect and enable the Ethernet controller (if it is disabled by default)? ===

Note: in the previous Debian releases the Ethernet was auto-detected and initialized during boot BUT this was causing big delays in the start-up of the board if you didn't want to use Ethernet or if there wasn't Ethernet cable connected.

You can enable it by following these two steps:

1. To check under what name the LAN is associated write "ifconfig –a"

2. If, for example, it is under eth0 name, then write: "dhclient eth0"

This should enable the Ethernet and then SSH would also be available.

===How to install Android on SD-card? ===

[http://olimex.wordpress.com/2013/10/02/android-4-2-2-images-for-a20-olinuxino-running-from-sd-card-is-updated-on-wiki/ Blog post about it]

===How to access UART, I2C, GPIOs under Android? ===

[http://olimex.wordpress.com/2013/10/02/a20-olinuxino-tools-for-android-released/ Use our Open Source OLinuXino A20-TOOLS]

===How to control PWM under Linux? ===

There is an article here: [[how to add pwm]]

===How to build the Android 4.2.2 image for A20-OLinuXino-MICRO? ===

First you need to Download the [http://dl.linux-sunxi.org/users/tsvetan/ANDROID-4.2.2-SDK2.0-KERNEL-3.4/ A20 SDK2.0 Linux Kernel 3.4]

Second you need to configure your environment read the instructions [http://source.android.com/source/initializing.html here]

Then Build the kernel, kernel modules and u-boot

cd lichee
./build.sh -psun7i_android

When done, continue with Bulding the android image:

cd ../android4.2
cd device/softwinner/
tar zxfv olinuxino-a20.tgz
cd ../../
source build/envsetup.sh
lunch #select olinuxino-a20_eng
extract-bsp
make -j4

Dave from Axon instruments wrote more detailed [http://axonjakarta.wordpress.com/2014/02/14/olimex-a20-android-building-4/ blog post] about how he generates the Android image]

A20-SOM

2023-08-31T13:56:03Z

LubOlimex: /* Old Linux images */

[[File:A20-SOM-1 jpeg.jpg|675px]]

Features:

*A20 dual core Cortex-A7 processor
*1GB DDR3 memory
*AXP209 PMU IC
*MicroSD card
*UART console
*4GB NAND Flash
*Status LEDs
*RESET, RECOVERY buttons
*6 connectors x 40 pin 0.05" step
 
== Official Images from OLIMEX ==

'''The recommended image for most of Olimex-made Linux boards is Olimage Linux, you can find information about it in the document here:'''

https://github.com/OLIMEX/OLINUXINO/blob/master/DOCUMENTS/OLIMAGE/Olimage-guide.pdf

'''Notice this wiki article refers to outdated images and practices, if using Olimage Linux, use the information only as a reference (do not take it literally)!'''

Note that only the microSD connector is suitable for booting the desired operating system, the SD-MMC connector is not suitable for booting since it is not a part of the boot sequence (refer to A20 datasheet).

=== Old Linux images ===

These Debian images should be downloaded to a microSD card. You need a properly set torrent client to download the official images - they are available only as torrents. You can install the Debian to the NAND or the eMMC of your board (if it comes with one). Information on booting Debian from the NAND or eMMC might be found in these wiki article: [[how to install Debian to NAND]]; [[how to install Debian to eMMC]]. Download locations for the official images might be found below:

'''ALWAYS FIRST TEST WITH LATEST OFFICIAL IMAGE, NEWER HARDWARE REVISIONS OF THE BOARD MIGHT NOT WORK WITH OLDER IMAGES!!!'''

----

'''Latest stable official image - Debian 9 (Jessie)''' '''(recommended for all board revisions)''':'''

FTP download location for the official Debian Jessie release #10 (suitable for boards with NAND): [https://ftp.olimex.com/Allwinner_Images/A20-SOM/Debian/sd/a20-SOM_mainline_uboot_GMAC_master_sunxi_kernel_3.4.103_jessie_NAND_rel_10.img.7z A20-SOM Debian Jessie with kernel 3.4.103+ for boards with NAND flash memory release 10]

FTP download for A20-SOM (suitable for boards with eMMC): [https://ftp.olimex.com/Allwinner_Images/A20-OLinuXino/2.legacy_images_kernel_3.4.x/boards_with_eMMC/a20-SOM_mainline_uboot_GMAC_master_sunxi_kernel_3.4.103_jessie_eMMC_SPI_rel_13.zip A20-SOM Debian Jessie with kernel 3.4.103+ for boards with eMMC flash memory release 13]

Image description and typical interfacing: [https://raw.githubusercontent.com/OLIMEX/OLINUXINO/master/SOFTWARE/A20/A20-build-3.4.103-release-7/USAGE-AND-COMMON-PRACTICEs-A20-Olimex_kernel_3.4.103%2B_Jessie_rel_3.txt description and basic usage of different peripherals at at the GitHub page]

Image build instructions and required files for latest Debian Jessie release might be found here: [https://github.com/OLIMEX/OLINUXINO/raw/master/SOFTWARE/A20/A20-build-3.4.103-release-7/BUILD_DESCRIPTION_A20_Olimex_kernel_3.4.103%2B_Jessie_rel_6.txt build instructions and required files at the GitHub page]

You can find some older releases and older build instructions (older image revisions might be used as a reference, for testing purposes, or if you own old hardware revision of the board) at the following article: [[A20-SOM-older-releases|older releases and older build instructions]]

----

Note: in the previous Debian releases the Ethernet was auto-detected and initialized during boot BUT this caused big delays in the start-up of the board if you didn't want to use Ethernet or if there wasn't Ethernet cable connected.

You can enable it by following these two steps:

1. To check under what name the LAN is associated write "ifconfig –a"

2. If, for example, it is under eth0 name, then write: "dhclient eth0"

This should enable the Ethernet and then SSH would also be available.

The Debian Linux file system can be extended to suit a bigger card. If the whole SD card is not used, use the following three commands to execute a script that would use all the free space of your card:

sudo su
resize_sd.sh /dev/mmcblk0 2
reboot

=== Android images ===

Links to official Android releases are below. Please read description of the image carefully.

Direct download of Android 4.2.2 release 1 for NAND memory (with HDMI and 800x480 support): [https://ftp.olimex.com/Allwinner_Images/A20-SOM/Android/nand/A20_SOM_camera_LCD7_HDMI_release1.img A20-SOM Android for NAND with HDMI and 7 inch display support]

Direct download of Android 4.2.2 release 1 for microSD card (with HDMI and 800x480 support):
[https://ftp.olimex.com/Allwinner_Images/A20-SOM/Android/sd/A20_SOM_Android_4.22_SD_card_LCD_800x480_HDMI_release_1.img.7z A20-SOM Android for NAND with HDMI and 7 inch display support]

Build instructions and source files for the official Android images for A20 boards in this repository: https://github.com/hehopmajieh/olinuxino_configs
 

== Documents ==

=== A20 Brief ===

[https://github.com/OLIMEX/OLINUXINO/blob/master/HARDWARE/A20-PDFs/A20%20brief%2020130407.pdf A20-Brief description]

=== A20 Datasheet ===

[https://github.com/OLIMEX/OLINUXINO/blob/master/HARDWARE/A20-PDFs/A20%20Datasheet%20v1.0%2020130227.pdf A20 datasheet]

=== A20 User Manual ===
[https://github.com/OLIMEX/OLINUXINO/blob/master/HARDWARE/A20-PDFs/A20%20User%20Manual%202013-03-22.pdf A20 Users manual]

== Hardware ==
 
===Board Layout===
[[File:A20-SOM-1_top_named.jpg|675px]]

 

===Board dimensions===

[[File:a20-som_dimensions.png|675px]]

A20-SOM and A20-SOM-4GB basic dimensions in mils: [https://www.olimex.com/Products/SOM/A20/A20-SOM/resources/a20-som_dimensions.png click]

A20-SOM-EVB basic dimension in mils: [https://www.olimex.com/Products/SOM/A20/A20-SOM-EVB/resources/a20-som-evb_dimensions.png click]

===Power supply and consumption===

*'''A20-SOM''' 
A20-SOM typically consumes between 0.20A and 0.25A when connected to a 5V
voltage source (provided at pins GND and 5VEXT).

During heavy load of the processor the consumption might raise up to 0.35A
(tested with 'top d0').

The current consumed might have peaks as high as 0.50A @ 5V during start-up when
different modules are initialized.

Make sure your supply is capable of providing at least half an ampere of
current at 5V of voltage.

*'''A20-SOM + A20-SOM-EVB''' 
The consumption of the combination A20-SOM + A20-SOM-EVB is betwen 0.10A and 0.15A when the A20-SOM-EVB is connected to a 12V voltage source (provided at the board's PWR jack).

During heavy load of the processor the consumption might raise up to 0.20A @ 12V
(tested with 'top d0').

The current consumed might have peaks as high as 0.25A @ 12V during start-up when
different modules are initialized.

===CAD files===

A20-SOM is considered commercial, proprietary design. The board file is not available to the customer. A pdf extracted from the original schematic is available at GitHub: [https://github.com/OLIMEX/SOM/tree/master/A20/A20-SOM A20-SOM schematics]

KiCAD files of the connectors of A20-SOM/A20-SOM-EVB that are perfect as a template for own design can be found here: [https://github.com/OLIMEX/SOM/tree/master/A20/A20-SOM/KiCAD%20connector%20library KiCAD templates A20-SOM]

A20-SOM-EVB is considered Open Source Hardware, Eagle CAD files are available here [https://www.olimex.com/Products/SOM/A20/A20-SOM-EVB/resources/A20-SOM-EVB_eagle_sources.zip A20-SOM-EVB sources]

The CAD product used to design OLinuXino is Eagle and you can download evaluation free version from their [http://www.cadsoftusa.com/ web site]. The evaluation version allows you to inspect the schematic and the board file sources.

== How To? ==
 

=== Is it possible to boot Debian from NAND? Do you provide such image?===
Yes, it is possible. Use the latest Debian Jessie image and write "nandinstall". More information can be found in this wiki article: [[How_to_install_Debian_to_NAND| installing Debian Jessie to the 4GB NAND memory]]

There are other people who are also successful in booting Debian from the NAND. Make sure to check on the forum. Make sure to check the number of very good and optimized A20-OLinuXino Debian images by Igor Pečovnik. There are also his instructions for NAND installation of Debian: [http://www.armbian.com/download/ link to his web-site]

===How to correctly power off OLinuXino running from NAND Flash===
[http://olimex.wordpress.com/2014/01/24/how-to-correctly-power-off-olinuxino-running-android/ In this Blog post] we explain what are the problems. This is common problem for all computers running OS. [http://www.linux-mtd.infradead.org/doc/ubifs.html#L_ubifs_mlc Here] you can read more about MLC NAND Flash and Linux file system.

===How to build the official Debian Linux image for A20-SOM? ===

Build instructions and required files for the latest Debian Jessie images: [https://github.com/OLIMEX/OLINUXINO/tree/master/SOFTWARE/A20/A20-build-3.4.103-release-2 build instructions and required files at the GitHub page]

Build instructions and required files for the latest Debian Wheezy images: [https://github.com/OLIMEX/OLINUXINO/tree/master/SOFTWARE/A20/A20-build-3.4.90 instructions and files at the GitHub page]

===How to download new Android image to the NAND memory of my A20-SOM-4GB board?===

In order to download the Android image to the NAND memory of the board follow these steps:

1. Install and run PhoenixSuit (can be found here: [https://drive.google.com/file/d/0BwplT87k9SCgaTFTZnVST05ONzA/view?usp=sharing google drive location]).

2. Download and extract the latest official image - can be found above in the Android section of this article. Make sure that the download link you visit clearly indicates that the image is suitable for the NAND memory since there are images suitable for microSD card also. The images suitable for the microSD memory and those suitable for microSD card are different. However, the upload method is almost identical – using PhoenixSuit.

3. Go to firmware tab of the program and point to the already downloaded and extracted Android image.

4. Disconnect the power supply and USB cable from the A20 board.

5. Press and hold RECOVERY button, apply power supply (the requirement various depending on whether you use the board stand-alone or on top of A20-SOM-EVB), release RECOVERY button.

6. Connect USB cable to the mini USB connector.

7. You will be asked for drivers for the bootloader. Navigate to the folder where you extracted the PhoenixSuit and install the drivers from the respective executable (or manually point the installer to the drivers folder in the PhoenixSuit installation path).

8. PhoenixSuit will detect the board and would ask whether you wish to also of writing the image. Choose method of writing the image and confirm your wish to write the image.

9. Wait till upgrade succeeds

Note that it is not recommended to have your mini USB connected to an external USB hub. This might cause delays and might distort the signal levels. Always test with the USB connected straight to the USB ports of your computer.

===How do I write the official Android image to a micro SD card for my A20 board?===
A: First download one of the official Android images, which might be found in the Android section above.

Make sure that the download link you visit clearly indicates that the image is suitable for the microSD card since there are images suitable for NAND memory also. The images suitable for the microSD memory and those suitable for NAND card are different. However, the upload method is almost identical – using PhoenixSuit.

There are two types of Android images for microSD card that we usually provide and each of them has to be downloaded to a microSD card using a different method. The image provided for microSD card is either the native Android image that can be downloaded to the card via a software tool like PhoenixSuit (through the board) or an image taken from an already prepared microSD card that requires to simply write the image (through a microSD card reader).

'''It is more likely that you have an Android image that requires a simple copy to a card. If that is the case you can follow the exact steps as for Linux (e.g. using "Win32 Disk Imager" or "dd" command).'''

In order to prepare a microSD card with a native Android you will need a software tool called PhoenixSuit and then:

1. Install and run PhoenixSuit (can be found here: [https://drive.google.com/file/d/0BwplT87k9SCgaTFTZnVST05ONzA/view?usp=sharing download from google drive])

2. Go to the firmware tab of the program and point to a valid Android image (note that the images on Google drive are compressed and you have to extract the archives to .img files to be able write them with PhoenixSuit)

3. Disconnect the power supply and USB cable from the A20 board. Put an SD card in micro SD holder. We recommend 4GB class 10 card.

4. Press and hold RECOVERY button, apply power supply (the requirement various depending on whether you use the board stand-alone or on top of A20-SOM-EVB), release RECOVERY button.

5. Connect USB cable to the mini USB connector.

6. You will be asked for drivers for the boot-loader. Navigate to the folder where you extracted the PhoenixSuit and install the drivers from the respective executables (or manually point the installer to the drivers folder in the PhoenixSuit installation path).

7. PhoenixSuit will detect the board and would ask for the method of writing the image. Choose method of writing the image and confirm your wish to write the image.

8. Wait till upgrade succeeds

Note that it is not recommended to have your mini USB connected to an external USB hub. This
might cause delays and might distort the signal levels. Always test with the USB connected straight to the USB ports of your computer.

Important: When Android runs for very first time it takes several minutes to initialize all files and buffers please do not cut the power supply during this process! Also when fresh image is installed fast boot may be disabled, which means that when you apply power supply after few seconds Android will go in sleep mode and you have to press POWER button to start it, you can change to fast boot when you power off there is dialog box asking you if you want next boot to be fast boot, you have to check this box before you power off. Also note that you must do touch screen calibration when you run Android for very first time which might require a mouse.

===How do I write the Linux image to a micro SD card to use with my A20 board?===

To write a Linux image to an SD card under Windows we use Win32 Disk Imager):

*Download Win32 Disk Imager [http://sourceforge.net/projects/win32diskimager/ Win32 Disk Imager]
*Insert card
*Start program
*Select file
*Click "write"

To write a Linux image to an SD card under Linux:

For instance you have an image with the file name of "debian_2g.img". It would be downloaded to the SD card connected to a Linux machine using one of the following commands:

* # dd bs=4M oflag=sync if=debian_2g.img of=/dev/sdX
or
* # cp debian_2g.img /dev/sdX

where X is the uSD card.

===I don't have neither serial cable, nor HDMI monitor. I also can't access the local Ethernet network. Can I somehow access the board anyway?===

The latest official Debian Linux image allows the use the USB_OTG connector for SSH connection without the need of a LAN cable or a serial cable. You can use a mini USB cable connected between your host PC and the on-board mini USB connector. For connection convenience there is a DHCP server running specifically for USB0 interface. The DHCP server should give IP address to the new USB0 interface of your host PC so you can make SSH connection from your PC to the default board IP address of the USB0 interface – 192.168.2.1.

You can connect to the board using a mini USB cable and an SSH client (if you use Windows you might use "puTTY", for example) at address 192.168.2.1.

For Windows operating system - upon connection, the board should show up in "Windows Device Manager" as "RNDIS Ethernet Gadget". You might be asked to install a driver. The drivers can be found online as "RNDIS driver" (Remote Network Driver Interface Specification). The drivers are provided by Microsoft and they should be available for every Windows distribution - refer to the respective files and articles provided by Microsoft on how to install the required drivers.

===How to change HDMI, VGA and LCD resolutions in the official Debian image?===

The default SD card setup is made with settings for HDMI 720p/60Hz. If you want to change to some other LCD, VGA or HDMI resolution then you have to start change_display.sh script file in /root directory. When you are logged as super user in the board type:

For Debian Wheezy releases: ./change_display* (* = press 'tab' to auto-complete)
For Debian Jessie releases: change_display* (* = press 'tab' to auto-complete)

and press "Enter".

'''Note that the script should be executed as super user. Under the command line interface you are automatically logged as super user (user "root", password "olimex"). However, under the graphical environment you are not auto-logged as super user and you must type "sudo" before the command (in the GUI the super-user is "olimex" and the password is "olimex")'''

Then choose the resolution and the interface(LCD, HDMI or VGA). Note that the selection of a specific resolution is done by navigating with the arrow keys and pressing "space" button. Make sure the asterisk marks your selection properly.

The supported resolutions are:

'''For LCD:'''

*1. 4.3" (480x272)
*2. 7" (800x480)
*3. 10" (1024x600)
*4. 15.6" (1366x768)

Important: initially the boards are calibrated for a specific display. If you re-write the image (no matter whether the SD card or the NAND memory) you would need to use a mouse to calibrate the display initially. It might be impossible to calibrate it via touching the display.

'''For HDMI:'''

*0. 480i
*1. 576i
*2. 480p
*3. 576p
*4. 720p50
*5. 720p60
*6. 1080i50
*7. 1080i60
*8. 1080p24
*9. 1080p50
*10. 1080p60
*11. pal
*14. ntsc

'''For VGA:'''

*0. 1680x1050
*1. 1440x900
*2. 1360x768
*3. 1280x1024
*4. 1024x768
*5. 800x600
*6. 640x480
*7. 1920x1080
*8. 1280x720
 

===How to edit board configurations and definitions in the official Debian Linux? ===

Do you want a custom video resolution output? Do you need a different port definition? Do you need to change the hardware defitions of the board?

You would need to edit the board's script.bin/script.fex file. How to do it is described in a separate article: [[How_to_edit_board_configurations_and_definitions_in_the_official_Debian_Linux]].

===How to generate Arch Linux image?===

Recent forum post by user progmetalbg here: [https://www.olimex.com/forum/index.php?topic=4261.0| at Olimex forums]

[http://alarma20.wordpress.com/2013/09/13/howto-build-arch-linux-arm-for-a20-olinuxino-micro/ Older step by step instructions on how to build Arch Linux image for another A20 board]

===How to detect and enable the Ethernet controller (if it is disabled by default)? ===

Note: in the previous Debian releases the Ethernet was auto-detected and initialized during boot BUT this was causing big delays in the start-up of the board if you didn't want to use Ethernet or if there wasn't Ethernet cable connected.

You can enable it by following these two steps:

1. To check under what name the LAN is associated write "ifconfig –a"

2. If, for example, it is under eth0 name, then write: "dhclient eth0"

This should enable the Ethernet and then SSH would also be available.

===How to install Android on SD-card? ===

[http://olimex.wordpress.com/2013/10/02/android-4-2-2-images-for-a20-olinuxino-running-from-sd-card-is-updated-on-wiki/ Blog post about it]

===How to access UART, I2C, GPIOs under Android? ===

[http://olimex.wordpress.com/2013/10/02/a20-olinuxino-tools-for-android-released/ Use our Open Source OLinuXino A20-TOOLS]

===How to control PWM under Linux? ===

There is an article here: [[how to add pwm]]

===How to build the Android 4.2.2 image for A20-OLinuXino-MICRO? ===

First you need to Download the [http://dl.linux-sunxi.org/users/tsvetan/ANDROID-4.2.2-SDK2.0-KERNEL-3.4/ A20 SDK2.0 Linux Kernel 3.4]

Second you need to configure your environment read the instructions [http://source.android.com/source/initializing.html here]

Then Build the kernel, kernel modules and u-boot

cd lichee
./build.sh -psun7i_android

When done, continue with Bulding the android image:

cd ../android4.2
cd device/softwinner/
tar zxfv olinuxino-a20.tgz
cd ../../
source build/envsetup.sh
lunch #select olinuxino-a20_eng
extract-bsp
make -j4

Dave from Axon instruments wrote more detailed [http://axonjakarta.wordpress.com/2014/02/14/olimex-a20-android-building-4/ blog post] about how he generates the Android image]

RT5350F-OLinuXino

2023-07-28T08:21:36Z

LubOlimex: /* Prebuilt files and system restore */

=RT5350F-OLinuXino official images build instructions=

==Overview==

==Quick-start==

1. Connect USB<->serial cable between the UART0 pins of the board and your personal computer.

2. Open your favourite serial terminal software on the COM port, created by your USB<->serial cable.

3. Set the baud rate for the connection to 57600.

4. Power on RT5350F-OLinuXino-EVB.

==Prebuilt files and system restore==

RT5350F-OLinuXino comes with an image loaded into the SPI flash memory. If something goes wrong you can restore the original image.

The original files can be found at this FTP location:

https://ftp.olimex.com/Ralink/RT5350F-OLinuXino/1.latest_images/

The repository contains six (7) files, two (2) upgrade binaries for each variant of Olimex-made RT5350 boards; and a text file with a link to u-boot+factory binary that serves as a restore point should a serious problem with u-boot or bootloader appears. The upgrade can be performed over different mediums, but the restore requires a programmer.

We have three variants of RT5350F-OLinuXino - RT5350F-OLinuXino, RT5350F-OLinuXino-EVB, and RT5350F-OLinuXino-EVB+ (which is the latest revisions of RT5350F-OLinuXino-EVB, starting revision C, with SD card and reset button, among other difference).

One of the two binary files for each board is meant for u-boot upgrade, while the other is meant for LuCI (web browser interface) upgrade. Read about the upgrade procedures the OpenWRT upgrading here:

https://openwrt.org/docs/guide-user/installation/generic.sysupgrade

===Upload prebuilt images using uboot===
Reboot the board and you'll see:
U-Boot 1.1.3 (Apr 20 2015 - 13:25:55)

Board: RT5350F-OLinuXino DRAM: 32 MB
relocate_code Pointer at: 81fb4000
spi_wait_nsec: 42
spi device id: 1c 30 17 1c 30 (30171c30)
find flash: EN25Q64
raspi_read: from:30000 len:1000
.*** Warning - bad CRC, using default environment

=============================================================
RT5350F-OLinuXino UBoot Version: 4.0.0.0
--------------------------------------------------------------
ASIC 5350_MP (Port5<->None)
DRAM_CONF_FROM: Boot-Strapping
DRAM_TYPE: SDRAM
DRAM_SIZE: 256 Mbits
DRAM_WIDTH: 16 bits
DRAM_TOTAL_WIDTH: 16 bits
TOTAL_MEMORY_SIZE: 32 MBytes
Flash component: SPI Flash
Date:Apr 20 2015 Time:13:25:55
============================================
icache: sets:256, ways:4, linesz:32 ,total:32768
dcache: sets:128, ways:4, linesz:32 ,total:16384

##### The CPU freq = 360 MHZ ####
estimate memory size =32 Mbytes

Please choose the operation:
1: Load system code to SDRAM via TFTP.
2: Load system code then write to Flash via TFTP.
3: Boot system code via Flash (default).
4: Entr boot command line interface.
7: Load Boot Loader code then write to Flash via Serial.
9: Load Boot Loader code then write to Flash via TFTP.

===Upload prebuilt OpenWRT using uboot===

Press 2, then y and enter some values for ip, server ip and filename:

You choosed 2
2: System Load Linux Kernel then write to Flash via TFTP.
Warning!! Erase Linux in Flash then burn new one. Are you sure?(Y/N)
Please Input new ones /or Ctrl-C to discard
Input device IP (10.10.10.123) ==:10.10.10.123
Input server IP (10.10.10.3) ==:10.10.10.3
Input Linux Kernel filename () ==:file.bin

Then your new system will boot.

===Upload prebuilt uboot===

Press 9, then again enter ip address, server ip and filename to upload:

You choosed 9

0
raspi_read: from:40028 len:6
.

9: System Load Boot Loader then write to Flash via TFTP.
Warning!! Erase Boot Loader in Flash then burn new one. Are you sure?(Y/N)

Press '''Y''' and continue:

Input device IP (10.10.10.123) ==:10.10.10.123
Enter some static address for the device, for example ''192.168.0.201''.

Next enter server address, for example ''192.168.0.15'':

Input server IP (10.10.10.3) ==:192.168.0.15

Finally enter filename:

Input Uboot filename () ==:bootloader.img

'''Don't forget to plug LAN cable.''' You should see something like that:

Got it
#####################
done
Bytes transferred = 106976 (1a1e0 hex)
NetBootFileXferSize= 0001a1e0
raspi_erase_write: offs:0, count:1a1e0
raspi_erase: offs:0 len:10000
.
raspi_write: to:0 len:10000
.
raspi_read: from:0 len:10000
.raspi_read: from:10000 len:10000
.raspi_erase: offs:10000 len:10000
.
raspi_write: to:10000 len:10000
.
raspi_read: from:10000 len:10000
.Done!

===Upload prebuilt images using programmer tool===

We will use [https://www.olimex.com/Products/ARM/JTAG/ARM-USB-OCD/ ARM-USB-OCD]. It has FT2232 chip which can be used to in SPI master mode. You can also use ARM-USB-TINY; ARM-USB-TINY-H; ARM-USB-OCD-H or any FT2232-based debugger.

Connect ARM-USB-OCD with RT5350F-OLinuXino-EVB according the schematic below (for the blue wire GND you can also use other GND pins available at the board; the GND is common):

[[File:Arm-usb-ocd.png|480px]]

'''RST_RT''' jumper MUST be closed. Then power the board to become ready writing.

Download flashrom software and build it using instructions on the site.

To program the SPI flash run:
flashrom -p ft2232_spi:type=arm-usb-ocd -w file.bin

Then wait some minutes for process to complete.

==Building uboot==

Get the sources from:
git clone https://github.com/OLIMEX/u-boot_RT5350F-OLinuXino
cd u-boot_RT5350F-OLinuXino

Target must be build with gcc3.4! This is very important because with another versions of GCC the build process will fail. You can find that version from '''Ralink SDK'''. Use Google to find it.

Run
make menuconfig

You'll see that the default location is /opt/buildroot-gcc342/bin. Change that with your path.

To actually build u-boot run:
make

At the end of the process you'll see something like this

===============<<IMPORTANT>>==================
Notes:Uboot firmware in flash is uboot.img NOT uboot.bin
================================================

./tools/mkimage -A mips -T standalone -C none \
-a 0x80200000 -e 0x80200000 \
-n "SPI Flash Image" \
-r SDR -s 16 -t 32 -u 16 \
-y 0x0 -z 0x0 -w 0xFF -d uboot.bin uboot.img
Image Name: SPI Flash Image
Created: Thu May 14 08:23:19 2015
Image Type: MIPS Linux Standalone Program (uncompressed)
Data Size: 106912 Bytes = 104.41 kB = 0.10 MB
Load Address: 0x80200000
Entry Point: 0x80200000
DRAM Parameter: 6 (Parm0=0 Parm1=0)

The image '''uboot.img''' can be uploaded via tftp.

==Building OpenWRT==

=== OpenWRT 18.06 ===

Download sources:
git clone https://github.com/OLIMEX/openwrt -b evb+/18.06

Go into openwrt directory:
cd openwrt

Update and install feeds:
./scripts/feeds update -a
./scripts/feeds install -a

Apply config:
cat > .config << __EOF__
CONFIG_TARGET_ramips=y
CONFIG_TARGET_ramips_rt305x=y
CONFIG_TARGET_MULTI_PROFILE=y
CONFIG_TARGET_DEVICE_ramips_rt305x_DEVICE_rt5350f-olinuxino=y
CONFIG_TARGET_DEVICE_ramips_rt305x_DEVICE_rt5350f-olinuxino-evb=y
CONFIG_TARGET_DEVICE_ramips_rt305x_DEVICE_rt5350f-olinuxino-evb-plus=y
# CONFIG_FEED_luci is not set
# CONFIG_FEED_packages is not set
# CONFIG_FEED_routing is not set
# CONFIG_FEED_telephony is not set
CONFIG_PACKAGE_block-mount=y
CONFIG_PACKAGE_i2c-tools=y
CONFIG_PACKAGE_kmod-crypto-crc32c=y
CONFIG_PACKAGE_kmod-crypto-hash=y
CONFIG_PACKAGE_kmod-fs-ext4=y
CONFIG_PACKAGE_kmod-fs-ntfs=y
CONFIG_PACKAGE_kmod-fs-vfat=y
CONFIG_PACKAGE_kmod-lib-crc16=y
CONFIG_PACKAGE_kmod-nls-cp437=y
CONFIG_PACKAGE_kmod-nls-iso8859-1=y
CONFIG_PACKAGE_kmod-nls-utf8=y
CONFIG_PACKAGE_kmod-scsi-core=y
CONFIG_PACKAGE_kmod-usb-storage=y
CONFIG_PACKAGE_libiwinfo-lua=y
CONFIG_PACKAGE_liblua=y
CONFIG_PACKAGE_liblucihttp=y
CONFIG_PACKAGE_liblucihttp-lua=y
CONFIG_PACKAGE_libubus-lua=y
CONFIG_PACKAGE_lua=y
CONFIG_PACKAGE_luci=y
CONFIG_PACKAGE_luci-app-firewall=y
CONFIG_PACKAGE_luci-base=y
CONFIG_PACKAGE_luci-lib-ip=y
CONFIG_PACKAGE_luci-lib-jsonc=y
CONFIG_PACKAGE_luci-lib-nixio=y
CONFIG_PACKAGE_luci-mod-admin-full=y
CONFIG_PACKAGE_luci-proto-ipv6=y
CONFIG_PACKAGE_luci-proto-ppp=y
CONFIG_PACKAGE_luci-theme-bootstrap=y
CONFIG_PACKAGE_rpcd=y
CONFIG_PACKAGE_rpcd-mod-rrdns=y
CONFIG_PACKAGE_uhttpd=y
__EOF__

Expand to full config:
make defconfig

Make some modifications with:
make menuconfig

Build the images:
make

Target images can be found in '''bin/targets/ramips/rt305x/''':
tree bin/targets/ramips/rt305x/
bin/targets/ramips/rt305x/
|-- config.seed
|-- openwrt-ramips-rt305x-device-rt5350f-olinuxino-evb-plus.manifest
|-- openwrt-ramips-rt305x.manifest
|-- openwrt-ramips-rt305x-root.squashfs
|-- openwrt-ramips-rt305x-rt5350f-olinuxino-evb-initramfs-kernel.bin
|-- openwrt-ramips-rt305x-rt5350f-olinuxino-evb-plus-initramfs-kernel.bin
|-- openwrt-ramips-rt305x-rt5350f-olinuxino-evb-plus-squashfs-sysupgrade.bin
|-- openwrt-ramips-rt305x-rt5350f-olinuxino-evb-squashfs-sysupgrade.bin
|-- openwrt-ramips-rt305x-rt5350f-olinuxino-initramfs-kernel.bin
|-- openwrt-ramips-rt305x-rt5350f-olinuxino-squashfs-sysupgrade.bin
|-- openwrt-ramips-rt305x-uImage.bin
|-- openwrt-ramips-rt305x-uImage-initramfs.bin
|-- openwrt-ramips-rt305x-vmlinux.bin
|-- openwrt-ramips-rt305x-vmlinux.elf
|-- openwrt-ramips-rt305x-vmlinux-initramfs.bin
|-- openwrt-ramips-rt305x-vmlinux-initramfs.elf

=== OpenWRT ===
Make a directory:
# mkdir some_dir
# cd some_dir

Download sources:
# git clone https://github.com/OLIMEX/openwrt -b rt5350f

Go into openwrt directory:
# cd openwrt

You can use our config:
# make

or if you want to change something:
# make menuconfig
# make

After some time build will finish. The image is found under:
'''build_dir/target-mipsel_24kec+dsp_uClibc-0.9.33.2/linux-ramips_rt305x/\'''
'''openwrt-ramips-rt305x-olinuxino-rt5350f-squashfs-sysupgrade.bin'''

Place that file on some tftp server and then upload it to the board.

=Demo projects=

*First steps video with RT5350F-OLinuXino-EVB by Leon Anavi: [https://www.youtube.com/watch?v=-MsywWtN79c https://www.youtube.com/watch?v=-MsywWtN79c]

= Images changelog =

== Release-3 (03 APR 2019) ==
* Upgrade OpenWRT to 18.06 (kernel 4.14.x+)
* Added support for RT5350-OLinuXino-EVB+

== Release-2 (06 JUL 2015) ==
* More info about this software release can be found at this GitHub page:
 
https://github.com/OLIMEX/OLINUXINO/tree/master/SOFTWARE/RT5350F/Prebuilt%20images

* Upgraded kernel version to 3.18.17
* Inverted wlan led polarity - this way it blink when WiFi is on
* Fixed firmware partition size - https://github.com/OLIMEX/openwrt/issues/1

A13-OLinuXino-MICRO

2023-06-23T09:47:14Z

LubOlimex: /* Linux */

== Official Images from OLIMEX ==

=== Linux ===

'''[https://ftp.olimex.com/Allwinner_Images/A13-OLinuXino-MICRO/Debian/sd/A13_Micro_Debian_kernel_34_79_100kHz_I2C_WIFI_USB_LAN_X_touch_third_release.7z Download location to A13-OLinuXino-MICRO Debian 4GB SD-card image release 3]'''

'''[https://drive.google.com/file/d/0B-bAEPML8fwlYmdWLWJrYWJ1YW8/edit?usp=sharing Step-by-step instructions for building the latest release]'''

The image has the following features:

*Linux Kernel 3.4.79+
*LXDE desktop environment
*GCC 4.6
*dpkg
*git
*i2c-tools
*perl
*xorg
*Python 2.7
*vlc
*mplayer
*smplayer
*LCD support
*GPIO
*I2C
*SPI
*USB WIFI RTL8188CU, Ethernet AX88772B
*Audio
*PyA13 python module with GPIO,I2C,SPI support
*Default Login: '''root/olimex'''

The file A13_Micro_Debian_kernel_34_79_100kHz_I2C_WIFI_USB_LAN_X_touch_third_release.7z is an archive of A13_Micro_Debian_kernel_34_79_100kHz_I2C_WIFI_USB_LAN_X_touch_third_release.img file.

So in order to write the image on SD card you have to unzip A13_Micro_Debian_kernel_34_79_100kHz_I2C_WIFI_USB_LAN_X_touch_third_release.7z file:

Install under Windows

Use 7zip and then use Win32DiskImager.exe [http://sourceforge.net/projects/win32diskimager/ http://sourceforge.net/projects/win32diskimager/] for image writing

Install under linux
Use p7zip package. If you have no installed 7zip then type

<nowiki>#apt-get install p7zip</nowiki>

Copy A13_Micro_Debian_kernel_34_79_100kHz_I2C_WIFI_USB_LAN_X_touch_third_release.7z file in your directory and unzip it with

<nowiki>#7za e A13_Micro_Debian_kernel_34_79_100kHz_I2C_WIFI_USB_LAN_X_touch_third_release.7z</nowiki>

The output should be a new 4GB file named A13_Micro_Debian_kernel_34_79_100kHz_I2C_WIFI_USB_LAN_X_touch_third_release.img
Put 4GB SD card in your card reader and type

<nowiki># ls /dev/sd</nowiki>

Then press two times <TAB> you will see a list of your sd devices like sda sdb sdc note that some of these devices may be your hard disk so make sure you know which one is your sd card before you proceed as you can damage your HDD if you choose the wrong sd-device. You can do this by unplugging your sd card reader and identify which "sd" devices remove from the list.
Once you know which device is your sdcard like sda use this text instead of the sdX name in the references below:

<nowiki>#dd if=A13_Micro_Debian_kernel_34_79_100kHz_I2C_WIFI_USB_LAN_X_touch_third_release.img of=/dev/sdX</nowiki>

The list of all installed packages is [https://drive.google.com/file/d/0B-bAEPML8fwlb1ZWODhGUl9uVlE/edit?usp=sharing here]

'''Note:''' the A13-OLinuXino-MICRO-SD card which we have on our webshop contain same image on 4GB Class10 fast micro sd-card, if you want to use this image please use Class10 fast card or the performance of Linux will slow down

=== Android ===

A13-OLinuXino-MICRO has only 256MB of RAM, Android 4.x requires at least 512MB to run well. Running obsolete Android would be possible but without video acceleration )since only MALI requires around 200MB). Forget for Android on this board.

=== Changing A13-OLinuxino-MICRO screen resolution ===

The default Debian SD card setup is made with settings for VGA 800x600.
If you want to switch resolutions between VGA (800x600) and LCD (4.3<nowiki>''</nowiki> or 7<nowiki>''</nowiki> or 10.1<nowiki>''</nowiki>, respectively with native screen resolutions of 480x242, 800x480 and 1024x600) then you have to replace the existing script.bin file from the first SD card partition (note that this partition is FAT - so you can replace the file under Windows or Linux) with the script.bin file from script_GPIO_VGA_xxx directory (with the desired VGA resolution mode) or from script_GPIO_LCD_xxx directory (with the desired LCD resolution mode).

The archive of scripts might be download from here: [https://www.olimex.com/Products/OLinuXino/A13/_resources/VGA_LCD_scripts_A13_micro.zip all available screen resolution scripts for A13-MICRO]

Note that these A13-MICRO scripts are not compatible with the A13 boards. Please check the A13 wiki article for such scripts.

===How to edit board configurations and definitions in the official Debian Linux? ===

The biggest part of the board configuration might be edited, changed or improved in a file called script.bin

The script.bin file can usually be found in the main directory of a microSD card prepared with official Debian image. The folder containing the script can be inspected under both Windows, Linux or Mac.

You can't directly edit binary file so you would need to convert it to text format (it is called fex in this case), then edit the parameters via a text editor and finally switch it back to binary format.

The different options for the script are explained here: [http://linux-sunxi.org/Fex_Guide SUNXI FEX GUIDE]

IMPORTANT! ADJUSTING SCRIPT.BIN WITH IMPROPER VALUES MIGHT BREAK YOUR DEBIAN IMAGE AND IT IS ALWAYS RECOMMENDED TO KEEP A BACK-UP OF YOUR DEFAULT SCRIPT.BIN

To convert back and fort the script.bin you might use different tools. You can find Windows tools here: [https://github.com/OLIMEX/OLINUXINO/tree/master/SOFTWARE/fex-bin-convertor-windows SUNXI TOOLS FOR WINDOWS] . For Linux convertors please check the sunxi tools here: [https://github.com/linux-sunxi/sunxi-tools SUNXI TOOLS]

Note that it is possible to change the script.bin in a running Debian image in newest releases! More information might be found at the end of the document! Not all releases feature the live method of changing fex to bin so if you board doesn't have it follow the other methods.

Changing script.bin file without removing the microSD card:

The tools for script.bin changing are located in /opt/sunxi-tools directory
<nowiki># cd /opt/sunxi-tools</nowiki>
<nowiki># ./chscr.sh</nowiki>
This will convert script.bin file from sdcard to script.fex file and the file will be opened using nano editor.
Now you can change the board modules and parameters, save the changes and exit from nano editor
<nowiki># ./wrscr.sh</nowiki>
this will convert script.fex to script.bin and the script.bin file will be written to sdcard.

===Linux Commands===

[[Linux-Commands]] Brief Linux Command reference

[[Main_Page]]

A13-SOM-building-latest-Debian

2023-05-23T08:57:16Z

LubOlimex:

A13 SOM kernel 3.4.90 build description release 4

How to make a bootable SD card for A13-OLinuXino-MICRO, A13-SOM-256 and A13-SOM-512 (HYNIX or SAMSUNG RAM memory with kernel 3.4 (and either sunxi or main-line uboot) and Debian file system.

'''This guide is not suitable for A13-OLinuXino and A13-OLinuXino-WIFI.'''

===============================================================================================

'''1. Setup of the toolchain'''
-------------------------
You should make sure you have the software tools required for building the Linux Kernel. Please install the required tools if you don't have them already. To install new software you should be logged as a super user on your Linux machine; the first thing to do would be to type in the terminal:

$ sudo su

you will be asked for your password and then your prompt will change to # which means you are now the super user, all future commands should be run in this mode.

At this point update apt-get links by typing

apt-get update

Install the toolchain by typing the following.

apt-get install gcc-4.7-arm-linux-gnueabihf ncurses-dev uboot-mkimage build-essential git

This will install: GCC compiler used to compile the kernel; the kernel config menu uboot creates image which is required to allow the SD card to boot into the linux image; Git which allows you to download from the github which holds source code for some of the system; additional other tools for building the kernel.

Note that if you use debian may be you will need to add

deb http://www.emdebian.org/debian squeeze main in the file below:

/etc/apt/sources.list

after the installation you now have all tools to make your very own A13 kernel image!

'''2. Building Uboot'''
-----------------
Here you have two options. The first is to use sunxi u-boot and the second is to use mainline u-boot. The sunxi u-boot is suitable for the boards that have HYNIX DDR3 chip - H5TQ2G83CFR. The mainline u-boot is suitable for boards that have SAMSUNG DDR3 chip - K4B2G0846Q. Note that if you use the sunxi u-boot with SAMSUNG DDR3 memory then you would have different problems because the new SAMSUNG DDR chip is not supported in this u-boot. The mainline u-boot will be suitable for HYNIX and SAMSUNG DDR3.

First let's make the directory where we will build the A13-OLinuXino-Micro/SOM linux:

mkdir a13-micro-SOM-kernel_3.4
cd a13-micro-SOM-kernel_3.4

After that follow either chapter 2.1 or 2.2 (2.1 is suitable for sunxi u-boot and XYNIX RAM memory; 2.2 is suitable for mainline u-boot and SAMSUNG RAM memory)

2.1. Building sunxi u-boot
If we have a board with HYNIX RAM let's download the uboot sources from GitHub repository, note that there are lot of branches but you have to use sunxi branch. Note that the u-boot for A13-OLinuXino-MICRO and A13-SOM boards is tested with the next branch:

git rev-parse --verify HEAD 78592f1d95cccf329ed515a176c80be5c87827a0

this means after you have download the sources (with git clone) you can switch to the exact commit with:

git reset --hard 78592f1d95cccf329ed515a176c80be5c87827a0

Download u-boot sources:

git clone -b sunxi https://github.com/linux-sunxi/u-boot-sunxi.git

After the download you should have a new directory

cd u-boot-sunxi/

Note that there are 2 versions of A13-SOM boards:

-A13-SOM with 256MB DDR3 memory size
-A13-SOM with 512MB DDR3 memory size - need u-boot patch

If you have A13-SOM board with 512MB memory size then first you have to aply patch for changing DDR3 memory size:
download u-boot_A13_SOM_512MB.patch using wget command

wget "https://drive.google.com/file/d/0BwplT87k9SCgY3lIWVlLd3ZlSEk/view?usp=sharing&resourcekey=0-5DKIvjZcbpdjsrseLdzMtg"

and patch the file board/sunxi/dram_a13_oli_micro.c with the next command

patch -p0 < u-boot_A13_SOM_512MB.patch

If you have A13-SOM with 256MB memory size you no need from patch. By default u-boot settings are set for 256MB memory size and you can start building imediately after download u-boot.

You can start uboot building with the next commands:

make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- A13-OLinuXinoM_config
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf-

At the end of the process you can check if everything is OK by

ls u-boot.bin u-boot-sunxi-with-spl.bin spl/sunxi-spl.bin

spl/sunxi-spl.bin u-boot.bin u-boot-sunxi-with-spl.bin

If you got these files everything is complete, well done so far

cd ..

You should be in the following directory

/home/user/a13-micro-SOM-kernel_3.4#

At this point skip 2.2 directly to chapter 3.

2.2. Building mainline u-boot

Note that if you want to use latest mainline u-boot then you have to use linaro toolchain 6.2 and above!

The mainline u-boot in our image is compiled using linaro toolchain version 6.4 from this link
https://releases.linaro.org/components/toolchain/binaries/6.4-2018.05/arm-linux-gnueabihf/gcc-linaro-6.4.1-2018.05-i686_arm-linux-gnueabihf.tar.xz

After you download it, unzip it with with:

# tar xJf gcc-linaro-6.4.1-2018.05-i686_arm-linux-gnueabihf.tar.xz

Download u-boot sources:

git clone git://git.denx.de/u-boot.git

After the download you should have a new directory

cd u-boot

If we have a board with SAMSUNG RAM let's download the uboot sources from GitHub repository, note that the u-boot for A13-OLinuXino-MICRO and A13-SOM boards is tested with the next branch:

git rev-parse --verify HEAD 1733259d25015c28c47990ec11af99b3f62f811c

this means after you have download the sources you can switch to the exact commit with

git reset --hard 1733259d25015c28c47990ec11af99b3f62f811c

Load the configuration file. It is tha same for A13-SOM and A13-Micro board

make CROSS_COMPILE=arm-linux-gnueabihf- A13-OLinuXinoM_defconfig

you can configure some u-boot settings like DDR3 settings, clocks and other with:

make menuconfig

It is recommended to choose:

[*]Enable workaround for booting old kernels

and

[*] sunxi dram odt enable

the board has stable behaviour with
[360] sunxi dram clock speed
[100] sunxi mbus clock speed

but you can choose other settings depending from your application

save it the settings and exit

Compile the u-boot

# make CROSS_COMPILE=/path_to_file/arm-linux-gnueabihf-

When the compilation completes, there will be u-boot-sunxi-with-spl.bin available in your u-boot tree.

Now you have to create a new boot.cmd file with the following contain

setenv bootm_boot_mode sec
setenv bootargs console=ttyS0,115200 root=/dev/mmcblk0p2 rootwait panic=10
load mmc 0:1 0x43000000 script.bin || load mmc 0:1 0x43000000 boot/script.bin
load mmc 0:1 0x42000000 uImage || load mmc 0:1 0x42000000 boot/uImage
bootm 0x42000000

convert boot.cmd in boot.scr with the next command

mkimage -C none -A arm -T script -d boot.cmd boot.scr

The result should be a new boot.scr file that you have to copy to the first SD card partition (where uImage and script.bin file are located).

'''3. Building kernel sources for A13-SOM'''
----------------------------------------------
Kernel sources for A13 are available on GitHub. Note that the following building is made with the revision below:

git rev-parse --verify HEAD e37d760b363888f3a65cd6455c99a75cac70a7b8

You can download the kernel sources using the following command:

git clone https://github.com/linux-sunxi/linux-sunxi

After the download go to the kernel directory

cd linux-sunxi/

Note that before compiling kernel you have to do a patch kernel in order to change I2C sped from 200kHz to 100kHz (need for Olimex's I2C modules) and some other changes related with missing power management with AXP209 chip.

download the patch a13_micro_SOM.patch using wget command

wget "https://drive.google.com/file/d/0BwplT87k9SCgQ0IxZjRtaHVnMzg/view?usp=sharing&resourcekey=0-livmBN2h0X6-wv4R8jr8QA"

and apply the patch:

patch -p1 < a13_micro_SOM.patch

The next step is to configure the system

Here you need from a13 configuration file - a13_micro_SOM_defconfig. The file contains all kernel module settings.

Download a13_micro_SOM_defconfig using wget command

wget "https://drive.google.com/file/d/0BwplT87k9SCgWEdqRGl2amxyd2c/view?usp=sharing&resourcekey=0-CzihPrsCCVaiVMuSEHHrpw"

then copy a13_micro_SOM_defconfig file to configs directory:

cp a13_micro_SOM_defconfig ./arch/arm/configs/

and make:

make ARCH=arm a13_micro_SOM_defconfig

The result should be:
configuration written to .config

If you wish to make your changes in the kernel configuration do:

make ARCH=arm menuconfig

The menuconfig changes a .config text file, which you can view/edit even with a text editor like vi,nano.
With this command you can add or remove different modules for the different peripherals in the kernel. Be careful when use this as this may cause the kernel to not work properly.

Now you can continue with kernel image compiling

make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- -j4 uImage

when this finish you will have uImage ready and the result should be:

Kernel: arch/arm/boot/Image is ready
LD arch/arm/boot/compressed/vmlinux
OBJCOPY arch/arm/boot/zImage
Kernel: arch/arm/boot/zImage is ready
UIMAGE arch/arm/boot/uImage
Image Name: Linux-3.4.79+
Created: Mon May 12 09:22:56 2014
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 4612216 Bytes = 4504.12 kB = 4.40 MB
Load Address: 40008000
Entry Point: 40008000
Image arch/arm/boot/uImage is ready

Now you can build the kernel modules:

make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- -j4 INSTALL_MOD_PATH=out modules
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- -j4 INSTALL_MOD_PATH=out modules_install

DONE! At this point you have uboot and kernel modules.

The uImage file is located in linux-sunxi/arch/arm/boot/

The kernel modules are located in

linux-sunxi/out/lib/modules/3.x.xx
where 3.x.xx is kernel version

in our case the directory with modules is:

linux-sunxi/out/lib/modules/3.4.90+

'''4. Format and setup the SD-card'''
--------------------------------
We suggest 4GB class 10 micro sd-card but you can use any card between 2GB and 16GB.

First we have to make the correct card partitions, this is done with fdisk.

Plug SD card into your SD card reader and enter in the terminal

ls /dev/sd
Then press two times <TAB> you will see a list of your sd devices like sda sdb sdc note that some of these devices may be your hard disk so make sure you know which one is your sd card before you proceed as you can damage your HDD if you choose the wrong sd-device. You can do this by unplugging your sd card reader and identify which of the ?sd? devices disappears from the list.

Once you know which device is your sdcard like sda use this text instead of the sdX name in the references below:

fdisk /dev/sdX
then do these steps:

1. p
will list your partitions

if there are already partitions on your card do:

2. d enter 1
if you have more than one partition press d while delete them all

3. create the first partition, starting from 2048
n enter p enter 1 enter enter +16M

4. create second partition
n enter p enter 2 enter enter enter

then list the created partitions:
p enter
if you did everything correctly on 4GB card you should see something like:

Disk /dev/sdg: 3980 MB, 3980394496 bytes
123 heads, 62 sectors/track, 1019 cylinders, total 7774208 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Device Boot Start End Blocks Id System
/dev/sdg1 2048 34815 16384 83 Linux
/dev/sdg2 34816 7774207 3869696 83 Linux

7. w

write changes to sd card

now we have to format the file system on the card:

the first partition should be vfat as this is FS which the Allwinner bootloader understands

mkfs.vfat /dev/sdX1

the second should be normal Linux EXT3 FS

mkfs.ext3 /dev/sdX2

'''5. Write the Uboot and sunxi-spl.bin'''
-------------------------------------
You should be in /home/user/a13-micro-SOM-kernel_3.4# directory
Note that you have to write u-boot-sunxi-with-spl.bin in /dev/sdX (not sdX1 or sdX2)

dd if=u-boot-sunxi/u-boot-sunxi-with-spl.bin of=/dev/sdX bs=1024 seek=8

Note that if you use mainline u-boot then you have to copy the generated boot.scr file in the first sdcard partition. For example:

mkdir /mnt/sd
mount /dev/sdX1 /mnt/sd
cp /u-boot/boot.scr /mnt/sd/

'''6. Write kernel uImage you build to the SD-card'''
-----------------------------------------------

copy the Kernel uImage to root directory in partition 1

cp linux-sunxi/arch/arm/boot/uImage /mnt/sd

'''7. Write script.bin file'''
-------------------------
script.bin is a file with very important configuration parameters like port GPIO assignments, DDR memory parameters, Video resolution etc, download the script.bin using wget command

wget "https://drive.google.com/file/d/0BwplT87k9SCgYXhpQ2djd2hZRDg/view?usp=sharing&resourcekey=0-aOTtYqfAz029aCbvpuLkPQ"
cp script.bin /mnt/sd
sync
umount /dev/sdX1

'''8. Debian rootfs'''
----------------
The Linux Kernel and Uboot are ready, now we have need from Linux distribution rootfs.

Basically the only difference between the different Linux distributions is the rootfs, so if you put Debian rootfs you will have Debian, if you put Ubuntu rootfs it will be Ubuntu etc.

How to build one is a long topic, the good thing is that there are many already pre-built so we can just download one and use.

exit the kernel directory

cd ..

You should be in the directory below

/home/user/a13-micro-SOM-kernel_3.4
download the torrent of the archive with debian rootfs - a13_micro_SOM_debian_FS.tgz using wget command

wget https://ftp.olimex.com/Allwinner_Images/A13-SOM/Outdated%20Sunxi%20Images/sd/a13_micro_SOM_debian_FS.tgz --no-check-certificate

mount your sd card EXT3 FS partition:

mount /dev/sdX2 /mnt/sd

and unarchive the rootfs

tar xzvf a13_micro_SOM_debian_FS.tgz -C /mnt/sd
ls /mnt/sd

the right result should be:
bin dev home lost+found mnt proc run selinux sys usr
boot etc lib media opt root sbin srv tmp var

Now you have to replace the new generated kernel modules from /home/user/a13-micro-SOM-kernel_3.4linux-sunxi/out/lib/modules/ to the new debian file system

rm -rf /mnt/sd/lib/modules/*

cp -rfv linux-sunxi/out/lib/modules/3.x.xx+/ /mnt/sd/lib/modules/
where x.xx is the kernel version
in our case:
cp -rfv linux-sunxi/out/lib/modules/3.4.90+/ /mnt/sd/lib/modules/

replace /lib/firmware folder with the generated /linux-sunxi/out/firmware
rm -rf /mnt/sd/lib/firmware/
cp -rfv linux-sunxi/out/lib/firmware/ /mnt/sd/lib/

sync
umount /mnt/sdX2

At this point you have Debian on your SD card second partition and you have an SD card ready to boot debian on A13-OLinuXino-Micro/SOM

Connect USB-SERIAL-CABLE-F to UEXT Tx.Rx and GND, or connect a HDMI screen. Put the SD-card in A13-OLinuXino-Micro/SOM and apply 6-16V power, you should see Uboot and then Kernel messages on the console

default username/password is : root / olimex

RK3188-SOM

2023-04-21T10:24:47Z

LubOlimex: /* Debian for microSD card */

== Overview ==

[[File:Rk3188-som-resized.png|650px]]

RK3188-SOM board is a very productive small beast compared to the previous Olimex board designs. If we compare RockChip RK3188 and Allwinner A20: RK3188 has 4x Cortex-A9, while A20 only 2x Cortex-A7. It runs at 1.6 GHz vs. the 1.0 GHz frequency of the A20. RK3188 reaches a total of 16000 DMPIS vs. the 3800 DMIPS for the A20 (RK3188 is 4.2 times faster). For comparison, the RaspberryPi has 965 DMIPS (RK3188 is 16.6 times faster).

The RK3188-SOM design has the following features:

*Rockchip RK3188 quad core Cortex-A9 processor, each core typically running at 1.6GHz
*1GB DDR3 memory
*Integrated power management unit
*Optional 4GB NAND flash memory for Linux or Android boot
*Micro SD-card for Linux or Android boot
*Three buttons - POWER, RESET, RECOVERY
*Four LEDs (one for power and three user-programmable)
*UART console pins exposed for serial debug
*Five GPIO connectors 2×20 pins @ 0.05" step
*Dimensions: (3.2×1.8)" ~ (81×56)mm
 

== Ready-to-use Debian images ==
=== Debian for microSD card ===

'''Newest official release (recommended):'''

Direct download of Debian release #2:[https://ftp.olimex.com/Rockchip_images/sd/debian/RK3188_debian_3.0.36_SD_release2.img.7z RK3188-SOM Debian for microSD card - kernel 3.0.36+ - release #2]

In the command line interface of image you are automatically logged as root. The default superuser username/password combination in the GUI (XFCE4) is: olimex/olimex.

Build instructions and links to required files for the latest Debian images might be found below in chapter "Building Linux for RK3188-SOM".

'''Older official releases (not recommended):'''

Direct download of Debian release #1:[https://ftp.olimex.com/Rockchip_images/sd/debian/RK3188_debian_3.0.36_SD_release1.img.7z RK3188-SOM Debian for microSD card - kernel 3.0.36+ - release #1]

====How to prepare your microSD card with the suitable official Debian image?====
----
In order to download an official Linux image to a microSD card under Windows you can use Win32 Disk Imager: [http://sourceforge.net/projects/win32diskimager/ click here]

1. Download the latest official image suitable for a microSD card from the chapter above

2. Download Win32 Disk Imager from this link.

3. Insert card in your microSD card reader.

4. Launch the software.

5. Point the software to the image

6. Click "write"

Under Linux you can write the image image to the card with dd utility. This is how it can be done:

Let's say the name of the image is "debian_2g.img". It would be downloaded to the microSD card connected to a Linux machine using one of the following commands:

dd bs=4M oflag=sync if=debian_2g.img of=/dev/sdX

or

cp debian_2g.img /dev/sdX

where /dev/sdX is the uSD card as listed by the Linux.

=== Debian for NAND memory ===

'''Newest official release (recommended):'''

Direct download Debian for NAND release #1: [https://ftp.olimex.com/Rockchip_images/nand/debian/RK3188_debian_3.0.36_NAND_release1.img.7z|RK3188-SOM Debian for NAND memory - kernel 3.0.36+ - release #1]

Note that this image is suitable only for RK3188-SOM-4GB boards.

Build instructions and links to required files for the latest Debian images might be found below in chapter "Building Linux for RK3188-SOM"

====How to download the ready Debian image to the NAND memory of RK3188-SOM?====
----

'''IMPORTANT: RK3188-SOM-4GB comes with Debian already pre-loaded on the NAND memory. No need to perform this operation initially.'''

1. You need to download the software tools for your computer provided by Rockchip. If you use Windows download “Rockchip Batch Tool”. If you use Linux use either rkflashkit or upgrade_tool. These are the tools that I recommend but there are a lot of tools available. Get the Rockchip batch tool from here: [https://drive.google.com/file/d/0BwplT87k9SCgRDB4ZGY3SnMzd00/view?usp=sharing Rockchip Batch Tool]

For Windows:

2. Install the drivers that allows your computer to recognize the board (that is already set in bootloader mode) connected to it. The installer is called "Rockchip Driver Assistant" – download it here: [https://drive.google.com/file/d/0BwplT87k9SCgbkdXX1ByUW1RSW8/view?usp=sharing Rockchip Driver Assistant]

3. You need to download and extract the latest image suitable for the NAND from our wiki. It is available as a direct download here: [https://ftp.olimex.com/Rockchip_images/nand/debian/RK3188_debian_3.0.36_NAND_release1.img.7z%7CRK3188-SOM|RK3188 Debian 3.0.36 for NAND memory]

4. You need enter bootloader mode with the board to be able to establish connection between the board and the software provided by Rockchip. You would also need a mini USB cable. To enter bootloader mode you need to press and hold down the recovery button before powering the board (then connect the board to the PC via the mini USB cable). After the board is powered you can release the button.

5. Start the tool for uploading the firmware and point it to the extracted image.

6. Click button "Upgrade".

7. Test with a serial cable.

== Ready-to-use Android images ==
TODO

== Documents ==

[https://www.olimex.com/Products/SOM/RK3188/RK3188-SOM/resources/RK3188-SOM-UM.pdf OLIMEX RK3188-SOM user's manual]

[https://www.olimex.com/Products/SOM/RK3188/RK3188-SOM-EVB/resources/RK3188-SOM-EVB-UM.pdf OLIMEX RK3188-SOM-EVB user's manual]

[https://github.com/OLIMEX/OLINUXINO/raw/master/HARDWARE/RK3188-PDFs/Rockchip%20RK3188%20datasheet%20V1.0.pdf Processor (Rockchip RK3188) datasheet in pdf format]

[https://www.olimex.com/Products/SOM/RK3188/RK3188-SOM/resources/RK3188_SOM_GPIOs.pdf RK3188-SOM connectors' pinout and GPIO table]

=== CAD files ===

RK3188-SOM is considered commercial, proprietary design. The board file is not available to the customer. A pdf extracted from the original schematic is available at GitHub: [https://github.com/OLIMEX/SOM/tree/master/RK3188/RK3188-SOM RK3188-SOM schematics]

RK3188-SOM-EVB is considered Open Source Hardware, Eagle CAD files are available also at GitHub: [https://github.com/OLIMEX/SOM/tree/master/RK3188/RK3188-EVB RK3188-SOM-EVB sources]

The CAD product used to design OLinuXino is Eagle and you can download evaluation free version from their [http://www.cadsoftusa.com/ web site]. The evaluation version allows you to inspect the schematic and the board file sources.

==Board Layout==

[[File:Rk3188-som-resized-TOP-NAMED.png|650px]]

[[File:Rk3188-som-resized-BOTTOM-NAMED.png|650px]]

== Building Linux for RK3188-SOM ==
=== Building the parameter file ===
----
The parameter file describes many board parameters as firmware version, machine id, manufacturer name, etc.

For the user the most important parameter is '''CMDLINE'''. This is the command that is passed to the kernel. It looks something like this:
CMDLINE:console=ttyFIQ0,115200 console=tty0 root=/dev/mmcblk0p1 rw rootfstype=ext4 init=/sbin/init initrd=0x62000000,0x00800000 \
mtdparts=rk29xxnand:0x00008000@0x00002000(boot),-@0x0000A000(linuxroot)

Define serial port at 115200:
console=ttyFIQ0,115200

Define location of the rootfs:
root=/dev/mmcblk0p1

Define rootfs file system as ext4:
rootfstype=ext4

Define the address of the kernel and size:
0x00008000@0x00002000

Define start address of the rootfs:
-@0x0000A000

Additionally, you can set static MAC address with:
mac_addr=xx:xx:xx:xx:xx:xx

Once you're ready with the file, make the parameter image

* Get rkutils:
https://github.com/naobsd/rkutils
cd rkutils
gcc rkcrc.c -o rkcrc
If you're getting error try to comment ''''#include <err.h>'''' in ''''rkcrc.c''''

* Encrypt parameter file:
./rkcrc -p you_parameter_file parameter

The parameter file is ready for further use.

=== Building the kernel ===
----
* Fist prepare the toolchain:
apt-get update
apt-get install gcc-4.7-arm-linux-gnueabihf ncurses-dev uboot-mkimage build-essential git

* Get the sources:
git clone -b olimex/stable-3.0 https://github.com/StefanMavrodiev/RK3188-SOM.git

* Get the default configuration:
cd RK3188-SOM/
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- '''olimex_rk3188_defconfig'''

* You can modify defconfig with (for additional modules):
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- menuconfig

'''Note!''' The default config will set hdmi to 1080p. You can change it from:
Device Drivers --->
Graphics support --->
<*> Frame buffer support for Rockchip --->
LCD Panel Select --->
'''''Choose one of the following:'''''
HDMI framebuffer size and timing is 1080p <--- '''Set HDMI to 1080p'''
HDMI framebuffer size and timing is 720p <--- '''Set HDMI to 720p'''
HDMI framebuffer size and timing is 480p <--- '''Set HDMI to 480p'''
RGB AT070TN90 <--- [https://www.olimex.com/Products/OLinuXino/LCD/LCD-OLinuXino-7/open-source-hardware LCD-OLinuXino-7]
RGB AR010H05N <--- [https://www.olimex.com/Products/OLinuXino/LCD/LCD-OLinuXino-10/open-source-hardware LCD-OLinuXino-10]
RGB BT043DCNNHHP <--- [https://www.olimex.com/Products/OLinuXino/LCD/LCD-OLinuXino-4.3TS/open-source-hardware LCD-OLinuXino-4.3TS]

* Build the kernel:
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- -j4 kernel.img
After the build is finish you will have '''RK3188-SOM/kernel.img''' and '''RK3188-SOM/arch/arm/boot/Image'''. The first one can be uploaded to the kernel partition (if you have one). The second file is raw binary. It can be combined with ramdisk to get boot.img.

* Generate ramdisk
cd ../
git clone https://github.com/radxa/initrd.git
cd initrd/
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- -j4
cd ../

* Make mkbootimg
git clone https://github.com/neo-technologies/rockchip-mkbootimg.git
cd rockchip-mkbootimg
make
make install
cd ../

* Make boot.img
mkbootimg --kernel RK3188-SOM/arch/arm/boot/Image --ramdisk initrd.img -o boot.img

=== Creating the root filesystem ===
==== Debian Wheezy ====
----
In this post we will explain how you can create your own Debian rootfs with pre-installed packages of your choice, which to allow tiny Linux images to be created. All steps below should work on any Debian host (Debian/Ubuntu etc) and are verified with Ubuntu 12.04LTS. First of all you need to install the support packages on your pc:

* Install the needed packages:
sudo apt-get install qemu-user-static debootstrap binfmt-support

* Define some variables:
targetdir=rootfs
distro=wheezy

* Build first stage:
mkdir $targetdir
sudo debootstrap --arch=armhf --foreign $distro $targetdir

* Copy needed files from host to the target:
sudo cp /usr/bin/qemu-arm-static $targetdir/usr/bin/
sudo cp /etc/resolv.conf $targetdir/etc

We should now have a minimal Debian Rootfs.
* Login into the new filesystem:
sudo chroot $targetdir

* Inside the chroot we need to set up the environment again:
distro=wheezy
export LANG=C

* Now we would run the setup for the second stage of debootstrap needs to run install the packages downloaded earlier
/debootstrap/debootstrap --second-stage

* Once the package installation has finished, setup some support files and apt configuration.
cat <<EOT > /etc/apt/sources.list
deb http://ftp.uk.debian.org/debian $distro main contrib non-free
deb-src http://ftp.uk.debian.org/debian $distro main contrib non-free
deb http://ftp.uk.debian.org/debian $distro-updates main contrib non-free
deb-src http://ftp.uk.debian.org/debian $distro-updates main contrib non-free<
deb http://security.debian.org/debian-security $distro/updates main contrib non-free
deb-src http://security.debian.org/debian-security $distro/updates main contrib non-free

EOT

* Update Debian package database:
apt-get update

* Set up locales dpkg scripts since it tends to complain otherwise; note in Debian Jessie you will also need to install the dialog package as well:
apt-get install locales dialog sudo
dpkg-reconfigure locales

* Fix permission for sudo:
chmod u+s /usr/bin/sudo

* Fix ownership of man forlder
chown -R man /var/cache/man

* Install some useful packages inside the chroot:
apt-get install openssh-server ntpdate

* Set a root password so you can login:
passwd

* Build a basic network interface file:
vi /etc/network/interfaces
Add the following to get static ip:
allow-hotplug eth0
iface eth0 inet static
address 192.168.1.254
netmask 255.255.255.248
gateway 192.168.1.1
Or if you want dhcp
allow-hotplug eth0
iface eth0 inet dhcp

Note: Your board will be accessible over SSH on IP address defined above!

* Set the hostname
echo '''myhost'''> /etc/hostname
echo "127.0.0.1 '''myhost'''" >> /etc/hosts

* Enable the serial console, Debian sysvinit way
echo T0:2345:respawn:/sbin/getty -L ttyFIQ0 115200 vt100 >> /etc/inittab

This way you'll get login prompt at startup. By default you cannot login as root. To do this you should make another user, add him to the sudo group, login at startup and then login as root. To skip all this replace the line above with:
echo T0:2345:respawn:/sbin/getty -L ttyFIQ0 -a root 115200 vt100 >> /etc/inittab

* We are done inside the chroot, so quit the chroot shell
exit

* Tidy up the support files
sudo rm $targetdir/etc/resolv.conf
sudo rm $targetdir/usr/bin/qemu-arm-static

===== Installing X =====
----
You cannot run X as root (actually it's possible, but it's a bad practice), so you have to add new user to run X.

* Edit default useradd settings
vi /etc/default/useradd
Modify '''SHELL''' variable:
SHELL=/bin/bash

* Add new user
useradd '''myuser'''

* Add the user to the sudo group
adduser '''myuser''' sudo

* Make home folder
mkdir /home/'''myuser'''
chown -R '''myuser''':'''myuser''' /home/'''myuser'''

* Install xfce4 and lightdm
apt-get update
apt-get install lightdm xfce4

* Modify lightdm configuration to enable autologin:
vi /etc/lightdm/lightdm.conf
autologin-user='''myuser'''
autologin-user-timeout=0
Make sure that the right lines are uncommented. If you don't want autologin just skip the step above.

* Reboot the system
reboot
After the system loads, you should see the default desktop of xfce4.

==== Ubuntu ====
----

You can download prebuild rootfs from [http://releases.linaro.org/ linaro] site or you can build it yourself.

===== Prebuild linaro images =====
----

You can download prebuild images from https://releases.linaro.org/.
In most cases the builds are separated in:
*'''nano'''
*'''developer'''
*'''server'''
*'''alip'''

You can read additional information from [https://wiki.linaro.org/Platform/DevPlatform/Rootfs here].

In this tutorial we will build Ubuntu 14.10 ALIP rootfs.

* Make empty image file:
dd if=/dev/zero of=linaro_alip_rootfs.img bs=1M count=1024

* Format the new image file:
mkfs.ext4 -F -L linuxroot linaro_alip_rootfs.img

* Create mount point:
mkdir mnt
mount -o loop linaro_alip_rootfs.img ./mnt

* Download prebuild image:
wget https://releases.linaro.org/14.10/ubuntu/trusty-images/alip/linaro-trusty-alip-20141024-684.tar.gz

* Make sure that the archive is downloaded:
md5sum linaro-trusty-alip-20141024-684.tar.gz

* Extract is into the mounted image file:
tar -zxvf linaro-trusty-alip-20141024-684.tar.gz
mv binary/* ./mnt

* Copy any modules that are generated with the kernel:
cp -rvf /'''path/to/modules'''/lib/modules ./mnt/lib/

* Chroot into the new rootfs:
cp /usr/bin/qemu-arm-static ./mnt/usr/bin
cp /etc/resolv.conf ./mnt/etc
chroot ./mnt

* Update repository
apt-get update
'''Note!''' If you have a problem with the update, try changing '''sources.list''' to:
deb http://old-releases.ubuntu.com/ubuntu/ raring main universe restricted multiverse
deb-src http://old-releases.ubuntu.com/ubuntu/ raring main universe restricted multiverse
deb http://old-releases.ubuntu.com/ubuntu/ raring-security main universe restricted multiverse
deb-src http://old-releases.ubuntu.com/ubuntu/ raring-security main universe restricted multiverse
deb http://old-releases.ubuntu.com/ubuntu/ raring-updates main universe restricted multiverse
deb-src http://old-releases.ubuntu.com/ubuntu/ raring-updates main universe restricted multiverse
deb http://old-releases.ubuntu.com/ubuntu/ raring-backports main restricted universe multiverse
deb-src http://old-releases.ubuntu.com/ubuntu/ raring-backports main restricted universe multiverse
deb http://old-releases.ubuntu.com/ubuntu/ raring-proposed main restricted universe multiverse
deb-src http://old-releases.ubuntu.com/ubuntu/ raring-proposed main restricted universe multiverse

* Install some useful packages:
apt-get install ssh nano wpasupplicant wireless-tools

* Set root password:
passwd

Linaro prebuild images comes with default use '''linaro'''.
* Set password for user:
passwd linaro

* Add '''linaro''' to sudo group:
adduser linaro sudo

* Configure network. Create new file for loopback, wlan and eth device:
vi /etc/network/interfaces.d/lo
Inside paste:
auto lo
iface lo inet loopback

Do the same for eth:
vi /etc/network/interfaces.d/eth
If you're using dhcp:
auto eth0
iface eth0 inet dhcp
Or for static ip:
auto eth0
iface eth0 inet static
address <your.ip.here>
netmask <your.netmask.here>
gateway <your.gateway.here>

And another for wireless devices:
vi /etc/network/interfaces.d/wlan
auto wlan0
iface lo inet dhcp
wpa-ssid <your.router.ssid>
wpa-pak <your.ssid.password>

'''Note!''' All connections are '''auto'''. If you don't want to use them all the time remove '''auto''' line.

You can do some additional work before exit.
When you are ready to exit from the target filesystem:
exit

Your rootfs is ready. The next step is to create image for nand or sdcard.

===== Manual build using debootstrap =====
----
The procedure is almost identical to the one used for the Debin image.

* First of all you need to install the support packages on your pc
sudo apt-get install qemu-user-static debootstrap binfmt-support ubuntu-archive-keyring

* We will build latest trusty Ubuntu image:
targetdir=ubuntu
distro=trusty

* Now we will build first stage of Ubuntu rootfs:
mkdir $targetdir
sudo debootstrap --arch=armhf --keyring=/usr/share/keyrings/ubuntu-archive-keyring.gpg --foreign $distro $targetdir

* Login into the new filesystem
sudo cp /usr/bin/qemu-arm-static $targetdir/usr/bin/
sudo cp /etc/resolv.conf $targetdir/etc
sudo chroot $targetdir

* Inside the chroot we need to set up the environment again
distro=trusty
export LANG=C

* Now we are setup the second stage of debootstrap needs to run install the packages downloaded earlier
/debootstrap/debootstrap --second-stage

* Configure apt-sources:
cat <<EOT > /etc/apt/sources.list
###### Ubuntu Main Repos
deb http://ports.ubuntu.com/ubuntu-ports/ $distro main restricted universe multiverse
deb-src http://ports.ubuntu.com/ubuntu-ports/ $distro main restricted universe multiverse
###### Ubuntu Update Repos
deb http://ports.ubuntu.com/ubuntu-ports/ $distro-security main restricted universe multiverse
deb http://ports.ubuntu.com/ubuntu-ports/ $distro-updates main restricted universe multiverse
deb-src http://ports.ubuntu.com/ubuntu-ports/ $distro-security main restricted universe multiverse
deb-src http://ports.ubuntu.com/ubuntu-ports/ $distro-updates main restricted universe multiverse
EOT

* Update Ubuntu package database:
apt-get update

* Set a root password so you can login
passwd

* Set the hostname
echo '''myhost'''> /etc/hostname
echo "127.0.0.1 '''myhost'''" >> /etc/hosts

* Build a basic network interface file so that the board will DHCP on eth0
echo <<EOT >> /etc/network/interfaces
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet dhcp
EOT

* Enable the serial console, Debian sysvinit way
echo T0:2345:respawn:/sbin/getty -L ttyFIQ0 115200 vt100 >> /etc/inittab

This way you'll get login prompt at startup. By default you cannot login as root. To do this you should make another user,
add him to the sudo group, login at startup and then login as root. To skip all this replace the line above with:
echo T0:2345:respawn:/sbin/getty -L ttyFIQ0 -a root 115200 vt100 >> /etc/inittab

* We are done inside the chroot, so quit the chroot shell
exit

* Tidy up the support files
sudo rm $targetdir/etc/resolv.conf
sudo rm $targetdir/usr/bin/qemu-arm-static

==== Make rootfs image ====
----

Once you are ready with the rootfs you can make image file. Later it can be used for NAND or SD image. Go to parent directory of you rootfs.

* See how big the image should be:
# du -khs <roofs_folder>
For example this will return 600MB. So we will make 1GB image.

* Make empty image:
# dd if=/dev/zero of=rootfs.img bs=1M count=1024

* Format the image:
# mkfs.ex4 -F -L linuxroot rootfs.img

* Mount the image:
# mount -o loop rootfs.img /mnt

* Copy rootfs files into the image:
# cp -prf <root_folder>/* /mnt/
''''Note!''' Use -p option to keep the permissions for the files and folders.

* Unmount the image:
# umount /mnt

=== Booting from NAND ===
----
* Get rk-tools:
git clone https://github.com/goodybag/rk-tools
cd rk-tools
make

*You will need the following files:
**bootloader --> This is RockChip RK3188Loader
**[[#Building parameter file|parameter]] --> Parameter file with crc encryption
**[[#Building kernel|boot]] --> Kernel with ramdisk compiled as shown here
**[[#Creating root filesystem|linux]] --> Rootfs image file
'''CMDLINE''' in parameter file should look something like this:
CMDLINE:console=ttyFIQ0,115200 console=tty0 root=/dev/block/mtd/by-name/linuxroot rw rootfstype=ext4 init=/sbin/init initrd=0x62000000,0x00800000 mtdparts=rk29xxnand:0x00008000@0x00002000(boot),-@0x0000A000(linuxroot)

* Copy all files in '''rk-tools''' folder

* Edit '''package-file'''. It should be:
#nano package-file

# NAME Relative path
#
#HWDEF HWDEF
package-file package-file
bootloader RK3188Loader
parameter parameter
boot boot.img
linuxroot rootfs.img
backup RESERVED
update-script update-script
recover-script recover-script

* Pack the image:
./afptool -pack . update_tmp.img

* Update the image:
./img_maker -rk31 RK3188Loader 1 0 0 update_tmp.img update.img

The image should be ready. What's left is flashing the image.

*Important: to flash the image the board needs to be in bootloader mode. To enter bootloader mode you need to press and hold down the recovery button before connecting the board to the PC. After the connection is established you can release the button.

 

=== Booting from SD-card ===
----
You'll need at least 512MB sd-card. Depending on rootfs needed size can grow to 4GB.

*You will need the following files:
**sdboot_rk3188.img --> RK3188Loader for booting from SDcard
**[[#Building parameter file|parameter]] --> Parameter file with crc encryption
**[[#Building kernel|boot]] --> Kernel with ramdisk compiled as shown here
**[[#Creating root filesystem|linux]] --> Rootfs image file

'''CMDLINE''' in parameter file should look something like this:
CMDLINE:console=ttyFIQ0,115200 console=tty0 root=/dev/mmcblk0p1 rw rootfstype=ext4 init=/sbin/init initrd=0x62000000,0x00800000 mtdparts=rk29xxnand:0x00008000@0x00002000(boot),-@0x0000A000(linuxroot)

Insert sd-card. Lets say that your device is '''/dev/sdc'''.

* Write Rockchip loader:
dd if=sdboot_rk3188.img of=/dev/sdc conv=sync,fsync

* Write parameter file:
dd if=parameter.img of=/dev/sdc conv=sync,fsync seek=$((0x2000))

* Write kernel:
dd if=boot.img of=/dev/sdc conv=sync,fsync seek=$((0x2000+0x2000))

* Write rootfs:
dd if=rootfs.img of=/dev/sdc conv=sync,fsync seek=$((0x2000+0xA000))

You can do this also on image file:
dd if=/dev/zero of=sd.img bs=1M count=1024
If 1GB is not enough increase count number.

* Write Rockchip loader:
dd if=sdboot_rk3188.img of=sd.img conv=sync,fsync

* Write parameter file:
dd if=parameter.img of=sd.img conv=sync,fsync seek=$((0x2000))

* Write kernel:
dd if=boot.img of=sd.img conv=sync,fsync seek=$((0x2000+0x2000))

* Write rootfs:
dd if=rootfs.img of=sd.img conv=sync,fsync seek=$((0x2000+0xA000))

* Format image:
fdisk sd.img << EOF
n
p
1
49152

w
EOF

=== Calibrate touchscreen ===
If you want to use LCD panel with touchscreen, you should perform a screen calibration.

==== Calibrate using tslib ====
----

* Install the required packages:
apt-get update
apt-get install xorg-dev xserver-xorg-dev x11proto-core-dev git automake make libtool

* Download tslib:
git clone https://github.com/kergoth/tslib.git
cd tslib

* Download patch:
cd plugin
wget https://dl.dropbox.com/u/40057/patches/input-raw.c
cd ../

* Compile the library:
autoreconf -vi
./configure --prefix=/usr
make
make install
ldconfig

* Modify tslib configuration
vi /usr/etc/ts.conf
Uncomment the following line:
module_raw input

* Export tslib needed variables:
export TSLIB_TSEVENTTYPE=raw
export TSLIB_CONSOLEDEVICE=none
export TSLIB_FBDEVICE=/dev/fb0
export TSLIB_TSDEVICE=/dev/input/event0
export TSLIB_CALIBFILE=/usr/etc/pointercal
export TSLIB_CONFFILE=/usr/etc/ts.conf
export TSLIB_PLUGINDIR=/usr/lib/ts

* Now tslib is working but still it should be set as default driver in the X:
wget http://ftp.de.debian.org/debian/pool/main/x/xf86-input-tslib/xf86-input-tslib_0.0.6.orig.tar.gz
tar zxfv xf86-input-tslib_0.0.6.orig.tar.gz
cd xf86-input-tslib-0.0.6/
Replace tslib.c file with patched one:
cd src/
rm -f tslib.c
wget https://dl.dropbox.com/u/40057/patches/tslib.c
cd ..
Build and install package:
./configure --prefix=/usr
make
make install

* Add tslib configuration:
cd /usr/share/X11/xorg.conf.d/
Make new file:
nano 20-touchscreen.conf
Add the following text inside:
Section "InputClass"
Identifier "AR1020"
MatchDevicePath "/dev/input/event0"
Driver "tslib"
Option "Device" "/dev/input/event0"
Option "ScreenNumber" "0"
Option "Rotate" "NONE"
Option "Width" "'''800'''"
Option "Height" "'''480'''"
Option "SendCoreEvents" "yes"
Option "Type" "touchscreen"
EndSection
Note! Resolution in this example is set for 7 inch LCD.

* Do the actual calibration:
service lightdm stop
ts_calibrate
service lightdm start
After lightdm start you could check if everything is running smoothly.

* Save tslib variables:
vi /etc/environment
Paste the following:
TSLIB_TSEVENTTYPE=raw
TSLIB_CONSOLEDEVICE=none
TSLIB_FBDEVICE=/dev/fb0
TSLIB_TSDEVICE=/dev/input/event0
TSLIB_CALIBFILE=/etc/pointercal
TSLIB_CONFFILE=/usr/etc/ts.conf
TSLIB_PLUGINDIR=/usr/lib/ts

If you change the LCD panel run ts_calibrate to configure touchscreen for the new LCD.

==== Calibrate using AR1021 driver ====
TODO

=== Enabling wireless modules ===
==== RTL8188CUS ====
----
[[File:MOD-WIFI-RTL8188-1.jpg|thumb|[https://www.olimex.com/Products/USB-Modules/MOD-WIFI-RTL8188/ MOD-WIFI-RTL8188]]]
To connect OLinuXino board with wireless, you could use [https://www.olimex.com/Products/USB-Modules/MOD-WIFI-RTL8188/ MOD-WIFI-RTL8188] dongle. Also you can use another one with the same chip.

[https://www.olimex.com/Products/USB-Modules/MOD-WIFI-RTL8188/ MOD-WIFI-RTL8188] has the following features:
* Has WM-294 module with RTL8188
* Operates in 2.4 GHz frequency bands
* 1x1 MIMO technology improves effective throughput and range over existing 802.11 b/g products
* Data rates: up to 150Mbps
* 802.11e-compatible bursting and I standards BPSK, QPSK, 16 QAM, 64 QAM modulation schemes WEP, TKIP, and AES, WPA, WPA2 hardware encryption schemes
* Standard USB type A connector
* On-board antenna
* 5V/3.3V operation modes via SMD jumper
* 4 test pads for easy tracking the supply, d-, d+, and GND
* PCB: FR-4, 1.00 mm (0,039"), solder mask, silkscreen component print
* Dimensions: 65.15x20.38 mm (2.56x0.80")
----

The kernel module is prebuild. You should just get it loaded and then plug the dongle.
* Load the module:
modprobe 8192cu

* Plug the device and check if it is available:
ifconfig -a

==== RT5370 ====
----
[[File:MOD-WIFI-R5370-ANT-1.jpg|border|thumb|[https://www.olimex.com/Products/USB-Modules/MOD-WIFI-R5370-ANT/ MOD-WIFI-R5370-ANT]]]

To use one this wifi dongle (like [https://www.olimex.com/Products/USB-Modules/MOD-WIFI-R5370/ MOD-WIFI-R5370] or [https://www.olimex.com/Products/USB-Modules/MOD-WIFI-R5370-ANT/ MOD-WIFI-R5370-ANT]) additional files are required.

[https://www.olimex.com/Products/USB-Modules/MOD-WIFI-R5370-ANT/ MOD-WIFI-R5370-ANT] has the following features:

* 2.4GHz with 150Mbps PHY data rate
*External antenna for extended range
*USB 2.0 interface
*Security: WEP/TKIP/AES/WPA/WPA2/WAPI
*CMOS single chip with RF, baseband, and MAC integration
*QoS: WMM & WMM-PS support
*Multiple BSSID support
*Maximum likelihood decoding support
*Cisco CCX 5.0 support
*Low-power usage with advanced power management
----

*First a make new directory and navigate to it. This is where the module will search for files.
mkdir -p /etc/Wireless/RT2870STA
cd /etc/Wireless/RT2870STA/

*Download the files from Github
wget https://raw.githubusercontent.com/SelfDestroyer/RK3188-SOM/olimex/stable-3.0/drivers/net/wireless/rtxx7x/RT2870STA.dat
wget https://raw.githubusercontent.com/SelfDestroyer/RK3188-SOM/olimex/stable-3.0/drivers/net/wireless/rtxx7x/RT2870STACard.dat

*Load module
modprobe rt5370sta

*Plug the device and run:
ifconfig -a
*You should see this:
wlan0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

*Configure your new device:
vi /etc/network/interfaces
*Add configuration. Here we will show DHCP configuration.
iface wlan0 inet dhcp
wpa-ssid "'''your ssid'''"
wpa-psk "'''your password'''"

*Save the configuration and up the interface:
ifup wlan0

*If everything is working and this module to be loaded on boot:
echo rt5370sta >> /etc/modules

== Android ==

RK3188-SOM

2023-04-21T10:22:19Z

LubOlimex: /* Debian for microSD card */

== Overview ==

[[File:Rk3188-som-resized.png|650px]]

RK3188-SOM board is a very productive small beast compared to the previous Olimex board designs. If we compare RockChip RK3188 and Allwinner A20: RK3188 has 4x Cortex-A9, while A20 only 2x Cortex-A7. It runs at 1.6 GHz vs. the 1.0 GHz frequency of the A20. RK3188 reaches a total of 16000 DMPIS vs. the 3800 DMIPS for the A20 (RK3188 is 4.2 times faster). For comparison, the RaspberryPi has 965 DMIPS (RK3188 is 16.6 times faster).

The RK3188-SOM design has the following features:

*Rockchip RK3188 quad core Cortex-A9 processor, each core typically running at 1.6GHz
*1GB DDR3 memory
*Integrated power management unit
*Optional 4GB NAND flash memory for Linux or Android boot
*Micro SD-card for Linux or Android boot
*Three buttons - POWER, RESET, RECOVERY
*Four LEDs (one for power and three user-programmable)
*UART console pins exposed for serial debug
*Five GPIO connectors 2×20 pins @ 0.05" step
*Dimensions: (3.2×1.8)" ~ (81×56)mm
 

== Ready-to-use Debian images ==
=== Debian for microSD card ===

'''Newest official release (recommended):'''

Direct download of Debian release #2:[https://ftp.olimex.com/Rockchip_images/sd/debian/RK3188_debian_3.0.36_SD_release2.img.7z RK3188-SOM Debian for microSD card - kernel 3.0.36+ - release #2]

In the command line interface of image you are automatically logged as root. The default superuser username/password combination in the GUI (XFCE4) is: olimex/olimex.

Build instructions and links to required files for the latest Debian images might be found below in chapter "Building Linux for RK3188-SOM".

'''Older official releases (not recommended):'''

Direct download of Debian release #1:[[https://ftp.olimex.com/Rockchip_images/sd/debian/RK3188_debian_3.0.36_SD_release2.img.7z|RK3188-SOM Debian for microSD card - kernel 3.0.36+ - release #1]]

====How to prepare your microSD card with the suitable official Debian image?====
----
In order to download an official Linux image to a microSD card under Windows you can use Win32 Disk Imager: [http://sourceforge.net/projects/win32diskimager/ click here]

1. Download the latest official image suitable for a microSD card from the chapter above

2. Download Win32 Disk Imager from this link.

3. Insert card in your microSD card reader.

4. Launch the software.

5. Point the software to the image

6. Click "write"

Under Linux you can write the image image to the card with dd utility. This is how it can be done:

Let's say the name of the image is "debian_2g.img". It would be downloaded to the microSD card connected to a Linux machine using one of the following commands:

dd bs=4M oflag=sync if=debian_2g.img of=/dev/sdX

or

cp debian_2g.img /dev/sdX

where /dev/sdX is the uSD card as listed by the Linux.

=== Debian for NAND memory ===

'''Newest official release (recommended):'''

Direct download Debian for NAND release #1: [https://ftp.olimex.com/Rockchip_images/nand/debian/RK3188_debian_3.0.36_NAND_release1.img.7z|RK3188-SOM Debian for NAND memory - kernel 3.0.36+ - release #1]

Note that this image is suitable only for RK3188-SOM-4GB boards.

Build instructions and links to required files for the latest Debian images might be found below in chapter "Building Linux for RK3188-SOM"

====How to download the ready Debian image to the NAND memory of RK3188-SOM?====
----

'''IMPORTANT: RK3188-SOM-4GB comes with Debian already pre-loaded on the NAND memory. No need to perform this operation initially.'''

1. You need to download the software tools for your computer provided by Rockchip. If you use Windows download “Rockchip Batch Tool”. If you use Linux use either rkflashkit or upgrade_tool. These are the tools that I recommend but there are a lot of tools available. Get the Rockchip batch tool from here: [https://drive.google.com/file/d/0BwplT87k9SCgRDB4ZGY3SnMzd00/view?usp=sharing Rockchip Batch Tool]

For Windows:

2. Install the drivers that allows your computer to recognize the board (that is already set in bootloader mode) connected to it. The installer is called "Rockchip Driver Assistant" – download it here: [https://drive.google.com/file/d/0BwplT87k9SCgbkdXX1ByUW1RSW8/view?usp=sharing Rockchip Driver Assistant]

3. You need to download and extract the latest image suitable for the NAND from our wiki. It is available as a direct download here: [https://ftp.olimex.com/Rockchip_images/nand/debian/RK3188_debian_3.0.36_NAND_release1.img.7z%7CRK3188-SOM|RK3188 Debian 3.0.36 for NAND memory]

4. You need enter bootloader mode with the board to be able to establish connection between the board and the software provided by Rockchip. You would also need a mini USB cable. To enter bootloader mode you need to press and hold down the recovery button before powering the board (then connect the board to the PC via the mini USB cable). After the board is powered you can release the button.

5. Start the tool for uploading the firmware and point it to the extracted image.

6. Click button "Upgrade".

7. Test with a serial cable.

== Ready-to-use Android images ==
TODO

== Documents ==

[https://www.olimex.com/Products/SOM/RK3188/RK3188-SOM/resources/RK3188-SOM-UM.pdf OLIMEX RK3188-SOM user's manual]

[https://www.olimex.com/Products/SOM/RK3188/RK3188-SOM-EVB/resources/RK3188-SOM-EVB-UM.pdf OLIMEX RK3188-SOM-EVB user's manual]

[https://github.com/OLIMEX/OLINUXINO/raw/master/HARDWARE/RK3188-PDFs/Rockchip%20RK3188%20datasheet%20V1.0.pdf Processor (Rockchip RK3188) datasheet in pdf format]

[https://www.olimex.com/Products/SOM/RK3188/RK3188-SOM/resources/RK3188_SOM_GPIOs.pdf RK3188-SOM connectors' pinout and GPIO table]

=== CAD files ===

RK3188-SOM is considered commercial, proprietary design. The board file is not available to the customer. A pdf extracted from the original schematic is available at GitHub: [https://github.com/OLIMEX/SOM/tree/master/RK3188/RK3188-SOM RK3188-SOM schematics]

RK3188-SOM-EVB is considered Open Source Hardware, Eagle CAD files are available also at GitHub: [https://github.com/OLIMEX/SOM/tree/master/RK3188/RK3188-EVB RK3188-SOM-EVB sources]

The CAD product used to design OLinuXino is Eagle and you can download evaluation free version from their [http://www.cadsoftusa.com/ web site]. The evaluation version allows you to inspect the schematic and the board file sources.

==Board Layout==

[[File:Rk3188-som-resized-TOP-NAMED.png|650px]]

[[File:Rk3188-som-resized-BOTTOM-NAMED.png|650px]]

== Building Linux for RK3188-SOM ==
=== Building the parameter file ===
----
The parameter file describes many board parameters as firmware version, machine id, manufacturer name, etc.

For the user the most important parameter is '''CMDLINE'''. This is the command that is passed to the kernel. It looks something like this:
CMDLINE:console=ttyFIQ0,115200 console=tty0 root=/dev/mmcblk0p1 rw rootfstype=ext4 init=/sbin/init initrd=0x62000000,0x00800000 \
mtdparts=rk29xxnand:0x00008000@0x00002000(boot),-@0x0000A000(linuxroot)

Define serial port at 115200:
console=ttyFIQ0,115200

Define location of the rootfs:
root=/dev/mmcblk0p1

Define rootfs file system as ext4:
rootfstype=ext4

Define the address of the kernel and size:
0x00008000@0x00002000

Define start address of the rootfs:
-@0x0000A000

Additionally, you can set static MAC address with:
mac_addr=xx:xx:xx:xx:xx:xx

Once you're ready with the file, make the parameter image

* Get rkutils:
https://github.com/naobsd/rkutils
cd rkutils
gcc rkcrc.c -o rkcrc
If you're getting error try to comment ''''#include <err.h>'''' in ''''rkcrc.c''''

* Encrypt parameter file:
./rkcrc -p you_parameter_file parameter

The parameter file is ready for further use.

=== Building the kernel ===
----
* Fist prepare the toolchain:
apt-get update
apt-get install gcc-4.7-arm-linux-gnueabihf ncurses-dev uboot-mkimage build-essential git

* Get the sources:
git clone -b olimex/stable-3.0 https://github.com/StefanMavrodiev/RK3188-SOM.git

* Get the default configuration:
cd RK3188-SOM/
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- '''olimex_rk3188_defconfig'''

* You can modify defconfig with (for additional modules):
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- menuconfig

'''Note!''' The default config will set hdmi to 1080p. You can change it from:
Device Drivers --->
Graphics support --->
<*> Frame buffer support for Rockchip --->
LCD Panel Select --->
'''''Choose one of the following:'''''
HDMI framebuffer size and timing is 1080p <--- '''Set HDMI to 1080p'''
HDMI framebuffer size and timing is 720p <--- '''Set HDMI to 720p'''
HDMI framebuffer size and timing is 480p <--- '''Set HDMI to 480p'''
RGB AT070TN90 <--- [https://www.olimex.com/Products/OLinuXino/LCD/LCD-OLinuXino-7/open-source-hardware LCD-OLinuXino-7]
RGB AR010H05N <--- [https://www.olimex.com/Products/OLinuXino/LCD/LCD-OLinuXino-10/open-source-hardware LCD-OLinuXino-10]
RGB BT043DCNNHHP <--- [https://www.olimex.com/Products/OLinuXino/LCD/LCD-OLinuXino-4.3TS/open-source-hardware LCD-OLinuXino-4.3TS]

* Build the kernel:
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- -j4 kernel.img
After the build is finish you will have '''RK3188-SOM/kernel.img''' and '''RK3188-SOM/arch/arm/boot/Image'''. The first one can be uploaded to the kernel partition (if you have one). The second file is raw binary. It can be combined with ramdisk to get boot.img.

* Generate ramdisk
cd ../
git clone https://github.com/radxa/initrd.git
cd initrd/
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- -j4
cd ../

* Make mkbootimg
git clone https://github.com/neo-technologies/rockchip-mkbootimg.git
cd rockchip-mkbootimg
make
make install
cd ../

* Make boot.img
mkbootimg --kernel RK3188-SOM/arch/arm/boot/Image --ramdisk initrd.img -o boot.img

=== Creating the root filesystem ===
==== Debian Wheezy ====
----
In this post we will explain how you can create your own Debian rootfs with pre-installed packages of your choice, which to allow tiny Linux images to be created. All steps below should work on any Debian host (Debian/Ubuntu etc) and are verified with Ubuntu 12.04LTS. First of all you need to install the support packages on your pc:

* Install the needed packages:
sudo apt-get install qemu-user-static debootstrap binfmt-support

* Define some variables:
targetdir=rootfs
distro=wheezy

* Build first stage:
mkdir $targetdir
sudo debootstrap --arch=armhf --foreign $distro $targetdir

* Copy needed files from host to the target:
sudo cp /usr/bin/qemu-arm-static $targetdir/usr/bin/
sudo cp /etc/resolv.conf $targetdir/etc

We should now have a minimal Debian Rootfs.
* Login into the new filesystem:
sudo chroot $targetdir

* Inside the chroot we need to set up the environment again:
distro=wheezy
export LANG=C

* Now we would run the setup for the second stage of debootstrap needs to run install the packages downloaded earlier
/debootstrap/debootstrap --second-stage

* Once the package installation has finished, setup some support files and apt configuration.
cat <<EOT > /etc/apt/sources.list
deb http://ftp.uk.debian.org/debian $distro main contrib non-free
deb-src http://ftp.uk.debian.org/debian $distro main contrib non-free
deb http://ftp.uk.debian.org/debian $distro-updates main contrib non-free
deb-src http://ftp.uk.debian.org/debian $distro-updates main contrib non-free<
deb http://security.debian.org/debian-security $distro/updates main contrib non-free
deb-src http://security.debian.org/debian-security $distro/updates main contrib non-free

EOT

* Update Debian package database:
apt-get update

* Set up locales dpkg scripts since it tends to complain otherwise; note in Debian Jessie you will also need to install the dialog package as well:
apt-get install locales dialog sudo
dpkg-reconfigure locales

* Fix permission for sudo:
chmod u+s /usr/bin/sudo

* Fix ownership of man forlder
chown -R man /var/cache/man

* Install some useful packages inside the chroot:
apt-get install openssh-server ntpdate

* Set a root password so you can login:
passwd

* Build a basic network interface file:
vi /etc/network/interfaces
Add the following to get static ip:
allow-hotplug eth0
iface eth0 inet static
address 192.168.1.254
netmask 255.255.255.248
gateway 192.168.1.1
Or if you want dhcp
allow-hotplug eth0
iface eth0 inet dhcp

Note: Your board will be accessible over SSH on IP address defined above!

* Set the hostname
echo '''myhost'''> /etc/hostname
echo "127.0.0.1 '''myhost'''" >> /etc/hosts

* Enable the serial console, Debian sysvinit way
echo T0:2345:respawn:/sbin/getty -L ttyFIQ0 115200 vt100 >> /etc/inittab

This way you'll get login prompt at startup. By default you cannot login as root. To do this you should make another user, add him to the sudo group, login at startup and then login as root. To skip all this replace the line above with:
echo T0:2345:respawn:/sbin/getty -L ttyFIQ0 -a root 115200 vt100 >> /etc/inittab

* We are done inside the chroot, so quit the chroot shell
exit

* Tidy up the support files
sudo rm $targetdir/etc/resolv.conf
sudo rm $targetdir/usr/bin/qemu-arm-static

===== Installing X =====
----
You cannot run X as root (actually it's possible, but it's a bad practice), so you have to add new user to run X.

* Edit default useradd settings
vi /etc/default/useradd
Modify '''SHELL''' variable:
SHELL=/bin/bash

* Add new user
useradd '''myuser'''

* Add the user to the sudo group
adduser '''myuser''' sudo

* Make home folder
mkdir /home/'''myuser'''
chown -R '''myuser''':'''myuser''' /home/'''myuser'''

* Install xfce4 and lightdm
apt-get update
apt-get install lightdm xfce4

* Modify lightdm configuration to enable autologin:
vi /etc/lightdm/lightdm.conf
autologin-user='''myuser'''
autologin-user-timeout=0
Make sure that the right lines are uncommented. If you don't want autologin just skip the step above.

* Reboot the system
reboot
After the system loads, you should see the default desktop of xfce4.

==== Ubuntu ====
----

You can download prebuild rootfs from [http://releases.linaro.org/ linaro] site or you can build it yourself.

===== Prebuild linaro images =====
----

You can download prebuild images from https://releases.linaro.org/.
In most cases the builds are separated in:
*'''nano'''
*'''developer'''
*'''server'''
*'''alip'''

You can read additional information from [https://wiki.linaro.org/Platform/DevPlatform/Rootfs here].

In this tutorial we will build Ubuntu 14.10 ALIP rootfs.

* Make empty image file:
dd if=/dev/zero of=linaro_alip_rootfs.img bs=1M count=1024

* Format the new image file:
mkfs.ext4 -F -L linuxroot linaro_alip_rootfs.img

* Create mount point:
mkdir mnt
mount -o loop linaro_alip_rootfs.img ./mnt

* Download prebuild image:
wget https://releases.linaro.org/14.10/ubuntu/trusty-images/alip/linaro-trusty-alip-20141024-684.tar.gz

* Make sure that the archive is downloaded:
md5sum linaro-trusty-alip-20141024-684.tar.gz

* Extract is into the mounted image file:
tar -zxvf linaro-trusty-alip-20141024-684.tar.gz
mv binary/* ./mnt

* Copy any modules that are generated with the kernel:
cp -rvf /'''path/to/modules'''/lib/modules ./mnt/lib/

* Chroot into the new rootfs:
cp /usr/bin/qemu-arm-static ./mnt/usr/bin
cp /etc/resolv.conf ./mnt/etc
chroot ./mnt

* Update repository
apt-get update
'''Note!''' If you have a problem with the update, try changing '''sources.list''' to:
deb http://old-releases.ubuntu.com/ubuntu/ raring main universe restricted multiverse
deb-src http://old-releases.ubuntu.com/ubuntu/ raring main universe restricted multiverse
deb http://old-releases.ubuntu.com/ubuntu/ raring-security main universe restricted multiverse
deb-src http://old-releases.ubuntu.com/ubuntu/ raring-security main universe restricted multiverse
deb http://old-releases.ubuntu.com/ubuntu/ raring-updates main universe restricted multiverse
deb-src http://old-releases.ubuntu.com/ubuntu/ raring-updates main universe restricted multiverse
deb http://old-releases.ubuntu.com/ubuntu/ raring-backports main restricted universe multiverse
deb-src http://old-releases.ubuntu.com/ubuntu/ raring-backports main restricted universe multiverse
deb http://old-releases.ubuntu.com/ubuntu/ raring-proposed main restricted universe multiverse
deb-src http://old-releases.ubuntu.com/ubuntu/ raring-proposed main restricted universe multiverse

* Install some useful packages:
apt-get install ssh nano wpasupplicant wireless-tools

* Set root password:
passwd

Linaro prebuild images comes with default use '''linaro'''.
* Set password for user:
passwd linaro

* Add '''linaro''' to sudo group:
adduser linaro sudo

* Configure network. Create new file for loopback, wlan and eth device:
vi /etc/network/interfaces.d/lo
Inside paste:
auto lo
iface lo inet loopback

Do the same for eth:
vi /etc/network/interfaces.d/eth
If you're using dhcp:
auto eth0
iface eth0 inet dhcp
Or for static ip:
auto eth0
iface eth0 inet static
address <your.ip.here>
netmask <your.netmask.here>
gateway <your.gateway.here>

And another for wireless devices:
vi /etc/network/interfaces.d/wlan
auto wlan0
iface lo inet dhcp
wpa-ssid <your.router.ssid>
wpa-pak <your.ssid.password>

'''Note!''' All connections are '''auto'''. If you don't want to use them all the time remove '''auto''' line.

You can do some additional work before exit.
When you are ready to exit from the target filesystem:
exit

Your rootfs is ready. The next step is to create image for nand or sdcard.

===== Manual build using debootstrap =====
----
The procedure is almost identical to the one used for the Debin image.

* First of all you need to install the support packages on your pc
sudo apt-get install qemu-user-static debootstrap binfmt-support ubuntu-archive-keyring

* We will build latest trusty Ubuntu image:
targetdir=ubuntu
distro=trusty

* Now we will build first stage of Ubuntu rootfs:
mkdir $targetdir
sudo debootstrap --arch=armhf --keyring=/usr/share/keyrings/ubuntu-archive-keyring.gpg --foreign $distro $targetdir

* Login into the new filesystem
sudo cp /usr/bin/qemu-arm-static $targetdir/usr/bin/
sudo cp /etc/resolv.conf $targetdir/etc
sudo chroot $targetdir

* Inside the chroot we need to set up the environment again
distro=trusty
export LANG=C

* Now we are setup the second stage of debootstrap needs to run install the packages downloaded earlier
/debootstrap/debootstrap --second-stage

* Configure apt-sources:
cat <<EOT > /etc/apt/sources.list
###### Ubuntu Main Repos
deb http://ports.ubuntu.com/ubuntu-ports/ $distro main restricted universe multiverse
deb-src http://ports.ubuntu.com/ubuntu-ports/ $distro main restricted universe multiverse
###### Ubuntu Update Repos
deb http://ports.ubuntu.com/ubuntu-ports/ $distro-security main restricted universe multiverse
deb http://ports.ubuntu.com/ubuntu-ports/ $distro-updates main restricted universe multiverse
deb-src http://ports.ubuntu.com/ubuntu-ports/ $distro-security main restricted universe multiverse
deb-src http://ports.ubuntu.com/ubuntu-ports/ $distro-updates main restricted universe multiverse
EOT

* Update Ubuntu package database:
apt-get update

* Set a root password so you can login
passwd

* Set the hostname
echo '''myhost'''> /etc/hostname
echo "127.0.0.1 '''myhost'''" >> /etc/hosts

* Build a basic network interface file so that the board will DHCP on eth0
echo <<EOT >> /etc/network/interfaces
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet dhcp
EOT

* Enable the serial console, Debian sysvinit way
echo T0:2345:respawn:/sbin/getty -L ttyFIQ0 115200 vt100 >> /etc/inittab

This way you'll get login prompt at startup. By default you cannot login as root. To do this you should make another user,
add him to the sudo group, login at startup and then login as root. To skip all this replace the line above with:
echo T0:2345:respawn:/sbin/getty -L ttyFIQ0 -a root 115200 vt100 >> /etc/inittab

* We are done inside the chroot, so quit the chroot shell
exit

* Tidy up the support files
sudo rm $targetdir/etc/resolv.conf
sudo rm $targetdir/usr/bin/qemu-arm-static

==== Make rootfs image ====
----

Once you are ready with the rootfs you can make image file. Later it can be used for NAND or SD image. Go to parent directory of you rootfs.

* See how big the image should be:
# du -khs <roofs_folder>
For example this will return 600MB. So we will make 1GB image.

* Make empty image:
# dd if=/dev/zero of=rootfs.img bs=1M count=1024

* Format the image:
# mkfs.ex4 -F -L linuxroot rootfs.img

* Mount the image:
# mount -o loop rootfs.img /mnt

* Copy rootfs files into the image:
# cp -prf <root_folder>/* /mnt/
''''Note!''' Use -p option to keep the permissions for the files and folders.

* Unmount the image:
# umount /mnt

=== Booting from NAND ===
----
* Get rk-tools:
git clone https://github.com/goodybag/rk-tools
cd rk-tools
make

*You will need the following files:
**bootloader --> This is RockChip RK3188Loader
**[[#Building parameter file|parameter]] --> Parameter file with crc encryption
**[[#Building kernel|boot]] --> Kernel with ramdisk compiled as shown here
**[[#Creating root filesystem|linux]] --> Rootfs image file
'''CMDLINE''' in parameter file should look something like this:
CMDLINE:console=ttyFIQ0,115200 console=tty0 root=/dev/block/mtd/by-name/linuxroot rw rootfstype=ext4 init=/sbin/init initrd=0x62000000,0x00800000 mtdparts=rk29xxnand:0x00008000@0x00002000(boot),-@0x0000A000(linuxroot)

* Copy all files in '''rk-tools''' folder

* Edit '''package-file'''. It should be:
#nano package-file

# NAME Relative path
#
#HWDEF HWDEF
package-file package-file
bootloader RK3188Loader
parameter parameter
boot boot.img
linuxroot rootfs.img
backup RESERVED
update-script update-script
recover-script recover-script

* Pack the image:
./afptool -pack . update_tmp.img

* Update the image:
./img_maker -rk31 RK3188Loader 1 0 0 update_tmp.img update.img

The image should be ready. What's left is flashing the image.

*Important: to flash the image the board needs to be in bootloader mode. To enter bootloader mode you need to press and hold down the recovery button before connecting the board to the PC. After the connection is established you can release the button.

 

=== Booting from SD-card ===
----
You'll need at least 512MB sd-card. Depending on rootfs needed size can grow to 4GB.

*You will need the following files:
**sdboot_rk3188.img --> RK3188Loader for booting from SDcard
**[[#Building parameter file|parameter]] --> Parameter file with crc encryption
**[[#Building kernel|boot]] --> Kernel with ramdisk compiled as shown here
**[[#Creating root filesystem|linux]] --> Rootfs image file

'''CMDLINE''' in parameter file should look something like this:
CMDLINE:console=ttyFIQ0,115200 console=tty0 root=/dev/mmcblk0p1 rw rootfstype=ext4 init=/sbin/init initrd=0x62000000,0x00800000 mtdparts=rk29xxnand:0x00008000@0x00002000(boot),-@0x0000A000(linuxroot)

Insert sd-card. Lets say that your device is '''/dev/sdc'''.

* Write Rockchip loader:
dd if=sdboot_rk3188.img of=/dev/sdc conv=sync,fsync

* Write parameter file:
dd if=parameter.img of=/dev/sdc conv=sync,fsync seek=$((0x2000))

* Write kernel:
dd if=boot.img of=/dev/sdc conv=sync,fsync seek=$((0x2000+0x2000))

* Write rootfs:
dd if=rootfs.img of=/dev/sdc conv=sync,fsync seek=$((0x2000+0xA000))

You can do this also on image file:
dd if=/dev/zero of=sd.img bs=1M count=1024
If 1GB is not enough increase count number.

* Write Rockchip loader:
dd if=sdboot_rk3188.img of=sd.img conv=sync,fsync

* Write parameter file:
dd if=parameter.img of=sd.img conv=sync,fsync seek=$((0x2000))

* Write kernel:
dd if=boot.img of=sd.img conv=sync,fsync seek=$((0x2000+0x2000))

* Write rootfs:
dd if=rootfs.img of=sd.img conv=sync,fsync seek=$((0x2000+0xA000))

* Format image:
fdisk sd.img << EOF
n
p
1
49152

w
EOF

=== Calibrate touchscreen ===
If you want to use LCD panel with touchscreen, you should perform a screen calibration.

==== Calibrate using tslib ====
----

* Install the required packages:
apt-get update
apt-get install xorg-dev xserver-xorg-dev x11proto-core-dev git automake make libtool

* Download tslib:
git clone https://github.com/kergoth/tslib.git
cd tslib

* Download patch:
cd plugin
wget https://dl.dropbox.com/u/40057/patches/input-raw.c
cd ../

* Compile the library:
autoreconf -vi
./configure --prefix=/usr
make
make install
ldconfig

* Modify tslib configuration
vi /usr/etc/ts.conf
Uncomment the following line:
module_raw input

* Export tslib needed variables:
export TSLIB_TSEVENTTYPE=raw
export TSLIB_CONSOLEDEVICE=none
export TSLIB_FBDEVICE=/dev/fb0
export TSLIB_TSDEVICE=/dev/input/event0
export TSLIB_CALIBFILE=/usr/etc/pointercal
export TSLIB_CONFFILE=/usr/etc/ts.conf
export TSLIB_PLUGINDIR=/usr/lib/ts

* Now tslib is working but still it should be set as default driver in the X:
wget http://ftp.de.debian.org/debian/pool/main/x/xf86-input-tslib/xf86-input-tslib_0.0.6.orig.tar.gz
tar zxfv xf86-input-tslib_0.0.6.orig.tar.gz
cd xf86-input-tslib-0.0.6/
Replace tslib.c file with patched one:
cd src/
rm -f tslib.c
wget https://dl.dropbox.com/u/40057/patches/tslib.c
cd ..
Build and install package:
./configure --prefix=/usr
make
make install

* Add tslib configuration:
cd /usr/share/X11/xorg.conf.d/
Make new file:
nano 20-touchscreen.conf
Add the following text inside:
Section "InputClass"
Identifier "AR1020"
MatchDevicePath "/dev/input/event0"
Driver "tslib"
Option "Device" "/dev/input/event0"
Option "ScreenNumber" "0"
Option "Rotate" "NONE"
Option "Width" "'''800'''"
Option "Height" "'''480'''"
Option "SendCoreEvents" "yes"
Option "Type" "touchscreen"
EndSection
Note! Resolution in this example is set for 7 inch LCD.

* Do the actual calibration:
service lightdm stop
ts_calibrate
service lightdm start
After lightdm start you could check if everything is running smoothly.

* Save tslib variables:
vi /etc/environment
Paste the following:
TSLIB_TSEVENTTYPE=raw
TSLIB_CONSOLEDEVICE=none
TSLIB_FBDEVICE=/dev/fb0
TSLIB_TSDEVICE=/dev/input/event0
TSLIB_CALIBFILE=/etc/pointercal
TSLIB_CONFFILE=/usr/etc/ts.conf
TSLIB_PLUGINDIR=/usr/lib/ts

If you change the LCD panel run ts_calibrate to configure touchscreen for the new LCD.

==== Calibrate using AR1021 driver ====
TODO

=== Enabling wireless modules ===
==== RTL8188CUS ====
----
[[File:MOD-WIFI-RTL8188-1.jpg|thumb|[https://www.olimex.com/Products/USB-Modules/MOD-WIFI-RTL8188/ MOD-WIFI-RTL8188]]]
To connect OLinuXino board with wireless, you could use [https://www.olimex.com/Products/USB-Modules/MOD-WIFI-RTL8188/ MOD-WIFI-RTL8188] dongle. Also you can use another one with the same chip.

[https://www.olimex.com/Products/USB-Modules/MOD-WIFI-RTL8188/ MOD-WIFI-RTL8188] has the following features:
* Has WM-294 module with RTL8188
* Operates in 2.4 GHz frequency bands
* 1x1 MIMO technology improves effective throughput and range over existing 802.11 b/g products
* Data rates: up to 150Mbps
* 802.11e-compatible bursting and I standards BPSK, QPSK, 16 QAM, 64 QAM modulation schemes WEP, TKIP, and AES, WPA, WPA2 hardware encryption schemes
* Standard USB type A connector
* On-board antenna
* 5V/3.3V operation modes via SMD jumper
* 4 test pads for easy tracking the supply, d-, d+, and GND
* PCB: FR-4, 1.00 mm (0,039"), solder mask, silkscreen component print
* Dimensions: 65.15x20.38 mm (2.56x0.80")
----

The kernel module is prebuild. You should just get it loaded and then plug the dongle.
* Load the module:
modprobe 8192cu

* Plug the device and check if it is available:
ifconfig -a

==== RT5370 ====
----
[[File:MOD-WIFI-R5370-ANT-1.jpg|border|thumb|[https://www.olimex.com/Products/USB-Modules/MOD-WIFI-R5370-ANT/ MOD-WIFI-R5370-ANT]]]

To use one this wifi dongle (like [https://www.olimex.com/Products/USB-Modules/MOD-WIFI-R5370/ MOD-WIFI-R5370] or [https://www.olimex.com/Products/USB-Modules/MOD-WIFI-R5370-ANT/ MOD-WIFI-R5370-ANT]) additional files are required.

[https://www.olimex.com/Products/USB-Modules/MOD-WIFI-R5370-ANT/ MOD-WIFI-R5370-ANT] has the following features:

* 2.4GHz with 150Mbps PHY data rate
*External antenna for extended range
*USB 2.0 interface
*Security: WEP/TKIP/AES/WPA/WPA2/WAPI
*CMOS single chip with RF, baseband, and MAC integration
*QoS: WMM & WMM-PS support
*Multiple BSSID support
*Maximum likelihood decoding support
*Cisco CCX 5.0 support
*Low-power usage with advanced power management
----

*First a make new directory and navigate to it. This is where the module will search for files.
mkdir -p /etc/Wireless/RT2870STA
cd /etc/Wireless/RT2870STA/

*Download the files from Github
wget https://raw.githubusercontent.com/SelfDestroyer/RK3188-SOM/olimex/stable-3.0/drivers/net/wireless/rtxx7x/RT2870STA.dat
wget https://raw.githubusercontent.com/SelfDestroyer/RK3188-SOM/olimex/stable-3.0/drivers/net/wireless/rtxx7x/RT2870STACard.dat

*Load module
modprobe rt5370sta

*Plug the device and run:
ifconfig -a
*You should see this:
wlan0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

*Configure your new device:
vi /etc/network/interfaces
*Add configuration. Here we will show DHCP configuration.
iface wlan0 inet dhcp
wpa-ssid "'''your ssid'''"
wpa-psk "'''your password'''"

*Save the configuration and up the interface:
ifup wlan0

*If everything is working and this module to be loaded on boot:
echo rt5370sta >> /etc/modules

== Android ==

A20-SOM

2023-04-11T11:49:35Z

LubOlimex: /* Android images */

[[File:A20-SOM-1 jpeg.jpg|675px]]

Features:

*A20 dual core Cortex-A7 processor
*1GB DDR3 memory
*AXP209 PMU IC
*MicroSD card
*UART console
*4GB NAND Flash
*Status LEDs
*RESET, RECOVERY buttons
*6 connectors x 40 pin 0.05" step
 
== Official Images from OLIMEX ==

'''The recommended image for most of Olimex-made Linux boards is Olimage Linux, you can find information about it in the document here:'''

https://github.com/OLIMEX/OLINUXINO/blob/master/DOCUMENTS/OLIMAGE/Olimage-guide.pdf

'''Notice this wiki article refers to outdated images and practices, if using Olimage Linux, use the information only as a reference (do not take it literally)!'''

Note that only the microSD connector is suitable for booting the desired operating system, the SD-MMC connector is not suitable for booting since it is not a part of the boot sequence (refer to A20 datasheet).

=== Old Linux images ===

These Debian images should be downloaded to a microSD card. You need a properly set torrent client to download the official images - they are available only as torrents. You can install the Debian to the NAND or the eMMC of your board (if it comes with one). Information on booting Debian from the NAND or eMMC might be found in these wiki article: [[how to install Debian to NAND]]; [[how to install Debian to eMMC]]. Download locations for the official images might be found below:

'''ALWAYS FIRST TEST WITH LATEST OFFICIAL IMAGE, NEWER HARDWARE REVISIONS OF THE BOARD MIGHT NOT WORK WITH OLDER IMAGES!!!'''

----

'''Latest stable official image - Debian 9 (Jessie)''' '''(recommended for all board revisions)''':'''

FTP download location for the official Debian Jessie release #10 (suitable for boards with NAND): [https://ftp.olimex.com/Allwinner_Images/A20-SOM/Debian/sd/a20-SOM_mainline_uboot_GMAC_master_sunxi_kernel_3.4.103_jessie_NAND_rel_10.img.7z A20-SOM Debian Jessie with kernel 3.4.103+ for boards with NAND flash memory release 10]

FTP download for A20-SOM (suitable for boards with eMMC): [https://ftp.olimex.com/Allwinner_Images/A20-SOM/Debian/sd/a20-SOM_mainline_uboot_GMAC_master_sunxi_kernel_3.4.103_jessie_eMMC_rel_11.zip A20-SOM Debian Jessie with kernel 3.4.103+ for boards with eMMC flash memory release 11]

Image description and typical interfacing: [https://raw.githubusercontent.com/OLIMEX/OLINUXINO/master/SOFTWARE/A20/A20-build-3.4.103-release-7/USAGE-AND-COMMON-PRACTICEs-A20-Olimex_kernel_3.4.103%2B_Jessie_rel_3.txt description and basic usage of different peripherals at at the GitHub page]

Image build instructions and required files for latest Debian Jessie release might be found here: [https://github.com/OLIMEX/OLINUXINO/raw/master/SOFTWARE/A20/A20-build-3.4.103-release-7/BUILD_DESCRIPTION_A20_Olimex_kernel_3.4.103%2B_Jessie_rel_6.txt build instructions and required files at the GitHub page]

You can find some older releases and older build instructions (older image revisions might be used as a reference, for testing purposes, or if you own old hardware revision of the board) at the following article: [[A20-SOM-older-releases|older releases and older build instructions]]

----

Note: in the previous Debian releases the Ethernet was auto-detected and initialized during boot BUT this caused big delays in the start-up of the board if you didn't want to use Ethernet or if there wasn't Ethernet cable connected.

You can enable it by following these two steps:

1. To check under what name the LAN is associated write "ifconfig –a"

2. If, for example, it is under eth0 name, then write: "dhclient eth0"

This should enable the Ethernet and then SSH would also be available.

The Debian Linux file system can be extended to suit a bigger card. If the whole SD card is not used, use the following three commands to execute a script that would use all the free space of your card:

sudo su
resize_sd.sh /dev/mmcblk0 2
reboot

=== Android images ===

Links to official Android releases are below. Please read description of the image carefully.

Direct download of Android 4.2.2 release 1 for NAND memory (with HDMI and 800x480 support): [https://ftp.olimex.com/Allwinner_Images/A20-SOM/Android/nand/A20_SOM_camera_LCD7_HDMI_release1.img A20-SOM Android for NAND with HDMI and 7 inch display support]

Direct download of Android 4.2.2 release 1 for microSD card (with HDMI and 800x480 support):
[https://ftp.olimex.com/Allwinner_Images/A20-SOM/Android/sd/A20_SOM_Android_4.22_SD_card_LCD_800x480_HDMI_release_1.img.7z A20-SOM Android for NAND with HDMI and 7 inch display support]

Build instructions and source files for the official Android images for A20 boards in this repository: https://github.com/hehopmajieh/olinuxino_configs
 

== Documents ==

=== A20 Brief ===

[https://github.com/OLIMEX/OLINUXINO/blob/master/HARDWARE/A20-PDFs/A20%20brief%2020130407.pdf A20-Brief description]

=== A20 Datasheet ===

[https://github.com/OLIMEX/OLINUXINO/blob/master/HARDWARE/A20-PDFs/A20%20Datasheet%20v1.0%2020130227.pdf A20 datasheet]

=== A20 User Manual ===
[https://github.com/OLIMEX/OLINUXINO/blob/master/HARDWARE/A20-PDFs/A20%20User%20Manual%202013-03-22.pdf A20 Users manual]

== Hardware ==
 
===Board Layout===
[[File:A20-SOM-1_top_named.jpg|675px]]

 

===Board dimensions===

[[File:a20-som_dimensions.png|675px]]

A20-SOM and A20-SOM-4GB basic dimensions in mils: [https://www.olimex.com/Products/SOM/A20/A20-SOM/resources/a20-som_dimensions.png click]

A20-SOM-EVB basic dimension in mils: [https://www.olimex.com/Products/SOM/A20/A20-SOM-EVB/resources/a20-som-evb_dimensions.png click]

===Power supply and consumption===

*'''A20-SOM''' 
A20-SOM typically consumes between 0.20A and 0.25A when connected to a 5V
voltage source (provided at pins GND and 5VEXT).

During heavy load of the processor the consumption might raise up to 0.35A
(tested with 'top d0').

The current consumed might have peaks as high as 0.50A @ 5V during start-up when
different modules are initialized.

Make sure your supply is capable of providing at least half an ampere of
current at 5V of voltage.

*'''A20-SOM + A20-SOM-EVB''' 
The consumption of the combination A20-SOM + A20-SOM-EVB is betwen 0.10A and 0.15A when the A20-SOM-EVB is connected to a 12V voltage source (provided at the board's PWR jack).

During heavy load of the processor the consumption might raise up to 0.20A @ 12V
(tested with 'top d0').

The current consumed might have peaks as high as 0.25A @ 12V during start-up when
different modules are initialized.

===CAD files===

A20-SOM is considered commercial, proprietary design. The board file is not available to the customer. A pdf extracted from the original schematic is available at GitHub: [https://github.com/OLIMEX/SOM/tree/master/A20/A20-SOM A20-SOM schematics]

KiCAD files of the connectors of A20-SOM/A20-SOM-EVB that are perfect as a template for own design can be found here: [https://github.com/OLIMEX/SOM/tree/master/A20/A20-SOM/KiCAD%20connector%20library KiCAD templates A20-SOM]

A20-SOM-EVB is considered Open Source Hardware, Eagle CAD files are available here [https://www.olimex.com/Products/SOM/A20/A20-SOM-EVB/resources/A20-SOM-EVB_eagle_sources.zip A20-SOM-EVB sources]

The CAD product used to design OLinuXino is Eagle and you can download evaluation free version from their [http://www.cadsoftusa.com/ web site]. The evaluation version allows you to inspect the schematic and the board file sources.

== How To? ==
 

=== Is it possible to boot Debian from NAND? Do you provide such image?===
Yes, it is possible. Use the latest Debian Jessie image and write "nandinstall". More information can be found in this wiki article: [[How_to_install_Debian_to_NAND| installing Debian Jessie to the 4GB NAND memory]]

There are other people who are also successful in booting Debian from the NAND. Make sure to check on the forum. Make sure to check the number of very good and optimized A20-OLinuXino Debian images by Igor Pečovnik. There are also his instructions for NAND installation of Debian: [http://www.armbian.com/download/ link to his web-site]

===How to correctly power off OLinuXino running from NAND Flash===
[http://olimex.wordpress.com/2014/01/24/how-to-correctly-power-off-olinuxino-running-android/ In this Blog post] we explain what are the problems. This is common problem for all computers running OS. [http://www.linux-mtd.infradead.org/doc/ubifs.html#L_ubifs_mlc Here] you can read more about MLC NAND Flash and Linux file system.

===How to build the official Debian Linux image for A20-SOM? ===

Build instructions and required files for the latest Debian Jessie images: [https://github.com/OLIMEX/OLINUXINO/tree/master/SOFTWARE/A20/A20-build-3.4.103-release-2 build instructions and required files at the GitHub page]

Build instructions and required files for the latest Debian Wheezy images: [https://github.com/OLIMEX/OLINUXINO/tree/master/SOFTWARE/A20/A20-build-3.4.90 instructions and files at the GitHub page]

===How to download new Android image to the NAND memory of my A20-SOM-4GB board?===

In order to download the Android image to the NAND memory of the board follow these steps:

1. Install and run PhoenixSuit (can be found here: [https://drive.google.com/file/d/0BwplT87k9SCgaTFTZnVST05ONzA/view?usp=sharing google drive location]).

2. Download and extract the latest official image - can be found above in the Android section of this article. Make sure that the download link you visit clearly indicates that the image is suitable for the NAND memory since there are images suitable for microSD card also. The images suitable for the microSD memory and those suitable for microSD card are different. However, the upload method is almost identical – using PhoenixSuit.

3. Go to firmware tab of the program and point to the already downloaded and extracted Android image.

4. Disconnect the power supply and USB cable from the A20 board.

5. Press and hold RECOVERY button, apply power supply (the requirement various depending on whether you use the board stand-alone or on top of A20-SOM-EVB), release RECOVERY button.

6. Connect USB cable to the mini USB connector.

7. You will be asked for drivers for the bootloader. Navigate to the folder where you extracted the PhoenixSuit and install the drivers from the respective executable (or manually point the installer to the drivers folder in the PhoenixSuit installation path).

8. PhoenixSuit will detect the board and would ask whether you wish to also of writing the image. Choose method of writing the image and confirm your wish to write the image.

9. Wait till upgrade succeeds

Note that it is not recommended to have your mini USB connected to an external USB hub. This might cause delays and might distort the signal levels. Always test with the USB connected straight to the USB ports of your computer.

===How do I write the official Android image to a micro SD card for my A20 board?===
A: First download one of the official Android images, which might be found in the Android section above.

Make sure that the download link you visit clearly indicates that the image is suitable for the microSD card since there are images suitable for NAND memory also. The images suitable for the microSD memory and those suitable for NAND card are different. However, the upload method is almost identical – using PhoenixSuit.

There are two types of Android images for microSD card that we usually provide and each of them has to be downloaded to a microSD card using a different method. The image provided for microSD card is either the native Android image that can be downloaded to the card via a software tool like PhoenixSuit (through the board) or an image taken from an already prepared microSD card that requires to simply write the image (through a microSD card reader).

'''It is more likely that you have an Android image that requires a simple copy to a card. If that is the case you can follow the exact steps as for Linux (e.g. using "Win32 Disk Imager" or "dd" command).'''

In order to prepare a microSD card with a native Android you will need a software tool called PhoenixSuit and then:

1. Install and run PhoenixSuit (can be found here: [https://drive.google.com/file/d/0BwplT87k9SCgaTFTZnVST05ONzA/view?usp=sharing download from google drive])

2. Go to the firmware tab of the program and point to a valid Android image (note that the images on Google drive are compressed and you have to extract the archives to .img files to be able write them with PhoenixSuit)

3. Disconnect the power supply and USB cable from the A20 board. Put an SD card in micro SD holder. We recommend 4GB class 10 card.

4. Press and hold RECOVERY button, apply power supply (the requirement various depending on whether you use the board stand-alone or on top of A20-SOM-EVB), release RECOVERY button.

5. Connect USB cable to the mini USB connector.

6. You will be asked for drivers for the boot-loader. Navigate to the folder where you extracted the PhoenixSuit and install the drivers from the respective executables (or manually point the installer to the drivers folder in the PhoenixSuit installation path).

7. PhoenixSuit will detect the board and would ask for the method of writing the image. Choose method of writing the image and confirm your wish to write the image.

8. Wait till upgrade succeeds

Note that it is not recommended to have your mini USB connected to an external USB hub. This
might cause delays and might distort the signal levels. Always test with the USB connected straight to the USB ports of your computer.

Important: When Android runs for very first time it takes several minutes to initialize all files and buffers please do not cut the power supply during this process! Also when fresh image is installed fast boot may be disabled, which means that when you apply power supply after few seconds Android will go in sleep mode and you have to press POWER button to start it, you can change to fast boot when you power off there is dialog box asking you if you want next boot to be fast boot, you have to check this box before you power off. Also note that you must do touch screen calibration when you run Android for very first time which might require a mouse.

===How do I write the Linux image to a micro SD card to use with my A20 board?===

To write a Linux image to an SD card under Windows we use Win32 Disk Imager):

*Download Win32 Disk Imager [http://sourceforge.net/projects/win32diskimager/ Win32 Disk Imager]
*Insert card
*Start program
*Select file
*Click "write"

To write a Linux image to an SD card under Linux:

For instance you have an image with the file name of "debian_2g.img". It would be downloaded to the SD card connected to a Linux machine using one of the following commands:

* # dd bs=4M oflag=sync if=debian_2g.img of=/dev/sdX
or
* # cp debian_2g.img /dev/sdX

where X is the uSD card.

===I don't have neither serial cable, nor HDMI monitor. I also can't access the local Ethernet network. Can I somehow access the board anyway?===

The latest official Debian Linux image allows the use the USB_OTG connector for SSH connection without the need of a LAN cable or a serial cable. You can use a mini USB cable connected between your host PC and the on-board mini USB connector. For connection convenience there is a DHCP server running specifically for USB0 interface. The DHCP server should give IP address to the new USB0 interface of your host PC so you can make SSH connection from your PC to the default board IP address of the USB0 interface – 192.168.2.1.

You can connect to the board using a mini USB cable and an SSH client (if you use Windows you might use "puTTY", for example) at address 192.168.2.1.

For Windows operating system - upon connection, the board should show up in "Windows Device Manager" as "RNDIS Ethernet Gadget". You might be asked to install a driver. The drivers can be found online as "RNDIS driver" (Remote Network Driver Interface Specification). The drivers are provided by Microsoft and they should be available for every Windows distribution - refer to the respective files and articles provided by Microsoft on how to install the required drivers.

===How to change HDMI, VGA and LCD resolutions in the official Debian image?===

The default SD card setup is made with settings for HDMI 720p/60Hz. If you want to change to some other LCD, VGA or HDMI resolution then you have to start change_display.sh script file in /root directory. When you are logged as super user in the board type:

For Debian Wheezy releases: ./change_display* (* = press 'tab' to auto-complete)
For Debian Jessie releases: change_display* (* = press 'tab' to auto-complete)

and press "Enter".

'''Note that the script should be executed as super user. Under the command line interface you are automatically logged as super user (user "root", password "olimex"). However, under the graphical environment you are not auto-logged as super user and you must type "sudo" before the command (in the GUI the super-user is "olimex" and the password is "olimex")'''

Then choose the resolution and the interface(LCD, HDMI or VGA). Note that the selection of a specific resolution is done by navigating with the arrow keys and pressing "space" button. Make sure the asterisk marks your selection properly.

The supported resolutions are:

'''For LCD:'''

*1. 4.3" (480x272)
*2. 7" (800x480)
*3. 10" (1024x600)
*4. 15.6" (1366x768)

Important: initially the boards are calibrated for a specific display. If you re-write the image (no matter whether the SD card or the NAND memory) you would need to use a mouse to calibrate the display initially. It might be impossible to calibrate it via touching the display.

'''For HDMI:'''

*0. 480i
*1. 576i
*2. 480p
*3. 576p
*4. 720p50
*5. 720p60
*6. 1080i50
*7. 1080i60
*8. 1080p24
*9. 1080p50
*10. 1080p60
*11. pal
*14. ntsc

'''For VGA:'''

*0. 1680x1050
*1. 1440x900
*2. 1360x768
*3. 1280x1024
*4. 1024x768
*5. 800x600
*6. 640x480
*7. 1920x1080
*8. 1280x720
 

===How to edit board configurations and definitions in the official Debian Linux? ===

Do you want a custom video resolution output? Do you need a different port definition? Do you need to change the hardware defitions of the board?

You would need to edit the board's script.bin/script.fex file. How to do it is described in a separate article: [[How_to_edit_board_configurations_and_definitions_in_the_official_Debian_Linux]].

===How to generate Arch Linux image?===

Recent forum post by user progmetalbg here: [https://www.olimex.com/forum/index.php?topic=4261.0| at Olimex forums]

[http://alarma20.wordpress.com/2013/09/13/howto-build-arch-linux-arm-for-a20-olinuxino-micro/ Older step by step instructions on how to build Arch Linux image for another A20 board]

===How to detect and enable the Ethernet controller (if it is disabled by default)? ===

Note: in the previous Debian releases the Ethernet was auto-detected and initialized during boot BUT this was causing big delays in the start-up of the board if you didn't want to use Ethernet or if there wasn't Ethernet cable connected.

You can enable it by following these two steps:

1. To check under what name the LAN is associated write "ifconfig –a"

2. If, for example, it is under eth0 name, then write: "dhclient eth0"

This should enable the Ethernet and then SSH would also be available.

===How to install Android on SD-card? ===

[http://olimex.wordpress.com/2013/10/02/android-4-2-2-images-for-a20-olinuxino-running-from-sd-card-is-updated-on-wiki/ Blog post about it]

===How to access UART, I2C, GPIOs under Android? ===

[http://olimex.wordpress.com/2013/10/02/a20-olinuxino-tools-for-android-released/ Use our Open Source OLinuXino A20-TOOLS]

===How to control PWM under Linux? ===

There is an article here: [[how to add pwm]]

===How to build the Android 4.2.2 image for A20-OLinuXino-MICRO? ===

First you need to Download the [http://dl.linux-sunxi.org/users/tsvetan/ANDROID-4.2.2-SDK2.0-KERNEL-3.4/ A20 SDK2.0 Linux Kernel 3.4]

Second you need to configure your environment read the instructions [http://source.android.com/source/initializing.html here]

Then Build the kernel, kernel modules and u-boot

cd lichee
./build.sh -psun7i_android

When done, continue with Bulding the android image:

cd ../android4.2
cd device/softwinner/
tar zxfv olinuxino-a20.tgz
cd ../../
source build/envsetup.sh
lunch #select olinuxino-a20_eng
extract-bsp
make -j4

Dave from Axon instruments wrote more detailed [http://axonjakarta.wordpress.com/2014/02/14/olimex-a20-android-building-4/ blog post] about how he generates the Android image]

A20-SOM

2023-04-11T06:12:12Z

LubOlimex: /* Android images */

[[File:A20-SOM-1 jpeg.jpg|675px]]

Features:

*A20 dual core Cortex-A7 processor
*1GB DDR3 memory
*AXP209 PMU IC
*MicroSD card
*UART console
*4GB NAND Flash
*Status LEDs
*RESET, RECOVERY buttons
*6 connectors x 40 pin 0.05" step
 
== Official Images from OLIMEX ==

'''The recommended image for most of Olimex-made Linux boards is Olimage Linux, you can find information about it in the document here:'''

https://github.com/OLIMEX/OLINUXINO/blob/master/DOCUMENTS/OLIMAGE/Olimage-guide.pdf

'''Notice this wiki article refers to outdated images and practices, if using Olimage Linux, use the information only as a reference (do not take it literally)!'''

Note that only the microSD connector is suitable for booting the desired operating system, the SD-MMC connector is not suitable for booting since it is not a part of the boot sequence (refer to A20 datasheet).

=== Old Linux images ===

These Debian images should be downloaded to a microSD card. You need a properly set torrent client to download the official images - they are available only as torrents. You can install the Debian to the NAND or the eMMC of your board (if it comes with one). Information on booting Debian from the NAND or eMMC might be found in these wiki article: [[how to install Debian to NAND]]; [[how to install Debian to eMMC]]. Download locations for the official images might be found below:

'''ALWAYS FIRST TEST WITH LATEST OFFICIAL IMAGE, NEWER HARDWARE REVISIONS OF THE BOARD MIGHT NOT WORK WITH OLDER IMAGES!!!'''

----

'''Latest stable official image - Debian 9 (Jessie)''' '''(recommended for all board revisions)''':'''

FTP download location for the official Debian Jessie release #10 (suitable for boards with NAND): [https://ftp.olimex.com/Allwinner_Images/A20-SOM/Debian/sd/a20-SOM_mainline_uboot_GMAC_master_sunxi_kernel_3.4.103_jessie_NAND_rel_10.img.7z A20-SOM Debian Jessie with kernel 3.4.103+ for boards with NAND flash memory release 10]

FTP download for A20-SOM (suitable for boards with eMMC): [https://ftp.olimex.com/Allwinner_Images/A20-SOM/Debian/sd/a20-SOM_mainline_uboot_GMAC_master_sunxi_kernel_3.4.103_jessie_eMMC_rel_11.zip A20-SOM Debian Jessie with kernel 3.4.103+ for boards with eMMC flash memory release 11]

Image description and typical interfacing: [https://raw.githubusercontent.com/OLIMEX/OLINUXINO/master/SOFTWARE/A20/A20-build-3.4.103-release-7/USAGE-AND-COMMON-PRACTICEs-A20-Olimex_kernel_3.4.103%2B_Jessie_rel_3.txt description and basic usage of different peripherals at at the GitHub page]

Image build instructions and required files for latest Debian Jessie release might be found here: [https://github.com/OLIMEX/OLINUXINO/raw/master/SOFTWARE/A20/A20-build-3.4.103-release-7/BUILD_DESCRIPTION_A20_Olimex_kernel_3.4.103%2B_Jessie_rel_6.txt build instructions and required files at the GitHub page]

You can find some older releases and older build instructions (older image revisions might be used as a reference, for testing purposes, or if you own old hardware revision of the board) at the following article: [[A20-SOM-older-releases|older releases and older build instructions]]

----

Note: in the previous Debian releases the Ethernet was auto-detected and initialized during boot BUT this caused big delays in the start-up of the board if you didn't want to use Ethernet or if there wasn't Ethernet cable connected.

You can enable it by following these two steps:

1. To check under what name the LAN is associated write "ifconfig –a"

2. If, for example, it is under eth0 name, then write: "dhclient eth0"

This should enable the Ethernet and then SSH would also be available.

The Debian Linux file system can be extended to suit a bigger card. If the whole SD card is not used, use the following three commands to execute a script that would use all the free space of your card:

sudo su
resize_sd.sh /dev/mmcblk0 2
reboot

=== Android images ===

Links to official Android releases are below. Please read description of the image carefully.

Direct download of Android 4.2.2 release 1 for NAND memory (with HDMI and 800x480 support): [https://ftp.olimex.com/Allwinner_Images/A20-SOM/Android/nand/A20_SOM_camera_LCD7_HDMI_release1.img‎ A20-SOM Android for NAND with HDMI and 7 inch display support]

Direct download of Android 4.2.2 release 1 for microSD card (with HDMI and 800x480 support):
[https://ftp.olimex.com/Allwinner_Images/A20-SOM/Android/sd/A20_SOM_Android_4.22_SD_card_LCD_800x480_HDMI_release_1.img.7z‎ A20-SOM Android for NAND with HDMI and 7 inch display support]

Build instructions and source files for the official Android images for A20 boards in this repository: https://github.com/hehopmajieh/olinuxino_configs
 

== Documents ==

=== A20 Brief ===

[https://github.com/OLIMEX/OLINUXINO/blob/master/HARDWARE/A20-PDFs/A20%20brief%2020130407.pdf A20-Brief description]

=== A20 Datasheet ===

[https://github.com/OLIMEX/OLINUXINO/blob/master/HARDWARE/A20-PDFs/A20%20Datasheet%20v1.0%2020130227.pdf A20 datasheet]

=== A20 User Manual ===
[https://github.com/OLIMEX/OLINUXINO/blob/master/HARDWARE/A20-PDFs/A20%20User%20Manual%202013-03-22.pdf A20 Users manual]

== Hardware ==
 
===Board Layout===
[[File:A20-SOM-1_top_named.jpg|675px]]

 

===Board dimensions===

[[File:a20-som_dimensions.png|675px]]

A20-SOM and A20-SOM-4GB basic dimensions in mils: [https://www.olimex.com/Products/SOM/A20/A20-SOM/resources/a20-som_dimensions.png click]

A20-SOM-EVB basic dimension in mils: [https://www.olimex.com/Products/SOM/A20/A20-SOM-EVB/resources/a20-som-evb_dimensions.png click]

===Power supply and consumption===

*'''A20-SOM''' 
A20-SOM typically consumes between 0.20A and 0.25A when connected to a 5V
voltage source (provided at pins GND and 5VEXT).

During heavy load of the processor the consumption might raise up to 0.35A
(tested with 'top d0').

The current consumed might have peaks as high as 0.50A @ 5V during start-up when
different modules are initialized.

Make sure your supply is capable of providing at least half an ampere of
current at 5V of voltage.

*'''A20-SOM + A20-SOM-EVB''' 
The consumption of the combination A20-SOM + A20-SOM-EVB is betwen 0.10A and 0.15A when the A20-SOM-EVB is connected to a 12V voltage source (provided at the board's PWR jack).

During heavy load of the processor the consumption might raise up to 0.20A @ 12V
(tested with 'top d0').

The current consumed might have peaks as high as 0.25A @ 12V during start-up when
different modules are initialized.

===CAD files===

A20-SOM is considered commercial, proprietary design. The board file is not available to the customer. A pdf extracted from the original schematic is available at GitHub: [https://github.com/OLIMEX/SOM/tree/master/A20/A20-SOM A20-SOM schematics]

KiCAD files of the connectors of A20-SOM/A20-SOM-EVB that are perfect as a template for own design can be found here: [https://github.com/OLIMEX/SOM/tree/master/A20/A20-SOM/KiCAD%20connector%20library KiCAD templates A20-SOM]

A20-SOM-EVB is considered Open Source Hardware, Eagle CAD files are available here [https://www.olimex.com/Products/SOM/A20/A20-SOM-EVB/resources/A20-SOM-EVB_eagle_sources.zip A20-SOM-EVB sources]

The CAD product used to design OLinuXino is Eagle and you can download evaluation free version from their [http://www.cadsoftusa.com/ web site]. The evaluation version allows you to inspect the schematic and the board file sources.

== How To? ==
 

=== Is it possible to boot Debian from NAND? Do you provide such image?===
Yes, it is possible. Use the latest Debian Jessie image and write "nandinstall". More information can be found in this wiki article: [[How_to_install_Debian_to_NAND| installing Debian Jessie to the 4GB NAND memory]]

There are other people who are also successful in booting Debian from the NAND. Make sure to check on the forum. Make sure to check the number of very good and optimized A20-OLinuXino Debian images by Igor Pečovnik. There are also his instructions for NAND installation of Debian: [http://www.armbian.com/download/ link to his web-site]

===How to correctly power off OLinuXino running from NAND Flash===
[http://olimex.wordpress.com/2014/01/24/how-to-correctly-power-off-olinuxino-running-android/ In this Blog post] we explain what are the problems. This is common problem for all computers running OS. [http://www.linux-mtd.infradead.org/doc/ubifs.html#L_ubifs_mlc Here] you can read more about MLC NAND Flash and Linux file system.

===How to build the official Debian Linux image for A20-SOM? ===

Build instructions and required files for the latest Debian Jessie images: [https://github.com/OLIMEX/OLINUXINO/tree/master/SOFTWARE/A20/A20-build-3.4.103-release-2 build instructions and required files at the GitHub page]

Build instructions and required files for the latest Debian Wheezy images: [https://github.com/OLIMEX/OLINUXINO/tree/master/SOFTWARE/A20/A20-build-3.4.90 instructions and files at the GitHub page]

===How to download new Android image to the NAND memory of my A20-SOM-4GB board?===

In order to download the Android image to the NAND memory of the board follow these steps:

1. Install and run PhoenixSuit (can be found here: [https://drive.google.com/file/d/0BwplT87k9SCgaTFTZnVST05ONzA/view?usp=sharing google drive location]).

2. Download and extract the latest official image - can be found above in the Android section of this article. Make sure that the download link you visit clearly indicates that the image is suitable for the NAND memory since there are images suitable for microSD card also. The images suitable for the microSD memory and those suitable for microSD card are different. However, the upload method is almost identical – using PhoenixSuit.

3. Go to firmware tab of the program and point to the already downloaded and extracted Android image.

4. Disconnect the power supply and USB cable from the A20 board.

5. Press and hold RECOVERY button, apply power supply (the requirement various depending on whether you use the board stand-alone or on top of A20-SOM-EVB), release RECOVERY button.

6. Connect USB cable to the mini USB connector.

7. You will be asked for drivers for the bootloader. Navigate to the folder where you extracted the PhoenixSuit and install the drivers from the respective executable (or manually point the installer to the drivers folder in the PhoenixSuit installation path).

8. PhoenixSuit will detect the board and would ask whether you wish to also of writing the image. Choose method of writing the image and confirm your wish to write the image.

9. Wait till upgrade succeeds

Note that it is not recommended to have your mini USB connected to an external USB hub. This might cause delays and might distort the signal levels. Always test with the USB connected straight to the USB ports of your computer.

===How do I write the official Android image to a micro SD card for my A20 board?===
A: First download one of the official Android images, which might be found in the Android section above.

Make sure that the download link you visit clearly indicates that the image is suitable for the microSD card since there are images suitable for NAND memory also. The images suitable for the microSD memory and those suitable for NAND card are different. However, the upload method is almost identical – using PhoenixSuit.

There are two types of Android images for microSD card that we usually provide and each of them has to be downloaded to a microSD card using a different method. The image provided for microSD card is either the native Android image that can be downloaded to the card via a software tool like PhoenixSuit (through the board) or an image taken from an already prepared microSD card that requires to simply write the image (through a microSD card reader).

'''It is more likely that you have an Android image that requires a simple copy to a card. If that is the case you can follow the exact steps as for Linux (e.g. using "Win32 Disk Imager" or "dd" command).'''

In order to prepare a microSD card with a native Android you will need a software tool called PhoenixSuit and then:

1. Install and run PhoenixSuit (can be found here: [https://drive.google.com/file/d/0BwplT87k9SCgaTFTZnVST05ONzA/view?usp=sharing download from google drive])

2. Go to the firmware tab of the program and point to a valid Android image (note that the images on Google drive are compressed and you have to extract the archives to .img files to be able write them with PhoenixSuit)

3. Disconnect the power supply and USB cable from the A20 board. Put an SD card in micro SD holder. We recommend 4GB class 10 card.

4. Press and hold RECOVERY button, apply power supply (the requirement various depending on whether you use the board stand-alone or on top of A20-SOM-EVB), release RECOVERY button.

5. Connect USB cable to the mini USB connector.

6. You will be asked for drivers for the boot-loader. Navigate to the folder where you extracted the PhoenixSuit and install the drivers from the respective executables (or manually point the installer to the drivers folder in the PhoenixSuit installation path).

7. PhoenixSuit will detect the board and would ask for the method of writing the image. Choose method of writing the image and confirm your wish to write the image.

8. Wait till upgrade succeeds

Note that it is not recommended to have your mini USB connected to an external USB hub. This
might cause delays and might distort the signal levels. Always test with the USB connected straight to the USB ports of your computer.

Important: When Android runs for very first time it takes several minutes to initialize all files and buffers please do not cut the power supply during this process! Also when fresh image is installed fast boot may be disabled, which means that when you apply power supply after few seconds Android will go in sleep mode and you have to press POWER button to start it, you can change to fast boot when you power off there is dialog box asking you if you want next boot to be fast boot, you have to check this box before you power off. Also note that you must do touch screen calibration when you run Android for very first time which might require a mouse.

===How do I write the Linux image to a micro SD card to use with my A20 board?===

To write a Linux image to an SD card under Windows we use Win32 Disk Imager):

*Download Win32 Disk Imager [http://sourceforge.net/projects/win32diskimager/ Win32 Disk Imager]
*Insert card
*Start program
*Select file
*Click "write"

To write a Linux image to an SD card under Linux:

For instance you have an image with the file name of "debian_2g.img". It would be downloaded to the SD card connected to a Linux machine using one of the following commands:

* # dd bs=4M oflag=sync if=debian_2g.img of=/dev/sdX
or
* # cp debian_2g.img /dev/sdX

where X is the uSD card.

===I don't have neither serial cable, nor HDMI monitor. I also can't access the local Ethernet network. Can I somehow access the board anyway?===

The latest official Debian Linux image allows the use the USB_OTG connector for SSH connection without the need of a LAN cable or a serial cable. You can use a mini USB cable connected between your host PC and the on-board mini USB connector. For connection convenience there is a DHCP server running specifically for USB0 interface. The DHCP server should give IP address to the new USB0 interface of your host PC so you can make SSH connection from your PC to the default board IP address of the USB0 interface – 192.168.2.1.

You can connect to the board using a mini USB cable and an SSH client (if you use Windows you might use "puTTY", for example) at address 192.168.2.1.

For Windows operating system - upon connection, the board should show up in "Windows Device Manager" as "RNDIS Ethernet Gadget". You might be asked to install a driver. The drivers can be found online as "RNDIS driver" (Remote Network Driver Interface Specification). The drivers are provided by Microsoft and they should be available for every Windows distribution - refer to the respective files and articles provided by Microsoft on how to install the required drivers.

===How to change HDMI, VGA and LCD resolutions in the official Debian image?===

The default SD card setup is made with settings for HDMI 720p/60Hz. If you want to change to some other LCD, VGA or HDMI resolution then you have to start change_display.sh script file in /root directory. When you are logged as super user in the board type:

For Debian Wheezy releases: ./change_display* (* = press 'tab' to auto-complete)
For Debian Jessie releases: change_display* (* = press 'tab' to auto-complete)

and press "Enter".

'''Note that the script should be executed as super user. Under the command line interface you are automatically logged as super user (user "root", password "olimex"). However, under the graphical environment you are not auto-logged as super user and you must type "sudo" before the command (in the GUI the super-user is "olimex" and the password is "olimex")'''

Then choose the resolution and the interface(LCD, HDMI or VGA). Note that the selection of a specific resolution is done by navigating with the arrow keys and pressing "space" button. Make sure the asterisk marks your selection properly.

The supported resolutions are:

'''For LCD:'''

*1. 4.3" (480x272)
*2. 7" (800x480)
*3. 10" (1024x600)
*4. 15.6" (1366x768)

Important: initially the boards are calibrated for a specific display. If you re-write the image (no matter whether the SD card or the NAND memory) you would need to use a mouse to calibrate the display initially. It might be impossible to calibrate it via touching the display.

'''For HDMI:'''

*0. 480i
*1. 576i
*2. 480p
*3. 576p
*4. 720p50
*5. 720p60
*6. 1080i50
*7. 1080i60
*8. 1080p24
*9. 1080p50
*10. 1080p60
*11. pal
*14. ntsc

'''For VGA:'''

*0. 1680x1050
*1. 1440x900
*2. 1360x768
*3. 1280x1024
*4. 1024x768
*5. 800x600
*6. 640x480
*7. 1920x1080
*8. 1280x720
 

===How to edit board configurations and definitions in the official Debian Linux? ===

Do you want a custom video resolution output? Do you need a different port definition? Do you need to change the hardware defitions of the board?

You would need to edit the board's script.bin/script.fex file. How to do it is described in a separate article: [[How_to_edit_board_configurations_and_definitions_in_the_official_Debian_Linux]].

===How to generate Arch Linux image?===

Recent forum post by user progmetalbg here: [https://www.olimex.com/forum/index.php?topic=4261.0| at Olimex forums]

[http://alarma20.wordpress.com/2013/09/13/howto-build-arch-linux-arm-for-a20-olinuxino-micro/ Older step by step instructions on how to build Arch Linux image for another A20 board]

===How to detect and enable the Ethernet controller (if it is disabled by default)? ===

Note: in the previous Debian releases the Ethernet was auto-detected and initialized during boot BUT this was causing big delays in the start-up of the board if you didn't want to use Ethernet or if there wasn't Ethernet cable connected.

You can enable it by following these two steps:

1. To check under what name the LAN is associated write "ifconfig –a"

2. If, for example, it is under eth0 name, then write: "dhclient eth0"

This should enable the Ethernet and then SSH would also be available.

===How to install Android on SD-card? ===

[http://olimex.wordpress.com/2013/10/02/android-4-2-2-images-for-a20-olinuxino-running-from-sd-card-is-updated-on-wiki/ Blog post about it]

===How to access UART, I2C, GPIOs under Android? ===

[http://olimex.wordpress.com/2013/10/02/a20-olinuxino-tools-for-android-released/ Use our Open Source OLinuXino A20-TOOLS]

===How to control PWM under Linux? ===

There is an article here: [[how to add pwm]]

===How to build the Android 4.2.2 image for A20-OLinuXino-MICRO? ===

First you need to Download the [http://dl.linux-sunxi.org/users/tsvetan/ANDROID-4.2.2-SDK2.0-KERNEL-3.4/ A20 SDK2.0 Linux Kernel 3.4]

Second you need to configure your environment read the instructions [http://source.android.com/source/initializing.html here]

Then Build the kernel, kernel modules and u-boot

cd lichee
./build.sh -psun7i_android

When done, continue with Bulding the android image:

cd ../android4.2
cd device/softwinner/
tar zxfv olinuxino-a20.tgz
cd ../../
source build/envsetup.sh
lunch #select olinuxino-a20_eng
extract-bsp
make -j4

Dave from Axon instruments wrote more detailed [http://axonjakarta.wordpress.com/2014/02/14/olimex-a20-android-building-4/ blog post] about how he generates the Android image]

A20-SOM

2023-04-10T13:55:44Z

LubOlimex: /* Android images */

[[File:A20-SOM-1 jpeg.jpg|675px]]

Features:

*A20 dual core Cortex-A7 processor
*1GB DDR3 memory
*AXP209 PMU IC
*MicroSD card
*UART console
*4GB NAND Flash
*Status LEDs
*RESET, RECOVERY buttons
*6 connectors x 40 pin 0.05" step
 
== Official Images from OLIMEX ==

'''The recommended image for most of Olimex-made Linux boards is Olimage Linux, you can find information about it in the document here:'''

https://github.com/OLIMEX/OLINUXINO/blob/master/DOCUMENTS/OLIMAGE/Olimage-guide.pdf

'''Notice this wiki article refers to outdated images and practices, if using Olimage Linux, use the information only as a reference (do not take it literally)!'''

Note that only the microSD connector is suitable for booting the desired operating system, the SD-MMC connector is not suitable for booting since it is not a part of the boot sequence (refer to A20 datasheet).

=== Old Linux images ===

These Debian images should be downloaded to a microSD card. You need a properly set torrent client to download the official images - they are available only as torrents. You can install the Debian to the NAND or the eMMC of your board (if it comes with one). Information on booting Debian from the NAND or eMMC might be found in these wiki article: [[how to install Debian to NAND]]; [[how to install Debian to eMMC]]. Download locations for the official images might be found below:

'''ALWAYS FIRST TEST WITH LATEST OFFICIAL IMAGE, NEWER HARDWARE REVISIONS OF THE BOARD MIGHT NOT WORK WITH OLDER IMAGES!!!'''

----

'''Latest stable official image - Debian 9 (Jessie)''' '''(recommended for all board revisions)''':'''

FTP download location for the official Debian Jessie release #10 (suitable for boards with NAND): [https://ftp.olimex.com/Allwinner_Images/A20-SOM/Debian/sd/a20-SOM_mainline_uboot_GMAC_master_sunxi_kernel_3.4.103_jessie_NAND_rel_10.img.7z A20-SOM Debian Jessie with kernel 3.4.103+ for boards with NAND flash memory release 10]

FTP download for A20-SOM (suitable for boards with eMMC): [https://ftp.olimex.com/Allwinner_Images/A20-SOM/Debian/sd/a20-SOM_mainline_uboot_GMAC_master_sunxi_kernel_3.4.103_jessie_eMMC_rel_11.zip A20-SOM Debian Jessie with kernel 3.4.103+ for boards with eMMC flash memory release 11]

Image description and typical interfacing: [https://raw.githubusercontent.com/OLIMEX/OLINUXINO/master/SOFTWARE/A20/A20-build-3.4.103-release-7/USAGE-AND-COMMON-PRACTICEs-A20-Olimex_kernel_3.4.103%2B_Jessie_rel_3.txt description and basic usage of different peripherals at at the GitHub page]

Image build instructions and required files for latest Debian Jessie release might be found here: [https://github.com/OLIMEX/OLINUXINO/raw/master/SOFTWARE/A20/A20-build-3.4.103-release-7/BUILD_DESCRIPTION_A20_Olimex_kernel_3.4.103%2B_Jessie_rel_6.txt build instructions and required files at the GitHub page]

You can find some older releases and older build instructions (older image revisions might be used as a reference, for testing purposes, or if you own old hardware revision of the board) at the following article: [[A20-SOM-older-releases|older releases and older build instructions]]

----

Note: in the previous Debian releases the Ethernet was auto-detected and initialized during boot BUT this caused big delays in the start-up of the board if you didn't want to use Ethernet or if there wasn't Ethernet cable connected.

You can enable it by following these two steps:

1. To check under what name the LAN is associated write "ifconfig –a"

2. If, for example, it is under eth0 name, then write: "dhclient eth0"

This should enable the Ethernet and then SSH would also be available.

The Debian Linux file system can be extended to suit a bigger card. If the whole SD card is not used, use the following three commands to execute a script that would use all the free space of your card:

sudo su
resize_sd.sh /dev/mmcblk0 2
reboot

=== Android images ===

Torrents of official Android releases are below. Please read description of the image carefully.

Direct download of Android 4.2.2 release 1 for NAND memory (with HDMI and 800x480 support): [https://ftp.olimex.com/Allwinner_Images/A20-SOM/Android/sd/A20_SOM_Android_4.22_SD_card_LCD_800x480_HDMI_release_1.img.7z‎ A20-SOM Android for NAND with HDMI and 7 inch display support]

Torrent of Android 4.2.2 release 1 for microSD card (with HDMI and 800x480 support): [[Media:A20_SOM_Android_4.22_SD_card_LCD_800x480_HDMI_release_1.torrent‎|A20-SOM Android for microSD card with HDMI and 7 inch display support]]

Direct download locations of official Android releases are below. In case the daily limit of the download locations had been reached, please use the torrents above. Please read description of the image carefully.

Direct download of Android release 1 for microSD card [https://drive.google.com/file/d/0BwplT87k9SCgZW5RUF9JUjZDMk0/view?usp=sharing microSD card image for Android 4.2.2 with 7″ LCD 800×480 pixels]

Build instructions and source files for the official Android images for A20 boards in this repository: https://github.com/hehopmajieh/olinuxino_configs
 

== Documents ==

=== A20 Brief ===

[https://github.com/OLIMEX/OLINUXINO/blob/master/HARDWARE/A20-PDFs/A20%20brief%2020130407.pdf A20-Brief description]

=== A20 Datasheet ===

[https://github.com/OLIMEX/OLINUXINO/blob/master/HARDWARE/A20-PDFs/A20%20Datasheet%20v1.0%2020130227.pdf A20 datasheet]

=== A20 User Manual ===
[https://github.com/OLIMEX/OLINUXINO/blob/master/HARDWARE/A20-PDFs/A20%20User%20Manual%202013-03-22.pdf A20 Users manual]

== Hardware ==
 
===Board Layout===
[[File:A20-SOM-1_top_named.jpg|675px]]

 

===Board dimensions===

[[File:a20-som_dimensions.png|675px]]

A20-SOM and A20-SOM-4GB basic dimensions in mils: [https://www.olimex.com/Products/SOM/A20/A20-SOM/resources/a20-som_dimensions.png click]

A20-SOM-EVB basic dimension in mils: [https://www.olimex.com/Products/SOM/A20/A20-SOM-EVB/resources/a20-som-evb_dimensions.png click]

===Power supply and consumption===

*'''A20-SOM''' 
A20-SOM typically consumes between 0.20A and 0.25A when connected to a 5V
voltage source (provided at pins GND and 5VEXT).

During heavy load of the processor the consumption might raise up to 0.35A
(tested with 'top d0').

The current consumed might have peaks as high as 0.50A @ 5V during start-up when
different modules are initialized.

Make sure your supply is capable of providing at least half an ampere of
current at 5V of voltage.

*'''A20-SOM + A20-SOM-EVB''' 
The consumption of the combination A20-SOM + A20-SOM-EVB is betwen 0.10A and 0.15A when the A20-SOM-EVB is connected to a 12V voltage source (provided at the board's PWR jack).

During heavy load of the processor the consumption might raise up to 0.20A @ 12V
(tested with 'top d0').

The current consumed might have peaks as high as 0.25A @ 12V during start-up when
different modules are initialized.

===CAD files===

A20-SOM is considered commercial, proprietary design. The board file is not available to the customer. A pdf extracted from the original schematic is available at GitHub: [https://github.com/OLIMEX/SOM/tree/master/A20/A20-SOM A20-SOM schematics]

KiCAD files of the connectors of A20-SOM/A20-SOM-EVB that are perfect as a template for own design can be found here: [https://github.com/OLIMEX/SOM/tree/master/A20/A20-SOM/KiCAD%20connector%20library KiCAD templates A20-SOM]

A20-SOM-EVB is considered Open Source Hardware, Eagle CAD files are available here [https://www.olimex.com/Products/SOM/A20/A20-SOM-EVB/resources/A20-SOM-EVB_eagle_sources.zip A20-SOM-EVB sources]

The CAD product used to design OLinuXino is Eagle and you can download evaluation free version from their [http://www.cadsoftusa.com/ web site]. The evaluation version allows you to inspect the schematic and the board file sources.

== How To? ==
 

=== Is it possible to boot Debian from NAND? Do you provide such image?===
Yes, it is possible. Use the latest Debian Jessie image and write "nandinstall". More information can be found in this wiki article: [[How_to_install_Debian_to_NAND| installing Debian Jessie to the 4GB NAND memory]]

There are other people who are also successful in booting Debian from the NAND. Make sure to check on the forum. Make sure to check the number of very good and optimized A20-OLinuXino Debian images by Igor Pečovnik. There are also his instructions for NAND installation of Debian: [http://www.armbian.com/download/ link to his web-site]

===How to correctly power off OLinuXino running from NAND Flash===
[http://olimex.wordpress.com/2014/01/24/how-to-correctly-power-off-olinuxino-running-android/ In this Blog post] we explain what are the problems. This is common problem for all computers running OS. [http://www.linux-mtd.infradead.org/doc/ubifs.html#L_ubifs_mlc Here] you can read more about MLC NAND Flash and Linux file system.

===How to build the official Debian Linux image for A20-SOM? ===

Build instructions and required files for the latest Debian Jessie images: [https://github.com/OLIMEX/OLINUXINO/tree/master/SOFTWARE/A20/A20-build-3.4.103-release-2 build instructions and required files at the GitHub page]

Build instructions and required files for the latest Debian Wheezy images: [https://github.com/OLIMEX/OLINUXINO/tree/master/SOFTWARE/A20/A20-build-3.4.90 instructions and files at the GitHub page]

===How to download new Android image to the NAND memory of my A20-SOM-4GB board?===

In order to download the Android image to the NAND memory of the board follow these steps:

1. Install and run PhoenixSuit (can be found here: [https://drive.google.com/file/d/0BwplT87k9SCgaTFTZnVST05ONzA/view?usp=sharing google drive location]).

2. Download and extract the latest official image - can be found above in the Android section of this article. Make sure that the download link you visit clearly indicates that the image is suitable for the NAND memory since there are images suitable for microSD card also. The images suitable for the microSD memory and those suitable for microSD card are different. However, the upload method is almost identical – using PhoenixSuit.

3. Go to firmware tab of the program and point to the already downloaded and extracted Android image.

4. Disconnect the power supply and USB cable from the A20 board.

5. Press and hold RECOVERY button, apply power supply (the requirement various depending on whether you use the board stand-alone or on top of A20-SOM-EVB), release RECOVERY button.

6. Connect USB cable to the mini USB connector.

7. You will be asked for drivers for the bootloader. Navigate to the folder where you extracted the PhoenixSuit and install the drivers from the respective executable (or manually point the installer to the drivers folder in the PhoenixSuit installation path).

8. PhoenixSuit will detect the board and would ask whether you wish to also of writing the image. Choose method of writing the image and confirm your wish to write the image.

9. Wait till upgrade succeeds

Note that it is not recommended to have your mini USB connected to an external USB hub. This might cause delays and might distort the signal levels. Always test with the USB connected straight to the USB ports of your computer.

===How do I write the official Android image to a micro SD card for my A20 board?===
A: First download one of the official Android images, which might be found in the Android section above.

Make sure that the download link you visit clearly indicates that the image is suitable for the microSD card since there are images suitable for NAND memory also. The images suitable for the microSD memory and those suitable for NAND card are different. However, the upload method is almost identical – using PhoenixSuit.

There are two types of Android images for microSD card that we usually provide and each of them has to be downloaded to a microSD card using a different method. The image provided for microSD card is either the native Android image that can be downloaded to the card via a software tool like PhoenixSuit (through the board) or an image taken from an already prepared microSD card that requires to simply write the image (through a microSD card reader).

'''It is more likely that you have an Android image that requires a simple copy to a card. If that is the case you can follow the exact steps as for Linux (e.g. using "Win32 Disk Imager" or "dd" command).'''

In order to prepare a microSD card with a native Android you will need a software tool called PhoenixSuit and then:

1. Install and run PhoenixSuit (can be found here: [https://drive.google.com/file/d/0BwplT87k9SCgaTFTZnVST05ONzA/view?usp=sharing download from google drive])

2. Go to the firmware tab of the program and point to a valid Android image (note that the images on Google drive are compressed and you have to extract the archives to .img files to be able write them with PhoenixSuit)

3. Disconnect the power supply and USB cable from the A20 board. Put an SD card in micro SD holder. We recommend 4GB class 10 card.

4. Press and hold RECOVERY button, apply power supply (the requirement various depending on whether you use the board stand-alone or on top of A20-SOM-EVB), release RECOVERY button.

5. Connect USB cable to the mini USB connector.

6. You will be asked for drivers for the boot-loader. Navigate to the folder where you extracted the PhoenixSuit and install the drivers from the respective executables (or manually point the installer to the drivers folder in the PhoenixSuit installation path).

7. PhoenixSuit will detect the board and would ask for the method of writing the image. Choose method of writing the image and confirm your wish to write the image.

8. Wait till upgrade succeeds

Note that it is not recommended to have your mini USB connected to an external USB hub. This
might cause delays and might distort the signal levels. Always test with the USB connected straight to the USB ports of your computer.

Important: When Android runs for very first time it takes several minutes to initialize all files and buffers please do not cut the power supply during this process! Also when fresh image is installed fast boot may be disabled, which means that when you apply power supply after few seconds Android will go in sleep mode and you have to press POWER button to start it, you can change to fast boot when you power off there is dialog box asking you if you want next boot to be fast boot, you have to check this box before you power off. Also note that you must do touch screen calibration when you run Android for very first time which might require a mouse.

===How do I write the Linux image to a micro SD card to use with my A20 board?===

To write a Linux image to an SD card under Windows we use Win32 Disk Imager):

*Download Win32 Disk Imager [http://sourceforge.net/projects/win32diskimager/ Win32 Disk Imager]
*Insert card
*Start program
*Select file
*Click "write"

To write a Linux image to an SD card under Linux:

For instance you have an image with the file name of "debian_2g.img". It would be downloaded to the SD card connected to a Linux machine using one of the following commands:

* # dd bs=4M oflag=sync if=debian_2g.img of=/dev/sdX
or
* # cp debian_2g.img /dev/sdX

where X is the uSD card.

===I don't have neither serial cable, nor HDMI monitor. I also can't access the local Ethernet network. Can I somehow access the board anyway?===

The latest official Debian Linux image allows the use the USB_OTG connector for SSH connection without the need of a LAN cable or a serial cable. You can use a mini USB cable connected between your host PC and the on-board mini USB connector. For connection convenience there is a DHCP server running specifically for USB0 interface. The DHCP server should give IP address to the new USB0 interface of your host PC so you can make SSH connection from your PC to the default board IP address of the USB0 interface – 192.168.2.1.

You can connect to the board using a mini USB cable and an SSH client (if you use Windows you might use "puTTY", for example) at address 192.168.2.1.

For Windows operating system - upon connection, the board should show up in "Windows Device Manager" as "RNDIS Ethernet Gadget". You might be asked to install a driver. The drivers can be found online as "RNDIS driver" (Remote Network Driver Interface Specification). The drivers are provided by Microsoft and they should be available for every Windows distribution - refer to the respective files and articles provided by Microsoft on how to install the required drivers.

===How to change HDMI, VGA and LCD resolutions in the official Debian image?===

The default SD card setup is made with settings for HDMI 720p/60Hz. If you want to change to some other LCD, VGA or HDMI resolution then you have to start change_display.sh script file in /root directory. When you are logged as super user in the board type:

For Debian Wheezy releases: ./change_display* (* = press 'tab' to auto-complete)
For Debian Jessie releases: change_display* (* = press 'tab' to auto-complete)

and press "Enter".

'''Note that the script should be executed as super user. Under the command line interface you are automatically logged as super user (user "root", password "olimex"). However, under the graphical environment you are not auto-logged as super user and you must type "sudo" before the command (in the GUI the super-user is "olimex" and the password is "olimex")'''

Then choose the resolution and the interface(LCD, HDMI or VGA). Note that the selection of a specific resolution is done by navigating with the arrow keys and pressing "space" button. Make sure the asterisk marks your selection properly.

The supported resolutions are:

'''For LCD:'''

*1. 4.3" (480x272)
*2. 7" (800x480)
*3. 10" (1024x600)
*4. 15.6" (1366x768)

Important: initially the boards are calibrated for a specific display. If you re-write the image (no matter whether the SD card or the NAND memory) you would need to use a mouse to calibrate the display initially. It might be impossible to calibrate it via touching the display.

'''For HDMI:'''

*0. 480i
*1. 576i
*2. 480p
*3. 576p
*4. 720p50
*5. 720p60
*6. 1080i50
*7. 1080i60
*8. 1080p24
*9. 1080p50
*10. 1080p60
*11. pal
*14. ntsc

'''For VGA:'''

*0. 1680x1050
*1. 1440x900
*2. 1360x768
*3. 1280x1024
*4. 1024x768
*5. 800x600
*6. 640x480
*7. 1920x1080
*8. 1280x720
 

===How to edit board configurations and definitions in the official Debian Linux? ===

Do you want a custom video resolution output? Do you need a different port definition? Do you need to change the hardware defitions of the board?

You would need to edit the board's script.bin/script.fex file. How to do it is described in a separate article: [[How_to_edit_board_configurations_and_definitions_in_the_official_Debian_Linux]].

===How to generate Arch Linux image?===

Recent forum post by user progmetalbg here: [https://www.olimex.com/forum/index.php?topic=4261.0| at Olimex forums]

[http://alarma20.wordpress.com/2013/09/13/howto-build-arch-linux-arm-for-a20-olinuxino-micro/ Older step by step instructions on how to build Arch Linux image for another A20 board]

===How to detect and enable the Ethernet controller (if it is disabled by default)? ===

Note: in the previous Debian releases the Ethernet was auto-detected and initialized during boot BUT this was causing big delays in the start-up of the board if you didn't want to use Ethernet or if there wasn't Ethernet cable connected.

You can enable it by following these two steps:

1. To check under what name the LAN is associated write "ifconfig –a"

2. If, for example, it is under eth0 name, then write: "dhclient eth0"

This should enable the Ethernet and then SSH would also be available.

===How to install Android on SD-card? ===

[http://olimex.wordpress.com/2013/10/02/android-4-2-2-images-for-a20-olinuxino-running-from-sd-card-is-updated-on-wiki/ Blog post about it]

===How to access UART, I2C, GPIOs under Android? ===

[http://olimex.wordpress.com/2013/10/02/a20-olinuxino-tools-for-android-released/ Use our Open Source OLinuXino A20-TOOLS]

===How to control PWM under Linux? ===

There is an article here: [[how to add pwm]]

===How to build the Android 4.2.2 image for A20-OLinuXino-MICRO? ===

First you need to Download the [http://dl.linux-sunxi.org/users/tsvetan/ANDROID-4.2.2-SDK2.0-KERNEL-3.4/ A20 SDK2.0 Linux Kernel 3.4]

Second you need to configure your environment read the instructions [http://source.android.com/source/initializing.html here]

Then Build the kernel, kernel modules and u-boot

cd lichee
./build.sh -psun7i_android

When done, continue with Bulding the android image:

cd ../android4.2
cd device/softwinner/
tar zxfv olinuxino-a20.tgz
cd ../../
source build/envsetup.sh
lunch #select olinuxino-a20_eng
extract-bsp
make -j4

Dave from Axon instruments wrote more detailed [http://axonjakarta.wordpress.com/2014/02/14/olimex-a20-android-building-4/ blog post] about how he generates the Android image]

A20-OLinuXino-LIME

2023-03-16T13:24:57Z

LubOlimex: /* Android images */

[[File:A20-OLinuXino-LIME.jpeg]]

A20-OLinuXino-LIME looks identical to [[A10-OLinuXino-LIME]], except for the more powerful A20 processor. The A10 and the A20 processors are pin-to-pin compatible. Because of the processor, software-wise the board is closer to [[A20-OLinuXino-MICRO]] than to the [[A10-OLinuXino-LIME]]. This resemblance to other designs definitely might speed the development on the board - a lot of software written for A20-OLinuXino-MICRO might work out-of-the-box with A20-OLinuXino-LIME. Additionally, pinout tables, GPIO maps, etc released for A10-OLinuXino-LIME would apply to A20-OLinuXino-LIME

A20-OLinuXino-LIME features:
*A20 Cortex-A7 dual-core ARM Cortex-A7 CPU and dual-core Mali 400 GPU
*512MB DDR3 RAM memory
*optional 4GB NAND FLASH memory
*SATA connector with 5V SATA power jack
*HDMI FullHD 1080p
*2x USB Low-Full-High-Speed hosts with power control and current limiter
*USB-OTG with power control and current limiter
*100MBit native Ethernet
*LiPo Battery connector with battery-charging capabilities
*LCD connector compatible with with 4.3", 7.0", 10.1" LCD modules from Olimex
*160 GPIOs on three GPIO connectors
*MicroSD card connector
*DEBUG-UART connector for console debug with USB-SERIAL-CABLE-F
*status LED
*Battery charge status LED
*Power LED
*2KB EEPROM for MAC address storage and more
*2 BUTTONS with ANDROID functionality + RESET button
*2 mount holes
*5V input power supply, noise immune design
*PCB dimensions: 84 x 60 mm

== Official images from OLIMEX ==

'''The recommended image for most of Olimex-made Linux boards is Olimage Linux, you can find information about it in the document here:'''

https://github.com/OLIMEX/OLINUXINO/blob/master/DOCUMENTS/OLIMAGE/Olimage-guide.pdf

'''Notice this wiki article refers to outdated images and practices, if using Olimage Linux, use the information only as a reference (do not take it literally)!'''

Below you will find links to download files containing the Debian and Android images. The images in this chapter were compiled by Olimex. They are recommended for beginners and first time users since they include full hardware support. If you are experienced Linux professional you might find bare-bone images and much more in the next chapter "Notable unofficial images".

The downloaded file is usually an archive of the image file. Make sure to first extract the 7z or zip archive. In order to be able to download the image to a SD card you can use software like Etcher or Win32DiskImager. Under Linux you can use dd command.

*For Windows: use 7zip and then use Win32DiskImager.exe (http://sourceforge.net/projects/win32diskimager/) to write the image

*For Linux: use p7zip package. If you don't have 7zip installed first install it 

#apt-get install p7zip
Copy a20_Lime_debian_second_release.7z file in your directory and unzip the archive with
#7za e a20_Lime_debian_second_release.7z
where a20_Lime_debian_second_release.7z
The output should be a new 4GB file with extension img
Put 4GB SD card in your card reader and type
# ls /dev/sd
Then press two times <TAB> you will see a list of your sd devices like sda sdb sdc note that some of these devices may be your hard disk so make sure you know which one is your sd card before you proceed as you can damage your HDD if you choose the wrong sd-device. You can do this by unplugging your sd card reader and identify which "sd" devices remove from the list.
Once you know which device is your sdcard like sda use this text instead of the sdX name in the references below:
#dd if=a20_Lim2_debian_second_release.img of=/dev/sdX

The file system can be extended to suit a bigger card. Use the following three commands to execute a script that would use all the free space of your card:

sudo su
resize_sd.sh /dev/mmcblk0 2
reboot

=== Linux images ===

These official Debian images should be downloaded to a microSD card. They are availalbe at our FTP server. You can install the Debian to the NAND or the eMMC of your board (if it comes with one). Information on booting Debian from the NAND might be found in these wiki articles: [[how to install Debian to NAND]]; [[how to install Debian to eMMC]]. Download locations for the official images might be found below:

'''ALWAYS FIRST TEST WITH LATEST OFFICIAL IMAGE, NEWER HARDWARE REVISIONS OF THE BOARD MIGHT NOT WORK WITH OLDER IMAGES!!!'''

----

'''Latest stable official images - Debian 8 (Jessie):'''

FTP location official Debian Jessie release #7, suitable for boards with no extra flash memory or with extra NAND memory (not suitable for boards with eMMC memory): [https://ftp.olimex.com/Allwinner_Images/A20-OLinuXino-LIME/Debian/sd/a20_Lime_debian_3.4.103_Jessie_2G_release_7.img.7z A20-OLinuXino-LIME Debian Jessie with kernel 3.4.103+ release 7]

FTP download location of official Debian Jessie release #9, suitable for boards with no extra flash memory or with extra eMMC flash memory (not suitable for boards with NAND flash memory): [https://ftp.olimex.com/Allwinner_Images/A20-OLinuXino-LIME/Debian/sd/a20_Lime_debian_3.4.103_Jessie_2G_eMMC_release_9.zip A20 lime mainline uboot sunxi kernel 3.4.103 jessie eMMC rel 9]

Image description and typical interfacing: [https://github.com/OLIMEX/OLINUXINO/blob/master/SOFTWARE/A20/A20-build-3.4.103-release-7/USAGE-AND-COMMON-PRACTICEs-A20-Olimex_kernel_3.4.103%2B_Jessie_rel_3.txt description and basic usage of different peripherals at at the GitHub page]

Image build instructions and required files for latest Debian Jessie release might be found here: [https://github.com/OLIMEX/OLINUXINO/blob/master/SOFTWARE/A20/A20-build-3.4.103-release-8/BUILD_DESCRIPTION_A20_Olimex_kernel_3.4.103%2B_Jessie_rel_8.txt build instructions and required files at the GitHub page]

You can find some older releases and older build instructions (older image revisions might be used as a reference, for testing purposes, or if you own old hardware revision of the board) at the following article: [[A20-OLinuXino-LIME-older-releases|older releases and older build instructions]]

----

Note: the A20-LIME-DEBIAN-SD card which we have in our web store contains the same image on 8GB Class10 fast micro SDcard, if you want to use this image please use card of Class10 speed or the performance of Linux will be very slow.

Note: in the previous Debian releases the Ethernet was auto-detected and initialized during boot BUT this was causing big delays in the start-up of the board if you didn't want to use Ethernet or if there wasn't Ethernet cable connected.

You can enable it by following these two steps:

1. To check under what name the LAN is associated write "ifconfig –a"

2. If, for example, it is under eth0 name, then write: "dhclient eth0"

This should enable the Ethernet and then SSH would also be available.

=== Android images ===

FTP location of official Android releases are below. Please read description of the image carefully.

FTP location of Android 4.2.2 release 1 for NAND memory (with HDMI and 800x480 support): [https://ftp.olimex.com/Allwinner_Images/A20-OLinuXino-LIME/Android/nand/a20_Lime_android_4.22_nand_LCD_800x480_release1.img A20-OLinuXino-Lime Android for NAND with HDMI and 7 inch display support]

FTP location of Android 4.2.2 release 1 for NAND memory (with HDMI and 1024x600 support): [https://ftp.olimex.com/Allwinner_Images/A20-OLinuXino-LIME/Android/nand/a20_Lime_android_4.22_nand_LCD_1024x600_release1.img A20-OLinuXino-Lime Android for NAND with HDMI and 10 inch display support]

Build instructions and source files for the official Android images for A20 boards in this repository: https://github.com/hehopmajieh/olinuxino_configs

FTP location of Android 4.2.2 release 1 for microSD card (with HDMI and 800x480 support): [https://ftp.olimex.com/Allwinner_Images/A20-OLinuXino-LIME/Android/sd/A20_Lime_android_422_SD_LCD_800x480_HDMI_release_1.7z A20-OLinuXino-Lime Android for microSD card with HDMI and 7 inch display support]

FTP location of Android 4.2.2 release 1 for microSD card (with HDMI and 1024x600 support): [https://ftp.olimex.com/Allwinner_Images/A20-OLinuXino-LIME/Android/sd/A20_Lime_android_422_SD_LCD_1024x600_HDMI_release_1.7z A20-OLinuXino-Lime Android for microSD card with HDMI and 10 inch display support]

== Notable unofficial images ==

Below you would find locations to images released by the community. These are not officially supported by Olimex, however, some of these releases are pretty good and worth a try:

*A number of very good and optimized A20-OLinuXino-LIME Armbian images: [https://www.armbian.com/olimex-lime/ link to LIME article at Armbian's web-site]

*A20-OLinuXino-LIME is supported by openSUSE Factory, installation instructions might be found here: [https://en.opensuse.org/HCL:A10-OLinuXino-LIME openSUSE wiki link]
 

== Documents ==

===A20-OLinuXino-LIME user's manual===
[https://www.olimex.com/Products/OLinuXino/A10/A10-OLinuXino-LIME/resources/A10-OLinuXino-LIME_manual.pdf User's manual for A20-OLinuXino-LIME and A20-OLinuXino-LIME-4GB]

=== A20 Brief ===
[https://github.com/OLIMEX/OLINUXINO/blob/master/HARDWARE/A20-PDFs/A20%20brief%2020130407.pdf A20 brief]

=== A20 Datasheet ===

[https://github.com/OLIMEX/OLINUXINO/blob/master/HARDWARE/A20-PDFs/A20%20Datasheet%20v1.0%2020130227.pdf A20 Datasheet]

=== A20 User Manual ===

[https://github.com/OLIMEX/OLINUXINO/blob/master/HARDWARE/A20-PDFs/A20%20User%20Manual%202013-03-22.pdf A20 user's manual]

== Hardware ==

===LIME shields===
[https://github.com/OLIMEX/OLINUXINO/tree/master/HARDWARE/A10-OLinuXino-LIME Eagle and KiCAD shield templates for LIME]

===GPIO description===

[https://github.com/OLIMEX/OLINUXINO/blob/master/HARDWARE/A10-OLinuXino-LIME/A10_Lime_GPIOs.pdf A10-OLinuXino-LIME GPIO description]

A template that might be used to create custom shields or own adapters might be downloaded for Eagle or KiCad at the GitHub here: [https://github.com/OLIMEX/OLINUXINO/tree/master/HARDWARE/A10-OLinuXino-LIME shield template]

===Power supply and consumption===

A20-OLinuXino-LIME requires 5V regulated power supply external source. regulated means that the power supply adapter should provide exactly 5V no matter loaded or unloaded (some cheap wallwart adapters are not regulated and under no load their power supply may be higher than 5V although marked as 5V power supply, please measure with voltmeter if your power supply provide 5V as if you connect more than 5V to LIME it will be damaged!!!)

The power jack is standard [https://www.olimex.com/wiki/PWRJACK OLIMEX Power jack].

A20-OLinuXino-LIME can be powered from three sources:
*+5VDC voltage applied PWR jack
*+3.7V from LiPo re-chargable battery connected to LiPo board connector
*+5V applied to USB-OTG connector

Power consumption is as follows:
*LiPo 3.7V power battery: 1.2W
*+5VDC input power: 1.3W

Comparison table of power consumption might be found at the following [https://www.olimex.com/Products/OLinuXino/_resources/OLinuXino-Consumption.pdf link].

LiPo battery allow backup power supply when main power is interrupted. A20-OLinuXino-LIME have power managment IC which charge the battery when main power is present, when power is interrupted the LiPo battery automatically provide backup power supply. Step-up converter prvide 5V for the USB peripherials too. For LiPo batteries we recommend these:
*[https://www.olimex.com/Products/Power/BATTERY-LIPO1400mAh/ 1400mAh]
*[https://www.olimex.com/Products/Power/BATTERY-LIPO3000mAh/ 3000mAh]
*[https://www.olimex.com/Products/Power/BATTERY-LIPO4400mAh/ 4400mAh]
*[https://www.olimex.com/Products/Power/BATTERY-LIPO6600mAh/ 6600mAh]
 

===Board dimensions===

A20-OLinuXino-LIME basic dimensions in mils: 3305.5 x 2347.0

Some additional measures might be seen in the image here:
[https://www.olimex.com/Products/OLinuXino/A10/A10-OLinuXino-LIME/resources/A10-LIME-dimensions.png link]

===CAD files===

A20-OLinuXino-LIME is Open Source Hardware, CAD files are available at [https://github.com/OLIMEX/OLINUXINO/tree/master/HARDWARE/A20-OLinuXino-LIME GitHub]

The CAD product used to design OLinuXino is Eagle and you can download evaluation free version from their [http://www.cadsoftusa.com/ web].

===Board Layout===

[[File:A20-OLinuXino-LIME-FRONT.png|650px]]

[[File:A10-OLinuXino-LIME-BACK.jpg|650px]]

== Software ==

===Linux Commands===

[[Linux-Commands]] Brief Linux Command reference

===Python===

pyA20Lime is Python library for the GPIOs, I2C and SPI use of suitable A20-OLinuXino-LIME's pins. It makes the access to GPIO, I2C and SPI considerably easier.

Full information might be found [https://pypi.python.org/pypi/pyA20Lime at this web address]

===GPIO under Linux===

GPIOs are located in /sys/class/gpio directory. Note that first you have to export GPIOs. For example:

add gpioPH2

root@A10:~# echo 20 > /sys/class/gpio/export

make PH2 output

root@A10:~# echo out > //sys/class/gpio/gpio20_ph2/direction

turn on onboard LED(connected to PH2)

root@A10:~# echo 1 > /sys/class/gpio/gpio20_ph2/value

turn off onboard LED(connected to PH2)

root@A10:~# echo 0 > /sys/class/gpio/gpio20_ph2/value

Full list with supported GPIOs is:

gpio21_ph7 gpio33_ph20 gpio45_pb12 gpio57_pi2 gpio69_pi14
gpio10_pg11 gpio22_ph9 gpio34_ph21 gpio46_pb13 gpio58_pi3 gpio6_pg5
gpio11_pc3 gpio23_ph10 gpio35_ph22 gpio47_pb14 gpio59_pi4 gpio70_pi15
gpio12_pc18 gpio24_ph11 gpio36_ph23 gpio48_pb15 gpio5_pg4 gpio71_pi16
gpio13_pc19 gpio25_ph12 gpio37_pb3 gpio49_pb16 gpio60_pi5 gpio72_pi17
gpio14_pc20 gpio26_ph13 gpio38_pb4 gpio4_pg3 gpio61_pi6 gpio73_pi18
gpio15_pc21 gpio27_ph14 gpio39_pb5 gpio50_pb17 gpio62_pi7 gpio74_pi19
gpio16_pc22 gpio28_ph15 gpio3_pg2 gpio51_ph24 gpio63_pi8 gpio75_pi20
gpio17_pc23 gpio29_ph16 gpio40_pb6 gpio52_ph25 gpio64_pi9 gpio7_pg6
gpio18_pc24 gpio2_pg1 gpio41_pb7 gpio53_ph26 gpio65_pi10 gpio8_pg7
gpio19_ph0 gpio30_ph17 gpio42_pb8 gpio54_ph27 gpio66_pi11 gpio9_pg8
gpio1_pg0 gpio31_ph18 gpio43_pb10 gpio55_pi0 gpio67_pi12 gpiochip1
gpio20_ph2 gpio32_ph19 gpio44_pb11 gpio56_pi1 gpio68_pi13

===Add Voice to your OLinuXino project===

[http://olimex.wordpress.com/2013/10/03/make-things-talk-with-olinuxino/ Installation of Festival on OLinuXino]

== How To? ==
===How to generate boot-able SD-card Debian Linux image for A20-OLinuXino-LIME? ===

Build instructions and required files for the latest Debian images: [https://github.com/OLIMEX/OLINUXINO/tree/master/SOFTWARE/A20/A20-build instructions and files at the GitHub page]

Note that Linux-Sunxi Kernel is a work-in-progress, this means you can try the current stage/sunxi-x.x branch but if something is broken and doesn't work just revert to the git tags we give in the blog and they would work for sure.

[https://github.com/linux-sunxi/u-boot-sunxi/wiki Sunxi u-boot loader] The linux-sunxi git page contains a lot of sources for all Olimex Allwinner boards.

===How to connect a display and adjust the video output resolution?===
There is a separate article on the subject: [[How_to_connect_display_to_a_Lime_board]]
 

=== Is it possible to boot Debian from NAND? Do you provide such image?===
Yes, it is possible. Use the latest Debian Jessie image and write "nandinstall". More information can be found in this wiki article: [[How_to_install_Debian_to_NAND| installing Debian Jessie to the NAND flash memory]]

If after installation to the NAND you have problems with the Ethernet, check the value of address 0x01c20164 in the memory, if it is 0x0 then change the value to 0x1006. Do the following:

Check the value with:

devmem 0x01c20164

Change the value with:

devmem 0x01c20164 w 0x1006

There are other people who are also successful in booting Debian from the NAND. Make sure to check on the forum. Make sure to check the number of very good and optimized A20-OLinuXino Debian images by Igor Pečovnik. There are also his instructions for NAND installation of Debian: [http://www.armbian.com/download/ link to his web-site]

===How to detect and enable the Ethernet controller (if it is disabled by default)? ===

Note: in the previous Debian releases the Ethernet was auto-detected and initialized during boot BUT this was causing big delays in the start-up of the board if you didn't want to use Ethernet or if there wasn't Ethernet cable connected.

You can enable it by following these two steps:

1. To check under what name the LAN is associated write "ifconfig –a"

2. If, for example, it is under eth0 name, then write: "dhclient eth0"

This should enable the Ethernet and then SSH would also be available.

===How to generate Arch Linux image?===

Recent forum post by user progmetalbg here: [https://www.olimex.com/forum/index.php?topic=4261.0| at Olimex forums]

[http://alarma20.wordpress.com/2013/09/13/howto-build-arch-linux-arm-for-a20-olinuxino-micro/ Older step by step instructions on how to build Arch Linux image for another A20 board]

===How to download new Android image to the NAND memory of my A20 board?===

To repair the image on the NAND re-upload it following these steps:

*1. Install and run PhoenixSuit (can be found here: [https://drive.google.com/file/d/0BwplT87k9SCgaTFTZnVST05ONzA/view?usp=sharing download from google drive]).

*2. Go to firmware tab of the program and point to a valid Android image (the latest official one may also be downloaded above).

*3. Disconnect the power supply and USB cable from the A20 board.

*4. Press and hold RECOVERY button, apply power supply 5V, release RECOVERY button.

*5. Connect USB cable to the mini USB connector.

*6. You will be asked for drivers for the bootloader. Navigate to the folder where you extracted the PhoenixSuit and install the drivers from the respective executables (or manually point the installer to the drivers folder in the PhoenixSuit installation path).

*7. PhoenixSuit will detect the board and would ask for the method of writing the image. Choose method of writing the image and confirm your wish to write the image.

*8. Wait till upgrade succeeds

Note that it is not recommended to have your mini USB connected to an external USB hub. This might cause delays and might distort the signal levels. Always test with the USB connected straight to the USB ports of your computer.

===How do I write the official Android image to a micro SD card for my A20 board?===
A: First download one of the official Android images, which might be found in the Android section above.

Make sure that the download link you visit clearly indicates that the image is suitable for the microSD card since there are images suitable for NAND memory also. The images suitable for the microSD memory and those suitable for NAND card are different. However, the upload method is almost identical – using PhoenixSuit.

There are two types of Android images for microSD card that we usually provide and each of them has to be downloaded to a microSD card using a different method. The image provided for microSD card is either the native Android image that can be downloaded to the card via a software tool like PhoenixSuit (through the board) or an image taken from an already prepared microSD card that requires to simply write the image (through a microSD card reader).

'''It is more likely that you have an Android image that requires a simple copy to a card. If that is the case you can follow the exact steps as for Linux (e.g. using "Win32 Disk Imager" or "dd" command).'''

In order to prepare a microSD card with a native Android you will need a software tool called PhoenixSuit and then:

• Install and run PhoenixSuit (can be found here: [https://drive.google.com/file/d/0BwplT87k9SCgaTFTZnVST05ONzA/view?usp=sharing download from google drive])

• Go to the firmware tab of the program and point to a valid Android image (note that the
imagesare compressed and you have to extract them to .img files to be able write
them with PhoenixSuit)

• Disconnect the power supply and USB cable from the A20 board. Put an SD card in micro SD
holder. We recommend 4GB class 10 card.

• Press and hold RECOVERY button, apply power supply 5V, release RECOVERY button.

• Connect USB cable to the mini USB connector.

• You will be asked for drivers for the boot-loader. Navigate to the folder where you extracted the PhoenixSuit and install the drivers from the respective executable (or manually point the installer to the drivers folder in the PhoenixSuit installation path).

• PhoenixSuit will detect the board and would ask for the method of writing the image. Choose
method of writing the image and confirm your wish to write the image.

• Wait till upgrade succeeds

Note that it is not recommended to have your mini USB connected to an external USB hub. This
might cause delays and might distort the signal levels. Always test with the USB connected straight to the USB ports of your computer.

Important: When Android runs for very first time it takes several minutes to initialize all files and buffers please do not cut the power supply during this process! Also when fresh image is installed fast boot may be disabled, which means that when you apply power supply after few seconds Android will go in sleep mode and you have to press POWER button to start it, you can change to fast boot when you power off there is dialog box asking you if you want next boot to be fast boot, you have to check this box before you power off. Also note that you must do touch screen calibration when you run Android for very first time which might require a mouse.

===I don't have neither serial cable, nor HDMI monitor. I also can't access the local Ethernet network. Can I somehow access the board anyway?===

The latest official Debian Linux image allows the use the USB_OTG connector for SSH connection without the need of a LAN cable or a serial cable. You can use a mini USB cable connected between your host PC and the on-board mini USB connector. For connection convenience there is a DHCP server running specifically for USB0 interface. The DHCP server should give IP address to the new USB0 interface of your host PC so you can make SSH connection from your PC to the default board IP address of the USB0 interface – 192.168.2.1.

You can connect to the board using a mini USB cable and an SSH client (if you use Windows you might use "puTTY", for example) at address 192.168.2.1.

For Windows operating system - upon connection, the board should show up in "Windows Device Manager" as "RNDIS Ethernet Gadget". You might be asked to install a driver. The drivers can be found online as "RNDIS driver" (Remote Network Driver Interface Specification). The drivers are provided by Microsoft and they should be available for every Windows distribution - refer to the respective files and articles provided by Microsoft on how to install the required drivers.

===How to edit board configurations and definitions in the official Debian Linux? ===

Do you want a custom video resolution output? Do you need a different port definition? Do you need to change the hardware defitions of the board?

You would need to edit the board's script.bin/script.fex file. How to do it is described in another separate article: [[How_to_edit_board_configurations_and_definitions_in_the_official_Debian_Linux]].

===How to add STK1160 video capture driver support in Kernel 3.4===

[https://www.olimex.com/wiki/STK1160-howto-linux-sunxi-3_4 STK1160] driver backport by Dimitar Tomov

[[Main_Page]]

A20-OLinuXino-LIME

2023-03-16T13:24:36Z

LubOlimex: /* Android images */

[[File:A20-OLinuXino-LIME.jpeg]]

A20-OLinuXino-LIME looks identical to [[A10-OLinuXino-LIME]], except for the more powerful A20 processor. The A10 and the A20 processors are pin-to-pin compatible. Because of the processor, software-wise the board is closer to [[A20-OLinuXino-MICRO]] than to the [[A10-OLinuXino-LIME]]. This resemblance to other designs definitely might speed the development on the board - a lot of software written for A20-OLinuXino-MICRO might work out-of-the-box with A20-OLinuXino-LIME. Additionally, pinout tables, GPIO maps, etc released for A10-OLinuXino-LIME would apply to A20-OLinuXino-LIME

A20-OLinuXino-LIME features:
*A20 Cortex-A7 dual-core ARM Cortex-A7 CPU and dual-core Mali 400 GPU
*512MB DDR3 RAM memory
*optional 4GB NAND FLASH memory
*SATA connector with 5V SATA power jack
*HDMI FullHD 1080p
*2x USB Low-Full-High-Speed hosts with power control and current limiter
*USB-OTG with power control and current limiter
*100MBit native Ethernet
*LiPo Battery connector with battery-charging capabilities
*LCD connector compatible with with 4.3", 7.0", 10.1" LCD modules from Olimex
*160 GPIOs on three GPIO connectors
*MicroSD card connector
*DEBUG-UART connector for console debug with USB-SERIAL-CABLE-F
*status LED
*Battery charge status LED
*Power LED
*2KB EEPROM for MAC address storage and more
*2 BUTTONS with ANDROID functionality + RESET button
*2 mount holes
*5V input power supply, noise immune design
*PCB dimensions: 84 x 60 mm

== Official images from OLIMEX ==

'''The recommended image for most of Olimex-made Linux boards is Olimage Linux, you can find information about it in the document here:'''

https://github.com/OLIMEX/OLINUXINO/blob/master/DOCUMENTS/OLIMAGE/Olimage-guide.pdf

'''Notice this wiki article refers to outdated images and practices, if using Olimage Linux, use the information only as a reference (do not take it literally)!'''

Below you will find links to download files containing the Debian and Android images. The images in this chapter were compiled by Olimex. They are recommended for beginners and first time users since they include full hardware support. If you are experienced Linux professional you might find bare-bone images and much more in the next chapter "Notable unofficial images".

The downloaded file is usually an archive of the image file. Make sure to first extract the 7z or zip archive. In order to be able to download the image to a SD card you can use software like Etcher or Win32DiskImager. Under Linux you can use dd command.

*For Windows: use 7zip and then use Win32DiskImager.exe (http://sourceforge.net/projects/win32diskimager/) to write the image

*For Linux: use p7zip package. If you don't have 7zip installed first install it 

#apt-get install p7zip
Copy a20_Lime_debian_second_release.7z file in your directory and unzip the archive with
#7za e a20_Lime_debian_second_release.7z
where a20_Lime_debian_second_release.7z
The output should be a new 4GB file with extension img
Put 4GB SD card in your card reader and type
# ls /dev/sd
Then press two times <TAB> you will see a list of your sd devices like sda sdb sdc note that some of these devices may be your hard disk so make sure you know which one is your sd card before you proceed as you can damage your HDD if you choose the wrong sd-device. You can do this by unplugging your sd card reader and identify which "sd" devices remove from the list.
Once you know which device is your sdcard like sda use this text instead of the sdX name in the references below:
#dd if=a20_Lim2_debian_second_release.img of=/dev/sdX

The file system can be extended to suit a bigger card. Use the following three commands to execute a script that would use all the free space of your card:

sudo su
resize_sd.sh /dev/mmcblk0 2
reboot

=== Linux images ===

These official Debian images should be downloaded to a microSD card. They are availalbe at our FTP server. You can install the Debian to the NAND or the eMMC of your board (if it comes with one). Information on booting Debian from the NAND might be found in these wiki articles: [[how to install Debian to NAND]]; [[how to install Debian to eMMC]]. Download locations for the official images might be found below:

'''ALWAYS FIRST TEST WITH LATEST OFFICIAL IMAGE, NEWER HARDWARE REVISIONS OF THE BOARD MIGHT NOT WORK WITH OLDER IMAGES!!!'''

----

'''Latest stable official images - Debian 8 (Jessie):'''

FTP location official Debian Jessie release #7, suitable for boards with no extra flash memory or with extra NAND memory (not suitable for boards with eMMC memory): [https://ftp.olimex.com/Allwinner_Images/A20-OLinuXino-LIME/Debian/sd/a20_Lime_debian_3.4.103_Jessie_2G_release_7.img.7z A20-OLinuXino-LIME Debian Jessie with kernel 3.4.103+ release 7]

FTP download location of official Debian Jessie release #9, suitable for boards with no extra flash memory or with extra eMMC flash memory (not suitable for boards with NAND flash memory): [https://ftp.olimex.com/Allwinner_Images/A20-OLinuXino-LIME/Debian/sd/a20_Lime_debian_3.4.103_Jessie_2G_eMMC_release_9.zip A20 lime mainline uboot sunxi kernel 3.4.103 jessie eMMC rel 9]

Image description and typical interfacing: [https://github.com/OLIMEX/OLINUXINO/blob/master/SOFTWARE/A20/A20-build-3.4.103-release-7/USAGE-AND-COMMON-PRACTICEs-A20-Olimex_kernel_3.4.103%2B_Jessie_rel_3.txt description and basic usage of different peripherals at at the GitHub page]

Image build instructions and required files for latest Debian Jessie release might be found here: [https://github.com/OLIMEX/OLINUXINO/blob/master/SOFTWARE/A20/A20-build-3.4.103-release-8/BUILD_DESCRIPTION_A20_Olimex_kernel_3.4.103%2B_Jessie_rel_8.txt build instructions and required files at the GitHub page]

You can find some older releases and older build instructions (older image revisions might be used as a reference, for testing purposes, or if you own old hardware revision of the board) at the following article: [[A20-OLinuXino-LIME-older-releases|older releases and older build instructions]]

----

Note: the A20-LIME-DEBIAN-SD card which we have in our web store contains the same image on 8GB Class10 fast micro SDcard, if you want to use this image please use card of Class10 speed or the performance of Linux will be very slow.

Note: in the previous Debian releases the Ethernet was auto-detected and initialized during boot BUT this was causing big delays in the start-up of the board if you didn't want to use Ethernet or if there wasn't Ethernet cable connected.

You can enable it by following these two steps:

1. To check under what name the LAN is associated write "ifconfig –a"

2. If, for example, it is under eth0 name, then write: "dhclient eth0"

This should enable the Ethernet and then SSH would also be available.

=== Android images ===

FTP location of official Android releases are below. Please read description of the image carefully.

FTP location of Android 4.2.2 release 1 for NAND memory (with HDMI and 800x480 support): [https://ftp.olimex.com/Allwinner_Images/A20-OLinuXino-LIME/Android/nand/a20_Lime_android_4.22_nand_LCD_800x480_release1.img A20-OLinuXino-Lime Android for NAND with HDMI and 7 inch display support]

FTP location of Android 4.2.2 release 1 for NAND memory (with HDMI and 1024x600 support): [https://ftp.olimex.com/Allwinner_Images/A20-OLinuXino-LIME/Android/nand/a20_Lime_android_4.22_nand_LCD_1024x600_release1.img A20-OLinuXino-Lime Android for NAND with HDMI and 10 inch display support]

Build instructions and source files for the official Android images for A20 boards in this repository: https://github.com/hehopmajieh/olinuxino_configs

FTP location of Android 4.2.2 release 1 for microSD card (with HDMI and 800x480 support): [https://ftp.olimex.com/Allwinner_Images/A20-OLinuXino-LIME/Android/sd/A20_Lime_android_422_SD_LCD_800x480_HDMI_release_1.7z A20-OLinuXino-Lime Android for microSD card with HDMI and 7 inch display support]

FTP location of Android 4.2.2 release 1 for microSD card (with HDMI and 1024x600 support): [https://ftp.olimex.com/Allwinner_Images/A20-OLinuXino-LIME/Android/sd/A20_Lime_android_422_SD_LCD_1024x600_HDMI_release_1.7z A20-OLinuXino-Lime Android for microSD card with HDMI and 10 inch display support]]

== Notable unofficial images ==

Below you would find locations to images released by the community. These are not officially supported by Olimex, however, some of these releases are pretty good and worth a try:

*A number of very good and optimized A20-OLinuXino-LIME Armbian images: [https://www.armbian.com/olimex-lime/ link to LIME article at Armbian's web-site]

*A20-OLinuXino-LIME is supported by openSUSE Factory, installation instructions might be found here: [https://en.opensuse.org/HCL:A10-OLinuXino-LIME openSUSE wiki link]
 

== Documents ==

===A20-OLinuXino-LIME user's manual===
[https://www.olimex.com/Products/OLinuXino/A10/A10-OLinuXino-LIME/resources/A10-OLinuXino-LIME_manual.pdf User's manual for A20-OLinuXino-LIME and A20-OLinuXino-LIME-4GB]

=== A20 Brief ===
[https://github.com/OLIMEX/OLINUXINO/blob/master/HARDWARE/A20-PDFs/A20%20brief%2020130407.pdf A20 brief]

=== A20 Datasheet ===

[https://github.com/OLIMEX/OLINUXINO/blob/master/HARDWARE/A20-PDFs/A20%20Datasheet%20v1.0%2020130227.pdf A20 Datasheet]

=== A20 User Manual ===

[https://github.com/OLIMEX/OLINUXINO/blob/master/HARDWARE/A20-PDFs/A20%20User%20Manual%202013-03-22.pdf A20 user's manual]

== Hardware ==

===LIME shields===
[https://github.com/OLIMEX/OLINUXINO/tree/master/HARDWARE/A10-OLinuXino-LIME Eagle and KiCAD shield templates for LIME]

===GPIO description===

[https://github.com/OLIMEX/OLINUXINO/blob/master/HARDWARE/A10-OLinuXino-LIME/A10_Lime_GPIOs.pdf A10-OLinuXino-LIME GPIO description]

A template that might be used to create custom shields or own adapters might be downloaded for Eagle or KiCad at the GitHub here: [https://github.com/OLIMEX/OLINUXINO/tree/master/HARDWARE/A10-OLinuXino-LIME shield template]

===Power supply and consumption===

A20-OLinuXino-LIME requires 5V regulated power supply external source. regulated means that the power supply adapter should provide exactly 5V no matter loaded or unloaded (some cheap wallwart adapters are not regulated and under no load their power supply may be higher than 5V although marked as 5V power supply, please measure with voltmeter if your power supply provide 5V as if you connect more than 5V to LIME it will be damaged!!!)

The power jack is standard [https://www.olimex.com/wiki/PWRJACK OLIMEX Power jack].

A20-OLinuXino-LIME can be powered from three sources:
*+5VDC voltage applied PWR jack
*+3.7V from LiPo re-chargable battery connected to LiPo board connector
*+5V applied to USB-OTG connector

Power consumption is as follows:
*LiPo 3.7V power battery: 1.2W
*+5VDC input power: 1.3W

Comparison table of power consumption might be found at the following [https://www.olimex.com/Products/OLinuXino/_resources/OLinuXino-Consumption.pdf link].

LiPo battery allow backup power supply when main power is interrupted. A20-OLinuXino-LIME have power managment IC which charge the battery when main power is present, when power is interrupted the LiPo battery automatically provide backup power supply. Step-up converter prvide 5V for the USB peripherials too. For LiPo batteries we recommend these:
*[https://www.olimex.com/Products/Power/BATTERY-LIPO1400mAh/ 1400mAh]
*[https://www.olimex.com/Products/Power/BATTERY-LIPO3000mAh/ 3000mAh]
*[https://www.olimex.com/Products/Power/BATTERY-LIPO4400mAh/ 4400mAh]
*[https://www.olimex.com/Products/Power/BATTERY-LIPO6600mAh/ 6600mAh]
 

===Board dimensions===

A20-OLinuXino-LIME basic dimensions in mils: 3305.5 x 2347.0

Some additional measures might be seen in the image here:
[https://www.olimex.com/Products/OLinuXino/A10/A10-OLinuXino-LIME/resources/A10-LIME-dimensions.png link]

===CAD files===

A20-OLinuXino-LIME is Open Source Hardware, CAD files are available at [https://github.com/OLIMEX/OLINUXINO/tree/master/HARDWARE/A20-OLinuXino-LIME GitHub]

The CAD product used to design OLinuXino is Eagle and you can download evaluation free version from their [http://www.cadsoftusa.com/ web].

===Board Layout===

[[File:A20-OLinuXino-LIME-FRONT.png|650px]]

[[File:A10-OLinuXino-LIME-BACK.jpg|650px]]

== Software ==

===Linux Commands===

[[Linux-Commands]] Brief Linux Command reference

===Python===

pyA20Lime is Python library for the GPIOs, I2C and SPI use of suitable A20-OLinuXino-LIME's pins. It makes the access to GPIO, I2C and SPI considerably easier.

Full information might be found [https://pypi.python.org/pypi/pyA20Lime at this web address]

===GPIO under Linux===

GPIOs are located in /sys/class/gpio directory. Note that first you have to export GPIOs. For example:

add gpioPH2

root@A10:~# echo 20 > /sys/class/gpio/export

make PH2 output

root@A10:~# echo out > //sys/class/gpio/gpio20_ph2/direction

turn on onboard LED(connected to PH2)

root@A10:~# echo 1 > /sys/class/gpio/gpio20_ph2/value

turn off onboard LED(connected to PH2)

root@A10:~# echo 0 > /sys/class/gpio/gpio20_ph2/value

Full list with supported GPIOs is:

gpio21_ph7 gpio33_ph20 gpio45_pb12 gpio57_pi2 gpio69_pi14
gpio10_pg11 gpio22_ph9 gpio34_ph21 gpio46_pb13 gpio58_pi3 gpio6_pg5
gpio11_pc3 gpio23_ph10 gpio35_ph22 gpio47_pb14 gpio59_pi4 gpio70_pi15
gpio12_pc18 gpio24_ph11 gpio36_ph23 gpio48_pb15 gpio5_pg4 gpio71_pi16
gpio13_pc19 gpio25_ph12 gpio37_pb3 gpio49_pb16 gpio60_pi5 gpio72_pi17
gpio14_pc20 gpio26_ph13 gpio38_pb4 gpio4_pg3 gpio61_pi6 gpio73_pi18
gpio15_pc21 gpio27_ph14 gpio39_pb5 gpio50_pb17 gpio62_pi7 gpio74_pi19
gpio16_pc22 gpio28_ph15 gpio3_pg2 gpio51_ph24 gpio63_pi8 gpio75_pi20
gpio17_pc23 gpio29_ph16 gpio40_pb6 gpio52_ph25 gpio64_pi9 gpio7_pg6
gpio18_pc24 gpio2_pg1 gpio41_pb7 gpio53_ph26 gpio65_pi10 gpio8_pg7
gpio19_ph0 gpio30_ph17 gpio42_pb8 gpio54_ph27 gpio66_pi11 gpio9_pg8
gpio1_pg0 gpio31_ph18 gpio43_pb10 gpio55_pi0 gpio67_pi12 gpiochip1
gpio20_ph2 gpio32_ph19 gpio44_pb11 gpio56_pi1 gpio68_pi13

===Add Voice to your OLinuXino project===

[http://olimex.wordpress.com/2013/10/03/make-things-talk-with-olinuxino/ Installation of Festival on OLinuXino]

== How To? ==
===How to generate boot-able SD-card Debian Linux image for A20-OLinuXino-LIME? ===

Build instructions and required files for the latest Debian images: [https://github.com/OLIMEX/OLINUXINO/tree/master/SOFTWARE/A20/A20-build instructions and files at the GitHub page]

Note that Linux-Sunxi Kernel is a work-in-progress, this means you can try the current stage/sunxi-x.x branch but if something is broken and doesn't work just revert to the git tags we give in the blog and they would work for sure.

[https://github.com/linux-sunxi/u-boot-sunxi/wiki Sunxi u-boot loader] The linux-sunxi git page contains a lot of sources for all Olimex Allwinner boards.

===How to connect a display and adjust the video output resolution?===
There is a separate article on the subject: [[How_to_connect_display_to_a_Lime_board]]
 

=== Is it possible to boot Debian from NAND? Do you provide such image?===
Yes, it is possible. Use the latest Debian Jessie image and write "nandinstall". More information can be found in this wiki article: [[How_to_install_Debian_to_NAND| installing Debian Jessie to the NAND flash memory]]

If after installation to the NAND you have problems with the Ethernet, check the value of address 0x01c20164 in the memory, if it is 0x0 then change the value to 0x1006. Do the following:

Check the value with:

devmem 0x01c20164

Change the value with:

devmem 0x01c20164 w 0x1006

There are other people who are also successful in booting Debian from the NAND. Make sure to check on the forum. Make sure to check the number of very good and optimized A20-OLinuXino Debian images by Igor Pečovnik. There are also his instructions for NAND installation of Debian: [http://www.armbian.com/download/ link to his web-site]

===How to detect and enable the Ethernet controller (if it is disabled by default)? ===

Note: in the previous Debian releases the Ethernet was auto-detected and initialized during boot BUT this was causing big delays in the start-up of the board if you didn't want to use Ethernet or if there wasn't Ethernet cable connected.

You can enable it by following these two steps:

1. To check under what name the LAN is associated write "ifconfig –a"

2. If, for example, it is under eth0 name, then write: "dhclient eth0"

This should enable the Ethernet and then SSH would also be available.

===How to generate Arch Linux image?===

Recent forum post by user progmetalbg here: [https://www.olimex.com/forum/index.php?topic=4261.0| at Olimex forums]

[http://alarma20.wordpress.com/2013/09/13/howto-build-arch-linux-arm-for-a20-olinuxino-micro/ Older step by step instructions on how to build Arch Linux image for another A20 board]

===How to download new Android image to the NAND memory of my A20 board?===

To repair the image on the NAND re-upload it following these steps:

*1. Install and run PhoenixSuit (can be found here: [https://drive.google.com/file/d/0BwplT87k9SCgaTFTZnVST05ONzA/view?usp=sharing download from google drive]).

*2. Go to firmware tab of the program and point to a valid Android image (the latest official one may also be downloaded above).

*3. Disconnect the power supply and USB cable from the A20 board.

*4. Press and hold RECOVERY button, apply power supply 5V, release RECOVERY button.

*5. Connect USB cable to the mini USB connector.

*6. You will be asked for drivers for the bootloader. Navigate to the folder where you extracted the PhoenixSuit and install the drivers from the respective executables (or manually point the installer to the drivers folder in the PhoenixSuit installation path).

*7. PhoenixSuit will detect the board and would ask for the method of writing the image. Choose method of writing the image and confirm your wish to write the image.

*8. Wait till upgrade succeeds

Note that it is not recommended to have your mini USB connected to an external USB hub. This might cause delays and might distort the signal levels. Always test with the USB connected straight to the USB ports of your computer.

===How do I write the official Android image to a micro SD card for my A20 board?===
A: First download one of the official Android images, which might be found in the Android section above.

Make sure that the download link you visit clearly indicates that the image is suitable for the microSD card since there are images suitable for NAND memory also. The images suitable for the microSD memory and those suitable for NAND card are different. However, the upload method is almost identical – using PhoenixSuit.

There are two types of Android images for microSD card that we usually provide and each of them has to be downloaded to a microSD card using a different method. The image provided for microSD card is either the native Android image that can be downloaded to the card via a software tool like PhoenixSuit (through the board) or an image taken from an already prepared microSD card that requires to simply write the image (through a microSD card reader).

'''It is more likely that you have an Android image that requires a simple copy to a card. If that is the case you can follow the exact steps as for Linux (e.g. using "Win32 Disk Imager" or "dd" command).'''

In order to prepare a microSD card with a native Android you will need a software tool called PhoenixSuit and then:

• Install and run PhoenixSuit (can be found here: [https://drive.google.com/file/d/0BwplT87k9SCgaTFTZnVST05ONzA/view?usp=sharing download from google drive])

• Go to the firmware tab of the program and point to a valid Android image (note that the
imagesare compressed and you have to extract them to .img files to be able write
them with PhoenixSuit)

• Disconnect the power supply and USB cable from the A20 board. Put an SD card in micro SD
holder. We recommend 4GB class 10 card.

• Press and hold RECOVERY button, apply power supply 5V, release RECOVERY button.

• Connect USB cable to the mini USB connector.

• You will be asked for drivers for the boot-loader. Navigate to the folder where you extracted the PhoenixSuit and install the drivers from the respective executable (or manually point the installer to the drivers folder in the PhoenixSuit installation path).

• PhoenixSuit will detect the board and would ask for the method of writing the image. Choose
method of writing the image and confirm your wish to write the image.

• Wait till upgrade succeeds

Note that it is not recommended to have your mini USB connected to an external USB hub. This
might cause delays and might distort the signal levels. Always test with the USB connected straight to the USB ports of your computer.

Important: When Android runs for very first time it takes several minutes to initialize all files and buffers please do not cut the power supply during this process! Also when fresh image is installed fast boot may be disabled, which means that when you apply power supply after few seconds Android will go in sleep mode and you have to press POWER button to start it, you can change to fast boot when you power off there is dialog box asking you if you want next boot to be fast boot, you have to check this box before you power off. Also note that you must do touch screen calibration when you run Android for very first time which might require a mouse.

===I don't have neither serial cable, nor HDMI monitor. I also can't access the local Ethernet network. Can I somehow access the board anyway?===

The latest official Debian Linux image allows the use the USB_OTG connector for SSH connection without the need of a LAN cable or a serial cable. You can use a mini USB cable connected between your host PC and the on-board mini USB connector. For connection convenience there is a DHCP server running specifically for USB0 interface. The DHCP server should give IP address to the new USB0 interface of your host PC so you can make SSH connection from your PC to the default board IP address of the USB0 interface – 192.168.2.1.

You can connect to the board using a mini USB cable and an SSH client (if you use Windows you might use "puTTY", for example) at address 192.168.2.1.

For Windows operating system - upon connection, the board should show up in "Windows Device Manager" as "RNDIS Ethernet Gadget". You might be asked to install a driver. The drivers can be found online as "RNDIS driver" (Remote Network Driver Interface Specification). The drivers are provided by Microsoft and they should be available for every Windows distribution - refer to the respective files and articles provided by Microsoft on how to install the required drivers.

===How to edit board configurations and definitions in the official Debian Linux? ===

Do you want a custom video resolution output? Do you need a different port definition? Do you need to change the hardware defitions of the board?

You would need to edit the board's script.bin/script.fex file. How to do it is described in another separate article: [[How_to_edit_board_configurations_and_definitions_in_the_official_Debian_Linux]].

===How to add STK1160 video capture driver support in Kernel 3.4===

[https://www.olimex.com/wiki/STK1160-howto-linux-sunxi-3_4 STK1160] driver backport by Dimitar Tomov

[[Main_Page]]