|
|
| Line 1: |
Line 1: |
| − | [[Smart4418/zh | 查看中文]]
| |
| | | | |
| − | ==Introduction==
| |
| − | [[File:Smart441801.jpg|thumb|frameless|500px|]]
| |
| − | [[File:Smart4418-SDK-1606F1.jpg|thumb|500px|Front]]
| |
| − | [[File:Smart4418-SDK-1606O1.jpg|thumb|500px|Overview]]
| |
| − | * The Smart4418 CPU board is a quad core Cortex A9 CPU board designed and developed by FriendlyARM for industrial applications. As a successor of the Smart210 CPU board it uses the Samsung Quad Core Cortex-A9 S5P4418 SoC with dynamic frequency scaling up to 1.4GHz. The standard Smart4418 CPU board has 1GB DDR3 RAM and 8GB eMMC. It has the AXP229 PMU enabling software power off/on and wake-up functions. In addition its Gbps Ethernet and audio jack make it suitable for various industrial applications.
| |
| − | * The Smart4418 CPU board has 2.0mm pitch double row pin headers(P1, P2 and P4) containing 174 pins in total. These pins contain most popular interface pins. By default we have P1 and P2 soldered on the board and leave P4 for users' applications. It works with various FriendlyARM LCDs e.g. 3.5"LCD, 4.3"LCD, 5"LCD, 7"LCD and 10.1"LCD.
| |
| − | * In addition we have a Smart4418/6818SDK carrier board which enables the Smart4418 CPU board's Gbps Ethernet.In addition FriendlyARM will soon release a Samsung Octa Core Cortex-A53 S5P6818@1.4GHz based board which is pin to pin compatible to the Smart4418 CPU board.
| |
| − | * For more details about the Smart4418 SDK carrier board V1606 refer to [http://wiki.friendlyarm.com/wiki/index.php/Smart4418_SDK Smart4418SDK 1606].
| |
| − |
| |
| − | ==Features==
| |
| − | * CPU: Samsung S5P4418 Quad Core Cortex-A9, with dynamic frequency scaling from 400M Hz to 1.4G Hz
| |
| − | * PMU Power Management Unit: AXP228. it supports software power-off and wake-up functions.
| |
| − | * DDR3 RAM: 1GB 32bit DDR3 RAM
| |
| − | * Ethernet: Gbps Ethernet(RTL8211E) with unique MAC
| |
| − | * eMMC: 8GB
| |
| − | * Audio: 1 x audio codec chip, 1 x onboard Microphone and 1 x audio jack
| |
| − | * LED: 1 x Power LED, 2 x GPIO LED
| |
| − | * Others: onboard thermistor
| |
| − | * PCB Dimension: 74 x 55 mm, Six-Layer
| |
| − | * Power: DC 5V, up to 1.2A
| |
| − | * OS/Software: u-boot, Android5.1/4.4, Debian8, ubuntu-core
| |
| − | * 3 x 2.0mm pitch double row pin header, 174 pins in total:
| |
| − | ** USB 2.0 - Host x1, OTG x1
| |
| − | ** Video output/Display - RGB Parallel I/F (24-bit), LVDS and HDMI 1.4a
| |
| − | ** Video input - DVP Camera interface, ITU-R BT 601/656 8-bit and MIPI-CSI
| |
| − | ** Audio input - Microphone
| |
| − | ** Audio output - Audio jack (with headset detection) and HDMI audio
| |
| − | ** Ethernet - 10/100/1000Mbps Ethernet x 1
| |
| − | ** ADC - CPU internal ADC, 7 channels, 12-bit, range: 0 ~ 1.8V
| |
| − | ** External interface - SDIO/MMC x2, SPI x2, I2C x3, UART x5, PWM x3, GPIOs x24
| |
| − | ** Others - Power key input, RESET input, RESET output, RTC battery input
| |
| − |
| |
| − | ==Pin Spec==
| |
| − | ::{| class="wikitable"
| |
| − | |-
| |
| − | | style="background: PaleTurquoise; color: black" colspan="4"| '''P1''' || style="background: PaleTurquoise; color: black" colspan="4"| '''P2'''
| |
| − | |-
| |
| − | |Pin# || Name || Pin# || Name ||Pin# || Name || Pin# || Name
| |
| − | |-
| |
| − | |1 || VDD_5V || 2 || DGND ||1 || UART0_TX || 2 || UART0_RX
| |
| − | |-
| |
| − | |3 || RTC_BATT || 4 || GPIOB8 ||3 || UART1_TX || 4 || UART1_RX
| |
| − | |-
| |
| − | |5 || NRESETIN || 6 || GPIOC17 ||5 || UART2_TX || 6 || UART2_RX
| |
| − | |-
| |
| − | |7 || MMC0_CMD || 8 || MMC1_CMD ||7 || UART3_TX || 8 || UART3_RX
| |
| − | |-
| |
| − | |9 || MMC0_CLK || 10 || MMC1_CLK ||9 || UART1_nCTS || 10 || UART1_nRTS
| |
| − | |-
| |
| − | |11 || MMC0_D0 || 12 || MMC1_D0 ||11 || CAM0_D0 || 12 || CAM0_D1
| |
| − | |-
| |
| − | |13 || MMC0_D1 || 14 || MMC1_D1 ||13 || CAM0_D2 || 14 || CAM0_D3
| |
| − | |-
| |
| − | |15 || MMC0_D2 || 16 || MMC1_D2 ||15 || CAM0_D4 || 16 || CAM0_D5
| |
| − | |-
| |
| − | |17 || MMC0_D3 || 18 || MMC1_D3 ||17 || CAM0_D6 || 18 || CAM0_D7
| |
| − | |-
| |
| − | |19 || MMC0_CD || 20 ||GPIOB24 ||19 || CAM0_PCLK || 20 ||CAM0_VSYNC
| |
| − | |-
| |
| − | |21 || PWRKEY || 22 || SPI1_CS/GPIOC10 ||21 || CAM0_HYNC || 22 || GPIOB14
| |
| − | |-
| |
| − | |23 || GPIOB28/UART4_RX || 24 || SPI1_MISO/GPIOC11 ||23 || GPIOB16 || 24 || HDMI_TX1P
| |
| − | |-
| |
| − | |25 || GPIOB29/UART4_TX || 26 || SPI1_MOSI/GPIOC12 |||25 || HDMI_TX0P || 26 || HDMI_TX1N
| |
| − | |-
| |
| − | |27 || GPIOB30 || 28 || SPI1_CLK/GPIOC9 ||27 || HDMI_TX0N || 28 || HDMI_TXCP
| |
| − | |-
| |
| − | |29 || GPIOC15 || 30 || GPIOC16 ||29 || HDMI_TX2P || 30 || HDMI_TXCN
| |
| − | |-
| |
| − | |31 || GPIOB31 || 32 || GPIOB18 ||31 || HDMI_TX2N || 32 || HDMI_HPD
| |
| − | |-
| |
| − | |33 || GPIOD1/PWM0 || 34 || I2C0_SCL ||33 || I2C1_SDA || 34 || I2C1_SCL
| |
| − | |-
| |
| − | |35 || GPIOC13/PWM1 || 36 || I2C0_SDA ||35 || USB_OTG_ID || 36 || SPI0_CS
| |
| − | |-
| |
| − | |37 || USB_HOST_D- || 38 || I2C2_SCL ||37 || USB_OTG_D- || 38 || SPI0_MISO
| |
| − | |-
| |
| − | |39 || USB_HOST_D+ || 40 || I2C2_SDA ||39 || USB_OTG_D+ || 40 || SPI0_MOSI
| |
| − | |-
| |
| − | |41 || LCD_B0 || 42 || LCD_B1 ||41 || VBUS_5V || 42 || SPI0_CL
| |
| − | |-
| |
| − | |43 || LCD_B2 || 44 || LCD_B3 ||43 || LVDS_CLKP || 44 || GPIOB25
| |
| − | |-
| |
| − | |45 || LCD_B4 || 46 || LCD_B5 ||45 || LVDS_CLKM || 46 || DGND
| |
| − | |-
| |
| − | |47 || LCD_B6 || 48 || LCD_B7 ||47 || LVDS_Y0P || 48 || LAN_MDI1_N
| |
| − | |-
| |
| − | |49 || LCD_G0 || 50 || LCD_G1 ||49 ||LVDS_Y0M || 50 || LAN_MDI1_P
| |
| − | |-
| |
| − | |51 || LCD_G2 || 52 || LCD_G3 ||51 || LVDS_Y1P || 52 || LAN_MDI0_N
| |
| − | |-
| |
| − | |53 || LCD_G4 || 54 || LCD_G5 ||53 || LVDS_Y1M || 54 || LAN_MDI0_P
| |
| − | |-
| |
| − | |55 || LCD_G6 || 56 || LCD_G7 ||55 || LVDS_Y2P || 56 || LINK_LED
| |
| − | |-
| |
| − | |57 || LCD_R0 || 58 || LCD_R1 ||57 || LVDS_Y2M || 58 || SPEED_LED
| |
| − | |-
| |
| − | |59 || LCD_R2 || 60 || LCD_R3 ||59 || LVDS_Y3P || 60 || DGND
| |
| − | |-
| |
| − | |61 || LCD_R4 || 62 || LCD_R5 ||61 || LVDS_Y3M || 62 || HP_DETECT
| |
| − | |-
| |
| − | |63 || LCD_R6 || 64 || LCD_R7 ||63 || HP-R || 64 || HP-L
| |
| − | |-
| |
| − | |65 || LCD_VSYNC || 66 || LCD_HSYNC ||65 || LAN_MDI2_P || 66 || LAN_MDI3_P
| |
| − | |-
| |
| − | |67 || LCD_CLK || 68 || LCD_DE ||67 || LAN_MDI2_N ||68 || LAN_MDI3_N
| |
| − | |-
| |
| − | |69 || DGND || 70 || BOOT_CS ||69 || Mic-P || 70 || Mic-N
| |
| − | |}
| |
| − |
| |
| − | ::{| class="wikitable"
| |
| − | |-
| |
| − | | style="background: PaleTurquoise; color: black" colspan="4"| '''P4'''
| |
| − | |-
| |
| − | |Pin# || Name || Pin# || Name
| |
| − | |-
| |
| − | |1 || MIPICSI_DP0 || 2 || GPIOD8/PPM
| |
| − | |-
| |
| − | |3 || MIPICSI_DN0 || 4 || GPIOC7
| |
| − | |-
| |
| − | |5 || MIPICSI_DP1 || 6 || GPIOC8
| |
| − | |-
| |
| − | |7 || MIPICSI_DN1 || 8 || GPIOC24
| |
| − | |-
| |
| − | |9 || MIPICSI_DP2 || 10 || GPIOC28
| |
| − | |-
| |
| − | |11 || MIPICSI_DN2 || 12 || GPIOC0
| |
| − | |-
| |
| − | |13 || MIPICSI_DP3 || 14 || GPIOC1
| |
| − | |-
| |
| − | |15 || MIPICSI_DN3 || 16 || GPIOC2
| |
| − | |-
| |
| − | |17 || MIPICSI_DPCLK || 18 || GPIOC3
| |
| − | |-
| |
| − | |19 || MIPICSI_DNCLK || 20 || DGND
| |
| − | |-
| |
| − | |21 || GPIOB9 || 22 || ADC1
| |
| − | |-
| |
| − | |23 || GPIOB26 || 24 || ADC3
| |
| − | |-
| |
| − | |25 || GPIOC4 || 26 || ADC4
| |
| − | |-
| |
| − | |27 || AliveGPIO3 || 28 || ADC5
| |
| − | |-
| |
| − | |29 || PWREN_SYS || 30 || ADC6
| |
| − | |-
| |
| − | |31 || GPIOC14/PWM2 || 32 || ADC7
| |
| − | |-
| |
| − | |33 || NRESETOUT || 34 || DGND
| |
| − | |}
| |
| − | :Note:
| |
| − | ::#VDD_5V: Supply voltage, range:4.7 ~ 5.6V. We recommend a 5V/1.2A(MAX) power. You can lower the clock to decrease the power consumption. When the clock is lowered by 200MHz the power consumption roughly decreases 0.5W .
| |
| − | ::#BOOT_CS: Boot chip selection. When it is not connected or pulled up the board boots from eMMC otherwise it boots from SD card
| |
| − | ::#NRESETIN: Reset input. Activated when it is low. A reset signal is input to CPU from this pin
| |
| − | ::#NRESETOUT: Reset output. Activated when it is low. CPU's reset signal outputs to this pin.
| |
| − | ::#RTC_BATT: RTC's input, direct connection to a 3V power source. If the CPU board is powered on the RTC seat is powered by 3.3V external power otherwise when the CPU board is not powered on it is powered by the RTC battery.
| |
| − | ::#ADC1~7: CPU internal ADC, 12-bit, 7 channels 1~7, range:0 ~ 1.8V
| |
| − | ::#10/100M Ethernet mode: LAN_MDI1_N/P=RX-/+, LAN_MDI0_N/P=TX-/+, four pins connected to RJ45
| |
| − | ::#10/100/1000M Ethernet mode: LAN_MDI0_N/P~LAN_MDI3N/P, all eight pins connected to RJ45
| |
| − | ::#For more details refer to our carrier board's design:[http://wiki.friendlyarm.com/wiki/index.php/Smart210/4418_SDK Smart210/4418 SDK]
| |
| − | ::#* For more details about the Smart4418 SDK carrier board V1606 refer to [http://wiki.friendlyarm.com/wiki/index.php/Smart4418_SDK Smart4418SDK 1606].
| |
| − | ::#[http://wiki.friendlyarm.com/wiki/images/3/32/Smart4418-1608-Schematic.pdf Smart4418 Schematic in pdf]
| |
| − |
| |
| − | ==Board Dimension==
| |
| − | :[[File:Smart4418-dim.png|500px]]<br>
| |
| − | :For more details refer to the dxf file:[http://wiki.friendlyarm.com/wiki/images/d/df/Smart4418-1512-Dimension%28dxf%29.zip Smart4418-1512-Dimension(dxf).zip]
| |
| − |
| |
| − | ==Notes in Hardware Design==
| |
| − | ===EEPROM===
| |
| − | * The Smart4418 CPU board has an EEPROM(model: 24AA025E48T-I/OT) with a unique MAC. This EEPROM is connected to I2C0 and its address is 0x51 therefore some EEPROM chips cannot be connected to I2C0 which will cause conflicts of addresses.
| |
| − | * In our tests these EEPROM chips cannot be connected to I2C0: 24C04, 24C08 and 24C16. There chips which we tested can be connected to I2C0: 24C01, 24C02 and 24C256
| |
| − | * For more details about EEPROM address issues refer to http://www.onsemi.com/pub_link/Collateral/CAT24C01-D.PDF
| |
| − |
| |
| − | ==Carrier Board==
| |
| − | :[http://wiki.friendlyarm.com/wiki/index.php/Smart4418SDK_Comparison Smart4418SDK Comparison]
| |
| − | :[http://wiki.friendlyarm.com/wiki/index.php/Smart210/4418_SDK Smart210/4418 SDK]
| |
| − |
| |
| − | ==Get Started==
| |
| − | ===Essentials You Need===
| |
| − | Before starting to use your Smart4418 get the following items ready
| |
| − | * Smart4418 CPU board and Smart210/4418 SDK carrier board
| |
| − | * Standard SD card: Class10 or above 8GB SDHC card
| |
| − | * A DC 12V/2A power is a must
| |
| − | * HDMI monitor or LCD
| |
| − | * USB keyboard and mouse
| |
| − | * A host computer running Ubuntu 14.04 64 bit system
| |
| − |
| |
| − | ===Make an Installation SD Card===
| |
| − | ====Boot Smart4418 from SD Card====
| |
| − | Get the following files from here [https://www.mediafire.com/folder/ilkcy37otd7il/NanoPi2Board download link]:<br />
| |
| − | * Get a 8G SDHC card and backup its data if necessary<br/>
| |
| − | <!---
| |
| − | FriendlyARM migrated both Android 5.1 and Android 4.4 to the NanoPC-T2. Android 4.4 includes features that professional users usually need: 4G, Ethernet configuration and etc.
| |
| − | ::{| class="wikitable"
| |
| − | |-
| |
| − | |colspan=2|For LCD or HDMI output use the following files:
| |
| − | |-
| |
| − | |nanopi2-debian-sd4g.img.zip || Debian image files
| |
| − | |-
| |
| − | |nanopi2-android-sd4g.img.zip || Android 5.1 image files
| |
| − | |-
| |
| − | |s5p4418-kitkat-sd4g-20160803.img.zip || Android 4.4 image files
| |
| − | |-
| |
| − | |colspan=2|Flash Utility:
| |
| − | |-
| |
| − | |win32diskimager.rar || Windows utility. Under Linux users can use "dd"
| |
| − | |-
| |
| − | |}
| |
| − | --->
| |
| − | ::{| class="wikitable"
| |
| − | |-
| |
| − | |colspan=2| Image Files
| |
| − | |-
| |
| − | |s5p4418-debian-sd4g-YYYYMMDD.img.zip || Debian image file with X Window
| |
| − | |-
| |
| − | |s5p4418-debian-wifiap-sd4g-YYYYMMDD.img.zip || Debian image file with X Window and WiFi configured as AP
| |
| − | |-
| |
| − | |s5p4418-kitkat-sd4g-YYYYMMDD.img.zip || Android4.4 image file with support for 4G LTE
| |
| − | |-
| |
| − | |s5p4418-android-sd4g-YYYYMMDD.img.zip || Android5.1 image file
| |
| − | |-
| |
| − | |s5p4418-core-qte-sd4g-YYYYMMDD.img.zip || Ubuntu core with Qt Embedded
| |
| − | |-
| |
| − | |colspan=2|Flash Utility:
| |
| − | |-
| |
| − | |win32diskimager.rar || Windows utility. Under Linux users can use "dd"
| |
| − | |-
| |
| − | |}
| |
| − |
| |
| − | * Uncompress these files. Insert an SD card(at least 8G) into a Windows PC and run the win32diskimager utility as administrator，On the utility's main window select your SD card's drive, the wanted image file and click on "write" to start flashing the SD card.
| |
| − | * Insert this card into your Smart4418's boot slot, press and hold the boot key and power on (with a 12V/2A power source). If the PWR LED is on and LED1 is blinking this indicates your Smart4418 has successfully booted.<br/>
| |
| − |
| |
| − | ====Flash Image to Smart4418's eMMC====
| |
| − | * Download eflasher <br />
| |
| − | Get the eflasher utility s5p4418-eflasher-sd8g-xxx-full.img.7z<br />
| |
| − | This package includes a Ubuntu Core, Debian, Android 5 and Android 4.4 image files;<br />
| |
| − | Get the Windows utility: win32diskimager.rar;<br/>
| |
| − | * Flash eflasher Image <br />
| |
| − | Extract the .7z package and you will get .img files.Insert an SD card(at least 8G) into a Windows PC and run the win32diskimager utility as administrator. On the utility's main window select your SD card's drive, the wanted image file and click on "write" to start flashing the SD card.<br/>
| |
| − | If your PC runs Linux you can use the dd command to flash a .img file to the SD card;<br />
| |
| − | * Flash image to eMMC
| |
| − | Insert this card into your Smart4418 SDK carrier board, connect the board to an HDMI monitor or an LCD, press and hold the boot key and power on (with a 12V/2A power source) the board. After your board is powered on you will see multiple OS options and you can select an OS to start installation.
| |
| − | <!---
| |
| − | * Download eflasher <br />
| |
| − | Get the eflasher utility s5p4418-eflasher-sd8g-xxx-full.img.7z and the Windows utility: win32diskimager.rar;<br/>
| |
| − | * Flash eflasher Image <br />
| |
| − | Insert an SD card(at least 8G) into a Windows PC and run the win32diskimager utility as administrator. On the utility's main window select your SD card's drive, the wanted image file and click on "write" to start flashing the SD card.
| |
| − | * Flash image to eMMC
| |
| − | Insert this card into your Smart4418 carrier board, connect the board to an HDMI monitor or an LCD, press and hold the boot key and power on (with a 5V/2A power source) the board. After your board is powered on you will see multiple OS options and you can select an OS to start installation.
| |
| − |
| |
| − | ;Flash image to eMMC with RAW Image
| |
| − | Get the RAW image file: nanopi2-eflasher-sd4g.img.zip and the Windows utility: win32diskimager.rar;
| |
| − | * Flash RAW Image to SD Card <br />
| |
| − | Insert an SD card(at least 4G) into a Windows PC and run the win32diskimager utility as administrator. On the utility's main window select your SD card's drive, the wanted image file and click on "write" to start flashing the SD card
| |
| − | * Prepare RAW image
| |
| − | Go to this link [https://www.mediafire.com/folder/ilkcy37otd7il/NanoPi2Board] to download Android and Debian image files(System-image-files-for-eMMC). After download extract the ".tgz" ball and copy the files to your SD card.
| |
| − | ::{| class="wikitable"
| |
| − | |-
| |
| − | |OS || Image || Files || Copy to...
| |
| − | |-
| |
| − | |Android 5.1 || android-lollipop-images.tgz <br /> android-lollipop-images.tgz.hash.md5
| |
| − | || boot.img <br /> system.img <br /> userdata.img <br /> cache.img <br /> partmap.txt <br />
| |
| − | || images\android
| |
| − | |-
| |
| − | |Android4.4 || android-lollipop-images.tgz <br /> android-lollipop-images.tgz.hash.md5
| |
| − | || boot.img <br /> system.img <br /> userdata.img <br /> cache.img <br /> partmap.txt <br />
| |
| − | || images\android
| |
| − | |-
| |
| − | |Debian (Jessie) || debian-jessie-images.tgz <br />debian-jessie-images.tgz.hash.md5
| |
| − | || boot.img <br />rootfs.img <br />partmap.txt <br />
| |
| − | || images\debian
| |
| − | |-
| |
| − | |}
| |
| − |
| |
| − | * Specify OS
| |
| − | By default the SD card's configuration file "images\FriendlyARM.ini" specifies Android to be flashed to eMMC. If you want to install Debian make the following change:
| |
| − | <syntaxhighlight lang="bash">
| |
| − | OS = Debian
| |
| − | </syntaxhighlight>
| |
| − | "#" is a comment
| |
| − |
| |
| − | * Flash Image to eMMC
| |
| − | Insert this card into your Smart4418 carrier board, connect the board to an HDMI monitor or an LCD, press and hold the boot key and power on (with a 5V/2A power source) the board to start installation. You can watch the whole installation process from the HDMI monitor or LCD. If the following messages pop up it means the installation has succeeded.
| |
| − |
| |
| − | <syntaxhighlight lang="bash">
| |
| − | Android is fused successfully.
| |
| − | All done.
| |
| − | </syntaxhighlight>
| |
| − | After installation is done do "reset" or power off and on the board to boot the board from eMMC.
| |
| − |
| |
| − | ;You can check the LED's status to monitor the installation process too:
| |
| − | ::{| class="wikitable"
| |
| − | |-
| |
| − | |LED Status || Installation Status
| |
| − | |-
| |
| − | |LED1 blinks twice continuously<br /> LED2 off || Power on normal.<br /> If installation doesn't proceed LED1 will keep behaving this way and LED2 will be off
| |
| − | |-
| |
| − | |LED1 and LED2 blink alternatively with each blink for 0.3s || Installation proceeding
| |
| − | |-
| |
| − | |LED1 and LED2 blink alternatively with each blink for 1.2s || Installation succeeded
| |
| − | |-
| |
| − | |LED1 and LED2 blink simultaneously || Installation failed
| |
| − | |-
| |
| − | |}
| |
| − | --->
| |
| − |
| |
| − | ====Make Installation Card under Linux Desktop====
| |
| − | * 1) Insert your SD card into your host PC running Ubuntu and check your SD card's device name
| |
| − | <syntaxhighlight lang="bash">
| |
| − | dmesg | tail
| |
| − | </syntaxhighlight>
| |
| − | Search the messages output by "dmesg" for similar words like "sdc: sdc1 sdc2". If you can find them it means your SD card has been recognized as "/dev/sdc". Or you can check that by commanding "cat /proc/partitions"
| |
| − |
| |
| − | * 2) Downlaod Linux script
| |
| − | <syntaxhighlight lang="bash">
| |
| − | git clone https://github.com/friendlyarm/sd-fuse_nanopi2.git
| |
| − | cd sd-fuse_nanopi2
| |
| − | </syntaxhighlight>
| |
| − |
| |
| − | * 3) Make Android SD Card
| |
| − | <syntaxhighlight lang="bash">
| |
| − | su
| |
| − | ./fusing.sh /dev/sdx
| |
| − | </syntaxhighlight>
| |
| − | (Note: you need to replace "/dev/sdx" with the device name in your system)<br/>
| |
| − | When you run the script for the first time it will prompt you to download an image you have to hit “Y” within 10 seconds otherwise you will miss the download
| |
| − |
| |
| − | * 4) Here is how to make a Debian SD card
| |
| − | <syntaxhighlight lang="bash">
| |
| − | ./fusing.sh /dev/sdx debian
| |
| − | </syntaxhighlight>
| |
| − |
| |
| − | ====Extend Smart4418's SD Card Section====
| |
| − | * When Debian/Ubuntu boots it will automatically extend its SD card's section. On its initial booting the system will extend the root file system and other sections.
| |
| − | * Under Android users need to extend the section by using the following commands:
| |
| − | <syntaxhighlight lang="bash">
| |
| − | sudo umount /dev/sdx?
| |
| − | sudo parted /dev/sdx unit % resizepart 4 100 resizepart 7 100 unit MB print
| |
| − | sudo resize2fs -f /dev/sdx7
| |
| − | </syntaxhighlight>
| |
| − | (Note: you need to replace "/dev/sdx" with the device name in your system)
| |
| − |
| |
| − | ====LCD/HDMI Resolution====
| |
| − | When system boots our uboot will check whether it is connected to an LCD or an HDMI monitor. If it recognizes an LCD it will configure its resolution. Our uboot defaults to the HDMI 720P configuration.<br/>
| |
| − | If you want to modify the LCD resolution you can modify file "arch/arm/plat-s5p4418/nanopi2/lcds.c" in the kernel and recompile it.<br/>
| |
| − | If your Smart4418 is connected to an HDMI monitor and it runs Android it will automatically set the resolution to an appropriate HDMI mode by checking the "EDID". If your Smart4418 is connected an HDMI monitor and it runs Debian by default it will set the resolution to HDMI 720P. If you want to modify the HDMI resolution to 1080P modify your kernel's configuration as explained above.
| |
| − |
| |
| − | ===Update Image Files in SD Card From PC Host===
| |
| − | If you want to make some changes to the image files in your SD card follow steps below otherwise you can skip this section.<br />
| |
| − | Insert your SD card into a host PC running Linux, mount the boot and rootfs sections of the SD card and follow the steps below:<br />
| |
| − | 1) If you want to change your kernel command line parameters you can do it via the fw_setevn utility under "sd-fuse_nanopi2/tools":<br />
| |
| − | Check the current Command Line:
| |
| − | <syntaxhighlight lang="bash">
| |
| − | cd sd-fuse_nanopi2/tools
| |
| − | ./fw_printenv /dev/sdc | grep bootargs
| |
| − | </syntaxhighlight>
| |
| − | Android 5.1.1_r6 starts SELinux. By default it is enforcing. You can change it this way:
| |
| − | <syntaxhighlight lang="bash">
| |
| − | ./fw_setenv /dev/sdc bootargs XXX androidboot.selinux=permissive
| |
| − | </syntaxhighlight>
| |
| − | This sets it to "permissive". The "XXX" stands for the original bootargs' value.<br />
| |
| − |
| |
| − | 2) Update Kernel<br/>
| |
| − | Our customized uboot will check the LCD type when it boots.<br/>
| |
| − | For a non-Android OS If it recognizes an LCD connected to the Smart4418 it will load "uImage" from "boot" otherwise it will load "uImage.hdmi".<br />
| |
| − | For Android it doesn't make any difference what display device is detected. You can use your generated uImage to replace the existing one under "boot".<br/>
| |
| − | For Debian if your generated kernel is for an LCD you need to replace the existing uImage or if your kernel is for an HDMI monitor you need to replace the existing uImage.hdmi.<br/>
| |
| − |
| |
| − | ===Run Android or Debian===
| |
| − | * Insert an SD card with Android/Debian image file into your Smart4418's carrier board, connect the board to an HDMI monitor, switch S2 to "SDBOOT", power on the board the Smart4418 will be booted from the SD card. If you can see the PWR LED on and the LED1 flashing it means your board is working and you will see Android/Debain being loaded on the HDMI monitor.<br/>
| |
| − | 1) If you connect the Smart4418 to an HDMI monitor you need to use a USB mouse and a USB keyboard to operate. If you connect it to an LCD with capacitive touch you can operate directly on the LCD.<br/>
| |
| − | 2）If you want to do kernel development you need to use a serial communication board, ie a PSU-ONECOM board, which will allow you to operate the board via a serial terminal.<br/>
| |
| − | * Here is a setup in which we connect the COM0 on the Smart4418's V1606 SDK carrier board to a PC running Ubuntu and Minicom via a serial cable you will see system messages output to the PC’s minicom terminal
| |
| − | [[File:PSU-ONECOM03.png|frameless|400px|PSU-ONECOM03]]
| |
| − | * Under Debian the password for "root" is "fa"
| |
| − |
| |
| − | ===Login Debian via VNC or SSH===
| |
| − | If your Smart4418 is not connected to a display device and your board runs the "-wifiap.img" image you can login to your Smart4418's nanopi2-wifiap(the default password is "123456789") via a mobile phone. You can download and install a "VNC Viewer" from [http://www.realvnc.com/download/ here] on mobile phone and login to the Smart4418 via VNC. Its default password is "fa123456". Here is a screenshot which shows how it looks like when users login to the Smart4418 from an iPhone via VNC:<br/>
| |
| − | [[File:iphone6-vnc-nanopi2.png|frameless|400px|VNC to NanoPi2]]
| |
| − | <br />
| |
| − | You can login via "SSH -l root 192.168.8.1" too and the default password for "root" is "fa"<br/>
| |
| − | <br />
| |
| − | To make SSH session run faster turn off the WiFi's power saving mode by using the following command:
| |
| − | <syntaxhighlight lang="bash">
| |
| − | iwconfig wlan0 power off
| |
| − | </syntaxhighlight>
| |
| − |
| |
| − | ==Working with Debian==
| |
| − | ===Ethernet Connection===
| |
| − | * If the Smart4418 is connected to a network via Ethernet before it is powered on, it will automatically obtain an IP after it is powered up.
| |
| − |
| |
| − | ===Wireless Connection===
| |
| − | <!---
| |
| − | ;The following section only applies to the NanoPC-T2 which is connected to an HDMI monitor or an LCD:
| |
| − | * When the board runs Debian after it is fully loaded click on the network icon on the GUI. It will automatically search for nearby WiFi sources. Select a source from the list, click on its "Properties", type in its password, save, close and then "Connect".<br/><br/>
| |
| − | ;The following section only applies to the NanoPC-T2 which is not connected to any display device(ie running "-wifiap.img"):<br/>
| |
| − | By default the system's WiFi AP mode is on therefore it cannot search and connect to a wireless router. You need to turn off the WiFi AP mode by following the instructions below:
| |
| − | Firstly set up the WiFi router you expect to connect to:<br/>
| |
| − | Login to the NanoPC-T2 via SSH. Check the WiFi device by running the following commands. Those starting with "wlan" are WiFi devices:
| |
| − | <syntaxhighlight lang="bash">
| |
| − | ifconfig -a
| |
| − | </syntaxhighlight>
| |
| − | By default "wlan0" is the Wifi device. You need to create a configuration file with the same name under "/etc/network/interfaces.d/". For instance you can create a "wlan0" file:
| |
| − | <syntaxhighlight lang="bash">
| |
| − | vi /etc/network/interfaces.d/wlan0
| |
| − | </syntaxhighlight>
| |
| − | Here is the wlan0's content:
| |
| − | <syntaxhighlight lang="bash">
| |
| − | auto wlan0
| |
| − | iface wlan0 inet dhcp
| |
| − | wpa-ssid YourWiFiESSID
| |
| − | wpa-ap-scan 1
| |
| − | wpa-psk YourWiFiPassword
| |
| − | </syntaxhighlight>
| |
| − | The "YourWiFiESSID" and "YourWiFiPassword" need to be replaced with your actual ESSID and password.<br /><br />
| |
| − | If your WiFi password has special characters or you don't want your password saved as plain text you can use "wpa_passphrase" to generate a psk for your WiFi password. Here is how you can do it:<br/>
| |
| − | <syntaxhighlight lang="bash">
| |
| − | wpa_passphrase YourWiFiESSID
| |
| − | </syntaxhighlight>
| |
| − | Following the prompt type in your password and you will get some code in the following format. The string after "psk=" is your new password:
| |
| − | <syntaxhighlight lang="bash">
| |
| − | network={
| |
| − | ssid="YourWiFiESSID"
| |
| − | #psk="YourWiFiPassword"
| |
| − | psk=1b66ca678d6f439f7360686ff5eeb7519cdc44b76a40d96515e4eb807a6d408b
| |
| − | }
| |
| − | </syntaxhighlight>
| |
| − |
| |
| − | Now you can replace the existing password in the wlan0 file with the new one:
| |
| − | <syntaxhighlight lang="bash">
| |
| − | auto wlan0
| |
| − | iface wlan0 inet dhcp
| |
| − | wpa-ssid YourWiFiESSID
| |
| − | wpa-ap-scan 1
| |
| − | wpa-psk 1b66ca678d6f439f7360686ff5eeb7519cdc44b76a40d96515e4eb807a6d408b
| |
| − | </syntaxhighlight>
| |
| − | Next turn off the AP mode. You need to do this as root. Run the following commands and your system will be rebooted. After your system is rebooted it will automatically connect to the WiFi router you set up in your first step:
| |
| − | <syntaxhighlight lang="bash">
| |
| − | su
| |
| − | turn-wifi-into-apmode no
| |
| − | </syntaxhighlight>
| |
| − | --->
| |
| − | Open the file /etc/wpa_supplicant/wpa_supplicant.conf and append the following lines:
| |
| − | <syntaxhighlight lang="bash">
| |
| − | network={
| |
| − | ssid="YourWiFiESSID"
| |
| − | psk="YourWiFiPassword"
| |
| − | }
| |
| − | </syntaxhighlight>
| |
| − | The "YourWiFiESSID" and "YourWiFiPassword" need to be replaced with your actual ESSID and password.<br />
| |
| − | Save, exit and run the following commands to connect to a WiFi:<br />
| |
| − | <syntaxhighlight lang="bash">
| |
| − | ifdown wlan0
| |
| − | ifup wlan0
| |
| − | </syntaxhighlight>
| |
| − |
| |
| − | If your WiFi password has special characters or you don't want your password saved as plain text you can use "wpa_passphrase" to generate a psk for your WiFi password. Here is how you can do it:<br />
| |
| − | <syntaxhighlight lang="bash">
| |
| − | wpa_passphrase YourWiFiESSID
| |
| − | </syntaxhighlight>
| |
| − | Following the prompt type in your password and open the file /etc/wpa_supplicant/wpa_supplicant.conf you will find that your password has been changed and your can delete your plain text password.
| |
| − |
| |
| − | If your AP mode is turned on you need to turn it off. You can do it by using the following commands:
| |
| − | <syntaxhighlight lang="bash">
| |
| − | su
| |
| − | turn-wifi-into-apmode no
| |
| − | </syntaxhighlight>
| |
| − |
| |
| − | ===Setup Wi-Fi AP===
| |
| − | You can follow the steps below to setup Wi-Fi AP:<br/>
| |
| − | <syntaxhighlight lang="bash">
| |
| − | turn-wifi-into-apmode yes
| |
| − | </syntaxhighlight>
| |
| − | Reboot the system as prompted. By default the AP's name is "nanopi2-wifiap" and the password is 123456789.<br/>
| |
| − | <br />
| |
| − | Now you are able to find the "nanopi2-wifiap" from a host PC and connect to it. If the connection is successful you will be able to SSH to this Smart4418 at "192.168.8.1":
| |
| − | <syntaxhighlight lang="bash">
| |
| − | ssh root@192.168.8.1
| |
| − | </syntaxhighlight>
| |
| − | The password for it is "fa".<br/>
| |
| − | <br/>
| |
| − | To make SSH run faster turn off the WiFi's power saving mode by using the following command:
| |
| − | <syntaxhighlight lang="bash">
| |
| − | iwconfig wlan0 power off
| |
| − | </syntaxhighlight>
| |
| − | You can check the WiFi mode via the following command:<br />
| |
| − | <syntaxhighlight lang="bash">
| |
| − | cat /sys/module/bcmdhd/parameters/op_mode
| |
| − | </syntaxhighlight>
| |
| − | If the result is "2" it means it is currently working as a WiFi AP.If you want to switch back to the Station mode you can do it this way:<br />
| |
| − | <syntaxhighlight lang="bash">
| |
| − | turn-wifi-into-apmode no
| |
| − | </syntaxhighlight>
| |
| − |
| |
| − | ===Bluetooth===
| |
| − | Here are the steps to transfer a file from Smart4418 to a mobile phone. Run the following command to search a surrounding Bluetooth device:<br />
| |
| − | <syntaxhighlight lang="bash">
| |
| − | hcitool scan
| |
| − | </syntaxhighlight>
| |
| − | <br />
| |
| − | In our example a mobile phone was detected and the following messages were listed:<br />
| |
| − | Scanning ...<br />
| |
| − | 38:BC:1A:B1:7E:DD MEIZU MX4<br />
| |
| − | <br />
| |
| − | These messages indicated that a MEIZU MX4 mobile phone was detected. We then checked the Bluetooth services this phone supported with its MAC address presented in front of its device name<br />
| |
| − | <syntaxhighlight lang="bash">
| |
| − | sdptool browse 38:BC:1A:B1:7E:DD
| |
| − | </syntaxhighlight>
| |
| − | Note: you need to use your device's name and its MAC address when you run these commands.<br /><br />
| |
| − | The command listed all the services the phone supported. We needed the "OBEX Object Push" service which is for file transfers.<br />
| |
| − | Service Name: OBEX Object Push<br />
| |
| − | Service RecHandle: 0x1000b<br />
| |
| − | Service Class ID List:<br />
| |
| − | "OBEX Object Push" (0x1105)<br />
| |
| − | Protocol Descriptor List:<br />
| |
| − | "L2CAP" (0x0100)<br />
| |
| − | "RFCOMM" (0x0003)<br />
| |
| − | Channel: 25<br />
| |
| − | "OBEX" (0x0008)<br />
| |
| − | Profile Descriptor List:<br />
| |
| − | "OBEX Object Push" (0x1105)<br />
| |
| − | Version: 0x0100<br />
| |
| − | <br />
| |
| − | From the above messages we could get the channel number 25 for the "OBEX Object Push" service. We input this number to the "ussp-push" by running the following command:
| |
| − | <syntaxhighlight lang="bash">
| |
| − | ussp-push 38:BC:1A:B1:7E:DD@25 example.jpg example.jpg
| |
| − | </syntaxhighlight>
| |
| − | Note: you need to use your device's name, its MAC address and channel number when you run these commands.<br /><br />
| |
| − | Usually after the above commands are run a popup window will show on the phone that communicates with Smart4418 and you can start file transfers.<br />
| |
| − | <br />
| |
| − | Common Issues:<br />
| |
| − | 1) If Smart4418 cannot find a Bluetooth device you can try this command to restart its Bluetooth:<br />
| |
| − | <syntaxhighlight lang="bash">
| |
| − | rfkill unblock 0
| |
| − | </syntaxhighlight>
| |
| − | 2) If any of these commands is not installed you can try this command to install it:<br />
| |
| − | <syntaxhighlight lang="bash">
| |
| − | apt-get install bluetooth bluez obexftp openobex-apps python-gobject ussp-push
| |
| − | </syntaxhighlight>
| |
| − |
| |
| − | <!---
| |
| − | Click on the bluetooth icon on the GUI a menu will pop up:<br/>
| |
| − | Make discoverable... enables the Smart4418 to be searched for by nearby bluetooth devices;<br/>
| |
| − | Devices... opens a search window and searches for nearby bluetooth devices(Note: the "Make discoverable" property needs to be enabled on those nearby devices);<br/>
| |
| − | Send Files to Device...enables the Smart4418 to send files to another bluetooth device which is paired to the Smart4418.<br/>
| |
| − | --->
| |
| − |
| |
| − | ===Install Debian Packages===
| |
| − | We provide a Debian Jessie image. You can install Jessie's packages by commanding "apt-get". If this is your first installation you need to update the package list by running the following command:
| |
| − | <syntaxhighlight lang="bash">
| |
| − | apt-get update
| |
| − | </syntaxhighlight>
| |
| − | You can install your preferred packages. For example if you want to install an FTP server you can do this:
| |
| − | <syntaxhighlight lang="bash">
| |
| − | apt-get install vsftpd
| |
| − | </syntaxhighlight>
| |
| − | Note: you can change your download server by editting "/etc/apt/sources.list". You can get a complete server list from [http://www.debian.org/mirror/list]. You need to select the one with "armhf".
| |
| − |
| |
| − | ==Make Your Own OS Image==
| |
| − |
| |
| − | ===Install Cross Compiler===
| |
| − | Download the compiler package:
| |
| − | <syntaxhighlight lang="bash">
| |
| − | git clone https://github.com/friendlyarm/prebuilts.git
| |
| − | sudo mkdir -p /opt/FriendlyARM/toolchain
| |
| − | sudo tar xf prebuilts/gcc-x64/arm-cortexa9-linux-gnueabihf-4.9.3.tar.xz -C /opt/FriendlyARM/toolchain/
| |
| − | </syntaxhighlight>
| |
| − |
| |
| − | Then add the compiler's directory to "PATH" by appending the following lines in "~/.bashrc":
| |
| − | <syntaxhighlight lang="bash">
| |
| − | export PATH=/opt/FriendlyARM/toolchain/4.9.3/bin:$PATH
| |
| − | export GCC_COLORS=auto
| |
| − | </syntaxhighlight>
| |
| − |
| |
| − | Execute "~/.bashrc" to make the changes into effect. Note that there is a space after the first ".":
| |
| − | <syntaxhighlight lang="bash">
| |
| − | . ~/.bashrc
| |
| − | </syntaxhighlight>
| |
| − |
| |
| − | This compiler is a 64-bit one therefore it cannot be run on a 32-bit Linux. After the compiler is installed you can verify it by running the following commands:
| |
| − | <syntaxhighlight lang="bash">
| |
| − | arm-linux-gcc -v
| |
| − | Using built-in specs.
| |
| − | COLLECT_GCC=arm-linux-gcc
| |
| − | COLLECT_LTO_WRAPPER=/opt/FriendlyARM/toolchain/4.9.3/libexec/gcc/arm-cortexa9-linux-gnueabihf/4.9.3/lto-wrapper
| |
| − | Target: arm-cortexa9-linux-gnueabihf
| |
| − | Configured with: /work/toolchain/build/src/gcc-4.9.3/configure --build=x86_64-build_pc-linux-gnu
| |
| − | --host=x86_64-build_pc-linux-gnu --target=arm-cortexa9-linux-gnueabihf --prefix=/opt/FriendlyARM/toolchain/4.9.3
| |
| − | --with-sysroot=/opt/FriendlyARM/toolchain/4.9.3/arm-cortexa9-linux-gnueabihf/sys-root --enable-languages=c,c++
| |
| − | --with-arch=armv7-a --with-tune=cortex-a9 --with-fpu=vfpv3 --with-float=hard
| |
| − | ...
| |
| − | Thread model: posix
| |
| − | gcc version 4.9.3 (ctng-1.21.0-229g-FA)
| |
| − | </syntaxhighlight>
| |
| − |
| |
| − | ===Compile U-Boot===
| |
| − | Download the U-Boot source code and compile it. Note the github's branch is nanopi2-lollipop-mr1:
| |
| − | <syntaxhighlight lang="bash">
| |
| − | git clone https://github.com/friendlyarm/uboot_nanopi2.git
| |
| − | cd uboot_nanopi2
| |
| − | git checkout nanopi2-lollipop-mr1
| |
| − | make s5p4418_nanopi2_config
| |
| − | make CROSS_COMPILE=arm-linux-
| |
| − | </syntaxhighlight>
| |
| − |
| |
| − | After your compilation succeeds a u-boot.bin will be generated. If you want to test it flash it to your installation SD card via fastboot. Here is how you can do it<br />
| |
| − | 1) On your host PC run "sudo apt-get install android-tools-fastboot" to install the fastboot utility;<br />
| |
| − | 2) Connect your Smart4418 to your host PC via a serial cable (e.g. PSU-ONECOME). Press the enter key within two seconds right after you power on your Smart4418 and you will enter uboot's command line mode;<br />
| |
| − | 3) After type in "fastboot" and press "enter" you will enter the fastboot mode;<br />
| |
| − | 4) Connect your Smart4418 to this host PC via a microUSB cable and type in the following command to flash the u-boot.bin you generated:<br/>
| |
| − | <syntaxhighlight lang="bash">
| |
| − | fastboot flash bootloader u-boot.bin
| |
| − | </syntaxhighlight>
| |
| − | <br />
| |
| − | Warning: you cannot update this SD card by commanding "dd". This command which will cause trouble when booting the Smart4418.<br />
| |
| − |
| |
| − | ===Prepare mkimage===
| |
| − | You need the mkimage utility to compile a U-Boot source code package. Make sure this utility works well on your host before you start compiling a uImage.<br/>
| |
| − | You can install this utility by either commanding "sudo apt-get install u-boot-tools" or following the commands below:
| |
| − | <syntaxhighlight lang="bash">
| |
| − | cd uboot_nanopi2
| |
| − | make CROSS_COMPILE=arm-linux- tools
| |
| − | sudo mkdir -p /usr/local/sbin && sudo cp -v tools/mkimage /usr/local/sbin
| |
| − | </syntaxhighlight>
| |
| − |
| |
| − | ===Compile Linux Kernel===
| |
| − | ====Compile Kernel====
| |
| − | * Download Kernel Source Code
| |
| − | <syntaxhighlight lang="bash">
| |
| − | git clone https://github.com/friendlyarm/linux-3.4.y.git
| |
| − | cd linux-3.4.y
| |
| − | git checkout nanopi2-lollipop-mr1
| |
| − | </syntaxhighlight>
| |
| − | The Smart4418's kernel source code lies in the "nanopi2-lollipop-mr1" branch.
| |
| − | * Compile Android Kernel
| |
| − | <syntaxhighlight lang="bash">
| |
| − | make nanopi2_android_defconfig
| |
| − | touch .scmversion
| |
| − | make uImage
| |
| − | </syntaxhighlight>
| |
| − | * Compile Debian Kernel
| |
| − | <syntaxhighlight lang="bash">
| |
| − | make nanopi2_linux_defconfig
| |
| − | touch .scmversion
| |
| − | make uImage
| |
| − | </syntaxhighlight>
| |
| − | After your compilation succeeds a uImage will be generated in the "arch/arm/boot/uImage" directory. This kernel is for HDMI 720P. You can use it to replace the existing uImage.hdmi.<br/>
| |
| − | If you want to generate a kernel for HDMI 1080P you can do it this way
| |
| − | <syntaxhighlight lang="bash">
| |
| − | touch .scmversion
| |
| − | make nanopi2_linux_defconfig
| |
| − | make menuconfig
| |
| − | Device Drivers -->
| |
| − | Graphics support -->
| |
| − | Nexell Graphics -->
| |
| − | [ ] LCD
| |
| − | [*] HDMI
| |
| − | (0) Display In [0=Display 0, 1=Display 1]
| |
| − | Resolution (1920 * 1080p) --->
| |
| − | make uImage
| |
| − | </syntaxhighlight>
| |
| − | After your compilation succeeds a uImage will be generated for HDMI 1080P. You can use it to replace the existing uImage
| |
| − |
| |
| − | ====Compile Kernel Modules====
| |
| − | Android contains kernel modules which are in the "/lib/modules" directory in the system section. If you want to add your own modules to the kernel or you changed your kernel configurations you need to recompile these new modules.<br/>
| |
| − | Compile Original Kernel Modules:
| |
| − | <syntaxhighlight lang="bash">
| |
| − | cd linux-3.4.y
| |
| − | make CROSS_COMPILE=arm-linux- modules
| |
| − | </syntaxhighlight>
| |
| − | Here we have two new modules and we can compile them by following the commands below:
| |
| − | <syntaxhighlight lang="bash">
| |
| − | cd /opt/FriendlyARM/s5p4418/android
| |
| − | ./vendor/friendly-arm/build/common/build-modules.sh
| |
| − | </syntaxhighlight>
| |
| − | The "/opt/FriendlyARM/s5p4418/android" directory points to the top directory of Android source code. You can get more details by specifying option "-h".<br/>
| |
| − | After your compilation succeeds new modules will be generated
| |
| − |
| |
| − | ===Compile Android===
| |
| − | * Install Cross Compiler
| |
| − | Install 64 bit Ubuntu 14.04 on your PC host.
| |
| − | <syntaxhighlight lang="bash">
| |
| − | sudo apt-get install bison g++-multilib git gperf libxml2-utils make python-networkx zip
| |
| − | sudo apt-get install flex libncurses5-dev zlib1g-dev gawk minicom
| |
| − | </syntaxhighlight>
| |
| − | For more details refer to https://source.android.com/source/initializing.html 。
| |
| − |
| |
| − | * Download Source Code(Android 5.1)
| |
| − | You need to use repo to get the Android source code. Refer to https://source.android.com/source/downloading.html 。
| |
| − | <syntaxhighlight lang="bash">
| |
| − | mkdir android && cd android
| |
| − | repo init -u https://github.com/friendlyarm/android_manifest.git -b nanopi2-lollipop-mr1
| |
| − | repo sync
| |
| − | </syntaxhighlight>
| |
| − | The "android" directory is the working directory.<br />
| |
| − |
| |
| − | If you want to try Android4.4's source code you can run the following commands:
| |
| − | <syntaxhighlight lang="bash">
| |
| − | mkdir android && cd android
| |
| − | repo init -u https://github.com/friendlyarm/android_manifest.git -b nanopi2-kitkat
| |
| − | repo sync
| |
| − | </syntaxhighlight>
| |
| − | Option "-b" specifies a branch
| |
| − |
| |
| − | * Compile System Package
| |
| − | <syntaxhighlight lang="bash">
| |
| − | source build/envsetup.sh
| |
| − | lunch aosp_nanopi2-userdebug
| |
| − | make -j8
| |
| − | </syntaxhighlight>
| |
| − | After your compilation succeeds the following files will be generated in the "out/target/product/nanopi2/" directory.
| |
| − | ::{| class="wikitable"
| |
| − | |-
| |
| − | |filename || partition || Description
| |
| − | |-
| |
| − | |boot.img || boot || -
| |
| − | |-
| |
| − | |cache.img || cache || -
| |
| − | |-
| |
| − | |userdata.img || userdata || -
| |
| − | |-
| |
| − | |system.img || system || -
| |
| − | |-
| |
| − | |partmap.txt || - || partition description file
| |
| − | |-
| |
| − | |}
| |
| − |
| |
| − | * Flash Image to eMMC
| |
| − | After compiling Android successfully you can flash it to eMMC with either of the following methods<br />
| |
| − | 1) fastboot: right after the Smart4418 is booted from eMMC press any key to enter the uboot commandline mode and type in "fastboot"<br />
| |
| − | Connect your board to a host PC running Ubuntu with a USB cable and run the following commands in the PC's terminal:
| |
| − | <syntaxhighlight lang="bash">
| |
| − | cd out/target/product/nanopi2
| |
| − | sudo fastboot flash boot boot.img
| |
| − | sudo fastboot flash cache cache.img
| |
| − | sudo fastboot flash userdata userdata.img
| |
| − | sudo fastboot flash system system.img
| |
| − | sudo fastboot reboot
| |
| − | </syntaxhighlight>
| |
| − | 2) Use an SD Card<br />
| |
| − | Copy these files: boot.img, cache.img, userdata.img, system.img, partmap.txt from the out/target/product/nanopi2 directory to your installation SD card's images/android directory and you can use this SD card to flash Android to eMMC<br />
| |
| − |
| |
| − | ==Connect Smart4418 to External Modules==
| |
| − | ===Connect Smart4418 to 4G Module===
| |
| − | * The Smart4418 can work with some 4G modules under Android 4.4. After you connect a 4G module (e.g. ME909u-521 which supports FDD-LTE) to a Smart4418 power on the board the 4G module will be activated automatically
| |
| − | [[File:4G Model-nanopc-t3.png|frameless|500px|4G Model]]
| |
| − |
| |
| − | ===Connect Smart4418 to USB Camera(FA-CAM202)===
| |
| − | * In this use case the Smart4418 runs Debian. If you connect your Smart4418 to our LCD or an HDMI monitor after Debain is fully loaded click on "other"-->"xawtv9" on the left bottom of the GUI and the USB Camera application will be started. After enter "welcome to xawtv！" click on "OK" to start exploring.
| |
| − | [[File:USB-camera-nanopi2.png|frameless|500px|USB camera]]
| |
| − | [[File:USB-camera-Smart4418-01.png|frameless|500px|USB camera-01]]
| |
| − | ===Connect Smart4418 to CMOS 5M-Pixel Camera===
| |
| − | <!---
| |
| − | * In this use case the Smart4418 runs Android5.1. If you connect your Smart4418 to our LCD or an HDMI monitor after Debain is fully loaded click on the "Camera" icon the application will be started
| |
| − | [[File:CMOS-camera-Smart4418.png|frameless|500px|CMOS camera]]
| |
| − | --->
| |
| − | For more details about the CAM500A camera refer to [http://wiki.friendlyarm.com/wiki/index.php/Matrix_-_CAM500A]<br/>
| |
| − | *If your Smart4418 runs Android5.1 and it is connected to our LCD or an HDMI monitor after Android is fully loaded click on the "Camera" icon and the application will be started. You can take pictures or record videos
| |
| − | [[File:CMOS-camera-nanopc-t2.png|frameless|500px|CMOS camera]]
| |
| − |
| |
| − | *Under Debian/Ubuntu a camera utility "nanocams" is available for previewing 40 frames and picture taking. You can try it by following the commands below
| |
| − | <syntaxhighlight lang="bash">
| |
| − | sudo nanocams -p 1 -n 40 -c 4 -o IMG001.jpg
| |
| − | </syntaxhighlight>
| |
| − | For more details about the usage of the nanocams run "nanocams -h".
| |
| − | You can get its source code from our git hub:
| |
| − | <syntaxhighlight lang="bash">
| |
| − | git clone https://github.com/friendlyarm/nexell_linux_platform.git
| |
| − | </syntaxhighlight>
| |
| − |
| |
| − | ===Use OpenCV to Access USB Camera===
| |
| − | * The full name of "OpenCV" is Open Source Computer Vision Library and it is a cross platform vision library.
| |
| − | * When the Smart4418 runs Debian users can use OpenCV APIs to access a USB Camera device.<br>
| |
| − | 1. Here is a guideline on how to use OpenCV with C++ on the Smart4418:
| |
| − | * Firstly you need to make sure your Smart4418 is connected to the internet. Login to your Smart4418 via a serial terminal or SSH. After login type your username(root) and password(fa):
| |
| − | * Run the following commands:<br>
| |
| − | <syntaxhighlight lang="bash">
| |
| − | apt-get update
| |
| − | apt-get install libcv-dev libopencv-dev
| |
| − | </syntaxhighlight>
| |
| − |
| |
| − | 2. Make sure your USB camera works with the Smart4418. You can test your camera with Smart4418's camera utility.<br>
| |
| − | 3. Check your camera device:
| |
| − | <syntaxhighlight lang="bash">
| |
| − | ls /dev/video*
| |
| − | </syntaxhighlight>
| |
| − | * Note:in our test case video0 was the USB camera device
| |
| − |
| |
| − | 4. OpenCV's code sample(official code in C++) is under /home/fa/Documents/opencv-demo. Compile the code sample with the following commands:
| |
| − | <syntaxhighlight lang="bash">
| |
| − | cd /home/fa/Documents/opencv-demo
| |
| − | make
| |
| − | </syntaxhighlight>
| |
| − | After it is compiled successfully a "demo" executable will be generated<br/>
| |
| − |
| |
| − | 6. Connect Smart4418 to USB Keyboard & Run the Following Command
| |
| − | <syntaxhighlight lang="bash">
| |
| − | ./demo
| |
| − | </syntaxhighlight>
| |
| − |
| |
| − | This is what you expect to observe:
| |
| − |
| |
| − | ==More OS Support==
| |
| − | ===Ubuntu-Core with Qt-Embedded===
| |
| − | Ubuntu Core with Qt-Embedded is a light Linux system without X-windows. It uses the Qt-Embedded's GUI and is popular in industrial and enterprise applications.
| |
| − |
| |
| − | Besides the regular Ubuntu core's features our Ubuntu-Core has the following additional features:
| |
| − | * it supports our LCDs with both capacitive touch and resistive touch(S700, X710, S70)
| |
| − | * it supports WiFi
| |
| − | * it supports Ethernet
| |
| − | * it supports Bluetooth and has been installed with bluez utilities
| |
| − | * it supports audio playing
| |
| − |
| |
| − | For more details refer to [http://wiki.friendlyarm.com/wiki/index.php/Ubuntu_Core_with_Qt-Embedded Ubuntu Core with Qt-Embedded].<br>
| |
| − |
| |
| − | ====Flash Ubuntu-Core with Qt-Embedded to eMMC====
| |
| − | 1. Make an installation SD card with the win32 utility;<br/>
| |
| − | 2. Insert this SD card to a host PC and copy the UbuntuCore image (in our example it was "ubuntu_core.img") and 2nboot file(in our example it was "2ndboot.bin.emmc") to it;<br />
| |
| − | 2nboot can be downloaded from: https://github.com/friendlyarm/sd-fuse_s5p6818/tree/master/prebuilt <br />
| |
| − | 3. Run the following commands to flash the image file to your board's eMMC:
| |
| − | <syntaxhighlight lang="bash">
| |
| − | dd if=ubuntu_core.img of= /dev/mmcblk1
| |
| − | </syntaxhighlight>
| |
| − | 4. Flash the 2nboo file to the eMMC:
| |
| − | <syntaxhighlight lang="bash">
| |
| − | dd if=2ndboot.bin.emmc of=/dev/mmcblk1 bs=512 seek=1
| |
| − | </syntaxhighlight>
| |
| − |
| |
| − | ===Ubuntu-Mate===
| |
| − | Ubuntu-Mate is a Ubuntu variant and its GUI is Mate-desktop. You can log in via SSH when you connect the Smart4418 to an LCD or HDMI<br>
| |
| − | FriendlyARM doesn't provide technical support for it
| |
| − | * Go to this link [https://www.mediafire.com/folder/28mhgfosn62d5/Ubuntu-Mata download link] to download the image files
| |
| − | * Uncompress it and flash the image file to a TF card with win32diskimager under Windows
| |
| − | * After it is done you can boot your Smart4418 with this card
| |
| − | * Login name: "root" or "fa", Password: fa
| |
| − |
| |
| − | ===Kali===
| |
| − | * Go to this link [https://www.mediafire.com/folder/nbuvkg07p74er/Kali] to download the image files;
| |
| − | * Prepare an 8G High Speed MicroSD card, insert it to a Linux host and do "sudo fdisk -l" to check its device name, i.e. "/dev/sd*".
| |
| − | * Copy the image files to the card by running the following commands as root:
| |
| − | <syntaxhighlight lang="bash">
| |
| − | xzcat kali-2.0-nanopi2.img.xz | dd of=<YOURDEVICE> bs=1m
| |
| − | </syntaxhighlight>
| |
| − | * After it is done you can boot your Smart4418 with this card.
| |
| − | Note: this is offered by Kali and FriendlyARM doesn't provide technical support for it.
| |
| − |
| |
| − | ===Deepin15 ARM===
| |
| − | * Go to this link [https://www.mediafire.com/folder/rh97bk9o3rpiv/deepin15] to download the image files
| |
| − | * Uncompress the file and you will get a 16g.img file which is the image file for MicroSD card.
| |
| − | <syntaxhighlight lang="bash">
| |
| − | tar -xf deepin15_nanopi2_armhf_16g.tar.gz
| |
| − | </syntaxhighlight>
| |
| − | * Prepare an 16G High Speed SD card, insert it into a Linux host and do "sudo fdisk -l" to check its device name, i.e. "/dev/sd*"
| |
| − | * Flash the image files to the card by running the following command as root(in our case our card was recognized as "/dev/sdc"):
| |
| − | <syntaxhighlight lang="bash">
| |
| − | sudo dd if=16g.img of=/dev/sdc
| |
| − | </syntaxhighlight>
| |
| − | This process takes a while which can be up to one hour
| |
| − | * After it is done you can boot your Smart4418 with this card
| |
| − |
| |
| − | Notes:<br>
| |
| − | 1. The password for login name "deepin" is "deepin". The password for login name "root" is "admin".<br>
| |
| − | 2. The initial booting of Deepin15 takes a relative long time for it generates some configuration files.<br>
| |
| − | 3. If WiFi is activated in your system booting might take longer. In this case wait for the sound and wifi icons on the right bottom of the GUI to appear before you start any action.<br>
| |
| − | <syntaxhighlight lang="bash">
| |
| − | ARM code: http://packages.deepin.com/armhf/
| |
| − | NanoPC-T2 Image: http://cdimage.deepin.com/armhf/15/beta1.0/
| |
| − | NanoPC-T2 Image Installation Instruction; http://bbs.deepin.org/forum.php?mod=viewthread&tid=36670
| |
| − | Forum for Migrating Deepin15 to ARM: http://bbs.deepin.org/
| |
| − | </syntaxhighlight>
| |
| − | Note: this is offered by the Deepin15 team and FriendlyARM doesn't provide technical support for it.
| |
| − |
| |
| − | ===Android-Remixos===
| |
| − | Go to this link [http://pan.baidu.com/s/1qYCbqDu] to download the image files;<br>
| |
| − | * Untar the image ball:
| |
| − | <syntaxhighlight lang="bash">
| |
| − | tar -xf nanopi2-android-remixos-sd4g.tar
| |
| − | </syntaxhighlight>
| |
| − | * Use the win32diskimager utility to flash the image to an SD card.
| |
| − | It supports HDMI and LCD output and works with all existing FriendlyARM 4418 boards.<br>
| |
| − | Note: this is offered by Remix team and FriendlyARM doesn't provide technical support for it.<br>
| |
| − |
| |
| − |
| |
| − | <!---
| |
| − | ==Extend Smart4418's SD Card Section==
| |
| − | ===Debian===
| |
| − | * Run the following commands on a host PC's terminal:
| |
| − | <syntaxhighlight lang="bash">
| |
| − | sudo umount /dev/sdx?
| |
| − | sudo parted /dev/sdx unit % resizepart 2 100 unit MB print
| |
| − | sudo resize2fs -f /dev/sdx2
| |
| − | </syntaxhighlight>
| |
| − | ===Android===
| |
| − | * Run the following commands on a host PC's terminal:
| |
| − | <syntaxhighlight lang="bash">
| |
| − | sudo umount /dev/sdx?
| |
| − | sudo parted /dev/sdx unit % resizepart 4 100 resizepart 7 100 unit MB print
| |
| − | sudo resize2fs -f /dev/sdx7
| |
| − | </syntaxhighlight>
| |
| − | (Note: you need to replace "/dev/sdx" with the device name in your system)
| |
| − | --->
| |
| − |
| |
| − | ==Resources==
| |
| − | :[http://wiki.friendlyarm.com/wiki/images/0/0b/Smart4418-1512-Schematic.pdf Smart4418 1512 Schematic in PDF]
| |
| − | :[http://wiki.friendlyarm.com/wiki/images/3/32/Smart4418-1608-Schematic.pdf Smart4418 1608 Schematic in PDF]
| |
| − | :[http://wiki.friendlyarm.com/wiki/images/d/df/Smart4418-1512-Dimension%28dxf%29.zip dimension (Smart4418-1512-Dimension(dxf).zip)]
| |
| − | * 《创客秘籍》[http://wiki.friendlyarm.com/wiki/index.php/File:%E5%88%9B%E5%AE%A2%E7%A7%98%E7%B1%8D.pdf Hacker's Book in Chinese by FriendlyARM]
| |
| − | * 《创客秘籍-02》[http://pan.baidu.com/s/1hrDu9es Hacker's Book-02 in Chinese by FriendlyARM]
| |
| − | * 《创客秘籍-03》[http://wiki.friendlyarm.com/wiki/index.php/File:%E5%88%9B%E5%AE%A2%E7%A7%98%E7%B1%8D-03.pdf Hacker's Book-03 in Chinese by FriendlyARM]
| |
| − | * SEC_Users_Manual_S5P4418_Users_Manual_Preliminary[http://wiki.friendlyarm.com/wiki/images/3/3d/SEC_Users_Manual_S5P4418_Users_Manual_Preliminary_Ver.0.10.pdf]
| |
| − |
| |
| − | ==Update Log==
| |
| − | ===March-09-2016===
| |
| − | * Released English version
| |
| − |
| |
| − | ===April-10-2016===
| |
| − | * Corrected expression errors
| |
| − |
| |
| − | ===Sep-8-2016===
| |
| − | * Updated sections 8.2, 9.5 and 12
| |
| − | * Added section 10.1 and 11
| |
| − |
| |
| − | ===Sep-27-2016===
| |
| − | * Updated sections 7.2.2 and 10.3
| |
| − |
| |
| − | ===Dec-8-2016===
| |
| − | * Updated sections 7.1, 7.2, 7.4, 8.4, 9.5 and 10.1
| |
| − | * add Smart4418 1608 Schematic in PDF
| |
