Posted   by 

System Sensor Driver



The terms of the software license agreement included with any software you download will control your use of the software.

INTEL SOFTWARE LICENSE AGREEMENT
  • System Component Radar Sensor J428 System Warnings and Icons Adaptive Cruise Control (ACC) controls the speed set by the driver, based on the speed of vehicles ahead. If a vehicle is detected in front of the Volkswagen, ACC keeps a constant set distance from the other vehicle.
  • System effectiveness is dependent on many factors including road, weather and vehicle conditions. See Owner's Manual for additional limitations and details. Dynamic Radar Cruise Control (DRCC) is designed to assist the driver and is not a substitute for safe and attentive driving practices.

The tire pressure monitoring system’s (TPMS) primary function is to make the driver aware of the state of tire pressure within the tires. Under normal system operations, the TPMS system will alert the driver when one or more affected tires PSI reading falls below 25% of the vehicle’s placard. When the tire sensor indicates “low tire pressure,” it sends a radio frequency (RF) signal of.

IMPORTANT - READ BEFORE COPYING, INSTALLING OR USING.

Do not use or load this software and any associated materials (collectively,

the 'Software') until you have carefully read the following terms and

conditions. By loading or using the Software, you agree to the terms of this

Agreement. If you do not wish to so agree, do not install or use the Software.

LICENSES: Please Note:

- If you are a network administrator, the 'Site License' below shall

apply to you.

- If you are an end user, the 'Single User License' shall apply to you.

- If you are an original equipment manufacturer (OEM), the 'OEM License'

shall apply to you.

SITE LICENSE. You may copy the Software onto your organization's computers

for your organization's use, and you may make a reasonable number of

back-up copies of the Software, subject to these conditions:

1. This Software is licensed for use only in conjunction with Intel

component products. Use of the Software in conjunction with non-Intel

component products is not licensed hereunder.

2. You may not copy, modify, rent, sell, distribute or transfer any part

of the Software except as provided in this Agreement, and you agree to

prevent unauthorized copying of the Software.

3. You may not reverse engineer, decompile, or disassemble the Software.

4. You may not sublicense or permit simultaneous use of the Software by

more than one user.

5. The Software may include portions offered on terms in addition to those

set out here, as set out in a license accompanying those portions.

SINGLE USER LICENSE. You may copy the Software onto a single computer for

your personal, noncommercial use, and you may make one back-up copy of the

Software, subject to these conditions:

1. This Software is licensed for use only in conjunction with Intel

component products. Use of the Software in conjunction with non-Intel

component products is not licensed hereunder.

2. You may not copy, modify, rent, sell, distribute or transfer any part

of the Software except as provided in this Agreement, and you agree to

prevent unauthorized copying of the Software.

3. You may not reverse engineer, decompile, or disassemble the Software.

4. You may not sublicense or permit simultaneous use of the Software by

more than one user.

5. The Software may include portions offered on terms in addition to those

set out here, as set out in a license accompanying those portions.

OEM LICENSE: You may reproduce and distribute the Software only as an

integral part of or incorporated in Your product or as a standalone

Software maintenance update for existing end users of Your products,

excluding any other standalone products, subject to these conditions:

1. This Software is licensed for use only in conjunction with Intel

component products. Use of the Software in conjunction with non-Intel

component products is not licensed hereunder.

2. You may not copy, modify, rent, sell, distribute or transfer any part

of the Software except as provided in this Agreement, and you agree to

prevent unauthorized copying of the Software.

3. You may not reverse engineer, decompile, or disassemble the Software.

4. You may only distribute the Software to your customers pursuant to a

written license agreement. Such license agreement may be a 'break-the-

seal' license agreement. At a minimum such license shall safeguard

Intel's ownership rights to the Software.

5. The Software may include portions offered on terms in addition to those

set out here, as set out in a license accompanying those portions.

NO OTHER RIGHTS. No rights or licenses are granted by Intel to You, expressly

or by implication, with respect to any proprietary information or patent,

copyright, mask work, trademark, trade secret, or other intellectual property

right owned or controlled by Intel, except as expressly provided in this

Agreement.

System Sensor Driver

OWNERSHIP OF SOFTWARE AND COPYRIGHTS. Title to all copies of the Software

remains with Intel or its suppliers. The Software is copyrighted and

protected by the laws of the United States and other countries, and

international treaty provisions. You may not remove any copyright notices

from the Software. Intel may make changes to the Software, or to items

referenced therein, at any time without notice, but is not obligated to

support or update the Software. Except as otherwise expressly provided, Intel

grants no express or implied right under Intel patents, copyrights,

trademarks, or other intellectual property rights. You may transfer the

Software only if the recipient agrees to be fully bound by these terms and if

you retain no copies of the Software.

LIMITED MEDIA WARRANTY. If the Software has been delivered by Intel on

physical media, Intel warrants the media to be free from material physical

Sensor

defects for a period of ninety days after delivery by Intel. If such a defect

is found, return the media to Intel for replacement or alternate delivery of

the Software as Intel may select.

EXCLUSION OF OTHER WARRANTIES. EXCEPT AS PROVIDED ABOVE, THE SOFTWARE IS

PROVIDED 'AS IS' WITHOUT ANY EXPRESS OR IMPLIED WARRANTY OF ANY KIND

INCLUDING WARRANTIES OF MERCHANTABILITY, NONINFRINGEMENT, OR FITNESS FOR A

PARTICULAR PURPOSE. Intel does not warrant or assume responsibility for the

accuracy or completeness of any information, text, graphics, links or other

items contained within the Software.

LIMITATION OF LIABILITY. IN NO EVENT SHALL INTEL OR ITS SUPPLIERS BE LIABLE

FOR ANY DAMAGES WHATSOEVER (INCLUDING, WITHOUT LIMITATION, LOST PROFITS,

BUSINESS INTERRUPTION, OR LOST INFORMATION) ARISING OUT OF THE USE OF OR

System Sensor Driver Installer

INABILITY TO USE THE SOFTWARE, EVEN IF INTEL HAS BEEN ADVISED OF THE

POSSIBILITY OF SUCH DAMAGES. SOME JURISDICTIONS PROHIBIT EXCLUSION OR

LIMITATION OF LIABILITY FOR IMPLIED WARRANTIES OR CONSEQUENTIAL OR INCIDENTAL

DAMAGES, SO THE ABOVE LIMITATION MAY NOT APPLY TO YOU. YOU MAY ALSO HAVE

OTHER LEGAL RIGHTS THAT VARY FROM JURISDICTION TO JURISDICTION.

TERMINATION OF THIS AGREEMENT. Intel may terminate this Agreement at any time

if you violate its terms. Upon termination, you will immediately destroy the

Software or return all copies of the Software to Intel.

APPLICABLE LAWS. Claims arising under this Agreement shall be governed by the

laws of California, excluding its principles of conflict of laws and the

United Nations Convention on Contracts for the Sale of Goods. You may not

System Sensor Driver Updater

export the Software in violation of applicable export laws and regulations.

Intel is not obligated under any other agreements unless they are in writing

and signed by an authorized representative of Intel.

GOVERNMENT RESTRICTED RIGHTS. The Software is provided with 'RESTRICTED

RIGHTS.' Use, duplication, or disclosure by the Government is subject to

restrictions as set forth in FAR52.227-14 and DFAR252.227-7013 et seq. or its

successor. Use of the Software by the Government constitutes acknowledgment

of Intel's proprietary rights therein. Contractor or Manufacturer is Intel

2200 Mission College Blvd., Santa Clara, CA 95052.

-->

This topic shows you how to install the sensor driver on a development board, after you update the secondary system description table (SSDT) for the development board.

This topic uses the Sharks Cove development board and an ADXL345 accelerometer as a case study, to help explain the process of installing a sensor driver on a development board. So if you want to perform the tasks presented in this topic, you must first install an operating system on the Sharks Cove. For more information about how to do that, see Download kits and tools for Windows 10, and follow the instructions to install Windows 10.

After you finish installing the operating system on the Sharks Cove, See Build the sensor driver to learn how to build a driver in Microsoft Visual Studio. Then return here to continue.

The accelerometer is attached to the Sharks Cove via the I2C bus. Peripherals that are connected to the I2C bus are enumerated via the Advanced Configuration and Power Interface (ACPI). So the sample driver for the accelerometer was developed to support ACPI instead of Plug and Play.

To make the Sharks Cove's ACPI driver aware of the new device (the accelerometer) on the I2C bus, you must add information about the accelerometer to the SSDT on the Sharks Cove. This table describes the hardware resources and interrupt requirements for a hardware platform's devices, including attached peripherals like the accelerometer.

Before you begin

System Sensor Driver

Before you start performing the tasks outlined below, please make sure that your Sharks Cove is set up as shown in the following image:

Retrieve and review the default SSDT

This section shows you how to use the ACPI Source Language (ASL) compiler to retrieve the factory default SSDT for the Sharks Cove, and then review it. You will also learn how to replace the default SSDT with an updated one.

  1. On your development computer, navigate to the following location to copy the ASL compiler:c:Program Files (x86)Windows Kits10Toolsx86ACPIVerify

  2. Copy the Asl.exe file, and save it to a flash drive.

  3. On the Sharks Cove, create a Tools folder in the root directory. Then Attach the flash drive to the Sharks Cove's USB hub, and copy the Asl.exe file to the Tools folder.

  4. Open a Command prompt window as an administrator, and enter the following commands:cdtoolsdirMake sure that the Asl.exe file is listed in the directory.

  5. Invoke the ASL compiler and create an ASL file by entering the following command:asl /tab=ssdt

  6. Make sure that the ASL file was created successfully by entering the following command:dir ssdt.asl

  7. Open the ASL file in Notepad by entering the following command:notepad ssdt.aslReview the ASL file, and notice that there are no references to the accelerometer, or the I2C bus.

  8. Close Notepad. Then enter the following command in the Command prompt window, to rename the ssdt.asl file.ren ssdt.asl ssdt-old.aslThen use the dir command to make sure that the file is now listed as ssdt-old.asl.

Update the default SSDT

Perform the following tasks to update the SSDT, and load it to replace the factory default version. The updated SSDT will be stored in a potion of memory called battery-backed RAM. So make sure that the button cell (battery) that came with your Sharks Cove is plugged into its socket.

  1. Copy the following updated SSDT and paste it into a new instance of Notepad.

  2. In Notepad, select File > Save As. Then select the Save as type dropdown box, and select All Files.

  3. In the File name box, type ssdt.asl, then select Save, and close Notepad.

  4. In the Command prompt window, use the dir command to make sure that you can see the default file now listed as ssdt-old.asl, and the new file listed as ssdt.asl.

  5. Compile the ssdt.asl file into a format that the Sharks Cove can understand by entering the following command:asl ssdt.asl

  6. Verify that the compiled file was successfully created in Step 3 by entering the following command:dir ssdt.amlYou should see the ssdt.aml file listed in the tools directory.

  7. Load the compiled file into battery-backed RAM by entering the following command:asl /loadtable ssdt.aml

Turn on testsigning

Before you install the sample sensor driver, you must turn on testsigning. Perform the following tasks to turn on testsigning. Perform the following steps to install the sensor driver via Device Manager.

  1. In the Command prompt window, enter the following command to see whether testsigning is already turned on.
    bcdedit /enum

  2. If you see a listing similar to the following, showing an entry for testsigning, with its value set to yes then skip to Step 5.

  3. If you need to turn on test signing, then enter the following command:bcdedit /set testsigning on

  4. Repeat Step 1 (in this exercise) to verify that the value of the testsigning system variable is now set to 'yes' in the Windows Boot Loader list.

  5. Restart the Sharks Cove. As the board restarts, hold the Volume-up button for about 2 seconds, to enter system setup (UEFI) window.

  6. In the UEFI window, select Device Manager > System Setup > Boot, and make sure that UEFI Security Boot is set to <Disable>.

  7. Save your changes and exit the UEFI window.

Sensor System With Driver Alerts

Install the sensor driver

There are four main methods for installing a driver on the Sharks Cove board:

  • Download the driver from a network source directly onto the Sharks Cove.
  • Develop the sensor driver on a host computer, with your Sharks Cove connected as a provisioned client. Then deploy the driver from the host computer to the Sharks Cove.
  • Copy the driver package to a flash drive and attach the flash drive to the Sharks Cove. Then use the devcon command from a Command prompt window to install the driver manually.
  • Copy the driver package to a flash drive and attach the flash drive to the Sharks Cove. Then install the driver manually via Device Manager.

For simplicity, we will use the last method in the preceding list. Perform the following steps to manually install the sensor driver via Device Manager.

You must connect your sensor to the Sharks Cove before you install the sensor driver. For information about how to modify the ADXL345 accelerometer breakout board from SparkFun, to get it to work with the sample sensor driver, see Prepare your sensor test board. And for information about how to connect the sensor breakout board to the Sharks Cove, see Connect your sensor to the Sharks Cove board.

  1. Make sure that the ADXL345 accelerometer is connected to the Sharks Cove J1C1 connector, then power up the Sharks Cove.

  2. Attach a flash drive with the sensor driver to the powered USB hub connected to the Sharks Cove. For example, this can be the flash drive onto which you saved the driver that you built by following the steps in Build the sensor driver.

  3. Open Device Manager, and look for an 'Unknown device' in the Other devices node with a yellow bang symbol against it (see the following screen shot).

  4. Select and hold (or right-click) the device with the yellow bang (listed as Unknown device), and select Update Driver Software, and select Browse my computer for driver software.

  5. Browse to the ADXL345 driver on the flash drive, then select Next. Follow the screen prompts to install the sensor driver.

  6. After the sample sensor driver is successfully installed, Device Manager displays the sensor as shown in the following screen shot.

For information about how to use Visual Studio to deploy a driver to a client computer (like the Sharks Cove), see Deploying a Driver to a Test Computer.

After successfully installing the sample sensor driver, see Test your universal sensor driver for information about how to test a sensor.