Qualification testing - rfcomm

["Daryl Van Vorst" <daryl@wideray.com>]

[-- Attachment #1: Type: text/plain, Size: 1605 bytes --]

Marcel,

Finally got some results on those latest rfcomm changes for qualification.
Looks like there are a few more problems. :(  But we're close. :)

TP/RFC/BV-09-C:
"Verify that the IUT handles flow control correctly when the Tester, acting
as a device conforming to Bluetooth version 1.0B, controls the data flow
using the Modem Status Command. The IUT's device role is of no importance."

The command and console output:

root@jack-00000000:~>./rctest -s -P 1 -b 20 00:A0:96:1F:83:71
rctest[351]: Connected
rctest[351]: Sending ...
rctest[351]: Send failed. Resource temporarily unavailable(11)

The IUT sends data in 5 frames, then stops for aboue 20s, then sends 5 more,
then stops, etc. Technically, this test passed because we did stop sending
data after the tester send MSC stop to the IUT. But something's clearly not
right.

There is an hcidump of the session attached.

TP/RFC/BV-12-C:
"Verify that the IUT handles aggregate flow control correctly when the
Tester, acting as a device conforming to Bleutooth version 1.0B, controls
the data flow using the Flow Control on/off commands FCon and FCoff. The
IUT's device role is of no importance."

The command and console output:

root@jack-00000000:~>./rctest -s -P 1 -b 20 00:A0:96:1F:83:71
rctest[362]: Connected
rctest[362]: Sending ...
rfcomm_recv_mcc: Unknown control type 0x18
rfcomm_recv_mcc: Unknown control type 0x28

The IUT does not respond to FCoff with FCoff, and continues sending data. It
also does not respond to FCon with FCon. 

There is an hcidump of the session attached.

-Daryl.

[-- Attachment #2: RFC_BV_09_IUT_sends_5_frames_every_20s_hcidump --]
[-- Type: application/octet-stream, Size: 1792 bytes --]

[-- Attachment #3: RFC_BV_12_IUT_does_not_reply_with_FCoff_FCon_hcidump --]
[-- Type: application/octet-stream, Size: 4864 bytes --]