A problem about android starting on my i.MX6Q SDB that designed according to the freescale i.MX6Q SDB

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

A problem about android starting on my i.MX6Q SDB that designed according to the freescale i.MX6Q SDB

1,056件の閲覧回数
pengxingwei
Contributor III

Hello all,

          my board was designed according to the freescale i.MX6Q-SDB's layout ,it has been  downloaded the android jb4.3_1.1.0 system.But it come across the problem,the uboot can start,but the system can't startup. the starting log as follow:

U-Boot 2009.08-dirty (10鏈28 2015 - 19:30:58)

CPU: Freescale i.MX6 family TO1.5 at 792 MHz

Thermal sensor with ratio = 178

Temperature:   29 C, calibration data 0x5674d369

mx6q pll1: 792MHz

mx6q pll2: 528MHz

mx6q pll3: 480MHz

mx6q pll8: 50MHz

ipg clock     : 66000000Hz

ipg per clock : 66000000Hz

uart clock    : 80000000Hz

cspi clock    : 60000000Hz

ahb clock     : 132000000Hz

axi clock   : 264000000Hz

emi_slow clock: 132000000Hz

ddr clock     : 528000000Hz

usdhc1 clock  : 198000000Hz

usdhc2 clock  : 198000000Hz

usdhc3 clock  : 198000000Hz

usdhc4 clock  : 198000000Hz

nfc clock     : 24000000Hz

Board: i.MX6Q-SABRESD: unknown-board Board: 0x63015 [POR ]

Boot Device: MMC

I2C:   ready

DRAM:   1 GB

MMC:   FSL_USDHC: 0,FSL_USDHC: 1,FSL_USDHC: 2,FSL_USDHC: 3

*** Warning - bad CRC or MMC, using default environment

In:    serial

Out:   serial

Err:   serial

Net:   got MAC address from IIM: 00:00:00:00:00:00

FEC0 [PRIME]

Hit any key to stop autoboot:  0

MX6Q SABRESD U-Boot > boot

kernel   @ 10808000 (4724400)

ramdisk  @ 11800000 (234389)

kernel cmdline:

        use boot.img command line:

        console=ttymxc0,115200 init=/init video=mxcfb0:dev=ldb,bpp=32 video=mxcfb1:off video=mxcfb2:off fbmem=10M fb0base=0x27b00000 vmalloc=400M androidboot.console=ttymxc0 androidboot.hardware=freescale

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

Initializing cgroup subsys cpu

Linux version 3.0.35-06433-g8e02e5d-dirty (zhangyang@ubuntu-12) (gcc version 4.6.x-google 20120106 (prerelease) (GCC) ) #13 SMP PREEMPT Sun Sep 20 19:52:01 CST 2015

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 Sabre-SD Board

Ignoring unrecognised tag 0x54410008

Memory policy: ECC disabled, Data cache writealloc

CPU identified as i.MX6Q, unknown revision

PERCPU: Embedded 7 pages/cpu @c12fd000 s6592 r8192 d13888 u32768

Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 208128

Kernel command line: console=ttymxc0,115200 init=/init video=mxcfb0:dev=ldb,bpp=32 video=mxcfb1:off video=mxcfb2:off fbmem=10M fb0base=0x27b00000 vmalloc=400M androidboot.console=ttymxc0 androidboot.hardware=freescale

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: 379MB 378MB 64MB = 821MB total

Memory: 820504k/820504k available, 228072k 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  : 0xc0000000 - 0xd9000000   ( 400 MB)

    pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)

    modules : 0xbf000000 - 0xbfe00000   (  14 MB)

      .init : 0xc0008000 - 0xc0046000   ( 248 kB)

      .text : 0xc0046000 - 0xc08d2db8   (8756 kB)

      .data : 0xc08d4000 - 0xc096be20   ( 608 kB)

       .bss : 0xc096be44 - 0xc0af3b88   (1568 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

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 3ff00000, size 100000

ram_console: uncorrectable error in header

ram_console: no valid data in buffer (sig = 0x0180421a)

console [ram-1] enabled

No AHCI save PWR: PDDQ enabled

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 0x32070000, Cache size: 1048576 B

bio: create slab <bio-0> at 0

mxs-dma mxs-dma-apbh: initialized

print_constraints: SPKVDD: 4200 mV

print_constraints: vmmc: 3300 mV

vgaarb: loaded

SCSI subsystem initialized

spi_imx imx6q-ecspi.0: 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: recv failed!:-5,0

mc_pfuze: probe of 1-0008 failed with error -1

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

max17135_regulator_init abort: EPDC not enabled

max17135 2-0048: PMIC MAX17135 for eInk display

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: 228K

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=d9934000

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:0x00cfb100, DB_R1:0x08200000!

IMX PCIe port: link down with power supply 1!

IMX usb wakeup probe

the wakeup pdata is 0xd41921e0

add wake up source irq 75

IMX usb wakeup probe

the wakeup pdata is 0xd46ece60

cpu regulator mode(cpu 监管模式):ldo_enable

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 740

NET: Registered protocol family 38

cryptodev: driver loaded.

io scheduler noop registered

io scheduler deadline registered

io scheduler cfq registered (default)

mxc_mipi_dsi mxc_mipi_dsi: i.MX MIPI DSI driver probed

MIPI DSI driver module loaded

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: Can't get fb option for mxcfb1!

mxc_sdc_fb mxc_sdc_fb.2: Can't get fb option for mxcfb2!

imx-sdma imx-sdma: loaded firmware 1.1

imx-sdma imx-sdma: initialized

Serial: IMX driver

imx-uart.2: ttymxc2 at MMIO 0x21ec000 (irq = 60) is a IMX

imx-uart.0: ttymxc0 at MMIO 0x2020000 (irq = 58) is a IMX

console [ttymxc0] enabled, bootconsole disabled

console [ttymxc0] enabled, bootconsole disabled

loop: module loaded

m25p80 spi0.0: unrecognized JEDEC id ffffff

GPMI NAND driver registered. (IMX)

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 <maxk@qualcomm.com>

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

input: max11801_ts as /devices/platform/imx-i2c.1/i2c-1/1-0048/input/input1

egalax_ts 1-0004: egalax_ts: failed to read firmware version

egalax_ts: probe of 1-0004 failed with error -5

egalax_ts 2-0004: egalax_ts: failed to read firmware version

egalax_ts: probe of 2-0004 failed with error -5

android_work: did not send uevent (0 0   (null))

android_work: sent uevent USB_STATE=CONNECTED

android_work: sent uevent USB_STATE=DISCONNECTED

android_work: sent uevent USB_STATE=CONNECTED

android_work: sent uevent USB_STATE=DISCONNECTED

android_work: sent uevent USB_STATE=CONNECTED

android_work: sent uevent USB_STATE=DISCONNECTED

android_work: did not send uevent (0 0   (null))

fsl_gadget_disconnect_event: udc enter low power mode

elan - Read Hello Packet Failed

elan-touch: probe of 2-0010 failed with error -22

i2c-core: driver [isl29023] using legacy suspend method

i2c-core: driver [isl29023] using legacy resume method

using rtc device, snvs_rtc, for alarms

snvs_rtc snvs_rtc.0: rtc core: registered snvs_rtc as rtc0

i2c /dev entries driver

Linux video capture interface: v2.00

USB Gadget resume begins

fsl_udc_resume, Wait for wakeup thread finishes

ov5642_read_reg:write reg error:reg=300a

camera ov5642 is not found

ov5640_read_reg:write reg error:reg=300a

camera ov5640 is not found

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

usbcore: registered new interface driver uvcvideo

USB Video Class driver (v1.1.0)

FIFO_RD_AUX_MSB read fails

FIFO_RD_AUX_LSB read fails

FIFO_RD_AUX_MSB read fails

FIFO_RD_AUX_LSB read fails

FIFO_RD_AUX_MSB read fails

FIFO_RD_AUX_LSB read fails

FIFO_RD_AUX_MSB read fails

FIFO_RD_AUX_LSB read fails

FIFO_RD_AUX_MSB read fails

FIFO_RD_AUX_LSB read fails

FIFO_RD_AUX_MSB read fails

FIFO_RD_AUX_LSB read fails

FIFO_RD_AUX_MSB read fails

FIFO_RD_AUX_LSB read fails

FIFO_RD_AUX_MSB read fails

FIFO_RD_AUX_LSB read fails

FIFO_RD_AUX_MSB read fails

FIFO_RD_AUX_LSB read fails

FIFO_RD_AUX_MSB read fails

FIFO_RD_AUX_LSB read fails

FIFO_RD_AUX_MSB read fails

FIFO_RD_AUX_LSB read fails

FIFO_RD_AUX_MSB read fails

FIFO_RD_AUX_LSB read fails

mag3110 2-000e: check mag3110 chip ID

mag3110 2-000e: read chip ID 0xfffffffb is not equal to 0xc4!

mag3110: probe of 2-000e failed with error -22

i2c-core: driver [mag3110] using legacy suspend method

i2c-core: driver [mag3110] using legacy resume method

mma8x5x 0-001c: read chip ID 0xfffffffb is not equal to 0x1a,0x2a,0x3a,0x4a,0x5a!

mma8x5x: probe of 0-001c failed with error -22

imx2-wdt imx2-wdt.0: IMX2+ Watchdog Timer enabled. timeout=60s (nowayout=1)

device-mapper: uevent: version 1.0.3

device-mapper: ioctl: 4.20.0-ioctl (2011-02-02) initialised: dm-devel@redhat.com

Bluetooth: Virtual HCI driver ver 1.3

Bluetooth: HCI UART driver ver 2.2

Bluetooth: HCIATH3K protocol initialized

Bluetooth: Generic Bluetooth USB driver ver 0.6

usbcore: registered new interface driver btusb

sdhci: Secure Digital Host Controller Interface driver

sdhci: Copyright(c) Pierre Ossman

mmc0: SDHCI controller on platform [sdhci-esdhc-imx.3] using DMA

mmc1: SDHCI controller on platform [sdhci-esdhc-imx.2] using DMA

mmc2: SDHCI controller on platform [sdhci-esdhc-imx.1] 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 0x5674d369

Thermal sensor with ratio = 178

Anatop Thermal registered as thermal_zone0

anatop_thermal_probe: default cooling device is cpufreq!

TO here ,the board  died down ,the cpu  cooled. I need some suggestion about this problem!Thanks!

ラベル(2)
0 件の賞賛
返信
4 返答(返信)

599件の閲覧回数
igorpadykov
NXP Employee
NXP Employee

Hi peng

from log:

mc_pfuze 1-0008: recv failed!:-5,0

mc_pfuze: probe of 1-0008 failed with error -1

seems pmic is not working, so processor voltages may become wrong.

Best regards

igor

-----------------------------------------------------------------------------------------------------------------------

Note: If this post answers your question, please click the Correct Answer button. Thank you!

-----------------------------------------------------------------------------------------------------------------------

0 件の賞賛
返信

599件の閲覧回数
pengxingwei
Contributor III

Hi igorpadykov,

                      Thank you ! if it is really this problem,therefore What should I do to solve it ? Look forward your reply! Thanks!

0 件の賞賛
返信

599件の閲覧回数
igorpadykov
NXP Employee
NXP Employee

you should check i2c pmic signals with oscilloscope.

~igor

0 件の賞賛
返信

599件の閲覧回数
pengxingwei
Contributor III

Hello,

      For my log,there is no PFUZE100 messages,

log1.png

,but at freescale board,there has it

.   log.png

it seems the pfuse hasn't work or the i2c has problem,and platform matching about pfuse maybe need to modfy,if it need to modfy,what should I do for it ?

0 件の賞賛
返信