adafruit_support_mike wrote:When you say "The messaging associated with any device that runs Linux", I assume you mean the dmesg trace that gets dumped to the screen while the machine boots. I further assume you were connecting to the RasPi through `screen` or some other terminal emulator.
The fact that you saw the dmesg output means the cable works as it should. The RasPi boot sequence has a quirk where you need to hit a key once the dmesg trace ends before it will give you a login prompt.
adafruit_support_mike wrote:When you say "this did not happen," which 'this' are you referring to: the dmesg crawl during boot, or the eventual 'press a key to log in' part?
If you get the dmesg crawl, both the cable and driver are working as they should. You may need to restart `putty` after the dmesg crawl ends because of some quirk in the way your machine handles the IO connection, but that's a userland issue, not a hardware or driver issue.
adafruit_support_mike wrote:What version of Windows are you using? There could be a driver compatibility issue, though it isn't anything we've heard about before.
adafruit_support_mike wrote:Again, if you see a dmesg crawl while the RasPi is booting, the cable is working as it should.
It isn't a complicated chip, generally speaking. It just converts USB data signals to TTL UART signals. It has no protocol sensitivity, and tends to be all-or-nothing in terms of functionality.
Some people have reported trouble with `putty` as the terminal emulator. Try using zterm.
Users browsing this forum: No registered users and 2 guests