diff options
| author | Paul Sokolovsky <pfalcon@users.sourceforge.net> | 2017-02-17 22:06:52 +0300 |
|---|---|---|
| committer | Paul Sokolovsky <pfalcon@users.sourceforge.net> | 2017-02-17 22:08:42 +0300 |
| commit | 3d739eb398e44c3151bb999fcb3427b5184b4f58 (patch) | |
| tree | 967a581b89dae5d4b847410fd6808f4809e09642 | |
| parent | d80df91ef2818ccef3185c9ecffcc8c396cc7d9f (diff) | |
zephyr/README: Network startup issues with frdm_k64f resolved.
But leave a generic warning that users should be aware of Zephyr's
limitations/issues for a board they use.
| -rw-r--r-- | zephyr/README.md | 10 |
1 files changed, 6 insertions, 4 deletions
diff --git a/zephyr/README.md b/zephyr/README.md index 65729df5b..6e9e5d849 100644 --- a/zephyr/README.md +++ b/zephyr/README.md @@ -59,10 +59,12 @@ it's a sign that you didn't followed instructions above. If you would like to just run it quickly without extra setup, see "minimal" build below. For deploying/flashing a firmware on a real board, follow Zephyr -documentation for a given board (mind again that networking is enabled -for the build, so you should be aware of known issues for a particular -board; for example, frdm_k64f requires Ethernet cable connected to both -board and host or it will hang/crash on startup). +documentation for a given board, including known issues for that board +(if any). (Mind again that networking is enabled for the default build, +so you should know if there're any special requirements in that regard, +cf. for example QEMU networking requirements above; real hardware boards +generally should not have any special requirements, unless there're known +issues). Quick example |