locked
SerialDevice.FromIdAsync always returns null on 1 of 3 USB ports. RRS feed

  • Question

  • On my UDOO x86 device, I have 3 USB connectors. On 2 of them I am able successfully to communicate to FPGA device, but on the 3d one I always getting null from

    serialPort = await SerialDevice.FromIdAsync(myDevices[0].Id);

    A difference that I noticed:

    <g class="gr_ gr_26 gr-alert gr_spell gr_inline_cards gr_run_anim ContextualSpelling ins-del multiReplace" data-gr-id="26" id="26">deviceInformation</g>.Name on two working USB connectors is “Silicon Labs CP210x USB to UART Bridge (COM3)” and on the 3d USB connector - “DESKTOP-KRV2KIE - Front” (where DESKTOP-KRV2KIE is UDOO machine name). On “Device Manager” all 3 connectors have display name as “Silicon Labs CP210x USB to UART Bridge (COM3)”.

    As I’ve seen at MSDN when USB has a name as machine name, <g class="gr_ gr_20 gr-alert gr_gramm gr_inline_cards gr_run_anim Grammar only-ins doubleReplace replaceWithoutSep" data-gr-id="20" id="20">device</g> will not connect.

    Why UDOO’s USB connector has <g class="gr_ gr_21 gr-alert gr_gramm gr_inline_cards gr_run_anim Grammar only-ins doubleReplace replaceWithoutSep" data-gr-id="21" id="21">name</g> as machine name? Is it possible to connect to this connector at all (for our app we need all 3 USB connectors)?

    The other differences from “Device Manager”:

     bad USB connector doesn’t have CM_DEVCAP_REMOVABLE in Capabilities and its Container iD is {00000000-0000-0000-ffff-ffffffffffff}

    Wednesday, February 14, 2018 9:39 PM

All replies

  • Hi larysa56,

    According to your description, you said that you have 3 USB connectors in your UD)) x86 device, two of them were able to communicate  with FPGA device, and you also said that you have seen at MSDN when USB has a name as machine name, <g class="gr_ gr_20 gr-alert gr_gramm gr_inline_cards gr_run_anim Grammar only-ins doubleReplace replaceWithoutSep" data-gr-id="20" id="20">device</g> will not connect. So I suggest you can feedback your issue and doubts at that MSDN article.

    Best Regards,

    Cherry


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Thursday, February 15, 2018 8:08 AM