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 | ||
| README | ||
| prj.conf | ||
README
This sample application illustrates how to use the I2C APIs from Zephyr. The slave device (STTS751) is present in Quark SE devboard so no wiring instructions are required in order to get this sample working. This is a very simple application which reads the value from the temperature register from STTS751 sensor.