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

[microblaze-uclinux] TR: TR: A reference design for S3E500 Rev D boards



Hi moise,
 
So your board is OK, great.
 
Just copy the EDK project in the Hardware/user platform directory of petalinux tree (I use CentOS3 VMWare platform from Xilinx).
Then use petalinux-new-platform
Go Software/uclinux dist
make menuconfig -> choose your platform
go back Hardware/user platform/your platform directory
use petalinux-copy-autoconfig
Go Software/uclinux dist
make menuconfig-> configure kernel settings.
make dep all
 
This steps are detailed in Petalogix tutorials about adding new platforms.
 
that works for me to build the 2.4 kernel image I send with the modified reference design for S3E500RevD board.
 
I don't know how to manage correctly with 2.6 kernel with EDK9.1SP2, but I won't spend too much time on that for the moment, it's perhaps better to wait for a reference design for 2.6 kernel supporting EDK9.2.
 
FS-Boot and U-boot worked well as far I remember, but I don't use them in courses this your. Students just use XMD.
 
For your DCE and DTE problem, I don't know, ask on the mailing list, I already read something about that.
 
I am sorry I have no web page, I encourage you to read intensively Petalogix tutorial pages.
 
Best regards,
 
Frederic


De : moises j. cabrera [mailto:mojuca1808@xxxxxxxxxxxx]
Envoyé : mercredi 7 novembre 2007 19:26
À : LEGER
Objet : Re: TR: A reference design for S3E500 Rev D boards

hi LEGER, thanks for your files
 
they works perfectly, but i want really to do all for my self, since build my hardware platform to buil my kernel image and download it to my board, please help me.
 
i have some other doubts, and some other things that i need your help:
 
-- the kernel image that you send me is 2.4 version, have you probed configure and download a 2.6 kernel image??
 
-- i dont know how configure my hardware platform, because i set up the steps in this page: http://developer.petalogix.com/wiki/BoardGuides/Custom/Tutorial in section "create hardware design", but i dont know if this hardware platform is allright for SPartan 3E 500 rev.D platform?? Can you please send me the steps to build your hardware platform??
 
-- i always see that when use the Spartan 3E 500 board, they use DTE serial port, but can i use DCE port??, or have implemented both and use one of them??, i want to do a hardwae platform that has DTE and DCE ports implemented in my hardware platform, and one of them i will use to uClinux (to view my uClinux terminal window in the hyperterminal), and the other one serial port i want to use it to send/receive data to a robot, it is posible??
 
-- if you have worked with 2.6 kernel images, can you please send me the kernel settings that you put when configured your kernel (also for 2.4 kernel) ??, i really want to create my own kernel image and download it to my board and that it works fine
 
-- have you tried use the FS-boot and U-boot tools to work with download kernel images (without using XMD)?? they works well??
 
-- do you have a tutorial in your web page or something like that to work with petalinux??,  i heard that you are a teacher and have some students group working in this issue, it would be great that you have some webpage with stuff related to this topic.
 
thanks for your attention and help. i really appreciate it
Best Regards
 


LEGER <frederic.leger@xxxxxxxxxxxxxx> escribió:
Hi Moise,

This is a copy of what I sent to petalogix last week.

Tell me if it works yourside.

Regards,

Frédéric LEGER
Transfert de Technologie
ESISAR - INPG
50 rue Barthélémy de Laffemas
BP54 - 26902 Valence Cedex 9
Tel: +33(0)475759475
Fax: +33(0)475435642
web: http://www.esisar.inpg.fr



-----Message d'origine-----
De : LEGER [mailto:frederic.leger@xxxxxxxxxxxxxx]
Envoyé : mercredi 31 octobre 2007 19:01
À : 'John Williams'
Objet : A reference design for S3E500 Rev D boards

Hello John,

I know it is time for EDK9.2, anyway I modified your reference design for
RevD board under EDK9.1 SP2 ISE9.1 SP3

I didn't see any reference design for this board comming from your side, so
perhaps it will help you to create one.

What I modified:

1) Assigned DCM2_LOCK to reset input of proc_sys_reset, instead of
DCM0_LOCK. (system in reset until all DCM locked)
2) All BUFG suppressed on DCM1 and DCM2. (placement problem otherwise,
checked with floorplanner)

3) Constraints added to UCF file: (i don't know if it is usefull, read on
forums...) NET fpga_0_DDR_SDRAM_32Mx16_DDR_DQ_pin<*> NODELAY; NET
fpga_0_DDR_SDRAM_32Mx16_DDR_DQS_pin<*> NODELAY;

5) BSB Wizard for Rev D added these lines also, I pasted to you UCF.
Net fpga_0_DDR_CLK_FB TNM_NET = fpga_0_DDR_CLK_FB; TIMESPEC
TS_fpga_0_DDR_CLK_FB = PERIOD fpga_0_DDR_CLK_FB 10000 ps;

6)SDRAM maps 0x44000000, FLASH 0x43000000, MHS and UCF partly replaced by
output of RevD EDK BSB wizard

4)TestApp_Memory covers all the 64MB.

Below is a log of the messages of the TestApp_Memory and PetaLinux2.4
(image.bin compiled for another design very close but slight differences.
Method used: dow -data image.bin 0x44000000 con 0x44000000, flash contains
still Xilinx demo)

Now, it's OK for RevD boards & Petalinux in course :-) I have 10 students
next month to play with the boards. Time to write some slides.

Best regards,

Frédéric LEGER
Transfert de Technologie
ESISAR - INPG
50 rue Barthélémy de Laffemas
BP54 - 26902 Valence Cedex 9
Tel: +33(0)475759475
Fax: +33(0)475435642
web: http://www.esisar.inpg.fr


-- Entering main() --
Starting MemoryTest for DDR_SDRAM_32Mx16:
Running 32-bit test...PASSED!
Running 16-bit test...PASSED!
Running 8-bit test...PASSED!
-- Exiting main() --
Linux version 2.4.32-uc0 (devel@localhost) (gcc version 3.4.1 ( PetaLinux
0.20 Build -rc1 050607 )) #7 Fri Sep 21 15:49:57 EDT 2007 On node 0
totalpages: 16384
zone(0): 16384 pages.
zone(1): 0 pages.
zone(2): 0 pages.
CPU: MICROBLAZE
Kernel command line: G×ÝpD?Console: xmbserial on UARTLite
Calibrating delay loop... 24.83 BogoMIPS
Memory: 64MB = 64MB total
Memory: 62628KB available (1055K code, 1137K data, 44K init) Dentry cache
hash table entries: 8192 (order: 4, 65536 bytes) Inode cache hash table
entries: 4096 (order: 3, 32768 bytes) Mount cache hash table entries: 512
(order: 0, 4096 bytes) Buffer cache hash table entries: 4096 (order: 2,
16384 bytes) Page-cache hash table entries: 16384 (order: 4, 65536 bytes)
POSIX conformance testing by UNIFIX Linux NET4.0 for Linux 2.4 Based upon
Swansea University Computer Society NET3.039 Initializing RT netlink socket
Microblaze UARTlite serial driver version 1.00 ttyS0 at 0x40600000 (irq = 2)
is a Microblaze UARTlite Starting kswapd xgpio #0 at 0x40000000 mapped to
0x40000000 Xilinx GPIO registered RAMDISK driver initialized: 16 RAM disks
of 4096K size 1024 blocksize
eth0: using fifo mode.
eth0: No PHY detected. Assuming a PHY at address 0.
eth0: Xilinx EMACLite #0 at 0x40E00000 mapped to 0x40E00000, irq=1
physmap_auto flash device: 1000000 at 43000000 physmap_auto probing buswidth
1
cfi_cmdset_0001: Erase suspend on write enabled
0: offset=0x0,size=0x20000,blocks=128
Using buffer write method
physmap_auto: no partition info available, registering whole flash at once
uclinux[mtd]: RAM probe address=0x441460ec size=0xde000
uclinux[mtd]: root filesystem index=2
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 4096 bind 8192)
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
VFS: Mounted root (cramfs filesystem) readonly.
Freeing init memory: 44K
Mounting proc:
Mounting var:
Populating /var:
Running local start scripts.
Mounting /etc/config:
Populating /etc/config:
flatfsd: Nonexistent or bad flatfs (-48), creating new one...
flatfsd: Failed to write flatfs (-48): No such device
flatfsd: Created 5 configuration files (185 bytes) Setting hostname:
Setting up interface lo:
Setting up interface eth0:
Starting thttpd:

uclinux login: root
Password:
# dhcpcd &
42
# ifconfig
eth0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
inet addr:172.20.4.34 Bcast:172.20.7.255 Mask:255.255.252.0
UP BROADCAST NOTRAILERS RUNNING MTU:1500 Metric:1
RX packets:4 errors:0 dropped:0 overruns:0 frame:0
TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
Interrupt:1

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0

#
#
# ping
usage: ping [-LRdfnqrva] [-c count] [-i wait] [-l preload]
[-p pattern] [-s packetsize] [-t ttl] [-I interface or IP address]
host # # ping 172.20.4.51 PING 172.20.4.51 (172.20.4.51): 56 data bytes
64 bytes from 172.20.4.51: icmp_seq=0 ttl=64 time=1.5 ms
64 bytes from 172.20.4.51: icmp_seq=1 ttl=64 time=1.2 ms
64 bytes from 172.20.4.51: icmp_seq=2 ttl=64 time=1.2 ms
64 bytes from 172.20.4.51: icmp_seq=3 ttl=64 time=1.2 ms
64 bytes from 172.20.4.51: icmp_seq=4 ttl=64 time=1.2 ms
64 bytes from 172.20.4.51: icmp_seq=5 ttl=64 time=1.2 ms
64 bytes from 172.20.4.51: icmp_seq=6 ttl=64 time=1.2 ms
64 bytes from 172.20.4.51: icmp_seq=7 ttl=64 time=1.2 ms
64 bytes from 172.20.4.51: icmp_seq=8 ttl=64 time=1.2 ms
64 bytes from 172.20.4.51: icmp_seq=9 ttl=64 time=1.2 ms
64 bytes from 172.20.4.51: icmp_seq=10 ttl=64 time=1.2 ms
64 bytes from 172.20.4.51: icmp_seq=11 ttl=64 time=1.2 ms
64 bytes from 172.20.4.51: icmp_seq=12 ttl=64 time=1.2 ms
64 bytes from 172.20.4.51: icmp_seq=13 ttl=64 time=1.2 ms
64 bytes from 172.20.4.51: icmp_seq=14 ttl=64 time=1.2 ms
64 bytes from 172.20.4.51: icmp_seq=15 ttl=64 time=1.2 ms
64 bytes from 172.20.4.51: icmp_seq=16 ttl=64 time=1.2 ms
64 bytes from 172.20.4.51: icmp_seq=17 ttl=64 time=1.2 ms
64 bytes from 172.20.4.51: icmp_seq=18 ttl=64 time=1.2 ms
64 bytes from 172.20.4.51: icmp_seq=19 ttl=64 time=1.2 ms
64 bytes from 172.20.4.51: icmp_seq=20 ttl=64 time=1.2 ms
64 bytes from 172.20.4.51: icmp_seq=21 ttl=64 time=1.2 ms
64 bytes from 172.20.4.51: icmp_seq=22 ttl=64 time=1.2 ms
64 bytes from 172.20.4.51: icmp_seq=23 ttl=64 time=1.2 ms
64 bytes from 172.20.4.51: icmp_seq=24 ttl=64 time=1.2 ms
64 bytes from 172.20.4.51: icmp_seq=25 ttl=64 time=1.2 ms
64 bytes from 172.20.4.51: icmp_seq=26 ttl=64 time=1.2 ms
64 bytes from 172.20.4.51: icmp_seq=27 ttl=64 time=1.2 ms
64 bytes from 172.20.4.51: icmp_seq=28 ttl=64 time=1.2 ms
64 bytes from 172.20.4.51: icmp_seq=29 ttl=64 time=1.2 ms
64 bytes from 172.20.4.51: icmp_seq=30 ttl=64 time=1.2 ms
64 bytes from 172.20.4.51: icmp_seq=31 ttl=64 time=1.2 ms
64 bytes from 172.20.4.51: icmp_seq=32 ttl=64 time=1.2 ms
64 bytes from 172.20.4.51: icmp_seq=33 ttl=64 time=1.2 ms
64 bytes from 172.20.4.51: icmp_seq=34 ttl=64 time=1.2 ms
64 bytes from 172.20.4.51: icmp_seq=35 ttl=64 time=1.2 ms
64 bytes from 172.20.4.51: icmp_seq=36 ttl=64 time=1.2 ms
64 bytes from 172.20.4.51: icmp_seq=37 ttl=64 time=1.2 ms
64 bytes from 172.20.4.51: icmp_seq=38 ttl=64 time=1.2 ms

--- 172.20.4.51 ping statistics ---
39 packets transmitted, 39 packets received, 0% packet loss round-trip
min/avg/max = 1.2/1.2/1.5 ms # #




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