USB Testing

1141516171820»

Comments

  • samuellsamuell Posts: 286
    edited 2019-05-16 - 21:13:05
    VonSzarvas wrote: »
    samuell wrote: »

    However, as in the MSC driver, only the upper port works on the add-on board.

    Kind regards, Samuel Lourenço

    Hi Samuel,

    Just to double check that both power enable pins are getting set; the upper and lower usb sockets each have an ENable pin.
    basepin+1 and basepin+5

    garryj's post/code above includes those, but maybe some older code didn't assert both?
    These pins act as they are very high impedance. As soon as I try to measure the voltage on pin 1 with the device connected to the upmost port, the device disconnects. I'm essentially disabling the power switch on the board because the burden resistance of the DVM is enough to "ground" the pin. I've noticed that, although having no effect on terminal, I can disable the lower port by trying to measure between pin 5 and ground. I've concluded that by observing the LED on the pen.

    The measured voltages are always on the order of tens of mV. I get the same voltages if I try to measure between any of these pins and VIO_3V3. I was expecting pin 1 and 5 to be output pins. but they seem to be close to floating.

    Kind regards, Samuel Lourenço
  • Is there some problem with the DP/DM pin driving in the USB smart pin mode?
  • I don't think the USB smart pin mode is involved, as I'm using the P2-Eval board + the Serial Host accessory board and both ports are working nicely.
    garryj
  • jmgjmg Posts: 13,522
    cgracey wrote: »
    Is there some problem with the DP/DM pin driving in the USB smart pin mode?
    I think (hopefully?) it's more a labeling/config issue as one reports ok and another reports no activity ?
    garryj wrote: »
    I'm at a loss as to why the lower port is not working, as that is the one I usually test with:
    Can you confirm which Specific P2 pins (pin pairs) you have tested USB on ?
    In theory, it should work on any valid pin-pair, right ?


  • jmg wrote: »
    garryj wrote: »
    I'm at a loss as to why the lower port is not working, as that is the one I usually test with:
    Can you confirm which Specific P2 pins (pin pairs) you have tested USB on ?
    In theory, it should work on any valid pin-pair, right ?
    I normally work with the Serial Host board on the pin group starting at pin #16. Moved it to group #24 and all is good there, too. D- must be connected to an even pin# for the smart pins to do their thing.
    garryj
  • This sounds like an issue with providing the 5V power that devices need..
    Prop Info and Apps: http://www.rayslogic.com/
  • samuellsamuell Posts: 286
    edited 2019-05-17 - 01:06:54
    Rayman wrote: »
    This sounds like an issue with providing the 5V power that devices need..
    I've confirmed that it is not the case. The lower port provides power as well. However, the enabling pins should not be floating. Even touching with a finger will ground those pins and disable power going to the devices.

    But, I'm certain that this is not the only problem, since the lower port is powered as well. There must be another factor. I can "blink" pins 25 (1 on add-on board) and 29 (5 on add-on board) via TAQOZ and the power on each port "blinks" accordingly.

    Kind regards, Samuel Lourenço
  • I've been testing USB keyboards on both top and bottom sockets on different pin groups too.
    Works fine here.
    For refrence here's the pin offsets I use.
    Eval accessory board top socket
    
    	usb_enable = usb_basepin + 1
            DM = usb_basepin + 2 
            DP = usb_basepin + 3 
    
    Eval accessory board bottom socket
    
    	usb_enable = usb_basepin + 5
            DM = usb_basepin + 6 
            DP = usb_basepin + 7 
    
    Melbourne, Australia
  • cgraceycgracey Posts: 11,129
    edited 2019-05-17 - 05:08:39
    samuell wrote: »
    Rayman wrote: »
    This sounds like an issue with providing the 5V power that devices need..
    I've confirmed that it is not the case. The lower port provides power as well. However, the enabling pins should not be floating. Even touching with a finger will ground those pins and disable power going to the devices.

    But, I'm certain that this is not the only problem, since the lower port is powered as well. There must be another factor. I can "blink" pins 25 (1 on add-on board) and 29 (5 on add-on board) via TAQOZ and the power on each port "blinks" accordingly.

    Kind regards, Samuel Lourenço

    Samuel, by "enabling pins", do you mean pins other than DP and DM?
  • samuell wrote: »
    Rayman wrote: »
    This sounds like an issue with providing the 5V power that devices need..
    I've confirmed that it is not the case. The lower port provides power as well. However, the enabling pins should not be floating. Even touching with a finger will ground those pins and disable power going to the devices.

    But, I'm certain that this is not the only problem, since the lower port is powered as well. There must be another factor. I can "blink" pins 25 (1 on add-on board) and 29 (5 on add-on board) via TAQOZ and the power on each port "blinks" accordingly.

    Kind regards, Samuel Lourenço


    Correct. ENable is a high impedance input that controls the 5V power out.

    That ENable pin should be set LOW in your code (or enable smartpin pulldown) during code startup.

    When you want either USB port to output 5V, then set the appropriate EN pin HIGH (basepin+1 for the upper USB, basepin+5 for the lower USB).

    D+ and D- are not controlled by the switch. They are always connected from the socket to the basepin+X. Although granted, you'd likely want 5V-out active in most applications!

    Part number for the switch is: TPD3S014-Q1


    Given that you are measuring 5V at the lower port, it would seem the issue is elsewhere....

    Is there a short between D+ and D- perhaps?
    OR a path to ground?
    Have you tried the accessory module in another header position?
  • samuellsamuell Posts: 286
    edited 2019-05-17 - 13:33:57
    cgracey wrote: »
    samuell wrote: »
    Rayman wrote: »
    This sounds like an issue with providing the 5V power that devices need..
    I've confirmed that it is not the case. The lower port provides power as well. However, the enabling pins should not be floating. Even touching with a finger will ground those pins and disable power going to the devices.

    But, I'm certain that this is not the only problem, since the lower port is powered as well. There must be another factor. I can "blink" pins 25 (1 on add-on board) and 29 (5 on add-on board) via TAQOZ and the power on each port "blinks" accordingly.

    Kind regards, Samuel Lourenço

    Samuel, by "enabling pins", do you mean pins other than DP and DM?
    Hi Chip. I'm referring to the USB enable pins, offset 1 and 5.
    VonSzarvas wrote: »
    samuell wrote: »
    Rayman wrote: »
    This sounds like an issue with providing the 5V power that devices need..
    I've confirmed that it is not the case. The lower port provides power as well. However, the enabling pins should not be floating. Even touching with a finger will ground those pins and disable power going to the devices.

    But, I'm certain that this is not the only problem, since the lower port is powered as well. There must be another factor. I can "blink" pins 25 (1 on add-on board) and 29 (5 on add-on board) via TAQOZ and the power on each port "blinks" accordingly.

    Kind regards, Samuel Lourenço


    Correct. ENable is a high impedance input that controls the 5V power out.

    That ENable pin should be set LOW in your code (or enable smartpin pulldown) during code startup.

    When you want either USB port to output 5V, then set the appropriate EN pin HIGH (basepin+1 for the upper USB, basepin+5 for the lower USB).

    D+ and D- are not controlled by the switch. They are always connected from the socket to the basepin+X. Although granted, you'd likely want 5V-out active in most applications!

    Part number for the switch is: TPD3S014-Q1


    Given that you are measuring 5V at the lower port, it would seem the issue is elsewhere....

    Is there a short between D+ and D- perhaps?
    OR a path to ground?
    Have you tried the accessory module in another header position?
    I could try other header position. But since the code is not mine, I'm having difficulty finding the variable where the offset can be changed.

    Update:
    Tested pins 24 to 31 as blinking outputs, with TAQOZ, and found no issues. Also tested the add-on board separately for shorts to ground or IO_3V3, and detected no problems whatsoever.

    Kind regards, Samuel Lourenço
Sign In or Register to comment.