(Updated)Android-4.3 Source Git and Tarball for Wandboard

Discuss Android on the Wandboard, as well as app development for or on the Wandboard.

Re: Android-4.3 Source Code Tarball for Wandboard

Postby chopsuey5540 » Mon Feb 10, 2014 11:07 am

I am getting the following error when making the sd card:

Code: Select all
$sudo mount -t vfat /dev/sdc1 /media/imx6
mount: /dev/sdc1: can't read superblock


I think the script that formats the sd card is not doing it properly. I've posted the output of
Code: Select all
./wand_fsl_sdcard-part.sh
here if you want to have a look: http://pastie.org/private/bo7kbtphzhdbgt28ycc2q

Thanks for any help!
chopsuey5540
 
Posts: 8
Joined: Mon Feb 10, 2014 11:00 am

Re: Android-4.3 Source Code Tarball for Wandboard

Postby chopsuey5540 » Mon Feb 10, 2014 12:32 pm

No worries, it was an issue with my machine.

Now the board boots but in user space, the SurfaceFlinger service keeps dying. It has something to do the display so I'm suspecting it might not be configure to output to HDMI by default. Here is the stack trace when the service dies:

Code: Select all
D/SurfaceFlinger( 1855): Screen acquired, type=0 flinger=0x2aacc008
E/BufferQueue( 1855): [FramebufferSurface] dequeueBuffer: can't dequeue multiple buffers without setting the buffer count
F/SurfaceFlinger( 1855): eglSwapBuffers(0x1, 0x3625e658) failed with 0x0000300b
F/libc    ( 1855): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1), thread 1856 (SurfaceFlinger)
I/DEBUG   ( 1394): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG   ( 1394): Build fingerprint: 'unknown'
I/DEBUG   ( 1394): Revision: '405522'
I/DEBUG   ( 1394): pid: 1855, tid: 1856, name: SurfaceFlinger  >>> /system/bin/surfaceflinger <<<
I/DEBUG   ( 1394): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr deadbaad
I/DEBUG   ( 1394):     r0 00000027  r1 00000001  r2 00000008  r3 deadbaad
I/DEBUG   ( 1394):     r4 00000000  r5 2b05d7f4  r6 00000000  r7 3625e6c8
I/DEBUG   ( 1394):     r8 00000001  r9 0000000c  sl 2ab85989  fp 2ab85892
I/DEBUG   ( 1394):     ip 3625e6c8  sp 2b05d7f0  lr 2aca012b  pc 2ac9d684  cpsr 600f0030
I/DEBUG   ( 1394):     d0  000000000000000f  d1  3f0000003f000000
I/DEBUG   ( 1394):     d2  000000003f000000  d3  0000000000000000
I/DEBUG   ( 1394):     d4  0000000000000000  d5  0000000000000000
I/DEBUG   ( 1394):     d6  3f80000000000000  d7  3f0000003f800000
I/DEBUG   ( 1394):     d8  0000000000000000  d9  0000000000000000
I/DEBUG   ( 1394):     d10 0000000000000000  d11 0000000000000000
I/DEBUG   ( 1394):     d12 0000000000000000  d13 0000000000000000
I/DEBUG   ( 1394):     d14 0000000000000000  d15 0000000000000000
I/DEBUG   ( 1394):     d16 0000000000000000  d17 0000000000000058
I/DEBUG   ( 1394):     d18 0000000000619f50  d19 0013005500ff019a
I/DEBUG   ( 1394):     d20 00ff00ff00ff00fe  d21 0000000000000000
I/DEBUG   ( 1394):     d22 0000000000000000  d23 3f80000000000000
I/DEBUG   ( 1394):     d24 0000000000000000  d25 0000000000000000
I/DEBUG   ( 1394):     d26 40bc200000000000  d27 0000000000000000
I/DEBUG   ( 1394):     d28 0000000000000000  d29 0000000000000000
I/DEBUG   ( 1394):     d30 0000000000000000  d31 4000000000000000
I/DEBUG   ( 1394):     scr 80000010
I/DEBUG   ( 1394):
I/DEBUG   ( 1394): backtrace:
I/DEBUG   ( 1394):     #00  pc 0001e684  /system/lib/libc.so
I/DEBUG   ( 1394):     #01  pc 0001c550  /system/lib/libc.so (abort+4)
I/DEBUG   ( 1394):     #02  pc 0000892f  /system/lib/libcutils.so (__android_log_assert+86)
I/DEBUG   ( 1394):     #03  pc 0001d703  /system/lib/libsurfaceflinger.so (android::DisplayDevice::swapBuffers(android::HWComposer&) const+106)
I/DEBUG   ( 1394):     #04  pc 000233df  /system/lib/libsurfaceflinger.so (android::SurfaceFlinger::doDisplayComposition(android::sp<android::DisplayDevice const> const&, android::Region const&)+182)
I/DEBUG   ( 1394):     #05  pc 000255f9  /system/lib/libsurfaceflinger.so (android::SurfaceFlinger::doComposition()+96)
I/DEBUG   ( 1394):     #06  pc 00025855  /system/lib/libsurfaceflinger.so (android::SurfaceFlinger::handleMessageRefresh()+48)
I/DEBUG   ( 1394):     #07  pc 000262b5  /system/lib/libsurfaceflinger.so (android::SurfaceFlinger::onMessageReceived(int)+64)
I/DEBUG   ( 1394):     #08  pc 000150fd  /system/lib/libutils.so (android::Looper::pollInner(int)+384)
I/DEBUG   ( 1394):     #09  pc 000151fd  /system/lib/libutils.so (android::Looper::pollOnce(int, int*, int*, void**)+92)
I/DEBUG   ( 1394):     #10  pc 00021da9  /system/lib/libsurfaceflinger.so (android::MessageQueue::waitMessage()+36)
I/DEBUG   ( 1394):     #11  pc 00022b35  /system/lib/libsurfaceflinger.so (android::SurfaceFlinger::threadLoop()+2)
I/DEBUG   ( 1394):     #12  pc 00011a8d  /system/lib/libutils.so (android::Thread::_threadLoop(void*)+216)
I/DEBUG   ( 1394):     #13  pc 00011581  /system/lib/libutils.so
I/DEBUG   ( 1394):     #14  pc 0000ca78  /system/lib/libc.so (__thread_entry+72)
I/DEBUG   ( 1394):     #15  pc 0000cbf4  /system/lib/libc.so (pthread_create+208)
I/DEBUG   ( 1394):     #16  pc 000048a4  [heap]


In particular, I am getting an EGL_BAD_DISPLAY error which according to Freescale is returned by the function
Code: Select all
EGLDisplay eglGetDisplay(NativeDisplayTypedisplay_id);
and means that:

Code: Select all
An EGL_BAD_DISPLAY error is generated if the dpy argument does not refer to a valid EGLDisplay
chopsuey5540
 
Posts: 8
Joined: Mon Feb 10, 2014 11:00 am

Re: (Updated)Android-4.3 Source Git and Tarball for Wandboard

Postby chopsuey5540 » Fri Feb 14, 2014 3:16 pm

I managed to successfully build using the sources on git but fail to create a bootable sdcard. I've used the script that was posted on a 8GB sdcard without errors. On boot, the serial console outputs:

Code: Select all
U-Boot SPL 2013.10-06661-g35f8017 (Feb 14 2014 - 14:27:03)
Boot Device: SD0
reading boot/u-boot.img
Load image from RAW...
spl: wrong MMC boot mode
### ERROR ### Please RESET the board ###
chopsuey5540
 
Posts: 8
Joined: Mon Feb 10, 2014 11:00 am

Re: (Updated)Android-4.3 Source Git and Tarball for Wandboard

Postby marco1957 » Fri Feb 14, 2014 3:49 pm

Also me had the same problem. The file uEnv.txt it isn't correct.
you can change it as:
bootargs_base=console=ttymxc0,115200 androidboot.console=ttymxc0 androidboot.hardware=wandboard vmalloc=400M
video_mode=display0=dev=hdmi0,mode=1280x720@60,if=RGB24,bpp=32 fbmem=28M
expansion=
baseboard=wand

If you use tuture fwbadpt set expansion=fwbadapt.
I have a lot problem to work on future lcd wvga-seiko and dual display hdmi + lcd.
I can not find information on what to do.
marco1957
 
Posts: 29
Joined: Wed Dec 18, 2013 4:55 pm

Re: (Updated)Android-4.3 Source Git and Tarball for Wandboard

Postby sc.chang » Fri Feb 14, 2014 4:09 pm

I noticed when I use wand_fsl_sdcard-part.sh to create sdcard partitions.
Partition 1 with label imx was not created successful.
Try to do it manually!
sc.chang
 
Posts: 3
Joined: Fri Jan 31, 2014 11:23 am

Re: (Updated)Android-4.3 Source Git and Tarball for Wandboard

Postby chopsuey5540 » Fri Feb 14, 2014 4:28 pm

I wouldn't mind doing it myself but I looked in the formatting script and can't see what the partition table must look like. Have you investigated to see why the script wasn't working?

UPDATE: I tried unmounting before launching the script and same result, here is my partition table after the script
Code: Select all
Model: Generic USB SD Reader (scsi)
Disk /dev/sda: 7969MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number  Start   End     Size    Type      File system  Flags
 1      7809kB  78.1MB  70.3MB  primary                lba
 2      78.1MB  180MB   102MB   primary   ext4
 3      180MB   1320MB  1140MB  extended
 5      180MB   718MB   539MB   logical   ext4
 6      718MB   1257MB  539MB   logical   ext4
 7      1257MB  1273MB  15.6MB  logical   ext4
 8      1273MB  1288MB  15.6MB  logical
 4      1320MB  7918MB  6599MB  primary   ext4
Last edited by chopsuey5540 on Fri Feb 14, 2014 4:47 pm, edited 1 time in total.
chopsuey5540
 
Posts: 8
Joined: Mon Feb 10, 2014 11:00 am

Re: (Updated)Android-4.3 Source Git and Tarball for Wandboard

Postby marco1957 » Fri Feb 14, 2014 4:33 pm

the sd must be umounted. Before the script you can umount /dev/sdX*
marco1957
 
Posts: 29
Joined: Wed Dec 18, 2013 4:55 pm

Re: (Updated)Android-4.3 Source Git and Tarball for Wandboard

Postby sc.chang » Fri Feb 14, 2014 6:50 pm

Make sure part type of partition 1 is FAT32. then
>> mkfs.msdos -F 32 /dev/sdX -n imx6
Reinsert your sdcard.
>> mkdir -p /media/imx6/boot
>> cp android-4.3/kernel_imx/arch/arm/boot/uImage /media/imx6/boot/
>> cp android-4.3/bootable/bootloader/uboot-imx/u-boot.img /media/imx6/boot/
>> cp android-4.3/bootable/bootloader/uboot-imx/out.bmp.gz /media/imx6/boot/
>> cp android-4.3/bootable/bootloader/uboot-imx/uEnv.txt /media/imx6/boot/
Go to wandboard, power up again.

The bad news is even you u-boot successful, you may still die in android init().
That's may case.
sc.chang
 
Posts: 3
Joined: Fri Jan 31, 2014 11:23 am

Re: (Updated)Android-4.3 Source Git and Tarball for Wandboard

Postby chopsuey5540 » Mon Feb 17, 2014 8:52 am

I managed to boot thanks to your instructions but I die before I get the android prompt as you said, here are the tail of the kernel logs:

Code: Select all
[    3.593053] mmc0: new high speed SDHC card at address 0007
[    3.599126] mmcblk0: mmc0:0007 SD08G 7.42 GiB
[    3.632208]  mmcblk0: p1 p2 p3 < p5 p6 p7 p8 > p4
[    4.000339] mmc1: queuing unknown CIS tuple 0x80 (50 bytes)
[    4.116243] mmc1: queuing unknown CIS tuple 0x80 (7 bytes)
[    4.148233] mmc1: queuing unknown CIS tuple 0x80 (4 bytes)
[    4.532900] mmc1: queuing unknown CIS tuple 0x02 (1 bytes)
[    4.574089] mmc1: new SDIO card at address 0001
[    8.302450] ehci_fsl_bus_suspend begins, Host 1
[    8.307246] ehci_fsl_bus_suspend ends, Host 1
chopsuey5540
 
Posts: 8
Joined: Mon Feb 10, 2014 11:00 am

Re: (Updated)Android-4.3 Source Git and Tarball for Wandboard

Postby torsti76 » Sat Mar 01, 2014 12:14 pm

Hi,

it took me a while to figure this out, but to be able to install paid apps from the Playstore, several additional kernel options have to be enabled, before compilation.

In particular:
Code: Select all
CONFIG_AUDIT=y
CONFIG_MD=y
CONFIG_BLK_DEV_DM=y
CONFIG_DM_CRYPT=y
CONFIG_DM_UEVENT=y
CONFIG_CRYPTO_TWOFISH=y

Afterwards, all apps install just fine.

Also, to be able to use the SDCard on the base board, (at least for WBQUAD) the first line in device/fsl/wandboard/fstab.wandboard has to be changed to read:

Code: Select all
/devices/platform/sdhci-esdhc-imx.0/mmc_host/mmc2 /mnt/extsd vfat defaults voldmanaged=sdcard:auto

Best,
Torsten
torsti76
 
Posts: 2
Joined: Sat Mar 01, 2014 12:06 pm

PreviousNext

Return to Software - Android

Who is online

Users browsing this forum: No registered users and 13 guests