Android source build...What next?

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

Android source build...What next?

Postby khiremandar » Tue Sep 30, 2014 6:17 am

Hi,
I am java programmer but want to learn how Android OS works in different Hardwares.
I use 64bit Ubuntu 14.04.
I follow http://git.wandboard.org/git/?p=about for learn how to Build & Deploy Android-4.3.
After make command I thought as i got one image (same as by http://www.wandboard.org/images/downloads/android-4.4.2-wandboard-20140815.zip
this link i got img file & which i deployed it successfully on sd card in first attemt before using Source code, i run first Hello World App also) but i was wrong.
By make command in out folder there are 4 img files generated along with lots of files & folders named as
1. boot.img
2. ramdisk.img
3. ramdisk-recovery.img
4.recovery.img
5.system.img
Then i follow http://www.cnx-software.com/2013/07/25/wandboard-quad-unboxing-getting-started-with-android-and-linux-via-the-yocto-project/
Which shows instructions
chmod 6755 ~/wandboard/myandroid/out/target/product/wandboard/system/xbin/su
sudo umount /dev/sdX*
sudo dd if=~/wandboard/myandroid/out/target/product/wandboard/u-boot-6quad.bin of=/dev/sdX bs=1K seek=1 skip=1
sudo dd if=~/wandboard/myandroid/out/target/product/wandboard/boot.img of=/dev/sdX1
sudo dd if=~/wandboard/myandroid/out/target/product/wandboard/recover.img of=/dev/sdX2
sudo mount -t ext4 /dev/sdX5 /mnt
sudo cp -a ~/wandboard/myandroid/out/target/product/wandboard/system/* /mnt/
sudo unzip ~/wandboard/gapps-jb-20130301-signed.zip -d /tmp/
sudo cp -a /tmp/system/* /mnt/
sudo sync
sudo umount /dev/sdX

No errors but no success.
Can anybody give me hint/help etc which use for learning how to deploy Android 4.3 after completion of build?
How can i make one img file as i got from Download section?
khiremandar
 
Posts: 86
Joined: Wed Sep 03, 2014 11:38 am

Re: Android source build...What next?

Postby Richard » Tue Sep 30, 2014 9:49 am

Hello, khiremandar:

There is a "REAME" file under /wandboard-4.3-pre-source
Please follow the installation in README file.

Installation,
$ sudo dd if=/dev/zero of=/dev/sdX bs=1M count=1
$ sudo ./wand_fsl_sdcard-part.sh /dev/sdX
$ dd if=wand-4.3/bootable/bootloader/uboot-imx/SPL of=/dev/sdX bs=1K seek=1
$ sudo mount -t vfat /dev/sdX1 /media/imx6
$ sudo mount -t ext4 /dev/sdX5 /media/system
$ mkdir -p /media/imx6/boot
$ cp wand-4.3/kernel_imx/arch/arm/boot/uImage /media/imx6/boot/
$ cp wand-4.3/bootable/bootloader/uboot-imx/u-boot.img /media/imx6/boot/
$ cp wand-4.3/bootable/bootloader/uboot-imx/out.bmp.gz /media/imx6/boot/
$ cp wand-4.3/bootable/bootloader/uboot-imx/uEnv.txt /media/imx6/boot/
$ mkimage -A arm -O linux -T ramdisk -C none -a 0x10800800 -n "Android Root Filesystem" -d wand-4.3/out/target/product/wandboard/ramdisk.img /media/imx6/boot/uramdisk.img

(If you don't build android source with 'su' permission, please use "dd" command to install /system partition instead of "cp")
$ sudo cp -a wand-4.3/out/target/product/wandboard/system/* /media/system/
or
$ sudo dd if=wand-4.3/out/target/product/wandboard/system.img of=/dev/sdX5 && sudo sync

$ sudo umount /dev/sdX*
Richard
Site Admin
 
Posts: 137
Joined: Tue Dec 17, 2013 6:57 am

Re: Android source build...What next?

Postby khiremandar » Tue Sep 30, 2014 11:46 am

Thanks Richard,
Two points i notice after reading & using your reply as follows:-

1. by http://git.wandboard.org/git/ i follow steps for download source code
$ cd ~
$ mkdir -p wandboard/myandroid
$ cd wandboard/myandroid
$ curl http://commondatastorage.googleapis.com ... loads/repo > ./repo
$ chmod a+x ./repo
$ ./repo init -u https://android.googlesource.com/platform/manifest -b android-4.3_r2.1
$ curl http://git.wandboard.org/git/manifest.g ... _wandboard > .repo/manifest.xml
$ ./repo sync -j4
Build Android
$ cd ~/wandboard/myandroid
$ source build/envsetup.sh
$ lunch wandboard-userdebug
$ make

in downloaded source folders there is nothing like
There is a "REAME" file under /wandboard-4.3-pre-source


2. as given instructions
$ sudo ./wand_fsl_sdcard-part.sh /dev/sdb

i found fsl-sdcard-partition.sh in /device/fsl/common/tools
if i use this script i cant use next given command by you.
sudo mount -t vfat /dev/sdX1 /media/imx6


is some thing more missing by me?
khiremandar
 
Posts: 86
Joined: Wed Sep 03, 2014 11:38 am

Re: Android source build...What next?

Postby omid » Tue Sep 30, 2014 6:14 pm

Hi khiremandar,
I suggest you to Download Android4.3 or 4.4 source code from wandboard.org download page and there is a README files follow the steps there and you won't have any problem

Download the source code : wget http://www.wandboard.org/images/downloa ... 625.tar.xz
And after compile
Do the following steps :


sudo dd if=/dev/zero of=/dev/sdX bs=1M count=1
sudo ./wand_fsl_sdcard-part.sh /dev/sdX
dd if=wand-4.3/bootable/bootloader/uboot-imx/SPL of=/dev/sdX bs=1K seek=1
sudo mount -t vfat /dev/sdX1 /media/imx6
sudo mount -t ext4 /dev/sdX5 /media/system
mkdir -p /media/imx6/boot ( first do this and then go to above command )
cp wand-4.3/kernel_imx/arch/arm/boot/uImage /media/imx6/boot/
cp wand-4.3/bootable/bootloader/uboot-imx/u-boot.img /media/imx6/boot/
cp wand-4.3/bootable/bootloader/uboot-imx/out.bmp.gz /media/imx6/boot/
cp wand-4.3/bootable/bootloader/uboot-imx/uEnv.txt /media/imx6/boot/
mkimage -A arm -O linux -T ramdisk -C none -a 0x10800800 -n "Android Root Filesystem" -d wand-4.3/out/target/product/wandboard/ramdisk.img /media/imx6/boot/uramdisk.img
sudo cp -a wand-4.3/out/target/product/wandboard/system/* /media/system/ If you have problem after you put SD card into your board with booting then do the same thing but use dd command to copy system files into SD card
sudo umount /dev/sdX*


Best regards
omid
 
Posts: 19
Joined: Fri Sep 12, 2014 5:13 pm

Re: Android source build...What next?

Postby khiremandar » Wed Oct 01, 2014 9:27 am

Thanks omid,
i downloaded Android4.3 by http://www.wandboard.org/images/downloads/wandboard_android-4.3_fullsource_20140625.tar.xz
When i follow step
lunch wandboard-userdebug

i got message
No such file: wandboard-userdebug


What should i do? This message never appear when i build previously downloaded source.
khiremandar
 
Posts: 86
Joined: Wed Sep 03, 2014 11:38 am

Re: Android source build...What next?

Postby omid » Wed Oct 01, 2014 7:55 pm

Hi , I am not expert in Android :D But i have not had this problem before ,
I suggest you to Download one more time or Download 4.4 version It is ok for me, After I downloaded I followed the steps wandboard-userdebug should be in source code ( make sure you are in the right directory wand4-3...) maybe you need to Download it one more time maybe some files did not download properly .
Another things that I can tell is make sure to download all these packages before compilation other wise you will get lots of errors

$ sudo apt-get install git gnupg flex bison gperf build-essential \
zip curl libc6-dev libncurses5-dev:i386 x11proto-core-dev \
libx11-dev:i386 libreadline6-dev:i386 libgl1-mesa-glx:i386 \
libgl1-mesa-dev g++-multilib mingw32 tofrodos \
python-markdown libxml2-utils xsltproc zlib1g-dev:i386
$ sudo ln -s /usr/lib/i386-linux-gnu/mesa/libGL.so.1 /usr/lib/i386-linux-gnu/libGL.so

make sure to install openJDK also
omid
 
Posts: 19
Joined: Fri Sep 12, 2014 5:13 pm

Re: Android source build...What next?

Postby khiremandar » Mon Oct 06, 2014 9:22 am

Thanks omid,
I done successfully as per readme file in Android 4.3.
I use following steps for installation(i change sdX to sdb as per my pc shows sd card as sdb)
sudo dd if=/dev/zero of=/dev/sdb bs=1M count=1
sudo ./wand_fsl_sdcard-part.sh /dev/sdb
dd if=wand-4.3/bootable/bootloader/uboot-imx/SPL of=/dev/sdb bs=1K seek=1
sudo mount -t vfat /dev/sdb1 /media/androiddev/imx6
sudo mount -t ext4 /dev/sdb5 /media/androiddev/system
mkdir -p /media/androiddev/imx6/boot
cp wand-4.3/kernel_imx/arch/arm/boot/uImage /media/androiddev/imx6/boot/
cp wand-4.3/bootable/bootloader/uboot-imx/u-boot.img /media/androiddev/imx6/boot/
cp wand-4.3/bootable/bootloader/uboot-imx/out.bmp.gz /media/androiddev/imx6/boot/
cp wand-4.3/bootable/bootloader/uboot-imx/uEnv.txt /media/androiddev/imx6/boot/
mkimage -A arm -O linux -T ramdisk -C none -a 0x10800800 -n "Android Root Filesystem" -d wand-4.3/out/target/product/wandboard/ramdisk.img /media/androiddev/imx6/boot/uramdisk.img
sudo cp -a wand-4.3/out/target/product/wandboard/system/* /media/androiddev/system/
sudo umount /dev/sdb*

No error in console. But when i put SD card in wandboard, it shows only wandboard image in screen. I attached HDMI screen.
Why not it boot i dont understand!
When i use only image file from http://www.wandboard.org/images/downloads/android-4.4.2-wandboard-20140815.zip
then after successful running Android i check SD card by gparted & it shows partitioning as follows
Image

but when i make & install android 4.3 source code which i got from tar file, i cant even boot?
Is anything i forgot to do? Is readme installation instructions are complete?
khiremandar
 
Posts: 86
Joined: Wed Sep 03, 2014 11:38 am

Re: Android source build...What next?

Postby khiremandar » Mon Oct 06, 2014 10:07 am

After using installation steps given in readme, i can see sd card in gparted as follows:-
Image

when i see sd card in disk utility
i can see it as follows:-
Image
Image
Image
Image
Image
Image
Image
Image
Image

i will upload successful Android 4.4 sd card's images which i can see in disk utility if required.
khiremandar
 
Posts: 86
Joined: Wed Sep 03, 2014 11:38 am

Re: Android source build...What next?

Postby khiremandar » Tue Oct 07, 2014 1:15 pm

I try to run wandboard after freshly build & installation process as per given in Readme file inside the source tar file.
few things i observe when i follow installation steps:-
1. after first step which is
Code: Select all
sudo dd if=/dev/zero of=/dev/sdx bs=1M count=1
, if i not remove SD card reader from comuter & reattach it, i cant use step 4th
which is
Code: Select all
sudo mount -t vfat /dev/sdx1 /media/imx6

I didnt understand.
2. when i want to use
Code: Select all
sudo cp -a wand-4.3/out/target/product/wandboard/system/* /media/system/
i found this 'system' partition is read only.
When i check out folder which generated by make command it also read only, so i think it make read only partition.
So i change its permissions as 777 by chmod command, then freshly follow installation steps from start again after making sd card blank unallocated.
3. when i complete installation process, i attach serial communicator with pc & wandboard so i can get output in console.
in console i got as follows:-
Code: Select all
ram_console: uncorrectable error in header
ram_console: no valid data in buffer (sig = 0xf7ffffef)

is this thing giving trouble?
here i post whole console output which i get when i can see only wandboard logo for 1 sec & then nothing.
Code: Select all
U-Boot SPL 2013.10-06663-g46edfb3-dirty (Aug 14 2014 - 17:24:47)
Boot Device: SD0                       
reading boot/u-boot.img                 
reading boot/u-boot.img                 
                                       
                                       
U-Boot 2013.10-06663-g46edfb3-dirty (Aug 14 2014 - 17:24:47)
                                       
CPU:   Freescale i.MX6Q rev1.2 at 792 MHz
Reset cause: POR
Board: Wandboard
DRAM:  2 GiB
MMC:   FSL_SDHC: 0, FSL_SDHC: 1
*** Warning - bad CRC, using default environment

splash_screen_prepare
reading boot/out.bmp.gz
splash:loading boot/out.bmp.gz from MMC FAT...
In:    serial
Out:   serial
Err:   serial
Net:   FEC
Hit any key to stop autoboot:  0
mmc0 is current device
reading boot/uEnv.txt
212 bytes read in 11 ms (18.6 KiB/s)
Loaded environment from boot/uEnv.txt
Importing environment...
reading boot/uramdisk.img
237804 bytes read in 29 ms (7.8 MiB/s)
reading boot/uImage
2921028 bytes read in 165 ms (16.9 MiB/s)
## Booting kernel from Legacy Image at 10800000 ...
   Image Name:   Linux-3.0.35
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2920964 Bytes = 2.8 MiB
   Load Address: 10008000
   Entry Point:  10008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 13000000 ...
   Image Name:   Android Root Filesystem
   Image Type:   ARM Linux RAMDisk Image (uncompressed)
   Data Size:    237740 Bytes = 232.2 KiB
   Load Address: 10800800
   Entry Point:  10800800
   Verifying Checksum ... OK
   Loading Kernel Image ... OK

Starting kernel ...

 Linux version 3.0.35 (root@DTP233) (gcc version 4.6.x-google 20120106 (prerelease) (GCC) ) #1 SMP PREEMPT Wed Oct 1 15:34
 CPU: ARMv7 Processor  revision 10 (ARMv7), cr=10c53c7d
 CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache
 Machine: Freescale i.MX 6Quad/DualLite/Solo Wandboard
 EDWARD :  ram console init at phys 0x7ff00000
 EDWARD : GPU_Reserved Memory equals to 184549376
 EDWARD :  gpumem init at phys 0x74f00000
 Memory policy: ECC disabled, Data cache writealloc
 CPU identified as i.MX6Q, silicon rev 1.2
 PERCPU: Embedded 7 pages/cpu @81983000 s5696 r8192 d14784 u32768
 Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 470784
 Kernel command line: console=ttymxc0,115200 androidboot.console=ttymxc0 androidboot.hardware=wandboard vmalloc=400M dispd
 PID hash table entries: 4096 (order: 2, 16384 bytes)
 Dentry cache hash table entries: 262144 (order: 8, 1048576 bytes)
 Inode-cache hash table entries: 131072 (order: 7, 524288 bytes)
 Memory: 1615MB 240MB = 1855MB total
 Memory: 1871476k/1871476k available, 225676k reserved, 441344K highmem
 Virtual kernel memory layout:
     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
     fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
     DMA     : 0xfbe00000 - 0xffe00000   (  64 MB)
     vmalloc : 0xd9800000 - 0xf2000000   ( 392 MB)
     lowmem  : 0x80000000 - 0xd9000000   (1424 MB)
     pkmap   : 0x7fe00000 - 0x80000000   (   2 MB)
     modules : 0x7f000000 - 0x7fe00000   (  14 MB)
       .init : 0x80008000 - 0x80041000   ( 228 kB)
       .text : 0x80041000 - 0x80793000   (7496 kB)
       .data : 0x80794000 - 0x807ec900   ( 355 kB)
        .bss : 0x807ec924 - 0x80973e48   (1566 kB)
 SLUB: Genslabs=13, HWalign=32, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
 Preemptible hierarchical RCU implementation.
 NR_IRQS:624
 MXC GPIO hardware
 sched_clock: 32 bits at 3000kHz, resolution 333ns, wraps every 1431655ms
 arm_max_freq=1GHz
 MXC_Early serial console at MMIO 0x2020000 (options '115200')
 bootconsole  enabled
 Console: colour dummy device 80x30
Calibrating delay loop... 1581.05 BogoMIPS (lpj=7905280)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
CPU1: Booted secondary processor
CPU2: Booted secondary processor
CPU3: Booted secondary processor
Brought up 4 CPUs
SMP: Total of 4 processors activated (6324.22 BogoMIPS).
print_constraints: dummy:
NET: Registered protocol family 16
print_constraints: vddpu: 725 <--> 1300 mV at 1150 mV fast normal
print_constraints: vddcore: 725 <--> 1300 mV at 1150 mV fast normal
print_constraints: vddsoc: 725 <--> 1300 mV at 1200 mV fast normal
print_constraints: vdd2p5: 2000 <--> 2775 mV at 2400 mV fast normal
print_constraints: vdd1p1: 800 <--> 1400 mV at 1100 mV fast normal
print_constraints: vdd3p0: 2625 <--> 3400 mV at 3000 mV fast normal
ram_console: got buffer at 7ff00000, size 100000
ram_console: uncorrectable error in header
ram_console: no valid data in buffer (sig = 0xf7ffffef)
console  enabled
mx6_display : list of transmitter settings:
mx6_display : hdmi : ipu0, di0
EDWARD: btwifi_pwr GPIO_5_31 is gpio159
EDWARD: wl_rst_n GPIO_6_0 is gpio160
EDWARD: wl_reg_on GPIO_1_26 is gpio26
L310 cache controller enabled
l2x0: 16 ways, CACHE_ID 0x410000c7, AUX_CTRL 0x32070000, Cache size: 1048576 B
bio: create slab <bio-0> at 0
mxs-dma mxs-dma-apbh: initialized
print_constraints: VDDA: 2500 mV
print_constraints: VDDIO: 3300 mV
vgaarb: loaded
SCSI subsystem initialized
libata version 3.00 loaded.
spi_imx imx6q-ecspi.0: probed
spi_imx imx6q-ecspi.1: probed
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
Freescale USB OTG Driver loaded, $Revision: 1.55 $
imx-ipuv3 imx-ipuv3.0: IPU DMFC NORMAL mode: 1(0~1), 5B(4,5), 5F(6,7)
imx-ipuv3 imx-ipuv3.1: IPU DMFC NORMAL mode: 1(0~1), 5B(4,5), 5F(6,7)
Advanced Linux Sound Architecture Driver Version 1.0.24.
Bluetooth: Core ver 2.16
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: L2CAP socket layer initialized
Bluetooth: SCO socket layer initialized
cfg80211: Calling CRDA to update world regulatory domain
Switching to clocksource mxc_timer1
NET: Registered protocol family 2
IP route cache hash table entries: 65536 (order: 6, 262144 bytes)
TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
TCP bind hash table entries: 65536 (order: 7, 786432 bytes)
TCP: Hash tables configured (established 262144 bind 65536)
TCP reno registered
UDP hash table entries: 1024 (order: 3, 32768 bytes)
UDP-Lite hash table entries: 1024 (order: 3, 32768 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
PCI: CLS 0 bytes, default 32
Unpacking initramfs...
Freeing initrd memory: 232K
_regulator_get: etb supply vcore not found, using dummy regulator
_regulator_get: etm.0 supply vcore not found, using dummy regulator
_regulator_get: etm.1 supply vcore not found, using dummy regulator
_regulator_get: etm.2 supply vcore not found, using dummy regulator
_regulator_get: etm.3 supply vcore not found, using dummy regulator
Static Power Management for Freescale i.MX6
 wait mode is disabled for i.MX6
cpaddr = d9880000 suspend_iram_base=d9914000
PM driver module loaded
iMX6 PCIe PCIe RC mode imx_pcie_pltfm_probe entering.
PCIE: imx_pcie_pltfm_probe start link up.
link up failed, DB_R0:0x0069d500, DB_R1:0x08200000!
IMX PCIe port: link down with power supply 1!
IMX usb wakeup probe
the wakeup pdata is 0xd622e3c0
add wake up source irq 75
IMX usb wakeup probe
the wakeup pdata is 0xd622eac0
rfkill: BT RF going to : on
edm_cf_imx6_bt_on
mxc_bt_rfkill driver success loaded
cpu regulator mode:ldo_enable
i.MXC CPU frequency driver
highmem bounce pool size: 64 pages
ashmem: initialized
NTFS driver 2.1.30 .
fuse init (API version 7.16)
msgmni has been set to 2793
NET: Registered protocol family 38
cryptodev: driver loaded.
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
mxc_sdc_fb mxc_sdc_fb.0: register mxc display driver hdmi
mxc_hdmi mxc_hdmi: Detected HDMI controller 0x13:0xa:0xa0:0xc1
imx-ipuv3 imx-ipuv3.0: IPU DMFC DP HIGH RESOLUTION: 1(0,1), 5B(2~5), 5F(6,7)
imx-sdma imx-sdma: loaded firmware 1.1
imx-sdma imx-sdma: initialized
Serial: IMX driver
imx-uart.0: ttymxc0 at MMIO 0x2020000 (irq = 58) is a IMX
console  enabled, bootconsole disabled
console  enabled, bootconsole disabled
imx-uart.1: ttymxc1 at MMIO 0x21e8000 (irq = 59) is a IMX
imx-uart.2: ttymxc2 at MMIO 0x21ec000 (irq = 60) is a IMX
ion: failed to create debug files.
loop: module loaded
Wait for CR ACK error!
No sata disk.
vcan: Virtual CAN interface driver
CAN device driver interface
flexcan netdevice driver
FEC Ethernet Driver
fec_enet_mii_bus: probed
PPP generic driver version 2.4.2
PPP Deflate Compression module registered
PPP BSD Compression module registered
PPP MPPE Compression module registered
NET: Registered protocol family 24
PPTP driver version 0.8.5
 usbcore: registered new interface driver asix
 usbcore: registered new interface driver cdc_ether
 usbcore: registered new interface driver smsc75xx
 usbcore: registered new interface driver smsc95xx
 usbcore: registered new interface driver MOSCHIP usb-ethernet driver
 ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
 fsl-ehci fsl-ehci.0: Freescale On-Chip EHCI Host Controller
 fsl-ehci fsl-ehci.0: new USB bus registered, assigned bus number 1
 fsl-ehci fsl-ehci.0: irq 75, io base 0x02184000
 fsl-ehci fsl-ehci.0: USB 2.0 started, EHCI 1.00
 hub 1-0:1.0: USB hub found
 hub 1-0:1.0: 1 port detected
 add wake up source irq 72
 fsl-ehci fsl-ehci.1: Freescale On-Chip EHCI Host Controller
 fsl-ehci fsl-ehci.1: new USB bus registered, assigned bus number 2
 fsl-ehci fsl-ehci.1: irq 72, io base 0x02184200
 fsl-ehci fsl-ehci.1: USB 2.0 started, EHCI 1.00
 hub 2-0:1.0: USB hub found
 hub 2-0:1.0: 1 port detected
 Initializing USB Mass Storage driver...
 usbcore: registered new interface driver usb-storage
 USB Mass Storage support registered.
 usbcore: registered new interface driver usbserial
 usbserial: USB Serial Driver core
 USB Serial support registered for cp210x
 usbcore: registered new interface driver cp210x
 cp210x: v0.09:Silicon Labs CP210x RS232 serial adaptor driver
 USB Serial support registered for FTDI USB Serial Device
 usbcore: registered new interface driver ftdi_sio
 ftdi_sio: v1.6.0:USB FTDI Serial Converters Driver
 USB Serial support registered for GSM modem (1-port)
 usbcore: registered new interface driver option
 option: v0.7.2:USB Driver for GSM modems
 USB Serial support registered for pl2303
 usbcore: registered new interface driver pl2303
 pl2303: Prolific PL2303 USB to serial adaptor driver
 USB Serial support registered for Qualcomm USB modem
 usbcore: registered new interface driver qcserial
 ARC USBOTG Device Controller driver (1 August 2005)
 android_usb gadget: Mass Storage Function, version: 2009/09/11
 android_usb gadget: Number of LUNs=1
  lun0: LUN: removable file: (no medium)
 Gadget Android: controller 'fsl-usb2-udc' not recognized
 android_usb gadget: android_usb ready
 Suspend udc for OTG auto detect
 USB Host suspend begins
 will suspend roothub and its children
 ehci_fsl_bus_suspend begins, DR
 ehci_fsl_bus_suspend ends, DR
 host suspend ends
 USB Gadget resume begins
 fsl_udc_resume, Wait for wakeup thread finishes
 dr_controller_run: udc out low power mode
 USB Gadget resume ends
 fsl-usb2-udc: bind to driver android_usb
 mousedev: PS/2 mouse device common for all mice
 i2c-core: driver  using legacy suspend method
 i2c-core: driver  using legacy resume method
 i2c /dev entries driver
 Linux video capture interface: v2.00
 mxc_v4l2_output mxc_v4l2_output.0: V4L2 device registered as video16
 mxc_v4l2_output mxc_v4l2_output.0: V4L2 device registered as video17
 usbcore: registered new interface driver uvcvideo
 USB Video Class driver (v1.1.0)
 i2c-core: driver  using legacy suspend method
 i2c-core: driver  using legacy resume method
 imx2-wdt imx2-wdt.0: IMX2+ Watchdog Timer enabled. timeout=60s (nowayout=1)
 Bluetooth: Virtual HCI driver ver 1.3
 Bluetooth: HCI UART driver ver 2.2
 Bluetooth: HCI H4 protocol initialized
 Bluetooth: Generic Bluetooth USB driver ver 0.6
 usbcore: registered new interface driver btusb
 cpuidle: using governor ladder
 cpuidle: using governor menu
 sdhci: Secure Digital Host Controller Interface driver
 sdhci: Copyright(c) Pierre Ossman
 usb 2-1: new low speed USB device number 2 using fsl-ehci
 sdhci sdhci-esdhc-imx.2: no write-protect pin available!
 _regulator_get: sdhci-esdhc-imx.2 supply vmmc not found, using dummy regulator
 mmc0: SDHCI controller on platform  using DMA
 _regulator_get: sdhci-esdhc-imx.1 supply vmmc not found, using dummy regulator
 mmc1: SDHCI controller on platform  using DMA
 sdhci sdhci-esdhc-imx.0: no write-protect pin available!
 _regulator_get: sdhci-esdhc-imx.0 supply vmmc not found, using dummy regulator
 mmc2: SDHCI controller on platform  using DMA
 mxc_vdoa mxc_vdoa: i.MX Video Data Order Adapter(VDOA) driver probed
 VPU initialized
 mxc_asrc registered
 Galcore version 4.6.9.9754
 revserved_memory_account:viv_gpu registerd
 Thermal calibration data is 0x58e4ff69
 Thermal sensor with ratio = 184
 Anatop Thermal registered as thermal_zone0
 anatop_thermal_probe: default cooling device is cpufreq!
 usbcore: registered new interface driver usbhid
 usbhid: USB HID core driver
 logger: created 256K log 'log_main'
 logger: created 256K log 'log_events'
 logger: created 256K log 'log_radio'
 logger: created 256K log 'log_system'
 zram: num_devices not specified. Using default: 1
 zram: Creating 1 devices ...
 usbcore: registered new interface driver snd-usb-audio
 mxc_hdmi_soc mxc_hdmi_soc.0: MXC HDMI Audio
 mxc_spdif mxc_spdif.0: MXC SPDIF Audio
 _regulator_get: 1-000a supply VDDD not found, using dummy regulator
 sgtl5000 1-000a: sgtl5000 revision 17
 print_constraints: 1-000a: 850 <--> 1600 mV at 1200 mV normal
 mmc0: host does not support reading read-only switch. assuming write-enable.
 mmc0: new high speed SDHC card at address aaaa
 mmcblk0: mmc0:aaaa SS16G 14.8 GiB
 asoc: sgtl5000 <-> imx-ssi.1 mapping ok
 asoc: mxc-spdif <-> imx-spdif-dai.0 mapping ok
  mmcblk0: p1 p2 p3 < p5 p6 p7 p8 > p4
 mmcblk0: p4 size 28641280 extends beyond EOD, truncated
 asoc: mxc-hdmi-soc <-> imx-hdmi-soc-dai.0 mapping ok
 ALSA device list:
   #0: sgtl5000-audio
   #1: imx-spdif
   #2: imx-hdmi-soc
 GACT probability NOT on
 Mirror/redirect action on
 u32 classifier
     Actions configured
Netfilter messages via NETLINK v0.30.
nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
ctnetlink v0.93: registering with nfnetlink.
NF_TPROXY: Transparent proxy support initialized, version 4.1.0
NF_TPROXY: Copyright (c) 2006-2007 BalaBit IT Ltd.
xt_time: kernel timezone is -0000
IPv4 over IPv4 tunneling driver
GRE over IPv4 demultiplexor driver
ip_tables: (C) 2000-2006 Netfilter Core Team
arp_tables: (C) 2002 David S. Miller
TCP cubic registered
NET: Registered protocol family 10
Mobile IPv6
ip6_tables: (C) 2000-2006 Netfilter Core Team
IPv6 over IPv4 tunneling driver
mmc1: queuing unknown CIS tuple 0x80 (2 bytes)
NET: Registered protocol family 17
NET: Registered protocol family 15
can: controller area network core (rev 20090105 abi 8)
NET: Registered protocol family 29
can: raw protocol (rev 20090105)
can: broadcast manager protocol (rev 20090105 t)
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM ver 1.11
Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Bluetooth: BNEP filters: protocol multicast
Bluetooth: HIDP (Human Interface Emulation) ver 1.2
L2TP core driver, V2.0
PPPoL2TP kernel driver, V2.0
L2TP IP encapsulation support (L2TPv3)
L2TP netlink interface
L2TP ethernet pseudowire support (L2TPv3)
lib80211: common routines for IEEE802.11 drivers
lib80211_crypt: registered algorithm 'NULL'
Registering the dns_resolver key type
VFP support v0.3:
USB Gadget resume begins
fsl_udc_resume, Wait for wakeup thread finishes
implementor 41 architecture 3 part 30 variant 9 rev 4
ThumbEE CPU extension supported.
mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
Bus freq driver module loaded
Bus freq driver Enabled
mxc_dvfs_core_probe
DVFS driver module loaded
mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
Freeing init memory: 228K
init: cannot find '/system/bin/dbus-daemon', disabling 'dbus'
init: cannot find '/system/etc/install-recovery.sh', disabling 'flash_recovery'
init: cannot find '/system/bin/ingsvcd', disabling 'ing'
android_usb: already disabled
mtp_bind_config
adb_bind_config
adb_open
mmc1: new high speed SDIO card at address 0001
root@android:/ #  mmc0: Timeout waiting for hardware interrupt.
sdhci: =========== REGISTER DUMP (mmc0)===========
sdhci: Sys addr: 0x66e80000 | Version:  0x00000002
sdhci: Blk size: 0x00000200 | Blk cnt:  0x00000000
sdhci: Argument: 0x00000000 | Trn mode: 0x00000000
sdhci: Present:  0xfffd8088 | Host ctl: 0x00000003
sdhci: Power:    0x0000000d | Blk gap:  0x00000000
sdhci: Wake-up:  0x00000000 | Clock:    0x0000003f
sdhci: Timeout:  0x00000000 | Int stat: 0x00000000
sdhci: Int enab: 0x107f000b | Sig enab: 0x107f000b
sdhci: AC12 err: 0x00000000 | Slot int: 0x00000003
sdhci: Caps:     0x07eb0000 | Caps_1:   0x00000007
sdhci: Cmd:      0x00000c1b | Max curr: 0x00ffffff
sdhci: Host ctl2: 0x00000001
sdhci: ===========================================
usb 2-1: device descriptor read/64, error -110
input: PixArt USB Optical Mouse as /devices/platform/fsl-ehci.1/usb2/2-1/2-1:1.0/input/input0
generic-usb 0003:04CA:0061.0001: input,hidraw0: USB HID v1.11 Mouse  on usb-fsl-ehci.1-1/input0

I need help, where exactly going wrong in process of building & installation of Android OS.
khiremandar
 
Posts: 86
Joined: Wed Sep 03, 2014 11:38 am

Re: Android source build...What next?

Postby omid » Tue Oct 07, 2014 8:02 pm

I don't know why you have this much problem with this
Did you compile successfully ? If yes do the followings I hope it works for you
1) put the SD card into your computer then sudo gparted then go to Device then

create partition table and after that go to partition->new it should delete all information on your SD card
Then . sudo blkid to find out what is the name of SD card it usually is sdb
then

sudo dd if=/dev/zero of=/dev/sdX bs=1M count=1

sudo ./wand_fsl_sdcard-part.sh /dev/sdX ( it should takes around one minutes and make new patitions for your SD card )

dd if=wand-4.3/bootable/bootloader/uboot-imx/SPL of=/dev/sdX bs=1K seek=1

mkdir /media/imx6/boot

sudo mount -t vfat /dev/sdX1 /media/imx6
sudo mount -t ext4 /dev/sdX5 /media/system

sudo cp wand-4.3/kernel_imx/arch/arm/boot/uImage /media/imx6/boot/
sudo cp wand-4.3/bootable/bootloader/uboot-imx/u-boot.img /media/imx6/boot/
sudo wand-4.3/bootable/bootloader/uboot-imx/out.bmp.gz /media/imx6/boot/
sudo wand-4.3/bootable/bootloader/uboot-imx/uEnv.txt /media/imx6/boot/ ( go to wand4-3/settings ) and copy the boot arguments that you want to use )
sudo mkimage -A arm -O linux -T ramdisk -C none -a 0x10800800 -n "Android Root Filesystem" -d wand-4.3/out/target/product/wandboard/ramdisk.img /media/imx6/boot/uramdisk.img


sudo cp -a wand-4.3/out/target/product/wandboard/system/* /media/system/ ( or use dd command to copy this files if it doesnt work )

It should work
Best regards
omid
 
Posts: 19
Joined: Fri Sep 12, 2014 5:13 pm

Next

Return to Software - Android

Who is online

Users browsing this forum: No registered users and 15 guests