Linaro-android November 2013

linaro-android@lists.linaro.org

13 participants
17 discussions

Optimizing OVERLAY handling on android-build

by Paul Sokolovsky

Hello, There were increasing Android build times during last month again (going over 3.5hrs). Yesterday, I re-created the seed, but that didn't improve times match. I did more stats on builds and it turns out that we spend almost 1.5hrs in copying ever-growing overlay collection to the slaves via sluggish CopyToSlave Jenkins plugin. That's issues known for at least half-year, and was in queue for being reworked. I didn't work on android-build closely for few months, but now that I'm back on maintenance, I'd like to start with fixing this long-overdue issue. The idea was to pull all the needed overlay, straight to a slave. The complication here was handling of license protected files. ci.linaro.org had the same issue, and used a script to handle automatic downloads for some time. However, as of now, it was switched to other process and the script git bitrotted with recent linaro-license-protection codebase changes. I took a look at revamping it, but then though that it may be a good idea to use simpler and more explicit process, following closely click-thru usage. So, if you want to use a license-protected binaries in a build, you'd need to specify: ACCEPT_LICENSE=<license_id> Where <license_id> is id under which license is registered in linaro-license-protection. One good way to figure it out is to read the license page at all (well, as HTML source, the id is included in some links). Wording of variable name (as well as of commands in underlying implementation) is also explicit to point that its usage construes license acceptance. I prototypes these changes using https://android-build.linaro.org/builds/~pfalcon/panda-jb-gcc47-tilt-tracki… which is down to 2h10m build time. I'm ready to migrate all builds tomorrow, while we're early in cycle start. Please let me know if there're any issues with approach or proposed migration timeframe, otherwise let's make android-build rock again. Thanks, Paul 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, 3 months

Re: WiFi status on TI Panda 4460.

by Botao Sun

+ Linaro Android Mailing List On Fri, Nov 22, 2013 at 7:44 PM, Botao Sun <botao.sun(a)linaro.org> wrote: > Hi Vishal, > > Do you think we need a bug in Launchpad to track this issue? > > Thanks. > > > Best Regards > Botao Sun > > > On Fri, Nov 22, 2013 at 5:38 PM, Soumya Basak <soumya.basak(a)linaro.org>wrote: > >> Hi Botao, >> I have checked twice the image with panda 4460 board: >> >> http://snapshots.linaro.org/android/~linaro-android-member-ti/panda-linaro/… >> >> http://snapshots.linaro.org/android/~linaro-android-member-ti/panda-linaro/… >> >> http://snapshots.linaro.org/android/~linaro-android-member-ti/panda-linaro/… >> >> 1. basically, when eth0 cable is plugged in hw, and wifi is not turned on >> from UI, >> # busybox ifconfig -a not shown the wlan0 >> only eth0 up and accessing network. >> 2. when you turn on wifi it will ask you password, after assign password, >> wifi shown connected (but inactive), >> # busybox ifconfig -a shown the wlan0 candidate but no inet address, >> and mask. >> 3. when unplugged the eth0, wlan0 is get inet address and musk, and >> connected. >> >> on the other hand wifi is working well, there is no issue with Youtube >> playback, or enable from UI, after assign Password. >> >> so, both are not up at the same time. >> >> this stuff is observed from since Android version: 4.3 >> >> @Botao, what is your opinion ? >> >> Thank You. >> Best Regards >> Soumya Basak. >> >> >> >> >> On 21 November 2013 20:40, Botao Sun <botao.sun(a)linaro.org> wrote: >> >>> OK, with more tests, the problem is, if no Ethernet cable attached, WiFi >>> works, otherwise, it shows the error I mentioned in previous 2 emails. >>> >>> root@pandaboard:/ # busybox ifconfig -a >>> eth0 Link encap:Ethernet HWaddr 0E:60:CF:E5:49:01 >>> UP BROADCAST RUNNING MULTICAST MTU:1488 Metric:1 >>> RX packets:0 errors:0 dropped:0 overruns:0 frame:0 >>> TX packets:14 errors:0 dropped:0 overruns:0 carrier:0 >>> collisions:0 txqueuelen:1000 >>> RX bytes:0 (0.0 B) TX bytes:2510 (2.4 KiB) >>> >>> ip6tnl0 Link encap:UNSPEC HWaddr >>> 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 >>> NOARP MTU:1452 Metric:1 >>> RX packets:0 errors:0 dropped:0 overruns:0 frame:0 >>> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 >>> collisions:0 txqueuelen:0 >>> RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) >>> >>> lo Link encap:Local Loopback >>> inet addr:127.0.0.1 Mask:255.0.0.0 >>> UP LOOPBACK RUNNING MTU:16436 Metric:1 >>> RX packets:0 errors:0 dropped:0 overruns:0 frame:0 >>> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 >>> collisions:0 txqueuelen:0 >>> RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) >>> >>> sit0 Link encap:UNSPEC HWaddr >>> 00-00-00-00-0F-00-01-00-00-00-00-00-00-00-00-00 >>> NOARP MTU:1480 Metric:1 >>> RX packets:0 errors:0 dropped:0 overruns:0 frame:0 >>> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 >>> collisions:0 txqueuelen:0 >>> RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) >>> >>> wlan0 Link encap:Ethernet HWaddr 0E:20:CF:E5:49:01 >>> inet addr:10.0.0.25 Bcast:10.0.0.255 Mask:255.255.255.0 >>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >>> RX packets:96 errors:0 dropped:0 overruns:0 frame:0 >>> TX packets:105 errors:0 dropped:0 overruns:0 carrier:0 >>> collisions:0 txqueuelen:1000 >>> RX bytes:97780 (95.4 KiB) TX bytes:14813 (14.4 KiB) >>> >>> root@pandaboard:/ # >>> >>> Is it a "work-as-design" stuff or a bug? If we keep it likes this, then >>> in order to test WiFi, I have to disable Ethernet first, then restore it >>> after the test is done. >>> >>> Thanks. >>> >>> >>> Best Regards >>> Botao Sun >>> >>> >>> >>> >>> On Fri, Nov 22, 2013 at 2:02 AM, Botao Sun <botao.sun(a)linaro.org> wrote: >>> >>>> Hi Soumya, >>>> >>>> The WiFi doesn't work on 13.10 release image either: >>>> >>>> >>>> https://android-build.linaro.org/builds/~linaro-android-member-ti/panda-lin… >>>> >>>> On my TI Panda 4460 board, same behaviour observed, and following >>>> output shows: >>>> >>>> [ 148.630249] wl1271: loaded >>>> [ 149.538604] wl1271: firmware booted (Rev 6.3.0.0.77) >>>> [ 149.556671] ADDRCONF(NETDEV_UP): wlan0: link is not ready >>>> [ 250.320129] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready >>>> [ 250.383636] wl1271: Association completed. >>>> [ 251.542541] cfg80211: Calling CRDA to update world regulatory domain >>>> [ 261.064025] wl1271: Scan completed due to error. >>>> [ 261.069000] wl1271: Reading FW panic log >>>> [ 261.074127] wl1271: Hardware recovery in progress. FW ver: Rev >>>> 6.3.0.0.77 pc: 0x0 >>>> [ 261.074127] wl1271: down >>>> [ 261.086059] ieee80211 phy0: Hardware restart was requested >>>> [ 261.714691] wl1271: firmware booted (Rev 6.3.0.0.77) >>>> >>>> Would you double check it on your side? Based on the output of >>>> "ifconfig", there is no IP assigned to wlan0 interface: >>>> >>>> root@pandaboard:/ # busybox ifconfig -a >>>> eth0 Link encap:Ethernet HWaddr 0E:60:CF:E5:49:01 >>>> inet addr:10.0.0.24 Bcast:10.0.0.255 Mask:255.255.255.0 >>>> UP BROADCAST RUNNING MULTICAST MTU:1488 Metric:1 >>>> RX packets:34 errors:0 dropped:2 overruns:0 frame:0 >>>> TX packets:13 errors:0 dropped:0 overruns:0 carrier:0 >>>> collisions:0 txqueuelen:1000 >>>> RX bytes:3870 (3.7 KiB) TX bytes:1901 (1.8 KiB) >>>> >>>> ip6tnl0 Link encap:UNSPEC HWaddr >>>> 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 >>>> NOARP MTU:1452 Metric:1 >>>> RX packets:0 errors:0 dropped:0 overruns:0 frame:0 >>>> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 >>>> collisions:0 txqueuelen:0 >>>> RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) >>>> >>>> lo Link encap:Local Loopback >>>> inet addr:127.0.0.1 Mask:255.0.0.0 >>>> UP LOOPBACK RUNNING MTU:16436 Metric:1 >>>> RX packets:0 errors:0 dropped:0 overruns:0 frame:0 >>>> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 >>>> collisions:0 txqueuelen:0 >>>> RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) >>>> >>>> sit0 Link encap:UNSPEC HWaddr >>>> 00-00-00-00-0F-00-01-00-00-00-00-00-00-00-00-00 >>>> NOARP MTU:1480 Metric:1 >>>> RX packets:0 errors:0 dropped:0 overruns:0 frame:0 >>>> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 >>>> collisions:0 txqueuelen:0 >>>> RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) >>>> >>>> wlan0 Link encap:Ethernet HWaddr 0E:20:CF:E5:49:01 >>>> UP BROADCAST MULTICAST MTU:1500 Metric:1 >>>> RX packets:3 errors:0 dropped:0 overruns:0 frame:0 >>>> TX packets:3 errors:0 dropped:0 overruns:0 carrier:0 >>>> collisions:0 txqueuelen:1000 >>>> RX bytes:607 (607.0 B) TX bytes:655 (655.0 B) >>>> >>>> root@pandaboard:/ # >>>> >>>> Thanks. >>>> >>>> >>>> Best Regards >>>> Botao Sun >>>> >>>> >>>> On Fri, Nov 22, 2013 at 12:40 AM, Botao Sun <botao.sun(a)linaro.org>wrote: >>>> >>>>> Hi Soumya, >>>>> >>>>> Please take a look at WiFi status on TI Panda 4460, with Linaro >>>>> Android build 479: >>>>> >>>>> >>>>> http://snapshots.linaro.org/android/~linaro-android-member-ti/panda-linaro/… >>>>> >>>>> http://snapshots.linaro.org/android/~linaro-android-member-ti/panda-linaro/… >>>>> >>>>> http://snapshots.linaro.org/android/~linaro-android-member-ti/panda-linaro/… >>>>> >>>>> You can use "wget" to download them in your local terminal if the web >>>>> page can't be shown up. >>>>> >>>>> I ask because I just found WiFi doesn't work via GUI on my side, >>>>> following log shows in serial console: >>>>> >>>>> [ 25.692474] wl1271: loaded >>>>> [ 26.373870] smsc95xx 1-1.1:1.0: eth0: link up, 100Mbps, >>>>> full-duplex, lpa 0x45E1 >>>>> [ 27.608551] wl1271: firmware booted (Rev 6.3.0.0.77) >>>>> [ 27.629058] ADDRCONF(NETDEV_UP): wlan0: link is not ready >>>>> [ 29.750000] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready >>>>> [ 29.803771] wl1271: Association completed. >>>>> [ 29.951232] init: sys_prop: permission denied uid:1003 >>>>> name:service.bootanim.exit >>>>> [ 30.969970] cfg80211: Calling CRDA to update world regulatory domain >>>>> >>>>> The access point can be shown successfully in the list, and I can >>>>> click and enter password as well, but then above output shows, with >>>>> "Disabled" under the access point name on my screen. >>>>> >>>>> Based on our test result spreadsheet, it should at least work on 13.10 >>>>> release image. I'm going to try it soon. >>>>> >>>>> Thanks. >>>>> >>>>> >>>>> Best Regards >>>>> Botao Sun >>>>> >>>> >>>> >>> >> >

11 years, 9 months

Test Result Summary of Linaro Android 13.11 Release.

by Soumya Basak

Linaro Android 13.11 Release (Calender Week 48): Here is the test result summary for Linaro Android image on following targets: 1) TI-Panda 4460; 2) TI-Panda 4430; 3) Samsung Arndale; 4) Galaxy Nexus; 5) ARM Versatile Express A9; 6) ARM Versatile Express LSK TC2; 7) ARM Versatile Express TC2; 1. TI-Panda 4460 + Linaro Android 4.4 (Column: BK): https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AkxwyUNxNaAadGVWd… 2. TI-Panda 4430 + Linaro Android 4.4 (Column: BK): https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AkxwyUNxNaAadGVWd… 3. Samsung Arndale + Linaro Android 4.4 (Column: U): https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AuNOCeo15fRHdDFaR… 4) Galaxy Nexus + Linaro Android 4.4 (Column: O): https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AuNOCeo15fRHdFhhe… 5) ARM Versatile Express A9 + Linaro Android 4.4 (Column: BJ): https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AkxwyUNxNaAadExQd… 6) ARM Versatile Express LSK TC2 + Linaro Android 4.3.1 (Column: I): https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AkxwyUNxNaAadExQd… 7) ARM Versatile Express TC2 + Linaro Android 4.4 (Column: R): https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AkxwyUNxNaAadExQd… For consolidated Linaro Android test result spreadsheet 13.11 release, please refer to this link: https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AgB-fT5LL31CdFBSN… Thank You. Best Regards Soumya Basak.

11 years, 10 months

¨get binaries¨ failed

by R.Zhou

Hello everyone: I am new for this part. Today I tried to build Android to Pandaboard (Linaro 12.04). When I did the last step ¨Get Binaries¨, the text can be seen below. I do not know why. Could you give some advices? Best regards Ryan

11 years, 10 months

Linaro for Mako

by najmi.zabidi＠gmail.com

Hi, I am new to kernel compiling. I just compiled and boot my Nexus 4/Mako using Google Toolchain, and now I want to try Linaro. I look at the https://android-build.linaro.org/ page but can't find for Mako. Any tips? Thanks.

11 years, 10 months

Test Result Summary of Calendar Week 47, 2013, for Linaro Android Jellybean.

by Soumya Basak

Calendar Week 47 2013: Here is the test result summary for Linaro Android Jellybean image on following boards: 1) TI Panda 4430; 2) TI Panda 4460; 4) ARM Versatile Express A9; 5) Versatile Express LSK TC2; 1) TI Panda 4430 + Linaro Android Jellybean (Column: BJ) https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AkxwyUNxNaAadGVWd… 2) TI Panda 4460 + Linaro Android Jellybean (Column: BJ) https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AkxwyUNxNaAadGVWd… 3) ARM Versatile Express A9 + Linaro Android Jellybean (Column: BI) https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AkxwyUNxNaAadExQd… 4) Versatile Express LSK TC2 + Linaro Android Jellybean (Column: H) https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AkxwyUNxNaAadExQd… please refer to the test result spreadsheet. Thank You. Best Regards Soumya Basak.

11 years, 10 months

RE: Failure to boot with 13.10

by Eric Huang

Jon, I think I have solved issue. I replaced the motherboard USBMS contents with files from V5.0 VE DVD, and issue went away. Thanks Eric H ________________________________ From: Eric Huang Sent: Wednesday, November 20, 2013 1:05 PM To: 'Jon Medhurst (Tixy)'; linaro-android(a)lists.linaro.org Subject: Failure to boot with 13.10 Jon, I tried to update my Vexpress TC2 to 13.10, but bootup seems to stuck at "Running boot script from flash BOOTSCRIPT". This is the first time I tried to switch to use UEFI with zImage. I updated the firmware of my VExpress following the steps listed in the release note. Any idea what I did wrong? Cmd> Powering up system... Daughterboard fitted to site 1. Switching on ATXPSU... ATX3V3: ON VIOset: 1.8V MBtemp: 37 degC Configuring motherboard (rev D, var A)... IOFPGA config: PASSED MUXFPGA config: PASSED OSC CLK config: PASSED Programming image \SOFTWARE\TC2\zimage.bin Erasing Flash . Writing Flash Updating eeprom with image zimage Image: zimage UPDATED from \SOFTWARE\TC2\zimage.bin Programming image \SOFTWARE\TC2\dtb.bin Erasing Flash . Writing Flash Updating eeprom with image dtb Image: dtb UPDATED from \SOFTWARE\TC2\dtb.bin Programming image \SOFTWARE\TC2\initrd.bin Erasing Flash . Writing Flash Updating eeprom with image initrd Image: initrd UPDATED from \SOFTWARE\TC2\initrd.bin Testing SMC devices (FPGA build 16)... SRAM 32MB test: PASSED VRAM 8MB test: PASSED LAN9118 test: PASSED USB & OTG test: PASSED KMI1/KMI2 test: PASSED MMC & SD test: PASSED DVI image test: PASSED AACI AC97 test: PASSED CF card test: PASSED UART port test: PASSED MAC addrs test: PASSED Reading Site 1 Board File \SITE1\HBI0249A\board.txt DB1 JTAG configuration complete. Setting DB1 OSCCLKS... DB1.0 DCC 0 SPI configuration complete. Writing SCC 0x40610007 with 0xFF00FF00 Writing SCC 0x40610046 with 0x01CD1011 Writing SCC 0x406101C0 with 0x1032F003 Writing SCC 0x40610100 with 0x33330C00 Writing SCC 0x40610048 with 0x022F1010 Writing SCC 0x40610049 with 0x0011710D Writing SCC 0x4061004A with 0x022F1010 Writing SCC 0x4061004B with 0x0011710D Writing SCC 0x4061004C with 0x022F1010 Writing SCC 0x4061004D with 0x0011710D Writing SCC 0x4061004E with 0x022F1010 Writing SCC 0x4061004F with 0x0011710D Writing SCC 0x40610300 with 0x00000005 Writing SCC 0x40610301 with 0x060E0356 Writing SCC 0x40610302 with 0x00000000 Writing SCC 0x40610303 with 0x00000000 Writing SCC 0x40610304 with 0x384061A8 Writing SCC 0x40610305 with 0x38407530 Writing SCC 0x40610306 with 0x384088B8 Writing SCC 0x40610307 with 0x38409C40 Writing SCC 0x40610308 with 0x3840AFC8 Writing SCC 0x40610309 with 0x3840C350 Writing SCC 0x4061030A with 0x3CF0D6D8 Writing SCC 0x4061030B with 0x41A0EA60 Writing SCC 0x4061030C with 0x3840445C Writing SCC 0x4061030D with 0x38404E20 Writing SCC 0x4061030E with 0x384061A8 Writing SCC 0x4061030F with 0x38407530 Writing SCC 0x40610310 with 0x384088B8 Writing SCC 0x40610311 with 0x38409C40 Writing SCC 0x40610312 with 0x3CF0AFC8 Writing SCC 0x40610313 with 0x41A0C350 DB1.0 DCC 0 SCC configuration complete. DB SMB clock enabled. Waiting for SITE1 CB_READY... Testing SMB clock... Configuring MUXFPGA for MB. Setting DVI mode for VGA. Releasing Daughterboard resets. Switching MCC log to UART1. %BootMonitor-Warning, Unable to open SYSTEM.DAT ARM Versatile Express Boot Monitor Version: V5.1.9 Build Date: Dec 3 2012 Daughterboard Site 1: V2P-CA15_A7 Cortex A7 Daughterboard Site 2: Not Used Running boot script from flash - BOOTSCRIPT

11 years, 10 months

Failure to boot with 13.10

by Eric Huang

Jon, I tried to update my Vexpress TC2 to 13.10, but bootup seems to stuck at "Running boot script from flash BOOTSCRIPT". This is the first time I tried to switch to use UEFI with zImage. I updated the firmware of my VExpress following the steps listed in the release note. Any idea what I did wrong? Cmd> Powering up system... Daughterboard fitted to site 1. Switching on ATXPSU... ATX3V3: ON VIOset: 1.8V MBtemp: 37 degC Configuring motherboard (rev D, var A)... IOFPGA config: PASSED MUXFPGA config: PASSED OSC CLK config: PASSED Programming image \SOFTWARE\TC2\zimage.bin Erasing Flash . Writing Flash Updating eeprom with image zimage Image: zimage UPDATED from \SOFTWARE\TC2\zimage.bin Programming image \SOFTWARE\TC2\dtb.bin Erasing Flash . Writing Flash Updating eeprom with image dtb Image: dtb UPDATED from \SOFTWARE\TC2\dtb.bin Programming image \SOFTWARE\TC2\initrd.bin Erasing Flash . Writing Flash Updating eeprom with image initrd Image: initrd UPDATED from \SOFTWARE\TC2\initrd.bin Testing SMC devices (FPGA build 16)... SRAM 32MB test: PASSED VRAM 8MB test: PASSED LAN9118 test: PASSED USB & OTG test: PASSED KMI1/KMI2 test: PASSED MMC & SD test: PASSED DVI image test: PASSED AACI AC97 test: PASSED CF card test: PASSED UART port test: PASSED MAC addrs test: PASSED Reading Site 1 Board File \SITE1\HBI0249A\board.txt DB1 JTAG configuration complete. Setting DB1 OSCCLKS... DB1.0 DCC 0 SPI configuration complete. Writing SCC 0x40610007 with 0xFF00FF00 Writing SCC 0x40610046 with 0x01CD1011 Writing SCC 0x406101C0 with 0x1032F003 Writing SCC 0x40610100 with 0x33330C00 Writing SCC 0x40610048 with 0x022F1010 Writing SCC 0x40610049 with 0x0011710D Writing SCC 0x4061004A with 0x022F1010 Writing SCC 0x4061004B with 0x0011710D Writing SCC 0x4061004C with 0x022F1010 Writing SCC 0x4061004D with 0x0011710D Writing SCC 0x4061004E with 0x022F1010 Writing SCC 0x4061004F with 0x0011710D Writing SCC 0x40610300 with 0x00000005 Writing SCC 0x40610301 with 0x060E0356 Writing SCC 0x40610302 with 0x00000000 Writing SCC 0x40610303 with 0x00000000 Writing SCC 0x40610304 with 0x384061A8 Writing SCC 0x40610305 with 0x38407530 Writing SCC 0x40610306 with 0x384088B8 Writing SCC 0x40610307 with 0x38409C40 Writing SCC 0x40610308 with 0x3840AFC8 Writing SCC 0x40610309 with 0x3840C350 Writing SCC 0x4061030A with 0x3CF0D6D8 Writing SCC 0x4061030B with 0x41A0EA60 Writing SCC 0x4061030C with 0x3840445C Writing SCC 0x4061030D with 0x38404E20 Writing SCC 0x4061030E with 0x384061A8 Writing SCC 0x4061030F with 0x38407530 Writing SCC 0x40610310 with 0x384088B8 Writing SCC 0x40610311 with 0x38409C40 Writing SCC 0x40610312 with 0x3CF0AFC8 Writing SCC 0x40610313 with 0x41A0C350 DB1.0 DCC 0 SCC configuration complete. DB SMB clock enabled. Waiting for SITE1 CB_READY... Testing SMB clock... Configuring MUXFPGA for MB. Setting DVI mode for VGA. Releasing Daughterboard resets. Switching MCC log to UART1. %BootMonitor-Warning, Unable to open SYSTEM.DAT ARM Versatile Express Boot Monitor Version: V5.1.9 Build Date: Dec 3 2012 Daughterboard Site 1: V2P-CA15_A7 Cortex A7 Daughterboard Site 2: Not Used Running boot script from flash - BOOTSCRIPT

11 years, 10 months

what is manifest.xml used for?

by Alex Zhang

Hello, I am a newbie on linaro andrioid project. Hope this is the place where I can ask questions. When I build the android for pandaboard, I dont know which manifest.xml should be used, as I don understand the purpose of this file. Is there any place decribing this file? Also, what is overlay file used for and when should we use it in bulding the android? Thanks. -- Alex, *Dreams can come true – just believe.*

11 years, 10 months

KitKat sdcard problem, getFatVolumeId returns -1

by Jon Medhurst (Tixy)

Can anyone provide clues to help me get 'sdcard' partition working on Linaro Android KitKat images? Here's where I've got to so far... After updating the vexpress storage config for KitKat [1] the sdcard partition on Linaro Android images is getting mounted by vold, but apps can't access this because android.process.media keeps crashing in attachVolume because FileUtils.getFatVolumeId is returning -1. With MediaProvider hacked to provide verbose logging I get: V/MediaProvider( 2825): /storage/sdcard0 volume ID: -1 E/MediaProvider( 2825): Can't obtain external volume ID even though it's mounted. and I've verified the -1 comes from the call ioctl(fd, VFAT_IOCTL_GET_VOLUME_ID) in android_os_FileUtils_getFatVolumeId in frameworks/base/core/jni/android_os_FileUtils.cpp. Running 'mount' gives... rootfs / rootfs rw,relatime 0 0 tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0 devpts /dev/pts devpts rw,relatime,mode=600 0 0 proc /proc proc rw,relatime 0 0 sysfs /sys sysfs rw,relatime 0 0 tmpfs /mnt/secure tmpfs rw,relatime,mode=700 0 0 tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0 tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0 /sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0 /dev/block/sda2 /system ext4 ro,relatime,data=ordered 0 0 /dev/block/sda3 /cache ext4 rw,nosuid,nodev,noatime,errors=panic,data=ordered 0 0 /dev/block/sda5 /data ext4 rw,nosuid,nodev,noatime,errors=panic,data=ordered 0 0 nodev /dev/gator gatorfs rw,relatime 0 0 /dev/block/vold/8:6 /mnt/media_rw/sdcard0 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0 /dev/block/vold/8:6 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0 /dev/fuse /storage/sdcard0 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0 So first guess would be that fuse doesn't support this function, however as this seems to be the standard Android way of doing things, you would assume that it should work...? [1] http://review.android.git.linaro.org/#/c/4563/2 -- Tixy

11 years, 10 months

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Linaro-android November 2013