Septentrio Port Devices Driver Download

  

When you plug the device into your USB, Windows will look for the associated driver, if it cannot find this driver then you will be prompted to insert the driver disc that came with your device. Common USB Device errors are ‘ usb port not working ‘, ‘device descriptor request failed error’ or ‘bugcodeusbdriver’ issues. If you need to download a driver for a PreSonus device; the most current release, beta and legacy drivers are available on our website. The most current drivers will be listed at the top of the downloads page, followed by beta drivers and then below that you will find older legacy versions of the driver in case the current or beta releases are. Since 1985, SIIG Inc. Has led the way in creating IT and AV connectivity solutions you can trust. Built on core values of professional integrity with customer satisfaction as the focus point, our company is committed to providing top-notch service, support, and product solutions that elevate your AV and IT user experience. PC Pitstop - PC Performance Roots. PC Pitstop began in 1999 with an emphasis on computer diagnostics and maintenance. During the early days of the dot com boom, our online PC maintenance tools were skyrocketing.

-->

This article clarifies some confusion that vendors have experienced about how hardware that complies with PCI Power Management (PCI-PM) interacts with device drivers in the operating system and about how PCI-PM integrates with ACPI. For more information, see https://www.uefi.org/specifications

Device drivers and PCI power management

This discussion assumes that you are familiar with how Windows Driver Model (WDM) drivers handle power management events, as described in the current Windows DDK. In general, the responsibilities for device drivers are as follows:

  • Bus drivers: Bus drivers are responsible for enumerating, configuring, and controlling devices. For PCI-PM, the PCI driver is responsible for reading the PCI-PM registers to determine the capabilities of the hardware. When POWER IRPs request power state changes, the PCI driver writes to the PCI power management registers to set the hardware to different Dx states.

    When a device is enabled for wake-up, the PCI driver writes to PCI-PM registers to enable the device to fire PME (ACPI will also take an action, see the next section). Finally, when ACPI determines that the PCI bus is waking the system, the PCI driver scans PCI configuration space looking for which device is asserting PME, disables PME in that device, and notifies the driver for that device.

  • Device driver: The specific driver for the device is responsible for saving and restoring device context, and requesting power state changes as the policy owner for the device. When the device driver receives a POWER IRP requesting a lower device power state change, the device driver is responsible for saving any proprietary device context needed to later turn on the device. In some cases, there may be nothing to save.

PCI-PM registers are strictly the domain of the PCI driver--the IHV's device driver does not need to access any of these registers. Doing so would cause the system to not work reliably. The device driver's responsibility is to perform only proprietary actions.

Integrating ACPI and PCI PM

Some devices, particularly motherboard video devices in portables, may require both PCI Power Management as well as ACPI Source Language Assembler (ASL) to completely power manage the device. The PCI Power Management registers would control the internal state of a device, such as internal clocks and power planes. ASL would control the external state, such as external clocks and power planes, or in the case of video controllers, ASL would control the video backlights. Note that ASL and PCI-PM can only be combined on motherboard devices.

The OnNow architecture is a layered architecture, handling the integration of the device driver, PCI driver, and ACPI driver (and ASL) naturally. The following scenarios show the order in which drivers are called to handle these devices.

Note

For the above scenarios to work as described, a WDM driver must forward POWER IRPs correctly as described in the current version of the Microsoft Windows DDK.

Scenario 1: Turning off a device

  1. Device driver: Saves proprietary device state.
  2. PCI driver: Saves Plug and Play configuration, disables the device (interrupts and BARs), and puts the device in D3 using PCI-PM registers.
  3. ACPI driver: Runs ASL code (_PS3 and _OFF for power resources no longer in use) to control the state external to the chip.

Scenario 2: PCI power management and device drivers

  1. ACPI driver: Runs ASL code (_PS0 and _ON for any OnNow required power resources) to control the state external to the chip.
  2. PCI driver: Puts the device in D0 using PCI-PM registers and restores Plug and Play configuration (interrupts and BARs--these might be different from what the device was previously on).
  3. Device driver: Restores proprietary context in the device.

Septentrio Port Devices Driver Download Windows 7

Scenario 3: Enabling wake-up

  1. Device driver: Sets proprietary registers in the chip to enable wake-up. For example, in pattern matching network wake-up, this is when the patterns would be programmed into the adapter.
  2. PCI driver: Sets the wake-up enable bits in the PCI PM registers to allow the device to assert PME.
  3. ACPI driver: Enables the GPE in the chip set associated with PME (as described by the _PRW object listed under the root PCI bus).

Scenario 4: Wake-up

  1. ACPI driver: Wakes and scans the GPE status bits for wake-up events, disabling GPEs for set GPE status bits, and running any _Lxx or _Exx methods associated with set GPE bits. In response to a wake-up notification on the PCI bus, the ACPI driver will complete the PCI driver's WAIT_WAKE IRP to notify the PCI driver that it is waking the system.
  2. PCI driver: Scans configuration space looking for any devices with a set PME status bit. For each device, it disables PME and completes the WAIT_WAKE IRP for that device to inform the driver that it is asserting wake-up. The PCI driver stops scanning for wake devices when it has made a complete pass through all PCI devices having not found any asserting PME and when PME stops being asserted.
  3. Device driver: Requests the device be put in D0 (see scenario 2) and sets any proprietary registers in the chip required to handle the wake-up event.

Call to action on PCI power management and device drivers

  • Integrate ACPI and PCI-PM capabilities into your devices as described in this article.
  • The PCI Power Management specification is available at https://www.pcisig.com. This link leaves the Microsoft.com site.
  • ACPI Specification available at https://www.uefi.org/specifications. This link leaves the Microsoft.com site.
  • The ACPI Component Architecture (ACPICA) compiler can be found at https://acpica.org/downloads/binary-tools.

The CH340 chip is used by a number of Arduino compatible boards to provide USB connectivity, you may need to install a driver, don’t panic, it’s easier than falling off a log, and much less painful.


Windows

(Manufacturer’s Chinese Info Link)

  1. Download the Windows CH340 Driver
  2. Unzip the file
  3. Run the installer which you unzipped
  4. In the Arduino IDE when the CH340 is connected you will see a COM Port in the Tools > Serial Port menu, the COM number for your device may vary depending on your system.

Older Windows Driver Version and Instructions

  1. Download the Windows CH340 Driver
  2. Unzip the folder.
  3. If you are running a 64Bit Windows: – run the SETUP_64.EXE installer.
  4. If you are running a 32Bit Windows: – run the SETUP_32.EXE installer.
  5. If you don’t know, try the 64 bit and if it doesn’t work, the 32 bit.
  6. In the Arduino IDE when the CH340 is connected you will see a COM Port in the Tools > Serial Port menu, the COM number for your device may vary depending on your system.

Macintosh

(Manufacturer’s Chinese Info Link)

The following github has up to day pkg files for 1.3, 1.4 and 1.5 at time of writing, thanks to Joshua Wallis for bringing this to my attention…

Direct Download Links (from the github repo above):

Septentrio Port Devices Driver Download Win 7

See the github link above for installation instructions if you need them.

Previous macinstosh downloads if the above doesn’t work for you…

(V1.3) Download the CH340 Macintosh Signed Driver for Mavericks (10.9), Yosemite (10.10) and El Capitan (10.11) and Sierra (10.12)

Inside the zip file you will find a PDF and a “pkg” file, short version, double click the pkg file, the PDF has some extra information.

Septentrio Port Devices Driver Download

OSX Sierra (10.12) Note

A kindly user, Maarten Segers reports

FYI, the driver documented here WILL crash on OSX Sierra.

Make sure to use this one instead: https://github.com/MPParsley/ch340g-ch34g-ch34x-mac-os-x-driver

I can personally not test on MacOS and can not vouch for the above drivers at github, but there you go.

See uninstalling information at the bottom of the page if the driver causes problems for you.

Here is an older version of the Mac driver, NOT FOR 10.12 Sierra

(V1.0) Download the CH340 Macintosh Signed Driver for Mavericks (10.9), Yosemite (10.10) and El Capitan (10.11)

Linux

(Manufacturer’s Chinese Info Link)

Drivers are almost certainly built into your Linux kernel already and it will probably just work as soon as you plug it in. If not you can download the Linux CH340 Driver (but I’d recommend just upgrading your Linux install so that you get the “built in” one).

Septentrio Port Devices Driver Downloads

Uninstalling From Macinstosh

Septentrio Port Devices Driver Download

A couple of Mac users have said “the driver crashes my mac Sierra how do I uninstall”.

Firstly regards the crash make sure you installed the 1.3 version of the driver, not the old one. You could download it directly from the Manufacturers Website in case they have issued an update since I wrote this page.

Secondly a quick google search reveals that this is how you uninstall:

  1. Open a terminal and type: cd /Library/Extensions/
  2. Verify that the .kext file is present: ls grep usbserial.kext
  3. Output should be: usbserial.kext
  4. Then type: sudo rm -R usbserial.kext
  5. Verify that the .kext file has been removed: ls grep usbserial.kext
  6. Output should be empty.
  7. After you should remove the files stored in receipts folder: cd /private/var/db/receipts/
  8. Find the enties: ls grep usbserial*
  9. Output should be: codebender.cc.ch34xinstaller.usbserial.pkg.bom codebender.cc.ch34xinstaller.usbserial.pkg.plist
  10. Remove each one of the files of the above list: sudo rm -r filename`