Difference between revisions of "Adafruit 954 USB serial cable"

From eLinux.org
Jump to: navigation, search
(DRIVER_POWER_STATE_FAILURE)
(BAD_POOL_CALLER)
 
Line 35: Line 35:
 
Conflict amongst drivers.
 
Conflict amongst drivers.
 
Most probably another driver did already process the request (and should not have done so).
 
Most probably another driver did already process the request (and should not have done so).
 +
 +
====Bug Check: BAD_POOL_CALLER====
 +
?
  
 
==See also==
 
==See also==
 
*[[RPi Serial Connection]]
 
*[[RPi Serial Connection]]
 
*[[RPi_Hub|Raspberry Pi]]
 
*[[RPi_Hub|Raspberry Pi]]

Latest revision as of 12:12, 30 December 2015

Adafruit serial cable connected to Pi

The Adafruit 954 USB serial cable can be used to:

When using the Adafruit 954 USB cable on Windows 7 the Prolific driver' seems already be installed, so you could skip this step. Simply connect the USB cable. You will see a device Prolific USB-to-Serial Comm Port; verify via Control Panel → System → Device Manager to get the port number.

The cable can be ordered via the internet.

Known problems

Hardware problems

Transparent case for the Raspberry Pi model B+ is too low

There are some problems with the transparent case of Raspberry Pi B+:

  • The case is too low for the Adafruit 954 USB serial cable; it bends the circuit pins
  • The latch does not close properly
  • There is no spare hole for the cable

Software problems

Driver problems; this leads to system crashes (Blue screens) and potential data loss. Very difficult to solve. Maybe another version of the driver should be installed?

Bug Check: DRIVER_IRQL_NOT_LESS_OR_EQUAL

This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high. Possibly the Prolific driver contains a bug.

See: http://msdn.microsoft.com/en-us/library/windows/hardware/ff560244%28v=vs.85%29.aspx

Bug Check: DRIVER_POWER_STATE_FAILURE

ACPI problem

Bug Check: MULTIPLE_IRP_COMPLETE_REQUESTS

A driver has called IoCompleteRequest to ask that an IRP be completed, but the packet has already been completed. Conflict amongst drivers. Most probably another driver did already process the request (and should not have done so).

Bug Check: BAD_POOL_CALLER

?

See also