gards
Mirek
--
View this message in context:
http://www.nabble.com/Re%3A-Linux-doesn-not-boot-from-u-boot-on-ML403-tf4504418.html#a12875133
Sent from the linuxppc-embedded mailing list archive at Nabble.com.
___
Linuxppc-embedded mailing list
Linuxppc-embedde
On Sun, 23 Sep 2007 09:32:25 -0600
"Grant Likely" <[EMAIL PROTECTED]> wrote:
> On 9/23/07, Miroslaw Dach <[EMAIL PROTECTED]> wrote:
> > Hi Grant,
> >
> > Thank you very much for your advices which were very valuable for me.
> >
> > Recently I have followed your advice to move from kernel 2.6.21 to
On 9/23/07, Miroslaw Dach <[EMAIL PROTECTED]> wrote:
> Hi Grant,
>
> Thank you very much for your advices which were very valuable for me.
>
> Recently I have followed your advice to move from kernel 2.6.21 to the
> higher one in order to have the possibility to boot the kernel from
> u-boot. I hav
Hi Grant,
Thank you very much for your advices which were very valuable for me.
Recently I have followed your advice to move from kernel 2.6.21 to the
higher one in order to have the possibility to boot the kernel from
u-boot. I have copied across from you git tree the latest version of linux
ker
On 8/30/07, Miroslaw Dach <[EMAIL PROTECTED]> wrote:
>
> When I try to start zImage.elf with bootelf command the system hangs during
> uncompressing.
> When I try to start uImage with bootm command the image is uncompressed
> but it does not start properly.
Ugh, I'm stumped. Sorry. I'd spend som
I have done further investigation with bootelf and zImage.elf (from
u-boot) and it seems to be that the system fails during image
uncompression: The last command executed is: r = zlib_inflate(&s,
Z_FINISH); /* file: ./arch/ppc/boot/common/misc-common.c */
zlib_inflate function code is in ./lib/zli
Hi Grant,
Yes you are right that I should use uImage instead of zImage.elf
I have tried first bootm and uImage but it also hanged during
uncompression so next I have tried bootelf zImage.elf to see how this
works because I was able to run zImage.elf straight from EDK via jtag.
Cheers
On 8/29/07, Miroslaw Dach <[EMAIL PROTECTED]> wrote:
> Hi Grant,
>
> My zImage.elf has 1.1 MB and uImage 968 KB.
> Could you tell me please how to hook up GDB to debug u-boot?
Ah-HA! You're using the wrong type of kernel image. When booting
from u-boot, you should be using a 'uImage', no
Hi Grant,
My zImage.elf has 1.1 MB and uImage 968 KB.
Could you tell me please how to hook up GDB to debug u-boot?
I have examined the file in u-boot which does the bootelf:
cat common/cmd_elf.c:
int do_bootelf (cmd_tbl_t *cmdtp, int flag, int argc, char *argv[])
:
:
:
:
addr = l
On 8/28/07, Miroslaw Dach <[EMAIL PROTECTED]> wrote:
> This buffer refers to the kernel which I boot straight from jtag but not
> u-boot.
/me remembers something
How big is your kernel image? Seems to me I've had problems with
kernel images that were too large not being uncompressed properly
This buffer refers to the kernel which I boot straight from jtag but not
u-boot.
Below I attach whole buffer printout:
=> 0x20f0c4 200
0020f0c4: 3c353e5b 20202020 302e3030 30303030<5>[0.00
0020f0d4: 5d204c69 6e757820 76657273 696f6e20] Linux version
0020f0e4: 322e362e 32312d72 6
On 8/28/07, Miroslaw Dach <[EMAIL PROTECTED]> wrote:
> 8. I have typed: md 0x20f0c4 100 and it showed me the buffer:
>
> 0020f0c4: 3c353e5b 20202020 302e3030 30303030<5>[0.00
> 0020f0d4: 5d204c69 6e757820 76657273 696f6e20] Linux version
> 0020f0e4: 322e362e 32312d72 63362028 726f6f
Hi Grant,
I have did as you suggested:
1. I have started u-boot
2. I have loaded zImage.elf to the memory 0xf0
3. I have typed: bootelf 0xf0
Linux has hanged during uncompressing
4. I have stopped the system and reloaded u-boot to examine __log_buf
( address 0x20f0c4)
Unfort
On 8/28/07, Miroslaw Dach <[EMAIL PROTECTED]> wrote:
> Hi Grant,
>
> Thanks for your answer.
> I have found in the System.map :
> c020f0c4 b __log_buf
>
> Is the address c020f0c4 relative to the .data segment?
0xc000 are virtual kernel addresses; not physical addresses. If
the MMU is
Hi Grant,
Thanks for your answer.
I have found in the System.map :
c020f0c4 b __log_buf
Is the address c020f0c4 relative to the .data segment?
I understand that when the system hangs I should type in the XMD window
stop.
Is there anyway to examine the memory from the XMD window? or sho
On 8/28/07, Miroslaw Dach <[EMAIL PROTECTED]> wrote:
> Linux/PPC load: console=ttyUL0,9600 root=/dev/nfs rw
> nfsroot=129.117.144.113:/opt/eldk41/ppc_4xx,tcp
> ip=virtex4-mirek:eth0:dhcp panic=1
> Uncompressing Linux...
>
>
> After that system just hangs.
>
> I do not understand why it is possi
I have done additional test with my u-boot and linux kernel.
I have downloaded u-boot(.elf) and zImage.elf via jtag to SDRAM:
The SDRAM has 32 MB:
Address Map for Processor ppc405_0
(0x-0x01ff) DDR_SDRAM_1 plb
The steps I have doe are as following:
1. XMD% dow -data zImage.elf
On 8/27/07, Miroslaw Dach <[EMAIL PROTECTED]> wrote:
> Hi Grant,
>
> Thank you for your response.
>
> My u-boot bootargs is set to:
> console=ttyUL0,9600 root=/dev/nfs rw
> nfsroot=129.117.144.113:/opt/eldk41/ppc_4xx,tcp
> ip=virtex4-mirek:eth0:dhcp panic=1
Drop the ',9600'. It's i
Hi Grant,
Thank you for your response.
My u-boot bootargs is set to:
console=ttyUL0,9600 root=/dev/nfs rw
nfsroot=129.117.144.113:/opt/eldk41/ppc_4xx,tcp ip=virtex4-mirek:eth0:dhcp
panic=1
where I can find __log_buf for kernel messages?
Best Regards
Mirek
On Mon, 27 Aug 200
On 8/27/07, Mirek23 <[EMAIL PROTECTED]> wrote:
> 4. I am trying to start the kernel
>
> => bootm 0x100
>
> ## Booting image at 0100 ...
> Image Name: Linux-2.6.21-rc6
> Image Type: PowerPC Linux Kernel Image (gzip compressed)
> Data Size:991375 Bytes = 968.1 kB
> Load Address: 0
.144.113:/opt/eldk41/ppc_4xx,tcp
ip=virtex4-mirek:eth0:dhcp panic=1
Those bootargs where tested with zImage.elf and seem to be fine.
Does somebody has some suggestion?
Thank you in advance for any hint on that.
Mirek
--
View this message in context:
http://www.nabble.com/Linux-doesn-not-boo
21 matches
Mail list logo
