michaelh/zephyr
1
0
Fork 0
Code Releases Activity

doc : getting_started : correct path

Browse source 
The path to the sample applications is a mis-match of previous and the
current values.  Correcting it to represent the new value.

Change-Id: I54ffe823335b95f1076b1346d149b359b4f2e7bd
Signed-off-by: Dan Kalowsky <daniel.kalowsky@intel.com>
This commit is contained in:
Dan Kalowsky 2016-02-23 14:09:41 -08:00 • committed by Daniel Kalowsky
commit 8d0129656c
2 changed files with 4 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

4
doc/getting_started/building_zephyr.rst
View file

@ -52,8 +52,8 @@ architecture:
$ make help $ make help
The sample projects for the microkernel and the nanokernel are found The sample projects for the microkernel and the nanokernel are found
at :file:`$ZEPHYR_BASE/samples/microkernel/apps` and at :file:`$ZEPHYR_BASE/samples` with each sample having a microkernel
:file:`$ZEPHYR_BASE/samples/nanokernel/apps` respectively. and nanokernel specific build.
After building an application successfully, the results can be found in the After building an application successfully, the results can be found in the
:file:`outdir` sub-directory under the application root directory. :file:`outdir` sub-directory under the application root directory.

4
doc/kernel/nanokernel/nanokernel_kernel_event_logger.rst
View file

@ -266,8 +266,8 @@ Example: Retrieving Profiling Messages
.. note:: .. note::
To see an example that shows how to collect the kernel event data, check the sample To see an example that shows how to collect the kernel event data, check the
project: :file:`samples/microkernel/apps/kernel_event_logger_sample`. project :file:`samples/kernel_event_logger`.
Example: Adding a Kernel Event Logging Point Example: Adding a Kernel Event Logging Point
============================================ ============================================