SECO - Intel Amston Lake driver commands

The tables below provide a summary of driver commands for SECO Amston Lake platform.

Any other drivers used by the buildfile for SECO Amston Lake platform are available as part of the generic driver commands. For more information about the generic commands, see the Generic x86_64_Driver Commands chapter in this guide. For more information about these and other commands, see the QNX OSUtilities Reference.

Here are the SECO Amston Lake-specific drivers:

ECM Server
Resource manager that controls the MEC170 embedded controller and provides shared access for its clients
I2C
Client of the ECM server providing access to I²C devices managed through the MEC170
Watchdog
Client of the ECM server that monitors system health and triggers reset on failure
Note:
The commands summarized below represent the commands that are used on SECO Amston Lake platform. We've indicated which commands are board-specific. For SATA, NVMe, USB and network driver and other drivers, see Generic x86_64_Driver Commands or more information, see the buildfiles.

ECM Server

Device ecm-mec170x
Commands

ecm-mec170x

Required binaries ecm-mec170x
Source location src/utils/ecm-mec170x

Options:

Here are the options you can use with the ecm-mec170x command:

-p
Thread priority. Default is to Inherit

I2C

Device I2C
Commands

i2c-mec170 -d10 --u10

Required binaries i2c-mec170, isendrecv, isend
Source location src/hardware/i2c/mec170

Options:

There are SECO Amston Lake specific (single-dash) and generic (double-dash) options available.

-d
bus_num: I2C bus number. Default: 10
-v
Increase verbosity. Default: 0

Generic options:

These are generic options for the driver:

--b bus_speed
The default bus speed. If this option isn't specified, the default is 100000.
--u unit
Unit number. Number to append to device name prefix (/dev/i2c). The default is 0.

Example:

i2c-mec170 -d 10 --u 10 -v
Note:
You must start the ecm-mec170x (ECM Server) before starting the I2C driver.

Watchdog

Device Watchdog
Commands

wdtkick -d 100 -e 30000 -r 29000 -s 29000

Required binaries wdtkick
Source location src/hardware/support/intel/seco/wdtkick

Options:

Here are the options you can use with the wdtkick command:

-p
Thread priority. Default is to Inherit
-d
Initial delay for the WDT in milliseconds. Default: 100
-e
EventTimeout: WDT timeout in milliseconds to trigger a watchdog event. Default: 30000
-r
ResetTimeout: WDT timeout in milliseconds to trigger a system reset. Default: 29000
-s
sleep_period: Period between each WDT kick in milliseconds. Default: 29000 To ensure proper event handling, the sleep_period should always be set to a value greater than the EventTimeout.

Example:

 wdtkick -t 5000
Note:
It is recommended that you run the Watchdog timer early when you boot your system. For this reason, run the Watchdog timer early in your buildfile.
Note:
You must start the ecm-mec170x (ECM Server) before starting the Watchdog driver.
Page updated: