The granularity of kernel timer is 1ms, it is impossible to get 250us periodic timing. You need special hardware to generate interrupts every 250us (or 250us /n) to achieve that. 

Jerry Sui | Software Developer | jsui@qnx.com

O:613-591-0836 x 24904 C:613-240-9239 | www.qnx.com | QNX Software Systems
Cisco Support Team email: cisco_support@qnx.com



From: Mario Charest <community-noreply@qnx.com>
Reply-To: "ostech-core_os@community.qnx.com" <ostech-core_os@community.qnx.com>
Date: Friday, 11 October, 2013 2:59 PM
To: "ostech-core_os@community.qnx.com" <ostech-core_os@community.qnx.com>
Subject: RE: RE: Uncertainty about timer under the QNX RTOS

You never mentioned what is your hardware.  

BIOS can take over the OS, when then USB is in emulation mode, for example...

-----Message d'origine-----
De : yunfei qu [mailto:community-noreply@qnx.com]
Envoyé : 11 octobre 2013 10:25
À : ostech-core_os
Objet : Re: RE: Uncertainty about timer under the QNX RTOS
1.Yes, it is. I have tried many times, results are similar.
2.I use signal, not pulse, and the priority of the thread waiting for such signal is
200.
3.I have no idea how to write an ISR for the HPET while it has a default one
comes from the kernel maybe.
4.what I want to acquire is a periodic timing(250us) with high stability, so I could
get high synchronization  performence of motion control.
Thanks again!
_______________________________________________
OSTech
http://community.qnx.com/sf/go/post105867
To cancel your subscription to this discussion, please e-mail ostech-core_os-
unsubscribe@community.qnx.com





_______________________________________________

OSTech
http://community.qnx.com/sf/go/post105878
To cancel your subscription to this discussion, please e-mail ostech-core_os-unsubscribe@community.qnx.com