mxcintuart.0 - baudrate problem.

Noel_V — Wed, 21 Dec 2011 13:16:45 GMT

Hi all,

iMX53 -QSB .

I've tried to use the L2.6.35_11.09.01_ER patches for the QSB (loco)

kernel (2.6.35.3-1129-g691c08a-gd4b109a-dirty) is booting till.. I get all kernel messge

mxcintuart.0: ttymxc0 at MMIO 0x53fbc000 (irq = 31) is a Freescale i.MX..

After this only crap is printed out on the serial-console.

Anny suggestions ?

Regards

Noel

PS: older patches where working for the same hardware QSB

Re: mxcintuart.0 - baudrate problem.

fabio_estevam — Wed, 21 Dec 2011 14:07:57 GMT

Try to use the U-boot from 11.09 as well.

There were some changes in the UART source PLL, so you need to make sure U-boot and kernel are aligned.

Regards,

Fabio Estevam

Re: mxcintuart.0 - baudrate problem.

Noel_V — Wed, 21 Dec 2011 14:23:12 GMT

Hi,

thanks for the response.

BUT i;m using Uboot 11.09 (ref console log)

U-Boot 2011.09 (Dec 14 2011 - 15:51:24)

CPU:   Freescale i.MX53 family rev2.1 at 800 MHz
Reset cause: POR
Board: MX53 LOCO
DRAM: 1 GiB
WARNING: Caches not enabled
MMC:   FSL_ESDHC: 0, FSL_ESDHC: 1
lcd_enable(): invoked
setup_iopmux_ipu(): invoked
setup_iopmux_ipu(): done
lcd_enable(): DONE
In:    serial
Out:   serial
Err:   serial
Net:   got MAC address from fuse: 00:04:9f:01:c7:e3
FEC

Hit any key to stop autoboot: 0
Using FEC device
TFTP from server xxxxx; our IP address is yyyyyyy
Filename 'uImageIMX7'.
Load address: 0x70800000
Loading: #################################################################
         #################################################################
         ################################################################
done
Bytes transferred = 2846808 (2b7058 hex)
## Booting kernel from Legacy Image at 70800000 ...
   Image Name:   Linux-2.6.35.3-1129-g691c08a-gd4
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2846744 Bytes = 2.7 MiB
   Load Address: 70008000
   Entry Point: 70008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Linux version 2.6.35.3-1129-g691c08a-gd4b109a-dirty (noel@bmslin00042) (gcc versi
on 4.5.3 (Buildroot 2011.11-gd4b109a-dirty) ) #7 PREEMPT Wed Dec 21 13:54:24 CET
2011
CPU: ARMv7 Processor [412fc085] revision 5 (ARMv7), cr=10c53c7f
CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
Machine: Freescale MX53 LOCO Board
Memory policy: ECC disabled, Data cache writeback
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 250880
Kernel command line: console=ttymxc0,115200 video=mxcdi1fb:GBR24,XGA di1_primary
tve root=/dev/nfs ip=dhcp nfsroot=150.158.204.128:/nfsroot/testbimx
PID hash table entries: 4096 (order: 2, 16384 bytes)
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Memory: 480MB 512MB = 992MB total
Memory: 998332k/998332k available, 17476k reserved, 0K highmem
Virtual kernel memory layout:
    vector : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap : 0xfff00000 - 0xfffe0000   ( 896 kB)
    DMA     : 0xf9e00000 - 0xffe00000   ( 96 MB)
    vmalloc : 0xe0800000 - 0xf4000000   ( 312 MB)
    lowmem : 0x80000000 - 0xe0000000   (1536 MB)
    pkmap   : 0x7fe00000 - 0x80000000   (   2 MB)
    modules : 0x7f000000 - 0x7fe00000   ( 14 MB)
      .init : 0x80008000 - 0x80026000   ( 120 kB)
      .text : 0x80026000 - 0x807ee000   (7968 kB)
      .data : 0x8080e000 - 0x80856940   ( 291 kB)
SLUB: Genslabs=11, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Hierarchical RCU implementation.
        RCU-based detection of stalled CPUs is disabled.
        Verbose stalled-CPUs detection is disabled.
NR_IRQS:368
MXC GPIO hardware
MXC IRQ initialized
MXC_Early serial console at MMIO 0x53fbc000 (options '115200')
bootconsole [ttymxc0] enabled
Console: colour dummy device 80x30
Calibrating delay loop... 799.53 BogoMIPS (lpj=3997696)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
devtmpfs: initialized
regulator: core version 0.5
NET: Registered protocol family 16
i.MX IRAM pool: 128 KB@0xe0840000
IRAM READY
CPU is i.MX53 Revision 2.1
Using SDMA I.API
MXC DMA API initialized
IMX usb wakeup probe
IMX usb wakeup probe
bio: create slab <bio-0> at 0
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
da9052_i2c_is_connected - i2c read success....
regulator: DA9052_LDO1: 600 <--> 1800 mV at 1300 mV normal
regulator: DA9052_LDO2: 600 <--> 1800 mV at 1300 mV normal
regulator: DA9052_LDO3: 1725 <--> 3300 mV at 3300 mV normal
regulator: DA9052_LDO4: 1725 <--> 3300 mV at 2775 mV normal
regulator: DA9052_LDO5: 1200 <--> 3600 mV at 1300 mV normal
regulator: DA9052_LDO6: 1200 <--> 3600 mV at 1300 mV normal
regulator: DA9052_LDO7: 1200 <--> 3600 mV at 2750 mV normal
regulator: DA9052_LDO8: 1200 <--> 3600 mV at 1800 mV normal
regulator: DA9052_LDO9: 1250 <--> 3650 mV at 2500 mV normal
regulator: DA9052_LDO10: 1200 <--> 3600 mV at 1300 mV normal
regulator: DA9052_BUCK_CORE: 500 <--> 2075 mV at 1100 mV normal
regulator: DA9052_BUCK_PRO: 500 <--> 2075 mV at 1300 mV normal
regulator: DA9052_BUCK_MEM: 925 <--> 2500 mV at 1500 mV normal
regulator: DA9052_BUCK_PERI: 1800 <--> 3600 mV at 3600 mV normal
DA9053 chip ID reg read=0xa3
BB version probed
IPU DMFC NORMAL mode: 1(0~1), 5B(4,5), 5F(6,7)
Bluetooth: Core ver 2.15
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Switching to clocksource mxc_timer1
NET: Registered protocol family 2
IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
TCP bind hash table entries: 65536 (order: 6, 262144 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
TCP reno registered
UDP hash table entries: 512 (order: 1, 8192 bytes)
UDP-Lite hash table entries: 512 (order: 1, 8192 bytes)
NET: Registered protocol family 1
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
LPMode driver module loaded
Static Power Management for Freescale i.MX5
PM driver module loaded
sdram autogating driver module loaded
Bus freq driver module loaded
DI1 is primary
mxc_dvfs_core_probe
DVFS driver module loaded
i.MXC CPU frequency driver
DVFS PER driver module loaded
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
JFFS2 version 2.2. (NAND) Â© 2001-2006 Red Hat, Inc.
msgmni has been set to 1949
alg: No test for stdrng (krng)
cryptodev: driver loaded.
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
regulator: get() with no identifier
By setting, SII driver will not be enabled
By setting, LDB driver will not be enabled
mxc_ipu mxc_ipu: Channel already disabled 9
mxc_ipu mxc_ipu: Channel already uninitialized 9
Console: switching to colour frame buffer device 100x30
mxc_ipu mxc_ipu: Channel already disabled 7
mxc_ipu mxc_ipu: Channel already uninitialized 7
mxc_ipu mxc_ipu: Channel already disabled 10
mxc_ipu mxc_ipu: Channel already uninitialized 10
Serial: MXC Internal UART driver
mxcintuart.0: ttymxc0 at MMIO 0x53fbc000 (irq = 31) is a Freescale i.MX
ù <~Á§\ä

Fabio Estevam said:

Try to use the U-boot from 11.09 as well.
There were some changes in the UART source PLL, so you need to make sure U-boot and kernel are aligned.
Regards,
Fabio Estevam

Re: mxcintuart.0 - baudrate problem.

KrishnaPavan — Thu, 22 Dec 2011 06:06:08 GMT

Hi Noel,

Can you give your env. here.

Are you using SD/MMC, or NFS, or TFTP.

from your log it seems you are using TFTP, but for rootfs or other is unknown.

Also, can you tell me how you applied patches?

Regards :: Krishna Pavan

Re: mxcintuart.0 - baudrate problem.

JoshuaParrish — Thu, 22 Dec 2011 22:38:17 GMT

Do you have an oscope to measure the baud? That you can verify it's a bad baud. It could be a bad card write and mem locations are all screwed up.

i.MX ProcessorsのトピックRe: mxcintuart.0 - baudrate problem.

mxcintuart.0 - baudrate problem.

Re: mxcintuart.0 - baudrate problem.

Re: mxcintuart.0 - baudrate problem.

Re: mxcintuart.0 - baudrate problem.

Re: mxcintuart.0 - baudrate problem.