• Locked Locked
  • Replies 5 replies
  • Subscribers 119 subscribers
  • Views 4225 views
  • Users 0 members are here
Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Dstream probe questions

nicolas vassal
Note: This was originally posted on 4th March 2013 at http://forums.arm.com

Hello,
I just received a Dstream probe to do trace on an Omap 3530 (CortexA8) processor.
I started to setup the device but I have the following issues:

[1] I installed DS5 & Dstream on a windows XP (SP3) but the USB driver installation of the Dstream fails.
Each time I plug the probe (USB) to the PC, windows ask for the driver to install ... I follow the procedure given by arm and indicate the correct folder for the drivers.
The installation starts with files copy ... but at the end of the setup an error message indicates that the installation failed without giving further indications.
Does someone already had that kind of problem?

[2] As I'm not able to connect the Dstream to the host PC via USB I have connected the probe via Ethernet.
This is working fine but it seems that, when connected via ethernet, it is not possible to do trace capture with the ETM interface.
Looks like it is only possible to use the 4KB trace buffer embedded in the OMAP.
Someone can confirm?

Thanks for your help!

Regards,
Nicolas.
Parents
  • Note: This was originally posted on 5th March 2013 at http://forums.arm.com

    Hi Scott,
    thanks for the answer and here the additionnal informations:

    [1] This is a 32bits windows XP (with SP3 installed).
    It should work ... maybe a window issue, so if someone has an idea to avoid a system re-installation.

    [2] I have installed the DS5 v5.13.
    The problem I have is that the trace I get in the trace view of DS5 only contains a 'few' number of instructions.
    In the code I'm executing, after ~2000 instructions, there is a 'FIFO Overflow' flag in the trace window.
    According to the 4GB of buffer embedded in the probe I think I should be able to get a longer trace.
    That's why I suppose that only the ETB is read and the trace port (ETM) is not used.
    The 'TRC CLK' LED is OFF.

    Regards,
    Nicolas.
Reply
  • Note: This was originally posted on 5th March 2013 at http://forums.arm.com

    Hi Scott,
    thanks for the answer and here the additionnal informations:

    [1] This is a 32bits windows XP (with SP3 installed).
    It should work ... maybe a window issue, so if someone has an idea to avoid a system re-installation.

    [2] I have installed the DS5 v5.13.
    The problem I have is that the trace I get in the trace view of DS5 only contains a 'few' number of instructions.
    In the code I'm executing, after ~2000 instructions, there is a 'FIFO Overflow' flag in the trace window.
    According to the 4GB of buffer embedded in the probe I think I should be able to get a longer trace.
    That's why I suppose that only the ETB is read and the trace port (ETM) is not used.
    The 'TRC CLK' LED is OFF.

    Regards,
    Nicolas.
Children
No data