message: Add 'Running non-binary ...` section to renode.md
diff: @@ -73,6 +73,33 @@ failing.
  # Running a non-test Binary with Renode
  -It may be useful to run binaries on Renode that are not tests, independent of
  -the robot framework. We will be adding some documentation for that in this
  -section.
  +Renode can also be used to run and debug binaries interactively.
  +For example, to debug `kernel_addr_test` on Bluepill platform, run Renode:
  +
  +```
  +tensorflow/lite/micro/tools/make/downloads/renode/renode
  +```
  +and issue following commands:
  +```
  +mach create
  +machine LoadPlatformDescription @platforms/cpus/stm32f103.repl
  +# Create additional semihosting interface peripheral
  +machine LoadPlatformDescriptionFromString "uartSemihosting: UART.SemihostingUart @ cpu"
  +# Open separate window for semihosting UART output
  +showAnalyzer sysbus.cpu.uartSemihosting
  +# Load ELF file
  +sysbus LoadELF @tensorflow/lite/micro/tools/make/gen/bluepill_cortex-m3/bin/kernel_add_test
  +# Start simulation
  +start
  +```
  +You can also connect GDB to the simulation.
  +To do that, start the GDB server in Renode before issuing the `start` command:
  +```
  +machine StartGdbServer 3333
  +```
  +Than you can connect from GDB with:
  +```
  +target remote localhost:3333
  +```
  +
  +For further reference please see the [Renode documentation](https://renode.readthedocs.io/en/latest/).
  