Microcontroller-Based Hardware Design With Altium Designer - #3 USB C

[@AltiumAcademy]

Series Playlist is up! Have new ideas for videos or want to make some yourself? Comment below: kzbin.info/www/bejne/rHiaoIinmrRlptU

[@moakadarkmaster]

Thank you Phil! Awesome and educational as always.

[@PhilsLab]

Thanks for watching!

[@NewBeeHardwareEngineering]

Very nice. Thanks a lot!

[@waqasqammar4231]

Hi, I tried to find out the appropriate usb switch but couldn't find one. Can you mention any one of the IC for advance users. Thanks

[@kryptocat4240]

Hai i have a question please answer to me 7:20 how can i get 3 A of current ? Is it possible by changing the value of resistor connected to CC1 and CC2 ? If yes then what value should i go with ?

[@selva81652]

Hi, Thanks for the knowledge, I have a small doubt like how to choose frequency range and impedance value for ferrite bead, like in which frequency I need high impedance.

[@PhilsLab]

Thanks for watching! I'll make a more detailed video on that in the (near) future. For now, I highly recommend app note AN-1368 by Analog Devices covering ferrite beads in more detail.

[@selva81652]

@@PhilsLab Thanks for the reply, waiting for that video, because I can't get that information at anywhere.

[@petersage5157]

Very informative video series, but I'm curious why Phil verbally glossed over ESD protection twice, whereas demonstrating it and explaining the hows and wherefores of it would only have taken an additional minute or two. At the risk of being redundant, it's best to make a habit of practicing best practices from the beginning, so that when you *do* design a commercial product they'll be habitual. Basic ESD protection is terribly simple and should be implemented even in hobby-level designs; wouldn't want your whiz-bang prototype to crap the bed because you scuffed your feet on the carpet and forgot your grounding wrist strap.

[@TheBypasser]

Most devices are HBM ESD-rated so unless you are an elephant your carpet won't kill anything ) For USB-C, a thing to worry about much more are the external ground loops, residual cap charges and PSU glitches, as here it is no longer a boring 5V-2A at most, but a high-voltage adjustable device to be capable of 20V/65W (probably more - those are the specs I've seen on an actual device), so it needs some caution to be taken ))

[@AhmadAsmndr]

Thank you very much very helpful .

[@leungjohn3875]

Thank you for the video. I wish to know if there is part 2 of it regarding pcb trace routing for the differential bus of usb c? I am working on a type c receptacle and find the dual pins of differential bus pins particularly difficult to route.

[@PhilsLab]

Thanks for watching - yes, we'll cover routing of this board in later parts of this series, including the USB C diff pair.

[@TheBypasser]

@@PhilsLab But here it is not C, but a conventional USB 1 or 2 :P

[@hopf]

EDIT: I misunderstood your comment - sorry. I guess you mean that the differential routing is maybe not so important here since (even though USB C might suggest it to some folks), the actual data rates we are talking about in this project are in the 12 (USB 1) or 480 (USB 2) Mbps range. It is still a serial connection though 🙂 ------------------------- @@TheBypasser USB C is the connector. The connector is (mostly) independent of the USB protocol version. This project uses USB C for convenience and maybe for its little higher basic power delivery capabilities (1.5A vs. 500mA with microUSB etc.). You can run USB4, 3 (with all it's confusing flavors), 2 or even 1.1/1.0 over a USB C connector. If you for example look at all those USB C connectors on (entry-level) smartphones today, rest assured that they will not be capable of transmitting anything in the range of USB 3 speeds, but usually they are USB 2.0 (480 Mbps gross) or even lower-speed connections.

[@TheBypasser]

@@hopf Sorry, but what?! USB-C is NOT just a connector (nor a protocol), but an interconnection standard having a massive underlying specification (see "Universal Serial Bus Type-C Cable and Connector Specification"). And yes, you would say you could make a simple device having 1.1 fallback, or even just power alone fed through a Type-C connector and still remain sort-of within the named specs, but that is what the millennials would call "a lifehack", as we all know how to route those older USBs, now routing a fully-featured Type-C is what can get confusing at first (and exactly what you didn't show us).

[@navrajsingh9926]

you are the best dude

[@creedo8301]

I did read the app note yet still dont know how to pick values for the PI filter Does anyone have a source on it ?

[@ATauheed]

What do we need to do if the usb-c is connected to the output of the converter and the usb-c is only acting as a connector (power connector) to another usb-c powered device

[@ATauheed]

do i connect the CC pins to gnd or Vcc

[@danilmedvedev1013]

Thank you

[@PhilsLab]

Thanks for watching, Danil!

[@sanjaybatra6593]

Sir I have two questions: As you said, pi-filter is a lowpass filter. What type of noises pi filter is reducing. Question 1. Let suppose we are using SMPS, not USB. We can also use this pi-filter after SMPS ? (excellent quality SMPS) ? Suppose an AC inductive load when "switched off" create high surge voltage on POWER LINES. I have seen SMPS is not able to stop the impact of these surge voltage. So it pass through SMPS and disturb microcontroller and other components on board. 2. Do pi-filter will be useful in this case? 3. We can also used EDS protection after SMPS ? ESD protection after SMPS will be helpful to reduce impacts of surge voltage ? What component will be used for ESD protection ? TVS diode ? Humble rest to guide in details : 🙌 share a relevant video link.

[@sanjaybatra6593]

Sir, Isn't it a complicated buck convertor ? Can't we use AMS1117 3.3, which can handle up to 1A current and easy to use. I think it don't need an inductor and so much components.

[@TheBypasser]

A few issues tho: - Large symbols with missing pins make the schematic unreadable, and it is not obvious where the remaining pins go. Pro tip: use smaller multi-gate ones (say, here it is begging to split off the data lanes into a separate gate), so the schematic would be logically structured - and show every single pin so the reader would not get confused! - This is not C, but a "compatibility" C connector over USB 2.0/1.1, not only we all know how to route this relic, but also it even lacks the OTG features. The (somewhat) true C needs: power feed direction, voltage request/feedback, side selection/lane mux, usually a set of TVS as we talk potentially high power... - Everything with external cables must be protected! Aside of the mentioned TVS you need a fuse and an OVP for a case of a residual charge or a PSU glitch. Also by the specs the USB hardware must remain intact under a cable failure, so for a high-voltage request this one is not even a way to start.

[@kettusnuhveli]

Speak for yourself about knowing how to route relics. Also 2.0 is enough for 99,8% of projects and using a proper type-C IC would have just complicated a tutorial clearly aimed at beginners!

[@TheBypasser]

@@kettusnuhveli Wait, what? It is 2024 already, and someone doesn't know how to route USB2? Guess that is possible only in one sole case: one just doesn't need that at all in first place ;) (and btw nobody ever stated the actual line impedance on D+/D-, also stating you need a mux switch for 2.0 speeds is a false statement). Anyway. 2.0 is enough for whatever it is enough, sometimes even 1.1 is the best choice, in some other cases 2.0 is too slow - but. The title clearly states: "USB C". The content, however, covers almost nothing from the C features - could've been just routing power off the jack and calling it a day.