RE: [microblaze-uclinux] xmdstub

[Wade.Maxfield@xxxxxxxxxxxxxxx]

Hello Wade,
| From: owner-microblaze-uclinux@xxxxxxxxxxxxxx
| [mailto:owner-microblaze-uclinux@xxxxxxxxxxxxxx] On Behalf Of
| Wade.Maxfield@xxxxxxxxxxxxxxx

|   Using the gui, I did indeed mark it to init the BRAM using xmdstub.

|   However, the files don't exist to generate xmdstub.elf.

>This is weird.  It should copy the files over from the installation
>automagically. Do you have an xmdstub peripheral assigned (like Rod
>mentioned)? This is under
>   Software >> Software Platform Settings...
>in the Processor Parameters area.  This should be set to your debug
module.

  OK. I had to assign a driver to the MDM in the Menu Software->Software
Platform Settings, "Software Platform" selection on left, click on "Current
Value" column by xmdstub_peripheral after installing it and it then built.


  After  futzing around it appears that xmdstub does not work over the JTAG
port when you choose "stub".  However, if you don't use xmdstub (unmark it
so it does not "INITIALIZE BRAM") and then use the Debug->XMD Debug Options
and set it to "Hardware", then the debugger works.  If you've futzed around
and had a few failures with xps, be sure to reboot your machine, as some
tasks may be lying around in a bad state.

  After this, you can then launch the debugger server Debug->Launch XMD.
After this, you can then choose Debug->Launch Software Debugger, and get a
debug session.

   This session almost works.  Once you have  interrupts enabled, it will
give you an '0x10 <_vector interrupt>' error and stop the debug session. It
is difficult to recover from this position.

   If you aren't careful, and you start a second "Launch XMD" session, you
may have to use the windows Task Manager to kill xmd.exe to get your system
back to debug status again.

   I think I remember reading something about 0x10 <_vector interrupt> in
the past.  I'll check it out.

   Thanks for your help!

wade


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