Arm Community
Site
Search
User
Site
Search
User
Support forums
Arm Development Studio forum
DS-5 Gator Module Customization
Jump...
Cancel
Locked
Locked
Replies
8 replies
Subscribers
119 subscribers
Views
4631 views
Users
0 members are here
Options
Share
More actions
Cancel
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
over 12 years ago
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
Wade Cherry
over 12 years ago
Note: This was originally posted on 30th November 2011 at
http://forums.arm.com
In mmaped_simulate(), adding something like,
case 2:
result = 300;
break;
produces a constant 300 value every millisecond for the simulated counter #2.
Can you share your source code, including the updated events .xml file to enable the counters? Were you able to produce the simulated PWM, Triangle, and Sine wave examples? The examples would be the best way to understand how the driver event relates to the IDE timeline.
Cancel
Vote up
0
Vote down
Cancel
Reply
Wade Cherry
over 12 years ago
Note: This was originally posted on 30th November 2011 at
http://forums.arm.com
In mmaped_simulate(), adding something like,
case 2:
result = 300;
break;
produces a constant 300 value every millisecond for the simulated counter #2.
Can you share your source code, including the updated events .xml file to enable the counters? Were you able to produce the simulated PWM, Triangle, and Sine wave examples? The examples would be the best way to understand how the driver event relates to the IDE timeline.
Cancel
Vote up
0
Vote down
Cancel
Children
No data