Smoke test doesn't work

[toyowata]

I followed the instruction here, and got result below:

10:57:02 smoke $ ./test.sh K64F https://ruka.mbedcloudtesting.com:443
HOST: Inspecting './test/host_tests' for local host tests...
[1591063026.39][HTST][INF] host test executor ver. 0.0.13
[1591063026.39][HTST][INF] copy image onto target... SKIPPED!
[1591063026.40][HTST][INF] starting host test process...
[1591063026.40][CONN][INF] starting connection process...
[1591063026.40][CONN][INF] notify event queue about extra 240 sec timeout for serial port pooling
[1591063026.40][CONN][INF] initializing global resource mgr listener... 
[1591063026.40][GLRM][ERR] unable to load global resource manager 'raas_client' module!
[1591063026.40][GLRM][ERR] No module named 'raas_client'
[1591063026.40][HTST][INF] setting timeout to: 240 sec
[1591063026.40][CONN][ERR] Failed to connect to resource
[1591063026.41][HTST][ERR] None
[1591063026.41][HTST][WRN] stopped to consume events due to __notify_conn_lost event
[1591063026.41][HTST][INF] __exit_event_queue received
[1591063026.41][HTST][INF] test suite run finished after 0.00 sec...
[1591063026.41][HTST][INF] CONN exited with code: 0
[1591063026.41][HTST][INF] No events in queue
[1591063026.41][HTST][INF] host test result() call skipped, received: ioerr_serial
[1591063026.41][HTST][WRN] missing __exit event from DUT
[1591063026.41][HTST][INF] calling blocking teardown()
[1591063026.41][HTST][INF] teardown() finished
[1591063026.41][HTST][INF] {{result;ioerr_serial}}
10:57:06 smoke $ 

How can I run the smoke test for the mbed-bootloader?

[SeppoTakalo]

Hi @toyowata,

Instructions written here are intended for internal use, or at least the step four in the list. This is because we utilise test boards connected in our own LAB in a system called RAAS. That system is not available outside of Arm network.

If you want to manually test your bootloader, you can use the produced <target>_smoke.bin or .hex file and manually flash that into the device. Then observe the serial port. If you see Hello World application starting, it means that bootloader has passed the smoke test and was able to flash the firmware.

The test have further been improved so that after a Hello World message, it prints out a generated random string, which you can see in the compare.log, this allows you to re-build the test and be sure that it was your application that booted, not a previous version of the smoke test that is running.

[toyowata]

@SeppoTakalo thanks.