Re: [microblaze-uclinux] Jtag Debug

[Paul Hartke <phartke@xxxxxxxxxxxx>]

How do you know it runs "slow"--that's really a value judgement?  What makes
you think it should run faster--or even slower for that matter?  The design
appears to be created by Base System Builder which lots of folks have used
on ml401.

Paul

Quoting Abot Botbot <dejanigma@xxxxxxxxxxx>:
> Hey Friends,
>
>    This might be considered off topic, but I think I'm missing a
> fundamantal
> explanation for the performance that I get. Here's my basic design flow,
> which doesn't use uCLinux yet, I was just trying to verify that the DSP
> functionality I want is possible on the microblaze... I download the XMD
> stub to the board, then run "dow executable.elf" from XMD and type
> "run"...
> This sets my code in motion, but it seems to be going extremely slow.
> It's
> running entirely out of SRAM, but that shouldn't be the only factor in
> the
> performance I'm seeing... I'm wondering if my whole system is running
> over
> the JTAG clock and putting out debug symbols to the PC, even though I'm
> not
> observing them, and I took the -g option out of the compiler flags.. So
> two
> questions... Am I running in some debug mode where it is running much
> slower
> than it could be... How do I get the hardware to run independantly, if it
> is
> in some debug mode.. After I finish a few things for my graduate classes
> (mid terms, blech!) I will get back on the uCLinux train and get that
> running on my ML401 board. Thanks for any help you can give! I'll attatch
> some files in case anyone thinks looking at them will help them to
> understand.
>
> Thanks,
> Andy
>
___________________________
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/