You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@mynewt.apache.org by GitBox <gi...@apache.org> on 2018/03/06 01:42:09 UTC
[GitHub] aditihilbert closed pull request #825: Deleting Tooling Tutorials from mynewt-core
aditihilbert closed pull request #825: Deleting Tooling Tutorials from mynewt-core
URL: https://github.com/apache/mynewt-core/pull/825
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):
diff --git a/docs/os/tutorials/segger_rtt.rst b/docs/os/tutorials/segger_rtt.rst
deleted file mode 100644
index 53840dcf3..000000000
--- a/docs/os/tutorials/segger_rtt.rst
+++ /dev/null
@@ -1,109 +0,0 @@
-SEGGER RTT Console
-------------------
-
-Objective
-~~~~~~~~~
-
-Sometimes you dont have UART on your board, or you want to use it for
-something else while still having newt logs/shell capability. With
-`SEGGER's RTT <https://www.segger.com/jlink-rtt.html>`__ capability you
-can swap UART for RTT, which is a very high-speed memory-mapped I/O.
-
-Hardware needed
-~~~~~~~~~~~~~~~
-
-You'll need a SEGGER J-Link programmer in order to use this advanced
-functionality. You might have an external J-Link programmer you're
-already using, or maybe your board has a dedicated J-Link onboard as
-some development kits do. Another possibilty is J-Link OB firmware
-available for some devices like the micro:bit.
-
-Setup the target
-~~~~~~~~~~~~~~~~
-
-We'll assume you have an existing project with some kind of
-console/shell like `Blinky with console and shell <blinky_console.html>`__
-that we're switching over to RTT from UART.
-
-**Note:** We have tested RTT with J-Link version V6.14h. We recommend
-that you upgrade your J-Link if you have an earlier version of J-Link
-installed. Earlier versions of J-Link use the BUFFER\_SIZE\_DOWN value
-defined in hw/drivers/rtt/include/rtt/SEGGER\_RTT\_Conf.h for the
-maximum number of input characters. If an input line exceeds the
-BUFFER\_SIZE\_DOWN number of characters, RTT ignores the extra
-characters. The default value is 16 characters. For example, this limit
-causes shell commands with more than 16 characters of input to fail. You
-may set the Mynewt ``RTT_BUFFER_SIZE_DOWN`` syscfg setting in your
-target to increase this value if you do not upgrade your J-Link version.
-
-We can disable uart and enable rtt with the newt target command:
-
-::
-
- newt target amend nrf52_blinky syscfg=CONSOLE_UART=0
- newt target amend nrf52_blinky syscfg=CONSOLE_RTT=1
-
-Run the target executables
-~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-Now 'run' the newt target as you'll need an active debugger process to
-attach to:
-
-::
-
- $ newt run nrf52_blinky 0
- App image succesfully generated: ~/Downloads/myapp1/bin/targets/nrf52_blinky/app/apps/blinky/blinky.img
- Loading app image into slot 1
- [~Downloads/myapp1/repos/apache-mynewt-core/hw/bsp/nrf52-thingy/nrf52-thingy_debug.sh ~/Downloads/myapp1/repos/apache-mynewt-core/hw/bsp/nrf52-thingy ~/Downloads/myapp1/bin/targets/nrf52_blinky/app/apps/blinky/blinky]
- Debugging ~/Downloads/myapp1/bin/targets/nrf52_blinky/app/apps/blinky/blinky.elf
- GNU gdb (GNU Tools for ARM Embedded Processors) 7.8.0.20150604-cvs
- Copyright (C) 2014 Free Software Foundation, Inc.
- License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
- This is free software: you are free to change and redistribute it.
- There is NO WARRANTY, to the extent permitted by law. Type "show copying"
- and "show warranty" for details.
- This GDB was configured as "--host=x86_64-apple-darwin10 --target=arm-none-eabi".
- Type "show configuration" for configuration details.
- For bug reporting instructions, please see:
- <http://www.gnu.org/software/gdb/bugs/>.
- Find the GDB manual and other documentation resources online at:
- <http://www.gnu.org/software/gdb/documentation/>.
- For help, type "help".
- Type "apropos word" to search for commands related to "word"...
- Reading symbols from ~/Downloads/myapp1/bin/targets/nrf52_blinky/app/apps/blinky/blinky.elf...done.
- 0x000000d8 in ?? ()
- Resetting target
- 0x000000dc in ?? ()
- (gdb)
-
-Connect to console
-~~~~~~~~~~~~~~~~~~
-
-In a seperate terminal window ``telnet localhost 19021`` and when you
-continue your gdb session you should see your output. If you're not
-familiar with telnet, when you're ready to exit you may by using the
-hotkey ctrl+] then typing quit
-
-::
-
- $ telnet localhost 19021
- Trying ::1...
- telnet: connect to address ::1: Connection refused
- Trying fe80::1...
- telnet: connect to address fe80::1: Connection refused
- Trying 127.0.0.1...
- Connected to localhost.
- Escape character is '^]'.
- SEGGER J-Link V6.14e - Real time terminal output
- SEGGER J-Link EDU V8.0, SN=268006294
- Process: JLinkGDBServer
-
-Then you can interact with the device:
-
-::
-
- stat
- stat
- 000262 Must specify a statistic name to dump, possible names are:
- 000262 stat
- 000262 compat>
diff --git a/docs/os/tutorials/segger_sysview.rst b/docs/os/tutorials/segger_sysview.rst
deleted file mode 100644
index d95802f40..000000000
--- a/docs/os/tutorials/segger_sysview.rst
+++ /dev/null
@@ -1,96 +0,0 @@
-SEGGER SystemView
------------------
-
-Objective
-~~~~~~~~~~~~~~~
-
-
-With `SEGGER's SystemView <https://www.segger.com/systemview.html>`__
-you can "record data from the target system while it is running. The
-recorded data is analyzed and the system behavior is visualized in
-different views."
-
-Hardware needed
-~~~~~~~~~~~~~~~
-
-You'll need a SEGGER J-Link programmer in order to use this advanced
-functionality. You might have an external J-Link programmer you're
-already using, or maybe your board has a dedicated J-Link onboard as
-some development kits do. Another possibilty is J-Link OB firmware
-available for some devices like the micro:bit.
-
-Software needed
-~~~~~~~~~~~~~~~
-
-- Download `SEGGER's SystemView
- app <https://www.segger.com/downloads/free-utilities/>`__.
-- Copy the description file from sys/sysview/SYSVIEW\_Mynewt.txt to the
- /Description/ directory of SystemView
-
-Setup the target
-~~~~~~~~~~~~~~~~
-
-We'll assume you have an existing example we're enabling SystemView on,
-in this case `blinky on nrf52 <nRF52.html>`__. We can do so with the newt
-target amend command:
-
-::
-
- newt target amend blink_nordic syscfg=OS_SYSVIEW=1
-
-Run the target executables
-~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-Now 'run' the newt target as you'll need an active debugger process to
-attach to:
-
-::
-
- $ newt run blink_nordic 0
- App image succesfully generated: ~/Downloads/myproj/bin/targets/blink_nordic/app/apps/bleprph/bleprph.img
- Loading app image into slot 1
- [~/Downloads/myproj/repos/apache-mynewt-core/hw/bsp/nrf52-thingy/nrf52-thingy_debug.sh ~/Downloads/myproj/repos/apache-mynewt-core/hw/bsp/nrf52-thingy ~/Downloads/myproj/bin/targets/blink_nordic/app/apps/bleprph/bleprph]
- Debugging ~/Downloads/myproj/bin/targets/blink_nordic/app/apps/bleprph/bleprph.elf
- GNU gdb (GNU Tools for ARM Embedded Processors) 7.8.0.20150604-cvs
- Copyright (C) 2014 Free Software Foundation, Inc.
- License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
- This is free software: you are free to change and redistribute it.
- There is NO WARRANTY, to the extent permitted by law. Type "show copying"
- and "show warranty" for details.
- This GDB was configured as "--host=x86_64-apple-darwin10 --target=arm-none-eabi".
- Type "show configuration" for configuration details.
- For bug reporting instructions, please see:
- <http://www.gnu.org/software/gdb/bugs/>.
- Find the GDB manual and other documentation resources online at:
- <http://www.gnu.org/software/gdb/documentation/>.
- For help, type "help".
- Type "apropos word" to search for commands related to "word"...
- Reading symbols from ~/Downloads/myproj/bin/targets/blink_nordic/app/apps/bleprph/bleprph.elf...done.
- 0x000000d8 in ?? ()
- Resetting target
- 0x000000dc in ?? ()
-
-Launch the app
-~~~~~~~~~~~~~~
-
-Launch the app and press **OK** in the System Information dialog box.
-
-.. figure:: pics/segger_sysview1.png
- :alt: SEGGER SystemView
-
- SEGGER SystemView
-
-Select \*\* Target > Start Recording \*\* and press **OK** in the
-Configuration dialog box.
-
-.. figure:: pics/segger_sysview_start_record.png
- :alt: SEGGER SystemView Start Recording
-
- SEGGER SystemView Start Recording
-
-You should see the recording for your Mynewt application.
-
-.. figure:: pics/segger_sysview_recording.png
- :alt: SEGGER SystemView Recording
-
- SEGGER SystemView Recording
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services