CE6 CETK failure.

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

prayas MOHANTY - 20 Jun 2008 02:04 GMT

Hi,
I have problems running Camera CETK in CE6. When i run CETK, randomly it
gives data abort for k.coredll. And then i press go and it happily moves
ahead, and fails every test .. :)
I was fighting hard to get it working, but then i realised the same happens
with the device emulator setup as well.
Is this something that MSFT knows and has a fix or am i only 1 to be
reporting abt it.

Regards,
Prayas.

Reply to this Message

prayas MOHANTY - 26 Jun 2008 07:02 GMT

Hi,
After facing the issue below, i changed my approach an started running CETK
over the command line.
I faced lot of Hang issues earlier on. I debugged the MDD code and then
figured out that the CS was not implemented correctly for the SetState.
I then removed the CS from the STOP state and put CS checks for individual
states, PAUSE and RUN. It worked fine.
The reason for hang was in STOP state, there is a Kill Timer call, and when
we are trying to kill the timer, there is kind of a DEAD LOCK becoz of the CS
guarding the STOP senario and CS in HandlePinIO.

Other than this, i have issues in running CETK for camera. Most of the fail.

Comments and suggestions woud be much appreciated.

> Hi,
> I have problems running Camera CETK in CE6. When i run CETK, randomly it
[quoted text clipped - 7 lines]
> Regards,
> Prayas.

Reply to this Message

Sue Loh [MS] - 26 Jun 2008 16:04 GMT

Prayas, your posts are rather vague and unclear. You will get better help
when you give more context about what you are saying. MDD code of what?

For your camera CETK failures, what tests fail and what failure messages do
they give? Usually when CETK tests fail it’s because you need to fix the
drivers. I don’t know the state of our camera driver, whether it is
supposed to be “production quality” and pass all the CETK tests out of the
box, or whether you would need to do work to get the driver working
correctly.

Sue
sloh@microsoft.com (remove "online" from reply-to address)
http://blogs.msdn.com/ce_base/
_____________________________________________________________
This posting is provided "AS IS" with no warranties, and confers no rights.
_____________________________________________________________

Reply to this Message

prayas MOHANTY - 26 Jun 2008 23:18 GMT

Thanks for the reply Sue,
I appologise for not beeing clear. However the MDD code i was refering to
was of CAMERA in CE6.
You can see the details of the deadlock situation in the CAMERA driver MDD
code.
file : pindevice.cpp
Line : 347 & 703
Problem: Both are waiting on same CS (m_csStreamIO).
When we are in STOP state we already have aquired the CS, at the same time,
if the timercall back is triggered then that would be looking for that exact
same CS. and the Killtimer call cannot be completed becoz the timer callback
is waiting to get the CS. This is a DeadLock state.

You say, you are not sure of the state of the camera driver, if it is
supposed to be of production quality.
How can i know, if the camera driver for CE6 is ready for production quality ?
Plz reply.

> Prayas, your posts are rather vague and unclear. You will get better help
> when you give more context about what you are saying. MDD code of what?
[quoted text clipped - 12 lines]
> This posting is provided "AS IS" with no warranties, and confers no rights.
> _____________________________________________________________

Reply to this Message

prayas MOHANTY - 01 Jul 2008 06:09 GMT

Hello,

> How can i know, if the camera driver for CE6 is ready for production quality ?

May I please have an answer to thie above question.

> Thanks for the reply Sue,
> I appologise for not beeing clear. However the MDD code i was refering to
[quoted text clipped - 30 lines]
> > This posting is provided "AS IS" with no warranties, and confers no rights.
> > _____________________________________________________________

Reply to this Message