T3.6 USB Host - Bluetooth

mattrcampbell · Jun 6, 2020

Ahhh, I think I actually found my issue! The debug output stopping was just a serial port problem, however I was still having some issues with the code. It turns out what appears to be happening is that the first connection succeeds and starts streaming HID data. While the second connection is in the process of being established an HID report comes in and changes the value of current_connection_ back to 0, at which point as the connection finishes it overwrites the handle of connection 0 with connection 1. Does that make sense? I wonder if having current_connection_ re-assigned in rx2_data makes sense. Would it be more appropriate to just pass the l2cap and HID event handlers the connection to use, without changing the global?

KurtE · Jun 14, 2020

@mjs513 and ...

I have started playing some with the current Bluetooth stuff, in particular about a year ago we had a github branch that allowed Bluetooth support of multiple devices, which it would be nice to get it to complete.

I am mainly looking again as I would like to use one or more controllers to control a hexapod, with a T4.1...

SO I created new branch with the stuff we had about a year ago and applied the changes to the current released version of the USBHost_t36 code.

Some of it is working, especially with PS3 controller.

As for PS4, it works plugged into USB, and it appears to do stuff when connected to bluetooth when I have BT debug turned on, but not when it is turned off. Not sure why yet. Maybe timing?
Also with debug on I am not sure about mappings for the buttons and the like. Need to go look at the code some more.

mjs513 · Jun 15, 2020

@KurtE
Just downloaded the latest and will give it a try. Now to go find all my BT stuff again for testing

EDIT: Have a problem with the PS4. As you said wired it works fine no problem - now can not get BT to connect to PS4 to say my life. It sees and prints the dongle info. But when I go and connect nothing - doesn't even look like its trying to connect?

mjs513 · Jun 15, 2020

@KurtE
Ok got it to connect and work with 2 dongles and no debug prints. But connection process strange on first connect
1. Had to hold Share Button plus PS Button and it connected but not as a PS4 something else - ps3 maybe so the data was messed up and no rumble button.
2. Powered off the T4
3. Powered back T4 and connected normally with just the PS button and now I have a full PS4

Maybe something with the connection string with the PS4?

Have to pull out other controllers and recharge my PS4 before any more tests

KurtE · Jun 15, 2020

@mjs513 - Good morning,

Yes I was/am seeing that. However if you turn on debug in Bluetooth file (#define DEBUG_BT)
It then works.

But if I go into the start of BluetoothController::rx2_data
And comment out the DBGPrintf's it mostly stops working,
But if I then simply added in: digitalWriteFast(32, !digitalReadFast(32));
Then it worked again...

Sometimes it depended on the state of was the PS4 fully off before the program started or not... Again still not really sure of when it works or not.

mjs513 · Jun 15, 2020

KurtE said:
@mjs513 - Good morning,

Yes I was/am seeing that. However if you turn on debug in Bluetooth file (#define DEBUG_BT)
It then works.

But if I go into the start of BluetoothController::rx2_data
And comment out the DBGPrintf's it mostly stops working,
But if I then simply added in: digitalWriteFast(32, !digitalReadFast(32));
Then it worked again...

Sometimes it depended on the state of was the PS4 fully off before the program started or not... Again still not really sure of when it works or not.

Just some added info. I started with debug turned on and was still having issues with getting mine to connect until I used that procedure. I then turned it off and used a different dongle but with debug turned off - used that procedure and it worked whether the Debug was turned on or not.

Just tried it again, debug off, and it paired up right away and worked correctly.

Like you said not sure whats going on. Don't remember having this issue when we first incorporated the PS4. Since then, for BT, think we played with just the Motion Controller? Trying to remember?

KurtE · Jun 15, 2020

Which sketch did you use?

And which version of the constructor did you use?

Code:

//BluetoothController bluet(myusb, true, "0000");   // Version does pairing to device
BluetoothController bluet(myusb);   // version assumes it already was paired

This is the from my current USBHost_viewer But it also looks like the state of the one in JoystickBT

Again wondering if that state may make a difference or not.

mjs513 · Jun 15, 2020

You know, I started with

Code:

BluetoothController bluet(myusb, true, "0000");   // Version does pairing to device

then switched over to the later

Code:

BluetoothController bluet(myusb);   // version assumes it already was paired

but when i got it first connected looked liked it was using a different controller to output data, one that had only one joystick, the button data would then appear in the second joystick data elements (RX or RY).

KurtE · Jun 15, 2020

That is sort of some of the stuff I remembered, that in some cases we were not receiving the data to know that it was a PS4. Two different BT connection message sequences.

May need to capture the sequences again and see if anything makes sense. (Or just use PS3 )

mjs513 · Jun 15, 2020

@KurtE
Had to reload the Joystick sketch (made a change to pitch angle) but this time would not connect but i noticed something with debug output:

Code:

BluetoothController::find_driver  driver 20005e18
    *** Claimed ***
*** BTHID Device Joystick1 0:0 - connected ***
    control callback (bluetooth) 0

0F 04 00 01 19 04 
07 FF 00 EA 94 9B E2 1F 00 57 69 72 65 6C 65 73 
73 20 43 6F 6E 74 72 6F 6C 6C 65 72 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 

    control callback (bluetooth) 0

0F 04 00 01 09 04 
12 08 00 EA 94 9B E2 1F 00 00 
03 0B 00 48 00 EA 94 9B E2 1F 00 01 00 

    tx_data(bluetooth) 0

20 07 EA 94 9B E2 1F 00 01 
13 05 01 48 00 01 00 
1B 03 48 00 05 
17 06 EA 94 9B E2 1F 00 

    control callback (bluetooth) 78

0E 0A 01 0C 04 00 EA 94 9B E2 1F 00 
16 06 EA 94 9B E2 1F 00 
    control callback (bluetooth) 82

0E 0A 01 0D 04 00 EA 94 9B E2 1F 00 
18 17 EA 94 9B E2 1F 00 41 CB 98 E3 5F 93 E1 F2 
0A 75 39 4F DD 0A 0E 2E 00 
08 04 00 48 00 01 

[COLOR="#FF0000"]PS3 Motion Timer
PS3 Motion Joystick no longer detected
PS3 Motion Timer[/COLOR]

Its thinking its connecting to a PS3?

KurtE · Jun 15, 2020

If I remember correctly there were two paths through the BT messaging the pS4 took. One when it did an actual initial binding and one when it did not. And with one of these paths, we did not receive any data that we could deduce what type of joystick it was...

I may need to see if I still have any of this data captured...

I did do a USB capture this morning of starting up sketch, plugging in BT and then press button in on PS4, and this time it connected and started dumping data...

When I stopped the USB capture in Saleae and had it dump packets to a CSV file, there were about 1.9 million lines of text output, which might take me a while to look through

I did the linux grep for IN, OUT, SETUP lines where it also output the previous line as well, and this cut it down to a little over 19 thousand lines, which is a bit better.

I then edited in sublime text and cut this down to < 6500 lines, which again is manageable.. But again all raw data, plus there were lots of data groups, once it connected.

Like the last few are like:

Code:

23.21607064	IN	0x02	0x18	0x48 0x20 0x53 0x00 0x4F 0x00 0x71 0x00 0xA1 0x11 0xC0 0x00 0x81 0x7C 0x81 0x7C 0x08 0x00 0x48 0x00 0x00 0xA0 0x7F 0xFC 0x0E 0x00 0x00 0x00 0x05 0x00 0x81 0x0A 0x7C 0x1E 0x1A 0x00 0x00 0x00 0x00 0x00 0x00 0x09 0x00 0x00 0x00 0x00 0x80 0x00 0x00 0x00 0x80 0x00 0x00 0x00 0x00 0x80 0x00 0x00 0x00 0x80 0x00 0x00 0x00 0x00
23.21707062	IN	0x02	0x18	0x80 0x00 0x00 0x00 0x80 0x00 0x00 0x00 0x00 0x80 0x00 0x00 0x00 0x80 0x00 0x00 0x00 0x00 0x00 0xC3 0x7D 0xE1 0x8C
23.21807067	IN	0x02	0x18	0x48 0x20 0x53 0x00 0x4F 0x00 0x71 0x00 0xA1 0x11 0xC0 0x00 0x81 0x7C 0x81 0x7C 0x08 0x00 0x4C 0x00 0x00 0xF7 0x80 0xFC 0x0E 0x00 0x00 0x00 0x05 0x00 0x69 0x0A 0x83 0x1E 0x09 0x00 0x00 0x00 0x00 0x00 0x00 0x09 0x00 0x00 0x00 0x00 0x80 0x00 0x00 0x00 0x80 0x00 0x00 0x00 0x00 0x80 0x00 0x00 0x00 0x80 0x00 0x00 0x00 0x00
23.21907066	IN	0x02	0x18	0x80 0x00 0x00 0x00 0x80 0x00 0x00 0x00 0x00 0x80 0x00 0x00 0x00 0x80 0x00 0x00 0x00 0x00 0x00 0x54 0x59 0xCC 0x75

The interesting thing here is for this much data, returned by the joystick it requires two full packets of data, over USB... Wonder if we can/should increase packet sizes?

Also maybe a prod back up to the Logic Beta group for HLA support, especially with maybe translating data into more USB HLA stuff...

mjs513 · Jun 15, 2020

Your memory is better than mine. Was going to start trying to follow the path but got side tracked with home chores and things today.

Increasing the packet size might be a good first shot to see if that helps.

Do like the idea of sending off to Logic Beta Group for HLA support. Will definitely make life easier.

mjs513 · Jun 15, 2020

Ok new problem - maybe not - may have forgotten

Cant seem to connect at all with the PS3 or the motion controller by just pushing the PS button.

Want am i forgetting? I remember we had a process where we could connect via the sketch by holding certain buttons but cant remember that sequence.

KurtE · Jun 15, 2020

PS3 Motion - Mine is not really wanting to do anything... I think dead battery ... It did respond for a second when plugged in USB, but ...

With normal PS3 while plugged into USB, holding either R1 or L1 or ? and press PS3 button would try to do bind if it either has BT module plugged in or one was earlier.

mjs513 · Jun 15, 2020

Cant get PS3 to connect no matter what i do so i switched over to the XBox. Got this far when it died:

Code:

*** Device Bluet a12:1 - connected ***
  product: CSR8510 A10
  BDADDR: 11:71:da:7d:1a:0
2F FF 01 E9 A7 DB 1B AA 9C 01 02 08 05 00 B3 6F 
A0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 

BluetoothController::find_driver  driver 20005e18
    *** Claimed ***
*** BTHID Device Joystick1 0:0 - connected ***
  Serial:  
    control callback (bluetooth) 64
0E 04 01 02 04 00 
    control callback (bluetooth) 65
0F 04 00 01 05 04 
03 0B 00 48 00 E9 A7 DB 1B AA 9C 01 00 
    control callback (bluetooth) 6E
0F 04 00 00 11 04 
1B 03 48 00 05 
17 06 E9 A7 DB 1B AA 9C 
0F 04 00 01 00 00 
    control callback (bluetooth) 78
0E 0A 01 0C 04 00 E9 A7 DB 1B AA 9C 
16 06 E9 A7 DB 1B AA 9C 
    control callback (bluetooth) 82
0E 0A 01 0D 04 00 E9 A7 DB 1B AA 9C 
06 03 06 48 00 
    tx_data(bluetooth) 82
13 05 01 48 00 01 00 
    tx_data(bluetooth) 82
13 05 01 48 00 01 00

KurtE · Jun 15, 2020

I just tried a different PS3 with the dongle I am using and the JoystickBT sketch (this time an official Sony one) and it appeared to bind fine.

I first was running Bluetooth with the T4.1... Then unplgged BT and then plugged in PS2 using USB cable. I then held the L1 button in and pressed the PS3 button... I assume it showed some messages in the terminal window, but they scrolled away. I then unplugged it, and plugged back in BT and then pressed the PS3 button again...

Actually I had an interruption during this time. I tried reprogramming it with debug turned off, and then started getting USB device not recognized... Tried again... Still... Did 15 second restore T4.1 and still USB did not like it. So I unplugged it from a new 3' braided USB cable and back into my old USB cable and happy again. And PS3 talked through BT.

Will try Move again, I had it plugged in for a few hours into USB hub... Maybe some power, else new battery arrives later this week.

EDIT: tried pairing Motion again, by plugging it in and it supposedly paired... Tried to run it then and nothing... So I did something that used to be really good at as a kid and disassembled it, Checked battery in volt meter 0.0v more or less So probably won't work too well. So later this week a replacement is supposed to arrive and then I will try something that I was not as good at as a kid in putting it back into one piece without parts missing or extra parts left over

mjs513 · Jun 15, 2020

KurtE said:
I just tried a different PS3 with the dongle I am using and the JoystickBT sketch (this time an official Sony one) and it appeared to bind fine.

I first was running Bluetooth with the T4.1... Then unplgged BT and then plugged in PS2 using USB cable. I then held the L1 button in and pressed the PS3 button... I assume it showed some messages in the terminal window, but they scrolled away. I then unplugged it, and plugged back in BT and then pressed the PS3 button again...

Actually I had an interruption during this time. I tried reprogramming it with debug turned off, and then started getting USB device not recognized... Tried again... Still... Did 15 second restore T4.1 and still USB did not like it. So I unplugged it from a new 3' braided USB cable and back into my old USB cable and happy again. And PS3 talked through BT.

WIll try Move again, I had it plugged in for a few hours into USB hub... Maybe some power, else new battery arrives later this week.

Ok - after playing some more trying to connect with L1 and PS3 button it worked. Once paired it will always connect with the dongle..

XBox is the only one now to get working. Looks like it recognizes it but then hangs.

KurtE · Jun 15, 2020

Which XBox? If I remember correctly XBox360 would only connect either by USB or with their wireless adapter.

XBox One - I think early ones did not support Bluetooth, but later ones maybe... I will pull one down and see what I have.

mjs513 · Jun 15, 2020

This is the one i got from amazon a while back: https://www.amazon.com/gp/product/B01GW3H3U8/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1

KurtE · Jun 15, 2020

Looks like one of mine as well

XBox One with BT as the area around the X is part of the outside shell of the body and not part of the buttons part...

and if you plug it in to USB it says:

Code:

USB Host Testing

960

*** Device JOY1D 45e:2ea - connected ***
  manufacturer: Microsoft
  product: Controller
  Serial: 3033363...4
*** First Joystick message 45e:2ea ***
  manufacturer: Microsoft
  product: Controller
  Serial: 3033363030303332393035363234
LX: 686, LY: -759, RX: 600, RY: -1447 

L-Trig: 0, R-Trig: 0
Buttons: 0
LX: 621, LY: -469, RX: 600, RY: -1359 
L-Trig: 0, R-Trig: 0
Buttons: 0
LX: 621, LY: -469, RX: 600, RY: -1526 
L-Trig: 0, R-Trig: 0
Buttons: 0
LX: 621, LY: -469, RX: -557, RY: -5197 
L-Trig: 0, R-Trig: 0
Buttons: 0

And if I try to bind with it BT wise I get:

Code:

USB Host Testing

960

BluetoothController claim this=20005200 vid:pid=a12:1
    9 4 0 0 3 e0 1 1 0 7 5 81 3 10 0 1 7 5 2 2 40 0 1 7 5 82 2 40 0 1 9 4 1 0 2 e0 1 1 0 7 5 3 1 0 0 1 7 5 83 1 0 0 1 9 4 1 1 2 e0 1 1 0 7 5 
    3 1 9 0 1 7 5 83 1 9 0 1 9 4 1 2 2 e0 1 1 0 7 5 3 1 11 0 1 7 5 83 1 11 0 1 9 4 1 3 2 e0 1 1 0 7 5 3 1 19 0 1 7 5 83 1 19 0 1 9 4 1 4 2 e0 
    1 1 0 7 5 3 1 21 0 1 7 5 83 1 21 0 1 9 4 1 5 2 e0 1 1 0 7 5 3 1 31 0 1 7 5 83 1 31 0 1 
      rxep=1(16) txep=2(64) rx2ep=2(64)
HCI_RESET called (03 0c 00 )
    Control callback (bluetooth): 1 : 3 c 0 
BT rx_data(6): e 4 1 3 c 0 
    Command Completed! 
HCI_WRITE_CLASS_OF_DEV called (24 0c 03 04 08 00 )
    Control callback (bluetooth): 3 : 24 c 3 4 8 0 
BT rx_data(6): e 4 1 24 c 0 
    Command Completed! 
HCI_Read_BD_ADDR called (09 10 00 )
    Control callback (bluetooth): 4 : 9 10 0 
BT rx_data(12): e a 1 9 10 0 13 71 da 7d 1a 0 
    Command Completed! 
   BD Addr 0:1a:7d:da:71:13
HCI_Read_Local_Version_Information called (01 10 00 )
    Control callback (bluetooth): 4 : 1 10 0 
BT rx_data(14): e c 1 1 10 0 6 bb 22 6 a 0 bb 22 
    Command Completed! 
    Local Version: 6
HCI_WRITE_INQUIRY_MODE called (45 0c 01 02 )
    Control callback (bluetooth): 6 : 45 c 1 2 
BT rx_data(6): e 4 1 45 c 0 
    Command Completed! 
HCI_Set_Event_Mask called (01 0c 08 ff ff ff ff ff 5f 00 00 )
    Control callback (bluetooth): 7 : 1 c 8 ff ff ff ff ff 5f 0 0 
BT rx_data(6): e 4 1 1 c 0 
    Command Completed! 
HCI_INQUIRY called (01 04 05 33 8b 9e 30 0a )
    Control callback (bluetooth): 8 : 1 4 5 33 8b 9e 30 a 
BT rx_data(6): f 4 0 1 1 4 
    Command 401 Status 0
*** Device Bluet a12:1 - connected ***
  product: CSR8510 A10
  BDADDR: 13:71:da:7d:1a:0
BT rx_data(16): 2f ff 1 16 ac b3 26 3f c8 1 2 8 5 0 f9 1 
BT rx_data(16): c9 19 9 58 62 6f 78 20 57 69 72 65 6c 65 73 73 
BT rx_data(16): 20 43 6f 6e 74 72 6f 6c 6c 65 72 3 3 24 11 0 
BT rx_data(16): 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 
BT rx_data(16): 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 
BT rx_data(16): 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 
BT rx_data(16): 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 
BT rx_data(16): 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 
BT rx_data(16): 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 
BT rx_data(16): 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 
BT rx_data(16): 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 
BT rx_data(16): 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 
BT rx_data(16): 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 
BT rx_data(16): 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 
BT rx_data(16): 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 
BT rx_data(16): 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 
BT rx_data(1): 0 
    Extended Inquiry Result - Count: 1
      BD:16:ac:b3:26:3f:c8, PS:1, class: 508
      Local Name: Xbox Wireless Controller
      Peripheral device
        Gamepad
BluetoothController::find_driver  driver 20005938
    *** Claimed ***
HCI_INQUIRY_CANCEL called (02 04 00 )
*** BTHID Device Joystick1 0:0 - connected ***
  product: Xbox Wireless Controller
  Serial:  
    Control callback (bluetooth): 100 : 2 4 0 
BT rx_data(6): e 4 1 2 4 0 
    Command Completed! 
HCI_CREATE_CONNECTION called (05 04 0d 16 ac b3 26 3f c8 18 cc 01 00 00 00 00 )
    Control callback (bluetooth): 101 : 5 4 d 16 ac b3 26 3f c8 18 cc 1 0 0 0 0 
BT rx_data(6): f 4 0 1 5 4 
    Command 405 Status 0
BT rx_data(13): 3 b 0 48 0 16 ac b3 26 3f c8 1 0 
    Connection Complete - ST:0 LH:48
HCI_AUTH_REQUESTED called (11 04 02 48 00 )
    Control callback (bluetooth): 110 : 11 4 2 48 0 
BT rx_data(6): f 4 0 0 11 4 
    Command 411 Status 0

=====================
BT rx2_data(16): 48 20 c 0 8 0 1 0 2 1 4 0 1 0 40 0 
    L2CAP Connection Request: ID: 1, PSM: 1, SCID: 40
BT rx_data(5): 1b 3 48 0 5 
BT rx_data(8): 17 6 16 ac b3 26 3f c8 
    Event: Link Key Request 16:ac:b3:26:3f:c8
HCI_LINK_KEY_NEG_REPLY called (0c 04 06 16 ac b3 26 3f c8 )
BT rx_data(6): f 4 0 1 0 0 
    Command 0 Status 0
    Control callback (bluetooth): 120 : c 4 6 16 ac b3 26 3f c8 
BT rx_data(12): e a 1 c 4 0 16 ac b3 26 3f c8 
    Command Completed! 
BT rx_data(8): 16 6 16 ac b3 26 3f c8 
    Event: Pin Code Request 16:ac:b3:26:3f:c8
HCI_PIN_CODE_REPLY called (0d 04 17 16 ac b3 26 3f c8 04 30 30 30 30 00 00 00 00 00 00 00 00 00 00 00 00 )
    Control callback (bluetooth): 130 : d 4 17 16 ac b3 26 3f c8 4 30 30 30 30 0 0 0 0 0 0 0 0 0 0 0 0 
BT rx_data(12): e a 1 d 4 0 16 ac b3 26 3f c8 
    Command Completed! 
BT rx_data(5): 6 3 6 48 0 
    Event: HCI Authentication complete(6): handle: 48
ConnectionRequest called(48 20 0c 00 08 00 01 00 02 00 04 00 11 00 70 00 )
tx_data callback (bluetooth): 0 : 48 20 c 0 8 0 1 0 2 0 4 0 11 0 70 0 
BT rx_data(7): 13 5 1 48 0 1 0 

=====================
BT rx2_data(20): 48 20 10 0 c 0 1 0 3 0 8 0 40 0 70 0 3 0 0 0 
    L2CAP Connection Response: ID: 0, Dest:40, Source:70, Result:3, Status: 0
      Control Response
L2CAP_ConfigRequest called(48 20 10 00 0c 00 01 00 04 00 08 00 40 00 00 00 01 02 ff ff )
tx_data callback (bluetooth): 0 : 48 20 10 0 c 0 1 0 4 0 8 0 40 0 0 0 1 2 ff ff 

=====================
BT rx2_data(18): 48 20 e 0 a 0 1 0 1 0 6 0 2 0 40 0 0 0 
    [COLOR="#FF0000"]L2CAP command reject: ID: 0, length:6, Reason:2,  Data: 0 40 [/COLOR]
BT rx_data(7): 13 5 1 48 0 1 0

What I don't remember is if it worked before? Need to look through this thread

mjs513 · Jun 15, 2020

Was doing the same thing.

Don;t think we ever got it fully working - think we punted moved on.

mjs513 · Jun 15, 2020

Maybe this will help: https://github.com/felis/USB_Host_Shield_2.0/tree/master/examples/Xbox

EDIT: TAKE THAT BACK _ only does wired

KurtE · Jun 15, 2020

I think you are right that we never got it to work... The main Linux drivers don't support Bluetooth,...

However looks like someone else has a version for linux: https://github.com/atar-axis/xpadneo

so will try to see if there are any easy things that we can adapt.

mjs513 · Jun 16, 2020

KurtE said:
I think you are right that we never got it to work... The main Linux drivers don't support Bluetooth,...

However looks like someone else has a version for linux: https://github.com/atar-axis/xpadneo

so will try to see if there are any easy things that we can adapt.

I've been looking through this as well: https://github.com/paroj/xpad/blob/master/xpad.c

KurtE · Jun 16, 2020

Morning,

I was sort of wondering on the XBox one about the bluetooth reconnect patch in that project:

Subject: [PATCH] The current L2CAP implementation does not change any options if the
other side respons with "unknown options", but does if "unaccepted options" is the answer.
It is up to the implementation to decide on the effort spent on config negotiations,
therefore the current implementation is correct at this point - but many devices
(like Xbox One S controllers) are not useable this way.
A workaround for many users therefore is to disable_ertm, since this is often the option
which is unknown. I would prefer to try it again with altered options instead of globally
disable ERTM.

In result, I suggest the following patch. It simply adds a new case (L2CAP_CONF_UNKNOWN),
which does nothing but falling through to L2CAP_CONF_UNACCEPT.

Need to see what errors we are getting and see if this makes sense.

T3.6 USB Host - Bluetooth

Member

Senior Member+

Senior Member+

Senior Member+

Senior Member+

Senior Member+

Senior Member+

Senior Member+

Senior Member+

Senior Member+

Senior Member+

Senior Member+

Senior Member+

Senior Member+

Senior Member+

Senior Member+

Senior Member+

Senior Member+

Senior Member+

Senior Member+

Senior Member+

Senior Member+

Senior Member+

Senior Member+

Senior Member+