I couldn't flash the 2 years old sniffer firmware with the iOS application or with the nRFGo studio.

When I packaged it with nRFGo studio and tried to upload as bootloader it always said "Timeout waiting for acknowledgement from device. Failure to upgrade target. Error is: No data is received on serial port." I have tried different settings, rates and my device was in DFU mode.

With the ios application, at "custom firmware", I could not manage to get the init file right. I could not find the init file anywhere and using the .dat file created with nRFGo studo did not work because of some icloud issue. (Uploading the file is ok, but it is not selectable from the application).

Regards,
Gellért

Hi,

Is this firmware source code available somewhere ?

Thx.

I have a problem running the MDBT40-256RV3 module with this firmware in my project.

I have programmed the brand new MDBT40-256RV3 module purchased at https://www.adafruit.com/product/4076:

adalink nrf51822 --programmer stlink --wipe
--program-hex ./Adafruit_BluefruitLE_Firmware/bootloader/bootloader_nrf52_0008.hex
--program-hex ./Adafruit_BluefruitLE_Firmware/softdevice/s110_nrf51_8.0.0_softdevice.hex
--program-hex ./Adafruit_BluefruitLE_Firmware/0.8.0/blespifriend/blespifriend_s110_xxac_0_8_0_170925_blespifriend.hex
--program-hex ./Adafruit_BluefruitLE_Firmware/0.8.0/blespifriend/blespifriend_s110_xxac_0_8_0_170925_blespifriend_signature.hex

The module is not recognized by the software(https://learn.adafruit.com/adafruit-fea ... le-library), the LEDs do not flash.

Test reports the error:

Adafruit Bluefruit AT Command Example

Initialising the Bluefruit LE module: OK!
Performing a factory reset:
AT+FACTORYRESET

<- ??
??
Couldn't factory reset

Can we please get a reasonable list of what changed in the various firmware versions? The lack of source code means that the git binary check ins are basically useless to glean any wisdom. It was said that 0.8.0 was mostly to fix a specific bug related to losing configuration. But, what is 0.8.1? Is it just 0.8.0 out of beta or what does it do?

The last time someone asked this they were directed to a web site. Guess what, that page stops at firmware version 0.7.7. So, it still leaves me shrouded in mystery.

As in the topic, setting a callback on two GATT characteristics, as the example does, works fine. Three works fine. Four locks up the sketch hard as a stone. I've tried delays in between, changing the order, everything I can think of. I tried doing the things that setBleGattRxCallback does but manually in my sketch and it still locks up. There doesn't appear to be a way to get four or more callbacks registered at the same time. It's pretty easy to confim this, just a small edit to the callback example to add two more GATT callbacks will cause the example to lock up too. So far as I can tell this is a firmware bug of some sort.

Another thing I tried was calling setBleGattRxCallback once and then manually using lines like:
AT+EVENTENABLE=0x0,0x2000

To enable more GATT callbacks (this seems undocumented but I think I'm doing it properly). This will still lock up at the 4th registered callback. The call never seems to return.

According to this document : https://www.bluetooth.com/specifications/gatt/viewer?attributeXmlFile=org.bluetooth.characteristic.battery_level.xml
Battery level characteristic is assigned to UUID 0x2A19.
The value set with the AT command AT+BLEBATTVAL use UUID 0x2A1B instead.

Since the latest windows 10 update (1809) display this characteristic, it would be nice if you could fix this.

It would be interesting to be able to modify it.

Beta 0.8.0 has been in beta for 6 months, and it seems to solve (for some) the "couldn't factory reset" problem on the Feather Bluefruit 32u4 and M0 boards:

https://forums.adafruit.com/viewtopic.php?f=57&t=122726&start=15#p625126

and

https://forums.adafruit.com/viewtopic.php?f=57&t=106888&p=658252#p658152

What I'm hoping will happen is that 0.8.0 is tested to the point that it can be reliably used in production, i.e. waiting for 0.8.1 -- thanks!

I'll keep updating the forum posts with reliability info, as we're hoping to be able to use these in production. Thanks!

I have a sketch that works fine on version 6.7, however when I update to 7.x or 8.0 too many bytes (and the wrong bytes) are added to my characteristic. I am converting a float to 4 bytes and adding them to the characteristic. For some values of "Chromium" the code still works on the newer firmware, but about 10% of of the value are sent as 8 bytes instead of 4. Serial monitor indicates only 4 bytes (though they are not the correct 4 bytes) are being send but a sniffer shows otherwise. I'm at a loss to what may have changed between versions to cause this. See my code below:

union u {
float f;
uint8_t s[4];};

u both;

float Chromium;
Chromium = 0.26 + 0.0001 * random(0, 10);
uint32_t index = CrVal;
both.f = Chromium;

ble.print("AT+GATTCHAR=");
ble.print(index);
ble.print( ",");
ble.print(both.s[3],HEX);
ble.print("-");
ble.print(both.s[2],HEX);
ble.print("-");
ble.print(both.s[1],HEX);
ble.print("-");
ble.println(both.s[0],HEX);

I'm using a Feather 32u4 Bluefruit LE, talking to the Bluefruit over SDEP/SPI, and using AT+BLEHIDEN to make it act like a keyboard. I've been searching around for quite a while, but can't seem to find a way to get the current key lock LED states (num lock, caps lock, scroll lock) from the host. I'd like to be able to update the state of LEDs connected to the Feather with the current key lock states. Is this possible? If not, is it something that will be added in the future (maybe as another event callback)? Thanks!

Hi,
I was wondering if you have any plans for adding AT-commands for adding/accessing characteristic descriptors (such as "Presentation Format" or "User Description") to your Bluefruit LE SPI friend firmware.

Installing conncted/disconnect callbacks used to work:
void Adafruit_BLE::update(uint32_t period_ms)

You can work around it easily but figured it's better to let you know

My Feather is flashed to be a keyboard with minimal changes from "hid keyboard" example.
I have updated my Feather M0 to 0.8.0.
After that I see the following behavior connecting to Windows 10:

1. Initial connect - fine.
2. After device reboot or Windows bluetooth OFF-ON, the device begins blinking blue with random intervals from around 200 ms to 3 seconds, and Windows mostly shows "Connected", sometimes changing to "paired".
3. Whatever Windows shows, keyboard doesn't work.

I'm trying other firmware versions so far, but maybe you have any ideas on what this is?

Flashing various Bluefruit LE Friend-type devices (Feather M0 Bluefruit, Bluefruit LE Friend, Bluefruit LE UART) with 0.7.7, I can no longer connect via the UART service with Bluefruit LE Connect then switch to command mode by typing +++. Confirmed that this works as expected in 0.7.0 and earlier. I can swap modes when connected locally (via picocom on the Bluefruit LE Friend, or via the atcommand sketch), just not over the app the connection.

Guessing this is related to the new \+ escape char (added in 0.7.7, according to the release notes).

can you provide the firmware for ‘xxaa’ chip （nRF51822QFAA ）

I would find this information helpful, and I'm sure future devs would as well.

Nordic has released a newer version of the BLE sniffer firmware that plays well with the latest version of Wireshark. I tried to update to this new version pca10040_51296aa in a V3 (black) board but execution is failing with a trap at 0x00000576 (as seen in GDB while using BMP to flash the board).

I have soldered the 32.768 KHz crystal and I am able to switch back and forth between the Adafruit custom version (no32KHz) as well as the old official sniffer firmware release from Nordic website. So, I am confident that the programming steps are proper.

Since 1.x wireshark is quiet old, it would make more sense to support the latest version of firmware in the sniffer.

The Adafruit_BLEMIDI.send() call fails when sending a MIDI message less than 3 bytes. The resulting AT+BLEMIDITX command fails when this is attempted. There are several MIDI messages that are 2 bytes, including Channel Pressure, and Program Change. Please allow <3 byte messages to be sent!

I recently updated a V2 Bluefruit LE Friend to the version 0.8.1 firmware when prompted by the Bluefruit app. The OTA DFU went fine, but on reconnection, I was prompted to update the firmware again. A check of the device information showed the Software Revision has this value:

0.8.0 - Apr 10 2019

I also have a Feather M0 Bluefruit LE, which I also upgraded to latest firmware. This seemed to work fine and reported the expected Software Revision value:

0.8.1 - Apr 10 2019

Since the LE friend uses the BLEFRIEND32 firmware build, and the M0 used BLESPIFRIEND, I have to assume the former has an incorrect build number. I tried downgrading to the actual 0.8.0 and 0.7.7 versions of BLEFRIEND32, then upgrading again, with the same result. The issue seems to be in the release.

Can’t get any update info from 0.80.
You ‘ve done a pretty good job on Ver.0.80. But what?

Provide a way to save multiple bonding information, so a HID device is not limited to a single host. A user then would be able to pair multiple devices (eg., computer, htpc, laptop, tablet & phone), and switch between them by pressing a button.

Possible implementation:

AT+GAPSETACTIVEBOND=5 (switch to bonding slot number 5)

any other GAP command (like AT+GAPDELBONDS) will then work with this slot.

Readme product link for Bluefruit LE Friend V1 and Bluefruit LE Friend V2 Point to same location.

What are the steps for flashing the board over SWD?

I was able to get the sniffer firmware on the BLE friend v 2.0 with the following commands in JLinkExe:

JLink>device NRF51822_XXAA
JLink>erase
JLink>loadfile ble-sniffer_nRF51822_1.0.1_1111_Sniffer_No32kHz.hex
JLink>r
JLink>g
JLink>q

Trying to load the 0.6.2 or 0.6.5 blefriend32 images as above just results in a dead device.

Hello,

I wonder if you have or are planning to release the firmware source code with an open or closed license? It'll be a great study material for those of us, like myself, which have invested some time learning the nRF51 platform but which haven't got that far developing BLE code on it?

Thanks for your good work!

Well, after attempting to make my bluefruit a central and debricking it a couple times (THANK YOU FOR RASPI INSTRUCTIONS!) I've resigned to the fact that I'm probably going to have to go through the whole nordic process.

I was wondering if you were planning to implement central capabilities for it? I would love to be able to scan for devices with it and dump the data out to serial. There's a load of neat projects that could be done with it!

If you've already started down that road and need another tester please let me know!

Thank you for an awesome fun product! :)

When using the AT+GATTCHAR command, only the first four bytes are displayed even though it supports up to 20. Also if there could be a way for the MCU to be notified that a service characteristic has been changed instead of having to poll for new data.

I'm planning on developing a product that uses hardware based on the BluefruitLE and would like to use the firmware provided in this repository. I would just like to ask if it's possible for me to sell this product shipped with this firmware? And if yes, is there anything else I need to do, aside from crediting that the firmware was developed by Adafruit, or stuff I cannot do?

The repository has no license and I have done a bit of googling only to find this single post which does not exactly answer the question in the thread.

Please say the files and the order to use. Board is not responding after using sniffer firmware.

If I want to program as normal (5.0) it's broken too. What is the right order ?

Is there a way I can access a change log of firmware features?

Any chance to get the minimum characteristic length changed from 1 byte to 0 bytes? It’s a perfectly valid length, and appears to be supported in Adafruit's own nRF52 library, along with the underlying Nordic SDK and other BT SDK's I've briefly surveyed.

I do have a real use case for this. I'm implementing a simple peripheral on both Bluefruit and on Linux, with a protocol that can have zero-size characteristic writes in some cases. (Something like the UART service, but line-oriented, using a write size of less than 20 bytes to indicate the end-of-line condition.) It works fine in BlueZ on Linux, but then I found zero-size characteristics aren't supported by Bluefruit. It’s easy to work around in this case, but supporting zero size would be even better.

Hi - is the source code for this available?

If so, please could you add a link to the README in this repository? It might be helpful to others... thanks!

I am unable to write values to the TX characteristic with type: CBCharacteristicWriteType.WithoutResponse, .WithResponse works as expected.

self.blePeripheral.writeValue(data, forCharacteristic: self.txChar, type: CBCharacteristicWriteType.WithoutResponse)

I am on 0.7.0 with the blefriend32.

I was using another BLE module (not from adafruit) that had the same issue. They reported to me: Engineering found had some minor mismatch in the BLE properties that conflicted with iOS after they fixed it, not sure if that helps any.

Thanks for all the hard work!

I realize that some people believe 30 characteristics to be a whole lot. I do not. I have found ways to pack values into structs and pass them that way but it has limited the utility of descriptors. If I had more characteristics I could send each piece of data in a separate characteristic and define it with exponent and the unit. That would allow my characteristics to be more open. Then other apps could easily consume data from my project without having to get struct definitions ahead of time. Is this possible with the current hardware?

Hello, may I ask if these firmware can be flashed into 52840? Its capabilities are stronger than nrf51822. I look forward to your reply.

Hi!

I'm currently working on a project that requires me to process data sent using the Adafruit's SDEP protocol.
I'm not sure if it's possible to open source part of the firmware that involves SDEP? I understand that fully open sourcing the firmware isn't possible due to copyright restrictions from Nordic.

Thanks in advance!

On the product page FAQ, it says ANCS should be expected sometime during version 0.7. I was wondering if there are any updates regarding to ANCS support in the near future?

Related, in another issue that has since been closed it is mentioned that the source code for the firmware would be made open eventually, however that was nearly two years ago. I'd be happy to contribute to adding ANCS support if it were made open source, and I imagine many other devs would like to help as well.

Thanks -SH

What is the reference voltage range used for ADC sampling and the value range of sampling results when using AT+HWADC command

Hi there, we seem to be running into a limit with bonded devices, is 7 the max?

Is there a way to adjust the max bonded devices? We're trying to bond one peripheral-mode Bluefruit LE via the GAP profile, as an HID, to 15 different centrals.

Conversely, if there another way to initiate bonding other than HID? Seems like we should be able to set a characteristic as "secure" in our GATT and the pairing/bonding process should start upon attempted access?

So I am fairly new to this sort of thing, it does not appear that this file is available with the downloaded zip from Nordic, so I am guessing it has to be created. The instructions on Nordic's site about creating a file are sort of cryptic to me.