Part Number:WL1831MOD
Tool/software: Linux
Hello ,
TI-WL1831 .
We are experiencing data corruption on RFCOMM. (we are testing with 2 service packs version 4.2 and 3.9, both have similar bit errors in the data !)
Test scenario we use ONE-Bluetooth master ( bluegiga WT41 ) connecting to multiple bluetooth slaves ( WL1831).
The test sends one GENERATED DATA FRAME containing some header and data bytes 00, 01, 02 ... till FE. after some hours of loopback it happens occasionally ( 1a2 frames on 100.000) that we get faulty data-bytes.
( FYI each in and out going action, the generated data frame is checked on different levels, application and kernel driver just before sending to the ACIA ( in the HCI_LL driver) and or just after receiving on the acia.
Acia baud rate ( 3000000 baud) has been checked with an 'infinite persistence' scope for several hours, bits have no jitter, and levels are ok!
This is an example of an error data frame. ( for some reason if an error happens... the error frame is 'NOT' ok, some bits ( in a byte) are missing or shifted to next bit position in the bytes)
This error FRAME is being logged when we get the data into the HCI_LL driver ( received by the host cpu , after getting the bytes out of the ACIA) marked faulty bytes are colored RED and underlined,
Mar 28 05:56:17 DU9 kern.warn kernel: [152851.764375] [KERNEL] DUMP-DIFF !!!!!
Mar 28 05:56:17 DU9 kern.warn kernel: [152851.764410] RX-BUF [len=00304]
Mar 28 05:56:17 DU9 kern.warn kernel: [152851.764527] [0x0000] 01 00 03 00 00 09 00 00 00 02 00 00 00 00 00 00 FF FF 04 00 FF 02 00 00 00 01 00 00 00 FF 00 00 00 00 00 FF 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 10 11 12 13 14 15 16 17 18 19 1A 1B
Mar 28 05:56:17 DU9 kern.warn kernel: [152851.764638] [0x0040] 1C 1D 1E 1F 20 21 22 23 24 25 26 27 28 29 2A 2B 2C 2D 2E 2F 30 31 32 33 34 35 36 37 38 39 3A 3B 3C 3D 3E 3F 40 41 42 43 44 45 46 47 48 49 4A 4B 4C 4D 4E 4F 50 51 52 53 54 55 56 57 58 59 5A 5B
Mar 28 05:56:17 DU9 kern.warn kernel: [152851.764748] [0x0080] 5C 5D 5E 5F 60 61 62 63 64 65 66 67 68 69 6A 6B 6C 6D 6E 6F 70 71 72 73 74 75 76 77 78 79 7A 5B 7C 7D 7E 5F 80 81 82 83 84 85 86 97 88 89 8A 8B 8C 8D 8C 8F 90 91 92 93 94 95 96 97 98 99 9A 9B
Mar 28 05:56:17 DU9 kern.warn kernel: [152851.764858] [0x00C0] 9C 9D 9E 9F A0 A1 A2 A3 A4 A5 A6 A7 A8 A9 AA AB AC AD AE AF B0 B1 B2 B3 B4 B5 B6 B7 B8 B9 BA BB BC BD BE BF C0 C1 C2 C3 C4 C5 C6 C7 C8 C9 CA CB CC CD CE CF D0 D1 D2 D3 D4 D5 D6 D7 D8 D9 DA DB
Mar 28 05:56:17 DU9 kern.warn kernel: [152851.764931] [0x0100] DC DD DE DF E0 E1 E2 E3 E4 E5 E6 E7 E8 E9 EA EB EC ED EE EF F0 F1 F2 F3 F4 F5 F6 F7 F8 F9 FA FB FC FD FE BF 49 2F 72 65 71 75 65 73 74 6D 64 69
Finally this 'same' error pops-also up in the application software ... printing out the WRONG bytes ( first print out is just behind the socket read in the application)
Mar 28 05:56:18 DU9 user.info BMS_DUTEST_0 [24818]: [ModLoopbackDUMsg] BEGIN - LOG
Mar 28 05:56:18 DU9 user.info BMS_DUTEST_0 [24818]: [ModLoopbackDUMsg] OFFSET 0x007B : 0x7B <=> 0x5B
Mar 28 05:56:18 DU9 user.info BMS_DUTEST_0 [24818]: [ModLoopbackDUMsg] OFFSET 0x007F : 0x7F <=> 0x5F
Mar 28 05:56:18 DU9 user.info BMS_DUTEST_0 [24818]: [ModLoopbackDUMsg] OFFSET 0x0087 : 0x87 <=> 0x97
Mar 28 05:56:18 DU9 user.info BMS_DUTEST_0 [24818]: [ModLoopbackDUMsg] OFFSET 0x008E : 0x8E <=> 0x8C
Mar 28 05:56:18 DU9 user.info BMS_DUTEST_0 [24818]: [ModLoopbackDUMsg] END - LOG
Any hints on how to proceed ?
Is there any possibility to log the data-bytes over the serial line with the Ti-logger application ( I can see many things there , but I don't find a way to see serial DATA-BYTES on HCI_LL level ! )
Best Regards
Noel Vellemans
FYI:
1) this error is never seen on a bluegiga vs bluegiga setup.
2) it can take up to more than a day to get this 'error'.