[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [microblaze-uclinux] Kernell Boot Error on SpartanIIE LC



Hi Calayrac

I've make progress in my project but the kernel stay hang after the famous 
Calibrating delay loop...

I've a quick look in email archive and found that some of us already face that 
problem. Your recommendation at that ttime was that external memory should fit 
the real size of the one embed on the board (my own as 32MB SDRAM), and to 
check interrupt.

I've check all that point unsucessfully. 
I'm afraid there is a problem with cach memory because I resize it to 8k (16k 
on your original design uclinux_auto_6_30_b)

  
if you reduced the cache size, you are required to change your address tag as well.
in your case you should set both C_DCACHE_ADDR_TAG and C_ADDR_TAG_BITS to 12 not 11. It should resolve your problem.
The complete bootlog sequence is:

------------------------------------------------------------------------------
Linux version 2.4.31-uc0 (alayrac@debian-labo) (gcc version 2.95.3-4 Xilinx 
EDK 6.3 Build EDK_Gmm.12.2) #10 jeu jui 28 18:48:51 CEST 
2005                                                         
On node 0 totalpages: 8192                          
zone(0): 8192 pages.                    
zone(1): 0 pages.                 
zone(2): 0 pages.                 
CPU: MICROBLAZE               
Kernel command line: º                      
-----Here a lot of blank line have been removed to reduce the email!
__€
Console: xmbserial on UARTLite
Calibrating delay loop...
-------------------------------------------------------------------------------

As you can see there is a strange sequence after Kernel Command Line (blnk 
line have been removed).

I’ve read on your web site that hardware multiplier could be a reason of that 
kind of errors, but I think that with the auto-config.in this should not 
append?

In fact I’ve tried to remove hardware multiplier but I did not found out where 
to do it either in the hardware project (no such microblaze paramters ) as in 
the kernel configuration (no menu kernel configuration -> processor type and 
features).
  
The design didn't enable the multipiler in the mhs file.

cheers

Jason