cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Highlighted
Visitor
Visitor
8,234 Views
Registered: ‎11-12-2008

linux booting problem

Jump to solution

hi everyone

 

i have a problem with booting the linux

 

i get this message in the console and after that the system in freezed

 

zImage starting: loaded at 0x00400000 (sp: 0x0060eeb0)                        
Allocating 0x348dec bytes for kernel ...                    
gunzipping (0x00000000 <- 0x0040d000:0x00588b5b)...done 0x3265e4 bytes         
Attached initrd image at 0x00589000-0x0060d60b  
initrd head: 0x1f8b0808  

                        

Linux/PowerPC load: console=ttyS0 root=/dev/ram rw

Finalizing device tree... flat tree at 0x40ad68
 

no any idea ?

0 Kudos
1 Solution

Accepted Solutions
Highlighted
Visitor
Visitor
9,747 Views
Registered: ‎11-12-2008

 you sholud solve the problem with the MMU and Machine Check Exception .

this issue is in Virtex 4 processors and you can look for the Errata patch !

View solution in original post

0 Kudos
6 Replies
Highlighted
Visitor
Visitor
9,748 Views
Registered: ‎11-12-2008

 you sholud solve the problem with the MMU and Machine Check Exception .

this issue is in Virtex 4 processors and you can look for the Errata patch !

View solution in original post

0 Kudos
Highlighted
Visitor
Visitor
8,002 Views
Registered: ‎02-04-2009

Hi,

I had the same problem.

Which errata patch are you talking about ? : xps ? linux.2.6-xlnx.git ?

Thanks

Stéphane 

0 Kudos
Highlighted
7,580 Views
Registered: ‎03-11-2009

Hi, I have a similar problem : http://forums.xilinx.com/xlnx/board/message?board.id=ELINUX&thread.id=759

As what has been asked before can you explain a little bit what do you mean by:


ahmadexp wrote:

the problem with the MMU and Machine Check Exception .


I checked the Errata about the powerpc on virtex4, but could not find anything specific.

Can you point out which problem is it ?

 

Thanks,

0 Kudos
Highlighted
Visitor
Visitor
7,572 Views
Registered: ‎02-04-2009

I found the solution eventually:

The problem is described in the chapter 6 of 

 http://ce.et.tudelft.nl/publicationfiles/1367_700_thesis.pdf

 

Linux needs the TLB to manage virtual memory but there is a conflict when the design uses OCM.

The report states its an undocumented bug. But one could find a very difficult to understand description of

this limitation on page 194 of ug011"PowerPC Processor Reference Guide" from www.xilinx.com

This is described in two sentences but I guees one has to be a powerpc guru to understand it.

 

The solution is not to use OCM in the design.

 

Another one would be to change the way Linux manages the TLB to allow  the use of OCM if you need them. I would be very

interrested of such a solution if you find a way to circumvent this "feature".

 

May the Xilinx's features be with you !

 

Stéphane 

0 Kudos
Highlighted
Contributor
Contributor
6,848 Views
Registered: ‎09-24-2008

As you said,Can we boot the linux on the design without OCM?

I do delete the ppc405_0_iocm and ppc405 _0_docm,the linux can boot correctly?

0 Kudos
Highlighted
Visitor
Visitor
6,834 Views
Registered: ‎02-04-2009

Yes,

Try that solution.

Don't forget to have a BRAM on the system to hold the bootloop or some standalone test program. 

0 Kudos