[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [microblaze-uclinux] Microblaze4 slow kernel download with XMD
Aloha,
It seems you have a problem with the cable or printer port.
| From: owner-microblaze-uclinux@xxxxxxxxxxxxxx
| [mailto:owner-microblaze-uclinux@xxxxxxxxxxxxxx] On Behalf Of
| Claudio Lanconelli
| I use dl.sh script for download, and xilinx parallel cable IV in
| compatibility mode (cable III mode) in Linux.
Why compatibility mode? Did it use to work in fast mode?
| The download time was 1min with Mb3 design versus 4min with
| Mb4 design!
You are working at 200kHz in compatibility mode vs 5MHz in PCIV fast mode.
It should take longer.
...
| Reusing 780200E4 key.
| Reusing FC0200E4 key.
| Connecting to cable (Parallel Port - parport0).
| WinDriver v7.01 Jungo (c) 1997 - 2005 Build Date: Aug 10
| 2005 X86 32bit
| 16:24:42.
| parport0: baseAddress=0x378, ecpAddress=0x778
| LPT base address = 0378h.
| ECP base address = 0778h.
| ECP hardware is detected.
| Cable connection established.
| Connecting to cable (Parallel Port - parport0) in ECP mode.
| WARNING:iMPACT - Module xpc4drvr is not loaded. Please
| reinstall the cable
| drivers. See Answer Record 18612.
| Cable connection failed.
Above it seems it finds ECP hardware, but the driver is AWOL
| Connecting to cable (Parallel Port - parport0).
| WinDriver v7.01 Jungo (c) 1997 - 2005 Build Date: Aug 10
| 2005 X86 32bit
| 16:24:42.
| LPT base address = 0378h.
| ECP base address = 0778h.
| Cable connection established.
| ECP port test failed. Using download cable in compatibility mode.
Here it doesn't find the ECP hardware. Something is strange with the
hardware or a bug in the impact software.
Sorry I can't tell you exactly what you need to fix it, but those are the
clues I see.
./ks
___________________________
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/