Silently a new 96board starts appearing: Cello
It seems to be produced by LeMaker and is based around the AMD A1100
SoC. That's the same as on the illusive Husky, actually both boards look
very similar with only minor differences in the placement of some
The LeMaker product page has it up for preorder for 299$; with an
estimated shipping time frame of 2016Q2.
This could mean the first "cheap" 64 bit ARM server board becoming
available. Also more power: A57 cores.
Though I'm sure hrw will still disapprove as it has SATA, but is a weird
non-industry-standard form factor.
Oh, and the obligatory question:
Will it be 96boards compliant and are we going to get to see the actual
We now see better support for HiKey in v4.7-rc1 mainline vanilla, and
following features landed in v4.7-rc1: dts, configs, pmic, and drm.
Features supported from mainline kernel include:
- usb otg and host (high-speed mode)
- microSD card
- uart on Low-speed expansion port (LS)
- I2C on LS
- SPI on LS
- WiFi (need update UEFI to latest, see below for link)
Just for your curiosity, in v4.6, we upstreamed: usb & usb phy,
(CONFIG_PHY_HI6220_USB), hi655x regulator, hi6220 mailbox, hisi reset,
and mmc dw k3.
git checkout -b YOUR-WORKING-BRANCH v4.7-rc1
make ARCH=arm64 defconfig;
make ARCH=arm64 Image modules hisilicon/hi6220-hikey.dtb -j20;
1. latest UEFI:
2. Debian rootfs:
Then, replace Image and dtb, you can see v4.7-rc1 running on HiKey.
On 18 May 2016 at 04:18, YADLA NIRANJAN <niruyadla(a)gmail.com> wrote:
> Latest built AOSP images are not working on Hikey Board.
> Followed instructions to make system.img and other images from the link
> Loaded these system.img ,cache.img and userdata.img generated images
> on Hikey board and connected HDMI output from HIkey Board to HDMI
> However I could not see any display on HDMI screen.
> Please refer the attached logcat.txt and suggest me if I am missing
AOSP seem to have booted up fine on Hikey. See
"SystemBroadcastReceiver: Boot has been completed" in your logcat.
Did you try connecting hikey to any other HDMI display?
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-building(a)googlegroups.com
> To unsubscribe from this group, send email to
> For more options, visit this group at
> You received this message because you are subscribed to the Google Groups
> "Android Building" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to android-building+unsubscribe(a)googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
for further discussons.
On 17 May 2016 at 14:59, Zhong Kaihua <zhongkaihua(a)huawei.com> wrote:
> On 2016/4/26 16:20, Denis Ciocca wrote:
>> Hi Mr. Zhong,
>> I've been working with Hikey board using Hisilicon 6220.
>> I need to use SPI0, availabe on expansion connecto. I'm using android-linaro-kernel4.1.
>> Using spidev driver, I can see with oscilloscope that MOSI and CS are working correctly
>> but CLK is not moving.
>> Is it working corretly in the board and mine is broken somehow or something wrong with
>> the code?
>> Thanks & BR,
> Hi Denis,
> Excuse me for the delay of reply. The spi clock is divided from syspll and we have not met
> this situation before.
> Please check you have configured SPI driver as follow,
> (1) Change the status of SPI0 to "ok" in hi6220.dtsi
> (2) Enable the SPI suppORt in menuconfig
> Device Drivers->SPI support->[*] User mode SPI device driver support
> We ran spidev_test when we upstream the code, and it works well. You may use it to test your
> board. If the test is OK and the clock still cannot work, please contact us for further investigation.
> #Get latest spidev test, for example
> # https://github.com/torvalds/linux/blob/master/Documentation/spi/spidev_test…
> #and send it to the target.
> [On target with the new kernel:]
> [Confirm that there is f7106000.spi under /sys/devices/smb]
> [Compile spidev_test.c]
> $gcc -O2 -o spidev_test spidev_test.c
> [Target root:]
> [Loop test where connecting SDO to SDI on HiKey]
> #./spidev_test -D /dev/spidev0.0
> spi mode: 0x0
> bits per word: 8
> max speed: 500000 Hz (500 KHz)
> RX | FF FF FF FF FF FF 40 00 00 00 00 95 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF F0 0D | ......@....�..................�.
> [Send two bytes to some device. This is the result from gyroscope of ST LSM9DS0.]
> #./spidev_test -D /dev/spidev0.0 -p "\x8f\x00"
> spi mode: 0x0
> bits per word: 8
> max speed: 500000 Hz (500 KHz)
> RX | 00 D4 __ __ __ __ __ __ | .�
When I perform an OE RPB build for the DragonBoard410c I end up with the
following build artifacts (among others):
The *ext4 is flashed to the rootfs partition and the *img is flashed to the
boot partition; everything works great.
When I perform an OE RPB build for the HiKey I end up with only the following
The instructions I can find and the artifacts from the official download
areas suggest I should need something called *.emmc.img.gz, but my build
doesn't generate any such file and it doesn't look like the meta-96boards
layer provides any recipes for generating any such type of image. It's as
though I were missing a step in there somewhere. How do I get an *emmc.img
Is there a way (perhaps using fastboot) to see what partitions have been
created on the emmc and their sizes?
I've been having no luck getting low-speed USB devices (i.e.: keyboard
and mouse) to work with the 4.4 96boards kernel on hikey. My ethernet
dongle works fine though. Is there a known problem or do I maybe just
have a config issue? The error messages are:
device descriptor read/64, error -71
device not accepting address 7, error -71
> Hi Guodong,
> Thanks for your help. Another issue is that whether below branch supports
> HDMI out? I'm using arch/arm64/configs/defconfig and found no output on HDMI
HDMI should work. At least, you should be able to see there are Text
mode output in the HDMI display, right? (If you didn't see any text
output, let me know.)
For graphics UI to work, you need to update 'xf86-video-armsoc'. Since
in latest hikey-mainline-rebase (-4.4), DRM was updated and name is
changed. So, you need git clone and build this in your hikey:
# git clone https://github.com/xin3liang/xf86-video-armsoc/
# cd xf86-video-armsoc/
# git checkout hikey-kirin
# cat README ; here you need to follow the last three lines to build
& install for hikey
... build & install
> BTW, HDMI works well when I tested 3.18 kernel.
> Liming Wang
I had set up a website watcher a while ago, so that I wouldn't miss any
new developments, especially as I was interested in compliance reports
becoming available. This change came up about a week ago and as I
haven't seen official mentions anywhere, I thought I'd mention it here
I, explicitly, do not offer any interpretation or speculation as to the
reasons for that change.
This is left to LINARO to clarify, if they choose to do so.
changed: 96borads compliance page (http://www.96boards.org/compliance/)
--- @ Fri, 22 Apr 2016 00:23:21 +0000
+++ @ Tue, 26 Apr 2016 13:06:51 +0000
@@ -152,11 +152,12 @@
o Bluetooth and WiFi firmware
Note that Linux kernel modules must not be provided as binary firmware
The GPLv2 licence prohibits this.
- * At least one open source bootloader shall be provided for the
- executes immediately after the internal SoC startup code. The
- this bootloader should be available from a publicly accessible
- integrated into the bootloader trees on https://github.com/96boards
+*** Bootloader ***
+ * It is strongly recommended one open source bootloader to be
+ the board that executes immediately after the internal SoC
+ The source for this bootloader should be available from a publicly
+ accessible site or integrated into the bootloader trees onhttps://
* Fastboot protocol support shall be provided for all Consumer Edition
* It is strongly recommended that vendors of an ARMv8 board provide
One of the goals of RPB is to follow that our changes go back
upstream. For the next RPB release, a more polished report is planned.
But to get things started, here's a sample - and to use as baseline to
compare progress for the 16.06 release. The list of packages is
collected from db410/alip image with distrodelta script. This lists
the packages that do not become from Debian (Jessie release) or Debian
New packages not in Debian:
* add UCM config file for HDMI and HiFi on DB410c
* add UCM config file for HDMI on IFC6410
* seccomp and namespace fixes
* patches to compile on arm64/armhf
* ti-connectivity (updates for HiKey):
- Include wl18xx-fw-4 firmware
- Add TIInit_11.8.32.bts for bluetooth support
* Reverting requirement for debhelper >= 9.20151220
* Upload to make it work with latest systemd:
* See kernel changes report (TBD)
 https://github.com/suihkulokki/distrodelta with command
distrodelta -o Debian 'Debian Backports'