none
Time X RRS feed

  • Question

  • Hi,

    There is a strange issue with time. Everything is fine till 11:59 turns either 00:00 or 12:00 IDK because it has never happened. Then I am getting the following errors continuesly and the time is not updating anymore:

    PID:021B000A TID:027C001A NK Kernel: DEBUGCHK failed in file d:\chelanrtm14\private\winceos\coreos\nk\kernel\time.c at line 320
    PID:00400002 TID:027C001A CHECKTAKECRITSEC: Violation of critical section ordering, holding CS 9319c860 (4) while taking CS 9319c840 (10)
    PID:00400002 TID:027C001A NK Kernel: DEBUGCHK failed in file d:\chelanrtm14\private\winceos\coreos\nk\kernel\schedule.c at line 337
    PID:00400002 TID:027C001A CHECKTAKECRITSEC: Violation of critical section ordering, holding CS 9319c860 (4) while taking CS 9319c7c0 (12)
    PID:00400002 TID:027C001A NK Kernel: DEBUGCHK failed in file d:\chelanrtm14\private\winceos\coreos\nk\kernel\schedule.c at line 337
      KdTrap: JIT debugging requested, waiting for OEM selection
      KdTrap: JIT debugging accepted
    PID:00400002 TID:027C001A DEBUG_BREAK @910983d8 Ignored.
    PID:00400002 TID:027C001A CHECKTAKECRITSEC: Violation of critical section ordering, holding CS 9319c860 (4) while taking CS 9319c7c0 (12)
    PID:00400002 TID:027C001A NK Kernel: DEBUGCHK failed in file d:\chelanrtm14\private\winceos\coreos\nk\kernel\schedule.c at line 337
      KdTrap: JIT debugging requested, waiting for OEM selection
      KdTrap: JIT debugging accepted
    PID:00400002 TID:027C001A DEBUG_BREAK @910983d8 Ignored.
    PID:00400002 TID:027C001A CHECKTAKECRITSEC: Violation of critical section ordering, holding CS 9319c860 (4) while taking CS 9319c7c0 (12)
    PID:00400002 TID:027C001A NK Kernel: DEBUGCHK failed in file d:\chelanrtm14\private\winceos\coreos\nk\kernel\schedule.c at line 337
      KdTrap: JIT debugging requested, waiting for OEM selection
      KdTrap: JIT debugging accepted
    PID:00400002 TID:027C001A DEBUG_BREAK @910983d8 Ignored.
    PID:00400002 TID:027C001A CHECKTAKECRITSEC: Violation of critical section ordering, holding CS 9319c860 (4) while taking CS 9319c7c0 (12)
    PID:00400002 TID:027C001A NK Kernel: DEBUGCHK failed in file d:\chelanrtm14\private\winceos\coreos\nk\kernel\schedule.c at line 337
      KdTrap: JIT debugging requested, waiting for OEM selection
      KdTrap: JIT debugging accepted
    PID:00400002 TID:027C001A DEBUG_BREAK @910983d8 Ignored.
      KdTrap: JIT debugging requested, waiting for OEM selection
      KdTrap: JIT debugging accepted
    PID:00400002 TID:027C001A DEBUG_BREAK @910983d8 Ignored.
    PID:00400002 TID:027C001A CHECKTAKECRITSEC: Violation of critical section ordering, holding CS 9319c860 (4) while taking CS 9319c8a0 (6)
    PID:00400002 TID:027C001A NK Kernel: DEBUGCHK failed in file d:\chelanrtm14\private\winceos\coreos\nk\kernel\schedule.c at line 337
      KdTrap: JIT debugging requested, waiting for OEM selection
      KdTrap: JIT debugging accepted
    PID:00400002 TID:027C001A DEBUG_BREAK @910983d8 Ignored.

     

    Do you know what can be wrong?

    Thanks


    • Edited by Jker Tuesday, September 20, 2011 9:05 AM
    Tuesday, September 20, 2011 8:59 AM

All replies

  • The 1st DEBUGCHK (which may the cause of all the disaster) is in %_WINCEROOT%\PRIVATE\WINCEOS\COREOS\NK\KERNEL\time.c:

    // read RTC 
    
    OEMGetRealTime (&st); 
    
    DEBUGCHK(IsValidSystemTime(&st));  
    

    The function  IsValidSystemTime simply checks if the SYSTEMTIME structure is valid (wMinute < 60,  wSecond < 60, ...): maybe the OEMGetRealTime in your BSP has a bug: add some RETAILMSG into it, force/wait the clock to wrap and you'll probaby see something wrong in the SYSTEMTIME structure (let's say the time it's 11:60),


    Luca Calligaris lucaDOTcalligarisATeurotechDOTcom www.eurotech.com Check my blog: http://lcalligaris.wordpress.com
    Tuesday, September 20, 2011 10:00 AM