- #CSR USB BLUETOOTH DEVICE IN DFU STATE MEANING MAC OSX#
- #CSR USB BLUETOOTH DEVICE IN DFU STATE MEANING MOVIE#
- #CSR USB BLUETOOTH DEVICE IN DFU STATE MEANING INSTALL#
- #CSR USB BLUETOOTH DEVICE IN DFU STATE MEANING DRIVERS#
- #CSR USB BLUETOOTH DEVICE IN DFU STATE MEANING UPGRADE#
That did it! After changing the setting and rebooting VM, I was able to connect RN52 over USB as the Windows VM detected a new observations during and after the DFU process were true for me as well. Well, changing this to "Connect to virtual machine" enforces USB devices that when physically connected always connect to VM if it is running. Most devices will adhere and ask to connect to Mac (host) or Windows (VM). Normally, default vmware configurations are sufficient but in this case of attaching RN52 over USB, the Windows instance (Win 8.1 where DFU Utility is installed), under USB & Bluetooth vmware settings, the default when a USB device is connected is "Ask what to do".
#CSR USB BLUETOOTH DEVICE IN DFU STATE MEANING MAC OSX#
Here was my issue: I run Mac OSX with all Windows variants configured in virtual machines using VMWare Fusion. If that failed was going to try SPP method. Thank you both and was able to get my RN52-1/RM module FW updated to 1.16 following suggestions and MChips original instructions for DFU over USB.
#CSR USB BLUETOOTH DEVICE IN DFU STATE MEANING UPGRADE#
It may or may not work to upgrade the current module.įor ordering modules with v1.16 firmware, I suggested ordering from Microchip Direct using the part number "RN52-I/RM116". USB requires clean signals for proper connection, so this becomes a challenge. I have seen customers with issues doing this in the past. I said it might work to solder wires to the USB pins in order to add a USB connector. You mentioned that you were using a breakout board, which didn't have USB implemented. To upgrade from v1.10 to v1.16, you'll need to use the USB pins, and select USB in the upgrade utility.
This is a new feature that was added in v1.16. I informed you that it wasn't possible to upgrade firmware over UART in v1.10. It was good talking with you this afternoon.
#CSR USB BLUETOOTH DEVICE IN DFU STATE MEANING MOVIE#
Also I didn't really proofread this post (time to watch a movie with the wife :) ) so I am sorry for any grammar mistakes. I hope this helps and I will respond to questions, because I know how frustrated I was in trying to upgrade the firmware. The installer said it failed, but it booted fine and I can get into CMD mode via UART the new version is V1.16 and I can use the new features It hung on there for a while and I was thinking that GPIO3 was still HIGH so I took the voltage off of GPIO3 and rebooted the device. at the end of the upgrade it said attempting to to boot device in run-time mode. Followed the instructions on the screen and it uploaded great.Ĩ.
#CSR USB BLUETOOTH DEVICE IN DFU STATE MEANING INSTALL#
Also Windows takes FOREVER trying to install the driver so I made sure to hit 'Don't look with Windows update for the driver' and it installed the driver really quick.ħ. (a second driver from when I plugged in the device) So when the device shuts off I would not keep turning it back on and I would check to see if windows is looking for a driver. Finally I noticed that windows was installing another driver it was 'CSR driver in DFU mode' or something like that. I thought the device shut off so I pushed my power button on and the device came on then it shut off. One thing to note when it was upgrading the firmware it said something like attempting to boot the device in DFU mode and the green and red lights turned off. Ran the utility following the instructions making sure to choose install over USB.Ħ.
#CSR USB BLUETOOTH DEVICE IN DFU STATE MEANING DRIVERS#
Windows recognized the device and installed the drivers for the device.ĥ. Downloaded the proper firmware and re-ran the installer and made sure I installed the USB drivers.Ĥ. I put the USB to the shared ground I was using for everything else.ģ. You will want to double check that before continuing. In my usb cable case green was USB+ and white was USB. Connect the USB+ from the cable to the USB+ of the chip and do the same for the USB. I previously soldered headers on my breakout board so I am connecting to my device through a breadboard. So just make sure you drive GPIO3 high on 3.3v.Ģ. (In the documentation is describes using a voltage divider).
I did not use the 5V that is coming from the USB cable to drive GPIO3 high. I have a RN52-1/RN110 breakout board from Sparkfunġ. So I have a simple list of my steps below what I did. He couldn't guarantee success, but my project needs these features so I decided to try it. So I connected to the 'USB - and the USB+' and try to upload the firmware over USB. The support tech suggested to try and connect via USB.
My RN52 is on a breakout board and I don't have an Evaluation Kit. (See full answer below) The short answer I received is that in V1.10 the ability to upgrade firmware over UART is not available so you are stuck unless you can upgrade over USB. I was having the same problems upgrading my RN52-i/R110 over UART from v1.10 to v1.16.