CY8CKIT064B0S2_4343W fails at test cordio_hci-driver

[MarceloSalazar]

Description of defect

The CY8CKIT064B0S2_4343W target fails at running thecordio_hci-driver greentea tests.

mbed test -t [GCC_ARM, ARM] -m CY8CKIT064B0S2_4343W -v -n mbed-os-connectivity-feature_ble-source-cordio-tests-cordio_hci-driver

Build successes:
  * CY8CKIT064B0S2_4343W::GCC_ARM::MBED-BUILD
  * CY8CKIT064B0S2_4343W::GCC_ARM::MBED-OS-CONNECTIVITY-FEATURE_BLE-SOURCE-CORDIO-TESTS-CORDIO_HCI-DRIVER
[mbed] Exec "mbedgt --test-spec ./BUILD/tests/CY8CKIT064B0S2_4343W/GCC_ARM/test_spec.json -n mbed-os-connectivity-feature_ble-source-cordio-tests-cordio_hci-driver -V" in "/Users/x/mbed/cypress/test2"
mbedgt: greentea test automation tool ver. 1.7.4
mbedgt: test specification file './BUILD/tests/CY8CKIT064B0S2_4343W/GCC_ARM/test_spec.json' (specified with --test-spec option)
mbedgt: using './BUILD/tests/CY8CKIT064B0S2_4343W/GCC_ARM/test_spec.json' from current directory!
mbedgt: detecting connected mbed-enabled devices...
mbedgt: detected 1 device
	| platform_name        | platform_name_unique    | serial_port            | mount_point      | target_id                                        |
	|----------------------|-------------------------|------------------------|------------------|--------------------------------------------------|
	| CY8CKIT064B0S2_4343W | CY8CKIT064B0S2_4343W[0] | /dev/tty.usbmodem14203 | /Volumes/DAPLINK | 191013011c111612021c111600000000000000002e127069 |
mbedgt: processing target 'CY8CKIT064B0S2_4343W' toolchain 'GCC_ARM' compatible platforms... (note: switch set to --parallel 1)
	| platform_name        | platform_name_unique    | serial_port                 | mount_point      | target_id                                        |
	|----------------------|-------------------------|-----------------------------|------------------|--------------------------------------------------|
	| CY8CKIT064B0S2_4343W | CY8CKIT064B0S2_4343W[0] | /dev/tty.usbmodem14203:9600 | /Volumes/DAPLINK | 191013011c111612021c111600000000000000002e127069 |
mbedgt: test case filter (specified with -n option)
	mbed-os-connectivity-feature_ble-source-cordio-tests-cordio_hci-driver
	test filtered in 'mbed-os-connectivity-feature_ble-source-cordio-tests-cordio_hci-driver'
mbedgt: running 1 test for platform 'CY8CKIT064B0S2_4343W' and toolchain 'GCC_ARM'
	use 1 instance of execution threads for testing
mbedgt: checking for 'host_tests' directory above image directory structure
	'host_tests' directory not found: two directory levels above image path checked
mbedgt: selecting test case observer...
	calling mbedhtrun: mbedhtrun -m CY8CKIT064B0S2_4343W -p /dev/tty.usbmodem14203:9600 -f "BUILD/tests/CY8CKIT064B0S2_4343W/GCC_ARM/mbed-os/connectivity/FEATURE_BLE/source/cordio/TESTS/cordio_hci/driver/driver.hex" -d /Volumes/DAPLINK -c default -t 191013011c111612021c111600000000000000002e127069 -r default -C 10 -R 5 --sync 5 -P 60
mbedgt: mbed-host-test-runner: started
[1601646435.52][HTST][INF] host test executor ver. 0.0.15
[1601646435.52][HTST][INF] copy image onto target...
[1601646435.52][COPY][INF] Waiting up to 60 sec for '191013011c111612021c111600000000000000002e127069' mount point (current is '/Volumes/DAPLINK')...
[1601646474.63][HTST][INF] starting host test process...
[1601646475.07][CONN][INF] starting connection process...
[1601646475.07][CONN][INF] notify event queue about extra 60 sec timeout for serial port pooling
[1601646475.07][CONN][INF] initializing serial port listener...
[1601646475.07][PLGN][INF] Waiting up to 60 sec for '191013011c111612021c111600000000000000002e127069' serial port (current is '/dev/tty.usbmodem14203')...
[1601646475.07][HTST][INF] setting timeout to: 60 sec
[1601646477.21][SERI][INF] serial(port=/dev/tty.usbmodem14203, baudrate=9600, read_timeout=0.01, write_timeout=5)
[1601646477.22][SERI][INF] reset device using 'default' plugin...
[1601646477.62][SERI][INF] waiting 5.00 sec after reset
[1601646482.62][SERI][INF] wait for it...
[1601646482.62][SERI][TXD] mbedmbedmbedmbedmbedmbedmbedmbedmbedmbed
[1601646482.62][CONN][INF] sending up to 5 __sync packets (specified with --sync=5)
[1601646482.62][CONN][INF] sending preamble 'f5aa6c75-ac53-453b-b32f-2eac3fe86ad7'
[1601646482.62][SERI][TXD] {{__sync;f5aa6c75-ac53-453b-b32f-2eac3fe86ad7}}
[1601646482.64][CONN][WRN] UnicodeDecodeError encountered!
[1601646482.76][CONN][RXD] IIIHmII閭Ѣ6Rbmbedmbedmbedmbedmbedmbedmbedmbed
[1601646482.81][CONN][INF] found SYNC in stream: {{__sync;f5aa6c75-ac53-453b-b32f-2eac3fe86ad7}} it is #0 sent, queued...
[1601646482.81][HTST][INF] sync KV found, uuid=f5aa6c75-ac53-453b-b32f-2eac3fe86ad7, timestamp=1601646482.806053
[1601646482.83][CONN][INF] found KV pair in stream: {{__version;1.3.0}}, queued...
[1601646482.83][HTST][INF] DUT greentea-client version: 1.3.0
[1601646482.85][CONN][INF] found KV pair in stream: {{__timeout;15}}, queued...
[1601646482.85][HTST][INF] setting timeout to: 15 sec
[1601646482.89][CONN][INF] found KV pair in stream: {{__host_test_name;default_auto}}, queued...
[1601646482.89][HTST][INF] host test class: '<class 'mbed_os_tools.test.host_tests.default_auto.DefaultAuto'>'
[1601646482.89][HTST][INF] host test setup() call...
[1601646482.89][HTST][INF] CALLBACKs updated
[1601646482.89][HTST][INF] host test detected: default_auto
[1601646482.91][CONN][RXD] >>> Running 1 test cases...
[1601646482.96][CONN][INF] found KV pair in stream: {{__testcase_name;Test cordio stack reset sequence}}, queued...
[1601646482.98][CONN][RXD]
[1601646483.03][CONN][RXD] >>> Running case #1: 'Test cordio stack reset sequence'...
[1601646483.09][CONN][INF] found KV pair in stream: {{__testcase_start;Test cordio stack reset sequence}}, queued...
mbedgt: :78::FAIL: Expected 2 Was 0
[1601646494.49][CONN][RXD] :78::FAIL: Expected 2 Was 0
[1601646494.55][CONN][INF] found KV pair in stream: {{__testcase_finish;Test cordio stack reset sequence;0;1}}, queued...
[1601646494.64][CONN][RXD] >>> 'Test cordio stack reset sequence': 0 passed, 1 failed with reason 'Assertion Failed'
[1601646494.64][CONN][RXD]
[1601646494.71][CONN][RXD] >>> Test cases: 0 passed, 1 failed with reason 'Assertion Failed'
[1601646494.73][CONN][RXD] >>> TESTS FAILED!
[1601646494.75][CONN][INF] found KV pair in stream: {{__testcase_summary;0;1}}, queued...
[1601646494.78][CONN][INF] found KV pair in stream: {{end;failure}}, queued...
[1601646494.78][HTST][INF] __notify_complete(False)
[1601646494.78][HTST][INF] __exit_event_queue received
[1601646494.78][HTST][INF] test suite run finished after 11.93 sec...
[1601646494.79][CONN][INF] found KV pair in stream: {{__exit;0}}, queued...
[1601646494.79][CONN][INF] received special event '__host_test_finished' value='True', finishing
[1601646494.89][HTST][INF] CONN exited with code: 0
[1601646494.89][HTST][INF] Some events in queue
[1601646494.89][HTST][INF] stopped consuming events
[1601646494.89][HTST][INF] host test result() call skipped, received: False
[1601646494.89][HTST][WRN] missing __exit event from DUT
[1601646494.89][HTST][INF] calling blocking teardown()
[1601646494.89][HTST][INF] teardown() finished
[1601646494.89][HTST][INF] {{result;failure}}
mbedgt: retry mbedhtrun 1/1
mbedgt: ['mbedhtrun', '-m', 'CY8CKIT064B0S2_4343W', '-p', '/dev/tty.usbmodem14203:9600', '-f', '"BUILD/tests/CY8CKIT064B0S2_4343W/GCC_ARM/mbed-os/connectivity/FEATURE_BLE/source/cordio/TESTS/cordio_hci/driver/driver.hex"', '-d', '/Volumes/DAPLINK', '-c', 'default', '-t', '191013011c111612021c111600000000000000002e127069', '-r', 'default', '-C', '10', '-R', '5', '--sync', '5', '-P', '60'] failed after 1 count
mbedgt: checking for GCOV data...
mbedgt: mbed-host-test-runner: stopped and returned 'FAIL'
mbedgt: test on hardware with target id: 191013011c111612021c111600000000000000002e127069
mbedgt: test suite 'mbed-os-connectivity-feature_ble-source-cordio-tests-cordio_hci-driver' .......... FAIL in 59.94 sec
	test case: 'Test cordio stack reset sequence' ................................................ FAIL in 11.46 sec
mbedgt: test case summary: 0 passes, 1 failure
mbedgt: all tests finished!
mbedgt: shuffle seed: 0.4482154100
mbedgt: test suite report:
| target                       | platform_name        | test suite                                                             | result | elapsed_time (sec) | copy_method |
|------------------------------|----------------------|------------------------------------------------------------------------|--------|--------------------|-------------|
| CY8CKIT064B0S2_4343W-GCC_ARM | CY8CKIT064B0S2_4343W | mbed-os-connectivity-feature_ble-source-cordio-tests-cordio_hci-driver | FAIL   | 59.94              | default     |
mbedgt: test suite results: 1 FAIL
mbedgt: test case report:
| target                       | platform_name        | test suite                                                             | test case                        | passed | failed | result | elapsed_time (sec) |
|------------------------------|----------------------|------------------------------------------------------------------------|----------------------------------|--------|--------|--------|--------------------|
| CY8CKIT064B0S2_4343W-GCC_ARM | CY8CKIT064B0S2_4343W | mbed-os-connectivity-feature_ble-source-cordio-tests-cordio_hci-driver | Test cordio stack reset sequence | 0      | 1      | FAIL   | 11.46              |
mbedgt: test case results: 1 FAIL
mbedgt: completed in 62.11 sec

Logs attached

cordio_hci-driver_test.txt

Target(s) affected by this defect ?

CY8CKIT064B0S2_4343W

Toolchain(s) (name and version) displaying this defect ?

Arm Compiler 6 and GCC 9

What version of Mbed-os are you using (tag or sha) ?

fbe0409

What version(s) of tools are you using. List all that apply (E.g. mbed-cli)

$ mbed --version
1.10.4

How is this defect reproduced ?

mbed test -t [GCC_ARM, ARM] -m CY8CKIT064B0S2_4343W -v -n mbed-os-connectivity-feature_ble-source-cordio-tests-cordio_hci-driver

@ARMmbed/team-cypress @ARMmbed/mbed-os-connectivity

[ciarmcom]

@MarceloSalazar thank you for raising this issue.Please take a look at the following comments:

Could you add some more detail to the description? A good description should be at least 25 words.

NOTE: If there are fields which are not applicable then please just add 'n/a' or 'None'.This indicates to us that at least all the fields have been considered.
Please update the issue header with the missing information, the issue will not be mirroredto our internal defect tracking system or investigated until this has been fully resolved.

[ciarmcom]

Thank you for raising this detailed GitHub issue. I am now notifying our internal issue triagers.
Internal Jira reference: https://jira.arm.com/browse/IOTOSM-2449