I am interested in the TUSB1211 because of its SOF output pin, which would allow me to synchronize several devices to Start Of Frame.
However, the documentation in the datasheet is poor and there is no reference on how to enable this pin. The only thing mentioned is that it needs to be enabled by setting a flag in a specific vendor register but there is no reference made to any register addresses.
Now to my questions:
1. Is there a register description of the TUSB1211 available which would allow me to utilize the SOF output?
2. Is there any timing information of the SOF output, e.g. jitter and delay between USB SOF and the signal appearing on the SOF pin F6 available?
3. What will the SOF pin do in case the TUSB1211 misses one or several Start Of Frames because of transmission errors?
4. If the TUSB1211 is configured to output a 60 MHz ULPI Clock signal on pin A4, is this clock in phase (locked) to the recovered 240 MHz HS-USB clock?
5. What would be the expected jitter on the 60 MHz ULPI clock output?
Any help would be very much appreciated!
Is there really nobody out there who can answer my questions?
I was just made aware of your post 30mins ago.
I am the design lead for TUSB1210 and TUSB1211 products.
Yes this feature is admittedly poorly documented in the datasheet.
Please find the following information which should help you with your application:
HS USB SOF (Start-Of-Frame) output clock.
This is to ensure that a "missing SOF" is only ever inserted after 125us is guaranteed to have elapsed based on fastest possible clock 60MHz+500ppm.
Note that if a missing SOF is inserted then SOF detection is ignored for the next five 60MHz clock cycles to ensure a double SOF is never generated
Currently TUSB1211 full datasheet can be distributed only under NDA (Non Disclosure Agreement). I need to check if your company has one in place with TI? Could you please contact your local TI representative. Failing this please send an email to me at email@example.com and we can discuss your requirements further.
Looking at your specific Q's:
[Peter] Please see above.
[Peter] Please see above
[Peter] Please see above. The SOF signal is synchronized with 60MHz clock. 60MHz clock is derived from internal 480MHz clock. The internal 480MHz PHY clock is not recovered from USB data. It is generated independently by the PHY but its phase is set in order to optimise data recovery, and its drift meets USB2.0 requirements (as described in HS eye diagram description of USB2.0 spec chapters 18.104.22.168 and 22.214.171.124 ) .
[Peter] Please see above.
I hope I have answered most of your questions. Please contact me if you need further information.
Is there a good reference schematic for using this part in host only mode? I'm assuming the default configuration (base on datasheet) is host mode.
Some background..... We switched from this part SMSC USB3322 (Used on original beagleboards) to the TUSB1211. Are there any key design differences that we should be aware of making that work with a OMAP. We originally assumed it was a drop in, but it doesn't seem to be working (can't access registers over ULPI interface and no negotiation for devices that are plugged in).
I just noticed, that from the spec both CS pins maybe should be pulled up. If you read about CS_N first, you would tie it to ground, but looking at CS, it notes that CS_N might be pulled high (or maybe low) when CS is high for normal operation.
=> Regarding CS and CS_N please find bellow the way to use it:- CS : Active-high chip select pin. When low the IC is in power down and ULPI bus is tri-stated. When CS is high (and CS_N pin is Tie to VDDIO if unused.s low) normal operation.- CS_N : Active-low chip select pin. When high the IC is in power down and ULPI bus is tri-stated. When CS_N is low (and CS pin is high) normal operation. Tie to GND if unused.
Please refer to http://www.ti.com/product/tusb1211 document Table 2-1. Terminal Functions.
=> Please find bellow a reference schematic :3542.TUSB1211 in ULPI output clock mode.pdf
=> Please find bellow a Basic low-level test to check TUSB1211 device is alive?Otherwise if it is very low-level testing you are referring to then you should bias TUSB1211 as in the application diagrams shown in TUSB1211 spec:- Apply VBAT (2.7V ~ 4.8V)- Apply VDDIO (1.8V)- Check CS, RESETB pin levels are VDDIO, CS_N is at GND- Set REFCLK (output CLOCK mode), or CLOCK (input CLOCK mode).
- Verify DIR goes High->Low (~3ms after CS enabled, which indicates that TUSB1211 PLL has locked, and bus is now in TX mode, i.e., control is given to Link)- Verify 60MHz clock is observed on CLOCK pin- Verify VDD33, VDD15 LDO power supply outputs are in spec (3.1V, 1.5V respectively)- Verify IDDQ vs IDDQ table in TUSB1211 datasheet
- Verify VBUS is at 5V
- Verify DIR goes High->Low- Verify VDD33, VDD18 LDO power supply outputs are in spec- Verify IDDQ vs IDDQ table in TUSB1211 spec
=> IMPORTANT: Some informations regardin TUSB1211 are TI-Confidential, not for public distribution.Could you please enter in contact with your TI Field Application Engineer in order to put an agrement in place?
Best Regards,FabianKindly click the Verify Answer button on this post, if it answers your question.
We went through and verified each of the steps. Everything looked good, with the only exception being the DIR which doesn't seem to be low for much time other then a blip after power on and after we toggle reset. Is there any additional guidance for making this chip work with a OMAP in host mode? We'd really like to use this chip over the SMSC part used on the BeagleBoard.
Another question we had was if we could get the power sequencing information (Section 126.96.36.199) mentioned in the datasheet on page 14?
Again, i am refering to NDA doc regarding TUSB1211. This is TI-Confidential, not for public distribution.Could you please enter in contact with your TI Field Application Engineer in order to put an agrement in place?
I guess Salmi, Jake is your contact?
Yes Jake Salmi is my contact. He provided me with a application guide and we evaluated that against our design. I'll send him a copy of our schematic.
Thanks for that hardware checkout. After performing that we found we had one data line getting repinmuxed after the OS booted. Once that was fixed it worked.
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with respect to these materials. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.