I have an old Logitech wireless keyboard which is still working perfectly fine. I was wondering if I could use its Bluetooth dongle in order to connect my Bluetooth speakers (different brand) to my computer? Is this something possible at all? If so, I'd be happy if I could get a hint or some write-ups on that.
When I first got my diNovo Edge, I found and tried the solution here. Unfortunately, I also discovered that following these instructions locks the dongle in Bluetooth mode. That is, even when you power up your system, the dongle is in Bluetooth mode!
That presented a big problem for me, because I could no longer get into the BIOS! (Note: if anyone who sees this knows of a way to use the instructions here to put the dongle in Bluetooth mode and retain the ability to get into BIOS, please share it!)
The first, which is the one I use, is found here. This guy wrote a small program, called LHid2Hci, which works perfectly. All you do is download the binary and place a shortcut to it in your Startup folder. The binary takes two command line options, the VID&PID values of the Bluetooth dongle. (The instructions are all there.)
The program does exactly what the name says, it converts the Logitech Bluetooth dongle from HID (USB) to HCI (Bluetooth) mode! It's activated when you log in, and voil! You have your Bluetooth dongle, with which you can pair any other device. (I have a Microsoft Bluetooth number pad and a Bluetooth stereo headset.)
Are you sure the dongle is actually a Bluetooth dongle? Logitech is pretty big on their Unifying receivers, which are used to connect up to six Logitech devices using similar (but incompatible) technology to Bluetooth.
The diNovo mini definitely uses Bluetooth, so I was sure the USB dongle was a Bluetooth one. The included dongle has two modes that it operates in, an embedded mode and a Bluetooth mode. It's set to embedded mode by default, which allows you to connect to the Logitech device without having to do the pairing process. To switch it to Bluetooth mode you have to do the following:
You should try to pair your speakers with the dongle in the same way you have paired your keyboard and in the same way you have paired your speakers elsewhere. Have in mind that successful pairing may happen even if the dongle lacks support for required profile.
In case you never had to pair your keyboard with the dongle, there comes another issue: are you sure you've got a Bluetooth keyboard, not a simple wireless one? It's good if you are sure, but certainly there are users out there who do not know the difference, so let me explain for them.
As far as I know, vast majority of wireless keyboards and mice uses non-Bluetooth (vendor-specific, I think) protocols to communicate with their dongles. The reasons are: lower power consumption and simplicity. Such a set works "out of the box", the keyboard knows nothing about relatively complex Bluetooth, pairing, etc. The host may also know nothing about Bluetooth, and USB support is enough.
In addition, there isn't any need for two-way communication: the keyboard works as sender only, and the dongle as a receiver; still, Bluetooth requires two-way communication, even with a keyboard or mouse. That's why Bluetooth devices are more expensive than their non-Bluetooth counterparts.
Bluetooth or not, how can you tell? A Bluetooth keyboard should have a Bluetooth symbol on it and a button allowing it to pair with something other than attached dongle (example: with a laptop having internal Bluetooth adapter).
In fact, there isn't often any dongle in the set. The Bluetooth dongle reports to operating system as Bluetooth radio, while non-Bluetooth keyboard dongle is recognized directly as a keyboard (HID device) connected to USB just like any wired USB keyboard.
If your keyboard and dongle are Bluetooth devices, you have to pair them in every operating system you connect the dongle to, because a Bluetooth keyboard (and any other Bluetooth device) pairs with the operating system via the dongle, not with the dongle only. If given set works just by plugging the dongle, then it's not Bluetooth.
In case you cannot tell whether you've got Bluetooth or non-Bluetooth keyboard, name its model here, so we could figure it out. If it is Bluetooth one and you need more help pairing speakers, I need to know your operating system before I guide you further.
On the desktop right click My Computer and the Manage. Down the list is Disk Management. If it is detected it should show up as removable media witha an assigned drive letter. There could be a conflict with existing devices using the same draive letter. This will keep it from showing up in Explorer. You would just right click and chsnge the drive letter to one not being used.
Ok, more seriously, what is on the Dongle? If it is a dongle to unlock a SW package, then I doubt you can just copy/clone it to a flash drive easily, and you may destroy it in the process. Only try this if you can go without the SW until either a new dongle arrives, or until a new license/dongle is purchased.
Thanks for signing up! Keep an eye out for a confirmation email from our team. To ensure any newsletters you subscribed to hit your inbox, make sure to add newsl...@nl.technologyadvice.com to your contacts list.
I decided to convert my existing project to run on the dongle by following the instructions on this page -range-guides/b/getting-started/posts/nrf52840-dongle-programming-tutorial . I also commenting out my code and pasted the blinky code just to get something recognisable.
I tried changing my project to have debug_additional_load_file mbr_nrf52_2.4.1_mbr.hex instead of s140_nrf52_6.1.1_softdevice.hex but it made no difference. Which I guess is obvious because the the dongle doesn't have debug support.
I notice that if I try to upload just my application.hex without adding the softdevice.hex then it actually works. My code is running now. I can change the blink speed in my project and it works on the dongle.
It's a classic mistake when staring out with Nordic, and you've almost solved it already.
The examples in "sdk/examples/peripheral" are not set up to use the SoftDevice, whereas the examples in "sdk/examples/ble_*" are.
The SoftDevice is placed at the bottom of flash and forwards interrupts to the applications vector table, often placed at 0x26000, on top of the SoftDevice. You will also need to set the start address and size of the application's RAM as the SoftDevice has a dedicated space at the bottom of RAM.
If you copy the ble_app_blinky example from "sdk/examples/ble_peripheral/" and swap out the main.c file and necessary libraries with the blinky example from "sdk/example/peripheral/" you should be able to run the blinky example with SoftDevice flashed, as the ble examples have everything set up already.
You can debug the dongle by using a DK's OB debugger. Though you need to either populate the debug port connector footprint at the bottom of the dongle, or solder a couple of wires to VDD, GND, SWDIO, and SWDCLK. Then you do not even need a bootloader.
See the dongle's Hardware drawings.
Unfortunately, I think you may be out of luck. All products that use the ancient parallel port dongles are long out of support, as are the parallel dongles themselves. Steinberg are in the process of deprecating the USB dongle system; the latest version of Cubase does not use it.
I thought of this plan to get that storage working again and to convert into a full USB flash drive (If that's possible)
So I plugged it in and... nothing
It didn't show up as a USB storage device.
I checked on Hardinfo and it detected it as a USB device (Specifically a 'Huawei Technologies Co., Ltd. E398 LTE/UMTS/GSM Modem/Networkcard')
So It is detected.
I wanted to mount it as a USB device so I used mount (But It was not already given a name like sda or sdb or I mounted by-id to /mnt/)
I checked In the folder and found the files and made a backup of it and then I tried to erase all data from it
But, It didn't work. It said It was a read-only filesystem
I checked on dmesg and it said it was a USB mass storage device
I thought all storage devices were mounted as /dev/sd*?
I would like to mount it like that.
Also, I'd like to make it rw and I would want to format it as ext4
Is this possible? If yes then how?
Disable usb_modeswitch for the respective device.
Okay, I skipped that you already managed to mount the dev.
If it's an RO flash, there's nothing you can do about it.
The manufacturer probably released it that way, so that users don't accidentally erase the shipped drivers and bloatware for which the flash space is usually used.
i want to convert my usb flash to dongle flash, but i donot understand the way that the dongle is work or how did it develope its software i want any one to help me to understand how to programme my owne dongle and how does the dongle work please help me
i know they are the same thing, i want to create my dongle , not to use one created , what i asked how can i create dongle porgrammatically and what requirements i need to create my dongle from my normal USB Flash
You might want to look at a predeveloped solution for that. If you use a USB flash drive for that, and you have a token in the form of a file on that drive, then someone can take the file off of that drive, and copy it to another drive.
another thing, do you mean if i convert my USB flash to dongle flash it will not be very good for security stuff -any one can copy it ?. is that mean the dongle flash hardware specially designed for dongles ?
the last thing i asked about, i want to know how dongles software was developed? how can i develope my special dongle software and what hardware and software requirements dongle is need to be developed?
c80f0f1006