[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
AW: AW: [microblaze-uclinux] Download problems (No target with id: -1)
Hello John,
I wonder if the Icache and Dcache starting address is correct:
It is the same base Address and high adress as the DDR-SDRAM:
Instruction Cache Base Address.....0x24000000
Instruction Cache High Address.....0x27ffffff
Data Cache Support.................on
Data Cache Base Address............0x24000000
Data Cache High Address............0x27ffffff
I set Icache and Dcache to 16 kB each, but this
Adress Range is the same for DDRSDRam which is 64 MB large.
And i used this starting Address to download the Image.
Is this OK?
Philipp
-----Ursprüngliche Nachricht-----
Von: owner-microblaze-uclinux@xxxxxxxxxxxxxx [mailto:owner-microblaze-uclinux@xxxxxxxxxxxxxx] Im Auftrag von Schleifer, Philipp, PGR2
Gesendet: Dienstag, 19. September 2006 11:09
An: microblaze-uclinux@xxxxxxxxxxxxxx
Betreff: AW: AW: [microblaze-uclinux] Download problems (No target with id: -1)
Hello John,
When I do it manually, i get following output on UART:
-- Entering main() --
Starting MemoryTest for DDR_SDRAM_64Mx32:
Running 32-bit test...PASSED!
Running 16-bit test...PASSED!
Running 8-bit test...FAILED!
-- Exiting main() --
When i download the Bitstream through XPS, i receive passed for all three tests.
This time, i did not change to initialise the microblaze_0_bootloop, as you said.
Philipp
On the cygwin Console, i received this output:
I142697D@de01002a /cygdrive/d/Programme/Xilinx/workspace/ucLinuxMB2
$ xmd
Xilinx Microprocessor Debug (XMD) Engine Xilinx EDK 8.1.02 Build EDK_I.20.4 Copyright (c) 1995-2005 Xilinx, Inc. All rights reserved.
XMD%
XMD% xload mhs system.mhs
Loading MHS File..
Processor(s) in System ::
Microblaze(1) : microblaze_0
Address Map for Processor microblaze_0
(0x00000000-0x00001fff) dlmb_cntlr dlmb
(0x00000000-0x00001fff) ilmb_cntlr ilmb
(0x22000000-0x227fffff) FLASH_2Mx32 mb_opb
(0x24000000-0x27ffffff) DDR_SDRAM_64Mx32 mb_opb
(0x40600000-0x4060ffff) RS232_Uart mb_opb
(0x41200000-0x4120ffff) opb_intc_0 mb_opb
(0x41400000-0x4140ffff) debug_module mb_opb
(0x41c00000-0x41c0ffff) opb_timer_1 mb_opb
XMD% connect mb mdm
Connecting to cable (Parallel Port - LPT1).
Checking cable driver.
Driver windrvr6.sys version = 7.0.0.0. LPT base address = 0378h.
ECP base address = 0778h.
Cable connection failed.
Connecting to cable (Parallel Port - LPT1).
Checking cable driver.
Driver windrvr6.sys version = 7.0.0.0. LPT base address = 0378h.
ECP base address = 0778h.
Cable connection failed.
Connecting to cable (Parallel Port - LPT2).
Checking cable driver.
Driver windrvr6.sys version = 7.0.0.0.Cable connection failed.
Connecting to cable (Parallel Port - LPT2).
Checking cable driver.
Driver windrvr6.sys version = 7.0.0.0.Cable connection failed.
Connecting to cable (Usb Port - USB22).
Checking cable driver.
Driver xusbdfwu.sys version: 1018 (1021).
Driver windrvr6.sys version = 7.0.0.0.Calling setinterface num=0, alternate=0.
DeviceAttach: received and accepted attach for:
vendor id 0x3fd, product id 0x8, device handle 0x2760038 Max current requested during enumeration is 280 mA.
Cable Type = 3, Revision = 0.
Setting cable speed to 6 MHz.
Cable connection established.
Firmware version = 1021.
CPLD file version = 0006h.
CPLD version = 0012h.
JTAG chain configuration
--------------------------------------------------
Device ID Code IR Length Part Name
1 0a001093 8 System_ACE
2 05059093 16 XCF32P
3 01e58093 10 XC4VFX12
4 09608093 8 xc95144xl
Assuming, Device No: 3 contains the MicroBlaze system Connected to the JTAG MicroProcessor Debug Module (MDM) No of processors = 1
MicroBlaze Processor 1 Configuration :
-------------------------------------
Version............................4.00.a
No of PC Breakpoints...............2
No of Read Addr/Data Watchpoints...0
No of Write Addr/Data Watchpoints..0
Instruction Cache Support..........on
Instruction Cache Base Address.....0x24000000
Instruction Cache High Address.....0x27ffffff
Data Cache Support.................on
Data Cache Base Address............0x24000000
Data Cache High Address............0x27ffffff
Exceptions Support................off
FPU Support.......................off
FSL DCache Support.................off
FSL ICache Support.................off
Hard Divider Support...............off
Hard Multiplier Support............on
Barrel Shifter Support.............off
MSR clr/set Instruction Support....off
Compare Instruction Support........off
Number of FSL ports..............1 JTAG
MDM Connected to MicroBlaze 1 Connected to "mb" target. id = 0 Starting GDB server for "mb" target (id = 0) at TCP port no 1234
XMD% dow -data binary/image.bin 0x24000000
XMD% con 0x24000000
Processor started. Type "stop" to stop processor
RUNNING>
-----Ursprüngliche Nachricht-----
Von: owner-microblaze-uclinux@xxxxxxxxxxxxxx [mailto:owner-microblaze-uclinux@xxxxxxxxxxxxxx] Im Auftrag von John Williams
Gesendet: Dienstag, 19. September 2006 00:14
An: microblaze-uclinux@xxxxxxxxxxxxxx
Betreff: Re: AW: [microblaze-uclinux] Download problems (No target with id: -1)
Hi Phillip,
Schleifer, Philipp, PGR2 wrote:
> i think, i have solved this issue. i added an environment variable
> target=microblaze Now, the download succeeds, but the linux-kernel is
> not booting.
>
> the memory-test runs fine, then i marked microblaze_0_bootloop to be
> initialized in BRAM and deactivated the Test-Applications. Then i
> downloaded the design to the board.
>
> after that, i used the dl.sh script to download the image to the memory.
> It worked, but
> there is nothing on the console on UART.
It looks like XMD is not properly connecting to the microblaze.
Instead of using the dl.sh script, try doing it manually, to see what part of the process is failing. Here are the commands you need (remember to remove/rename any file called xmd.ini from the project directory, it contains default XMD commands, which you don't want right now).
xmd
% xload mhs system.mhs
% connect mb mdm
% dow -data /path/to/image.bin 0xdeadbeef % con 0xdeadbeef
(replace 0xdeadbeef with the start addres of your DDR/external memory)
error messages at any stage in this process should alert you to where the problem is.
You don't need a bootlaoder when doing a JTAG boot like this.
Regards,
John
___________________________
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/