• Locked Locked
  • Replies 5 replies
  • Subscribers 120 subscribers
  • Views 4004 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 7th March 2013 at http://forums.arm.com

    I'm using an Omap3530 EVM board from Mistral and I connect the Dstream probe with the 38pins mictor.
    I have tried to check on a scope the Etk_Clk pin of ETM connector but there is no signal. Seems that the issue is here.

    As this trace mechanism is new to me. Please could you confirm I understood correctly how this should work?
    # If you're using a classic 14pins JTAG connector:
    - The on-chip 4KB ETB of the OMAP35x is automatically filled during code execution.
    - When the user stops the execution, the ETB content is transferred via JTAG to DStream then to DS5 and displayed in trace view.
    # If you're using the ETM connector
    - The trace data are continuously transferred  from ETM to DStream 4BG buffer during code execution.
    - When the user stops the execution, the DStream buffer content is transferred to DS5.

    When I check the trace properies in the trace view I can see that the buffer size is 4KB ... like the ETB size.
Reply
  • Note: This was originally posted on 7th March 2013 at http://forums.arm.com

    I'm using an Omap3530 EVM board from Mistral and I connect the Dstream probe with the 38pins mictor.
    I have tried to check on a scope the Etk_Clk pin of ETM connector but there is no signal. Seems that the issue is here.

    As this trace mechanism is new to me. Please could you confirm I understood correctly how this should work?
    # If you're using a classic 14pins JTAG connector:
    - The on-chip 4KB ETB of the OMAP35x is automatically filled during code execution.
    - When the user stops the execution, the ETB content is transferred via JTAG to DStream then to DS5 and displayed in trace view.
    # If you're using the ETM connector
    - The trace data are continuously transferred  from ETM to DStream 4BG buffer during code execution.
    - When the user stops the execution, the DStream buffer content is transferred to DS5.

    When I check the trace properies in the trace view I can see that the buffer size is 4KB ... like the ETB size.
Children
No data