armv7m4: add stlink host reset

[maska989]

JIRA: CI-433

Description

Implemented soft reset for host environment to run test runner without using GPIO's.

Motivation and Context

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

How Has This Been Tested?

• Already covered by automatic testing.
• New test added: (add PR link here).
• Tested by hand on: armv7m4-stm32l4x6-nucleo (On host env).

Checklist:

• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have added tests to cover my changes.
• All new and existing linter checks and tests passed.
• My changes generate no new compilation warnings for any of the targets.

Special treatment

• This PR needs additional PRs to work (list the PRs, preferably in merge-order).
  trunner: wait for possible plo interruption #336
• I will merge this PR by myself when appropriate.

[github-actions]

Unit Test Results

7 218 tests   - 242   6 527 ✅  - 217   36m 43s ⏱️ - 1m 57s
  420 suites ±  0     686 💤  -  29 
    1 files   ±  0       5 ❌ +  4 

For more details on these failures, see this check.

Results for commit fb0aa8f. ± Comparison against base commit 04b1486.

This pull request removes 246 and adds 4 tests. Note that renamed tests count towards both.

phoenix-rtos-tests/ioctl/unit ‑ armv7m4-stm32l4x6-nucleo:phoenix-rtos-tests/ioctl/unit.ioctl.data_in
phoenix-rtos-tests/ioctl/unit ‑ armv7m4-stm32l4x6-nucleo:phoenix-rtos-tests/ioctl/unit.ioctl.data_in_big
phoenix-rtos-tests/ioctl/unit ‑ armv7m4-stm32l4x6-nucleo:phoenix-rtos-tests/ioctl/unit.ioctl.data_inout
phoenix-rtos-tests/ioctl/unit ‑ armv7m4-stm32l4x6-nucleo:phoenix-rtos-tests/ioctl/unit.ioctl.data_inout_big
phoenix-rtos-tests/ioctl/unit ‑ armv7m4-stm32l4x6-nucleo:phoenix-rtos-tests/ioctl/unit.ioctl.data_out
phoenix-rtos-tests/ioctl/unit ‑ armv7m4-stm32l4x6-nucleo:phoenix-rtos-tests/ioctl/unit.ioctl.data_out_big
phoenix-rtos-tests/ioctl/unit ‑ armv7m4-stm32l4x6-nucleo:phoenix-rtos-tests/ioctl/unit.ioctl.in_val
phoenix-rtos-tests/ioctl/unit ‑ armv7m4-stm32l4x6-nucleo:phoenix-rtos-tests/ioctl/unit.ioctl.invalid_req
phoenix-rtos-tests/ioctl/unit ‑ armv7m4-stm32l4x6-nucleo:phoenix-rtos-tests/ioctl/unit.ioctl.no_data
phoenix-rtos-tests/ioctl/unit ‑ armv7m4-stm32l4x6-nucleo:phoenix-rtos-tests/ioctl/unit.ioctl.not_valid_fd
…

phoenix-rtos-tests/ioctl/unit ‑ armv7m4-stm32l4x6-nucleo:phoenix-rtos-tests/ioctl/unit
phoenix-rtos-tests/libc/misc ‑ armv7m4-stm32l4x6-nucleo:phoenix-rtos-tests/libc/misc
phoenix-rtos-tests/libc/pthread ‑ armv7m4-stm32l4x6-nucleo:phoenix-rtos-tests/libc/pthread
phoenix-rtos-tests/libc/scanf ‑ armv7m4-stm32l4x6-nucleo:phoenix-rtos-tests/libc/scanf

♻️ This comment has been updated with latest results.

[mateusz-bloch]

I wouldn't use the os module, since TargetBase should have specific paths to certain locations created (for example self.project_dir).

Also, I'm thinking if we should check if the reset was successful

[maska989]

First part is done.

Sadly, second one is not possible, OpenOCD throw non-zero status even if MCU voltage reading is below 3.3v (In our projects this reading is not even used and causing non-zero status return)

[damianloew]

According to our last meeting it will be better to add another method, for example called _reboot_dut_command, because as you can see sending a reset command to onboard debugger is definitely not a text mode.

Suggested change

	def _reboot_dut_text(self, hard):
	def _reboot_dut_command(self, hard):

Then we should introduce a launch_context, where we could specify what reset do we want to use. For now we can just change it temporary this way if needed: