RE: [microblaze-uclinux] xmdstub

[Wade.Maxfield@xxxxxxxxxxxxxxx]

  Thanks!  MDM module was the key I was missing.  The hardware engineer had
removed it without letting me know, and I didn't know the two items were
related.

wade




I don't use xmdstub to do debugging.  I do use xmd (running on the
development PC) and it connects to the FPGA and microblaze via the
Xilinx JTAG cable and the MDM module.  You need to instantiate and hook
up the MDM module to your microblaze module in XPS.  See the XMD chapter
in the Embedded Systems Tool Guide.  You can then use XMD to communicate
with the microblaze like a normal on-chip debugger/monitor - downloading
and executing microblaze .elf files, looking at and modifying memory or
registers, etc.

However, if I look around for xmdstub (in my 6.3 version of Xilinx
software), I see that in XPS, with your project open, if you right-click
on your microblaze module in the system window, you see a popup window.
Select S/W Settings..., then click the "Processor, Driver Parameters
..." tab.  You will see an entry for xmbstub_peripheral, then can select
a uart.  Have you done this? I wonder if you don't, if xmbstub is not
generated for you when you generate your project(?)  You do know that
you probably have go through the "generate netlist", "generate
bitstream", "update libraries and BSPs" steps to get xmbstub generated
for you, right?  Just some thoughts.

Rod Campbell

On Thu, 2006-06-01 at 16:57, Wade.Maxfield@xxxxxxxxxxxxxxx wrote:
> Hi Kevin,
>
>   I've made some progress and had some more failures, under the Xilinx
8.1
> EDK toolset.
>
>   Using the gui, I did indeed mark it to init the BRAM using xmdstub.
>
>   However, the files don't exist to generate xmdstub.elf.
>
>   I found some of the xmdstub source  files in a ZIP file included in the
> Xilinx documentation, so I put them in the microblaze_0/code directory.
>
>   That worked, and the project compiled and built the stub and downloaded
> it to the target.  But that is not the end of the story.
>
>    The XMD debug options via the gui only let me choose Simulator, not
> Stub, so that is totally useless.  Is there a way to configure the
debugger
> using a command line to force it to use the stub?  I've not yet gotten
that
> far, as the next thing that happened to me was very frustrating.
>
>     When I went back to my software project and marked it to initialize
the
> BRAM instead of xmdstub, the EDK deleted the contents of the
> microblaze_0/code directory for me!!!!!!    Therefore I can't get back to
> the xmdstub (which I can't select in the gui) unless I pull those files
> back out of the EDK example zip file and drop them in the directory.
>
>     You'll have to forgive my lack of understanding. A hardware engineer
> gave me this project to write code to, and I'm just now learning the
Xilinx
> EDK, as is he. Has anyone solved this same type of issue with 8.1 or in
> general?  I haven't found references to this in google search of the
> microblaze-uclinux list or a search the Xilinx site, or in the Xilinx
> documentation I've searched.
>
> thanks,
> wade
>
>
>
>
> Hello Wade,
>
> | From: owner-microblaze-uclinux@xxxxxxxxxxxxxx
> | [mailto:owner-microblaze-uclinux@xxxxxxxxxxxxxx] On Behalf Of
> | Wade.Maxfield@xxxxxxxxxxxxxxx
>
> | Hi,
> |
> |    I'm trying to download xmdstub.elf to a xilinx target so I
> | can debug
> | some bitram resident bootstrap code which will program my microblaze
> | uCLinux into flash on a custom target.
>
> How are you trying to do this?  At a command line or from the GUI.  I
> believe the xmdstub.elf file can only downloaded as part of the
> configuration bitstream and as such it has to be marked for initialize
> bitstream in the applications area.  Please correct me if I'm wrong.
>
> |    unfortunately, the Xilinx Platform studio says that it
> | can't make the
> | target xmdstub.elf due to "no rule".  the microblaze_0/code/
> | directory is
> | totally empty.
>
> The "no rule" sounds like you don't have the xmdstub marked to init the
> bram.
>
> Sorry I'm not much help here.  I don't quite understand what you're doing
> to
> get where you are.
>
> ./ks
>
>
>
>
> ***CONFIDENTIALITY NOTICE***
> This communication (and any attachment) is confidential. It should only
be
> read by the person(s) to whom
> it is addressed.  If you have received this communication in error,
please
> notify the sender by reply and delete this communication.
> *****************************************
>
> ___________________________
> 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/



***CONFIDENTIALITY NOTICE***
This communication (and any attachment) is confidential. It should only be
read by the person(s) to whom
it is addressed.  If you have received this communication in error, please
notify the sender by reply and delete this communication.
*****************************************

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