hasermichael.blogg.se

1. Bluesuite 2.6.2 how to#
2. Bluesuite 2.6.2 pdf#
3. Bluesuite 2.6.2 serial#
4. Bluesuite 2.6.2 drivers#
5. Bluesuite 2.6.2 driver#

I can! Not just that, I can dump the stock firmware.īrilliant. Open up BlueFlash, choose USB-SPI as the transport and see if you can connect to it. The FTDI board has a 3.3V output but it probably doesn't have the current capability for the HC-05, which can draw surprisingly high current at times (over 50mA). The device on the left is a bit of perfboard with a barrel jack and a 3.3V regulator on it. I used 100ohm resistors as jumpers, it seemed like the right thing to do. It's at this point that most people build a special programming clip or holder, but I am far too lazy for that and just soldered some bits of wire straight to the board.Īgain the wiring configuration is described on lorf's github page. As you can see on this lovely pinout diagram, they're all grouped at the end. To see if it works we need to access the SPI pins on the HC-05. In this zip file, under lib-win32 find our new usbspi.dll and copy it into the BlueSuite folder. Head to and download the pre-built drivers. Now go to the folder where your BlueSuite software was installed (for me, C:\Program Files (x86)\CSR\BlueSuite 2.6.2\ ) and rename the usbspi.dll to something like usbspi_original.dll.

Bluesuite 2.6.2 driver#

(Note: Make sure you really did select the FTDI device, and not, for instance, your USB mouse, as this will cause it to stop working, and you will have to try and restore the driver for your mouse without using it, which may be difficult.)

Bluesuite 2.6.2 drivers#

Select your FTDI device and then scroll through the replacement drivers to select libusbK, then hit replace driver. Download and run this executable, plug in your FTDI cable and click options > list all devices. As described on lorf's github page, there is a convenient tool for doing this called Zadig. Unfortunately – this is all on windows, by the way – unfortunately the windows COM port mechanism is not sufficient for our needs, and we will have to (temporarily) replace the FTDI driver with a libusb driver for lower level access to the chip. Thankfully, if it is a counterfeit board, it has not been bricked (FTDI have a history of pushing driver updates that brick knockoff chips).

Note that DSR is labelled on the silkscreen of that board as RSD. These are available on the edge of my breakout board, so I added another row of header pins. We'll need four pins to do this, DTR, RTS, RI, and DSR. The plan is to bitbang the SPI protocol using the auxiliary pins of the FTDI board as GPIO. Yet it's freely available, for a given value of free.

Bluesuite 2.6.2 pdf#

Every PDF you download has your username and email watermarked across each page, and a warning not to redistribute it. There are other links, and only part of the category tree is visible. Once they've approved you, you should be able to download a copy of BlueSuite – I got BlueSuite v2.6.2 as it was the latest version. The download page for their software is and if you visit that link you'll be prompted to register. But you have to register with CSR to get it. Note: the SDK and other development tools are not free and not available to the public, but the BlueFlash software suite, which can reprogram chips and change their settings, is free. The first step is to acquire the BlueFlash software from CSR. This is possible entirely due to this project on github and its various contributors.

Bluesuite 2.6.2 serial#

There is an official CSR USB-SPI programmer, and it costs OVER TWO HUNDRED POUNDS.īut there is a way to rewrite the firmware using just an ordinary FTDI serial adapter. Parallel ports are soooo last millennium.

It seems that all the copycat tutorials on doing this also need a parallel port adapter. The process involves building an LPT (parallel port) adapter which then bitbangs the SPI communication to the chip. And software can be pirated.įrom what I can make out the first person to realize this (or at least the first to write on the internet about it) was Robin Gross, whose site is called Byron's Blog. What makes the RN-42 more feature filled, and thus more expensive, is the software it's running. The thing is, under that shielding, the RN-42 uses virtually identical hardware to the HC-05, and its main chip (the CSR BC417) is the same. Here's a picture from the internet of an RN-42 module, a far more advanced bluetooth module, which costs over £20: The HC-05 module is a bluetooth serial adapter and this one cost me £2.03: Part two builds an example wireless gamepad with the result.

Bluesuite 2.6.2 how to#

Part one explains how to load an HC-05 module with the firmware from the RN-42 without the need for a parallel port programmer. This project draws hugely on the work of other people.