X-Git-Url: https://sigrok.org/gitweb/?p=libsigrok.git;a=blobdiff_plain;f=README.devices;h=3e9b631f75f9936708f5505e23499a47eeec0fe9;hp=8fc9d7b80aed58ff8e8f749ad1c922f76c850136;hb=22fdb67fa0714c11cc0a58ee1423f55d18a4f080;hpb=ebc51109899008694c50977cb2574050b1bc0c89

diff --git a/README.devices b/README.devices
index 8fc9d7b8..3e9b631f 100644
--- a/README.devices
+++ b/README.devices
@@ -98,7 +98,6 @@ The following drivers/devices do not need any firmware upload:
  - atten-pps3xxx
  - baylibre-acme
  - beaglelogic
- - brymen-dmm
  - cem-dt-885x
  - center-3xx (including all subdrivers)
  - chronovu-la
@@ -136,6 +135,7 @@ The following drivers/devices do not need any firmware upload:
  - pce-322a
  - pipistrello-ols
  - rdtech-dps
+ - rigol-dg
  - rigol-ds
  - rohde-schwarz-sme-0x
  - scpi-dmm
@@ -185,6 +185,7 @@ Formal syntax for serial communication:
    conn=hid[/<chip>]/usb=<bus>.<dev>[.<if>]
    conn=hid[/<chip>]/raw=<path>
    conn=hid[/<chip>]/sn=<serno>
+   conn=hid[/<chip>]/iokit=<path>
    chip can be: bu86x, ch9325, cp2110, victor
    path may contain slashes
    path and serno are "greedy" (span to the end of the spec)
@@ -210,6 +211,12 @@ or VXI communication parameters. See these examples:
  $ sigrok-cli --driver <somedriver>:conn=vxi/<ipaddr> ...
  $ sigrok-cli --driver <somedriver>:conn=usbtmc/<bus>.<addr> ...
 
+Individual device drivers _may_ implement additional semantics for the
+conn= specification, which would not apply to other drivers, yet can be
+rather useful for a given type of device.
+
+ $ sigrok-cli --driver <somedriver>:conn=sn=<serno>
+
 
 Specifying serial port parameters
 ---------------------------------
@@ -274,6 +281,20 @@ rules shipped by the system will be broken.
 Please consult the udev docs for details.
 
 
+Non-default drivers for commodity chips
+---------------------------------------
+
+Some vendors include common USB chips in their products yet assign device
+specific VID:PID pairs. Which results in the necessity for extra steps
+before the serial port can be used:
+
+- GW Instek VCP, found in GDM-8000 and probably other meters: Install the
+  vendors Windows driver to get access to a COM port. Or force the driver
+  assignment on Linux:
+    # modprobe cp210x
+    # echo 2184 0030 > /sys/bus/usb-serial/drivers/cp210x/new_id
+
+
 Cypress FX2 based devices
 -------------------------
 
@@ -389,7 +410,11 @@ a short list for convenience:
       'SI232 online' (28-29S) or 'SI232 store' (22-26x). The interface must
       be configured to the same baud rate as the host (default 9600).
       Multimeter and interface must be configured to the same address.
+ - GW Instek GDM-397: Press the "REL/RS232C (USB)" button for roughly 1 second.
+ - GW Instek VCP: See the discussion on manual driver assignment to common
+   USB to UART chips with non-default USB identification.
  - MASTECH MS6514: Press the "Setup/PC-Link" button for roughly 3 seconds.
+ - Meterman 38XR: Press the "RS232" button.
  - Metrix MX56C: Press the PRINT button to have the meter send acquisition
    data via IR. Hold the PRINT button to adjust the meter's transmission
    interval.
@@ -453,6 +478,16 @@ Example:
  $ sigrok-cli --driver ols:conn=/dev/ttyACM0 ...
 
 
+JTAGulator
+----------
+
+The Grand Idea Studio JTAGulator also implements the SUMP protocol and
+thus is covered by the OLS driver. See the vendor's wiki on details how
+to enable the Logic Analyzer mode of operation.
+
+  https://github.com/grandideastudio/jtagulator/wiki/Logic-Analyzer
+
+
 Mooshimeter
 -----------