Been quite a while since I've checked in on this thread... (Feb 2020)
Had wondered where development was headed at getting multiple device support. (Was looking to use 2 PS3 Move Navigation controllers)
Looks like KurtE found some time, and some merges happened since then:
https://github.com/PaulStoffregen/USBHost_t36/pull/38
I'll have to get my project back out and see if I can get things working.
Thank you for the continued work
This didn't get looked at yet with the release of TD 1.54.Originally Posted by kdharbert
Wondering if the Bt4.0 dongle tested to work functioned when running off a LiPo cell ...
Evening all decided to get a new toy to play with via bluetooth: https://www.amazon.com/gp/product/B0...?ie=UTF8&psc=1. Basically its a key board that attaches to the DS4/PS4 but still need to connect to the teensy dongle.
Unfortunately think getting this working is wrapped up with getting a PS4 working with USBHost. It recognizes the keyboard - tries to connect and then crashes - crash report comes in handy for debugging:
Code:CrashReport: A problem occurred at (system time) 0:1:31 Code was executing from address 0x6F1E CFSR: 82 (DACCVIOL) Data Access Violation (MMARVALID) Accessed Address: 0x5A781A4B Temperature inside the chip was 0.00 °C Startup CPU clock speed is 600MHz USB Host Testing 960 BluetoothController claim this=20005d00 vid:pid=a5c:21e8 9 4 0 0 3 ff 1 1 0 7 5 81 3 10 0 1 7 5 82 2 40 0 1 7 5 2 2 40 0 1 9 4 1 0 2 ff 1 1 0 7 5 83 1 0 0 1 7 5 3 1 0 0 1 9 4 1 1 2 ff 1 1 0 7 5 83 1 9 0 1 7 5 3 1 9 0 1 9 4 1 2 2 ff 1 1 0 7 5 83 1 11 0 1 7 5 3 1 11 0 1 9 4 1 3 2 ff 1 1 0 7 5 83 1 19 0 1 7 5 3 1 19 0 1 9 4 1 4 2 ff 1 1 0 7 5 83 1 21 0 1 7 5 3 1 21 0 1 9 4 1 5 2 ff 1 1 0 7 5 83 1 31 0 1 7 5 3 1 31 0 1 9 4 2 0 2 ff ff ff 0 7 5 84 2 20 0 1 7 5 4 2 20 0 1 9 4 3 0 0 fe 1 1 0 9 21 5 88 13 40 0 10 1 rxep=1(16) txep=2(64) rx2ep=2(64) HCI_RESET called (03 0c 00 ) *** Device Bluet a5c:21e8 - connected *** manufacturer: Broadcom Corp product: BCM20702A0 Serial: 001986000EE0 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 e0 e 0 86 19 0 Command Completed! BD Addr 0:19:86:0:e:e0 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 0 10 6 f 0 e 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 BT rx_data(16): 2f ff 1 3e 81 c1 17 62 67 1 0 40 25 0 3a 5b BT rx_data(16): cb 18 9 4e 59 4b 4f 20 54 59 50 45 20 50 41 44 BT rx_data(16): 20 20 20 20 20 20 20 20 20 20 3 3 24 11 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(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:3e:81:c1:17:62:67, PS:1, class: 2540 Local Name: NYKO TYPE PAD Peripheral device Keyboard BluetoothController::find_driver driver 200039f8 Keyboard Controller::claim_bluetooth - Class 2540 KeyboardController::claim_bluetooth TRUE *** Claimed *** HCI_INQUIRY_CANCEL called (02 04 00 ) 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 3e 81 c1 17 62 67 18 cc 01 00 00 00 00 ) Control callback (bluetooth): 101 : 5 4 d 3e 81 c1 17 62 67 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 b 0 3e 81 c1 17 62 67 1 0 Connection Complete - ST:0 LH:b HCI_AUTH_REQUESTED called (11 04 02 0b 00 ) Control callback (bluetooth): 110 : 11 4 2 b 0 BT rx_data(6): f 4 0 1 11 4 Command 411 Status 0 BT rx_data(8): 17 6 3e 81 c1 17 62 67 Event: Link Key Request 3e:81:c1:17:62:67 HCI_LINK_KEY_NEG_REPLY called (0c 04 06 3e 81 c1 17 62 67 ) Control callback (bluetooth): 120 : c 4 6 3e 81 c1 17 62 67 BT rx_data(12): e a 1 c 4 0 3e 81 c1 17 62 67 Command Completed! BT rx_data(8): 16 6 3e 81 c1 17 62 67 Event: Pin Code Request 3e:81:c1:17:62:67 HCI_PIN_CODE_REPLY called (0d 04 17 3e 81 c1 17 62 67 06 39 36 38 33 33 32 00 00 00 00 00 00 00 00 00 00 ) Control callback (bluetooth): 130 : d 4 17 3e 81 c1 17 62 67 6 39 36 38 33 33 32 0 0 0 0 0 0 0 0 0 0 BT rx_data(12): e a 1 d 4 0 3e 81 c1 17 62 67 Command Completed! BT rx_data(5): 6 3 8 b 0 Event: HCI Authentication complete(8): handle: b ConnectionRequest called(0b 20 0c 00 08 00 01 00 02 00 04 00 11 00 70 00 ) CrashReport: A problem occurred at (system time) 20:43:50 Code was executing from address 0x6F36 CFSR: 82 (DACCVIOL) Data Access Violation (MMARVALID) Accessed Address: 0x5A781A4B Temperature inside the chip was 0.00 °C Startup CPU clock speed is 600MHz Reboot was caused by auto reboot after fault or bad interrupt detected USB Host Testing 960 BluetoothController claim this=20005d00 vid:pid=a5c:21e8 9 4 0 0 3 ff 1 1 0 7 5 81 3 10 0 1 7 5 82 2 40 0 1 7 5 2 2 40 0 1 9 4 1 0 2 ff 1 1 0 7 5 83 1 0 0 1 7 5 3 1 0 0 1 9 4 1 1 2 ff 1 1 0 7 5 83 1 9 0 1 7 5 3 1 9 0 1 9 4 1 2 2 ff 1 1 0 7 5 83 1 11 0 1 7 5 3 1 11 0 1 9 4 1 3 2 ff 1 1 0 7 5 83 1 19 0 1 7 5 3 1 19 0 1 9 4 1 4 2 ff 1 1 0 7 5 83 1 21 0 1 7 5 3 1 21 0 1 9 4 1 5 2 ff 1 1 0 7 5 83 1 31 0 1 7 5 3 1 31 0 1 9 4 2 0 2 ff ff ff 0 7 5 84 2 20 0 1 7 5 4 2 20 0 1 9 4 3 0 0 fe 1 1 0 9 21 5 88 13 40 0 10 1 rxep=1(16) txep=2(64) rx2ep=2(64) HCI_RESET called (03 0c 00 ) *** Device Bluet a5c:21e8 - connected *** manufacturer: Broadcom Corp product: BCM20702A0 Serial: 001986000EE0 Control callback (bluetooth): 1 : 3 c 0 BT rx_data(7): 13 5 1 b 0 1 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 e0 e 0 86 19 0 Command Completed! BD Addr 0:19:86:0:e:e0 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 0 10 6 f 0 e 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 BT rx_data(16): 2f ff 1 3e 81 c1 17 62 67 1 0 40 25 0 3c 74 BT rx_data(16): bf 18 9 4e 59 4b 4f 20 54 59 50 45 20 50 41 44 BT rx_data(16): 20 20 20 20 20 20 20 20 20 20 3 3 24 11 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(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:3e:81:c1:17:62:67, PS:1, class: 2540 Local Name: NYKO TYPE PAD Peripheral device Keyboard BluetoothController::find_driver driver 200039f8 Keyboard Controller::claim_bluetooth - Class 2540 KeyboardController::claim_bluetooth TRUE *** Claimed *** HCI_INQUIRY_CANCEL called (02 04 00 ) 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 3e 81 c1 17 62 67 18 cc 01 00 00 00 00 ) Control callback (bluetooth): 101 : 5 4 d 3e 81 c1 17 62 67 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 4 b 0 3e 81 c1 17 62 67 1 0 Connection Complete - ST:4 LH:b HCI_AUTH_REQUESTED called (11 04 02 0b 00 ) Control callback (bluetooth): 110 : 11 4 2 b 0 BT rx_data(6): f 4 12 1 11 4 Command 411 Status 12 - ???
WOW! - Running at 0.00 °C !!! Saw one fault expose that as some version of NAN for that float, not sure why it would fail to return vlaid numbers from the TempCall? But it is packed under CRC - so that is the number it returned ???
Indeed very nice to get a clear restart with a note. Interesting if the provided address maps out to expected code? > executing from address 0x6F1E
If there is anything in memory ( DMAMEM - that can be cache_FLUSHED ) that status would be available to print after Crash.
I noted after TD 1.54 release - might have been handy to have the Crash handle flush ALL of DMAMEM(@, 512KB) to be sure ... instead of just (&info,#)
The other alternative would be to have a UserSketchCrashCall() that could pack up related state for review on restart. For instance: the debug On/Off viewed with a LogAnalyzer could be set in DMAMEM - then dumped after a crash to see what code path was active.
Ok, I broke down and ordered oneEvening all decided to get a new toy to play with via bluetooth: https://www.amazon.com/gp/product/B0...?ie=UTF8&psc=1. Basically its a key board that attaches to the DS4/PS4 but still need to connect to the teensy dongle.
Unfortunately think getting this working is wrapped up with getting a PS4 working with USBHost. It recognizes the keyboard - tries to connect and then crashes - crash report comes in handy for debugging:
...Supposed to get here maybe Tuesday
@KurtE
Had a feeling you weren't going to not be able to resist the temptation and go down another rabbit hole
Was playing a bit this morning. Tried pairing USBHost2, said pairing was successful but little blue light didn't stay on and no keyboard data. Then out of curiosity I tried pairing with my iPhone and that worked but interesting thing ws the phone what me to type a 4 digit number on the keypad and hit return and then connect. Just playing for now. Have to get the dump from linux later. Doing this on and off - but have a feeling it may pair the same way as the PS4's that we are having a problem with.
Does that "Type Pad" work stand alone or, and/or in combo with : PlayStation DualShock 4 Controller.
Never picked up a PS4 controller as they were WIP ... is there one that is a good start?
Good afternoon Tim
That "TypePad" works alone even though it connects to the PS4. As for a good PS4 to start - You can try the Voyee (red) that Kurt mentioned earlier - he said he was able to get it to work. I have 3 of them and none will pair.
Hi Mike, seemed it was self powered and stand alone - just injects Audio to the controller ?
Searching thread not finding link - but a note the RED was no longer there?
This search shows two Not_RED Voyee in early listing ... White ? : amazon.com/s?k=voyee+ps4
... gotta run ... there is a payroll at stake ... Win 8 HDD corrupted ... and I just cloned it Dec 2020 ... so ReCloned from that to a fresh HDD ... now needs updated and ...
> Bummer is Acronis and old clone tool both make the Disk GPT {UEFI? boot?} not MBR as they 'clone' ... so lucky I had a dual drive Offline Clone Copy device ... as the Win 8 machine not GPT aware ...
My NyKo keypad arrived today... I charged it a little, actually left it charging...
I loaded the example sketch KeyboardBT.
I built it first with: BluetoothController bluet(myusb, true, "0000"); // Version does pairing to device
Before the program started, I turned keypad on and pressed the BT button.
After it started up... Did not see many messages, but I then hit: 0000<cr>
Then I rebuilt the sketch without the pairing part
Then the program started up.... When I press the first key on the unit, it wakes up and connects and the sketch prints out the data like:
Code:USB Host Testing 960 *** Device Bluet a12:1 - connected *** product: CSR8510 A10 BluetoothController::find_driver driver 20002cd8 Keyboard Controller::claim_bluetooth - Class 2540 KeyboardController::claim_bluetooth TRUE *** Claimed *** KeyboardController::process_bluetooth_HID_data key '1' 49 MOD: 0 OEM: 1E LEDS: 0 KeyboardController::process_bluetooth_HID_data KeyboardController::process_bluetooth_HID_data key 'o' 111 MOD: 0 OEM: 12 LEDS: 0 KeyboardController::process_bluetooth_HID_data KeyboardController::process_bluetooth_HID_data key 'o' 111 MOD: 0 OEM: 12 LEDS: 0 KeyboardController::process_bluetooth_HID_data KeyboardController::process_bluetooth_HID_data key ',' 44 MOD: 0 OEM: 36 LEDS: 0 KeyboardController::process_bluetooth_HID_data KeyboardController::process_bluetooth_HID_data key ',' 44 MOD: 0 OEM: 36 LEDS: 0 KeyboardController::process_bluetooth_HID_data KeyboardController::process_bluetooth_HID_data key 'q' 113 MOD: 0 OEM: 14 LEDS: 0 KeyboardController::process_bluetooth_HID_data KeyboardController::process_bluetooth_HID_data key 'LEFT' 216 MOD: 0 OEM: 50 LEDS: 0 KeyboardController::process_bluetooth_HID_data KeyboardController::process_bluetooth_HID_data key 'RIGHT' 215 MOD: 0 OEM: 4F LEDS: 0 KeyboardController::process_bluetooth_HID_data KeyboardController::process_bluetooth_HID_data key 'UP' 218 MOD: 0 OEM: 52 LEDS: 0 KeyboardController::process_bluetooth_HID_data KeyboardController::process_bluetooth_HID_data key 'DN' 217 MOD: 0 OEM: 51 LEDS: 0 KeyboardController::process_bluetooth_HID_data KeyboardController::process_bluetooth_HID_data key 'LEFT' 216 MOD: 0 OEM: 50 LEDS: 0 KeyboardController::process_bluetooth_HID_data KeyboardController::process_bluetooth_HID_data key 'RIGHT' 215 MOD: 0 OEM: 4F LEDS: 0 KeyboardController::process_bluetooth_HID_data KeyboardController::process_bluetooth_HID_data key ' ' 10 MOD: 0 OEM: 28 LEDS: 0 KeyboardController::process_bluetooth_HID_data KeyboardController::process_bluetooth_HID_data key ' ' 10 MOD: 0 OEM: 28 LEDS: 0 KeyboardController::process_bluetooth_HID_data KeyboardController::process_bluetooth_HID_data key '
That looks promising! Similar function to the "Rii mini i8"?My NyKo keypad arrived today... I charged it a little, actually left it charging...
I loaded the example sketch KeyboardBT.
I built it first with: BluetoothController bluet(myusb, true, "0000"); // Version does pairing to device
Before the program started, I turned keypad on and pressed the BT button.
After it started up... Did not see many messages, but I then hit: 0000<cr>
Then I rebuilt the sketch without the pairing part
Then the program started up....
Do you have a way to power that from a LiPo cell? Recent post #952, wondered if the Bt dongle running on less than 5V would function.
@KurtE - @defragster
Just tried it again. Seems a bit sensitive to pairing but once you get it, works like charm. Got it working with both a broadcom and a CSR4.0 dongle. So very promising for other projects
@defragster - there's a rechargeable battery in the keypad so it can work stand alone from the DS4 -only need to use the wire to charge it.
Very cool yours worked too. Just clicked order to arrive tomorrow.@KurtE - @defragster
Just tried it again. Seems a bit sensitive to pairing but once you get it, works like charm. Got it working with both a broadcom and a CSR4.0 dongle. So very promising for other projects
@defragster - there's a rechargeable battery in the keypad so it can work stand alone from the DS4 -only need to use the wire to charge it.
@mjs513 - @kdharbert : question above was running the Teensy from LiPo - meaing the Dongle wouldn't have 5V ... does it work:
BT4.0 dongles to see if they can be used with only 3.3v instead of 5v supplies so a variety of units would be best. This lets me use an existing 3.7v battery system.
Type Pad arrived ... annoying wings to blend into the controller ... and that audio jack it seemed might fold away.
What code is WIP to work with? Want to see what happens when LiPo powered to Bt ...
Just used the standard KeyboardBT sketch thats part of USBHost_T36 installed with Teensyduino - so no WIP needed
Thanks, unit unboxed and charged yesterday - but not gotten time for more than that.
Will have to locate the Bt dongle part ...
can't find Dongle item #1 listed : CSR 4.0
But I did find the second : PANBT400 Plugable Bt 4.0 Low Energy { LINK STILL ACTIVE }
It worked USB POWERED. Type Pad doesn't seem to always sends keys? Not sure if it sleeps or something? Seems some keys need to be MASHED?
@kdharbert ::
Then using 5V Cut cable wired a charged LiPo - at 4+V
It came up working again - usb Data only connected to PC and T_4.1 w/USB header to that Dongle works here with NYKO Type Pad.
Tried connecting Logitech Mouse with : \Mouse_KeyboardBT.ino
> it seemed to pair but - then connects and disconnects?
Much better PAIRED the Rii keypad :: been powered some 15 minutes - gone from over 4V to 3.9V or just under on 1,000 mAh cell
> It pairs and works MUCH better - keys register on CLICK - not missed or requiring mashing.
I have been using the Kinivo USB Bluetooth Adapter primarily - also tested with a CSR4.0 dongle.
Seems when I was testing as a standalone unit (not attached to the DS4) it seemed a bit more awkward to use the keys and felt like it I had to mashed the keys as well. With that said when I attached it the DS4 did seemed like I had to mash them as before, but considering its on a gamepad not bad. Once paired didn't notice that it wasn't always sending keys.
With all that said, I would not use it as a standalone keyboard - there are better ones out there. Picked this one up specifically for use with the DS4 controller.
Cool - the Kinivo like the PANBT400 AMZN links are still valid and both working is good.
AMZN doesn't indicate one of the Kinivo was delivered here though.
As far as @kdharbert question on usage - not running at 5V but on LiPo - at least the PANBT400 seemed to function at 3.9V at tested.
Posting Permissions
Reply With Quote