-
Notifications
You must be signed in to change notification settings - Fork 79
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
VTGT indicator remains lit without Vref applied when data out pins are hot #20
Comments
Workaround for test purposes - if you need to coax the level shifters into high-z mode: powering tigard from a USB power supply without data lines will power on tigard and level shifters, but not trigger /enable, keeping the level shifters in high-z mode. This workaround doesn't alleviate the (potentially confusing/risky) situation where the vtgt is lit when vtgt is not properly powered. As a consolation, there doesn't seem to be a condition for the more dangerous case where vtgt would not be lit despite being live. |
Can we do something like this (with an extra MOSFET)? /ENABLE is HIGH, VREF is LOW (FTDI has not booted, no VREF): /OE is HIGH, therefore level shifter is OFF. |
Logic checks out. My analog skills are too rusty to even think of second guessing the simulation. |
I'm a little concerned that you measured 300mV on VREF, considering the BSH103 has a very low Vgs(th) of 400mV, but considering there don't seem to be any more issues with the VTGT LED lighting up when you touch a VTGT pin anymore, I think we should be safe after adding one or two more VREF pull-downs to keep it safely below Vgs(th). I have all the components to prototype this on a Tigard, so I can give it a try too. |
tested again and measured 130mv, not 300mv. Don't know if that was a typo or other conditions changed. Same behavior whether i connect to computer USB (with day, /enable asserted, VTGT LED off, level shifter undefined) as to a usb battery(no data, /enable deasserted, VTGT LED off, level shifter tristated) Will be interesting to see if prototype results yeild something different. |
Actual issue: because current can flow from the output to VREF when the level shifter output is enabled, the level shifter output enable signal latches high.
Resolution: Documentation. Maybe look into an ideal diode solution in the future or something like that. No easy solution. |
Initial observation::
Connect tigard, LA cable, and bitmagic with Vtgt off: VTGT indicator off. Vref = 0.3v
Slide switch to 1.8v: VTGT indicator on. Vref=1.8V
Slide switch back to VTGT: VTGT Indicator on (but should be off). Vref=1.0V
Disconnect bitmagic (from usb, or disconnect LA cable): VTGT indicator off. Vref=0.0V
Theory:
current is leaking through the level shifters back to Vref.
Experiment:
all output buffer pins affected. No input buffer pins affected.
Implication:
if vref=vtgt, voltage on an output pin could leak through to vref, powering all tigard output pins, interfering with the target.
Resoluttion:
SN74LVC8T245 datasheet section 13.2:
"Keep /OE high until VCCA and VCCB are powered up"
VCCA is taken care of by FT2232H's /ENABLE
VCCB = Vref.
Right now:
/OE = /ENABLE
Fix:
/OE = /ENABLE or !Vref
I haven't come up with a magic fix without an extra component:
can't use the level shifters cause we're controlling them
can't use the spare sw1 poles cause that won't work w/ vtarget
The text was updated successfully, but these errors were encountered: