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

[microblaze-uclinux] Trying to start kernel image



Hi every body,

I'm working in a mblaze-uclinux project with a ML402 board. I'm using EDK 8.1.02.

I make my mblaze project using XAPP730 manual of xilinx and, when I finish my Memory Test is OK.

The problem appears when I download the kernel image:

- Using "dow -data image.bin 0x24000000" and the "con 0x24000000" nothing appears on Hyperterminal. It's blank.

- Using dl.sh script I get this window on XMD:

$ ./dl.sh image.bin
Memory address Found
Memory Address is 0x24000000
Kimage is image.bin
Kparams are
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% 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
  (0x24000000-0x27ffffff) DDR_SDRAM_64Mx32      mb_opb
  (0x24000000-0x27ffffff) DDR_SDRAM_64Mx32      ixcl
  (0x24000000-0x27ffffff) DDR_SDRAM_64Mx32      dxcl
  (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% 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.
 ECP hardware is detected.
Cable connection established.
Connecting to cable (Parallel Port - LPT1) in ECP mode.
Checking cable driver.
 Driver xpc4drvr.sys version = 1.0.4.0. LPT base address = 0378h.
 Cable Type = 1, Revision = 3.
 Setting cable speed to 5 MHz.
Cable connection established.

JTAG chain configuration
--------------------------------------------------
Device   ID Code        IR Length    Part Name
 1       0a001093           8        System_ACE
 2       05059093          16        XCF32P
 3       02088093          10        XC4VSX35
 4       09608093           8        xc95144xl
Assuming, Device No: 3 contains the MicroBlaze system
WARNING:MDT - MDM Peripheral Not Detected on Hardware
WARNING:MDT - Assuming opb_jtag_uart peripheral
Connected to the JTAG MicroProcessor Debug Module (MDM)
No of processors = 1

UNKNOWN Processor Version (0)
        Verify if FPGA Bitstream was downloaded and DONE pin went High

XMD% Downloading kernel image...
XMD% This will only take a few seconds!
XMD%
No target with id: -1. Use command "targets" to get target list
Error: Invalid xmd target: -1
Use "targets" command to get current list of targets or change target
Use "connect mb" command to connect to a MicroBlaze target
Use "connect ppc" command to connect to a PowerPC target
XMD% setting kernel command line
XMD%
XMD% "cmdline is  "
XMD% 2
XMD% 0x100
XMD% > > > >
No target with id: -1. Use command "targets" to get target list
Error: Invalid xmd target: -1
Use "targets" command to get current list of targets or change target
Use "connect mb" command to connect to a MicroBlaze target
Use "connect ppc" command to connect to a PowerPC target
XMD%
No target with id: -1. Use command "targets" to get target list
Error: Invalid xmd target: -1
Use "targets" command to get current list of targets or change target
Use "connect mb" command to connect to a MicroBlaze target
Use "connect ppc" command to connect to a PowerPC target
XMD%
No target with id: -1. Use command "targets" to get target list
Error: Invalid xmd target: -1
Use "targets" command to get current list of targets or change target
Use "connect mb" command to connect to a MicroBlaze target
Use "connect ppc" command to connect to a PowerPC target
XMD%
No target with id: -1. Use command "targets" to get target list
Error: Invalid xmd target: -1
Use "targets" command to get current list of targets or change target
Use "connect mb" command to connect to a MicroBlaze target
Use "connect ppc" command to connect to a PowerPC target
XMD%
No target with id: -1. Use command "targets" to get target list
Error: Invalid xmd target: -1
Use "targets" command to get current list of targets or change target
Use "connect mb" command to connect to a MicroBlaze target
Use "connect ppc" command to connect to a PowerPC target
XMD% Done already WOW!
XMD%

I detected the problem is in the script at this line: "connect mb mdm -bscan USER1". Using this command i get this:

Assuming, Device No: 3 contains the MicroBlaze system
WARNING:MDT - MDM Peripheral Not Detected on Hardware
WARNING:MDT - Assuming opb_jtag_uart peripheral
Connected to the JTAG MicroProcessor Debug Module (MDM)
No of processors = 1

UNKNOWN Processor Version (0)
        Verify if FPGA Bitstream was downloaded and DONE pin went High

Then I decided to change this line for "connect mb mdm" resulting:

$ ./dl.sh image.bin
Memory address Found
Memory Address is 0x24000000
Kimage is image.bin
Kparams are
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% 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
  (0x24000000-0x27ffffff) DDR_SDRAM_64Mx32      mb_opb
  (0x24000000-0x27ffffff) DDR_SDRAM_64Mx32      ixcl
  (0x24000000-0x27ffffff) DDR_SDRAM_64Mx32      dxcl
  (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% 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.
 ECP hardware is detected.
Cable connection established.
Connecting to cable (Parallel Port - LPT1) in ECP mode.
Checking cable driver.
 Driver xpc4drvr.sys version = 1.0.4.0. LPT base address = 0378h.
 Cable Type = 1, Revision = 3.
 Setting cable speed to 5 MHz.
Cable connection established.

JTAG chain configuration
--------------------------------------------------
Device   ID Code        IR Length    Part Name
 1       0a001093           8        System_ACE
 2       05059093          16        XCF32P
 3       02088093          10        XC4VSX35
 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.................on
FSL ICache Support.................on
Hard Divider Support...............on
Hard Multiplier Support............on
Barrel Shifter Support.............on
MSR clr/set Instruction Support....off
Compare Instruction Support........off
Number of FSL ports..............1
MBsfsl(0)-MDMmfsl(0) Connected..........Yes
JTAG MDM Connected to MicroBlaze 1

Unable to open GDB Server at port: 1234
Connected to "mb" target. id = 0
Starting GDB server for "mb" target (id = 0) at TCP port no 1235
XMD% Downloading kernel image...
XMD% This will only take a few seconds!
XMD% XMD% setting kernel command line
XMD%
XMD% "cmdline is  "
XMD% 2
XMD% 0x100
XMD% > > > > XMD% XMD% XMD% XMD% Processor started. Type "stop" to stop processo
r
RUNNING> Done already WOW!
RUNNING> Closing MDM communication with Processor 1

But the hyperterminal follows blank.

I don't know where is the problem and it's becoming me crazy... Please couuld any one help me?

Attached you'll find my system.mhs file.

Thank you very much.
Kind Regards,
Raúl Rodríguez

Attachment: system.mhs
Description: Binary data