This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CC2640: bluetooth low energy file transfer service example code

Part Number: CC2640
Other Parts Discussed in Thread: CC2564

Greetings, TI,

We have an embedded product using a CC2640 as a controller.  We chose this partly because it has on-chip BLE support, which we would now like to engage.

We wish to send/receive files to a nearby PC which also supports BLE file transfer.  On the PC end, I believe the computer is expecting to use an existing BLE file transfer service UUID.

Can you point to any existing BLE code examples which you believe would come up speaking this existing BLE service ID, and run "out of the box"?  It doesn't have to be written native on a 2640.  I believe your example BLE applications could be ported to the 2640 if we can observe the data structures and callbacks needed to support the file transfer service UUID from any product.

Thank you!

  • Hi,

    I am not aware of any file transfer profile for Bluetooth Low Energy. If you have some references, could you share them?

    Best regards,

  • The BLE spec defines candidate profiles:

       FTP protocol UUID = 0x000A

       Object exchange UUID = 0x1106

    My question arises from the simple observation that every PC with BLE and every smart phone has a "file transfer over BLE" option, and they readily pair, implying use of a pre-defined protocol they both recognize.  The problem is, how are these implemented?   Since they use BLE, they have to be using a pre-defined UUID profile and ATT set.  And if such a protocol is known, then I'm wondering if any TI example based on the same profile has been written.

    Thanks!

  • Hi,

    FTP (File Transfer Protocol) and OBEX (OBject EXchange) are two Bluetooth Classic profiles. In other words, these two profiles are not compatible with Bluetooth Low Energy and you won't be able to send a file using the function "file transfer over Bluetooth" with a CC26xx device.

    Let me know if I can do something else to help.

    Best regards,

  • Thank you very much, Clement.

    This was an unexpected but educational reply, and it will send me back to school! I was assuming that any profile listed in the BLE spec was also a used mode. It would seem to be otherwise.

    It turns out that I have a mechanism to explore this further - I have an SDR (software defined radio) which can collect PHY raw data for detailed packet analysis and verification of the protocol used. If any surprises turn up from this research I'll report back on the forum.

    I'd like to add one last question at this time. Given that FTP is a classic not LE mode, and I was searching the LE academy for examples, would you know of any file transfer example code on a classic BT platform?

    Thank you again, this re-oriented me immensely,

    Belvin

  • Hi Belvin,

    Thank you for your nice words.

    FTP (File Transfer Protocol) and OBEX (OBject EXchange) are two Bluetooth Classic profiles for files transfer. You may want to review our CC2564 device (which is a dual mode device i.e. both Bluetooth Classic and Bluetooth LE). There you will find some examples for OBEX (and maybe FTP but I am not sure).

    If you have further questions regarding these protocols or the CC2564 device, I will kindly ask you to open a new thread in order to have Bluetooth Classic experts to comment.

    I will also ask you to mark this thread as resolved to help other readers to find it.

    Best regards,

  • resolved, thanks.  attempted X in resolved button is failing.