• Locked Locked
  • Replies 5 replies
  • Subscribers 120 subscribers
  • Views 4003 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.
  • Arm Employee Badge
    Note: This was originally posted on 5th March 2013 at http://forums.arm.com

    [1] Is your XP a 32-bit or a 64-bit version?  DS-5 only supports XP 32-bit.  Windows 7 is supported in both 32-bit and 64-bit.

    [2] You should be able to capture trace when connected to the DSTREAM via Ethernet.  Can you describe the problem in more detail:  what goes wrong when you try to capture trace?  Also, do you see any indications from the TRC CLK LEDs on the DSTREAM?
    What version of DS-5 are you installing?  The current latest is v5.13.
  • 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.
  • Arm Employee Badge
    Note: This was originally posted on 6th March 2013 at http://forums.arm.com


    [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.

    I'm afraid I don't have an answer to the USB problem, then.  Probably best to try sending it to ARM Support: support-sw@arm.com; that maybe true for the other question, too.


    [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.

    Approximately how many is a "few"?

    FIFO Overflow is when the TPIU's (trace port interface unit) FIFO overflows on-chip.  The TPIU is what sends trace data to the trace port/DSTREAM.  FIFO Overflow means that the trace clock is too low and/or the trace port is too narrow for the amount of trace data being generated.  I don't think the problem is the DSTREAM buffer.  You can look at the Properties pane in theTrace view in case it gives any clue; it will give the buffer size.

    What is your target platform?  Are you able to increase the trace clock frequency?  Or turn off data trace, etc.

    If your target has an ETB, I would expect it to be able to hold more than 2000 instructions; and I would expect the ETB to just wrap and not cause FIFO Overflows.


    The 'TRC CLK' LED is OFF.



    That doesn't sound right.  If you're using external trace (TPIU/DSTREAM) then I would expect the TRC CLK LED to blink green (at least when acquiring trace).  There are two TRC CLK LEDs one on the main DSTREAM and one on the probe connector box.
  • 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.
  • Arm Employee Badge
    Note: This was originally posted on 8th March 2013 at http://forums.arm.com

    You are right that the JTAG connection will not handle external trace, but the type of trace is not automatically selected by the cable connected

    The choice between ETB and TPIU (external trace) is made by choosing the platform and DTSL Options.   DS-5 doesn't supply a platform for OMAP3530EVM.   And the closest platforms [Mistral > AM3730, TI > OMAP 3530 (Generic) and TI > OMAP 35XX (Generic)] have only "Debug and ETB Trace" options.  Which platform have you selected in the debug configuration that you are using?

    I suggest you try creating your own platform by using Debug Hardware Config and cdbimporter.  See http://infocenter.ar...h/BGBIICAJ.html,  http://infocenter.ar...m/CIHEJGAB.html and http://infocenter.ar...m/CIHFJGAF.html

    I tried this on my OMAP3530EVM and was able to select the DSTREAM in the DTSL options, but I didn't get any trace clock (or trace).   I suspect there is some target pinmuxing required.