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
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
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
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
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
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
