[U-Boot-Users] PPC 8260 Linux boot

[Ori Idan <ori@helicontech.co.il>]

Ok, it seems Linux is booting now or at least we think so
There is not exception now but all we get is few unmeaningfull character 
on the terminal
We belive Linux is booting but the kernel is miscalculating the baud rate.
The clock information in bd_info seems to be Ok but I will double check 
this tomorow.

Does someone has any clue for what may cause this problem?

--
Ori Idan

Wolfgang Denk wrote:

>In message <4105294D.5070508@helicontech.co.il> you wrote:
>  
>
>>I am trying to boot Linux 2.4.25 (code from denx linux-2-4-devel)
>>The board is similar to MPC8260ADS
>>    
>>
>
>Arghh...  A  description  like  this  is  absolutley   useless,   and
>misleading.  Your probably even fooling yourself. Similar? In that it
>uses the same processor? Or is everything IDENTICAL?
>
>  
>
>>What happens is that the kernel is starting but after a short while gets 
>>an exception and the board is reset again.
>>    
>>
>
>Please define "after a short while". Do you see any boot messages  on
>the  console?  Do you see any messages when you do a post mortem dump
>of the log_buf memory?
>[See http://www.denx.de/twiki/bin/view/DULG/LinuxPostMortemAnalysis]
>
>  
>
>>We tried looking at the kernel sources to see where we get, we did this 
>>by lighting hardware LEDS we have on the board.
>>    
>>
>
>I see. Please remove ALL this code and try again. perhaps it is  just
>your  debugging  code  which  crashes  the  system.  [This  has  been
>discussed before, both here and in the linuxppc mailing lists. Search
>the archives.]
>
>  
>
>>We tried to find where in the kernel we get the exception, we could not 
>>find exactly where it happens, but we did find that it happens somewhere 
>>in the function prom_init called from early_init inside 
>>arch/ppc/kernel/setup.c
>>
>>Does anyone have any idea what we should look next?
>>    
>>
>
>OK, I'll give you two hints:
>
>1) get yourself a BDI2000. You will need it.
>
>2) Check your memory map, and the init sequence of  your  SDRAM  [no,
>   I'm not going to explain this here again. Search the archives.]
>
>Best regards,
>
>Wolfgang Denk
>
>  
>