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

RE: [microblaze-uclinux] PetaLinux on ML505

To: <microblaze-uclinux@xxxxxxxxxxxxxx>
Subject: RE: [microblaze-uclinux] PetaLinux on ML505
From: "John Mcgrath" <john.mcgrath@xxxxxxxxxx>
Date: Mon, 16 Jul 2007 13:59:32 +0100
In-reply-to: <B696AA1A36D0F24EAD0096987D276AF3021D3008@xxxxxxxxxxxxxxxx>
References: <B696AA1A36D0F24EAD0096987D276AF3021D3008@xxxxxxxxxxxxxxxx>
Reply-to: microblaze-uclinux@xxxxxxxxxxxxxx
Sender: owner-microblaze-uclinux@xxxxxxxxxxxxxx
Thread-index: AcfDnytwsS502IG3QjO/sjikyfblAgBhTmlAAJOWyYAAAAQ5wAANktdQ
Thread-topic: [microblaze-uclinux] PetaLinux on ML505

Hi Gerd,
Thanks a lot - I will try it!

Cheers
John

-----Original Message-----
From: owner-microblaze-uclinux@xxxxxxxxxxxxxx
[mailto:owner-microblaze-uclinux@xxxxxxxxxxxxxx] On Behalf Of Theidel
Gerd
Sent: Monday, July 16, 2007 12:34 AM
To: microblaze-uclinux@xxxxxxxxxxxxxx
Subject: RE: [microblaze-uclinux] PetaLinux on ML505

Hi John,

you can donwload u-boot-1.2.0 from 
ftp://ftp.denx.de/pub/u-boot/
(See http://www.denx.de/wiki/UBoot/SourceCode for more information)
Then just overwrtite 
petalinux-v0.20-rc3/software/petalinux-dist/u-boot/drivers/cfi_flash.c
and
petalinux-v0.20-rc3/software/petalinux-dist/u-boot/include/flash.h
in the petalinux source tree with the corresponding files from the
u-boot-1.2.0 distribution.
In the file cfi_flash.c  you have to add the global variable
monitor_flash_len and initialize it(e.g. somewhere araound line 202):

ulong monitor_flash_len = CFG_MONITOR_LEN;

Hope that helps...

Cheers
Gerd


-----Original Message-----
From: owner-microblaze-uclinux@xxxxxxxxxxxxxx
[mailto:owner-microblaze-uclinux@xxxxxxxxxxxxxx] On Behalf Of John
Mcgrath
Sent: Freitag, 13. Juli 2007 10:06
To: microblaze-uclinux@xxxxxxxxxxxxxx
Subject: RE: [microblaze-uclinux] PetaLinux on ML505

Hi Gerd,

I might give this a try :)
Can you explain the lines:

Replace the files 
	u-boot/drivers/cfi_flash.c
	u-boot/include/flash.h
   with the versions from u-boot-1.2.0
   and add the global variabel "monitor_flash_len" in cfi_flash.c:
	ulong monitor_flash_len;

Where do I find u-boot-1.2.0, is it somewhere in the petalinux
distribution, or should I download it from the web?

Cheers
John



-----Original Message-----
From: owner-microblaze-uclinux@xxxxxxxxxxxxxx
[mailto:owner-microblaze-uclinux@xxxxxxxxxxxxxx] On Behalf Of Theidel
Gerd
Sent: Wednesday, July 11, 2007 2:38 AM
To: microblaze-uclinux@xxxxxxxxxxxxxx
Subject: [microblaze-uclinux] PetaLinux on ML505


Hi PetaLinux team and users,

I have started working with petalinux-v0.20-rc3.tar.gz on the Xilinx
ML505
evaluation board. 
To get U-Boot working I made these changes:

1) In file u-boot\include\configs\petalogix-microblaze-auto.h
   change 
      #define CFG_MAX_FLASH_SECT	128
   to 
      #define CFG_MAX_FLASH_SECT	264
      #define CFG_FLASH_PROTECTION
   since the Flash on the ML505 has 259 sectors.

2) Replace the files 
	u-boot/drivers/cfi_flash.c
	u-boot/include/flash.h
   with the versions from u-boot-1.2.0
   and add the global variabel "monitor_flash_len" in cfi_flash.c:
	ulong monitor_flash_len;

   without the changes in 2) u-boot first seemed to work but then
   crashed after u-boot was written to flash, the system was restarted
   and "run load_uboot" was executed:
      U-Boot> run load_uboot
      TFTP from server 192.168.0.100; our IP address is 192.168.0.38
      Filename 'u-boot-s.bin'.
      Load address: 0x50000000
      Loading: #########################
      done
      Bytes transferred = 124016 (1e470 hex)
      =================================================
      FS-BOOT First Stage Bootloader (c) 2006 PetaLogix
      =================================================
      FS-BOOT: System initialisation completed.
      FS-BOOT: Booting from FLASH. Press 's' for image download.

   This seems a bit strange for me, because the "run load_uboot" does
   not write anything to flash, just to memory. So I am not really sure
   if that crash is caused by any other problem, but after applying the
   changes 1) and 2) I did not notice any problems at all with u-boot.


After loading Kernel uclinux 2.6.20-uc0 I discovered the following
problems with ping:

# ping 216.239.59.104
PING 216.239.59.104 (216.239.59.104): 56 data bytes
64 bytes from 216.239.59.104: icmp_seq=0 ttl=240 time=32.3 ms
ping: recvfrom: Invalid argument
ping: recvfrom: Invalid argument
64 bytes from 216.239.59.104: icmp_seq=2 ttl=240 time=33.3 ms
64 bytes from 216.239.59.104: icmp_seq=3 ttl=240 time=32.7 ms
64 bytes from 216.239.59.104: icmp_seq=4 ttl=240 time=34.9 ms
64 bytes from 216.239.59.104: icmp_seq=5 ttl=240 time=32.3 ms
ping: recvfrom: Invalid argument
64 bytes from 216.239.59.104: icmp_seq=6 ttl=240 time=34.2 ms
ping: recvfrom: Invalid argument
64 bytes from 216.239.59.104: icmp_seq=7 ttl=240 time=34.0 ms
ping: recvfrom: Invalid argument
64 bytes from 216.239.59.104: icmp_seq=8 ttl=240 time=34.4 ms

--- 216.239.59.104 ping statistics ---
9 packets transmitted, 8 packets received, 11% packet loss round-trip
min/avg/max = 32.3/33.5/34.9 ms # ping 66.98.178.193 PING 66.98.178.193
(66.98.178.193): 56 data bytes
64 bytes from 66.98.178.193: icmp_seq=0 ttl=47 time=143.1 ms
ping: recvfrom: Bad file descriptor
ping: recvfrom: Bad file descriptor
64 bytes from 66.98.178.193: icmp_seq=2 ttl=47 time=140.8 ms
ping: recvfrom: Bad file descriptor
64 bytes from 66.98.178.193: icmp_seq=3 ttl=47 time=142.7 ms
ping: recvfrom: Bad file descriptor
64 bytes from 66.98.178.193: icmp_seq=4 ttl=47 time=140.6 ms
ping: recvfrom: Bad file descriptor
64 bytes from 66.98.178.193: icmp_seq=5 ttl=47 time=142.4 ms

--- 66.98.178.193 ping statistics ---
6 packets transmitted, 5 packets received, 16% packet loss round-trip
min/avg/max = 140.6/141.9/143.1 ms


And sometimes I get this message inside the shell:

BUG: scheduling while atomic: sh/0x00000008/71

Stack:
  57effb74 50010d30 00000000 57c603d8 00000000 50002024 5015ac90
5017d1f8
  00000008 00000047 0f7f4900 00000000 57efe000 00000008 57c603ec
57efffea
  57c60388 00000000 57c603d8 00000000 578fff1c 00000000 00000000
00000000 Call Trace: [<50010d30>] [<50002024>] [<5017d1f8>] [<5017d06c>]


Has anyone an advice regarding the
"ping: recvfrom: Invalid argument",
"ping: recvfrom: Bad file descriptor" and
"BUG: scheduling while atomic" problems ?

Thanks and best regards,
Gerd

__________________________________________________

Gerd Theidel
Laboratory for Particle Physics (LTP)
Electronics and Measuring Systems
 
Paul Scherrer Institute (PSI)
WPDA/9
CH-5232 Villigen PSI
Switzerland
__________________________________________________


___________________________
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/




___________________________
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/


___________________________
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/




___________________________
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/

References:
- RE: [microblaze-uclinux] PetaLinux on ML505
  - From: Theidel Gerd

Prev by Date: [microblaze-uclinux] ### FLE Free Ethernet MAC
Next by Date: Re: [microblaze-uclinux] ### FLE Free Ethernet MAC
Previous by thread: RE: [microblaze-uclinux] PetaLinux on ML505
Next by thread: [microblaze-uclinux] aemb and uclinux on Spartan3E starterkit
Index(es):
- Date
- Thread