Thanks Gavin. I went searching for where that would be set in a file, but
couldn't see any file stand out in drivers/char that would contain it. Where is
that defined?
I did work out it was 115200 by just testing different baud rates in dBug.
So the kernel boots, but I get the following exception.
Access Error Exception 12: Error on data read
The full output is below.
What is the general strategy to debug these sorts of things?
Thanks,
Greg
Linux version 2.6.29-uc0 (ghula...@office-desktop) (gcc version 4.2.4) #4 Fri F0
uClinux/COLDFIRE(m5280/5282)
COLDFIRE port done by Greg Ungerer, g...@snapgear.com
Flat model support (C) 1998,1999 Kenneth Albanowski, D. Jeff Dionne
Built 1 zonelists in Zone order, mobility grouping off. Total pages: 2032
Kernel command line:
PID hash table entries: 32 (order: 5, 128 bytes)
Dentry cache hash table entries: 1024 (order: 0, 4096 bytes)
Inode-cache hash table entries: 1024 (order: 0, 4096 bytes)
Memory available: 5932k/8192k RAM, (1214k kernel code, 167k data)
SLUB: Genslabs=12, HWalign=16, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Calibrating delay loop... 43.82 BogoMIPS (lpj=219136)
Mount-cache hash table entries: 512
net_namespace: 520 bytes
NET: Registered protocol family 16
bio: create slab <bio-0> at 0
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 512 (order: 0, 4096 bytes)
TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
TCP: Hash tables configured (established 512 bind 1024)
TCP reno registered
NET: Registered protocol family 1
io scheduler noop registered
io scheduler cfq registered (default)
ColdFire internal UART serial driver
ttyS0 at MMIO 0x40000200 (irq = 77) is a ColdFire UART
console [ttyS0] enabled
ttyS1 at MMIO 0x40000240 (irq = 78) is a ColdFire UART
ttyS2 at MMIO 0x40000280 (irq = 79) is a ColdFire UART
brd: module loaded
PPP generic driver version 2.4.2
uclinux[mtd]: RAM probe address=0x169858 size=0xb6000
Creating 1 MTD partitions on "RAM":
0x000000000000-0x0000000b6000 : "ROMfs"
uclinux[mtd]: set ROMfs to be root filesystem
TCP cubic registered
NET: Registered protocol family 17
VFS: Mounted root (romfs filesystem) readonly on device 31:0.
Freeing unused kernel memory: 52k freed (0x14f000 - 0x15b000)
Access Error Exception 12: Error on data read
On Feb 26, 2010, at 10:38 PM, Gavin Lambert wrote:
> Quoth Greg Hulands:
>> So I was able to build my first 2.6 kernel using all the defaults - just
>> setting freescale and
>> mcf5282lite.
>>
>> When I download the image and then do a go 0x10000 all I get is a bit of
>> jibberish as if the image is
>> corrupt.
>
> Don't forget to check that the serial terminal under Linux is configured to
> use the same baud rate etc as your
> bootloader. (You may need to set boot parameters and/or config vars to do
> this, depending on the terminal driver.)
>
>
> _______________________________________________
> uClinux-dev mailing list
> uClinux-dev@uclinux.org
> http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
> This message was resent by uclinux-dev@uclinux.org
> To unsubscribe see:
> http://mailman.uclinux.org/mailman/options/uclinux-dev
_______________________________________________
uClinux-dev mailing list
uClinux-dev@uclinux.org
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by uclinux-dev@uclinux.org
To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev
