f62d86c42b
Using ARCH variable to select different configurations for the different architectures is misleading and conflicts with the variable ARCH being used by the build system. The variable is not needed, it is application specific and an application can be built without the need to specify ARCH on the command line. This is yet another item specific to samples and test cases that wrongfully being used and documented for every application. We need to use another variable and just make it clear it is specific to samples and how they are written. One possible solution is to have a script that gets the architecture based on the board being used. Attachments Jira: ZEP-238 Change-Id: Ieccbc087a41858fb96fb361c0aaa04705e968a4e Signed-off-by: Anas Nashif <anas.nashif@intel.com> |
||
---|---|---|
.. | ||
src | ||
Makefile | ||
prj.conf | ||
README |
I2C LSM9DS0 Sample Application ============================== This sample application illustrates how to use I2C APIs from Zephyr. It requires an external device in order to work. The external device is the accelerometer from LSM9DS0. The datasheet can be found in: https://www.adafruit.com/datasheets/LSM9DS0.pdf The application is very simple. It simply reads the 'WHO AM I' register from the accelerometer and check if matches with the value described in the datasheet. Below follows the wiring information for each board this samples has been tested. --------------+-------------------+------------------ | LSM9DS0 pin | Quark SE Devboard | Quark D2000 CRB | | | pin | pin | |-------------+-------------------+-----------------| | VIN | P4 pin 1 | J25 pin 1 | | GND | P4 pin 43 | J25 pin 2 | | SCL | P4 pin 31 | J21 pin 6 | | SDA | P4 pin 33 | J21 pin 5 | | CSG | P4 pin 29 | J25 pin 1 | | SDOG | P4 pin 17 | J25 pin 2 | --------------+-------------------+------------------