console massge problem

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

console massge problem

395 Views
kimsangyoung
Contributor I

Dear all

The console message i.mx6q board. I do not know why the message has stopped . Which problem is I can not hear the entire message ? Please let me know

 

U-Boot 2009.08 (12??24 2014 - 15:15:41)

 

 

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

 

Thermal sensor with ratio = 177

 

Temperature:   49 C, calibration data 0x5604b57d

 

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: 0x63012 [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

 

Found PFUZE100! deviceid=10,revid=11

 

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

 

FEC0 [PRIME]

 

Hit any key to stop autoboot:  0

 

kernel   @ 10808000 (4841212)

 

ramdisk  @ 11800000 (496509)

 

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 androidboot.serialno=2009b9d4dbc84cc9

 

 

Starting kernel ...

 

 

Uncompressing Linux... done, booting the kernel.

 

Initializing cgroup subsys cpu

 

Linux version 3.0.35-06522-g0a3529b (root@dwlee-All-Series) (gcc version 4.6.x-google 20120106 (prerelease) (GCC) ) #2 SMP PREEMPT Tue Dec 30 12:02:42 KST 2014

 

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, silicon rev 1.2

 

PERCPU: Embedded 7 pages/cpu @c133e000 s6528 r8192 d13952 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 androidboot.serialno=2009b9d4dbc84cc9

 

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: 819988k/819988k available, 228588k 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 - 0xc0047000   ( 252 kB)

 

      .text : 0xc0047000 - 0xc0910548   (8998 kB)

 

      .data : 0xc0912000 - 0xc09ac438   ( 618 kB)

 

       .bss : 0xc09ac45c - 0xc0b34f7c   (1571 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

 

Security Framework initialized

 

SELinux:  Initializing.

 

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

 

UV<0>

 

Labels (1)
0 Kudos
1 Reply

310 Views
art
NXP Employee
NXP Employee

The most likely cause of the problem is inappropriate hardware design in either SDRAM or power section (some indirect indication to this point is the fact that the system stops booting at the supply voltages setup stage) that prevents the system from completing booting.


Have a great day,
Artur

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