Porting BSP from CE 5.0 to 6.0 problem.

Hi all,

I am using Win CE 6.0. I am porting my one BSP from CE 5.0 to CE 6.0. I am
getting interrupt errors.

Is any body know when we port any BSP from CE5.0 to CE6.0 why this type
problem occurs?

Is any common solution for this?


Thanks in advance

Swapnil

Valter
Mon May 19 06:39:10 PDT 2008

=?Utf-8?B?U3dhcG5pbCBNYW5nbGVrYXI=?=
<SwapnilManglekar@discussions.microsoft.com> wrote in
news:0809BE39-B6A1-498B-8299-9948AB7C622E@microsoft.com:

> Hi all,
>
> I am using Win CE 6.0. I am porting my one BSP from CE 5.0 to CE
> 6.0. I am getting interrupt errors.
>
> Is any body know when we port any BSP from CE5.0 to CE6.0 why this
> type problem occurs?
>
> Is any common solution for this?
>
> Thanks in advance

AFAIK there is no "interrupt error" defined in Windows CE.
What do you mean?
Errors during build or errors at runtime?

To move your BSP to CE 6 you need to change your OAL organization
first. There is a great presentation by Travis Horbla on Channel 9
describing that:
http://channel9.msdn.com/Showpost.aspx?postid=376154


--
Valter Minute
www.fortechembeddedlabs.it
Training, support and development for Windows CE
(the reply address of this message is invalid)

SwapnilManglekar
Mon May 19 08:27:02 PDT 2008

Thanks for reply Valter,

I am using Touch Screen Driver which is of CE 5 and i am ported it in CE 6.
I am getting *INTERRUPTS* so it doesn't work in CE 6. It will be hang.

At the time of downloading image (at initialization of touch panel) it shows
this massage :

Failed to obtain sysintr value for touch!

Is any different interrupts are require to set for CE6?

Best Regards,

Swapnil


> AFAIK there is no "interrupt error" defined in Windows CE.
> What do you mean?
> Errors during build or errors at runtime?
>
> To move your BSP to CE 6 you need to change your OAL organization
> first. There is a great presentation by Travis Horbla on Channel 9
> describing that:
> http://channel9.msdn.com/Showpost.aspx?postid=376154
>
>
> --
> Valter Minute
> www.fortechembeddedlabs.it
> Training, support and development for Windows CE
> (the reply address of this message is invalid)
>

Bruce
Mon May 19 09:23:51 PDT 2008

That message is probably in your touch driver. What is failing and why? We
don't know anything about your BSP except that it is being ported from CE
5.0 to 6.0 and that it has a touch driver.

--
Bruce Eitman (eMVP)
Senior Engineer
Bruce.Eitman AT EuroTech DOT com
My BLOG http://geekswithblogs.net/bruceeitman

EuroTech Inc.
www.EuroTech.com

"Swapnil Manglekar" <SwapnilManglekar@discussions.microsoft.com> wrote in
message news:20441FC7-6F7B-43B3-996E-4E6D1DB75478@microsoft.com...
> Thanks for reply Valter,
>
> I am using Touch Screen Driver which is of CE 5 and i am ported it in CE
> 6.
> I am getting *INTERRUPTS* so it doesn't work in CE 6. It will be hang.
>
> At the time of downloading image (at initialization of touch panel) it
> shows
> this massage :
>
> Failed to obtain sysintr value for touch!
>
> Is any different interrupts are require to set for CE6?
>
> Best Regards,
>
> Swapnil
>
>
>> AFAIK there is no "interrupt error" defined in Windows CE.
>> What do you mean?
>> Errors during build or errors at runtime?
>>
>> To move your BSP to CE 6 you need to change your OAL organization
>> first. There is a great presentation by Travis Horbla on Channel 9
>> describing that:
>> http://channel9.msdn.com/Showpost.aspx?postid=376154
>>
>>
>> --
>> Valter Minute
>> www.fortechembeddedlabs.it
>> Training, support and development for Windows CE
>> (the reply address of this message is invalid)
>>

Valter
Tue May 20 01:04:38 PDT 2008

=?Utf-8?B?U3dhcG5pbCBNYW5nbGVrYXI=?=
<SwapnilManglekar@discussions.microsoft.com> wrote in
news:20441FC7-6F7B-43B3-996E-4E6D1DB75478@microsoft.com:

> Thanks for reply Valter,
>
> I am using Touch Screen Driver which is of CE 5 and i am ported it
> in CE 6. I am getting *INTERRUPTS* so it doesn't work in CE 6. It
> will be hang.
>
> At the time of downloading image (at initialization of touch
> panel) it shows
> this massage :
>
> Failed to obtain sysintr value for touch!
>
> Is any different interrupts are require to set for CE6?

You should find where this message is printed out in your driver
sources to understand what's happening.
I can guess that:
- there is no "sysintr" values specified in the registry (the code
will fail on a RegQueryValue or something like that)
- the sysintr value is not valid for the BSP (InterruptEnable will
fail)
- the driver reads an IRQ value but can't convert it to a sysintr
(KernelIoControl will fail).





--
Valter Minute
www.fortechembeddedlabs.it
Training, support and development for Windows CE
(the reply address of this message is invalid)