Dev

dev@lists.96boards.org

241 discussions

by Fathi Boudra

Hi, There's a change pending to enable PSCI on HiKey: https://github.com/96boards/linux/pull/15 A regression is introduced when using HiSilicon bootloader: we'll have one core when using Hisilicon's bootloader. Here's the summary: * current dtb + hisilicon bootloader: boot images, all cores enabled * current dtb + uefi: boot images, one core enabled * psci enabled dtb + hisilicon bootloader: boot images, one core enabled * psci enabled dtb + uefi: boot images, all cores enabled It won't be much of an issue since the long term plan is to deprecate HiSilicon bootloader in favor of UEFI. Unfortunately, UEFI isn't feature complete (SD card support missing, flash to eMMC limited to 128M, etc...). In the meantime, moving forward it's proposed to provide a legacy dtb and use the PSCI enabled combination (UEFI + kernel) as the default as it is the long term plan. It mitigates the issue for people using HiSilicon bootloader while it enables people using UEFI. Another option is to keep the status quo until UEFI is there (speculation is "in 2 weeks") and switch the default dtb at that time. The question is which default dtb should be used? Opinions? Cheers, Fathi

11 years, 5 months

Issue with hikey USB OTG serial adapter

by Tyler Baker

Hi, I have been trying to flash Peter's u-boot port to my early access hikey board without success. I'm stuck trying to use the burn-boot tool as the usb-serial device used in download mode keeps disconnecting. [ 165.408788] option 3-3:1.0: device disconnected [ 251.495189] usb 3-3: new full-speed USB device number 6 using xhci_hcd [ 251.624288] usb 3-3: New USB device found, idVendor=12d1, idProduct=3609 [ 251.624292] usb 3-3: New USB device strings: Mfr=1, Product=4, SerialNumber=0 [ 251.624293] usb 3-3: Product: \xffffffe3\xffffff84\xffffffb0㌲㔴㜶㤸 [ 251.624295] usb 3-3: Manufacturer: 䕇䕎䥎 [ 251.624780] option 3-3:1.0: GSM modem (1-port) converter detected [ 251.624862] usb 3-3: GSM modem (1-port) converter now attached to ttyUSB0 [ 252.131320] usb 3-3: USB disconnect, device number 6 [ 252.131539] option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0 [ 252.131560] option 3-3:1.0: device disconnected What I have tried and has not worked. * Using various PC's, System76 laptop w/Ubuntu 14.10, Chromebook Pixel 2 w/Debian 8, and Dell XPS8700 w/Debian 8 headless. All these system show the kernel messages above. * Disabling network manager * sudo echo 12D1 3609 > /sys/bus/usb-serial/drivers/option1/new_id; sudo mknod /dev/ttyUSB0 c 188 0 as suggested by the wiki * Using other micro-usb cables. * Created a script to loop the burn-boot tool Any thing else to try? Thanks, -- Tyler Baker Tech Lead, LAVA Linaro.org | Open source software for ARM SoCs Follow Linaro: http://www.facebook.com/pages/Linaro http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog

11 years, 5 months

[PATCH] hikey: hi6220: ensure output directory exists

by Tyler Baker

Fixes a build error, as the output directory may not exists. Signed-off-by: Tyler Baker <tyler.baker(a)linaro.org> --- hikey-u-boot.mak | 1 + 1 file changed, 1 insertion(+) diff --git a/hikey-u-boot.mak b/hikey-u-boot.mak index dda967e..12d5f51 100644 --- a/hikey-u-boot.mak +++ b/hikey-u-boot.mak @@ -16,6 +16,7 @@ have-crosscompiler: build: have-crosscompiler FORCE rm -rf $(build_dir) + @mkdir -p $(output_dir) @mkdir -p $(build_dir) $(MAKE) O=$(build_dir) CROSS_COMPILE=$(CROSS_COMPILE) distclean $(MAKE) O=$(build_dir) CROSS_COMPILE=$(CROSS_COMPILE) hikey_aemv8a_config -- 2.1.0

11 years, 5 months

[PATCH 1/2] mmc: dwmmc-k3: set disable boot for initialization

by Haojian Zhuang

If mmc controler is accessed in bootloader, it's required to execute disable boot before resetting the controller & enabling the clock in kernel driver. Signed-off-by: Haojian Zhuang <haojian.zhuang(a)linaro.org> --- .../devicetree/bindings/mmc/k3-dw-mshc.txt | 7 +++++ drivers/mmc/host/dw_mmc-k3.c | 33 ++++++++++++++++++++++ drivers/mmc/host/dw_mmc.h | 1 + 3 files changed, 41 insertions(+) diff --git a/Documentation/devicetree/bindings/mmc/k3-dw-mshc.txt b/Documentation/devicetree/bindings/mmc/k3-dw-mshc.txt index 3b35449..cf12cfa 100644 --- a/Documentation/devicetree/bindings/mmc/k3-dw-mshc.txt +++ b/Documentation/devicetree/bindings/mmc/k3-dw-mshc.txt @@ -14,6 +14,13 @@ Required Properties: * compatible: should be one of the following. - "hisilicon,hi4511-dw-mshc": for controllers with hi4511 specific extensions. +Optional Properties: + +* "hisilicon,disable-boot" + - Disable boot before reseting mmc controller and enabling clocks. It's + required on Hisilicon Hi6220 SoC if the mmc controller is accessed in + bootloader. + Example: /* for Hi3620 */ diff --git a/drivers/mmc/host/dw_mmc-k3.c b/drivers/mmc/host/dw_mmc-k3.c index 83a9f49..3042a7c 100644 --- a/drivers/mmc/host/dw_mmc-k3.c +++ b/drivers/mmc/host/dw_mmc-k3.c @@ -11,6 +11,7 @@ #include <linux/module.h> #include <linux/platform_device.h> #include <linux/clk.h> +#include <linux/delay.h> #include <linux/mmc/host.h> #include <linux/mmc/dw_mmc.h> #include <linux/of_address.h> @@ -29,8 +30,40 @@ static void dw_mci_k3_set_ios(struct dw_mci *host, struct mmc_ios *ios) host->bus_hz = clk_get_rate(host->ciu_clk); } +static void disable_boot(struct dw_mci *host) +{ + int timeout = 0; + unsigned int data; + + mci_writel(host, CTRL, SDMMC_CTRL_FIFO_RESET); + mci_writel(host, CMD, SDMMC_CMD_START | SDMMC_CMD_DISABLE_BOOT); + + while (1) { + data = mci_readl(host, CMD) & 0x80000000; + if (data == 0) + break; + if (timeout < 2000) { + timeout++; + mdelay(1); + } else { + dev_warn(host->dev, "failed to stop MMC\n"); + break; + } + } +} + +static int dw_mci_k3_parse_dt(struct dw_mci *host) +{ + struct device_node *np = host->dev->of_node; + if (of_find_property(np, "hisilicon,disable-boot", NULL)) { + disable_boot(host); + } + return 0; +} + static const struct dw_mci_drv_data k3_drv_data = { .set_ios = dw_mci_k3_set_ios, + .parse_dt = dw_mci_k3_parse_dt, }; static const struct of_device_id dw_mci_k3_match[] = { diff --git a/drivers/mmc/host/dw_mmc.h b/drivers/mmc/host/dw_mmc.h index 01b99e8..8c5977b 100644 --- a/drivers/mmc/host/dw_mmc.h +++ b/drivers/mmc/host/dw_mmc.h @@ -115,6 +115,7 @@ #define SDMMC_CMD_START BIT(31) #define SDMMC_CMD_USE_HOLD_REG BIT(29) #define SDMMC_CMD_VOLT_SWITCH BIT(28) +#define SDMMC_CMD_DISABLE_BOOT BIT(26) #define SDMMC_CMD_CCS_EXP BIT(23) #define SDMMC_CMD_CEATA_RD BIT(22) #define SDMMC_CMD_UPD_CLK BIT(21) -- 1.9.1

11 years, 5 months

Upgrading UEFI in linux on hikey

by Koen Kooi

Hi, I got tired of switching out the jumper, connecting the micro-USB cable, etc and tried: root@hikey:~# dd if=/tmp/fip.bin of=/dev/mmcblk0p4 Which works, so if you want to upgrade UEFI you can do it in linux. And with the latest changes by Leo that I just merged into ATF 'reboot' now works as well! -- Koen Kooi Builds and Baselines | Release Manager Linaro.org | Open source software for ARM SoCs

11 years, 5 months

Reporting bugs on HiKey....

by Scott Bambrough

Hi everyone, Could I ask that people report all bugs regarding HiKey here: https://github.com/96boards/bugs/issues Also if you are working on an problem reported in a issue, please update the issue data with the current status when you send a status update out to the list. It is easier for us to track progress on the issues there rather than via email. Everything is all in one place then. This will make Usman and my job a lot easier. Thanks, Scott -- Scott Bambrough Technical Director, Member Services Linaro

11 years, 5 months

DIY mezzanine boards

by Daniel Thompson

Hi Folks I've been looking a simple ways to hack together a simple through hole mezzanine board. One way is to get hold of a small protoboard[1] and hook it up to a 2mm to 2.54mm converter board such as this one by a small outfit called bitwizard[2]. I've been in touch with bitwizard and they are happy to make a run of boards with a male connector on the underside of the adapter board so we can hook it up directly to the 96boards LS connector. After that I just plan to drop the protoboard on the 2.54mm pins, solder it down and start creating... However the postage costs from Holland might be a bit steep for just me so I wondered if anyone else was interested in a group buy. If you're in the UK I can post out from here... if you're not in the UK and want in on the action I guess I could hand over some boards at the next 'connect. Guesstimated numbers are £3 per board plus £1 for P&P. Daniel. [1] http://goo.gl/9hbSVe [2] http://www.bitwizard.nl/cat/product_info.php?cPath=35&products_id=139

11 years, 5 months

WiFi status summary on HiKey - WL1835MOD

by Guodong Xu

Hi, all As of today, 2015/3/16: WiFi status I said WiFi is stable before, however, more tests show me it is not. Or I should say when the signal is good, no extra beacon loss/reassociation, WiFi seems stable. Otherwise, there is big chance (as below) that WiFi will hang. Part 1) https://github.com/96boards/linux/issues/16 About issue: wl1271_sdio mmc2:0001:2: sdio write failed (-110) in Debian when configured in /etc/network/interfaces.d/wlan0 and WiFi is up and connected when system booting, it is very easy to observe a WiFi hang. The reason of this lies in firmware cannot be waken up from ELP (Extreme Low Power) mode. Note: not every wakeup from ELP mode will fail, there are still unknown 'random' factors. So right, the issue is not rootcaused. But, Workaround exists: disable ELP mode. Attached a new config file (please save it to board's /lib/firmware/ti-connectivity/ and rename it to wl18xx-conf.bin) which has ELP disabled. Or you can do this before wlan0 up: iw wlan0 set power_save off echo 0> /sys/kernel/debug/ieee80211/phy0/wlcore/sleep_auth ifconfig wlan0 up Part 2) There is another type of error which is easy to be reproduced when you run 'iw wlan0 disconnect' then run 'iw wlan0 scan' repeatedly. Two kinds of error messages but both point to a firmware-side timeout issue. They are: a) wlcore: ERROR SW watchdog interrupt received! That's a firmware watchdog timer interrupt and reported from FW to the host. b) wlcore: Scan completed due to error. That's a scan timeout error. By changing the timeout value from 30 seconds to longer does'n help. And again, here I didn't see any SDIO or wlcore driver side errors. The only thing noticeable is just a firmware side timeout. Next plan: 1) check why firmware 'hangs'. Due to limited accessibility to pins on WL1835 module, this is not easy. Can we get TI field engineers' help here? Anybody has any experience on similar issues? 2) check why the current wlcore recovery effort always fail. If this can help firmware out, it also helps. Thanks, -Guodong Xu

11 years, 5 months

Interacting with the firmware via HDMI + USB keyboard?

by Steve Capper

Hi, I've noticed that the HDMI on the Hikey board only really activates when the kernel boots. Are there plans for the boot firmware (UEFI soon?) to interact with the HDMI port (and USB keyboard)? Cheers, -- Steve

11 years, 5 months

UEFI support in linux for hikey

by Koen Kooi

Hi, I was reading https://www.kernel.org/doc/Documentation/arm/uefi.txt and it looks like I should have everything needed to get EFI stuff in linux, but instead I get: root@hikey:~# dmesg | grep -i efi [ 0.000000] efi: Getting EFI parameters from FDT: [ 0.000000] efi: UEFI not found. [ 0.079367] EFI services will not be available. Double checking: root@hikey:~# uname -a Linux hikey 4.0.0-rc3 #19 SMP Sun Mar 15 10:57:36 CET 2015 aarch64 GNU/Linux root@hikey:~# zcat /proc/config.gz | grep -i efi CONFIG_EFI_PARTITION=y CONFIG_EFI_STUB=y CONFIG_EFI=y CONFIG_RTC_DRV_EFI=y # EFI (Extensible Firmware Interface) Support CONFIG_EFI_VARS=y CONFIG_EFI_PARAMS_FROM_FDT=y CONFIG_EFI_RUNTIME_WRAPPERS=y CONFIG_EFI_ARMSTUB=y CONFIG_EFIVAR_FS=y So it has everything mentioned in the kernel doc, which goes on to say "The stub populates the FDT /chosen node with (and the kernel scans for) the following parameters: [linux,uefi-system-table and more]". On hikey I get this: root@hikey:~# dtc -I fs -O dts -o ~/effective.dts /proc/device-tree/ root@hikey:~# grep chosen -A4 effective.dts chosen { linux,initrd-end = <0x0 0x7fff200>; bootargs = "console=ttyAMA0,115200 earlycon=pl011,0xf8015000 root=/dev/sda1 rootwait ro "; linux,initrd-start = <0x0 0x7fff000>; }; This is an UEFI I built myself using https://github.com/96boards/edk2/commits/hikey with a change to use /dev/sda1 as root in bootargs, nothing more. What is needed to get linux to notice UEFI? It looks like all the bits are in place (bootloader, kernelstub, kernel config). -- Koen Kooi Builds and Baselines | Release Manager Linaro.org | Open source software for ARM SoCs

11 years, 5 months

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Dev