I use the FTDI cable for years with no errors at all under Win7 64bits.
Usually I use putty but also used Hyper Terminal without issues. You should
configure the port 115200 8 bits, no parity
10 Сен 2015 г. 17:44 пользователь "Taceant Omnes" <[email protected]>
написал:

> I have used putty via USB on Windows on BB White without issue for
> more than a year. BB White has a FTDI chip.
>
> Now I am trying to use the BB Black with the FTDI cable recommended in
> the BBB manual, however it is not working in 95% of my tries. Once it
> worked when I had the cable working with Putty in Linux and moved the
> cable to the Windows PC. By not working I mean nothing I type gets
> displayed, or occasionally only a few garbage characters appear (for
> example after I power up the BBB).
>
> I am using the latest FTDI drivers for Windows (32 bits), the latest
> version of putty. I have this problem with both Angstrom and Debian on
> a BBB rev. B and C. I am configuring putty with 115200 baud. I tried
> Tera Term but no luck either. Also tried with and without external
> power supply.
>
> On Linux things are well enough with BBB and the FTDI cable (though
> not as good as with BBW). I also tried a UART-USB bridge with CP210x
> and it is working well enough on BBB in both Windows and Linux.
>
> Any ideas on how to make the recommend FTDI cable work reliably on
> Windows with BBB?
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/d/optout.
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to