Hi Jose, I can only give you some general help here; sorry.
You seem to have adb available, have you called 'adb logcat' and 'adb shell dmesg' to retrieve the user-space and kernel log? These often contain helpful error messages. If you set 'loglevel' in system/core/rootdir/init.rc to '7' and rebuild your images, init should give you more information about what's going on. The program 'logwrapper' can further help you to get program's output into the logcat. Have you checked if system and data partitions are mounted? You should try to fix these warnings about deprecated syntax. IIRC init uses some of these variables to select the init scripts to run. So if the variable contains the wrong value, your script might not be executed. You can find the init source code under /system/core/init/. Best regards Thomas On 19.03.2014 14:30, Jose Vidal wrote: > Hi Thomas, > > When I build my boot.img using my ramdisk and zImage from original > boot.img (I mean, from Android OS), I get the following information on > serial terminal: > > ============ > NAND read: device 0 offset 0x1000000, size 0x600000 > 6291456 bytes read: OK > kernel @ 10808000 (5254328) > ramdisk @ 11800000 (186420) > kernel cmdline: > use boot.img command line: > console=ttymxc0,115200 init=/init video=mxcfb0:dev=ldb,bpp=32 > video=mxcfb1:off video=mxcfb2:off arm_freq=1000 fbmem=24M vmalloc=400M and > > Starting kernel ... > > Initializing cgroup subsys cpu > Linux version 3.0.35-IMX6.JB4.2.2_110.VAR_R13-06284-gc93df02 > (ron@ron-Latitude-E6430-ub12) (gcc version 4.6.x-google 20120106 > (prerelease) (GCC)3 > CPU: ARMv7 Processor [412fc09a] revision 10 (ARMv7), cr=10c53c7d > CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache > Machine: Freescale i.MX 6Quad/DualLite/Solo Variscite SOM > Malformed early option 'caam' > Memory policy: ECC disabled, Data cache writealloc > CPU identified as i.MX6Q, silicon rev 1.2 > PERCPU: Embedded 7 pages/cpu @c1455000 s6592 r8192 d13888 u32768 > Built 1 zonelists in Zone order, mobility grouping on. Total pages: 200672 > Kernel command line: console=ttymxc0,115200 init=/init > video=mxcfb0:dev=ldb,bpp=32 video=mxcfb1:off video=mxcfb2:off > arm_freq=1000 fbmem=24M vma0 > PID hash table entries: 2048 (order: 1, 8192 bytes) > Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) > Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) > Memory: 575MB 216MB = 791MB total > Memory: 789352k/789352k available, 259224k reserved, 401280K 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 : 0xc0000000 - 0xd9000000 ( 400 MB) > pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB) > modules : 0xbf000000 - 0xbfe00000 ( 14 MB) > .init : 0xc0008000 - 0xc0047000 ( 252 kB) > .text : 0xc0047000 - 0xc0a1d408 (10074 kB) > .data : 0xc0a1e000 - 0xc0ac1780 ( 654 kB) > .bss : 0xc0ac17a4 - 0xc0c4b1e0 (1575 kB) > 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 [ttymxc0] 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 > Initializing cgroup subsys debug > Initializing cgroup subsys cpuacct > Initializing cgroup subsys freezer > CPU: Testing write buffer coherency: ok > hw perfevents: enabled with ARMv7 Cortex-A9 PMU driver, 7 counters available > 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 700 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 3ffe0000, size 20000 > ram_console: uncorrectable error in header > ram_console: no valid data in buffer (sig = 0xffffffff) > console [ram-1] enabled > imx_add_mxc_pwm:pdata= (null) > var_som_mx6: bt init > hw-breakpoint: found 6 breakpoint and 1 watchpoint registers. > hw-breakpoint: 1 breakpoint(s) reserved for watchpoint single-step. > hw-breakpoint: maximum watchpoint size is 4 bytes. > L310 cache controller enabled > l2x0: 16 ways, CACHE_ID 0x410000c7, AUX_CTRL 0x02070000, Cache size: > 1048576 B > bio: create slab <bio-0> at 0 > mxs-dma mxs-dma-apbh: initialized > print_constraints: vmmc: 3300 mV > print_constraints: VDD_1.8V: 1800 mV > vgaarb: loaded > SCSI subsystem initialized > libata version 3.00 loaded. > spi_imx imx6q-ecspi.2: 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 $ > mc_pfuze 1-0008: ID: 0,Full lay: 1 ,Metal lay: 1 > mc_pfuze 1-0008: FAB: 0 ,FIN: 0 > print_constraints: PFUZE100_SW1A: 300 <--> 1875 mV at 1300 mV > print_constraints: PFUZE100_SW1B: 300 <--> 1875 mV at 300 mV > print_constraints: PFUZE100_SW1C: 300 <--> 1875 mV at 1300 mV > print_constraints: PFUZE100_SW3A: 400 <--> 1975 mV at 1500 mV > print_constraints: PFUZE100_SW3B: 400 <--> 1975 mV at 1500 mV > print_constraints: PFUZE100_SW4: 800 <--> 3950 mV at 2400 mV > print_constraints: PFUZE100_VSNVS: 1200 <--> 3000 mV at 1800 mV > print_constraints: PFUZE100_VREFDDR: at 750 mV > print_constraints: PFUZE100_VGEN3: 1800 <--> 3300 mV at 2500 mV > print_constraints: PFUZE100_VGEN4: 1800 <--> 3300 mV at 1800 mV > print_constraints: PFUZE100_VGEN5: 1800 <--> 3300 mV at 2500 mV > print_constraints: PFUZE100_VGEN6: 3300 mV > 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) > mxc_mipi_csi2 mxc_mipi_csi2: i.MX MIPI CSI2 driver probed > mxc_mipi_csi2 mxc_mipi_csi2: i.MX MIPI CSI2 dphy version is 0x3130302a > MIPI CSI2 driver module loaded > 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 > i2c-core: driver [max17135] using legacy suspend method > i2c-core: driver [max17135] using legacy resume method > Switching to clocksource mxc_timer1 > NET: Registered protocol family 2 > IP route cache hash table entries: 16384 (order: 4, 65536 bytes) > TCP established hash table entries: 65536 (order: 7, 524288 bytes) > TCP bind hash table entries: 65536 (order: 7, 786432 bytes) > TCP: Hash tables configured (established 65536 bind 65536) > TCP reno registered > UDP hash table entries: 256 (order: 1, 8192 bytes) > UDP-Lite hash table entries: 256 (order: 1, 8192 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: 180K > PMU: registered new PMU device of type 0 > Static Power Management for Freescale i.MX6 > wait mode is enabled for i.MX6 > cpaddr = d9880000 suspend_iram_base=d98f8000 > PM driver module loaded > link up failed, DB_R0:0x001cfc00, DB_R1:0x08200000! > IMX PCIe port: link down with power supply 1! > IMX usb wakeup probe > the wakeup pdata is 0xd66f1ce0 > add wake up source irq 75 > IMX usb wakeup probe > the wakeup pdata is 0xd66f1aa0 > cpu regulator mode:ldo_bypass > _regulator_get: get() with no identifier > mx6_cpu_regulator_init: failed to get pu regulator > i.MXC CPU frequency driver > highmem bounce pool size: 64 pages > ashmem: initialized > NTFS driver 2.1.30 [Flags: R/O]. > JFFS2 version 2.2. (NAND) �© 2001-2006 Red Hat, Inc. > fuse init (API version 7.16) > msgmni has been set to 758 > 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 ldb > _regulator_get: get() with no identifier > mxc_sdc_fb mxc_sdc_fb.1: mxcfb1 is turned off! > mxc_sdc_fb mxc_sdc_fb.2: mxcfb2 is turned off! > 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 [ttymxc0] enabled, bootconsole disabled > console [ttymxc0] 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 > loop: module loaded > (stk) :sysfs entries created > (stk) : debugfs entries created > No sata disk. > ONFI flash detected > ONFI param page 0 valid > NAND device: Manufacturer ID: 0x2c, Chip ID: 0xdc (Micron MT29F4G08ABADAWP) > gpmi-nand imx6q-gpmi-nand.0: enable asynchronous EDO mode 5 > Bad block table found at page 262080, version 0x01 > Bad block table found at page 262016, version 0x01 > 4 cmdlinepart partitions found on MTD device gpmi-nand > Creating 4 MTD partitions on "gpmi-nand": > 0x000000000000-0x000001000000 : "bootloader" > 0x000001000000-0x000002000000 : "bootimg" > 0x000002000000-0x000004000000 : "recovery" > 0x000004000000-0x000020000000 : "root" > GPMI NAND driver registered. (IMX) > UBI: attaching mtd3 to ubi0 > UBI: physical eraseblock size: 131072 bytes (128 KiB) > UBI: logical eraseblock size: 126976 bytes > UBI: smallest flash I/O unit: 2048 > UBI: VID header offset: 2048 (aligned 2048) > UBI: data offset: 4096 > UBI: max. sequence number: 0 > UBI error: ubi_read_volume_table: the layout volume was not found > UBI error: ubi_init: cannot attach mtd3 > 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 > tun: Universal TUN/TAP device driver, 1.6 > tun: (C) 1999-2004 Max Krasnyansky <[email protected] > <mailto:[email protected]>> > 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 > usbcore: registered new interface driver cdc_acm > cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters > 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 GSM modem (1-port) > usbcore: registered new interface driver option > option: v0.7.2:USB Driver for GSM modems > 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 > input: gpio-keys as /devices/platform/gpio-keys/input/input0 > ctw6120-mt 2-0038: Rev.0 multi touchscreen, irq 327 > input: CTW6120 Touchscreen as > /devices/platform/imx-i2c.2/i2c-2/2-0038/input/input1 > ft5x06: Dec 24 2013 > i2c-core: driver [isl29023] using legacy suspend method > i2c-core: driver [isl29023] using legacy resume method > using rtc device, ds1307, for alarms > rtc-ds1307 2-0068: rtc core: registered ds1307 as rtc0 > rtc-ds1307 2-0068: 56 bytes nvram > i2c /dev entries driver > Linux video capture interface: v2.00 > android_work: did not send uevent (0 0 (null)) > mx6q_mipi_powerdown: powerdown=0, power_gp=0x4d > ov5640_read_reg:write reg error:reg=300a > camera ov5640_mipi is not found > mxc_v4l2_output mxc_v4l2_output.0: V4L2 device registered as video16 > mxc_v4l2_output mxc_v4l2_output.0: V4L2 device registered as video17 > usb 2-1: new high speed USB device number 2 using fsl-ehci > usbcore: registered new interface driver uvcvideo > USB Video Class driver (v1.1.0) > i2c-core: driver [mag3110] using legacy suspend method > i2c-core: driver [mag3110] using legacy resume method > imx2-wdt imx2-wdt.0: IMX2+ Watchdog Timer enabled. timeout=60s (nowayout=1) > device-mapper: ioctl: 4.20.0-ioctl (2011-02-02) initialised: > [email protected] <mailto:[email protected]> > Bluetooth: HCI UART driver ver 2.2 > Bluetooth: HCI H4 protocol initialized > Bluetooth: HCILL protocol initialized > sdhci: Secure Digital Host Controller Interface driver > sdhci: Copyright(c) Pierre Ossman > android_work: sent uevent USB_STATE=CONNECTED > mmc0: SDHCI controller on platform [sdhci-esdhc-imx.1] using DMA > android_work: sent uevent USB_STATE=DISCONNECTED > mmc1: SDHCI controller on platform [sdhci-esdhc-imx.2] using DMA > mxc_vdoa mxc_vdoa: i.MX Video Data Order Adapter(VDOA) driver probed > hub 2-1:1.0: USB hub found > VPU initialized > mxc_asrc registered > hub 2-1:1.0: 4 ports detected > revserved_memory_account:viv_gpu registerd > Thermal calibration data is 0x5764f269 > Thermal sensor with ratio = 180 > Anatop Thermal registered as thermal_zone0 > anatop_thermal_probe: default cooling device is cpufreq! > android_work: sent uevent USB_STATE=CONNECTED > android_work: sent uevent USB_STATE=DISCONNECTED > caam caam.0: device ID = 0x0a16010000000000 > caam caam.0: job rings = 2, qi = 0 > caam caam.0: authenc-hmac-md5-cbc-aes-caam > caam caam.0: authenc-hmac-sha1-cbc-aes-caam > caam caam.0: authenc-hmac-sha224-cbc-aes-caam > caam caam.0: authenc-hmac-sha256-cbc-aes-caam > caam caam.0: authenc-hmac-md5-cbc-des3_ede-caam > caam caam.0: authenc-hmac-sha1-cbc-des3_ede-caam > caam caam.0: authenc-hmac-sha224-cbc-des3_ede-caam > caam caam.0: authenc-hmac-sha256-cbc-des3_ede-caam > caam caam.0: authenc-hmac-md5-cbc-des-caam > caam caam.0: authenc-hmac-sha1-cbc-des-caam > caam caam.0: authenc-hmac-sha224-cbc-des-caam > caam caam.0: authenc-hmac-sha256-cbc-des-caam > caam caam.0: cbc-aes-caam > caam caam.0: ecb-aes-caam > caam caam.0: cbc-3des-caam > caam caam.0: cbc-des-caam > android_work: sent uevent USB_STATE=CONNECTED > platform caam_jr.0: registering rng-caam > android_work: sent uevent USB_STATE=DISCONNECTED > usbcore: registered new interface driver usbhid > usbhid: USB HID core driver > logger: created 256K log 'log_main' > mmc1: card claims to support voltages below the defined range. These > will be ignored. > logger: created 256K log 'log_events' > logger: created 256K log 'log_radio' > logger: created 256K log 'log_system' > usbcore: registered new interface driver snd-usb-audio > mmc1: queuing unknown CIS tuple 0x91 (3 bytes) > mxc_hdmi_soc mxc_hdmi_soc.0: MXC HDMI Audio > Cirrus Logic CS42888 ALSA SoC Codec Driver > i2c-core: driver [cs42888] using legacy suspend method > i2c-core: driver [cs42888] using legacy resume method > imx-hdmi-soc-dai imx-hdmi-soc-dai.0: Failed: Load HDMI-video first. > tlv320aic3x-codec 1-001b: asoc: failed to add kcontrol Left Line1R Mux > tlv320aic3x-codec 1-001b: asoc: failed to add kcontrol Left Line1L Mux > asoc: tlv320aic3x-hifi <-> imx-ssi.1 mapping ok > Initialize HDMI-audio failed. Load HDMI-video first! > ALSA device list: > #0: wm8962-audio > oprofile: using arm/armv7-ca9 > GACT probability NOT on > mmc1: new SDIO card at address 0001 > Mirror/redirect action on > USB Gadget resume begins > fsl_udc_resume, Wait for wakeup thread finishes > u32 classifier > Actions configured > Netfilter messages via NETLINK v0.30. > nf_conntrack version 0.5.0 (12336 buckets, 49344 max) > android_work: sent uevent USB_STATE=CONNECTED > 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 > 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' > lib80211_crypt: registered algorithm 'WEP' > lib80211_crypt: registered algorithm 'CCMP' > lib80211_crypt: registered algorithm 'TKIP' > VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4 > Bus freq driver module loaded > Bus freq driver Enabled > mxc_dvfs_core_probe > DVFS driver module loaded > regulator_init_complete: PFUZE100_VGEN6: incomplete constraints, leaving on > rtc-ds1307 2-0068: setting system clock to 2000-01-01 00:55:46 UTC > (946688146) > Freeing init memory: 252K > init (1): /proc/1/oom_adj is deprecated, please use > /proc/1/oom_score_adj instead. > init: cannot open '/initlogo.rle' > init: Unable to open persistent property directory /data/property errno: 2 > init: using deprecated syntax for specifying property > 'ro.product.manufacturer', use ${name} instead > init: property 'ro.product.manufacturer' doesn't exist while expanding > '$ro.product.manufacturer' > init: cannot expand '$ro.product.manufacturer' while writing to > '/sys/class/android_usb/android0/iManufacturer' > init: using deprecated syntax for specifying property > 'ro.product.model', use ${name} instead > init: property 'ro.product.model' doesn't exist while expanding > '$ro.product.model' > init: cannot expand '$ro.product.model' while writing to > '/sys/class/android_usb/android0/iProduct' > init: using deprecated syntax for specifying property 'ro.serialno', use > ${name} instead > init: cannot find '/system/bin/sh', disabling 'console' > init: cannot find '/system/bin/servicemanager', disabling 'servicemanager' > init: cannot find '/system/bin/vold', disabling 'vold' > init: cannot find '/system/bin/netd', disabling 'netd' > init: cannot find '/system/bin/debuggerd', disabling 'debuggerd' > init: cannot find '/system/bin/surfaceflinger', disabling 'surfaceflinger' > init: cannot find '/system/bin/app_process', disabling 'zygote' > init: cannot find '/system/bin/drmserver', disabling 'drm' > init: cannot find '/system/bin/mediaserver', disabling 'media' > init: cannot find '/system/bin/dbus-daemon', disabling 'dbus' > init: cannot find '/system/bin/installd', disabling 'installd' > init: cannot find '/system/etc/install-recovery.sh', disabling > 'flash_recovery' > init: cannot find '/system/bin/keystore', disabling 'keystore' > init: cannot find '/system/bin/rild', disabling 'ril-daemon' > init: cannot find '/system/bin/fakeperm', disabling 'fakeperm' > init: cannot find '/system/bin/gonksched', disabling 'gonksched' > init: cannot find '/system/bin/fakeappops', disabling 'fakeappops' > init: cannot find '/system/bin/b2g.sh', disabling 'b2g' > init: cannot find '/system/bin/rilproxy', disabling 'rilproxy' > init: cannot find '/system/bin/nfcd', disabling 'nfcd' > android_usb: already disabled > android_usb: already disabled > adb_bind_config > adb_open > android_work: sent uevent USB_STATE=DISCONNECTED > android_work: sent uevent USB_STATE=CONNECTED > android_usb gadget: high speed config #1: android > android_work: sent uevent USB_STATE=CONFIGURED > ehci_fsl_bus_suspend begins, Host 1 > ehci_fsl_bus_suspend ends, Host 1 > adb_release > adb_open > android_work: sent uevent USB_STATE=DISCONNECTED > fsl_gadget_disconnect_event: udc enter low power mode > > =========== > > > The above information is useful for you. > > I appreciate any kind of help. > > Thanks in advance > > Best regards, > > jvidalsm > > > 2014-03-19 3:29 GMT-05:00 Thomas Zimmermann <[email protected] > <mailto:[email protected]>>: > > Hi Jose, > > I don't know why it doesn't work, but is your kernel correctly > configured? That would be the first thing I'd look at. Did you build the > kernel yourself of did you re-use the devices pre-installed kernel? > > The start message comes from the serial command line? It could be that > the kernel actually boots, but the serial parameters are incorrect, so > you don't see any output. > > Sorry for not being very helpful here > Thomas > > > On 18.03.2014 22:37, Jose Vidal wrote: > > Hi Thomas, > > > > After a short break, I ready to continue. > > > > I put > > > > $(call inherit-product, device/fsl/imx6/arm2_6dq.mk > <http://arm2_6dq.mk>) > > > > on full_arm2_6dq.mk <http://full_arm2_6dq.mk> file and, after the > build, finally I have my boot.img > > with the next files: > > > > ============= > > drwxrwx--x 2 jvidal jvidal 4096 Mar 18 16:15 data > > -rw-r--r-- 1 jvidal jvidal 151 Mar 18 16:15 default.prop > > drwxr-xr-x 2 jvidal jvidal 4096 Mar 18 16:15 dev > > -rw-r----- 1 jvidal jvidal 857 Mar 18 16:15 fstab.freescale > > -rwxr-x--- 1 jvidal jvidal 109424 Mar 18 16:15 init > > -rwxr-x--- 1 jvidal jvidal 777 Mar 18 16:15 init.b2g.rc > > -rwxr-x--- 1 jvidal jvidal 2626 Mar 18 16:15 init.freescale.rc > > -rwxr-x--- 1 jvidal jvidal 1930 Mar 18 16:15 init.freescale.usb.rc > > -rwxr-x--- 1 jvidal jvidal 2487 Mar 18 16:15 init.goldfish.rc > > -rwxr-x--- 1 jvidal jvidal 23685 Mar 18 16:15 init.rc > > -rwxr-x--- 1 jvidal jvidal 1795 Mar 18 16:15 init.trace.rc > > -rwxr-x--- 1 jvidal jvidal 3947 Mar 18 16:15 init.usb.rc > > drwxr-xr-x 2 jvidal jvidal 4096 Mar 18 16:15 proc > > drwxr-x--- 2 jvidal jvidal 4096 Mar 18 16:15 sbin > > drwxr-xr-x 2 jvidal jvidal 4096 Mar 18 16:15 sys > > drwxr-xr-x 2 jvidal jvidal 4096 Mar 18 16:15 system > > -rw-r--r-- 1 jvidal jvidal 272 Mar 18 16:15 ueventd.goldfish.rc > > -rw-r--r-- 1 jvidal jvidal 4024 Mar 18 16:15 ueventd.rc > > > > ==================== > > > > But, when I turn on my device, I get: > > > > ============ > > > > kernel @ 10808000 (4744188) > > ramdisk @ 11800000 (186420) > > kernel cmdline: > > use boot.img command line: > > console=ttymxc0,115200 init=/init androidboot.console=ttymxc0 > > androidboot.hardware=freescale var_ts_type=ctw6120 > > > > Starting kernel ... > > > > ========== > > > > This is not booting. > > What is the problem ? > > Do you have any idea about how I can to debug ? > > > > > > Thanks in advance > > > > Regards. > > > > jvidalsm > > > > > > 2014-03-18 5:32 GMT-05:00 Thomas Zimmermann > <[email protected] <mailto:[email protected]>>: > > > >> Hi Jose, > >> > >> Good to see that you're making progress. :) I don't know in which > parts > >> of init.rc we really depend, but it's there on the other > platforms, so > >> it's probably necessary. > >> > >> On 18.03.2014 11:04, Jose Vidal wrote: > >>> Hi Thomas, > >>> > >>> Ok, I edited my full_arm2_6dq.mk <http://full_arm2_6dq.mk> > <http://full_arm2_6dq.mk> file. The > >>> line that I used is: > >>> > >>> $(call inherit-product, > >>> $(SRC_TARGET_DIR)/product/generic_no_telephony.mk > <http://generic_no_telephony.mk> > >>> <http://generic_no_telephony.mk>) > >> > >> If possible, try to build an include chain like in the example of the > >> Nexus 4. I don't know what exactly these files add to the build, but > >> some of it might be important. Maybe this could also fix the missing > >> init.rc. > >> > >> Best regards > >> Thomas > >> > >>> > >>> After the build, the files inside of boot.img are: > >>> > >>> drwxrwx--x 2 jvidal jvidal 4096 Mar 18 04:45 data > >>> -rw-r--r-- 1 jvidal jvidal 151 Mar 18 04:45 default.prop > >>> drwxr-xr-x 2 jvidal jvidal 4096 Mar 18 04:45 dev > >>> -rw-r----- 1 jvidal jvidal 857 Mar 18 04:45 fstab.freescale > >>> -rwxr-x--- 1 jvidal jvidal 109424 Mar 18 04:45 init > >>> -rwxr-x--- 1 jvidal jvidal 777 Mar 18 04:45 init.b2g.rc > >>> -rwxr-x--- 1 jvidal jvidal 2626 Mar 18 04:45 init.freescale.rc > >>> -rwxr-x--- 1 jvidal jvidal 2487 Mar 18 04:45 init.goldfish.rc > >>> -rwxr-x--- 1 jvidal jvidal 1795 Mar 18 04:45 init.trace.rc > >>> -rwxr-x--- 1 jvidal jvidal 3947 Mar 18 04:45 init.usb.rc > >>> drwxr-xr-x 2 jvidal jvidal 4096 Mar 18 04:45 proc > >>> drwxr-x--- 2 jvidal jvidal 4096 Mar 18 04:45 sbin > >>> drwxr-xr-x 2 jvidal jvidal 4096 Mar 18 04:45 sys > >>> drwxr-xr-x 2 jvidal jvidal 4096 Mar 18 04:45 system > >>> -rw-r--r-- 1 jvidal jvidal 272 Mar 18 04:45 ueventd.goldfish.rc > >>> -rw-r--r-- 1 jvidal jvidal 4024 Mar 18 04:45 ueventd.rc > >>> > >>> > >>> Only I have init.freescale.rc. Is necessary to have init.rc too? > >>> > >>> Thanks in advance. > >>> > >>> Best regards. > >>> > >>> > >>> jvidalsm > >>> > >>> > >>> 2014-03-18 4:34 GMT-05:00 Thomas Zimmermann > <[email protected] <mailto:[email protected]> > >>> <mailto:[email protected] <mailto:[email protected]>>>: > >>> > >>> Hi Jose > >>> > >>> On 18.03.2014 10:20, Jose Vidal wrote: > >>> > Hi Thomas, > >>> > > >>> > I have the next result: > >>> > > >>> > ~/B2G$ find . -name "*.mk" -type f | xargs grep -n b2g\.mk > >>> > > >>> > ./gaia/Android.mk:17:# We will keep this flag in .b2g.mk > <http://b2g.mk> > >>> <http://b2g.mk> <http://b2g.mk> > >>> > so |./flash.sh gaia| follows > >>> > ./gaia/Android.mk:73:echo $(GAIA_MAKE_FLAGS) > > >>> $(GAIA_PATH)/.b2g.mk <http://b2g.mk> <http://b2g.mk> > >>> > <http://b2g.mk> > >>> > ./build/target/product/generic_no_telephony.mk:89:$(call > >>> > inherit-product, gonk-misc/b2g.mk <http://b2g.mk> > <http://b2g.mk> <http://b2g.mk>) > >>> > > >>> > What it means that ? > >>> > I should to edit generic_no_telephony.mk > <http://generic_no_telephony.mk> > >>> <http://generic_no_telephony.mk> > >>> > <http://generic_no_telephony.mk> file and to link to my > device or > >> I > >>> > should to creat a new file? > >>> > >>> No, you need to make sure that the file is included from > within your > >>> device directory. For example for the Nexus 4 > >>> > >>> - device/lge/mako/full_mako.mk <http://full_mako.mk> > <http://full_mako.mk> includes > >>> - build/target/product/aosp_base.mk <http://aosp_base.mk> > <http://aosp_base.mk>, which > >>> includes > >>> - build/target/product/full_base.mk <http://full_base.mk> > <http://full_base.mk>, which > >>> includes > >>> - build/target/product/generic_no_telephony.mk > <http://generic_no_telephony.mk> > >>> <http://generic_no_telephony.mk>, which includes > >>> - gonk-misc/b2g.mk <http://b2g.mk> <http://b2g.mk>. > >>> > >>> I don't know how your device makefile is called > (full_arm2_6dq.mk <http://full_arm2_6dq.mk>? > >>> <http://full_arm2_6dq.mk?>), but > >>> it should provide something similar. And it should should > override > >> some > >>> of the PRODUCT_ variables. Just have a look at the other > platforms to > >>> get an idea of what exactly is required. > >>> > >>> Best regards > >>> Thomas > >>> > >>> > >>> > > >>> > In the bottom the generic_no_telephony.mk > <http://generic_no_telephony.mk> > >>> <http://generic_no_telephony.mk> > >>> > <http://generic_no_telephony.mk> file there is: > >>> > > >>> > # Overrides > >>> > PRODUCT_BRAND := generic > >>> > PRODUCT_DEVICE := generic > >>> > PRODUCT_NAME := generic_no_telephony > >>> > > >>> > > >>> > Thanks in advance > >>> > > >>> > Regards, > >>> > > >>> > jvidalsm > >>> > > >>> > > >>> > > >>> > 2014-03-18 4:07 GMT-05:00 Thomas Zimmermann > >>> <[email protected] <mailto:[email protected]> > <mailto:[email protected] <mailto:[email protected]>> > >>> > <mailto:[email protected] > <mailto:[email protected]> <mailto:[email protected] > <mailto:[email protected]> > >>>>> : > >>> > > >>> > Hi Jose > >>> > > >>> > On 18.03.2014 09:56, Jose Vidal wrote: > >>> > > Hi Thomas, > >>> > > > >>> > > No, not that happens. > >>> > > > >>> > > I have actually: > >>> > > > >>> > > drwxrwx--x 2 jvidal jvidal 4096 Mar 18 03:37 data > >>> > > -rw-r--r-- 1 jvidal jvidal 151 Mar 18 03:37 > default.prop > >>> > > drwxr-xr-x 2 jvidal jvidal 4096 Mar 18 03:37 dev > >>> > > -rw-r----- 1 jvidal jvidal 857 Mar 18 03:37 > >> fstab.freescale > >>> > > -rwxr-x--- 1 jvidal jvidal 109424 Mar 18 03:37 init > >>> > > -rwxr-x--- 1 jvidal jvidal 2626 Mar 18 03:37 > >> init.freescale.rc > >>> > > -rwxr-x--- 1 jvidal jvidal 2487 Mar 18 03:37 > >> init.goldfish.rc > >>> > > drwxr-xr-x 2 jvidal jvidal 4096 Mar 18 03:37 proc > >>> > > drwxr-x--- 2 jvidal jvidal 4096 Mar 18 03:37 sbin > >>> > > drwxr-xr-x 2 jvidal jvidal 4096 Mar 18 03:37 sys > >>> > > drwxr-xr-x 2 jvidal jvidal 4096 Mar 18 03:37 system > >>> > > -rw-r--r-- 1 jvidal jvidal 272 Mar 18 03:37 > >>> ueventd.goldfish.rc > >>> > > -rw-r--r-- 1 jvidal jvidal 4024 Mar 18 03:37 > ueventd.rc > >>> > > > >>> > > > >>> > > I should to edit gonk-misc/Android.mk ? > >>> > > >>> > Actually you shouldn't have to edit any files, except > those in > >>> > device/<your_device>. For the builds I have on my hard > disk, > >>> b2g.mk <http://b2g.mk> <http://b2g.mk> > >>> > <http://b2g.mk> is > >>> > included by an .mk file under build/target/product/, like > >>> > > >>> > find . -name "*.mk" -type f | xargs grep -n b2g\.mk > >>> > ./build/target/product/full_base.mk:56:$(call > >> inherit-product, > >>> > gonk-misc/b2g.mk <http://b2g.mk> <http://b2g.mk> > <http://b2g.mk>) > >>> > > >>> > You should check if such a line is present and if the > >>> respective file is > >>> > included from the *.mk files in your device directory; > either > >>> directly > >>> > or via other files. > >>> > > >>> > Best regards > >>> > Thomas > >>> > > >>> > > >>> > > > >>> > > Regards. > >>> > > > >>> > > > >>> > > jvidalsm > >>> > > > >>> > > > >>> > > 2014-03-18 3:48 GMT-05:00 Thomas Zimmermann > >>> > <[email protected] > <mailto:[email protected]> <mailto:[email protected] > <mailto:[email protected]>> > >>> <mailto:[email protected] > <mailto:[email protected]> <mailto:[email protected] > <mailto:[email protected]>>> > >>> > > <mailto:[email protected] > <mailto:[email protected]> > >>> <mailto:[email protected] > <mailto:[email protected]>> <mailto:[email protected] > <mailto:[email protected]> > >>> <mailto:[email protected] > <mailto:[email protected]>>>>>: > >>> > > > >>> > > > the dependecies listed in gonk-misc/Android.mk are > >>> included. > >>> > > > >>> > > s/Android.mk/b2g.mk <http://b2g.mk> > <http://b2g.mk> <http://b2g.mk> > >>> <http://b2g.mk> > >>> > > > >>> > > > >>> > > > > >>> > > > Best regards > >>> > > > Thomas > >>> > > > > >>> > > > On 18.03.2014 08:39, Jose Vidal wrote: > >>> > > >> Hi everyone, > >>> > > >> > >>> > > >> I have builded the image files: > >>> > > >> > >>> > > >> boot.img > >>> > > >> system.img > >>> > > >> userdata.img > >>> > > >> recovery.img > >>> > > >> > >>> > > >> I'm using unmkbootimg to extract the files from > >> boot.img. > >>> > > >> When I extract the files from my boot.img I don't > >>> have the same > >>> > > files like boot.img from Hamachi. > >>> > > >> > >>> > > >> My device is a fsl/arm2_6dq and the files > inside the > >>> boot.img > >>> > > (after the build) are: > >>> > > >> > >>> > > >> data > >>> > > >> dev > >>> > > >> proc > >>> > > >> sbin > >>> > > >> sys > >>> > > >> system > >>> > > >> init > >>> > > >> init.freescale.rc > >>> > > >> ueventd.goldfish.rc > >>> > > >> default.prop > >>> > > >> fstab.freescale > >>> > > >> init.goldfish.rc > >>> > > >> ueventd.rc > >>> > > >> > >>> > > >> The files inside the boot.img from Hamachi device > >>> (downloaded > >>> > > from http://elsimpicuitico.wordpress.com/firefoxos/) > >> are: > >>> > > >> > >>> > > >> boot.ver > >>> > > >> dev > >>> > > >> proc > >>> > > >> sbin > >>> > > >> sys > >>> > > >> system > >>> > > >> init.qcom.class_core.sh > <http://init.qcom.class_core.sh> > >>> <http://init.qcom.class_core.sh> > <http://init.qcom.class_core.sh> > >>> > <http://init.qcom.class_core.sh> > >>> > > >> init.qcom.syspart_fixup.sh > <http://init.qcom.syspart_fixup.sh> > >>> <http://init.qcom.syspart_fixup.sh> > >>> > <http://init.qcom.syspart_fixup.sh> > >>> <http://init.qcom.syspart_fixup.sh> > >>> > > >> ueventd.goldfish.rc > >>> > > >> charger > >>> > > >> init > >>> > > >> init.qcom.class_main.sh > <http://init.qcom.class_main.sh> > >>> <http://init.qcom.class_main.sh> > <http://init.qcom.class_main.sh> > >>> > <http://init.qcom.class_main.sh> > >>> > > >> init.qcom.usb.rc > >>> > > >> res > >>> > > >> ueventd.rc > >>> > > >> custpack > >>> > > >> init.b2g.rc > >>> > > >> init.qcom.early_boot.sh > <http://init.qcom.early_boot.sh> > >>> <http://init.qcom.early_boot.sh> > <http://init.qcom.early_boot.sh> > >>> > <http://init.qcom.early_boot.sh> > >>> > > >> init.qcom.usb.sh <http://init.qcom.usb.sh> > <http://init.qcom.usb.sh> > >>> <http://init.qcom.usb.sh> > >>> > <http://init.qcom.usb.sh> > >>> > > >> data > >>> > > >> init.goldfish.rc > >>> > > >> init.qcom.rc > >>> > > >> init.rc > >>> > > >> default.prop > >>> > > >> init.jrd.rc > >>> > > >> init.qcom.sh <http://init.qcom.sh> > <http://init.qcom.sh> > >>> <http://init.qcom.sh> <http://init.qcom.sh> > >>> > > >> init.target.rc > >>> > > >> > >>> > > >> > >>> > > >> How I can make to get the init.b2g.rc, > init.rc inside > >> the > >>> > boot.img ? > >>> > > >> > >>> > > >> I hope for your help. > >>> > > >> > >>> > > >> Thanks in advance. > >>> > > >> > >>> > > >> > >>> > > >> Best regards > >>> > > >> > >>> > > >> jvidalsm > >>> > > >> _______________________________________________ > >>> > > >> dev-b2g mailing list > >>> > > >> [email protected] > <mailto:[email protected]> > >>> <mailto:[email protected] > <mailto:[email protected]>> > >>> > <mailto:[email protected] > <mailto:[email protected]> > >>> <mailto:[email protected] > <mailto:[email protected]>>> > >>> <mailto:[email protected] > <mailto:[email protected]> <mailto:[email protected] > <mailto:[email protected]>> > >>> > <mailto:[email protected] > <mailto:[email protected]> > >>> <mailto:[email protected] > <mailto:[email protected]>>>> > >>> > > >> https://lists.mozilla.org/listinfo/dev-b2g > >>> > > >> > >>> > > > > >>> > > > _______________________________________________ > >>> > > > dev-b2g mailing list > >>> > > > [email protected] > <mailto:[email protected]> > >>> <mailto:[email protected] > <mailto:[email protected]>> > <mailto:[email protected] <mailto:[email protected]> > >>> <mailto:[email protected] > <mailto:[email protected]>>> > >>> > <mailto:[email protected] > <mailto:[email protected]> > >>> <mailto:[email protected] > <mailto:[email protected]>> > <mailto:[email protected] <mailto:[email protected]> > >>> <mailto:[email protected] > <mailto:[email protected]>>>> > >>> > > > https://lists.mozilla.org/listinfo/dev-b2g > >>> > > > > >>> > > > >>> > > > >>> > > > >>> > > > >>> > > -- > >>> > > Jose Vidal Noblecilla > >>> > > Ingeniero Electrónico > >>> > > UNMSM > >>> > > Lima-Perú > >>> > > Cel:994 682 455 > >>> > > >>> > > >>> > > >>> > > >>> > -- > >>> > Jose Vidal Noblecilla > >>> > Ingeniero Electrónico > >>> > UNMSM > >>> > Lima-Perú > >>> > Cel:994 682 455 > >>> > >>> > >> > >> > > _______________________________________________ > > dev-b2g mailing list > > [email protected] <mailto:[email protected]> > > https://lists.mozilla.org/listinfo/dev-b2g > > > > _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
