zephyr/samples/drivers/i2c_fujitsu_fram
Torsten Rasmussen 407b49b35c cmake: use find_package to locate Zephyr
Using find_package to locate Zephyr.

Old behavior was to use $ENV{ZEPHYR_BASE} for inclusion of boiler plate
code.

Whenever an automatic run of CMake happend by the build system / IDE
then it was required that ZEPHYR_BASE was defined.
Using ZEPHYR_BASE only to locate the Zephyr package allows CMake to
cache the base variable and thus allowing subsequent invocation even
if ZEPHYR_BASE is not set in the environment.

It also removes the risk of strange build results if a user switchs
between different Zephyr based project folders and forgetting to reset
ZEPHYR_BASE before running ninja / make.

Signed-off-by: Torsten Rasmussen <Torsten.Rasmussen@nordicsemi.no>
2020-03-27 16:23:46 +01:00
..
src
CMakeLists.txt cmake: use find_package to locate Zephyr 2020-03-27 16:23:46 +01:00
README
prj.conf
sample.yaml tests: fix test identifiers 2019-12-09 15:53:44 -05:00

README

This is a sample app to read and write
the Fujitsu MB85RC256V FRAM chip via I2C
on the Quark SE Sensor Subsystem.

This assumes the slave address of FRAM is 0x50,
where A0, A1, and A2 are all tied to ground.