Dev May 2016

dev@lists.96boards.org

17 participants
10 discussions

by Thomas B. Rücker

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 connectors. The LeMaker product page has it up for preorder for 299$; with an estimated shipping time frame of 2016Q2. http://www.lenovator.com/product/103.html 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 compliance report? Cheers Thomas

7 years, 7 months

HiKey is supported better in v4.7-rc1 vanilla.

by Guodong Xu

Hi, All 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. Ref: Build procedure: git checkout -b YOUR-WORKING-BRANCH v4.7-rc1 make ARCH=arm64 defconfig; export LOCALVERSION="-linaro-hikey"; make ARCH=arm64 Image modules hisilicon/hi6220-hikey.dtb -j20; With 1. latest UEFI: (https://builds.96boards.org/snapshots/reference-platform/components/uefi/la…), 2. Debian rootfs: http://builds.96boards.org/snapshots/reference-platform/debian/98/hikey/ Then, replace Image and dtb, you can see v4.7-rc1 running on HiKey. Enjoy! Best regards, Guodong Xu

8 years, 1 month

Re: [Dev] [android-building] Latest built AOSP images are not working on Hikey Board.

by Amit Pundir

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 > below. > http://source.android.com/source/devices.html > > Loaded these system.img ,cache.img and userdata.img generated images > on Hikey board and connected HDMI output from HIkey Board to HDMI > display. > However I could not see any display on HDMI screen. > > Please refer the attached logcat.txt and suggest me if I am missing > anything. 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? Regards, Amit Pundir > > Thanks, > NY > > -- > -- > 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 > android-building+unsubscribe(a)googlegroups.com > For more options, visit this group at > http://groups.google.com/group/android-building?hl=en > > --- > 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.

8 years, 2 months

Re: [Dev] SPI0 on HI6220 no clock

by Guodong Xu

+dev(a)lists.96boards.org 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, >> Denis >> >> > > 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. > > Regards, > Kaihua > > > #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 __ __ __ __ __ __ | .� >

8 years, 2 months

flashing OE RPB artifacts to hikey

by Trevor Woerner

Hi, When I perform an OE RPB build for the DragonBoard410c I end up with the following build artifacts (among others): rpb-console-image-dragonboard-410c.ext4.gz boot-dragonboard-410c.img 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 artifact: rpb-console-image-hikey.ext4.gz The instructions I can find[1] and the artifacts from the official download areas[2] 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 using OE? Is there a way (perhaps using fastboot) to see what partitions have been created on the emmc and their sizes? Best regards, Trevor [1] https://github.com/96boards/documentation/wiki/HiKeyGettingStarted [2] https://builds.96boards.org/releases/hikey/linaro/debian/latest/

8 years, 2 months

usb connection problems

by David Long

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 and device not accepting address 7, error -71 Thanks, -dl

8 years, 2 months

Re: [Dev] 4.4 kernel with HDMI display?

by Guodong Xu

> 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 > display. > https://github.com/96boards-hikey/linux/tree/hikey-mainline-rebase-4.4 Hi, Liming 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 # reboot. -Guodong > > BTW, HDMI works well when I tested 3.18 kernel. > > BR, > Liming Wang

8 years, 2 months

4.4 kernel can't detect sd card on hikey board?

by Liming Wang

hi Leo, My 4.4 kernel can't detect any sd card on hikey board but 3.18 kernel can. I run the kernel from u-boot bootloader. 3.18 kernel log: ---------------- [ 3.370348] mmc_host mmc1: Bus speed (slot 0) = 99200000Hz (slot req 100000000Hz, actual 99200000HZ div = 0) [ 3.370365] mmc1: new ultra high speed SDR50 SDHC card at address aaaa [ 3.371147] mmcblk1: mmc1:aaaa SS08G 7.40 GiB [ 3.372995] mmcblk1: p1 p2 p3 p4 4.4 kernel log: --------------- 4.4 kernel from: git://github.com/96boards-hikey/linux.git hikey-mainline-rebase and config is defconfig. # uname -a Linux linaro-alip 4.4.0+ #2 SMP PREEMPT Sun Apr 10 21:40:33 CST 2016 aarch64 GNU/Linux # dmesg|grep mmc1 [ 0.247672] dwmmc_k3 f723e000.dwmmc1: fifo-depth property not found, using value of FIFOTH register as default [ 0.247728] dwmmc_k3 f723e000.dwmmc1: IDMAC supports 32-bit address mode. [ 0.247808] dwmmc_k3 f723e000.dwmmc1: Using internal DMA controller. [ 0.247818] dwmmc_k3 f723e000.dwmmc1: Version ID is 250a [ 0.247850] dwmmc_k3 f723e000.dwmmc1: DW MMC controller at irq 40,32 bit host data width,64 deep fifo [ 0.248038] dwmmc_k3 f723e000.dwmmc1: Got CD GPIO [ 0.263396] mmc_host mmc1: Bus speed (slot 0) = 25000000Hz (slot req 400000Hz, actual 390625HZ div = 32) [ 0.280453] dwmmc_k3 f723e000.dwmmc1: 1 slots initialized [ 0.376089] mmc1: error -110 whilst initialising SD card Does 4.4 kernel still not support SD card? BR, Liming Wang

8 years, 2 months

FYI: changed: 96borads compliance web page

by Thomas B. Rücker

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 myself. 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 blobs. The GPLv2 licence prohibits this. - Bootloader - * At least one open source bootloader shall be provided for the board that - executes immediately after the internal SoC startup code. The source for - this bootloader should be available from a publicly accessible site or - integrated into the bootloader trees on https://github.com/96boards +*** Bootloader *** + * It is strongly recommended one open source bootloader to be provided for + the board that executes immediately after the internal SoC startup code. + The source for this bootloader should be available from a publicly + accessible site or integrated into the bootloader trees onhttps:// + github.com/96boards * Fastboot protocol support shall be provided for all Consumer Edition boards * It is strongly recommended that vendors of an ARMv8 board provide a port ================================== Cheers, Thomas

8 years, 2 months

Developer Reference Platform 16.03 differences compared to Debian

by Riku Voipio

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[1]. This lists the packages that do not become from Debian (Jessie release) or Debian backports: New packages not in Debian: 96boards-artwork: 0.6-0linaro1 96boards-tools: 0.5 optee-client: 1.0.1+git5+g89f25ce-1.linarojessie.1 glshim: 0.41+git20150911.42a7739-0.linarojessie.1 linaro-artwork: 0.6-0linaro1 linaro-default-settings: 0.3-0linaro1 linaro-overlay: 1112.8 wcnss-config: 1.8 Changed packages: alsa-lib: 1.0.28-1+linaro1.linarojessie.1 * add UCM config file for HDMI and HiFi on DB410c * add UCM config file for HDMI on IFC6410 chromium-browser: 47.0.2526.16-1.6.linarojessie.1 * seccomp and namespace fixes * patches to compile on arm64/armhf firmware-nonfree: 20160110-1.linarojessie.1 * ti-connectivity (updates for HiKey): - Include wl18xx-fw-4 firmware - Add TIInit_11.8.32.bts for bluetooth support isc-dhcp: 4.3.3-8~linaro1 * Reverting requirement for debhelper >= 9.20151220 * Upload to make it work with latest systemd: - https://bugs.96boards.org/show_bug.cgi?id=271 linux: 4.4.0.linaro.104-1.linarojessie.1 * See kernel changes report (TBD) No-changes Backports: apparmor: 2.10-2.linarojessie.1 binutils: 2.25.90.20160101-1.linarojessie.1 gdb: 7.10-1.linarojessie.1 gyp: 0.1+20150913git1f374df9-1.linarojessie.1 java-common: 2:1.8-53.linarojessie.1 nodejs: 4.2.2~dfsg-1.1.linarojessie.1 openssl: 1.0.2d-1.linarojessie.1 systemd: 228-2.4.linarojessie.3 sysvinit: 2.88dsf-59.2.linarojessie.1 util-linux: 2.27.1-1.linarojessie.1 x265: 1.7-4~bpo8+1.linarojessie.1 xorg: 1:7.7+11.linarojessie.1 xorg-server: 2:1.17.3-2.linarojessie.2 xserver-xorg-video-fbdev: 1:0.4.4-1.linarojessie.1 xserver-xorg-video-freedreno: 1.4.0-1.linarojessie.1 [1] https://github.com/suihkulokki/distrodelta with command distrodelta -o Debian 'Debian Backports'

8 years, 2 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Dev May 2016