• Locked Locked
  • Replies 8 replies
  • Subscribers 120 subscribers
  • Views 4366 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

DS-5 Gator Module Customization

David Bercovitz
Note: This was originally posted on 30th November 2011 at http://forums.arm.com

Hello,
I have the default DS-5 and Streamline setup working fine using a Pandaboard. I have the gator.ko 5.7 source code and I'm trying to add some new traces to gator.ko. Using the mmaped exemple, I'm returning always the same 'int' value=300 from my function which I trace through a "printk" too. The printk shows the value is good and always equal to 300. However, going to the DS-5 Eclipse IDE, the Streamline interface shows some strange values in the range of 145 to 427 when zooming to the 1ms on the graphical Timeline view. It looks like the values displayed are not constant but around my original 300 value. Can anyone explain how this should be working to display a constant value in the IDE?
Thanks a lot,
David.
Parents
  • Arm Employee Badge
    Note: This was originally posted on 1st December 2011 at http://forums.arm.com

    As Wade mentioned, you can use the "gator_events_mmaped.c" as an example - it contains "pseudocounters" generating different shapes on the timeline, as shown here: http://infocenter.ar...e/CIHBADHB.html

    I have also just added a "const 300" value to that driver and it works fine - see attached screenshot. To replicate what I did:

    1. Apply attached "gator-constant-value.patch" (it adds the "const 300" value generator) to your gator sources, build it and transfer to your target as usual.
    2. Copy the attached "events.xml" to your target, to the same directory as your gatord (that's really important).
    3. Launch the gatord (you may have to load the gator module first).
    4. When you click "Counter configuration" in Streamline, you should see 4 "Simulated" available counters (and only those, as the example events.xml I attached doesn't contain others).
    5. If you add the "Simulated: Constant" to the "Events to Collect" list and launch the capture you should get result similar to the attached screenshot.

    Now, getting back to your problem... The fact that you are getting random values suggest that you fill the buffer in a wrong way and, in effect, Streamline is getting random data. If you post your code here, we can try to find the problem together.
Reply
  • Arm Employee Badge
    Note: This was originally posted on 1st December 2011 at http://forums.arm.com

    As Wade mentioned, you can use the "gator_events_mmaped.c" as an example - it contains "pseudocounters" generating different shapes on the timeline, as shown here: http://infocenter.ar...e/CIHBADHB.html

    I have also just added a "const 300" value to that driver and it works fine - see attached screenshot. To replicate what I did:

    1. Apply attached "gator-constant-value.patch" (it adds the "const 300" value generator) to your gator sources, build it and transfer to your target as usual.
    2. Copy the attached "events.xml" to your target, to the same directory as your gatord (that's really important).
    3. Launch the gatord (you may have to load the gator module first).
    4. When you click "Counter configuration" in Streamline, you should see 4 "Simulated" available counters (and only those, as the example events.xml I attached doesn't contain others).
    5. If you add the "Simulated: Constant" to the "Events to Collect" list and launch the capture you should get result similar to the attached screenshot.

    Now, getting back to your problem... The fact that you are getting random values suggest that you fill the buffer in a wrong way and, in effect, Streamline is getting random data. If you post your code here, we can try to find the problem together.
Children
No data