Dev December 2015

dev@lists.96boards.org

23 participants
15 discussions

[ANN] Linaro Linux/Debian 15.11 release for DragonBoard 410c is available

by Nicolas Dechesne

hello there, A new release Linux release for the DragonBoard 410c is now available. The Linaro Linux release 15.11 is a Debian-based Linaro Build that provides developers with a desktop like environment using Ubuntu and the LXDE desktop, as well as a console-only image. What’s new in this release? * Based on Linux kernel v4.2.4 * Migration from Ubuntu 15.04 to Debian 8.0 (Jessie) * Various bug fixes and improvements reported on Bugzilla (including USB performance issue) Obviously, the main change is the migration to Debian, from Ubuntu, as I had announced in the previous release message. We believe it should be transparent for most users, if you need any assistance, or face any issues, please report on the forum or here. For more details and the list of bug fixes, or to download the release, please go to: http://builds.96boards.org/releases/dragonboard410c/linaro/debian/15.11 For general question or support request, please go to 96boards Community forum: https://www.96boards.org/dragonboard410c/forum For any bug related to this release, please submit issues to the 96Boards Bug tracking system: https://bugs.96boards.org/enter_bug.cgi?product=Dragonboard%20410c Finally, to get in touch with us, you can also use IRC: #96boards on irc.freenode.net On behalf of the Linaro Qualcomm Landing team, cheers, Nicolas

8 years, 4 months

JTAG @ Dragonboard

by Mateusz Kulikowski

Hi All, Contrary to popular believes, JTAG on Dragonboard seems to be operational. There is one catch - you need dongle worth thousands of USD for now :( I decided to write this post so maybe someone will help me to get it working on something cheaper. Short summary of my research below. @Peter - perhaps you could take a look and give some hints? 1) You need to solder JTAG connector to test points like that: http://rlyeh.eu/d/dragonboard_jtag.jpg (I suggest to protect test points as they're rather fragile and small). There is JTAG connector on the bottom, but I'm against using it because: - There are 4 DNI resistors (i.e. not installed) that have to be short. I don't know their location. - It requires fancy connector that is hard to get, and then you need some converter to standard 20-pin jtag cable. At least you need to solder: TDI, TDO, TMS, TCK, GND, VREF (VREG_L5_1P8) and TRST. I also wired SRST_N to RST pin of standard JTAG connector (but it's probably not needed) WARNING: you need dongle that is able to work/adapt to 1.8V. 2) There are 3 chips on JTAG chain, with software it's possible to disable some or all of them. Commands for OpenOCD: jtag newtap apq dap -expected-id 0x5ba00477 -irlen 4 <- This is ARM jtag newtap auto1 un1 -expected-id 0x000016dd -irlen 5 <- This is something (crypto processor?) jtag newtap auto2 un2 -expected-id 0x007060e1 -irlen 11 <- This is Hexagon core Commands for Trace32: Sum of length of all IR registers : 20. Number of JTAG devices (BYPASS registers) : 3. IDCODE of device 1 is : 0x007060e1 (QUALCOMM, QUALCOMM) SYS.CONFIG.DRPOST 0. SYS.CONFIG.DRPRE 2. SYS.CONFIG.IRPOST 0. SYS.CONFIG.IRPRE 9. (IRWIDTH 11.) IDCODE of device 2 is : 0x000016dd (Certicom Corporation, <unknown name>) SYS.CONFIG.DRPOST 1. SYS.CONFIG.DRPRE 1. SYS.CONFIG.IRPOST 11. SYS.CONFIG.IRPRE 4. (IRWIDTH 5.) IDCODE of device 3 is : 0x5ba00477 (ARM Ltd., ARM JTAG-DP DAP) SYS.CONFIG.DRPOST 2. SYS.CONFIG.DRPRE 0. SYS.CONFIG.IRPOST 16. SYS.CONFIG.IRPRE 0. (IRWIDTH 4.) <- This is ARM 3) Device configuration - single core for now: Commands for OpenOCD (they don't work though): target create apq aarch64 -chain-position apq.dap -dbgbase 0x80050000 -ctibase 0x80058000 -coreid 0 Commands for Trace32: SYStem.CPU CORTEXA53 SYStem.CONFIG CORENUMBER 1. SYStem.CONFIG.COREDEBUG.Base 0x80050000 SYStem.CONFIG.BMC.Base 0x80051000 SYStem.CONFIG.CTI.Base 0x80058000 SYStem.CONFIG.ETM.Base 0x8005c000 sys.option enreset off ;<-I'm not sure if this is needed for anything else than probe SYStem.Mode Attach 4) Results: - With Trace32, it is possible to attach, stop CPU. It's even possible to halt it in Secure mode (at least it looks like that). Some parts of memory (and system registers) are not accessible - probably ones that are Secure. - With OpenOCD (branch made by Peter Griffin), JTAG chain is visible properly, but probing of CPU fails: -------------- LOG Debug: 271 328 openocd.c:150 handle_init_command(): Examining targets... Debug: 272 328 target.c:1417 target_call_event_callbacks(): target event 21 (examine-start) Debug: 273 328 arm_adi_v5.c:647 ahbap_debugport_init(): Debug: 274 329 arm_adi_v5.c:688 ahbap_debugport_init(): DAP: wait CDBGPWRUPACK Debug: 275 329 arm_adi_v5.h:391 dap_dp_poll_register(): DAP: poll 4, mask 0x0820000000, value 0x20000000 Debug: 276 329 arm_adi_v5.c:695 ahbap_debugport_init(): DAP: wait CSYSPWRUPACK Debug: 277 329 arm_adi_v5.h:391 dap_dp_poll_register(): DAP: poll 4, mask 0x0880000000, value 0x80000000 Debug: 278 433 arm_adi_v5.h:404 dap_dp_poll_register(): DAP: poll 4 timeout Debug: 279 433 openocd.c:152 handle_init_command(): target examination failed -------------- END of LOG I've also attached diag data from Trace that can be useful for someone (I think I missed few DAP entries, but all CPUs are probably there). Best Regards, Mateusz

8 years, 4 months

enable Estuary Release Distribution on Hikey

by Xinwei Kong

hi all, HiKey will support Ubuntu, Debian and Fedora systerm and so on for estuary. visit:http://open-estuary.com/ You try Estuary for HiKey and if you meet testing problem, we will improve it. First, here is what you did: >>>> mkdir ~/work/open-estuary cd ~/work/open-estuary repo init -u https://github.com/open-estuary/estuary.git repo sync cd estuary ./build.sh -p HiKey -d Ubuntu >>>> Thank you xinwei

8 years, 4 months

Re: [Dev] Problem running AOSP build from source

by Vishal Bhoj

Hi Daniel, Can you share the logcat output as well ? On 01-Dec-2015 5:49 pm, "Daniel Schneider" <Daniel.Schneider1(a)hs-augsburg.de> wrote: > Thanks for the fast reply. > Yes i copied the files gralloc.hikey.so + libGLES_mali.so from > ../vendor/vendor/mali/64bit > into the ../android/ folder where i built the AOSP. > > > Am Dienstag, 01. Dezember 2015 12:40 CET, Vishal Bhoj < > vishal.bhoj(a)linaro.org> schrieb: > > > Hi Daniel, > > > > > > Did you download and extract vendor.tar.bz2 in AOSP source tree: > > > http://builds.96boards.org/snapshots/hikey/linaro/binaries/20150706/vendor.… > > > > On 1 December 2015 at 17:05, Daniel Schneider < > > Daniel.Schneider1(a)hs-augsburg.de> wrote: > > > > > Hi, > > > > > > The goal is to be able to run my own AOSP RPB Builds > > > However i've got problems at running my own CE AOSP RPB HiKey Build > with > > > the instructions from the wiki [1]: > > > Note: Installing and booting the pre-build binaries works fine. > > > I first tried to build the AOSP Images with the Instructions from [1] > and > > > used it with the self built bootloader files from [3]. > > > Building AOSP and the bootloader files was successful, so was flashing > on > > > the Hikey Board acc. to[3] + [2]. It then > > > started booting but did not boot correctly into Android but instead > showed > > > the following log message during boot: > > > > > > > > > [ 6.433602] EXT4-fs (mmcblk0p9): mounted filesystem with ordered > data > > > mode. Opts: (null) > > > [ 6.442000] fs_mgr: > > > > __mount(source=/dev/block/platform/f723d000.dwmmc0/by-name/system,target=/system,type=ext4)=0 > > > [ 6.487806] EXT4-fs (mmcblk0p8): mounting with "discard" option, but > > > the device does not support discard > > > [ 6.497310] EXT4-fs (mmcblk0p8): mounted filesystem with ordered > data > > > mode. Opts: discard,noauto_da_alloc,data=ordered,user_xatt1 > > > [ 6.510642] fs_mgr: > > > > __mount(source=/dev/block/platform/f723d000.dwmmc0/by-name/cache,target=/cache,type=ext4)=0 > > > [ 6.556490] EXT4-fs (mmcblk0p10): mounting with "discard" option, > but > > > the device does not support discard > > > [ 6.566146] EXT4-fs (mmcblk0p10): mounted filesystem with ordered > data > > > mode. Opts: discard,noauto_da_alloc,data=ordered,user_xat1 > > > [ 6.579670] fs_mgr: > > > > __mount(source=/dev/block/platform/f723d000.dwmmc0/by-name/userdata,target=/data,type=ext4)=0 > > > [ 6.591402] file system registered > > > [ 6.596261] init: Starting service 'adbd'... > > > [ 6.605118] read descriptors > > > [ 6.605180] init: Starting service 'logd'... > > > [ 6.612277] read strings > > > [ 6.655015] rfkill: version magic '3.18.0+ SMP preempt mod_unload > > > aarch64' should be '3.18.0+ SMP preempt aarch64' > > > [ 6.670410] compat: version magic '3.18.0+ SMP preempt mod_unload > > > aarch64' should be '3.18.0+ SMP preempt aarch64' > > > [ 6.729645] cfg80211: version magic '3.18.0+ SMP preempt mod_unload > > > aarch64' should be '3.18.0+ SMP preempt aarch64' > > > [ 6.796284] mac80211: version magic '3.18.0+ SMP preempt mod_unload > > > aarch64' should be '3.18.0+ SMP preempt aarch64' > > > [ 6.845168] wlcore: version magic '3.18.0+ SMP preempt mod_unload > > > aarch64' should be '3.18.0+ SMP preempt aarch64' > > > [ 6.864117] logd.auditd: start > > > [ 6.872944] wl18xx: version magic '3.18.0+ SMP preempt mod_unload > > > aarch64' should be '3.18.0+ SMP preempt aarch64' > > > [ 6.886715] wlcore_sdio: version magic '3.18.0+ SMP preempt > mod_unload > > > aarch64' should be '3.18.0+ SMP preempt aarch64' > > > [ 7.162376] bluetooth: version magic '3.18.0+ SMP preempt mod_unload > > > aarch64' should be '3.18.0+ SMP preempt aarch64' > > > [ 7.206857] hidp: version magic '3.18.0+ SMP preempt mod_unload > > > aarch64' should be '3.18.0+ SMP preempt aarch64' > > > [ 7.266267] rfcomm: version magic '3.18.0+ SMP preempt mod_unload > > > aarch64' should be '3.18.0+ SMP preempt aarch64' > > > [ 7.304858] st_drv: version magic '3.18.0+ SMP preempt mod_unload > > > aarch64' should be '3.18.0+ SMP preempt aarch64' > > > [ 7.315514] (stk) : timed out waiting for ldisc to be un-installed > > > [ 7.333862] tty_hci: version magic '3.18.0+ SMP preempt mod_unload > > > aarch64' should be '3.18.0+ SMP preempt aarch64' > > > [ 7.361656] btwilink: version magic '3.18.0+ SMP preempt mod_unload > > > aarch64' should be '3.18.0+ SMP preempt aarch64' > > > [ 7.428522] (stk) :ldisc_install = 1 > > > [ 7.440337] gator: version magic '3.18.0+ SMP preempt mod_unload > > > aarch64' should be '3.18.0+ SMP preempt aarch64' > > > [ 7.457707] init: Starting service 'vold'... > > > [ 7.465446] init: Not bootcharting. > > > > > > Then I built AOSP for Android 6.0 by making the following changes to > the > > > build instructions : > > > I used the branch android-6.0.0.r1 (instead of android-5.1.1._r1) for > the > > > repo init and android-6.0 (instead of android-5.0) for the > local_manifest. > > > I also > > > used the bootloader files from my own build. This time the log message > > > during boot was: > > > > > > [ 6.441490] EXT4-fs (mmcblk0p9): mounted filesystem with ordered > data > > > mode. Opts: (null) > > > [ 6.449859] fs_mgr: > > > > __mount(source=/dev/block/platform/f723d000.dwmmc0/by-name/system,target=/system,type=ext4)=0 > > > [ 6.596897] EXT4-fs (mmcblk0p8): recovery complete > > > [ 6.603855] EXT4-fs (mmcblk0p8): mounting with "discard" option, but > > > the device does not support discard > > > [ 6.613491] EXT4-fs (mmcblk0p8): mounted filesystem with ordered > data > > > mode. Opts: discard,noauto_da_alloc,data=ordered,user_xatt1 > > > [ 6.626964] fs_mgr: > > > > __mount(source=/dev/block/platform/f723d000.dwmmc0/by-name/cache,target=/cache,type=ext4)=0 > > > [ 6.726001] random: nonblocking pool is initialized > > > [ 7.305400] (stk) : timed out waiting for ldisc to be un-installed > > > [ 7.418574] (stk) :ldisc_install = 1[ 7.735815] EXT4-fs > > > (mmcblk0p10): recovery complete > > > [ 7.742897] EXT4-fs (mmcblk0p10): mounting with "discard" option, > but > > > the device does not support discard > > > [ 7.752645] EXT4-fs (mmcblk0p10): mounted filesystem with ordered > data > > > mode. Opts: discard,noauto_da_alloc,data=ordered,user_xat1 > > > [ 7.766184] fs_mgr: > > > > __mount(source=/dev/block/platform/f723d000.dwmmc0/by-name/userdata,target=/data,type=ext4)=0 > > > [ 7.777627] file system registered > > > [ 7.782144] init: Starting service 'adbd'... > > > [ 7.791612] read descriptors > > > [ 7.791990] init: Starting service 'logd'... > > > [ 7.798827] read strings > > > [ 7.812920] Loading modules backported from Linux version 3cf1c17 > > > [ 7.819068] Backport generated by backports.git 5394a1d > > > [ 7.856620] cfg80211: Calling CRDA to update world regulatory domain > > > [ 7.956810] init: Starting service 'vold'... > > > [ 7.962186] init: Not bootcharting. > > > [ 7.967196] wl18xx_driver wl18xx.0.auto: Direct firmware load for > > > ti-connectivity/wl1271-nvs.bin failed with error -2 > > > [ 7.977844] wl18xx_driver wl18xx.0.auto: Falling back to user helper > > > [ 7.990973] init: Starting service 'exec 0 > (/system/bin/tzdatacheck)'... > > > [ 8.082339] init: Service 'exec 0 (/system/bin/tzdatacheck)' (pid > 1478) > > > exited with status 0 > > > [ 8.083243] logd.auditd: start > > > [ 8.083361] logd.klogd: 8078974165 > > > [ 8.099467] init: SELinux: Could not get canonical path > > > /data/local/tmp/lava restorecon: No such file or directory. > > > [ 8.118620] init: property_set("ro.secure", "0") failed > > > [ 8.124122] init: (Loading properties from /system/build.prop took > > > 0.01s.) > > > [ 8.131149] init: (Loading properties from /vendor/build.prop took > > > 0.00s.) > > > [ 8.138098] init: (Loading properties from /factory/factory.prop > took > > > 0.00s.) > > > [ 8.145335] init: (Loading properties from /data/local.prop took > 0.00s.) > > > [ 8.152256] init: /recovery not specified in fstab > > > [ 8.157346] init: Starting service 'logd-reinit'... > > > [ 8.164797] init: Starting service 'healthd'... > > > [ 8.170030] init: Starting service 'lmkd'... > > > [ 8.171893] binder: 1489:1489 transaction failed 29189, size 0-0 > > > [ 8.177075] logd.daemon: reinit > > > [ 8.184277] init: Starting service 'servicemanager'... > > > [ 8.186238] wl18xx_driver wl18xx.0.auto: Direct firmware load for > > > ti-connectivity/wl18xx-conf.bin failed with error -2 > > > [ 8.186242] wl18xx_driver wl18xx.0.auto: Falling back to user helper > > > [ 8.187620] wlcore: ERROR could not get configuration binary > > > ti-connectivity/wl18xx-conf.bin: -11 > > > [ 8.187623] wlcore: WARNING falling back to default config > > > [ 8.221811] init: Starting service 'surfaceflinger'... > > > [ 8.227444] init: Service 'logd-reinit' (pid 1488) exited with > status 0 > > > [ 8.234266] init: property_set("ro.build.product", "generic") failed > > > [ 8.241015] init: property_set("ro.product.device", "generic") > failed > > > [ 8.248542] init: Starting service 'console'... > > > [ 8.253876] init: Starting service 'netd'... > > > [ 8.258852] init: Starting service 'debuggerd'... > > > [ 8.264117] init: Starting service 'debuggerd64'... > > > [ 8.269429] init: cannot find '/system/bin/rild', disabling > 'ril-daemon' > > > [ 8.276521] init: Starting service 'drm'... > > > [ 8.281427] init: Starting service 'media'... > > > [ 8.286577] init: Starting service 'installd'... > > > [ 8.291567] init: cannot find '/system/bin/install-recovery.sh', > > > disabling 'flash_recovery' > > > [ 8.300353] init: Starting service 'keystore'... > > > [ 8.305671] init: Starting service 'uim'... > > > [ 8.310546] init: Starting service 'zygote'... > > > [ 8.315682] init: Starting service 'zygote_secondary'... > > > [ 8.321742] init: Starting service 'gatekeeperd'... > > > [ 8.324669] of_dma_request_slave_channel: dma-names property of node > > > '/smb/uart@f7111000' missing or empty > > > [ 8.324679] uart-pl011 f7111000.uart: no DMA platform data > > > [ 8.349327] init: Starting service 'perfprofd'... > > > [ 8.375151] (stc): st_tty_open > > > [ 8.378183] (stk) :line discipline installed(stk) > > > :ti-connectivity/TIInit_11.8.32.bts > > > [ 8.391144] (stk) :change remote baud rate command in firmware(stk) > > > :skipping the wait event of change remote baud > > > [ 8.445038] wlcore: wl18xx HW: 183x or 180x, PG 2.2 (ROM 0x11) > > > [ 8.455602] wlcore: loaded > > > [ 8.458358] wlcore: driver version: > > > [ 8.461934] wlcore: compilation time: 11:54, Beijing, 09-Apr-2015 > > > shell@hikey:/ $ [ 9.127873] (stc): add_channel_to_table: id 4 > > > [ 9.132244] (stc): add_channel_to_table: id 2 > > > [ 9.136627] (stc): add_channel_to_table: id 3 > > > [ 9.173303] healthd: No charger supplies found > > > [ 9.177832] healthd: No battery devices found > > > [ 9.356078] init: Service 'surfaceflinger' (pid 1497) killed by > signal 6 > > > [ 9.362814] init: Service 'surfaceflinger' (pid 1497) killing any > > > children in process group > > > [ 9.371245] init: Service 'zygote' is being killed... > > > [ 9.379745] dwc2 f72c0000.usb: bound driver configfs-gadget > > > [ 9.388709] init: Service 'zygote' (pid 1557) killed by signal 9 > > > [ 9.394794] init: Service 'zygote' (pid 1557) killing any children > in > > > process group > > > [ 9.402579] init: write_file: Unable to open > > > '/sys/android_power/request_state': No such file or directory > > > [ 9.412366] init: write_file: Unable to write to '/sys/power/state': > > > Invalid argument > > > [ 9.420311] init: Service 'media' is being killed... > > > [ 9.425456] init: Service 'netd' is being killed... > > > [ 9.430625] init: Service 'media' (pid 1546) killed by signal 9 > > > [ 9.436643] init: Service 'media' (pid 1546) killing any children in > > > process group > > > [ 9.444371] init: Service 'netd' (pid 1542) killed by signal 9 > > > [ 9.450230] init: Service 'netd' (pid 1542) killing any children in > > > process group > > > [ 9.457996] init: Untracked pid 1673 killed by signal 9 > > > [ 9.466537] dwc2 f72c0000.usb: bound driver configfs-gadget > > > [ 9.475254] init: write_file: Unable to open > > > '/sys/class/android_usb/android0/enable': No such file or directory > > > [ 9.485465] init: write_file: Unable to open > > > '/sys/class/android_usb/android0/idVendor': No such file or directory > > > [ 9.495870] init: write_file: Unable to open > > > '/sys/class/android_usb/android0/idProduct': No such file or directory > > > [ 9.506401] init: write_file: Unable to open > > > '/sys/class/android_usb/android0/functions': No such file or directory > > > [ 9.516908] init: write_file: Unable to open > > > '/sys/class/android_usb/android0/enable': No such file or directory > > > [ 9.527236] init: write_file: Unable to write to > > > '/sys/kernel/config/usb_gadget/g1/UDC': Device or resource busy > > > [ 9.540650] dwc2 f72c0000.usb: bound driver configfs-gadget > > > [ 9.767073] dwc2 f72c0000.usb: new device is high-speed > > > [ 9.879422] dwc2 f72c0000.usb: new device is high-speed > > > [ 9.936162] dwc2 f72c0000.usb: new address 9 > > > [ 9.959138] configfs-gadget gadget: high-speed config #1: c > > > [ 11.144699] (stc): remove_channel_from_table: id 3 > > > [ 11.149520] (stc): remove_channel_from_table: id 2 > > > [ 11.154316] (stc): remove_channel_from_table: id 4 > > > [ 11.159179] (stc): all chnl_ids unregistered > > > [ 11.163474] (stk) :ldisc_install = 0(stc): st_tty_close > > > [ 12.175454] (hci_tty): called dumb_hci_callback > > > [ 13.553970] init: Starting service 'netd'... > > > [ 13.559074] init: Starting service 'surfaceflinger'... > > > [ 13.565316] init: Starting service 'media'... > > > [ 13.570388] init: Starting service 'zygote'... > > > [ 13.720157] init: Service 'surfaceflinger' (pid 1679) killed by > signal 6 > > > [ 13.726955] init: Service 'surfaceflinger' (pid 1679) killing any > > > children in process group > > > [ 13.735408] init: Service 'zygote' is being killed... > > > [ 13.743204] init: Service 'zygote' (pid 1683) killed by signal 9 > > > [ 13.749314] init: Service 'zygote' (pid 1683) killing any children > in > > > process group > > > [ 13.757137] init: write_file: Unable to open > > > '/sys/android_power/request_state': No such file or directory > > > [ 13.766965] init: write_file: Unable to write to '/sys/power/state': > > > Invalid argument > > > [ 13.774928] init: Service 'media' is being killed... > > > [ 13.779999] init: Service 'netd' is being killed... > > > [ 13.785208] init: Service 'media' (pid 1680) killed by signal 9 > > > [ 13.791197] init: Service 'media' (pid 1680) killing any children in > > > process group > > > [ 13.799067] init: Service 'netd' (pid 1678) killed by signal 9 > > > [ 13.804960] init: Service 'netd' (pid 1678) killing any children in > > > process group > > > [ 13.812752] init: Untracked pid 1710 killed by signal 9 > > > > > > > > > So i'd like to know/ need some help what AOSP Build Instruction to > follow > > > to be able to build and run Android 6.0 from source. > > > > > > > > > > > > Regards, > > > > > > Daniel > > > > > > > > > [1] > > > > https://github.com/96boards/documentation/wiki/CE-AOSP-RPB-HiKey-15.10-Build > > > > > > [2] > > > > https://github.com/96boards/documentation/wiki/CE-AOSP-RPB-HiKey-15.10-Inst… > > > > > > [3] https://github.com/96boards/documentation/wiki/HiKeyUEFI > > > > > > _______________________________________________ > > > Dev mailing list > > > Dev(a)lists.96boards.org > > > https://lists.96boards.org/mailman/listinfo/dev > > > > > > > > > >

8 years, 4 months

Problem running AOSP build from source

by Daniel Schneider

Hi, The goal is to be able to run my own AOSP RPB Builds However i've got problems at running my own CE AOSP RPB HiKey Build with the instructions from the wiki [1]: Note: Installing and booting the pre-build binaries works fine. I first tried to build the AOSP Images with the Instructions from [1] and used it with the self built bootloader files from [3]. Building AOSP and the bootloader files was successful, so was flashing on the Hikey Board acc. to[3] + [2]. It then started booting but did not boot correctly into Android but instead showed the following log message during boot: [ 6.433602] EXT4-fs (mmcblk0p9): mounted filesystem with ordered data mode. Opts: (null) [ 6.442000] fs_mgr: __mount(source=/dev/block/platform/f723d000.dwmmc0/by-name/system,target=/system,type=ext4)=0 [ 6.487806] EXT4-fs (mmcblk0p8): mounting with "discard" option, but the device does not support discard [ 6.497310] EXT4-fs (mmcblk0p8): mounted filesystem with ordered data mode. Opts: discard,noauto_da_alloc,data=ordered,user_xatt1 [ 6.510642] fs_mgr: __mount(source=/dev/block/platform/f723d000.dwmmc0/by-name/cache,target=/cache,type=ext4)=0 [ 6.556490] EXT4-fs (mmcblk0p10): mounting with "discard" option, but the device does not support discard [ 6.566146] EXT4-fs (mmcblk0p10): mounted filesystem with ordered data mode. Opts: discard,noauto_da_alloc,data=ordered,user_xat1 [ 6.579670] fs_mgr: __mount(source=/dev/block/platform/f723d000.dwmmc0/by-name/userdata,target=/data,type=ext4)=0 [ 6.591402] file system registered [ 6.596261] init: Starting service 'adbd'... [ 6.605118] read descriptors [ 6.605180] init: Starting service 'logd'... [ 6.612277] read strings [ 6.655015] rfkill: version magic '3.18.0+ SMP preempt mod_unload aarch64' should be '3.18.0+ SMP preempt aarch64' [ 6.670410] compat: version magic '3.18.0+ SMP preempt mod_unload aarch64' should be '3.18.0+ SMP preempt aarch64' [ 6.729645] cfg80211: version magic '3.18.0+ SMP preempt mod_unload aarch64' should be '3.18.0+ SMP preempt aarch64' [ 6.796284] mac80211: version magic '3.18.0+ SMP preempt mod_unload aarch64' should be '3.18.0+ SMP preempt aarch64' [ 6.845168] wlcore: version magic '3.18.0+ SMP preempt mod_unload aarch64' should be '3.18.0+ SMP preempt aarch64' [ 6.864117] logd.auditd: start [ 6.872944] wl18xx: version magic '3.18.0+ SMP preempt mod_unload aarch64' should be '3.18.0+ SMP preempt aarch64' [ 6.886715] wlcore_sdio: version magic '3.18.0+ SMP preempt mod_unload aarch64' should be '3.18.0+ SMP preempt aarch64' [ 7.162376] bluetooth: version magic '3.18.0+ SMP preempt mod_unload aarch64' should be '3.18.0+ SMP preempt aarch64' [ 7.206857] hidp: version magic '3.18.0+ SMP preempt mod_unload aarch64' should be '3.18.0+ SMP preempt aarch64' [ 7.266267] rfcomm: version magic '3.18.0+ SMP preempt mod_unload aarch64' should be '3.18.0+ SMP preempt aarch64' [ 7.304858] st_drv: version magic '3.18.0+ SMP preempt mod_unload aarch64' should be '3.18.0+ SMP preempt aarch64' [ 7.315514] (stk) : timed out waiting for ldisc to be un-installed [ 7.333862] tty_hci: version magic '3.18.0+ SMP preempt mod_unload aarch64' should be '3.18.0+ SMP preempt aarch64' [ 7.361656] btwilink: version magic '3.18.0+ SMP preempt mod_unload aarch64' should be '3.18.0+ SMP preempt aarch64' [ 7.428522] (stk) :ldisc_install = 1 [ 7.440337] gator: version magic '3.18.0+ SMP preempt mod_unload aarch64' should be '3.18.0+ SMP preempt aarch64' [ 7.457707] init: Starting service 'vold'... [ 7.465446] init: Not bootcharting. Then I built AOSP for Android 6.0 by making the following changes to the build instructions : I used the branch android-6.0.0.r1 (instead of android-5.1.1._r1) for the repo init and android-6.0 (instead of android-5.0) for the local_manifest. I also used the bootloader files from my own build. This time the log message during boot was: [ 6.441490] EXT4-fs (mmcblk0p9): mounted filesystem with ordered data mode. Opts: (null) [ 6.449859] fs_mgr: __mount(source=/dev/block/platform/f723d000.dwmmc0/by-name/system,target=/system,type=ext4)=0 [ 6.596897] EXT4-fs (mmcblk0p8): recovery complete [ 6.603855] EXT4-fs (mmcblk0p8): mounting with "discard" option, but the device does not support discard [ 6.613491] EXT4-fs (mmcblk0p8): mounted filesystem with ordered data mode. Opts: discard,noauto_da_alloc,data=ordered,user_xatt1 [ 6.626964] fs_mgr: __mount(source=/dev/block/platform/f723d000.dwmmc0/by-name/cache,target=/cache,type=ext4)=0 [ 6.726001] random: nonblocking pool is initialized [ 7.305400] (stk) : timed out waiting for ldisc to be un-installed [ 7.418574] (stk) :ldisc_install = 1[ 7.735815] EXT4-fs (mmcblk0p10): recovery complete [ 7.742897] EXT4-fs (mmcblk0p10): mounting with "discard" option, but the device does not support discard [ 7.752645] EXT4-fs (mmcblk0p10): mounted filesystem with ordered data mode. Opts: discard,noauto_da_alloc,data=ordered,user_xat1 [ 7.766184] fs_mgr: __mount(source=/dev/block/platform/f723d000.dwmmc0/by-name/userdata,target=/data,type=ext4)=0 [ 7.777627] file system registered [ 7.782144] init: Starting service 'adbd'... [ 7.791612] read descriptors [ 7.791990] init: Starting service 'logd'... [ 7.798827] read strings [ 7.812920] Loading modules backported from Linux version 3cf1c17 [ 7.819068] Backport generated by backports.git 5394a1d [ 7.856620] cfg80211: Calling CRDA to update world regulatory domain [ 7.956810] init: Starting service 'vold'... [ 7.962186] init: Not bootcharting. [ 7.967196] wl18xx_driver wl18xx.0.auto: Direct firmware load for ti-connectivity/wl1271-nvs.bin failed with error -2 [ 7.977844] wl18xx_driver wl18xx.0.auto: Falling back to user helper [ 7.990973] init: Starting service 'exec 0 (/system/bin/tzdatacheck)'... [ 8.082339] init: Service 'exec 0 (/system/bin/tzdatacheck)' (pid 1478) exited with status 0 [ 8.083243] logd.auditd: start [ 8.083361] logd.klogd: 8078974165 [ 8.099467] init: SELinux: Could not get canonical path /data/local/tmp/lava restorecon: No such file or directory. [ 8.118620] init: property_set("ro.secure", "0") failed [ 8.124122] init: (Loading properties from /system/build.prop took 0.01s.) [ 8.131149] init: (Loading properties from /vendor/build.prop took 0.00s.) [ 8.138098] init: (Loading properties from /factory/factory.prop took 0.00s.) [ 8.145335] init: (Loading properties from /data/local.prop took 0.00s.) [ 8.152256] init: /recovery not specified in fstab [ 8.157346] init: Starting service 'logd-reinit'... [ 8.164797] init: Starting service 'healthd'... [ 8.170030] init: Starting service 'lmkd'... [ 8.171893] binder: 1489:1489 transaction failed 29189, size 0-0 [ 8.177075] logd.daemon: reinit [ 8.184277] init: Starting service 'servicemanager'... [ 8.186238] wl18xx_driver wl18xx.0.auto: Direct firmware load for ti-connectivity/wl18xx-conf.bin failed with error -2 [ 8.186242] wl18xx_driver wl18xx.0.auto: Falling back to user helper [ 8.187620] wlcore: ERROR could not get configuration binary ti-connectivity/wl18xx-conf.bin: -11 [ 8.187623] wlcore: WARNING falling back to default config [ 8.221811] init: Starting service 'surfaceflinger'... [ 8.227444] init: Service 'logd-reinit' (pid 1488) exited with status 0 [ 8.234266] init: property_set("ro.build.product", "generic") failed [ 8.241015] init: property_set("ro.product.device", "generic") failed [ 8.248542] init: Starting service 'console'... [ 8.253876] init: Starting service 'netd'... [ 8.258852] init: Starting service 'debuggerd'... [ 8.264117] init: Starting service 'debuggerd64'... [ 8.269429] init: cannot find '/system/bin/rild', disabling 'ril-daemon' [ 8.276521] init: Starting service 'drm'... [ 8.281427] init: Starting service 'media'... [ 8.286577] init: Starting service 'installd'... [ 8.291567] init: cannot find '/system/bin/install-recovery.sh', disabling 'flash_recovery' [ 8.300353] init: Starting service 'keystore'... [ 8.305671] init: Starting service 'uim'... [ 8.310546] init: Starting service 'zygote'... [ 8.315682] init: Starting service 'zygote_secondary'... [ 8.321742] init: Starting service 'gatekeeperd'... [ 8.324669] of_dma_request_slave_channel: dma-names property of node '/smb/uart@f7111000' missing or empty [ 8.324679] uart-pl011 f7111000.uart: no DMA platform data [ 8.349327] init: Starting service 'perfprofd'... [ 8.375151] (stc): st_tty_open [ 8.378183] (stk) :line discipline installed(stk) :ti-connectivity/TIInit_11.8.32.bts [ 8.391144] (stk) :change remote baud rate command in firmware(stk) :skipping the wait event of change remote baud [ 8.445038] wlcore: wl18xx HW: 183x or 180x, PG 2.2 (ROM 0x11) [ 8.455602] wlcore: loaded [ 8.458358] wlcore: driver version: [ 8.461934] wlcore: compilation time: 11:54, Beijing, 09-Apr-2015 shell@hikey:/ $ [ 9.127873] (stc): add_channel_to_table: id 4 [ 9.132244] (stc): add_channel_to_table: id 2 [ 9.136627] (stc): add_channel_to_table: id 3 [ 9.173303] healthd: No charger supplies found [ 9.177832] healthd: No battery devices found [ 9.356078] init: Service 'surfaceflinger' (pid 1497) killed by signal 6 [ 9.362814] init: Service 'surfaceflinger' (pid 1497) killing any children in process group [ 9.371245] init: Service 'zygote' is being killed... [ 9.379745] dwc2 f72c0000.usb: bound driver configfs-gadget [ 9.388709] init: Service 'zygote' (pid 1557) killed by signal 9 [ 9.394794] init: Service 'zygote' (pid 1557) killing any children in process group [ 9.402579] init: write_file: Unable to open '/sys/android_power/request_state': No such file or directory [ 9.412366] init: write_file: Unable to write to '/sys/power/state': Invalid argument [ 9.420311] init: Service 'media' is being killed... [ 9.425456] init: Service 'netd' is being killed... [ 9.430625] init: Service 'media' (pid 1546) killed by signal 9 [ 9.436643] init: Service 'media' (pid 1546) killing any children in process group [ 9.444371] init: Service 'netd' (pid 1542) killed by signal 9 [ 9.450230] init: Service 'netd' (pid 1542) killing any children in process group [ 9.457996] init: Untracked pid 1673 killed by signal 9 [ 9.466537] dwc2 f72c0000.usb: bound driver configfs-gadget [ 9.475254] init: write_file: Unable to open '/sys/class/android_usb/android0/enable': No such file or directory [ 9.485465] init: write_file: Unable to open '/sys/class/android_usb/android0/idVendor': No such file or directory [ 9.495870] init: write_file: Unable to open '/sys/class/android_usb/android0/idProduct': No such file or directory [ 9.506401] init: write_file: Unable to open '/sys/class/android_usb/android0/functions': No such file or directory [ 9.516908] init: write_file: Unable to open '/sys/class/android_usb/android0/enable': No such file or directory [ 9.527236] init: write_file: Unable to write to '/sys/kernel/config/usb_gadget/g1/UDC': Device or resource busy [ 9.540650] dwc2 f72c0000.usb: bound driver configfs-gadget [ 9.767073] dwc2 f72c0000.usb: new device is high-speed [ 9.879422] dwc2 f72c0000.usb: new device is high-speed [ 9.936162] dwc2 f72c0000.usb: new address 9 [ 9.959138] configfs-gadget gadget: high-speed config #1: c [ 11.144699] (stc): remove_channel_from_table: id 3 [ 11.149520] (stc): remove_channel_from_table: id 2 [ 11.154316] (stc): remove_channel_from_table: id 4 [ 11.159179] (stc): all chnl_ids unregistered [ 11.163474] (stk) :ldisc_install = 0(stc): st_tty_close [ 12.175454] (hci_tty): called dumb_hci_callback [ 13.553970] init: Starting service 'netd'... [ 13.559074] init: Starting service 'surfaceflinger'... [ 13.565316] init: Starting service 'media'... [ 13.570388] init: Starting service 'zygote'... [ 13.720157] init: Service 'surfaceflinger' (pid 1679) killed by signal 6 [ 13.726955] init: Service 'surfaceflinger' (pid 1679) killing any children in process group [ 13.735408] init: Service 'zygote' is being killed... [ 13.743204] init: Service 'zygote' (pid 1683) killed by signal 9 [ 13.749314] init: Service 'zygote' (pid 1683) killing any children in process group [ 13.757137] init: write_file: Unable to open '/sys/android_power/request_state': No such file or directory [ 13.766965] init: write_file: Unable to write to '/sys/power/state': Invalid argument [ 13.774928] init: Service 'media' is being killed... [ 13.779999] init: Service 'netd' is being killed... [ 13.785208] init: Service 'media' (pid 1680) killed by signal 9 [ 13.791197] init: Service 'media' (pid 1680) killing any children in process group [ 13.799067] init: Service 'netd' (pid 1678) killed by signal 9 [ 13.804960] init: Service 'netd' (pid 1678) killing any children in process group [ 13.812752] init: Untracked pid 1710 killed by signal 9 So i'd like to know/ need some help what AOSP Build Instruction to follow to be able to build and run Android 6.0 from source. Regards, Daniel [1] https://github.com/96boards/documentation/wiki/CE-AOSP-RPB-HiKey-15.10-Build [2] https://github.com/96boards/documentation/wiki/CE-AOSP-RPB-HiKey-15.10-Inst… [3] https://github.com/96boards/documentation/wiki/HiKeyUEFI

8 years, 4 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Dev December 2015