Quantcast
Channel: Developers » Visit CNX Software
Viewing all 2336 articles
Browse latest View live

Amlogic S912 Processor Could Feature an ARM Mali-T830 GPU

$
0
0

Amlogic S912 launch has been delayed by a few months, and if we are to believe the data from GFXBench (test 1; test 2), the reason could be that they switched the design from a Mali-T7xx GPU to a more powerful Mali-T830 GPU.

Click to Enlarge

Click to Enlarge

S912 processor is still based on four Cortex A53 core @ up to 2.0 GHz like in S905, but the GPU will be much more powerful.

One person noticed these results and wrote an analysis and comparison (in Korean) against the Mali-860MP2 GPU found in Mediatek MT6755 SoC (Helio P10) SoC.

 Offscreen  Manhattan 3.1  Manhattan  T-Rex  ALU  ALU2  Fillrate  Texturing
 MT6755  4.8  7.2  17.2  6.0  1012
 S912  4.4  7.0  16.3  34.7  5.3  1283  1000

So while Mali-860MP2 is faster for all listed benchmark the advantage is not that great. His analysis  compared benchmarks (read post for details) concludes that the GPU in S912 could be clocked at around 650 MHz.

Thanks to Adriano for the tip.


DragonBoard 410c Development Board Quick Start Guide and Android Benchmarks

$
0
0

Linaro’s 96Boards initiative was announced in February with the introduction of Hikey board, and while progress has been rather slow, there are now two boards available for sale: Lemaker Hikey and Qualcomm Dragonboard 410c. The main advantage of these board is that 96Boards is not only an hardware specification, but also a software specifications that mandate most code to be open source, with recent versions of Linux and U-boot, and in the case of Dragonboard 410c work is being done with Freedreno open source GPU drivers.

Now that I’ve got a board I’ll explain my experience with the purchasing process, take a few pictures, and show how to get started with Android, and install the latest version, before running a few benchmarks.

Ordering DragonBoard 410c Development Board

I normally don’t like purchasing from North American and European distributors, because of the potential documentation involved to comply with silly laws, high shipping fees, which are themselves compounded by import taxes at home and the courier’s handling fees, meaning a $75 board could easily ending costing $150… So I did not intend to buy the board at first, and just went to the Arrow’s Dragonboard 410c page to find out how much shipping would be…

The board ships from the United Stated, but to my surprise shipping was free via Fedex Economy.

DragonBoard_410c_ShippingSo I just went ahead, the checkout process was rather straightforward, and paid by Paypal on Wednesday, November 12, with an estimated delivery date of November 18. Not too bad.

Two days later, I received an email asked me to complete an FCC Purchaser’s Certification form, because while the board had passed the company’s internal EMC tests, it had not passed FCC certification yet, so I could only use it as an evaluation platform. EMC certifications is expected by the end of the month. So I filled it up and simply sent it back by email.

The following Wednesday my order was confirmed, and I received the board yesterday (November 20). So it took about a week between my order and shipping, so I’m pretty satisfied how it all went considering the board is sent for free.

I did not pay any import duties, but Fedex did request for 7% VAT, amounting to about $6.

DragonBoard 410c Pictures

I got the board in a box warning about static electricity.

Dragonboard_410c_PackageI’ve seen pictures of the board before with Green and Red PCB, but mine ended up being Cyan, although the overall design did not really change since the first prototypes.

Click to Enlarge

Click to Enlarge

Click to Enlarge

Click to Enlarge

DragonBoard_410c_Angle

The main difference with the previous photos is that they added shields on top of the power circuitry, as well as on Qualcomm Snapdragon 410c and memory chips.

Click to Enlarge

Click to Enlarge

I’ve also take a picture with a few “friends” including Raspberry Pi 2, Orange Pi 2 mini, and Roseapple Pi boards. with DragonBoard 410c being slightly smaller.

Getting Started with DragonBoard 410c Development Board (in Android)

Linaro released the first Reference Software Platform for 96Boards a couple of weeks ago, and while Hikey supported both Android and Debian 8.2, ony the latter was released for DragonBoard 410c, so I was expecting the board to come pre-loaded with Debian Linux distribution, but instead it came with Android 5.1. That’s why I’m going to focus on Android in this first post, before checking out Linux in more details.

Since the board comes pre-loaded with an operating systems it should be easy to start with the platform, right? Sort of, but there are still some mini challenges to overcome.

First, the board takes 6.5 to 18V power supply as per 96Boards specifications, and the power barrel has a 1.7mm diameter instead of the more usual 2.1mm. That means all these 5V power supply I’ve accumulated can’t be used, so I had to find a 12V power supply, as well as some adapters to be able to connect it to the board. Luckily, I have a few 12V/1A power adapter from some TV boxes, and I have a 28 power jack adapters set to handle this case. If you don’t have any of those, you could also check out 96Boards power supply page with some recommendations.

12V/1A Power Adapter, and 2.1 to 1.7mm Adapter (Click to Enlarge)

12V/1A Power Adapter, and 2.1 to 1.7mm Adapter (Click to Enlarge)

Once I got this sorted out, I also connected a USB keyboard, and RF dongle for my air mouse, an HDMI cable to my TV, and an Ethernet… wait.. There’s no Ethernet port on 96Boards, so that’s it. As I connected the power, and LED quickly blink once, and then nothing for several (long) seconds, until I saw the Qualcomm boot animation, and later the lock screen.

Click for Original Size

Click for Original Size

These are the few apps pre-installed in the Android image.

Click for Original Size

Click for Original Size

And a look at “About phone” section shows MSM8916 for arm64 is running Android 5.1.1 on top of Linux 3.10.49. So I don’t think that image fully complies with 96Boards software specifications, and hopefully the Android release part of the Reference Software Platform will fix that.

Click for Original Size

Click for Original Size

I could connect to WiFi with issues, and transfer the screenshots via Bluetooth, since Android would not recognize my USB flash drive. Later on I found out micro SD cards work fine.

If you intend to modify the bootloader or kernel, you’ll most probably want to connect a USB to TLL board to the development platform. Unfortunately, while most development boards on the market are perfectly happy with a 3.3V or 5V power debug board, DragonBoard 410c board requires a 1.8V USB to TTL board which needs to inconveniently be connected to pins 1, 11 and 13 on the 40-pin low speed (LS) header.  I could remember that Hardkernel USB-UART board supports both 1.8 and 3.3V, and I got one thanks to the several ODROID board I was given to play with.

Click to Enlarge

Click to Enlarge

I fired up minicom in my Ubuntu computer, made sure it was set to 115200 8N1, but whatever I did I could not get any debug message on the serial console, even after switching Tx and Rx a few times… I tried to download Snapdragon 410 GPIO Pin Assignment from the Wiki, but the file in question had a “redirect loop”… So I gave up on that part for now.

Installing the latest Android Image

Eventually Linaro is going to update the firmware images and release the source regularly, so you’ll probably want to install the latest the latest build of the Android image, and I followed the instructions on 96Boards github wiki in an Ubuntu computer, which uses fastboot, and there’s also another method using a micro SD card.

Fastboot update

You’ll need fastboot utility to flash the firmware over USB. This command and all other below are typed from your Linux computer (Ubuntu/Debian):

sudo apt-get install android-tools-fastboot

Now download and extract the latest bootloader

mkdir bootloader

cd bootloader/

wget http://builds.96boards.org/releases/dragonboard410c/linaro/rescue/latest/dragonboard410c_bootloader_emmc_android*.zip -O dragonboard410c_bootloader_emmc_android_latest.zip

unzip dragonboard410c_bootloader_emmc_android_latest.zip

Dragonboard_410c_fastboot_switchNow make sure S6 switch on the board is set to 0-0-0-0 as shown in the right photo, and that there’s no micro SD card inserted in the board.

Now keep pressing S4 button (Volume -), while inserting the power jack into the board, and after a few releas the button. You should be in fastboot mode. Let’s check it:

sudo fastboot devices

ddb2310    fastboot

All good. Now flash all files with a single command

sudo ./flashall

The output will start with:

target reported max download size of 268435456 bytes

sending ‘partition’ (33 KB)...

OKAY [  0.006s]

writing ‘partition’...

It should take a few seconds to complete. If you forget to add sudo, the following message will show forever:

< waiting for device >

Now you’ll want to download the latest Android firmware files in your computer:

1

2

3

4

5

6

7

8

9

cd..

mkdir firmware

cd firmware

wget http://builds.96boards.org/releases/dragonboard410c/qualcomm/android/latest/boot.img.tar.xz

wget http://builds.96boards.org/releases/dragonboard410c/qualcomm/android/latest/system.img.tar.xz

wget http://builds.96boards.org/releases/dragonboard410c/qualcomm/android/latest/userdata.img.tar.xz

wget http://builds.96boards.org/releases/dragonboard410c/qualcomm/android/latest/recovery.img.tar.xz

wget http://builds.96boards.org/releases/dragonboard410c/qualcomm/android/latest/persist.img.tar.xz

wget http://builds.96boards.org/releases/dragonboard410c/qualcomm/android/latest/cache.img.tar.xz

Once this is done, unzip and flash the files to the board:

1

2

3

4

5

6

7

<span class=“pl-k”>for</span> <span class=“pl-smi”>f</span> <span class=“pl-k”>in</span> <span class=“pl-k”>*</span>.tar.xz<span class=“pl-k”>;</span> <span class=“pl-k”>do</span> tar xJf <span class=“pl-smi”>$f</span><span class=“pl-k”>;</span> <span class=“pl-k”>done</span>

sudo fastboot flash boot boot.img

sudo fastboot flash system system.img

sudo fastboot flash userdata userdata.img

sudo fastboot flash recovery recovery.img

sudo fastboot flash persist persist.img

sudo fastboot flash cache cache.img

Now unplug the power, and the micro USB cable, and put the power jack back into the board. Android should boot, but in my case it did not, and my power meter was stuck at 1 to 1.5 Watts instead of 2.0 to 3.0 Watts during a normal boot.

SD Card Update

So I fell back to the second update method, using a micro SD card. I’ve used a terminal windows in Ubuntu in the instructions below, but you could also use a Windows computer, and Win32DiskImager utility to perform the same tasks over a graphical user interface.

First download and extract the SD card image:

wget http://builds.96boards.org/releases/dragonboard410c/qualcomm/android/latest/dragonboard410c_sdcard_install_android-*.zip -O dragonboard410c_sdcard_android_latest.zip

unzip dragonboard410c_sdcard_android_latest.zip

Now insert your SD card into your computer, and check your device with lsblk:

1

2

3

4

5

6

7

8

9

lsblk

NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT

sda      8:0    0 465.8G  0 disk

├─sda1   8:1    0   512M  0 part /boot/efi

├─sda2   8:2    0 461.8G  0 part /

└─sda3   8:3    0   3.5G  0 part [SWAP]

<strong>sdb      8:16   1  29.3G  0 disk</strong>

└─sdb1   8:17   1  29.3G  0 part /media/jaufranc/2730-8926

sr0     11:0    1  1024M  0 rom

In my case, the micro SD card is 32GB, so my device is sdb. You need to replace <sd_device> with your own device in the command to dump the data to the SD card.

sudo umount /dev/&lt;sd_device&gt;*

sudo apt-get install pv

sudo dd if=db410c_sd_install_android.img | pv | sudo dd of=/dev/&lt;sd_device&gt; bs=16M

sync

DragonBoard_410c_SD_Card_BootYou can now remove the micro SD card from your computer and insert it into the board.

Set the S6 switch to 0110 (boot from SD-card ,USB Host mode) as shown on the right.

Now power on the board, LED 1 will blink regularly, and after a while NOOBS should show up on your monitor or TV, asking you to choose the operating system to install.

DragonBoard_410c_NOOBS_AndroidAbout_Phone_Android_Qualcomm_Snapdragon_410Click install, and complete the process. Once it asks your to remove the SD card. Disconnect the power, remove the micro SD card, set S6 back to 0000, re-connect the power, and be very patient for the first boot. I propose you make some tea and coffee, drink it, go to relieve yourself, and come back later where Android will have hopefully booted.

My Linux kernel is now a little newer, but still dated in August. So they have not released any Android firmware for a few months. This should change for the December Software Reference Platform release.

If you want to go further with Android on the board, I recommend you read the Android User Guide (PDF),  and visit DragonBoard 410C documentation page on 96Boards.org.

DragonBoard 410c Android Benchmarks

I’ve also side-loaded a few benchmarks to find out more about the board performance. But first let’s see what CPU-Z reports.

Click to Enlarge

Click to Enlarge

Qualcomm Snapdragon 400/410 is properly recognized with a quad core Cortex A53 processor clocked between 200 and 1.21 GHz and an Adreno 306 GPU @ up to 400 MHz. The governor is set to interactive, so it may slightly negatively impact the benchmarks below. The system has indeed 1GB RAM, with 4.84GB internal storage available to the user out of the 8GB eMMC flash.

Click to Enlarge

Click to Enlarge

After installing Antutu 5.7.1, it asked me whether I wanted to update to the 64-bit version for better performance. It’s the first time it happened in all my testing despite reviewing and benchmarking other 64-bit ARM systems before. The board scores 18,211 points in Antutu, quite lower as I expected compared to Amlogic S905 (quad core @ 2.0 Ghz -> ~28,000 points) and Rockchip RK3368 (octa-core @ 1.2 GHz -> ~34,000 points) processors also Cortex A53 cores.

Several smartphones have launched with Snapdragon 410 processors, so in theory it should be easy to find benchmark for comparison, but most of these phones come with a lower resolution 1280×720 display, and run Android 4.4. I still found Elephone Trunk with Snaprdragon 410, Android 5.1, and a 1280×780 scoring 21,500 points, so the score in DragonBoard 410c  appears more or less as expected.

Qualcomm_Snapdragon_410_VellamoVellamo 3.x should not run with Firefox at all, and only partially with Webview, so ignore the Browser scores. The board got 1,114 points in the multicore benchmark, or 786 points in the metal benchmark, which compares to respectively 1,572 and 763 with Amlogic S905 benchmark results.

DragonBoard_410c_3DMark_Ice_Storm_Extreme

Qualcomm DragonBoard 410c achieved 2,304 points in 3DMark Ice Storm Extreme compared to around 4,200 to 4,300 points in both Rockchip RK3368 and Amlogic S905 devices at the same 1920×1080 resolution.

Conclusion

As you can see from this initial review, 96Boards project is still very much work in progress on the software side, and I had wished some more common decision were made with regards to the specs (e.g. power supply, serial voltage, Ethernet…),  but at least the DragonBoard 410c platform should be interesting over time for people who want recent versions of U-boot, Linux and Android / Debian firmware, and source code, as well as an open source GPU drivers (Freedreno).

The next step should be to run Debian 8.2, but since the firmware is at the alpha stage with some issues like no HDMI audio, I may decide to take my time, and wait for the December release.

MeegoPad T07 Cherry Trail TV Stick with 4GB RAM Costs $109 (Crowdfunding)

$
0
0

There was some confused when MeegoPad T05, T06 and T07 Cherry Trail TV dongles details surfaced with specifications changing from sites to sites.  One forum post on x86pad.com, clarified MeegoPad products line up, including a new MeegoPad T08 Cherry Trail projector with battery. MeegoPad T07 was confirmed to be actively cooled with a small fan, and come with 2GB as seen on GeekBuying and GearBest, but the company also just launched a flexible funding Indiegogo campaign for the 4GB RAM version.

MeegoPad_T07_4GB_RAMMeegoPad T07 specifications:

  • SoC – Intel Atom x5-Z8300 “Cherry Trail” quad core processor @ 1.44 GHz (Turbo frequency: 1.84 GHz) with Intel Gen8 HD graphics (2W SDP)
  • System Memory –  4GB LPDDR3-1600
  • Storage – 32GB eMMC 5.0 flash + micro SD slot up to 128GB
  • Video Output – HDMI 1.4 male connector
  • Audio I/O – HDMI, 3.5mm audio jack
  • Connectivity – Dual band 802.11 b/g/n Wi-Fi, and Bluetooth 4.0
  • USB – 2x USB 2.0 host port, 1x micro USB port (power only)
  • Misc – Power button
  • Power Supply – 5V/2A via micro USB port
  • Dimensions – 106 x 53 x 13.5 mm
  • Weight – 50 grams

MeegoPad_T07_ConnectorsMeegoPad T07 is pre-loaded with an activated version of Windows 10. But note that the company do not have a stellar track record when it comes to license as they apparently shipped a MeegoPad T04 with an unlicensed Windows 10 to Lon Seidman, a YouTube reviewer, and then provided a link to some cracking software to fix the issue…

They ask for $109 for the “early supporter” reward, which includes T07 with Windows 10 Home,  an HDMI extension cable, a micro USB to USB cable, a power cable, and a carrying case. The company has also included MeegoPad T05 in the crowdfunding campaign featuring 2GB RAM only, and available barebone for $79, or with Windows 10 Home for $94. Shipping is not included, but is free to North America, and the few European countries I tried, and $10 to the rest of the world. Delivery is scheduled for January 2016.

Fan inside MeegoPad T07

Fan inside MeegoPad T07

MINI MX 4K Android Media Player Unboxing and Teardown

$
0
0

I received my first Amlogic S905 TV box last week with K1 Plus, and although I have not reviewed it yet due to some issues with Google Play, I’ve run some benchmarks on the Amlogic S905 platform, which some people mentioning that results could have been impacted by the small heatsink leading to CPU throttling. The good news is that I know have a new Amlogic SD905 TV Box to play with as GearBest sent me Beelink MINI MX TV box. Today, I’ll take a few photos of the device and the board, before hopefully publishing the full review early next week.

Beelink MINI MX Unboxing

I received the package via DHL, and thanks to its low price I did not have to pay custom duties or VAT.

Beelink_MINI_MX_Package
The package does not show any specific brand, only Mini MX 4K Movies products, as well as the specifications on the back.

Beelink MINI MX and Accessories (Click to Enlarge)

Beelink MINI MX and Accessories (Click to Enlarge)

The box ships with a 5V/2A power adapter, a simple IR remote control requiring two AAA batteries, an HDMI cable, and a quick start guide in English.

Click to Enlarge

Click to Enlarge

The device is quite thinner than some of the other TV boxes I’ve reviewed recently. The front panel has a small circular window for the power LED, while one of the side comes with a micro SD slot, and a USB port. The main ports can be found in the rear panel with an optical S/PDIF port, Gigabit Ethernet RJ45 connector, HDMI 2.0 output, , another USB 2.0 host port, and the power jack.

[embedded content]

Beelink MINI MX Teardown

There aren’t any screws holding the two parts of the case together, so you need some rigi and sharp plastic tool to pop up the parts.
Beelink_MINI_MX_Heatsink

The WiFi antenna is on the board itself, so I had nothing to break this time.., and there’s no heatsink on the processor, but instead heat dissipation is done via a themal pad glued to a metallic plate fastened to the top of the case, which should provide better cooling than the tiny heatsink found in VideoStrong K1 Plus.

Click to Enlarge

Click to Enlarge

The back of the board has nothing much, expect the recovery/firmware update button on the top right of the picture, and a 4-pin header for the serial console, on the right side.

Click to Enlarge

Click to Enlarge

Since they own Beelink brand, it’s no surprise to reading the board was made by Netxeon, with the board name reading S95_V2.0_20150909. Two Samsung K4B4G1646D-BCMA DDR3 chips bring 1GB RAM to the device, while FORESEE NCEFAT28-08G NAND? flash takes care of the 8GB internal storage. Ampak AP6212 wireless module adds Bluetooth 4.0 and 2.4GHz WiFi 802.11 b/g/n to the device, and Pulse H5007NL magnetics and Reatek RTL8211F Ethernet transceiver confirm Gigabit Ethernet support.  Beside the 4-pin serial console header, there are also 6 solder points to connect a JTAG debugger.

I’d like to thank GearBest for sending a review sample. If you are interested, you could purchase Beelink MINI MX from their website for just $40.79 including shipping with BEELL coupon. Alternative shopping options include GeekBuying ($44.99), eBay, Amazon US ($55), and a few others.

How to Build Brillo Operating System from Source Code and Run Brillo Emulator

$
0
0

Google formally launched Brillo operating system a few weeks ago. The new operating system is a stripped down version of Android that targets Internet of Things (IoT) applications, and more recently the company pushed the source code to their servers.

So I’ve given it a try by checking out the code, building Brillo emulator for Intel/AMD, and running it in Ubuntu 14.04 64-bit.

It took a few hours here with some errors the first time, so I tried again and I finally got the code a few hours later. Once this is done, set the build environment and configuration:

You could also run the “Brillo emulator” on ARM, and edison-eng must be the build for Intel Edison board.
Now you can start the build:

It has to complete 21491 different tasks, so depending on your computer performance it may take a few dozen of minutes to several hours.

and it failed again after switching to Java 1.7.x requesting OpenJDK, so I switched to OpenJDK 7.0 as shown in the error message:

After this configuration changes, running make clean && make -j8 did the trick and the build went much further, but still failed with:

So the rootfs is kept small at 95MB, and only 74MB RAM is used.

[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Initializing cgroup subsys cpuacct
[ 0.000000] Linux version 3.18.0+ (jaufranc@FX8350) (gcc version 4.9 20140827 (prerelease) (GCC) ) #1 SMP Mon Nov 23 17:48:36 ICT 2015
[ 0.000000] e820: BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009fbff] usable
[ 0.000000] BIOS-e820: [mem 0x000000000009fc00-0x000000000009ffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000000f0000-0x00000000000fffff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000003ffdffff] usable
[ 0.000000] BIOS-e820: [mem 0x000000003ffe0000-0x000000003fffffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fffc0000-0x00000000ffffffff] reserved
[ 0.000000] Notice: NX (Execute Disable) protection missing in CPU!
[ 0.000000] SMBIOS 2.8 present.
[ 0.000000] DMI: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.7.5.1-0-g8936dbb-20141113_115728-nilsson.home.kraxel.org 04/01/2014
[ 0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
[ 0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
[ 0.000000] e820: last_pfn = 0x3ffe0 max_arch_pfn = 0x1000000
[ 0.000000] found SMP MP-table at [mem 0x000f0e90-0x000f0e9f] mapped at [c00f0e90]
[ 0.000000] Scanning 1 areas for low memory corruption
[ 0.000000] initial memory mapped: [mem 0x00000000-0x01ffffff]
[ 0.000000] Base memory trampoline at [c009b000] 9b000 size 16384
[ 0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
[ 0.000000] [mem 0x00000000-0x000fffff] page 4k
[ 0.000000] init_memory_mapping: [mem 0x37400000-0x375fffff]
[ 0.000000] [mem 0x37400000-0x375fffff] page 2M
[ 0.000000] init_memory_mapping: [mem 0x34000000-0x373fffff]
[ 0.000000] [mem 0x34000000-0x373fffff] page 2M
[ 0.000000] init_memory_mapping: [mem 0x00100000-0x33ffffff]
[ 0.000000] [mem 0x00100000-0x001fffff] page 4k
[ 0.000000] [mem 0x00200000-0x33ffffff] page 2M
[ 0.000000] init_memory_mapping: [mem 0x37600000-0x377fdfff]
[ 0.000000] [mem 0x37600000-0x377fdfff] page 4k
[ 0.000000] BRK [0x01bd0000, 0x01bd0fff] PGTABLE
[ 0.000000] BRK [0x01bd1000, 0x01bd1fff] PGTABLE
[ 0.000000] ACPI: Early table checksum verification disabled
[ 0.000000] ACPI: RSDP 0x000F0C90 000014 (v00 BOCHS )
[ 0.000000] ACPI: RSDT 0x3FFE1A4A 000034 (v01 BOCHS BXPCRSDT 00000001 BXPC 00000001)
[ 0.000000] ACPI: FACP 0x3FFE1033 000074 (v01 BOCHS BXPCFACP 00000001 BXPC 00000001)
[ 0.000000] ACPI: DSDT 0x3FFE0040 000FF3 (v01 BOCHS BXPCDSDT 00000001 BXPC 00000001)
[ 0.000000] ACPI: FACS 0x3FFE0000 000040
[ 0.000000] ACPI: SSDT 0x3FFE10A7 0008F3 (v01 BOCHS BXPCSSDT 00000001 BXPC 00000001)
[ 0.000000] ACPI: APIC 0x3FFE199A 000078 (v01 BOCHS BXPCAPIC 00000001 BXPC 00000001)
[ 0.000000] ACPI: HPET 0x3FFE1A12 000038 (v01 BOCHS BXPCHPET 00000001 BXPC 00000001)
[ 0.000000] ACPI: Local APIC address 0xfee00000
[ 0.000000] 135MB HIGHMEM available.
[ 0.000000] 887MB LOWMEM available.
[ 0.000000] mapped low ram: 0 – 377fe000
[ 0.000000] low ram: 0 – 377fe000
[ 0.000000] BRK [0x01bd2000, 0x01bd2fff] PGTABLE
[ 0.000000] Zone ranges:
[ 0.000000] DMA [mem 0x00001000-0x00ffffff]
[ 0.000000] Normal [mem 0x01000000-0x377fdfff]
[ 0.000000] HighMem [mem 0x377fe000-0x3ffdffff]
[ 0.000000] Movable zone start for each node
[ 0.000000] Early memory node ranges
[ 0.000000] node 0: [mem 0x00001000-0x0009efff]
[ 0.000000] node 0: [mem 0x00100000-0x3ffdffff]
[ 0.000000] Initmem setup node 0 [mem 0x00001000-0x3ffdffff]
[ 0.000000] On node 0 totalpages: 262014
[ 0.000000] free_area_init_node: node 0, pgdat c1a79d40, node_mem_map f6ffe020
[ 0.000000] DMA zone: 32 pages used for memmap
[ 0.000000] DMA zone: 0 pages reserved
[ 0.000000] DMA zone: 3998 pages, LIFO batch:0
[ 0.000000] Normal zone: 1744 pages used for memmap
[ 0.000000] Normal zone: 223230 pages, LIFO batch:31
[ 0.000000] HighMem zone: 272 pages used for memmap
[ 0.000000] HighMem zone: 34786 pages, LIFO batch:7
[ 0.000000] Using APIC driver default
[ 0.000000] ACPI: PM-Timer IO Port: 0x608
[ 0.000000] ACPI: Local APIC address 0xfee00000
[ 0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
[ 0.000000] ACPI: LAPIC_NMI (acpi_id[0xff] dfl dfl lint[0x1])
[ 0.000000] ACPI: IOAPIC (id[0x00] address[0xfec00000] gsi_base[0])
[ 0.000000] IOAPIC[0]: apic_id 0, version 17, address 0xfec00000, GSI 0-23
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 5 global_irq 5 high level)
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 10 global_irq 10 high level)
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 11 global_irq 11 high level)
[ 0.000000] ACPI: IRQ0 used by override.
[ 0.000000] ACPI: IRQ5 used by override.
[ 0.000000] ACPI: IRQ9 used by override.
[ 0.000000] ACPI: IRQ10 used by override.
[ 0.000000] ACPI: IRQ11 used by override.
[ 0.000000] Using ACPI (MADT) for SMP configuration information
[ 0.000000] ACPI: HPET id: 0x8086a201 base: 0xfed00000
[ 0.000000] smpboot: Allowing 1 CPUs, 0 hotplug CPUs
[ 0.000000] e820: [mem 0x40000000-0xfffbffff] available for PCI devices
[ 0.000000] setup_percpu: NR_CPUS:8 nr_cpumask_bits:8 nr_cpu_ids:1 nr_node_ids:1
[ 0.000000] PERCPU: Embedded 14 pages/cpu @f6fe9000 s32832 r0 d24512 u57344
[ 0.000000] pcpu-alloc: s32832 r0 d24512 u57344 alloc=14*4096
[ 0.000000] pcpu-alloc: [0] 0
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 260238
[ 0.000000] Kernel command line: console=ttyS0 root=/dev/vda androidboot.hardware=qemu qemu=1 rootwait noinitrd init=/init androidboot.selinux=enforcing
[ 0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[ 0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[ 0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[ 0.000000] Initializing CPU#0
[ 0.000000] Initializing HighMem for node 0 (000377fe:0003ffe0)
[ 0.000000] Initializing Movable for node 0 (00000000:00000000)
[ 0.000000] Memory: 1026804K/1048056K available (7876K kernel code, 550K rwdata, 2376K rodata, 600K init, 580K bss, 21252K reserved, 139144K highmem)
[ 0.000000] virtual kernel memory layout:
[ 0.000000] fixmap : 0xfff16000 – 0xfffff000 ( 932 kB)
[ 0.000000] pkmap : 0xff800000 – 0xffa00000 (2048 kB)
[ 0.000000] vmalloc : 0xf7ffe000 – 0xff7fe000 ( 120 MB)
[ 0.000000] lowmem : 0xc0000000 – 0xf77fe000 ( 887 MB)
[ 0.000000] .init : 0xc1a90000 – 0xc1b26000 ( 600 kB)
[ 0.000000] .data : 0xc17b15ad – 0xc1a8eb80 (2933 kB)
[ 0.000000] .text : 0xc1000000 – 0xc17b15ad (7877 kB)
[ 0.000000] Checking if this processor honours the WP bit even in supervisor mode…Ok.
[ 0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[ 0.000000] Hierarchical RCU implementation.
[ 0.000000] RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=1.
[ 0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=1
[ 0.000000] NR_IRQS:2304 nr_irqs:256 0
[ 0.000000] CPU 0 irqstacks, hard=f6808000 soft=f680a000
[ 0.000000] Console: colour *CGA 80×25
[ 0.000000] console [ttyS0] enabled
[ 0.000000] hpet clockevent registered
[ 0.000000] tsc: Fast TSC calibration using PIT
[ 0.000000] tsc: Detected 4026.913 MHz processor
[ 0.005418] Calibrating delay loop (skipped), value calculated using timer frequency.. 8053.82 BogoMIPS (lpj=4026913)
[ 0.006453] pid_max: default: 32768 minimum: 301
[ 0.007059] ACPI: Core revision 20140926
[ 0.034542] ACPI: All ACPI Tables successfully acquired
[ 0.038869] Security Framework initialized
[ 0.040279] SELinux: Initializing.
[ 0.041568] SELinux: Starting in permissive mode
[ 0.042128] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.042547] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.053656] Initializing cgroup subsys freezer
[ 0.056312] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
[ 0.056312] Last level dTLB entries: 4KB 0, 2MB 0, 4MB 0, 1GB 0
[ 0.175834] Freeing SMP alternatives memory: 32K (c1b26000 – c1b2e000)
[ 0.188319] Enabling APIC mode: Flat. Using 1 I/O APICs
[ 0.193435] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
[ 0.204267] smpboot: CPU0: Intel QEMU Virtual CPU version 2.2.0 (fam: 06, model: 06, stepping: 03)
[ 0.205000] Performance Events: Broken PMU hardware detected, using software events only.
[ 0.206054] Failed to access perfctr msr (MSR c1 is 0)
[ 0.217459] x86: Booted up 1 node, 1 CPUs
[ 0.217782] smpboot: Total of 1 processors activated (8053.82 BogoMIPS)
[ 0.229611] devtmpfs: initialized
[ 0.244079] RTC time: 10:50:02, date: 11/23/15
[ 0.253859] kworker/u2:0 (15) used greatest stack depth: 7196 bytes left
[ 0.255302] NET: Registered protocol family 16
[ 0.263307] cpuidle: using governor ladder
[ 0.263655] cpuidle: using governor menu
[ 0.265240] ACPI: bus type PCI registered
[ 0.268645] PCI: PCI BIOS revision 2.10 entry at 0xfd456, last bus=0
[ 0.269093] PCI: Using configuration type 1 for base access
[ 0.325660] kworker/u2:0 (50) used greatest stack depth: 7188 bytes left
[ 0.329175] ACPI: Added _OSI(Module Device)
[ 0.329423] ACPI: Added _OSI(Processor Device)
[ 0.329644] ACPI: Added _OSI(3.0 _SCP Extensions)
[ 0.329876] ACPI: Added _OSI(Processor Aggregator Device)
[ 0.362799] ACPI: Interpreter enabled
[ 0.363221] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [_S1_] (20140926/hwxface-580)
[ 0.364505] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [_S2_] (20140926/hwxface-580)
[ 0.365631] ACPI: (supports S0 S3 S5)
[ 0.366056] ACPI: Using IOAPIC for interrupt routing
[ 0.367488] PCI: Using host bridge windows from ACPI; if necessary, use “pci=nocrs” and report a bug
[ 0.428846] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
[ 0.429403] acpi PNP0A03:00: _OSC: OS supports [ASPM ClockPM Segments MSI]
[ 0.430646] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
[ 0.434071] acpi PNP0A03:00: fail to add MMCONFIG information, can’t access extended PCI configuration space under this bridge.
[ 0.435869] PCI host bridge to bus 0000:00
[ 0.436299] pci_bus 0000:00: root bus resource [bus 00-ff]
[ 0.436849] pci_bus 0000:00: root bus resource [io 0x0000-0x0cf7]
[ 0.437381] pci_bus 0000:00: root bus resource [io 0x0d00-0xadff]
[ 0.437710] pci_bus 0000:00: root bus resource [io 0xae0f-0xaeff]
[ 0.438020] pci_bus 0000:00: root bus resource [io 0xaf20-0xafdf]
[ 0.438338] pci_bus 0000:00: root bus resource [io 0xafe4-0xffff]
[ 0.438678] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
[ 0.439396] pci_bus 0000:00: root bus resource [mem 0x40000000-0xfebfffff]
[ 0.441115] pci 0000:00:00.0: [8086:1237] type 00 class 0x060000
[ 0.445759] pci 0000:00:01.0: [8086:7000] type 00 class 0x060100
[ 0.447396] pci 0000:00:01.1: [8086:7010] type 00 class 0x010180
[ 0.453049] pci 0000:00:01.1: reg 0x20: [io 0xc0a0-0xc0af]
[ 0.455536] pci 0000:00:01.1: legacy IDE quirk: reg 0x10: [io 0x01f0-0x01f7]
[ 0.456064] pci 0000:00:01.1: legacy IDE quirk: reg 0x14: [io 0x03f6]
[ 0.456439] pci 0000:00:01.1: legacy IDE quirk: reg 0x18: [io 0x0170-0x0177]
[ 0.457036] pci 0000:00:01.1: legacy IDE quirk: reg 0x1c: [io 0x0376]
[ 0.459095] pci 0000:00:01.3: [8086:7113] type 00 class 0x068000
[ 0.459510] pci 0000:00:01.3: quirk: [io 0x0600-0x063f] claimed by PIIX4 ACPI
[ 0.459976] pci 0000:00:01.3: quirk: [io 0x0700-0x070f] claimed by PIIX4 SMB
[ 0.462178] pci 0000:00:02.0: [1af4:1001] type 00 class 0x010000
[ 0.464049] pci 0000:00:02.0: reg 0x10: [io 0xc000-0xc03f]
[ 0.466036] pci 0000:00:02.0: reg 0x14: [mem 0xfebc0000-0xfebc0fff]
[ 0.477345] kworker/u2:0 (118) used greatest stack depth: 7140 bytes left
[ 0.480000] pci 0000:00:03.0: [1af4:1001] type 00 class 0x010000
[ 0.482037] pci 0000:00:03.0: reg 0x10: [io 0xc040-0xc07f]
[ 0.484029] pci 0000:00:03.0: reg 0x14: [mem 0xfebc1000-0xfebc1fff]
[ 0.496407] pci 0000:00:04.0: [1af4:1000] type 00 class 0x020000
[ 0.498049] pci 0000:00:04.0: reg 0x10: [io 0xc080-0xc09f]
[ 0.500096] pci 0000:00:04.0: reg 0x14: [mem 0xfebc2000-0xfebc2fff]
[ 0.510057] pci 0000:00:04.0: reg 0x30: [mem 0xfeb80000-0xfebbffff pref]
[ 0.513912] pci_bus 0000:00: on NUMA node 0
[ 0.518203] ACPI: PCI Interrupt Link [LNKA] (IRQs 5 *10 11)
[ 0.519457] ACPI: PCI Interrupt Link [LNKB] (IRQs 5 *10 11)
[ 0.520605] ACPI: PCI Interrupt Link [LNKC] (IRQs 5 10 *11)
[ 0.521527] ACPI: PCI Interrupt Link [LNKD] (IRQs 5 10 *11)
[ 0.522607] ACPI: PCI Interrupt Link [LNKS] (IRQs *9)
[ 0.528000] ACPI: Enabled 16 GPEs in block 00 to 0F
[ 0.533195] vgaarb: loaded
[ 0.535669] SCSI subsystem initialized
[ 0.537168] libata version 3.00 loaded.
[ 0.538252] ACPI: bus type USB registered
[ 0.539386] usbcore: registered new interface driver usbfs
[ 0.540037] usbcore: registered new interface driver hub
[ 0.540565] usbcore: registered new device driver usb
[ 0.541840] pps_core: LinuxPPS API ver. 1 registered
[ 0.542063] pps_core: Software ver. 5.3.6 – Copyright 2005-2007 Rodolfo Giometti [email protected]>
[ 0.542695] PTP clock support registered
[ 0.545377] Advanced Linux Sound Architecture Driver Initialized.
[ 0.545843] PCI: Using ACPI for IRQ routing
[ 0.546211] PCI: pci_cache_line_size set to 32 bytes
[ 0.546757] e820: reserve RAM buffer [mem 0x0009fc00-0x0009ffff]
[ 0.546949] e820: reserve RAM buffer [mem 0x3ffe0000-0x3fffffff]
[ 0.559418] NetLabel: Initializing
[ 0.559651] NetLabel: domain hash size = 128
[ 0.559919] NetLabel: protocols = UNLABELED CIPSOv4
[ 0.561049] NetLabel: unlabeled traffic allowed by default
[ 0.561832] cfg80211: Calling CRDA to update world regulatory domain
[ 0.564280] HPET: 3 timers in total, 0 timers will be used for per-cpu timer
[ 0.564908] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0
[ 0.565196] hpet0: 3 comparators, 64-bit 100.000000 MHz counter
[ 0.570506] Switched to clocksource hpet
[ 0.660379] kworker/u2:0 (211) used greatest stack depth: 7020 bytes left
[ 0.728357] pnp: PnP ACPI init
[ 0.731334] pnp 00:00: Plug and Play ACPI device, IDs PNP0b00 (active)
[ 0.732336] pnp 00:01: Plug and Play ACPI device, IDs PNP0303 (active)
[ 0.732779] pnp 00:02: Plug and Play ACPI device, IDs PNP0f13 (active)
[ 0.733458] pnp 00:03: [dma 2]
[ 0.733732] pnp 00:03: Plug and Play ACPI device, IDs PNP0700 (active)
[ 0.734668] pnp 00:04: Plug and Play ACPI device, IDs PNP0400 (active)
[ 0.735401] pnp 00:05: Plug and Play ACPI device, IDs PNP0501 (active)
[ 0.737731] pnp: PnP ACPI: found 6 devices
[ 0.804489] pci_bus 0000:00: resource 4 [io 0x0000-0x0cf7]
[ 0.804525] pci_bus 0000:00: resource 5 [io 0x0d00-0xadff]
[ 0.804541] pci_bus 0000:00: resource 6 [io 0xae0f-0xaeff]
[ 0.804556] pci_bus 0000:00: resource 7 [io 0xaf20-0xafdf]
[ 0.804572] pci_bus 0000:00: resource 8 [io 0xafe4-0xffff]
[ 0.804587] pci_bus 0000:00: resource 9 [mem 0x000a0000-0x000bffff]
[ 0.804603] pci_bus 0000:00: resource 10 [mem 0x40000000-0xfebfffff]
[ 0.805098] NET: Registered protocol family 2
[ 0.810624] TCP established hash table entries: 8192 (order: 3, 32768 bytes)
[ 0.811671] TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
[ 0.812318] TCP: Hash tables configured (established 8192 bind 8192)
[ 0.812943] TCP: reno registered
[ 0.813306] UDP hash table entries: 512 (order: 2, 16384 bytes)
[ 0.813750] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
[ 0.816909] NET: Registered protocol family 1
[ 0.820002] RPC: Registered named UNIX socket transport module.
[ 0.820534] RPC: Registered udp transport module.
[ 0.820817] RPC: Registered tcp transport module.
[ 0.821176] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 0.822119] pci 0000:00:00.0: Limiting direct PCI/PCI transfers
[ 0.822608] pci 0000:00:01.0: PIIX3: Enabling Passive Release
[ 0.823194] pci 0000:00:01.0: Activating ISA DMA hang workarounds
[ 0.823597] PCI: CLS 0 bytes, default 32
[ 0.838067] microcode: CPU0 sig=0x663, pf=0x1, revision=0x0
[ 0.839734] microcode: Microcode Update Driver: v2.00 [email protected]>, Peter Oruba
[ 0.842525] Scanning for low memory corruption every 60 seconds
[ 0.848986] futex hash table entries: 256 (order: 2, 16384 bytes)
[ 0.850044] audit: initializing netlink subsys (disabled)
[ 0.851307] audit: type=2000 audit(1448275802.850:1): initialized
[ 0.856442] HugeTLB registered 2 MB page size, pre-allocated 0 pages
[ 0.889569] VFS: Disk quotas dquot_6.5.2
[ 0.890470] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[ 0.902369] NFS: Registering the id_resolver key type
[ 0.903546] Key type id_resolver registered
[ 0.903810] Key type id_legacy registered
[ 0.905558] msgmni has been set to 1733
[ 0.907349] SELinux: Registering netfilter hooks
[ 0.913599] bounce: pool size: 64 pages
[ 0.914549] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 251)
[ 0.915162] io scheduler noop registered
[ 0.915455] io scheduler deadline registered
[ 0.916333] io scheduler cfq registered (default)
[ 0.917877] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[ 0.921833] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input0
[ 0.922899] ACPI: Power Button [PWRF]
[ 1.301371] ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 10
[ 1.677267] ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 11
[ 1.981884] ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 11
[ 1.984959] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[ 2.010482] serial 00:05: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
[ 2.019988] Non-volatile memory driver v1.3
[ 2.020747] Linux agpgart interface v0.103
[ 2.023687] [drm] Initialized drm 1.1.0 20060810
[ 2.038309] loop: module loaded
[ 2.040861] virtio-pci 0000:00:02.0: irq 24 for MSI/MSI-X
[ 2.040928] virtio-pci 0000:00:02.0: irq 25 for MSI/MSI-X
[ 2.062221] vda: unknown partition table
[ 2.067705] virtio-pci 0000:00:03.0: irq 26 for MSI/MSI-X
[ 2.067744] virtio-pci 0000:00:03.0: irq 27 for MSI/MSI-X
[ 2.075634] vdb: unknown partition table
[ 2.079262] ata_piix 0000:00:01.1: version 2.13
[ 2.091046] scsi host0: ata_piix
[ 2.093511] scsi host1: ata_piix
[ 2.094658] ata1: PATA max MWDMA2 cmd 0x1f0 ctl 0x3f6 bmdma 0xc0a0 irq 14
[ 2.095072] ata2: PATA max MWDMA2 cmd 0x170 ctl 0x376 bmdma 0xc0a8 irq 15
[ 2.100894] e100: Intel(R) PRO/100 Network Driver, 3.5.24-k2-NAPI
[ 2.101400] e100: Copyright(c) 1999-2006 Intel Corporation
[ 2.102625] e1000: Intel(R) PRO/1000 Network Driver – version 7.3.21-k8-NAPI
[ 2.103018] e1000: Copyright (c) 1999-2006 Intel Corporation.
[ 2.103630] e1000e: Intel(R) PRO/1000 Network Driver – 2.3.2-k
[ 2.103920] e1000e: Copyright(c) 1999 – 2014 Intel Corporation.
[ 2.104790] sky2: driver version 1.30
[ 2.107568] ehci_hcd: USB 2.0 ‘Enhanced’ Host Controller (EHCI) Driver
[ 2.107977] ehci-pci: EHCI PCI platform driver
[ 2.108937] ohci_hcd: USB 1.1 ‘Open’ Host Controller (OHCI) Driver
[ 2.109708] ohci-pci: OHCI PCI platform driver
[ 2.110846] uhci_hcd: USB Universal Host Controller Interface driver
[ 2.112358] usbcore: registered new interface driver usblp
[ 2.112878] usbcore: registered new interface driver usb-storage
[ 2.114562] i8042: PNP: PS/2 Controller [PNP0303:KBD,PNP0f13:MOU] at 0x60,0x64 irq 1,12
[ 2.118596] serio: i8042 KBD port at 0x60,0x64 irq 1
[ 2.119178] serio: i8042 AUX port at 0x60,0x64 irq 12
[ 2.121894] mousedev: PS/2 mouse device common for all mice
[ 2.126816] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input1
[ 2.129980] rtc_cmos 00:00: RTC can wake from S4
[ 2.135665] rtc_cmos 00:00: rtc core: registered rtc_cmos as rtc0
[ 2.137045] rtc_cmos 00:00: alarms up to one day, 114 bytes nvram, hpet irqs
[ 2.141927] device-mapper: ioctl: 4.28.0-ioctl (2014-09-17) initialised: [email protected]
[ 2.143526] hidraw: raw HID events driver (C) Jiri Kosina
[ 2.147749] usbcore: registered new interface driver usbhid
[ 2.148068] usbhid: USB HID core driver
[ 2.150259] ashmem: initialized
[ 2.162457] Netfilter messages via NETLINK v0.30.
[ 2.163070] nf_conntrack version 0.5.0 (16044 buckets, 64176 max)
[ 2.166829] ctnetlink v0.93: registering with nfnetlink.
[ 2.172251] ip_tables: (C) 2000-2006 Netfilter Core Team
[ 2.175570] TCP: cubic registered
[ 2.175786] Initializing XFRM netlink socket
[ 2.179260] NET: Registered protocol family 10
[ 2.190932] ip6_tables: (C) 2000-2006 Netfilter Core Team
[ 2.193695] sit: IPv6 over IPv4 tunneling driver
[ 2.198711] NET: Registered protocol family 17
[ 2.200733] 9pnet: Installing 9P2000 support
[ 2.201702] Key type dns_resolver registered
[ 2.202013] mce: Unable to init device /dev/mcelog (rc: -5)
[ 2.203489] Using IPI No-Shortcut mode
[ 2.206294] registered taskstats version 1
[ 2.211717] Magic number: 7:606:831
[ 2.212589] console [netcon0] enabled
[ 2.212820] netconsole: network logging started
[ 2.215460] ALSA device list:
[ 2.215666] No soundcards found.
[ 2.255738] ata2.01: NODEV after polling detection
[ 2.257994] ata2.00: ATAPI: QEMU DVD-ROM, 2.2.0, max UDMA/100
[ 2.260900] ata2.00: configured for MWDMA2
[ 2.272379] scsi 1:0:0:0: CD-ROM QEMU QEMU DVD-ROM 2.2. PQ: 0 ANSI: 5
[ 2.291021] sr 1:0:0:0: [sr0] scsi3-mmc drive: 4x/4x cd/rw xa/form2 tray
[ 2.291731] cdrom: Uniform CD-ROM driver Revision: 3.20
[ 2.294976] sr 1:0:0:0: Attached scsi CD-ROM sr0
[ 2.298811] sr 1:0:0:0: Attached scsi generic sg0 type 5
[ 2.742960] input: ImExPS/2 Generic Explorer Mouse as /devices/platform/i8042/serio1/input/input3
[ 2.747584] md: Waiting for all devices to be available before autodetect
[ 2.747972] md: If you don’t use raid, use raid=noautodetect
[ 2.751416] md: Autodetecting RAID arrays.
[ 2.751687] md: Scanned 0 and added 0 devices.
[ 2.751930] md: autorun …
[ 2.752217] md: … autorun DONE.
[ 2.757233] EXT4-fs (vda): couldn’t mount as ext3 due to feature incompatibilities
[ 2.759757] EXT4-fs (vda): couldn’t mount as ext2 due to feature incompatibilities
[ 2.778756] EXT4-fs (vda): mounted filesystem with ordered data mode. Opts: (null)
[ 2.779925] VFS: Mounted root (ext4 filesystem) readonly on device 253:0.
[ 2.782752] devtmpfs: mounted
[ 2.830385] Freeing unused kernel memory: 600K (c1a90000 – c1b26000)
[ 2.831602] Write protecting the kernel text: 7880k
[ 2.831986] Write protecting the kernel read-only data: 2380k
[ 2.838582] tsc: Refined TSC clocksource calibration: 4026.947 MHz
[ 2.960886] init: init first stage started!
[ 2.996875] SELinux: 2048 avtab hash slots, 5772 rules.
[ 3.003446] SELinux: 2048 avtab hash slots, 5772 rules.
[ 3.003878] SELinux: 1 users, 2 roles, 598 types, 0 bools, 1 sens, 1024 cats
[ 3.003934] SELinux: 56 classes, 5772 rules
[ 3.010274] SELinux: Completing initialization.
[ 3.010293] SELinux: Setting up existing superblocks.
[ 3.010802] SELinux: initialized (dev rootfs, type rootfs), uses genfs_contexts
[ 3.011062] SELinux: initialized (dev bdev, type bdev), not configured for labeling
[ 3.011353] SELinux: initialized (dev proc, type proc), uses genfs_contexts
[ 3.011820] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
[ 3.012614] SELinux: initialized (dev devtmpfs, type devtmpfs), uses transition SIDs
[ 3.013539] SELinux: initialized (dev sockfs, type sockfs), uses task SIDs
[ 3.013580] SELinux: initialized (dev debugfs, type debugfs), uses genfs_contexts
[ 3.049335] SELinux: initialized (dev pipefs, type pipefs), uses task SIDs
[ 3.049371] SELinux: initialized (dev anon_inodefs, type anon_inodefs), not configured for labeling
[ 3.049392] SELinux: initialized (dev aio, type aio), not configured for labeling
[ 3.049416] SELinux: initialized (dev devpts, type devpts), uses transition SIDs
[ 3.049461] SELinux: initialized (dev hugetlbfs, type hugetlbfs), not configured for labeling
[ 3.049485] SELinux: initialized (dev mqueue, type mqueue), uses transition SIDs
[ 3.049522] SELinux: initialized (dev selinuxfs, type selinuxfs), uses genfs_contexts
[ 3.049714] SELinux: initialized (dev vda, type ext4), uses xattr
[ 3.050708] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
[ 3.050798] SELinux: initialized (dev sysfs, type sysfs), uses genfs_contexts
[ 3.065426] audit: type=1403 audit(1448275805.065:2): policy loaded auid=4294967295 ses=4294967295
[ 3.079294] audit: type=1404 audit(1448275805.079:3): enforcing=1 old_enforcing=0 auid=4294967295 ses=4294967295
[ 3.084369] init: (Initializing SELinux enforcing took 0.11s.)
[ 3.129708] init: init second stage started!
[ 3.159084] init: Running restorecon…
[ 3.218593] init: waitpid failed: No child processes
[ 3.221464] init: (Loading properties from /default.prop took 0.00s.)
[ 3.234797] init: property ‘ro.zygote’ doesn’t exist while expanding ‘/init.${ro.zygote}.rc’
[ 3.235713] init: /init.rc: 11: error while expanding import
[ 3.252415] init: /init.environ.rc: 10: export requires 2 arguments
[ 3.252848] init: /init.environ.rc: 11: export requires 2 arguments
[ 3.253969] init: (Parsing /init.environ.rc took 0.00s.)
[ 3.259032] init: (Parsing /init.usb.rc took 0.00s.)
[ 3.261443] init: (Parsing /init.qemu.rc took 0.00s.)
[ 3.262308] init: could not import file ‘/init.usb.configfs.rc’ from ‘/init.rc’: No such file or directory
[ 3.263186] init: (Parsing /init.rc took 0.03s.)
[ 3.276502] init: Starting service ‘ueventd’…
[ 3.291840] init: Waiting for /dev/.coldboot_done…
[ 3.300494] ueventd: ueventd started!
[ 3.841027] Switched to clocksource tsc
[ 3.861834] ueventd: Coldboot took 0.50s.
[ 3.867557] init: Waiting for /dev/.coldboot_done took 0.58s.
[ 3.869596] init: /dev/hw_random not found
[ 3.882262] SELinux: initialized (dev cgroup, type cgroup), uses genfs_contexts
[ 3.886386] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
[ 3.893500] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
[ 3.905288] init: write_file: Unable to open ‘/proc/sys/kernel/hung_task_timeout_secs’: No such file or directory
[ 3.905900] init: write_file: Unable to open ‘/proc/cpu/alignment’: No such file or directory
[ 3.906582] init: write_file: Unable to open ‘/proc/sys/kernel/sched_tunable_scaling’: No such file or directory
[ 3.907762] init: write_file: Unable to open ‘/proc/sys/kernel/sched_latency_ns’: No such file or directory
[ 3.908498] init: write_file: Unable to open ‘/proc/sys/kernel/sched_wakeup_granularity_ns’: No such file or directory
[ 3.909116] init: write_file: Unable to open ‘/proc/sys/kernel/sched_compat_yield’: No such file or directory
[ 3.919055] SELinux: initialized (dev cgroup, type cgroup), uses genfs_contexts
[ 3.920571] init: write_file: Unable to write to ‘/dev/cpuctl/cpu.shares’: Invalid argument
[ 3.921452] init: write_file: Unable to open ‘/dev/cpuctl/cpu.rt_runtime_us’: Permission denied
[ 3.922310] init: write_file: Unable to open ‘/dev/cpuctl/cpu.rt_period_us’: Permission denied
[ 3.925596] init: write_file: Unable to open ‘/dev/cpuctl/bg_non_interactive/cpu.rt_runtime_us’: Permission denied
[ 3.926485] init: write_file: Unable to open ‘/dev/cpuctl/bg_non_interactive/cpu.rt_period_us’: Permission denied
[ 3.941955] SELinux: initialized (dev cgroup, type cgroup), uses genfs_contexts
[ 3.946861] ————[ cut here ]————
[ 3.947817] WARNING: CPU: 0 PID: 1 at /media/hdd/edev/android/brillo-master/hardware/bsp/kernel/common/android-3.18/kernel/cpuset.c:884 cpuset_write_resmask+0x46e/0x5c0()
[ 3.948878] CPU: 0 PID: 1 Comm: init Not tainted 3.18.0+ #1
[ 3.949261] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.7.5.1-0-g8936dbb-20141113_115728-nilsson.home.kraxel.org 04/01/2014
[ 3.950329] 00000000 fa31800f 00000000 f685dec8 c17a7b7d 00000000 f685dee4 c1045792
[ 3.951427] 00000374 c10ad9ce f616ff00 f6193a80 f616f300 f685def4 c104588f 00000009
[ 3.951946] 00000000 f685df14 c10ad9ce 00000001 f616fcc0 00000001 c1a29080 c10ad560
[ 3.952683] Call Trace:
[ 3.953159] [] dump_stack+0x41/0x52
[ 3.953580] [] warn_slowpath_common+0x62/0x80
[ 3.953924] [] ? cpuset_write_resmask+0x46e/0x5c0
[ 3.954381] [] warn_slowpath_null+0xf/0x20
[ 3.954696] [] cpuset_write_resmask+0x46e/0x5c0
[ 3.955035] [] ? cpuset_css_offline+0x70/0x70
[ 3.955521] [] cgroup_file_write+0x3c/0xe0
[ 3.955853] [] ? __kmalloc+0xa5/0x140
[ 3.956286] [] ? cgroup_init_cftypes+0xc0/0xc0
[ 3.956620] [] kernfs_fop_write+0xc5/0x150
[ 3.956966] [] ? kernfs_vma_page_mkwrite+0x70/0x70
[ 3.957477] [] vfs_write+0x95/0x1d0
[ 3.957802] [] SyS_write+0x4a/0xb0
[ 3.958078] [] syscall_call+0x7/0x7
[ 3.958705] —[ end trace 34a6ebb916821bfe ]—
[ 3.960845] ————[ cut here ]————
[ 3.961269] WARNING: CPU: 0 PID: 1 at /media/hdd/edev/android/brillo-master/hardware/bsp/kernel/common/android-3.18/kernel/cpuset.c:1140 cpuset_write_resmask+0x1b7/0x5c0()
[ 3.962454] CPU: 0 PID: 1 Comm: init Tainted: G W 3.18.0+ #1
[ 3.962855] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.7.5.1-0-g8936dbb-20141113_115728-nilsson.home.kraxel.org 04/01/2014
[ 3.963708] 00000000 fa31800f 00000000 f685dec8 c17a7b7d 00000000 f685dee4 c1045792
[ 3.964489] 00000474 c10ad717 f616ff00 f6193a80 f616f300 f685def4 c104588f 00000009
[ 3.965002] 00000000 f685df14 c10ad717 00000000 f616f480 00000001 c1a29104 c10ad560
[ 3.967218] Call Trace:
[ 3.967403] [] dump_stack+0x41/0x52
[ 3.967680] [] warn_slowpath_common+0x62/0x80
[ 3.968074] [] ? cpuset_write_resmask+0x1b7/0x5c0
[ 3.968738] [] warn_slowpath_null+0xf/0x20
[ 3.969185] [] cpuset_write_resmask+0x1b7/0x5c0
[ 3.969513] [] ? cpuset_css_offline+0x70/0x70
[ 3.969845] [] cgroup_file_write+0x3c/0xe0
[ 3.970253] [] ? __kmalloc+0xa5/0x140
[ 3.970534] [] ? cgroup_init_cftypes+0xc0/0xc0
[ 3.970855] [] kernfs_fop_write+0xc5/0x150
[ 3.971252] [] ? kernfs_vma_page_mkwrite+0x70/0x70
[ 3.971591] [] vfs_write+0x95/0x1d0
[ 3.971858] [] SyS_write+0x4a/0xb0
[ 3.972227] [] syscall_call+0x7/0x7
[ 3.972492] —[ end trace 34a6ebb916821bff ]—
[ 3.976601] init: write_file: Unable to open ‘/proc/sys/abi/swp’: No such file or directory
[ 3.977757] init: /dev/hw_random not found
[ 3.988367] EXT4-fs (vdb): Ignoring removed nomblk_io_submit option
[ 3.995811] EXT4-fs (vdb): mounted filesystem with ordered data mode. Opts: errors=remount-ro,nomblk_io_submit
[ 3.996688] SELinux: initialized (dev vdb, type ext4), uses xattr
[ 3.997276] fs_mgr: check_fs(): mount(/dev/block/vdb,/data,ext4)=0: Success
[ 4.044239] fs_mgr: check_fs(): unmount(/data) succeeded
[ 4.046378] fs_mgr: Not running /system/bin/e2fsck on /dev/block/vdb (executable not in system image)
[ 4.048475] EXT4-fs (vdb): Ignoring removed nomblk_io_submit option
[ 4.056938] EXT4-fs (vdb): mounted filesystem with ordered data mode. Opts: nomblk_io_submit,errors=panic
[ 4.058544] SELinux: initialized (dev vdb, type ext4), uses xattr
[ 4.059041] fs_mgr: __mount(source=/dev/block/vdb,target=/data,type=ext4)=0
[ 4.065376] init (1168) used greatest stack depth: 6376 bytes left
[ 4.074890] init: (Parsing /system/etc/init/avahi-daemon.rc took 0.00s.)
[ 4.078605] init: (Parsing /system/etc/init/brillo.rc took 0.00s.)
[ 4.080801] init: (Parsing /system/etc/init/crash_reporter.rc took 0.00s.)
[ 4.082297] init: (Parsing /system/etc/init/firewalld.rc took 0.00s.)
[ 4.083550] init: (Parsing /system/etc/init/keystore.rc took 0.00s.)
[ 4.085184] init: (Parsing /system/etc/init/logcatd.rc took 0.00s.)
[ 4.087003] init: (Parsing /system/etc/init/logd.rc took 0.00s.)
[ 4.088444] init: (Parsing /system/etc/init/mediaserver.rc took 0.00s.)
[ 4.089697] init: (Parsing /system/etc/init/metrics_collector.rc took 0.00s.)
[ 4.090875] init: (Parsing /system/etc/init/metricsd.rc took 0.00s.)
[ 4.092361] init: (Parsing /system/etc/init/nativepowerman.rc took 0.00s.)
[ 4.093459] init: (Parsing /system/etc/init/perfprofd.rc took 0.00s.)
[ 4.094425] init: (Parsing /system/etc/init/sensorservice.rc took 0.00s.)
[ 4.095787] init: (Parsing /system/etc/init/servicemanager.rc took 0.00s.)
[ 4.097297] init: (Parsing /system/etc/init/shill.rc took 0.00s.)
[ 4.098771] init: (Parsing /system/etc/init/tlsdated.rc took 0.00s.)
[ 4.100223] init: (Parsing /system/etc/init/update_engine-dbus.rc took 0.00s.)
[ 4.101608] init: (Parsing /system/etc/init/weaved.rc took 0.00s.)
[ 4.102934] init: (Parsing /system/etc/init/webservd.rc took 0.00s.)
[ 4.114555] init: Starting service ‘logd’…
[ 4.118875] EXT4-fs (vda): re-mounted. Opts: (null)
[ 4.140076] init: (Loading properties from /system/build.prop took 0.00s.)
[ 4.144709] init: (Loading properties from /vendor/build.prop took 0.00s.)
[ 4.145353] init: (Loading properties from /factory/factory.prop took 0.00s.)
[ 4.147557] fs_mgr: Cannot open file /fstab.qemu
[ 4.147994] init: unable to read fstab /fstab.qemu: No such file or directory
[ 4.161572] init: do_start: Service vold not found
[ 4.190684] init: Not bootcharting.
[ 4.252415] random: logd urandom read with 11 bits of entropy available
[ 4.417431] init: cannot find ‘/system/bin/tzdatacheck’ (No such file or directory), disabling ‘exec 1 (/system/bin/tzdatacheck)’
[ 4.441966] init: (Loading properties from /data/local.prop took 0.00s.)
[ 4.443490] init: Starting service ‘logd-reinit’…
[ 4.484825] init: cannot find ‘/sbin/healthd’ (No such file or directory), disabling ‘healthd’
[ 4.489712] init: Starting service ‘wifi-setup’…
[ 4.495951] init: Starting service ‘dbus’…
[ 4.509599] init: Starting service ‘servicemanager’…
[ 4.524524] init: Starting service ‘initnetwork’…
[ 4.547731] init: Starting service ‘firewall-setup’…
[ 4.600328] init: Starting service ‘console’…
[ 4.625652] init: Starting service ‘adbd’…
[ 4.652013] init: cannot find ‘/system/bin/install-recovery.sh’ (No such file or directory), disabling ‘flash_recovery’
[ 4.653863] init: Starting service ‘avahi-daemon’…
[ 4.691713] init: Starting service ‘keystore’…
[ 4.744386] init: Starting service ‘media’…
[ 4.799800] init: Starting service ‘nativepowerman’…
[ 4.842000] init: Starting service ‘sensorservice’…
[ 4.901436] init: Starting service ‘wpa_supplicant’…
[ 4.944805] init: Starting service ‘crash_reporter’…
[ 4.989070] init: Starting service ‘crash_sender’…
[ 5.064776] init: Starting service ‘metricscollector’…
[ 5.118916] init: Starting service ‘metricsd’…
[ 5.208750] init: Starting service ‘perfprofd’…
[ 5.268018] init: Starting service ‘shill’…
[ 5.334890] init: Starting service ‘tlsdated’…
[ 5.444558] init: Starting service ‘update_engine’…
[ 5.524858] init: Starting service ‘weaved’…
[ 5.595089] init: Starting service ‘webservd’…
[ 5.848418] init: write_file: Unable to open ‘/sys/class/android_usb/android0/enable’: No such file or directory
[ 5.871453] init: write_file: Unable to open ‘/sys/class/android_usb/android0/idVendor’: No such file or directory
[ 5.892852] init: write_file: Unable to open ‘/sys/class/android_usb/android0/idProduct’: No such file or directory
[ 5.913237] init: write_file: Unable to open ‘/sys/class/android_usb/android0/functions’: No such file or directory
[ 5.913928] init: write_file: Unable to open ‘/sys/class/android_usb/android0/enable’: No such file or directory
[ 6.035576] init: Service ‘logd-reinit’ (pid 1177) exited with status 145
[ 6.081871] init: write_file: Unable to open ‘/sys/class/android_usb/android0/enable’: No such file or directory
[ 6.115634] init: write_file: Unable to open ‘/sys/class/android_usb/android0/idVendor’: No such file or directory
[ 6.136657] init: write_file: Unable to open ‘/sys/class/android_usb/android0/idProduct’: No such file or directory
[ 6.167701] init: write_file: Unable to open ‘/sys/class/android_usb/android0/functions’: No such file or directory
[ 6.203480] init: write_file: Unable to open ‘/sys/class/android_usb/android0/enable’: No such file or directory
[ 8.691342] crash_reporter (1191) used greatest stack depth: 6316 bytes left
[ 8.693299] init: Service ‘crash_reporter’ (pid 1191) exited with status 0
[ 8.696058] audit: type=1400 audit(1448275810.693:4): avc: denied { sys_module } for pid=1202 comm=”ifconfig” capability=16 scontext=u:r:brillo_setup:s0 tcontext=u:r:brillo_setup:s0 tclass=capability permissive=0
[ 10.727869] init: Service ‘wifi-setup’ (pid 1178) exited with status 0
[ 14.844780] capability: warning: `wpa_supplicant’ uses 32-bit capabilities (legacy support in use)
[ 15.517398] logd.auditd: start
[ 15.883205] logd.klogd: 15517854148
[ 15.989289] tlsdate-helper (1222) used greatest stack depth: 6132 bytes left
[ 16.066262] route (1208) used greatest stack depth: 5920 bytes left
[ 17.096653] init: Service ‘initnetwork’ (pid 1181) exited with status 126
[ 22.925006] init: Starting service ‘firewalld’…
[ 22.959332] init: Service ‘firewall-setup’ (pid 1182) exited with status 0
[ 24.005450] type=1400 audit(1448275817.466:5): avc: denied { dac_override } for pid=1181 comm=”initnetwork.sh” capability=1 scontext=u:r:brillo_setup:s0 tcontext=u:r:brillo_setup:s0 tclass=capability permissive=0

Some web servers, Weave daemon, a firewall, sensor monitor, adb daemon, etc.. but no ART runtime as found in the full Android. It actually looks more like a light weight Linux distribution, than something based on Android, as the root file system still remains Android like with system, vendor, data… directories.

MIPS Creator Ci40 Development Board Powered by cXT200 SoC Launched for $53 on Kickstarter

$
0
0

Last year, Imagination Technologies launched their first community development board with MIPS Creator CI20 powered by Ingenic JZ4780 dual core MIPS processor running both Android and Linux, and now supported by various projects. The company has been teasing about its MIPS Creatort Ci40 for a few weeks, and was already announced as the MIPS platform of choice for Google Brillo operating system, but the board has now officially been launched via a Kickstarter campaign where you can get the board for $53, as well as some add-on boards.

MIPS_Creator_CI40But instead of using a processor from one of their partner, Imagination just designed their own MIPS interAptiv SoC for the board.

Creator Ci40 board specifications:

  • SoC – Imagination Technologies Creator cXT200 with 2x MIPS interAptiv core @ 550MHz, 512KB L2 cache, and an Ensigma C4500 RPU (for 802.11ac/ BT 4.1 LE)
  • System Memory – 256 MB DDR3
  • Storage – 512 MB NAND flash, micro SD card slot
  • Connectivity – Ethernet, 802.11ac 2×2 WiFi, Bluetooth 4.1, 802.15.4 radio for 6LoWPAN
  • USB – 1x micro USB OTG port
  • Audio – 1 x 3.5mm input/output jack, 1 x S/PDIF input/output connector
  • Expansion Headers:
    • 40-pin Raspberry Pi compatible header
    • 2x mikroBus headers
    • Other undocumented headers
    • I/Os include: 32x GPIO, 4x PWM, 1x SPI, 2x UART, 2x I2C, and 5x ADC.
  • Debugging – JTAG/EJTAG, 1x micro USB port for serial console (TBC)
  • Security – TPM chip
  • Misc – 9x indicator LEDs
  • Power Supply – 9V via power barrel, or 5V via micro USB port
  • Dimensions – 100 mm x 106 mm
cXT200 Block Diagram

cXT200 Block Diagram

The board will support Linux (buildroot), Brillo OS, Debian, and OpenWRT. Optimized GNU tools and library will also be provided for the MIPS platform, and the board will have access to the cloud via the company’s FlowCloud IoT framework. Some code sample for the latter  have already been provided on github.

Creator Ci40 Open Source Software Stack (Click to Enlarge)

Creator Ci40 Open Source Software Stack (Click to Enlarge)

In Internet of Things projects you also need “things”, and not only a gateway, so the company is also offering Creator Ci40 IoT kit with Ci40 board, as well as two MikroElektronika’s 6LoWPAN Clicker boards  powered by 2 AAA batteries acting as nodes (i.e. things), and three Click boards fitting in mikroBus sockets.

Credtor Ci40 IoT Kit (Click to Enlarge)

Credtor Ci40 IoT Kit (Click to Enlarge)

The Clicker boards are powered by a MIPS based Pic32MX micro-controller, and run Contiki real-time operating system. As reported in my post about HummingBoard Gate board, there are over 150 Click (add-on) boards to both Ci40 and clickers board functionality can be augmented by any of these standard add-on boards by MikroElectronika.

While Creator Ci40 board itself is 35 GBP (~$53), you could consider getting the IoT kit instead for 70 GBP ($106). Shipping is not included, and they charge a flat fee to any destination ranging from 5 GBP for th board only to 12 GBP for the various kits. Delivery is scheduled for April 2016. You can also find more details on Imagination’s Creator Ci40 product page.

Inforce 6309 micro SBC is Software Compatible with DragonBoard 410c Board, Includes an Ethernet Port

$
0
0

I’ve recently written a review of DragonBoard 410c with Android, one of the first board part of Linaro’s 96Boards initiative that’s supposed to get Android and Debian distributions with recent Linux kernel & U-Boot, together with full source code. Inforce Computing has now launched Inforce 6309 micro Single Board Computer (SBC) with the same footprint, albeit different connectors’ placements, and software compatible with DragonBoard 410c development board powered by the same Qualcomm Snapdragon 410 processor. The board targets applications such as industrial automation, “sophisticated” IoE devices, medical devices, augmented reality computing, and robotics and drones.

Inforce_6309_micro_SBCInforce 6309 micro single board computer specifications:

  • SoC- Qualcomm Snapdragon 410 (APQ8016) quad-core ARM CortexA53 @ 1.2 GHz with Adreno 306 GPU and Hexagon QDSP6 @ 700 MHz
  • System Memory – 1GB LPDDR3 @ 533MHz, Single-channel 32-bit (4.2GBps)
  • Storage – 8GB eMMC flash (eMCP package with RAM) + micro SD slot
  • Video Output / Display IF – micro HDMI up to 1080p30; LVDS and touch screen up to 1920×1200 (24-bit) or 2048×1536
  • Audio – HDMI, combo jack for headphone and microphone, PMM8916 audio codec
  • Connectivity – Gigabit Ethernet (USB 2.0 to GbE bridge), 802.11 b/g/n WiFi, Bluetooth 4.1 LE, and GPS/GLONASS
  • USB – 2x USB 2.0 host ports, 1x micro USB OTG port
  • Camera – Dual MIPI-CSI2 (4/2 lanes) for dual camera support up to 13MP
  • Serial – Optional RS-485 port via interface card
  • Expansion – 26-pin header with I2C, SPI, I2S, UART and GPIOs
  • Power Supply – 12V/1.5A DC input; optional PoE
  • Dimensions – 85×54 mm
  • Temperature Range – Operating & Storage: -30ºC to +85ºC
Block Diagram (Click to Enlarge)

Block Diagram (Click to Enlarge)

The board size and specifications are similar to DragonBoard 410c, but the board gains Gigabit Ethernet (limited to the USB 2.0 bandwidth), and replaced LS and HS connectors by MIPI-CSI, LVDS and a 26-pin I/O header. The company provides Android Lollipop, Linaro Ubuntu, and ROS operating systems for the board, as well as Qualcomm SDKs (Vuforia, Alljoyn, FastCV, MARE…), and Dronecode open-source UAV. As usual with Inforce Computing, public documentation is limited to the product brief and a short explanation about the SDK, and all other downloads (datasheets, application notes, software released, and reference manuals) are only available to customers.

A development kit based Inforce 6309 micro SBC will soon be available for pre-order for $120 via the product page. Price for the SBC will start at $99 for small quantities.

Add an SSD, WiFi, and RTC to Your Raspberry Pi 2 Board with a $49 CSB502SSD Add-on Board (Crowdfunding)

$
0
0

If you wish your Raspberry Pi 2 could be a little more responsive, including WiFi connectivity and keep the time even when network is not available, and a few extra goodies then Pi 2 Design‘s CSB502SSD add-ons board (Raspberry Pi HAT) could be worth a look.

Raspberry_Pi_SSD

CSB502SSD technical specifications:

  • Storage – mSATA socket for up to 1TB on-board storage via PL2571 USB to SATA bridge controller
  • USB – 2x extra USB 2.0 ports
  • Connectivity – GWF-3M08 WiFi 802.11 b/g/n module (Ralink RT5370) with IPEX connector and up to 150 Mbps connection.
  • Real Time Clock – DS1339 with 16mm coin cell battery backup and programmable alarm.
  • Sensors – 1-Wire DS18B20 temperature sensor to monitor the health of SSD drive. 64-bit ID to identify the shield
  • Power Supply – 8V-24V DC input (Up to 27.5W) for peripherals and Raspberry Pi 2.
  • Dimensions – Full size Raspberry Pi 2 I/O Shield

Since the SSD data transfer will take place over USB 2.0, you may not not get much higher throughput compared to a USB 2.0 flash drive or a good class 10 SD card, however as I found out in Voyo V2 review, random write performance for USB flash drive are dismissal, and a SSD connected via USB was about 120 times faster for random writes. So any applications that requires good random writes, for example frequent databases writes, should gain in performance.

The add-on board / shield has now launched on Kickstarter, where you can pledge $49 to get it together with the micro USB to USB cable, a power supply, Wifi antenna and mounting posts, but without an SSD. Shipping is not included and amounts to $10 to the US, and $28 to the rest of the world (but the price should go down to $18 soon, so you may want to wait).


Xiaomi MiPad 2 Tablet Runs Android or Windows 10 on Intel Atom x5-Z8500 Processor for $156 and Up

$
0
0

Xiaomi launched their first MiPad tablet last year with an Nvidia Tegra K1 processor and running Android, and the company recently introduced an update with MiPad 2, with similar features to the original one, but replacing the ARM processor by an Intel Atom x5-Z8500 quad core “Cherry Trail” processor supporting both Android and Windows.

Xiaomi_MiPad_2Gizmo China made a comparison table between the two model’s specifications which I reproduced and edited below.

Model Mi Pad Mi Pad 2
Processor Nividia Tegra K1 quad core Cortex A15 @ 2.2 GHz Intel Atom X5-Z8500 quad core x86 up to 2.24GHz
RAM 2 GB LPDDR3
Internal Storage 16 GB/32 GB + micro SD slot 16 GB/64 GB, no micro SD slot
Display 7.9″ (2048 x 1536 pixels)
Connectivity 802.11ac 2×2 Wi-Fi + Bluetooth 4.0 802.11ac 2×2 Wi-Fi + Bluetooth 4.1
USB micro USB USB type-C
Camera 8 MP/ 5 MP
Battery 6700 mAh 6190 mAh
Dimensions 202.1 x 135.4 x 8.5 mm 200.4 x 132.6 x 6.95mm
Weight 360 grams 322 grams
OS Android OS Android OS/ Windows 10

So beside the processor difference, the new MiPad is lighter, and thinner, replaces the micro USB port by a new USB type-C reversible port, loses the micro SD slot, and comes with a smaller battery. I understand that MiPad 2 does not dual boot, but instead supports either Android (MIUI 7) or Windows 10.

MiPad_2_Battery_LifeMiPad 2 will launch in China for 999 RMB ($156) for the 16GB version (November 27) and 1,299 RMB ($203) for the 64GB version, available by the end of December.

Raspberry Pi Zero is a $5 Board Based on Broadcom BCM2835 Processor

$
0
0

The Raspberry Pi board had some serious competition price-wise with products such as Orange Pi PC, NanoPi, or even C.H.I.P, but the Raspberry Pi foundation has lowered the price barrier even further with the Raspberry Pi Zero board, based on the same processor as the original Raspberry Pi (model 1) boards but clocked at a higher speed, and in a much smaller form factor, and launching at an unbeatable price: $5.

Raspberry_Pi_ZeroRaspberry Pi Zero specifications:

  • Processor – Broadcomm BCM2835 ARM11 processor @ 1GHz with VideoCore IV GPU
  • System – 512MB RAM
  • Storage – microSD slot
  • Video Output – mini HDMI port and composite video (via 2 unpopulated  pins)
  • USB – 2x micro USB OTG ports for data and power
  • Expansion – 40-pin through-holes
  • Power Supply – 5V via micro USB port
  • Power Consumption – 0.5-0.7W (100-140mA at 5.09V) according to Raspi.TV
  • Dimensions – 65mm x 30mm x 5mm

The board is obviously software compatible with Raspberry Pi Model B/B+ and A+, and it’s a pretty exciting development.

Raspberry_Pi_Zero_Dollar_BillThe board is available in limited supplies in the UK via sites like Element14 or Pimoroni, and in the US via Microcenter and Adafruit. The board is also available for free with the December issue of The MagPi in UK stores.

If you find $5 is just too cheap, or Raspberry Pi Zero is out of stock, or you simply don’t happen to live in the US or UK, you can also fall back to Allwinner R8 based C.H.I.P board that’s available for pre-order on Cyber Monday for $8 + shipping.

ESP32 Module Schematics and Board Files

$
0
0

Espressif teased about their ESP32 WiSoC with WiFi and Bluetooth LE a few weeks ago in a letter addressed to developers, but did not release that much information. The company has now released some documents in the forums (registration required) concerning ESP32 module  including PCB processing requirement, schematics and PCB layout, and bill of materials.

ESP32 Module Pinout

ESP31 / ESP32 Module Pinout

The very first modules will actually be based on ESP31 processor, which only slightly differs from ESP32 with some swapped pins. The BoM is pretty small with several capacitors and resistors, one inductance, a 26 MHz crystal, ESP31, and a Gigadevice flash.

ESP32_Schematic

The schematics have been designed with Orcad 16.6, so if you don’t have the program, you can read the schematics with Orcad 16.6 Lite, which is free to download. I’ve also printed the schematics to a PDF file.  I’m not sure how to open the .pcb file which should be the module’s PCB layout.

Segger emPower is an embOS RTOS Evaluation Board with a J-Link OB Debug Interface

$
0
0
Home > Freescale i.MX, Hardware, Operating Systems > Segger emPower is an embOS RTOS Evaluation Board with a J-Link OB Debug Interface

Segger emPower is an embOS RTOS Evaluation Board with a J-Link OB Debug Interface

Segger, a company specializing in embedded software and hardware debugging tools, has recently launched Segger emPower, an evaluation board powered by Freescale Kinetis K66 Cortex M-4 MCU and including a J-LInk OB debug probe (JTAG/SWD), specially designed to evaluate the company’s embOS real-time operating system.

Segger_emPoweremPower board hardware specifications:

  • MCU – Freescale Kinetis K66 (MK66FN2M0VMD18) ARM Cortex M4F MCU @ 180MHz with with 256KB SRAM and 2MB flash memory
  • Storage – 1Gbit NAND Flash + micro SD card connector
  • Display I/F – 20-pin display adapter connector (5 V/3.3 V, SPI, PWM for backlight control) for small TFT displays
  • Connectivity – Fast Ethernet
  • USB – 1x USB device, 1x USB host (Full speed)
  • Debugging
    • On-board debug probe J-Link-OB with drag & drop (STM32F072, mini A/B-type connector); SWD/SWO only, no CDC/VCOM port support
    • External debug interface (19-pin Cortex-M) including trace
  • Expansion
  • Misc – Joystick 4(+1)-way, 1x “FIRE” button, 1x RESET button, rotary input (potentiometer to ADC), 4x bicolor LEDs
  • Power Supply – 5V via USB host port
  • Dimensions – 99 mm x 80 mm
Block Diagram (Click to Enlarge)

Block Diagram (Click to Enlarge)

The board is pre-loaded with SEGGER’s embOS real-time operating system, and evaluation versions of emFile file systems, emWin graphics library , as well as emUSB Host & Device stack, and TCP/IP stack embOS/IP are also included.

Some of embOS features include:

  • Zero interrupt latency time.
  • High resolution time measurement (more accurate than tick).
  • Power management: Unused CPU time can automatically be spent in halt mode, minimizing power consumption.
  • Full interrupt support: Most API functions can be used from within the Interrupt Service Routines (ISRs).
  • Automatic resolution of priority inversion.
  • Unlimited priorities: Every task can have an individual priority => the response of tasks can be precisely defined according to the requirements of the application.
  • Unlimited number of tasks, event flags,semaphores, message queues, mailboxes and software timers.
  • Time resolution tick can be freely selected (default is 1ms).
  • Nested interrupts are permitted.
  • High precision per task profiling. Real time kernel viewer (embOSView) included.
  • Debug build performs runtime checks, simplifying development.
  • Support for ARM, ColdFire, AVR, Reneasas H8/M16/M32, PIC32, etc…
embOSView Screenshot (Click to Enlarge)

embOSView Screenshot (Click to Enlarge)

emPower board can be purchased for 98 Euros + shipping. More information is available on Segger emPower and embOS RTOS product pages.

Graperain Introduces G8916 Qualcomm Snapdragon 410 SoM and LTE Mobile Development Board

$
0
0

Qualcomm applications processors used to be found mostly in consumer devices like smartphones and tablets, but recently the company has expended their use to the embedded space, and for example, we’ve seen Snapdragon 410 64-bit ARM processor used in DragonBoard 410c board, Intrinsyc Open-Q 410 SoM, Inforce 6309 SBC, and today I’m going to have a look at Graperain G8916 system-on-module that’s also integrated into a 4G/LTE mobile development platform.

Snapdragon_410_som

G6916 CPU module specifications:

  • SoC – Qualcomm Snapdragon 410 (MSM8916) quad core Cortex A53 processor @up to 1.4GHz with Adreno 306 GPU
  • System Memory – 1GB DDR3 (2GB optional)
  • Storage – 8GB eMMC 4.5 flash (16 and 32GB optional) + micro SD support up to 128GB via I/Os
  • Connectivity – 802.11 b/g/n WiFi, Bluetooth 4.0 LE, FM, NFC/RFID, GPS/GLONASS with 4x on-module antenna connectors.
  • Cellular Connectivity
    • TD-LTE – B38/B39/B40/B41; FDD-LTE – B1/B2/B5/B/B26
    • TD-SCDMA -B34/B39
    • GSM – 850/900/1800/1900
    • CDMA – 1x/EVDO BC0
  • Audio – Unnamed Audio codec with signals for two microphones, headset and speakers
  • Other I/O via half through holes around the module:
    • 4x I2C, 1x PWM, 2x ADC
    • 2x SIM card
    • 1x SD card
    • 1x USB OTG, 2x USB host
    • 20x GPIO
    • Camera – MIPI-CSI up to 12MP rear camera, and 5MP front-facing camera.
    • LCD interface up to 1920×1800
  • Power Supply – N/A
  • Dimensions – 56.5 x 40.5 mm
Snapdragon 410 SoM Block Diagram (Click to Enlarge)

Snapdragon 410 SoM Block Diagram (Best Resolution I could get from them).

The hardware specifications should be for reference only, as the company has very poor documentation about their module, and exact details, e.g. LTE frequency bands, differ from document to documents. There’s absolutely zero information about software support, so I had to ask again, and they support Android 4.4, and no other operating systems for now.

The company also has a mobile development platform (M9) using the module.Graperain_Snapdragon_410_Mobile_Development_Platform

Snapdragon_410_som_development_board No details technical could be provided in time for this article however.

G8916 module sample price is $115, and less in quantities. More details, but not that many, might be found on Graperain G8916 SoM page.

MINIX NEO U1 Android Media Hub Combines Amlogic S905 Processor with 2GB RAM, 802.11ac WiFi

$
0
0
Home > AMLogic, Android, Hardware > MINIX NEO U1 Android Media Hub Combines Amlogic S905 Processor with 2GB RAM, 802.11ac WiFi

MINIX NEO U1 Android Media Hub Combines Amlogic S905 Processor with 2GB RAM, 802.11ac WiFi

MINIX has posted several graphics on their Facebook page about a new NEO U1 media hub in the last few days. The company will launch the new model which include 2GB RAM, and 802.11ac WiFi next Friday (December 4, 2015) for $129.90 on their Amazon store, and other official resellers.

Minix_Neo_U1MINIX NEO U1 specifications:

  • SoC –  Amlogic S905 quad core ARM Cortex-A53 @ up to 2.0GHz with penta-core Mali-450MP GPU @ 750 MHz
  • System Memory – 2GB DDR3
  • Storage – 16GB eMMC 5.0 flash + micro SD card slot
  • Video Output – HDMI 2.0 up to 4K @ 60 Hz with HDMI CEC support
  • Audio – HDMI, optical S/PDIF, and 3.5mm headphone and microphone jacks
  • Connectivity – Gigabit Ethernet, 802.11 b/g/n/ac Wi-Fi (2×2 MIMO) and Bluetooth 4.1
  • USB – 3x USB 2.0 host ports, 1x micro USB OTG port
  • Misc – Power button, IR receiver, Kensington lock ready
  • Power Supply –  5V/3A
  • Dimensions & Weight – N/A

MINIX_NEO_U1_Remote_Control

The device will run Android 5.1 as on other Amlogic S905 TV boxes, but likely with the usual MINIX user interface. It’ one of the Amlogic S905 TV box with the highest specifications on the market, and similar to Ugoos AM1, but with Bluetooth 4.1 support, an extra USB OTG port, and a Kensington lock.

Via HDBlog.it

H.264 & H.265 4K Video Playback on Amlogic S905 Android TV Box

$
0
0
Home > AMLogic, Android, Hardware, Video > H.264 & H.265 4K Video Playback on Amlogic S905 Android TV Box

H.264 & H.265 4K Video Playback on Amlogic S905 Android TV Box

I’ve almost completed my review of Videostrong K1 Plus Android box powered by Amlogic S905, and while there are many shortcomings, 4K video playback is actually pretty good with Android’s Video Player (Kodi is not really usable @ 4K).

4K_10-bit_H.265_Video

4K 10-bit HEVC Video Played in Android Video Player

I connected the device to LG 42UB820T 4K UHD TV, and set video output to 2160p @ 60Hz, and went through several video samples:

  • Beauty_3840x2160_120fps_420_8bit_HEVC_MP4.mp4 (H.265 @ 30 fps – No audio) – OK
  • big_buck_bunny_4k_H264_30fps.mp4 (H.264 @ 30 fps – MPEG1/2 and AC3 audio) – OK
  • big_buck_bunny_4k_H264_60fps.mp4 (H.264 @ 60 fps – MPEG1/2 and AC3 audio) – Video looks somewhat OK, but big audio delay or AV sync issue.
  • BT.2020.20140602.ts (H.265 Rec.2020 compliant – AAC audio) – OK (First time I can play this video on any hardware).
  • Fifa_WorldCup2014_Uruguay-Colombia_4K-x265.mp4 (H.265 @ 60 fps – AC3) – Video is very good, but no audio
  • MHD_2013_2160p_ShowReel_R_9000f_24fps_RMN_QP23_10b.mkv (10-bit HEVC @ 24 fps – no audio) – OK
  • phfx_4KHD_VP9TestFootage.webm (VP9) – 3 to 4 fps (software decode)
  • Samsung_UHD_Dubai_10-bit_HEVC_51.4Mbps.ts (10-bit HEVC / MPEG-4 AAC) – Perfect!
  • Sintel.2010.4k.mkv (H.264 @ 24 fps – AC3) – Video OK but no audio
  • Astra-11479_V_22000-Canal+ UHD Demo 42.6 Mbps bitrate.ts (10-bit H.265 from DVB-S2 stream) – Most of the time OK, but it will freeze and the same exact point every time for several seconds.

You can watch the tests in the video below.

[embedded content]

I have to say I’m pretty pleased with 4K support on Amlogic S905 so far. 4K H.264 @ 60 fps and VP9 are simply not supported by the VPU in Amlogic S905 SoC, and the only problem I’ve seen with regards to video was with the DVB-S2 stream bug, which could be software or hardware, with the latter requiring a new silicon revision. Only time will tell. That’s not to say there’s still some work to be done, as DTS and Dolby are not supported in the device I tried, and if you are interested in Kodi, you’ll need to be a little more patient.

You can find links to the videos in the comment section of this list of video samples.


K1 Plus Amlogic S905 TV Box Review

$
0
0

Videostrong KI Plus is one of the first Amlogic S905 TV boxes to be launched on the market, and it also happens to be one of cheapest model selling for around $45 on various sites, and it’s even available for $39.99 on GearBest for Black Friday / Cyber Monday. I’ve posted the specifications and pictures of the device previously, and after updating the firmware, I’ve finally completed the review.

First Boot, Settings and First Impressions

As usual, I’ve connected a whole bunch of cables and peripherals to the device to make the power supply can handle it, including a USB hard drive, a USB webcam, a USB keyboard, a USB hub with two RF dongles for Tronsmart Mars G01 gamepad and MeLE F10 Deluxe air mouse, as well as a HDMI, optical audio and Ethernet cables, and a speaker connected to the 3.5mm AV jack and powered by one of the USB port of the device. Turn on the power, and the device will boot automatically (no need to press the power button), with a typical boot taking around 48 seconds.

Click for Original Size

Click for Original Size

The launcher is quite basic, which can be advantage for a TV interface, with the time, a list of customizable shortcuts which including IPFox and Private Live TV by default, and 5 icons on the bottom for Kodi 15.2, Explorer file manager, the list of apps, settings, and a web browser. There are also some icon on the bottom right for networking and storage. IPFox asks you to scan a QR code to buy something, and Private Live TV will download an IPTV plugin and work out of the box with various TV channels including Sky Sports F1…

Click for Original Size

Click for Original Size

I quickly tried one of the streams and it worked OK.

The settings’ user interface is basically the same as found as on Android 5.1 Amlogic S812 TV boxes such as WeTek Core, minus some features like automatic frame rate switching.

Click to Enlarge

Click to Enlarge

The most interesting settings include:

  • Network – WiFi, Ethernet, and VPN configuration
  • Display
    • Screen resolution: Auto, 480p-60Hz, 576p-50Hz, 720p 50/60Hz, 1080i 50/60Hz, 1080p 24/50/60Hz, 4K2K 24/25/30/50/60Hz or SMPTE
    • Screen position
    • Screen rotation (middle port, force land, original)
  • Sound – System sound (On/Off), and Digital sounds (Auto detection, PCM, HDMI or SPDIF)
  • Preferences – HDMI CEC (But not working: “This remote device does not support CEC”), and Play back settings with “HDMI self-adaption” On/Off. I don’t really understand what that means…

I had no problem to connect to my WiFi router, and setting video to 4k2k 60Hz also worked perfectly via Onkyo TX-NR636 AV receiver or LG UHD TV. However, the box did not always keep my video output settings, often falling back to 1080p50. I only tested the AV port by connecting it to my speakers, and it worked fine with both HDMI audio and stereo audio outputted at the same time.

About_Mediabox_K1_PlusYou can get to Lollipop Android settings by selecting More Settings. Bluetooth is not built-in into the device, and is completely missing from the settings, so even if you decided to connect a Bluetooth USB dongle it would not work. All other usual settings appear to be here including Printing, Language & input, accessibility and so on. A single 4.66GB partition is used for both app and data with around 4.21GB free space.

The “About Mediabox” section reports KI Plus model running Android 5.1.1 on top of Linux kernel 3.14.29. There’s also a link to the Update&Backup app in this section, but OTA firmware update is not enabled. The sample was sent to my by a manufacturer (Videostrong), and they probably rely on their customers to handle this. This firmware is not rooted by default.

The IR remote control work pretty well, and I could use it reliably as far as 10 meters. The IR learning function is also doing its job and I could program with TV’s remote control Volume, power, and TV input keys. I have no used the remote that much since I prefer using MeLE F10 Deluxe remote control in Android that’s much more user friendly that IR remotes. Since the status and notification bars are missing, I had to use the Home key on the IR remote during testing…

Google Play Store did not work well at all the first time, with most application being incompatible with this device. That’s why I delayed the review, and after installing a new firmware, everything works pretty well. Applications that require telephony, Bluetooth, and GPS can’t be installed, but that’s fine, as well as the ones which can’t be installed where I live (country limitations). Finally I installed Amazon Underground to load and play Riptide GP2 3D racing game.

Power handling has been implemented correctly as I could cleanly power off the device with either the power button on the unit and the remote control. The remote control can also be used to power on the device. There’s no standby mode, so the device will fully boot each time you turn it on.

For those interested in power consumption, I’ve done some measurements both without USB devices, and one USB hard drive in two modes:

  • Power off – 1.3 Watt
  • Idle – 3.2 ~ 3.4 Watts
  • Power off + HDD – 1.3 Watt
  • Idle + HDD – 6.1 ~ 7.4 Watts

There’s still some residual power used in power off mode, but at least the USB ports are turned off.

Temperature is under control most of the time, except possibly when playing games. I measured 42°C and 53°C on the top and bottom of the enclosure after running Antutu 5.7, but after playing Riptide GP2 for about 15 minutes the temperature went up to 50°C and 62°C, and I noticed a lower frame rate in the game.

After updating the firmware, the first impressions were quite good, as despite its low cost, the system was responsive, and stable, which everything from networking to video output working fine, except for video output changing randomly? after a power on.

Video Playback on KI Plus

I usually playing videos from a network share over Ethernet and using whatever Kodi version is pre-installed on the device. So far none of manufacturers have used Kodi from Google Play, and Videostrong is no exception. So I have some Kodi 15.2 app in the device with various add-ons.

Amlogic_S905_Kodi_15.2

For some reasons, the resolution is shown as 1280×720 @ 60Hz in the System information when the video output is set to 4k2k-60Hz, and despite the framebuffer being set to 1920×1080 as we’ve seen with some of the screenshots above.

Kodi_1280x720But when I went ahead with testing videos samples found on linaro website, I realized something was clearly wrong:

  • H.264 codec / MP4 container (Big Buck Bunny) – 480p/720p/1080p – Letterboxed
  • MPEG2 codec / MPG container –  1080p – Letterboxed
  • MPEG4 codec, AVI container 1080p – Letterboxed
  • VC1 codec (WMV) – 1080p – Letterboxed
  • Real Media (RMVB), 720p / 5Mbps – OK
  • WebM / VP8 – OK
  • H.265 codec / MPEG TS container (1080p) – Letterboxed
  • WebM / VP9 (no audio in video) – OK

So while all videos could play, most of them would be letterboxed.

Kodi_Letterbox_Amlogic_S905
So with this bug in mind, and my contacts telling me either Amlogic had not spent much resources on Kodi this time, or that many patchsets were still submitted to Kodi to fix Amlogic S905 support, I decided to give up on Kodi on this device, and instead do all my testing with Video Player app in Android. That means you’ll either need to wait for Kodi 16, or go with the daily builds.

Later, I still decided to give Kodi a try with the “reliability” test, playing a 2-hour 1080p movie… and I worked just fine, with a some 3800 skipped frame reported by Kodi’s log overlay maybe because the mismatch between video output and video frame rate. So I was confused, until I saw the video output bug kicked in to force video out to 1080p50, and the System info reported 1920×1080 @ 50Hz…

Amlogic_S905_1080p_kodiSo that means Kodi 15.2 pre-loaded in the box works at 1080p resolution, but has a bug at 4K. VideoStrong should provide a 4K TV to their developers…

I did not re-test the videos at 1080p in Kodi 15.2, as I’m expecting 2 to 3 more Amlogic S905 TV boxes, and I’ll ahve plenty of opportunities to test Kodi on Amlogic S905, so instead I’ll report results in Video Player, using Ethernet, unless otherwise stated.

Linaro samples, plus Elecard H.265, and a low res VP9 video:

  • H.264 codec / MP4 container (Big Buck Bunny) – 1080p – OK
  • MPEG2 codec / MPG container –  1080p – OK
  • MPEG4 codec, AVI container 1080p – OK
  • VC1 codec (WMV) – 1080p – OK
  • Real Media (RMVB), 720p / 5Mbps – OK
  • WebM / VP8 – OK
  • H.265 codec / MPEG TS container (1080p) – OK
  • WebM / VP9 (no audio in video) – OK

I started to see some issues, when I switched to some higher bitrate videos :

  • ED_HD.avi – Blackscreen
  • big_buck_bunny_1080p_surround.avi (1080p H.264 – 12 Mbps) – Video OK, but no audio
  • h264_1080p_hp_4.1_40mbps_birds.mkv (40 Mbps) – OK
  • hddvd_demo_17.5Mbps_1080p_VC1.mkv (17.5Mbps) – Could be smoother, and no audio
  • Jellyfish-120-Mbps.mkv (120 Mbps video without audio) – Not very smooth (played from USB hard drive, as Fast Ethernet could not handle this file).

The audio issues are probably due of the lack of DTS and Dolby licenses, and I could confirm it in the audio test below.

Video PCM Output HDMI Pass-through S/PDIF Pass-through
AC3 / Dolby Digital 5.1 No audio OK (Dolby D 5.1) OK (Dolby D 5.1)
E-AC-3 / Dolby Digital+ 5.1 No audio OK (Dolby D 5.1) OK (Dolby D 5.1)
Dolby Digital+ 7.1 No audio No audio Audio Formats Not Supported over S/PDIF
TrueHD 5.1 No audio OK (TrueHD 5.1)
TrueHD 7.1 No audio  OK (TrueHD 7.1)
Dolby Atmos 7.1 No audio Continuous beep and Dolby D 5.1 shows in AVR
DTS HD Master No audio DTS 5.1 only DTS 5.1
DTS HD High Resolution No audio DTS 5.1 only DTS 5.1

So if you don’t have AV receiver you are out of luck to get any audio, unless you use Kodi, which may not work that well right now, or some other app that also decoded DTS and Dolby by software.

One of the main selling point of Amlogic S905 SoC is support for 4K video including 10-bit HEVC, and it’s doing a pretty good job, as long as you play from a USB hard drive:

  • HD.Club-4K-Chimei-inn-60mbps.mp4 – OK from USB HDD, but buffering a lot from network.
  • sintel-2010-4k.mkv – OK, but no audio.
  • Beauty_3840x2160_120fps_420_8bit_HEVC_MP4.mp4 (H.265) –  OK
  • Bosphorus_3840x2160_120fps_420_8bit_HEVC_MP4.mp4 (H.265) – OK
  • Jockey_3840x2160_120fps_420_8bit_HEVC_TS.ts (H.265) – OK from USB HDD, but buffering often from network
  • MHD_2013_2160p_ShowReel_R_9000f_24fps_RMN_QP23_10b.mkv (10-bit HEVC) – OK
  • phfx_4KHD_VP9TestFootage.webm (VP9) – 3 to 4 fps
  • BT.2020.20140602.ts (Rec.2020 compliant video) – OK from USB HDD (first time ever!), but buffering from network, or even stopping in some instances.
  • big_buck_bunny_4k_H264_30fps.mp4 – OK
  • big_buck_bunny_4k_H264_60fps.mp4 – Audio/video synchronization issues, and the video could be a little smoother
  • Fifa_WorldCup2014_Uruguay-Colombia_4K-x265.mp4 (4K, H.265, 60 fps) – Excellent video decoding, but no audio…
  • Samsung_UHD_Dubai_10-bit_HEVC_51.4Mbps.ts (10-bit HEVC / MPEG-4 AAC) – Perfect from HHD, but buffering a lot from SAMBA share.
  • Astra-11479_V_22000-Canal+ UHD Demo 42.6 Mbps bitrate.ts (10-bit H.265 from DVB-S2 stream) – Most of the time OK, but it will freeze and the same exact point every time for several seconds. (tested on USB drive only)

You can watch a demo with most of these files via the post entitled “H.264 & H.265 4K Video Playback on Amlogic S905 Android TV Box“. While VP9 and H.264 @ 60 fps are not supported by current revision of S905 processor, I understand a new revision of the silicon should support VP9.

Video Player reports “can’t play this video” when I try to play Blu-ray ISO files such as Sintel-Bluray.iso and amay.iso, so I think it’s just not supported by the app. 1080i MPEG2 video samples (GridHD.mpg & Pastel1080i25HD.mpg) played OK, but Hi10p had the same artifacts issues as on Kodi on Amlogic S812, and lacked the subtitles.

I’ve played some stereoscopic 3D videos to see if the system could decode them (my TV does not support 3D):

  • bbb_sunflower_1080p_60fps_stereo_abl.mp4 (1080p Over/Under) – OK
  • bbb_sunflower_2160p_60fps_stereo_abl.mp4 (2160p Over/Under) – Audio only (Would require a dual 4K decoder)
  • Turbo_Film-DreamWorks_trailer_VO_3D.mp4 (1080p SBS) – OK

Lack of DTS/Dolby support was the main issue when I played several H.264, DViX/XVid, VOB, MKV, and MP4 movies, as many did not play audio at all, and Video Player app can not handle FLV videos, nor IFO files (although VOB is OK).

I installed Antutu Video Tester 3.0 manually, and the score (906 point) is pretty good, although not quite as high as on Amlogic S812 devices (1,000+ points).

Click to Enlarge

Click to Enlarge

If you are using premium video streaming applications such as Netflix, it might be important to check whether the level of DRM support, or whether any DRM is actually installed. This could easily be checked thanks to DRM Info app.

DRM_info_K1_PlusAnd sadly, even the basic Widewine security Level 3 is not installed. As a reminder, Widewine Level 1 is required for HD and UHD video playback.

Visit “Where to get video, audio and images samples” post and comments section for links to video samples.

Network Performance (Wi-Fi and Ethernet)

A 278MB file is transferred between a SAMBA share and the internal storage three times using ES File Explorer in order to test WiFi and Fast Ethernet performance. But during the first test,  I only did it twice because the transfer rate was stable but stuck at 130 KB/s during the whole transfer, and it took over 30 minutes for each transfer. Clearly the worst result ever, and at the time my phone could transfer the same file at over 2MB/s. But I tried again, before publishing the results, and the results are much better @ 3.45 MB/s , but I can’t explain what happened…

Performance in MB/s (Click to Enlarge)

Throughput in MB/s (Click to Enlarge)

Amlogic S905 SoC can support Gigabit Ethernet, but K1 Plus is only fitted with Fast Ethernet components, and file transfer performance is under average at about 6MB/s (48 Mbps).

Performance in MB/s

Throughput in MB/s

It looks better while using iperf with “-t 60 -c 192.168.0.104 -d” to test dual duplex transfer for 60 seconds, with a very good Fast Ethernet performance.

Throughput in Mbps

Throughput in Mbps

iperf output:

1

2

3

4

5

6

7

Client connecting to 192.168.0.110, TCP port 5001

TCP window size:  238 KByte (default)

[  6] local 192.168.0.104 port 45160 connected with 192.168.0.110 port 5001

[ ID] Interval       Transfer     Bandwidth

[  6]  0.0-60.0 sec   655 MBytes  91.6 Mbits/sec

[  4]  0.0-60.1 sec   657 MBytes  91.8 Mbits/sec

Miscellaneous Tests

Bluetooth

Bluetooth is not support by KI Plus.

Storage

FAT32 (micro SD card), NTFS, & exFAT (USB hard drive) partitions could all be mounted, but the same bug as on Amlogic S812’s Android 5.1 firmware meant the free space was wrongly reported as 10MB, making the NTFS and exFAT partition basically read-only.

File System Read Write
NTFS OK Not really (10 MB free space)
EXT-4 Not mounted Not mounted
exFAT OK Not really (10 MB free space)
BTRFS Not mounted Not mounted
FAT32 OK OK

I had to skip USB storage benchmarks, but I could still check out the internal storage with A1 SD bench app, which reported 22.71MB/s read speed and 8.67 MB/s write speed.

Read and Write Speeds in MB/s (Click to Enlarge)

Read and Write Speeds in MB/s (Click to Enlarge)

Clearly not the best performance, but it was to be expected for a $40 products, and I have not found it to affect the performance of the device much.

Gaming

I have never seen Candy Crush Saga on device expect when using SoC with Mali-400 GPU, and it played without issue on K1 Plus ising an air mouse. Beach Buggy Racing felt a little sluggish, and once I boosted the graphics settings to “high resolution” it started to become choppy, and at time the game seems to be slow to respond to gamepad inputs. Riptide GP2 was about the same story, but it started pretty well, then set the graphics setting to high resolution, and the game was quite not as smooth, and the game even exited/crashed once. Furthermote, I noticed the frame rate to get worse, the more I played, so the GPU must be throttling when the SoC gets hot, leading to performance degradations. So Amlogic S905 does not seem the best platform for gaming, and better stick with the more powerful Amlogic S812 or Rockchip RK3288 SoCs.

K1 Plus Benchmarks

Before running any benchmarks, let’s see what CPU-Z detects…

Click to Enlarge

Click to Enlarge

The app does not know Amlogic S905 processor, but it probably detects an ARM Cortex A53 quad core processor clocked between 100 MHz and 2.02 GHz, coupled with an ARM Mali-450MP GPU. The model is called KI Plus (p20x), the board p20x, the UI resolution is set to 1920×1080, there’s 807MB total RAM in the system, and 4.66GB internal storage. It’s running an aarch64 Linux kernel version 3.14.29 as reported previously.

K1_Plus_Antutu_5.7.3
I had already run Antutu 5.7.3 to compare Amlogic S905 and Rockchip RK3368 performance, but following the firmware update, I ran it again, and it yielded a marginally higher score of 29,167 points.

Please also find Vellamo 3.0 and 3DMark Ice Storm Extreme results below for reference.

K1_Plus_Vellamo_3.0

Click to Enlarge

Click to Enlarge

Conclusion

It’s quite amazing that you can now get an Android TV box with 4K video playback and HDMI 2.0 support for about $40. However, there’s still work to be done, as while their a good based with a reasonably good user interface, and surprisingly smooth video playback at 2160p resolution using Video Player app, the pre-installed Kodi 15.2 version was unusable at 4K resolution with most videos letterboxed, DTS and Dolby licenses are missing, there’s no DRM installed at all, and various other bugs need to be fixed.

PROS

  • Recent Android 5.1 OS firmware that is both responsive and stable
  • Video Output – HDMI 2.0 up to 2160p 60Hz; 24/25/30/50/60 Hz refresh rates supported; AV port (tested with speakers)
  • Impressive 4K H.265 (10-bit) and H.264 video playback in Video Player app
  • Dolby 5.1, DTS and TrueHD audio pass-through is working.
  • Proper power handling
  • IR remote support IR learning function, and has a good range (>10 meters)
  • 4x USB ports
  • Very good value for money (once issues can be resolved)

CONS

  • Pre-installed Kodi 15.2 version does not work well for 2160p video output is selected (1080p output looks better); automatic frame rate switching is not working either.
  • HDMI – Dolby Digital 7.1+, DTS HD and Atmos pass-through not working; CEC not working; Video output resolution set in settings is not always used at next power on.
  • Missing DTS and Dolby support for PCM output
  • No DRM installed, even Widewine Level 3 required for SD playback on relevant apps.
  • WiFi performance may be erratic (TBC), very good sometimes, and near stall speed at others.
  • 3D games such as Beach Buggy Racing and Riptide GP2 are not playing very smoothly, and performance may degrade with play time (and higher heat).
  • No option to show status and notification bars, no Download icon in app list.
  • Lacks Bluetooth support
  • USB hard drive partitions (NTFS / exFAT) reported as having 10MB free only, basically rendering the partitions read-only.

There are also IPTV apps that depending on your point of view can be PROS or CONS, and OTA firmware update is missing, but this may be due to Videostrong being a manufacturer, and not a brand, so they rely on their customer to handle firmware updates with their own servers and branding.

Videostrong was kind enough to send this first Amlogic S905 box sample for review, and if you are a distributor or resellers, you could contact the company via their Alibaba product page. Individual can purchase K1 Plus (aka Ki Plus) on retail sites starting at $39.99 including shipping on GearBest, GeekBuying, eBay, Amazon US, Aliexpress and others.

Intel Atom x5-Z8300 vs x5-Z8500 Benchmarks Comparison

$
0
0

We’ve previously seen there’s not that much difference in benchmarks between Intel Atom Z3735F and the newer Atom x5-Z8300 processor, except when it comes to 3D graphics performance where the latter can be up to twice as fast. The same benchmarks have been run in Windows 10 on an Atom x5-Z8500 based device, namely Kangaroo Mobile Desktop computer, and the difference seemed large enough that I decided to make a comparison against the Atom x5-Z8300 processor used in Tronsmart Ara X5.

Intel_Atom_x5-Z8300_vs_x5-Z8500The three benchmarks – PCMark 8, Passmark 8, and 3DMark – were run in Windows 10 64-bit Home in both devices. A Ratio greater than one indicates Kangaroo (x5-Z8500) is the faster device.

[Update: Benchmarking mobile or small form factor devices is a complex tasks, as performance may depend on the thermal dissipation of the device, version of the hardware, and obviously software status (e.g. Windows 10 is continuously updated), and I know have two comparison tables:

  1. The first table below compares  Ara X5 results in August 2015 to Kangaroo results in November 2015
  2. The second and new table compares Ara X5 results in November 2015 (likely different internal storage, updated Windows, and room temperature) using updated results posted by Linuxium to Kangaroo results (Nov 2015).]

1st Table –  Original Post

Benchmark Tronsmart Ara X5
Intel Atom x5-Z8300 @ 1.44 GHz / 1.84 GHz (Turbo)
Kangaroo Mobile Desktop
Intel Atom x5-Z8500 @ 1.44 GHz / 2.24 GHz (Turbo)
Ratio
PCMark8
Overall Score 1048 1597 1.52
Web Browsing – JunglePin 0.67417s 0.5599s 1.20
Web Browsing – Amazonia 0.23567s 0.18814s 1.25
Writing 11.78254s 9.03502s 1.30
Casual Gaming 7.62 fps 11.97 fps 1.57
Video Chat playback 29.95 fps 30.01 fps 1.00
Video Chat encoding 364s 212s 1.72
Photo Editing 2.63164s 0.85046s 3.09
Passmark 8
Passmark Rating 508 826 1.63
CPU Mark 1,444 1,950 1.35
2D Graphics Mark 128 206 1.61
3D Graphics Mark 238 297 1.25
Memory Mark 575 622 1.08
3DMark
Ice Storm 1.2 19,709 20,347 1.03
Cloud Gate 1.1 1,660 1,917 1.15
Sky Diver 1.0 885 1,104 1.25
Fire Strike 202 270 1.34

So Intel Atom x5-Z8500 is faster in all benchmarks. Passmark 8 also includes Disk Mark, but I have not included it in the table above, as it’s more related to the storage performance itself than the processor. Nevertheless, it should be noted that I/O performance may also impact the performance of some tests above, and Disk Mark results were 200 and 606 points for Ara X5 and Kangaroo respectively, so x5-Z8300 performance might be slightly unreported in some of the benchmarks that may use the internal storage.

The most confusing test is photo editing, as the Atom x5-Z8500 devices performs the task three times faster than Ara X5 with Atom x5-Z8300, and I can’t find a rational reason for it.

Memory _Bandwidth_x5-Z8500_vs_x5-Z8300

Memory Specs – x5-Z8500 (left) vs x5-Z8300 (right)

At first I thought that memory bandwidth may be at play here, but Passmark’s “Memory Mark” shows only marginal higher performance for x5-Z8500. Other factors that could have impacted the benchmark include thermal design, as well as Windows 10 updates, as Ara X5 was tested about three months ago (and I don’t own it anymore).

Nevertheless, overall Atom x5-Z8500 in Kangaroo mini PC should deliver noticeable performance improvement over x5-Z8300 in Ara X5, and if you already own an Intel Atom Z3735F based device, you would most certainly notice a performance boost by going to a computer or stick with an Atom x5-Z8500 processor, something that was not obvious with Atom x5-Z8300.

Price-wise Tronsmart Ara X5 now costs $120 with free shipping worldwide, and Kangaroo mobile desktop computer goes for $99 with shipping to the US only. The Kangaroo device does lack Ethernet however. Intel lists x5-Z8300 for $20 and x5-Z8500 for $25, with actual market prices likely to be even lower, so price/performance of x5-Z8500 appears to be much better than x5-Z8300.

2nd Table – With updated results for Ara X5

Benchmark Tronsmart Ara X5
Intel Atom x5-Z8300 @ 1.44 GHz
Kangaroo Mobile Desktop
Intel Atom x5-Z8500 @ 1.44 GHz
Ratio
PCMark8
Overall Score 1,354 1,597 1.18
Web Browsing – JunglePin 0.62407s 0.5599s 1.11
Web Browsing – Amazonia 0.20059s 0.18814s 1.07
Writing 13.24s 9.03502s 1.47
Casual Gaming 9.65 fps 11.97 fps 1.24
Video Chat playback 29.99 fps 30.01 fps 1.00
Video Chat encoding 254.3333s 212s 1.20
Photo Editing 0.96745s 0.85046s 1.14
Passmark 8
Passmark Rating 672 826 1.23
CPU Mark 1,468 1,950 1.33
2D Graphics Mark 138.8 206 1.48
3D Graphics Mark 240.2 297 1.24
Memory Mark 560 622 1.11
3DMark
Ice Storm 1.2 19,115 20,347 1.06
Cloud Gate 1.1 1,658 1,917 1.16
Sky Diver 1.0 903 1,104 1.22
Fire Strike 214 270 1.26

3DMark results for Ara X5 have stayed about the same between August and November, and most of Passmark results have stayed the same except the overall score explained by the jump of Disk Mark from 200 to 757. PCMark 8 however had nearly a 30% jump in the score with the “Photo Editing” score becoming “normal” (I can could only explain by some software optimization unless it’s highly reliant on I/O performance), and most other PCMark8 tests getting a small boost.

The overall conclusion remains that same: Atom x5-Z8500 shoud have a better price/performance as long as active or passive cooling is done properly.

Bmorn W4301 is a $34 Android Smartphone Powered by Intel Atom x3-C2101 Processor

$
0
0
Home > Android, Hardware, Intel Atom, Video > Bmorn W4301 is a $34 Android Smartphone Powered by Intel Atom x3-C2101 Processor

Bmorn W4301 is a $34 Android Smartphone Powered by Intel Atom x3-C2101 Processor

Intel unveils their plans for Atom X3, X5 and X7 processors last year, but so far we’ve mostly seen devices with Atom X5 processors.  The lowest end Intel Atom processor, namely X3-C2101 “Sofia” dual core processor, with an ARM Mali-400MP GPU and 3G connectivity did find its way into Teclast X70 3G tablet that is now selling for $64 and up retail (but there’s a deal on Geekbuying for $45.99), and a company called Bmorn is about to launch their W4301 smartphone based on Intel/Rockchip X3-C2101 SoC for just $34 ( factory price in quantities), but I think the retail price should be around $60 including shipping.

Bmorn_W4301Bmorn W4301 preliminary specifications:

  • SoC – Intel Atom x3-C3130 dual x86 core processor @ up to 1GHz with Mali-400MP2 GPU @ 533 MHz
  • System Memory – 512MB or 1GB LPDDR2
  • Storage – 4 or 8 GB eMMC
  • Display – 4″ touchscreen with 800×600 resolution
  • Connectivity – WiFi 802.11 b/g/n, Bluetooth 4.0, GPS
  • Cellular Connectivity – 3G (WCDMA)
  • Camera – 2MP rear camera, 0.3MP front-facing camera
  • Battery – TBD – 4 hours talk-time
  • Dimensions & Weight – N/A

The phone runs Android 4.4, but I understand Android 5.1 Lollipop will be used once the phone ships. There’s little information about the phone right now, but you can still go to Bmorn W4301 product page, and/or watch Charbax video below about this phone, and other products from Bmorn.

[embedded content]

If the SoC can be had for such a low price, it could be suitable for a 3G IoT board too.

UP Board Gets 2GB RAM and 32GB Storage Option, Linux Port in Progress

$
0
0

The UP Board is a Raspberry Pi like board with an Intel Atom processor that’s currently on Kickstarter with a few hours left, and it has just reached its 100,000 Euros stretch goal meaning that beside the 16GB storage / 1 GB version, a version with 32Gb storage and 2GB is now offered. The company also showed their progress with the implementation Debian based Ubilinux  on the Intel Atom x5-Z8300 board.

Up_BoardThat means the specifications have now been updated:

  • SoC – Intel Atom x5-Z8300 “Cherry Trail” quad core processor @ 1.44 GHz (Burst frequency: 1.84 GHz) with Intel Gen8 HD graphics @ 500 MHz
  • System Memory –  1 GB or 2 GB DDR3L-1600
  • Storage – 16 or 32 GB eMMC
  • Video Output / Display – HDMI, DSI connector
  • Audio I/O – HDMI
  • Connectivity – Gigabit Ethernet
  • USB – 4x USB 2.0 host ports, 1x USB 2.0 pin header, 1x micro USB 3.0 port (under the board)
  • Camera – CSI connector for 4MP camera
  • Expansion – 40-pin Raspberry Pi compatible header with GPIOs, I2C, SPI, UART. etc…
  • Misc – Power button, RTC
  • Power Supply – 5V via power barrel
  • Dimensions – 85.60 x 56.50 mm
  • Temperature Range – Operating: 0 to 60 C
  • Certifications – FCC, CE, RoHS

The first 500 backers will get their 16GB/1GB board updated to 32GB/2GB configuration, but new backers can get the UP Board with 2GB RAM, 32 GB storage for 109 Euros plus shipping, while the first version still stays at 89 Euros.

In their latest update, Emutex Labs also showed their progress booting UbiLinux on the board.

[embedded content]

There’s still some work to be done including support for GPIOs and I think audio, but the company also plans to port Ubuntu and Snappy to the board, and hopefully their work can be leveraged for other Intel Atom Cherry Trail based platforms.

Mediatek LinkIt Smart 7688 and Smart 7688 DUO Boards Run OpenWRT for IoT Applications

$
0
0

MediaTek LinkIt is a collection of development platforms designed for the prototyping of wearables and Internet of Things (IoT) devices, and last year they started with LinkIt ONE board based on Mediatek MT2501 “Aster” micro-controller and featuring WiFi, Bluetooth, GPSD and GSM/GPRS connectivity. Mediatek Labs has now launched two new LinkIt board, namely LinkIt Smart 7688 and LinkIt Smart 7688 DUO, both powered by Mediatek MT7688 MIPS processor and running OpenWRT, with the latter also adding an Atmel ATmega32U4 for Arduino compatibility.

LinkIt_Smart_7688

LinkIt Smart 7688 (Left) and Smart 7688 DUO (Right) Boards are Breadboard-Friendly Too

LinkIt Smart 7688 Board

LinkIt Smart 7688 Board (Click to Enlarge)

LinkIt Smart 7688 Board (Click to Enlarge)

LinkIt Smart 7688 is then the simpler of the two with the following specifications:

  • Processor – Mediatek MT7688AN MIPS24KEc processor @ 580 MHz with WiFi
  • System Memory – 128MB DDR2 RAM.
  • Storage – 32MB flash + micro SD slot
  • Connectivity – 1T1R Wi-Fi 802.11 b/g/n with chip antenna and I-PEX conector
  • USB – 1x micro USB host port, 1x micro USB port for power
  • Expansion – 2x 18-pin headers with GPIOs, I2C, I2S, SPI, UART, PWM and Ethernet Port.
  • Misc – MPU reset and WiFi reset buttons, MPU EJTAG solder pads
  • Power Supply – 5V via micro USB port, or 3.3V via header
  • Dimensions – 55.7 x 26 mm
Bottom of Smart 7688 Board (Click to Enlarge)

Bottom of Smart 7688 Board (Click to Enlarge)

CL245A on the back of the board is a switch IC to “bypass MT7688AN bootstrap behavior”.

LinkIt Smart 7688 DUO

LinkIt Smart 7688 Duo (Click to Enlarge)

LinkIt Smart 7688 Duo (Click to Enlarge)

The DUO board is pretty similar, and adds Atmel MCU and reset button, 4 more I/O pins, and is slightly longer:

  • Processor – Mediatek MT7688AN MIPS processor @ 580 MHz with 64 KB I-cache, 32 KB D-cache
  • System Memory – 128MB DDR2 RAM.
  • Storage – 32MB flash + micro SD slot
  • MCU – Atmel ATmega32U4 AVR @ 8 MHz
  • Connectivity – 1T1R Wi-Fi 802.11 b/g/n with chip antenna and I-PEX conector
  • USB – 1x micro USB host port, 1x micro USB port for power
  • Expansion – 2x 20-pin headers with GPIOs, I2C, I2S, SPI, UART, PWM and Ethernet Port.
  • Misc – MPU reset, MCU reset, and WiFi reset buttons, MPU EJTAG solder pads
  • Power Supply – 5V via micro USB port, or 3.3V via header
  • Dimensions – 60.8 x 26 mm
Bottom of Duo Board (Click to Enlarge)

Bottom of Duo Board (Click to Enlarge)

The I/Os pin are however connected quite differently on 7688 and 7688 DUO, as the latter has most IOs connected to the AVR MCU, with only 3 GPIOs directly connected to the MIPS processor.

7688 DUO Pintout Chart (Click to Enlarge)

LinkIt Smart 7688 DUO Pinout Chart (Click to Enlarge)

7688 Pinout Chart (Click to Enlarge)

LinkIt Smart 7688 Pinout Chart (Click to Enlarge)

Documentation for both board is pretty extensive with Getting Started Guides, a developer’s guide, tutorials, and information about the HDK (Hardware Developer Kit) , which is simply call “board”, including schematics and PCB layout (PDF only). The company also released the bootloader and firmware binary files, as well as an OpenWRT SDK. The boards support both Linux and OS X for development with C/C++, while Python, and Node.js are also supported on Windows. Arduino IDE is also available for the DUO version, and by default MT7688 MPU and Atmel MCU communicate over UART with applications code on the former, and I/Os and sensors managed by the latter. You can access all these resources on LinkIt Smart 7688 page on MediaTek Labs, with some code also found on Mediatek Labs’ Github account, and Seeed Studio’s Wiki.

LinkIt Smart 7688 boards are distributed by Seeed Studio, and you can purchase Mediatek LinkIt Smart 7688 for $12.90 and LinkIt Smart 7688 DUO for $15.90.

Viewing all 2336 articles
Browse latest View live