Just a guess. Did you have the breakpoint enabled in MDM? If yes, can you turn it off and try again?
----- Original Message ----
From: moises j. cabrera <mojuca1808@xxxxxxxxxxxx>
To: microblaze-uclinux@xxxxxxxxxxxxxx
Sent: Sunday, January 20, 2008 6:59:44 PM
Subject: Re: [microblaze-uclinux] problems with download image.bin for kernel 2.6
Hi,
i sure that serial driver is not the problem, because i probe with the SAME hardware platform, and 2.4 kernel works fine, but 2.6 kernel does not.
i only want to know what options do i check or not in the "Customize Kernel Settings" Options, when i configure my kernel.
only a simple configuration, only for 2.6 kernel can run on my board, only that.
i also left default options, i mean, i do nothing in "Customize Kernel Settings" and the same problem appers.
thanks for your help
Michal Simek <monstr@xxxxxxxxx> escribió:
Hi,
> i give up with 2.6 kernel and i am working with 2.4 kernel, until now,
>
no one can response me why is
this problem and how can i fix it, so i
> quit.
1. Kernel 2.6 is good choice.
> i am sure that is the kernel setting configuration, because in 2.4 and
> 2.6 menus of "make menuconfig" are different. And some options change
> since 2.4
2. Yes, .config files from 2.4 and 2.6 are different
> but appers next message in terminal window:
>
> found romfs @ 0x4416108c (0x000ee000)
> #### klimit 44175000 #####
> Moving 0x000ee000 bytes from 0x4416108c to 0x44174d54
> New klimit: 0x44263000
>
> and then nothing else happens. What is it happen??, i am using
> Spartan 3E rev. D, my test Memory works fine, and i change my mode
> jumpers to M.S. mode and to FPGA mode.
3. nothing happens? I think that a lot of things happen but you don't
have output on console. Be sure that you have correct setting for your
serial driver. I hope you use
uartlite.
> and
then nothing else happens. What is it happen??, i am using
> Spartan 3E rev. D, my test Memory works fine, and i change my mode
> jumpers to M.S. mode and to FPGA mode.
4. test Memory only tells you that the memory seem works properly - this
test is very simple and covers only small amount of faults.
5. Do you use U-BOOT? U-BOOT helps you testing your design more
carefully and helps you with booting kernel.
If you use U-BOOT I recommend you check the log_buf of kernel
# cat System.map | grep __log_buf (output is memory address)
output is 441bf650
in U-BOOT you can see output like this.
U-Boot-mONStR> md 441bf650
441bf650: 3c343e46 6f756e64 20464454 20617420 <4>Found FDT at
441bf660: 30783435 31303030 30300a3c 353e4c69 0x45100000.<5>Li
441bf670: 6e757820 76657273 696f6e20 322e362e nux version 2.6.
441bf680: 32302d75 63302028 6d696372 6f626c61 20-uc0
(microbla
441bf690: 7a65406d
6f6e7374 722e6575 29202867 ze@xxxxxxxxx) (g
441bf6a0: 63632076 65727369 6f6e2033 2e342e31 cc version 3.4.1
441bf6b0: 20282050 6574614c 696e7578 20302e32 ( PetaLinux 0.2
441bf6c0: 30204275 696c6420 2d726331 20303530 0 Build -rc1 050
441bf6d0: 36303720 29292023 31382046 7269204e 607 )) #18 Fri N
441bf6e0: 6f762032 33203136 3a34303a 35302043 ov 23 16:40:50 C
441bf6f0: 45542032 3030370a 3c363e73 65747570 ET 2007.<6>setup
441bf700: 5f637075 696e666f 3a20696e 69746961 _cpuinfo: initia
441bf710: 6c697369 6e670a3c 363e7365 7475705f lising.<6>setup_
441bf720: 63707569 6e666f3a 20557369 6e672066 cpuinfo: Using f
441bf730: 756c6c20 43505520 50565220 73757070 ull CPU PVR supp
441bf740: 6f72740a 3c333e20 2d3e2065 61726c79 ort.<3> -> early
If you see linux kernel log - you win. Your serial driver is not
configured properly.
Regards,
Michal
Simek
www.monstr.eu
___________________________
microblaze-uclinux mailing list
microblaze-uclinux@xxxxxxxxxxxxxx
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/
¡Capacidad ilimitada de almacenamiento en tu correo!
No te preocupes más por el espacio de tu cuenta con Correo Yahoo!:
http://correo.yahoo.com.mx/