>
> *On the contrary, I have no idea of what the root problem was but*
> * hibernation was part of the (accidental) solution!*
I've read a few "stories" of Hibernation causing issues very similar to the
one you've experienced here. E.G. causing devices to mysteriously go
missing, only to reappear
On 16 September 2015 at 17:22, William Hermans wrote:
> Ah ! Hibernation has a bad "habit" of causing problems like this.
On the contrary, I have no idea of what the root problem was but
hibernation was part of the (accidental) solution!
--
For more options, visit http://beagleboard.org/discuss
Ah ! Hibernation has a bad "habit" of causing problems like this.
On Wed, Sep 16, 2015 at 6:22 AM, Taceant Omnes wrote:
> On 10 September 2015 at 19:53, William Hermans wrote:
> > Probably what should be done first, is check device manager to make sure
> the
> > device is actually setup properl
On 10 September 2015 at 19:53, William Hermans wrote:
> Probably what should be done first, is check device manager to make sure the
> device is actually setup properly. I've had Windows change setting on me
> under device properties at least once. For unknown reasons.
>
> By the way, the prolific
On 10 September 2015 at 19:10, Graham wrote:
> Are you sure it is a "real" FTDI cable.
> There were some cables out there that look the same, but were built with
> counterfeit FTDI chips.
> FTDI released some (Windows) driver updates this past May that could tell
> them apart, and not work with th
Probably what should be done first, is check device manager to make sure
the device is actually setup properly. I've had Windows change setting on
me under device properties at least once. For unknown reasons.
By the way, the prolific pl2303hx cables that cost like 1/10th the price of
an FTDI work
I confirm what Graham describes. I had issues with custom boards where
bought FTDI chips were used, but never with FTDI cables purchased from
digikey
10 Сен 2015 г. 21:10 пользователь "Graham" написал:
> Are you sure it is a "real" FTDI cable.
> There were some cables out there that look the sam
Are you sure it is a "real" FTDI cable.
There were some cables out there that look the same, but were built with
counterfeit FTDI chips.
FTDI released some (Windows) driver updates this past May that could tell
them apart, and not work with the counterfeit chips.
They later recalled them, but you
On 10 September 2015 at 18:38, Maxim Podbereznyy wrote:
> You should go to the FTDI website and download the latest driver.
Thanks. I already did that. Also I tried two different FTDI cables
just in case one was not good.
--
For more options, visit http://beagleboard.org/discuss
---
You receiv
You should go to the FTDI website and download the latest driver.
10 Сен 2015 г. 20:00 пользователь "Taceant Omnes"
написал:
>
> On 10 September 2015 at 17:30, Maxim Podbereznyy
wrote:
> > I use the FTDI cable for years with no errors at all under Win7 64bits.
> > Usually I use putty but also us
On 10 September 2015 at 17:30, Maxim Podbereznyy wrote:
> 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
Thanks Maxim. My serial port configuration
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"
написал:
> I have used putty via USB on Windows on BB W
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
13 matches
Mail list logo
