Nathan K.

@USBCGuy

Freelance Smokejumper and Engineer. 「Have calipers, will travel.」

San Francisco Bay Area
Vrijeme pridruživanja: prosinac 2018.

Tweetovi

Blokirali ste korisnika/cu @USBCGuy

Jeste li sigurni da želite vidjeti te tweetove? Time nećete deblokirati korisnika/cu @USBCGuy

  1. Prikvačeni tweet
    20. srp 2019.
    Prikaži ovu nit
    Poništi
  2. prije 9 sati

    TL;DR: these compliance tests only look for the presence of an expected packet, not the ABSENCE of an unexpected one. I had to waste a few days refuting bad data because someone said "the box said green". Then had to spend two days explaining how broken the test was. :/

    Prikaži ovu nit
    Poništi
  3. prije 23 sata

    How apt. Not ten hours after I publish the article about debugging, I find a hole in the USB-IF Compliance test plan. Protip: "GREEN/PASS" does NOT always mean "okay". You still need a human behind the wheel! Both major test solutions are implicated. Whooptey doo.

    Prikaži ovu nit
    Poništi
  4. 3. velj

    I've posted the second article in a series on . Case Studies in USB-C™ Debugging Analog and digital compliance of a PD-enabled monitor Let me know if you have any comments, or anything needing correction. WARNING: It's quite long and detailed.

    Poništi
  5. 3. velj

    This... is disturbing. Perhaps there are two other books the school district admins should read: Nineteen Eighty-Four Fahrenheit 451 Why not say 14th Amendment is "often debated"? Always refer to primary, peer-reviewed sources.

    Poništi
  6. 1. velj

    Just saying, engineering this stuff (at least for USB-PD) is NOT trivial. Requires attention to detail, and working knowledge. Trust, but Verify. Perfectly safe if you know what you are doing. But companies cut corners for dumb reasons. Old as sin.

    Poništi
  7. 31. sij

    If anyone needs a Type-C debug specialist, let me know. I'm always looking for new opportunities and roles that offer growth, sustainability, and focus on product excellence.

    Poništi
  8. 29. sij

    Fair warning, / , the LILLHULT cable you sell is not compliant. Type-A SHELL is unconnected. Plus excessive DCR resistance GND-GND. Can you please USB-IF Certify? And fix it? A good friend bought this, and is unhappy; so am I. Sent email to your helpline.

    Poništi
  9. 26. sij

    Looks like the actual root cause was a bit worse. I still don't know if they fixed this. At least they provided patch notes. "Fix Thunderbolt SPI ROM Wear out issue." That's an "oops". Previous warnings still apply, but instead about "FWUPD"-atability.

    Prikaži ovu nit
    Poništi
  10. 25. sij

    This, my friends, is a perfect lesson in supply and demand.

    Poništi
  11. 25. sij

    Guess what? Found another one. There's a charger, from a big company, that blows eFuse (crowbars the AC mains line) when it is run at international voltages/frequencies at a specific voltage PDO. Even if NOT run at max load, 50-70% of capacity. Validate your circuits, people!

    Poništi
  12. 24. sij

    For clarity: the USB-IF discovered this AGES ago. Been a part of spec forever. Just a PSA to warn people to use the NEWEST spec PDF and CHECK if your silicon is compliant with the LATEST ECNs!! Some compliance DUT need "add-on" boards b/c of this. (3/2)

    Prikaži ovu nit
    Poništi
  13. 24. sij

    I reported it ages ago. Hopefully fixed? Controller gets confused and sends VBUS down an unconnected cable. Not good. USB-IF changed spec because this. Added whole new FSM state in UnattachedWait.SRC in that ECN. Already-baked silicon chips CAN'T have it. Hence problem. (2/2)

    Prikaži ovu nit
    Poništi
  14. 24. sij

    Guess what system the pinned image of a receptacle in my profile came from? I suspect this fw update has to do with UnattachWait.SRC state and false detection. See "USB Type-C ECN for Source VCONN Discharge.pdf". TI has a EE page on it. (1/2)

    Prikaži ovu nit
    Poništi
  15. 23. sij

    Shout out to the 2nd year Surgical Residents (and attendings) at and at . Without whom I would have never learned sleep is a somatic bodily function. Jokes aside, it's great experience for tech. Especially the M&M conferences...

    Poništi
  16. 21. sij

    I've posted the first article in a series on . Case Studies in USB-C™ Debugging Patient 0: Analog and digital compliance of a PD-enabled product Let me know if you have any comments on the subject, or proposed corrections. Long-form there.

    Poništi
  17. 18. sij

    There's an RTOS microcontroller that is running out of space. I think it is because of an abundance of debug strings. Need to find way to compress the strings using SMASH and decode to RAM at boot. Problem is A | B fw copies need to be separate. :( I don't know what I'm doing.

    Poništi
  18. 13. sij

    I'm thinking of writing a technical article due to some "hiccups" coworkers & I have seen. Two options: (1) Applied issues of analog CC signal and TCPCI spec compliance (2) "Proper" state machine behavior for Power Reserve mgmt Public may be wrong audience... but hey.

    Poništi
  19. proslijedio/la je Tweet
    9. sij
    Prikaži ovu nit
    Poništi
  20. 9. sij

    For clarity and honesty: has a document about this. But bugs are specifically "bugs" because they are unintended and unanticipated. My opinion only, but a good question when approaching any technology is "what is the worst that could happen".

    Poništi
  21. 9. sij

    Macbooks/ informally became this for USB-C due to marketshare + TB3. But because the "golden apple" allowed bugs, many, many badly made/poorly tested devices exist in the market. would do well to make sure TB4 has a "tests all edge cases" IPK equivalent. (4/4)

    Prikaži ovu nit
    Poništi

Čini se da učitavanje traje već neko vrijeme.

Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.

    Možda bi vam se svidjelo i ovo:

    ·