doc : getting_started : correct path
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:
parent
cfed6d8286
commit
8d0129656c
2 changed files with 4 additions and 4 deletions
|
@ -52,8 +52,8 @@ architecture:
|
|||
$ make help
|
||||
|
||||
The sample projects for the microkernel and the nanokernel are found
|
||||
at :file:`$ZEPHYR_BASE/samples/microkernel/apps` and
|
||||
:file:`$ZEPHYR_BASE/samples/nanokernel/apps` respectively.
|
||||
at :file:`$ZEPHYR_BASE/samples` with each sample having a microkernel
|
||||
and nanokernel specific build.
|
||||
After building an application successfully, the results can be found in the
|
||||
:file:`outdir` sub-directory under the application root directory.
|
||||
|
||||
|
|
|
@ -266,8 +266,8 @@ Example: Retrieving Profiling Messages
|
|||
|
||||
.. note::
|
||||
|
||||
To see an example that shows how to collect the kernel event data, check the sample
|
||||
project: :file:`samples/microkernel/apps/kernel_event_logger_sample`.
|
||||
To see an example that shows how to collect the kernel event data, check the
|
||||
project :file:`samples/kernel_event_logger`.
|
||||
|
||||
Example: Adding a Kernel Event Logging Point
|
||||
============================================
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue