In message [EMAIL PROTECTED] you wrote:
I am new to virtex 4 platform and i am trying to bringup u-boot on ML403
You are off topic on this list. Please post U-Boot related questions o
the U-Boot mailing list.
But - be warned:
DISCLAIMER:
Such disclaimers are taken seriously
Hi,
I am new to virtex 4 platform and i am trying to bringup u-boot on ML403
board. I download u-boot.zip ftrom ML410 site and am trying to compile
it for
ML403 using the following command
make ml403_config
make
and i am getting the following error.
../xilinx_iic/iic_adapter.c
If you're starting a new design, I *highly* recommend using EDK9.2 with
MPMC3 and LL_TEMAC.
Using the Wizard in EDK9.2 and using the kernel from git.xilinx.com
everything will work fine out-of-the-box. Including the ethernet.
I've had troubles with the older (EDK9.1) TEMAC and GigE switches not
Do you really need u-boot??
I'm using an ML403 without u-boot. I've generated my .ace file with the
zImage.elf directly and it works fine.
If there is a choice of u-boot or not, why choose u-boot?
RJW.
On Sat, 2008-01-26 at 23:10 -0800, Yedu Jathavedan wrote:
Hi,
I have downloaded
the net for an
u-boot ace file that could run on ML403 found it at
http://88.191.24.164/docenligne/projets/samba/2006/linux-embarque-sur-ml-403/u-boot-ml403.ace/view
I copied this ace file (u-boot-ml403.ace) along with the kernel 2.6 image
(uImage) onto my CF card booted the board. After loading
Looking at your bootlog, it doesn't look like you've got the systemace
driver built into the kernel.
Grant,
Yes, the systemace was not built into the kernel. It is successfully
booting the kernel now.
Trying to bring up the Ethernet interface. Any pointers?
Thank you,
Yedu
#$
-
PROBLEM -
2) Since generating ace files failed, I tried to search the net for an
u-boot ace file that could run on ML403 found it atÂ
http://88.191.24.164/docenligne/projets/samba/2006/linux-embarque-sur-ml-403/u-boot-ml403.ace/view
I copied this ace file (u-boot-ml403.ace
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-embedded@ozlabs.org
in u-boot.
I was not able to find the project which you have mentioned there:
git://git.secretlab.ca/git/u-boot.git
This what interests me in particular concerning u-boot is the uart lite
and temac interfaces from ml403.
Thank you very much in advance for any hint
Best Regards
Mirek
)
Second question:
In addition I wanted to ask you about u-boot tree which you have mentioned
in the post on u-boot mailing list. This post was about uart lite for
ml403 in u-boot.
I was not able to find the project which you have mentioned there:
git://git.secretlab.ca/git/u-boot.git
That's
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 some more
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 =
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
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
jtag
but it hangs when started from u-boot.
Is it any fundamental problem with running Linux from u-boot on ML403
(Virtex-4) boards?
Best Regards
Mirek
___
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo
zImage.elf straight from jtag
but it hangs when started from u-boot.
Is it any fundamental problem with running Linux from u-boot on ML403
(Virtex-4) boards?
No there isn't. It should work. Most likely the kernel did not hang
immediately, but rather the console is not setup correctly. You
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 still
=virtex4-mirek:eth0:dhcp panic=1
Uncompressing Linux...
After that system just hangs.
I do not understand why it is possible to run zImage.elf straight from jtag
but it hangs when started from u-boot.
Is it any fundamental problem with running Linux from u-boot on ML403
(Virtex-4
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.
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)
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 303030305[0.00
0020f0d4: 5d204c69 6e757820 76657273 696f6e20] Linux version
0020f0e4: 322e362e 32312d72 63362028 726f6f74
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 303030305[0.00
0020f0d4: 5d204c69 6e757820 76657273 696f6e20] Linux version
0020f0e4: 322e362e 32312d72
/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-boot-from-u-boot
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:
Entry
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
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 irrelevant
Ming Liu wrote:
Dear Frank,
I know you are using U-boot on ML403 now. So can you say something
about how to configure U-boot as ML403 board? I noticed that in U-boot
1.1.4, there is only ML300 supported. So if I want to configure the
board as ML403 and some other customed options(e.g
Ming Liu wrote:
Dear Frank,
So you mean, you built your ML403 system with U-Boot supported
according to the updated version of xapp542, right? There are NOT some
patches open to everyone to include ML403 support into the U-Boot
tree, right?
If both answers for the two questions are yes
on ML403
Date: Fri, 11 Aug 2006 11:39:59 -0400
Ming Liu wrote:
Dear Frank,
So you mean, you built your ML403 system with U-Boot supported
according to the updated version of xapp542, right? There are NOT some
patches open to everyone to include ML403 support into the U-Boot
tree, right
Dear Frank,
I know you are using U-boot on ML403 now. So can you say something about
how to configure U-boot as ML403 board? I noticed that in U-boot 1.1.4,
there is only ML300 supported. So if I want to configure the board as ML403
and some other customed options(e.g. no EEPROM), what shall I
30 matches
Mail list logo
