AnsweredAssumed Answered

NDIS Bad Driver Debug Message i.MX28 Windows CE 6.0

Question asked by markwilliams on May 3, 2013
Latest reply on May 30, 2013 by Adeneo Engineering Team
Branched to a new discussion

Hi all,

 

When I boot my i.MX28 board as a debug build but do not use KITL (debug messages output via serial port) I see the following repeatedly output while the network connection is present:

 

The value of ControlStatus is = 980h

***NDIS*** (10, 1409) Bad driver, indicating broadcast when not set to.

                                                                       The value of ControlStatus is = 980h

***NDIS*** (10, 1409) Bad driver, indicating broadcast when not set to.

                                                                       The value of ControlStatus is = 980h

***NDIS*** (10, 1409) Bad driver, indicating broadcast when not set to.

                                                                       The value of ControlStatus is = 8000h

 

Does anyone know what this could be? When the KITL connection to platform builder is attached I do not see these messages in the debug window.

 

Interestingly with KITL enabled the same image boots without any issues, with KITL disabled it boots up to a point and then starts streaming out messages like above.

 

I also noticed the following debug message:

 

TAPI:OldAddTapiDevice - This BSP is loading TSPs by old method!!! Change registry settings to use new way!!!

 

Does something in the registry need to be changed? I couldn't find any info on this message.

 

Kind regards, Mark

 

Outcomes