Atmel website | ARM Community | AVR freaks | Technical Support
Banner
 FAQ •  Search •  Register •  Login 

All times are UTC + 1 hour [ DST ]




Post new topic Reply to topic  [ 4 posts ] 
Author Message
 Post subject: Kernel boot log shows all junk characters
PostPosted: Fri Mar 25, 2011 7:22 am 
Offline

Joined: Fri Mar 25, 2011 6:58 am
Posts: 3
Hi

I have development board with AT91SAM9260 processor. I am trying to port linux-2.6.27 kernel on it.

The board is from local vendor. Vendor has ported u-boot and linux-2.6.19 kernel on it. Vendor also patched source for linux-2.6.19. I compiled this source and loaded on board through uboot. It boots the kernel correctly.

I downloaded the linux-2.6.27 vanilla kernel. Downloaded the patch for AT91SAM9260 for this community and applied it to the kernel.

I also applied patch specific to my board. compile it and downloaded it to the board.
But after "Uncompressing kernel.....done" message lots of junk characters are shown on the console. uboot passes boot argument as "console=ttyS0,38400"

Can you please help me ?


Top
 Profile  
 
 Post subject: Re: Kernel boot log shows all junk characters
PostPosted: Fri Mar 25, 2011 2:34 pm 
Offline

Joined: Sat Oct 30, 2010 6:04 pm
Posts: 574
Doesn't AT91BootStrap and u-boot use 115200 baud for the terminal? That's what I'm using for my 9260/9G20 linux builds.


Top
 Profile  
 
 Post subject: Re: Kernel boot log shows all junk characters
PostPosted: Thu Mar 31, 2011 9:36 am 
Offline

Joined: Fri Mar 25, 2011 6:58 am
Posts: 3
No. at91bootstrap.bin and u-boot.bin are provided by vendor and they are compiled to work at 34800 baud rate.

FYI, u-boot version is 1.1.6.


Top
 Profile  
 
 Post subject: Re: Kernel boot log shows all junk characters
PostPosted: Thu Mar 31, 2011 5:25 pm 
Offline

Joined: Sat Oct 30, 2010 6:04 pm
Posts: 574
Perhaps you should go to your local vendor, and work out what additional patches are required?

Have you tried seeing if the output works better at 115200? Assuming your boot parameter is wrong, or perhaps the kernel thinks the CPU/sysyem is clocking at a different rate than it really is. This might be especially true if the vendor's board doesn't use the standard 18.432 MHz crystal. You've provided no details of the board in question.

I'd suggest you stick a scope on the serial output, and figure out what the bit-timing actually being used is. Work backward from there using the output when you are using the right baud rate in your terminal. If the bit timing doesn't match any known valid baud rate, then the hardware and software have different ideas about the system clock(s).


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 4 posts ] 

All times are UTC + 1 hour [ DST ]


Who is online

Users browsing this forum: No registered users and 1 guest


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to: