AnsweredAssumed Answered

i.MX28 Windows CE 6.0 Boot Error (Debug UART driver?)

Question asked by markwilliams on Apr 28, 2013
Latest reply on May 3, 2013 by Karina Valencia Aguilar
Branched to a new discussion

Hi all,

 

I am hoping someone can help me with an error message produced during boot of my i.MX28 Windows CE 6.0 device:

 

4294778285 PID:1710002 TID:ff0002 [NOTIFY] HandleSystemEvent 7 /ADD I2C1:

4294778285 PID:1710002 TID:ff0002 [NOTIFY] HandleSystemEvent 7 /ADD NFY0:

4294779629 PID:400002 TID:f80002 !ERROR: Calling EnterCriticalSection on a CS (d002d7c8) that is not initialized!

4294779629 PID:400002 TID:f80002 Coredll: DEBUGCHK failed in file d:\yzkiqfe\private\winceos\coreos\core\dll\cscode.c at line 117

4294779629 PID:400002 TID:f80002 DEBUG_BREAK @c005f2d8 Ignored.

4294779629 PID:400002 TID:f80002 DeviceFolder::LoadDevice(Drivers\BuiltIn\COM0) last 1395 Ticks

4294779629 PID:400002 TID:f80002 DEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\COM2\BusPrefix) returned 2

4294779629 PID:1710002 TID:ff0002 [NOTIFY] HandleSystemEvent 7 /ADD COM0:

4294780380 PID:400002 TID:f80002 DeviceFolder::LoadDevice(Drivers\BuiltIn\COM2) last 585 Ticks

4294780380 PID:400002 TID:f80002 DEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\COM5\BusPrefix) returned 2

 

Observing the debug output a block of messages appear with the same timestamp 4294779629 so I am assuming they relate to the same source - the debug UART driver COM0? I was hoping someone may be able to help me understand where to look next for this.

 

I have COM2, COM5 and the DUART1 option ticked in my platform builder catalogue. I was wondering if the DUART1 option needs to be ticked? If this is for the debug output serial port then does it need a CE driver loading or is this the source of the issue?

 

Thanks in advance, Mark

Outcomes