Kernel for ARM.

Hi,

I'm trying to build new kernel for my ATMEL AT91SAM9260 processor. Kernel provided by manufacturer work well but my kernels sends garbage to a serial console.

Original kernel:

## Booting image at 20200000 ... > Image Name: Linux-2.6.24-rc5-rt1 > Image Type: ARM Linux Kernel Image (uncompressed) > Data Size: 1118064 Bytes = 1.1 MB > Load Address: 20008000 > Entry Point: 20008000 > Verifying Checksum ... OK > Loading Kernel Image ... OK > > Starting kernel ... > > Uncompressing

Linux.............................................................

............. done, booting the kernel. > Linux version 2.6.24-rc5-rt1 (awa@apps) (gcc version 4.3.6 (Buildroot 2011 > .11) ) #16 PREEMPT RT Thu Dec 29 00:08:08 CET 2011 > CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177 > Machine: Telit CS1275

My kernel:

## Booting image at 20200000 ... > Image Name: Linux-3.0.14-rt31 > Image Type: ARM Linux Kernel Image (uncompressed) > Data Size: 1451676 Bytes = 1.4 MB > Load Address: 20008000 > Entry Point: 20008000 > Verifying Checksum ... OK > Loading Kernel Image ... OK > > Starting kernel ... > > Uncompressing Linux... done, booting the kernel. >  garbage, more garbage

Any ideas?

--
Best regards,
Andrzej.
Reply to
Andrzej W.
Loading thread data ...

.........

011

Does your kernel's serial port baud/stopbits/flowcontrol settings match the settings of your hardware serial port? Differences here could cause apparent garbage output (text garbled into junk) to the serial console.

HTH

-- Lew Pitcher

Reply to
Lew Pitcher

The obvious one is that it's compiled with a different default baud rate. I don't have it to hand, but can you add a kernel boot option to force the baud rate to be what you expect?

Or boot it and work through the baud rates hitting return until it responds with plain text.

--
Dave
Too many gadgets, too little time.
Reply to
Dave

Andrzej W. ha scritto, Il 01/01/2012 12:32:

This is a typical problem related to a wrong console kernel parameter. Please pastebin [1] your .config file and your u-boot printenv See also:

-

formatting link

-

formatting link

-

formatting link

[1]
formatting link

-- Helix

Reply to
Helix

W dniu 2012-01-05 17:06, Helix pisze:

Hi,

U-boot parameters for kernel are probably fine, because one kernel starts without trouble another prints garbage.

rootfstype=ext

mtdparts=at91_nand:7936k(ARMboot)ro,-@7936k

--
Best Regards,
Andrzej.
Reply to
Andrzej W.

d!

0400 rootfstype=3Dext

boot)ro,-@7936k

In your board specific files ( linux_../arch/arm/mach-at91/ board_xxx,c), you have to enable the debug uart.

// dbg uart is uart 0 at91_register_uart(0,0,0); // no flow control at91_set_serial_console(0);

Make sure that you are using the right uart.

z
Reply to
zorroslade

ElectronDepot website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.