esp-idf/tools/test_apps/system/longjmp_test/app_test.py

#!/usr/bin/env python

import ttfw_idf
from tiny_test_fw import Utility


@ttfw_idf.idf_custom_test(env_tag='Example_GENERIC', target=['esp32', 'esp32s2'], group='test-apps')
def test_longjmp(env, _):

    dut = env.get_dut('longjmp_test', 'tools/test_apps/system/longjmp_test')
    dut.start_app()
    dut.expect('Test successful', 15)

    Utility.console_log('longjmp test done.')


if __name__ == '__main__':
    test_longjmp()
[system]: Made longjmp save for context switch * Patched longjmp to be context-switch safe longjmp modifies the windowbase and windowstart registers, which isn't safe if a context switch occurs during the modification. After a context switch, windowstart and windowbase will be different, leading to a wrongly set windowstart bit due to longjmp writing it based on the windowbase before the context switch. This corrupts the registers at the next window overflow reaching that wrongly set bit. The solution is to disable interrupts during this code. It is only 6 instructions long, the impact shouldn't be significant. The fix is implemented as a wrapper which replaces the original first instructions of longjmp which are buggy. Then, it jumps back to execute the rest of the original longjmp function. Added a comparably reliable test to the test apps. 2021-04-08 00:16:17 -04:00			`#!/usr/bin/env python`

			`import ttfw_idf`
			`from tiny_test_fw import Utility`


			`@ttfw_idf.idf_custom_test(env_tag='Example_GENERIC', target=['esp32', 'esp32s2'], group='test-apps')`
			`def test_longjmp(env, _):`

			`dut = env.get_dut('longjmp_test', 'tools/test_apps/system/longjmp_test')`
			`dut.start_app()`
			`dut.expect('Test successful', 15)`

			`Utility.console_log('longjmp test done.')`


			`if __name__ == '__main__':`
			`test_longjmp()`