Dev

dev@lists.96boards.org

241 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

9 years, 9 months

UART for MediaTek X20 96boards

by Leo Yan

Hi all, I'm working one MediaTek X20 96boards, and install one Mezzanine board on it so can try to see if UART can work well or not. After tried to switch Mezzanine's Jumpers in J1 to UART0, so I can see it can print out some logs; but later images print out log but totally cannot be unrecognized, please see below log info. Tried to change baudrate from 115200 to 38400, but it's no lucky. So the unrecognized char issue is not caused by baudrate. Before I look into detailed kernel configuration, I'd like check if any guy has fixed this issue, could you point out what's wrong for this? Thanks in advance. Leo Yan ---8<--- F0: 102B 0000 F3: 0000 0000 V0: 0000 0000 [0001] 00: 0000 0000 BP: 0000 0041 [0000] G0: 0190 0000 EC: 0000 0000 [0001] T0: 0000 0163 [000F] Jump to BL READY*3 Sw ?2"0 Rr?9? * ?r smNBrpt*sB:t*?_@ ??M 2 Er )#"?JBb* rJ:0 ?&? r ?(&b*?? ?J/1r:] *') "B: ?pZ 6J R8r*B?K* #

9 years, 9 months

Reference Software Platform 16.06 is released!

by Fathi Boudra

I'm pleased to announce the 16.06 release for the Reference Software Platform project! This is the fourth release, and like its predecessors, it has seen quite a few changes and improvements for both Consumer and Enterprise platforms. The Reference Software Platform has seen many substantial changes, among other more subtle ones. Below is a list of some of this release’s highlights: Common to both Consumer and Enterprise Editions ============================================== * Kernel - Unified tree shared between the CE and EE builds - 4.4.11-based, including some under-review topic branches to extend the features and platform hardware support - Device-Tree support for CE; ARM ACPI and PCIe support for Enterprise - Added OP-TEE support (enabled on HiKey and Juno) - Supports Reference HW platforms HiKey and Cello (Other Test Platforms include: Dragonboard 410c, Hisilicon D02 and D03, APM X-Gene, HP Proliant m400, AMD Overdrive, Qualcomm Q2432:ZB, and Cavium ThunderX) - Single kernel config for all platforms in arch/arm64/configs/distro.config - Single kernel binary (package) for all platforms * Bootloader - UEFI OpenPlatformPkg (upstream) now contains reference implementations for Huawei D02/D03, AMD Overdrive and LeMaker Cello - U-boot support in Dragonboard 410c images to allow easier handling of images Consumer Edition ================ * Reference hardware platform - LeMaker Hikey * Other supported test platforms - Dragonboard 410c * Overall CE Debian platform features, validated as part of the release - UEFI with DT - Upgrade to Debian 8.5 “Jessie” - Upgrade to the unified 4.4.11 Linux Kernel - Upgrade graphics components: Mesa 11.1.2 and XServer 1.17.3a - Rootfs automatically resized during the first boot * CE Debian RPB for HiKey: - OP-TEE integrated by default - UEFI updated to use the latest development trees based on Tianocore and OpenPlatformPkg * CE Debian build for DragonBoard 410c: - U-boot chain-loaded from LK * CE OE/Yocto RPB: - First OpenEmbedded-based RPB, including several changes and components merged from the LHG OE layers - Dragonboard 410c and HiKey support - HiKey features: OP-TEE and Mali support - Dragonboard 410c features: GPU, WLAN, BT, audio, LS I/O, camera and GPS support Enterprise Edition ================== * Reference hardware platform - LeMaker Cello * Other supported test platforms - AMD Overdrive A0 and B0 - Hisilicon D02 - Hisilicon D03 (new) - APM X-Gene Mustang - HP ProLiant m400 - Qualcomm Q2432LZB (new) - Cavium ThunderX (new) * Overall platform features, validated as part of the release - UEFI with ACPI - KVM - PCIe * Firmware - UEFI OpenPlatformPkg (upstream) now contains reference implementation for Huawei D02/D03, AMD Overdrive and LeMaker Cello * Network Installers - Use the unified 4.4.11 kernel - Debian upgrade to Debian 8.5 “Jessie” - CentOS upgrade to CentOS 7.2 16.03 * Enterprise Components - Docker 1.9.1 - OpenStack Liberty for Debian Jessie and CentOS - ODPi 1.0.0 based Hadoop - Spark 1.3.1 - OpenJDK 8 - QEMU 2.6 Known issues with this release ============================== Install instructions, known issues, test reports and instructions to build from source are all published on: https://github.com/96boards/documentation/wiki/Reference-Platform-Home For bugs related to the 96Boards platforms, please use the 96Boards bug tracking system: https://bugs.96boards.org/ For bugs related to the Reference Software Platform release, but on development boards that are not officially part of 96Boards (e.g. AMD Overdrive and HiSilicon D02/D03), please use: https://bugs.linaro.org On behalf of the Reference Platform teams, -- Fathi Boudra Engineering Manager | Builds and Baselines, Release Linaro.org | Open source software for ARM SoCs

10 years, 1 month

IPA Profiling Enviornment Enabling

by Leo Yan

Hi Baoquan, I also add support(a)linaro.org so we can track and follow up your questions more formally. Also translate your question into English as we can ask more English speaker to help for related questions as needed. So the questions is "how to profiling IPA and enable ftrace event for it"? - In generally, please don't manually do this thing by yourself. Workload-automation has prepared all this profiling flow already: https://github.com/ARM-software/workload-automation This docuemenation is very important when you want to easily start: https://github.com/ARM-software/workload-automation/blob/master/doc/source/… - To enable workload-automation, you need set configuration file at host PC side so it can connect with board smoothly: This file usually is in the folder: ~/.workload_automation/config.py; so "wa" command will use this configuration file to connect target board. - Then need define the testing configuration file so that can run the test case automatically, enabling ftrace events, and finally output profiling log files, you can refer the file: ipa_tunning.yaml; wa run ~/ipa_tunning.yaml -d ipa_tunning So finally you will all logs are saved in "ipa_tunning" folder. - After get the result, it will save trace.dat file into the log folder, so you can use trappy to analyse the file for temperature curves. The trappy have a very good example file is: https://github.com/ARM-software/trappy/blob/master/doc/00%20-%20Quick%20sta… I have enclosed my ~/.workload_automation/config.py file and ipa_tunning.yaml for reference. If have any further question, just let me know. Thanks, Leo Yan On Mon, Jun 20, 2016 at 05:05:03PM +0800, lu.baoquan(a)zte.com.cn wrote: > Hi,All, > > 我们目前在Android6+Kernel4.1上面测试IPA。 > > 目前情况是： > 1.使能IPA； > 2.打开Function Tracer，下面这些events是否满足 > trace-cmd record -e cpu_frequency* -e cpu_idle -e thermal -e > thermal_power_allocator > > WA和TRAPpy对我们来说都是全新的，能否提供一个ready的模板： > 能否提供一个WA Agenda的模板 > 能否提供TRAPpy相关分析脚本，如果能和WA结合出一个结果。然后我们可以做其他修 > 改。 > -------------------------------------------------------- > ZTE Information Security Notice: The information contained in this mail (and any attachment transmitted herewith) is privileged and confidential and is intended for the exclusive use of the addressee(s). If you are not an intended recipient, any disclosure, reproduction, distribution or other dissemination or use of the information contained is strictly prohibited. If you have received this mail in error, please delete it and notify us immediately.

10 years, 2 months

Hikey Wifi 4.4 or mainline

by Michal Simek

Hi guys, I am playing with Hikey and I am able to get wifi up and running on 3.18 Linaro kernel base/hikey branch. But I am not able to get it work on 4.4 or mainline. The problem is that st_tty_open is not called that's why it looks like that problem could be with line discipline setup. Do you have any kernel/branch with 4.4+ where BT is working? Thanks, Michal -- Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91 w: www.monstr.eu p: +42-0-721842854 Maintainer of Linux kernel - Xilinx Microblaze Maintainer of Linux kernel - Xilinx Zynq ARM and ZynqMP ARM64 SoCs U-Boot custodian - Xilinx Microblaze/Zynq/ZynqMP SoCs

10 years, 2 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

10 years, 2 months

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.

10 years, 3 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 __ __ __ __ __ __ | .� >

10 years, 3 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/

10 years, 3 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

10 years, 3 months

← Newer
1
...
4
5
6
7
8
9
10
...
25
Older →

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Dev