not allowed in shipping platforms RRS feed

  • Question

  • RNDISFN:: USFN [HAS] DMA capabilityUfnClientLib!UfnCheckPID: WARNING -- using MS reference platform VID/PID 0x045e/0x0301 (not allowed in shipping platforms)

    I'm using RNDIS to connect to my device through USB. But since a while, it doesn't work and I have this message on the console...

    What does that mean?


    Thursday, August 4, 2011 2:30 PM

All replies

  • Using wince 6.0R3 on ARM processor.
    Thursday, August 4, 2011 2:31 PM
  • It appears BOOL OMAPMHSUSBOTG::PostInit() is not being called...

    Any help on that? What to search for?


    Thursday, August 4, 2011 3:57 PM
  • Hi David,

    I guess that message is only a indication and that is might not be the actual reason for your device not working...

    Which version of BSP are you using?



    Friday, August 5, 2011 6:29 AM
  • I agree with GSRId that the message is not related to the malfunctioning: that warning is there because you are using the MSFT USB vendor/device ID instead of another one as is noted in the code:

    // Display a warning if the device descriptors are using Microsoft's vendor
    // ID with a prototype product ID.
    // Returns TRUE if a warning was displayed.
    // Note: Shipping devices cannot use Microsoft's vendor ID.

    and in the registry:

    ; idVendor must be changed. 045E belongs to Microsoft and is only to be used for
    ; prototype devices in your labs. Visit to obtain a vendor id.
      "Manufacturer"="Generic Manufacturer (PROTOTYPE--Remember to change idVendor)"
      "Product"="Generic RNDIS (PROTOTYPE--Remember to change idVendor)"


    Luca Calligaris lucaDOTcalligarisATeurotechDOTcom Check my blog:
    Friday, August 5, 2011 8:48 AM
  • Thanks for your help,

    Yes, I found out that this message was not the cause of the problem... I marked it as another thing to fix :) Thanks for pointing that.

    I'm using a customized BSP based on AM/OMAP35x_WinCE 6.0 from Adeneo.

    Also, performing code comparison with another branch (on which USB is working as it should), I found there is a difference with the integration of a new custom driver to support IRIG-B on a I/O pin + the integration of QueryPerformanceCounter and QueryPerformanceFrequency. But this code doesn't touch any of the USB stuff... I'm definitely trying to remove that to see what it does.

    Meanwhile, any ideas why the OmapMhsUsbOtg::PostInit would not be called ?


    Friday, August 5, 2011 1:12 PM