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.

TI Bluetooth LE wiki-page (ti.com/ble-wiki)

Other Parts Discussed in Thread: CC2541, CC2540, BLE-STACK

Hi all,

You may already know about the Bluetooth LE wikipage that we maintain, but if not you should know that it's a good place to find answers for frequently asked questions, links and guides.

ti.com/ble-wiki 

If you find anything wrong or you miss some information, please reply to this post, or simply register on the wiki to edit contents and make contributions yourselves.

Best regards,
Aslak 

  • Hey, the new look of the wiki is great! I like the new examples. I think this will be a nice intro to newcomers. Well done, Aslak :) It seems a nice, central place for BLE resources to me.

  • Hi .. when will code be coming for IOS demo for the SensorTag?

    It is blank on the wiki page.

     

    Thank you,

    Steve 

  • I had seen a youtube video where HTC phone has communications with the Keyfog board but in the wiki there isn't examples for Android except Motorola phones.

    Is it possible to find some example for Android Samsung S2?

  • Hi Juan,

    Juan Moya said:
    Android Samsung S2?

    I don't think Samsung Galaxy S2 support Bluetooth low energy.

    Best Regards

  • Hello,

    Thxs. You are right.

    S2 --> BT v3.0+HS

  • Hello Aslak,

    the wiki page is a very interesting place where to find useful info, thank you.

    One thing I miss and that seems quite difficult to find anywhere is any reference to import/export control regulations, not with regard to EMC related aspect, but to cryptography.

    Bluetooth is a so nice technology to be used all over the world because of its free frequency, but having the possibility to include encryption (especially low-energy version with AES 128bit) it seems that care should be taken when importing/exporting.. is it true? Or are there any exceptions for bluetooth well know technology? It seems so strange that one should care about this when manufacturing a simple product such as a remote control or a sensor just because it maybe enables security in the connection (or maybe even it is not using it, but just because it is a feature of the tech)..

    Do you have (and maybe can add to the wiki) any useful guide on how to approach this aspect? Thank you very much.

    Best regars,

    Antonio

  • I have searched far and wide and cannot find the alternate pin definitions for the CC2541. The Block diagram shows that it has 2 UARTs, but can anyone tell me what pins the TX and RX signals are on. If you can, how about sharing the rest of the alternate pin definitions.

  • http://www.ti.com/litv/pdf/swru191d

    • CC253x/4x User Guide. (Rev. D)  PDF  206312 Feb 201313,954 on page 81 Table 7-1. It would be nice if it was in the Data Sheet.
  • I am finding the table of alternate peripherals a little confusing. I understand the concept that there appears to be a primary mapping for the Peripheral function and an Alternate mapping for the same functions. It is just unclear on how to code for either. I am assuming if nothing is coded, the primary configuration is the default. 

    The Users Guide has the following:

    "Note that peripheral units have two alternative locations for their I/O pins; see Table 7-1. Priority can be set between peripherals if conflicting settings regarding I/O mapping are present (using the P2SEL.PRIxP1 and P2DIR.PRIP0 bits). All combinations not causing conflicts can be used. "

    If I want UART0 on Port 0 bits 2,3,4,5 that appears to be the default. If for UART1 I want them on Port 1, bits 4,5,6,7 then I need to select the Alternate. Can I select the alternate for some pins but not others? Is there a typo in the quote above where there is a missing "x" in P2DIR.PRIxP0? Do I set the value for each bit to "1" for the Primary and "0" for the Alternate?

     

  • Hi,

    thanks a lot for compiling all this information! :)

    These two links in your wiki page point to not up-to-date documents:

    CC2540 -> CC2540DK-MINI User’s Guide
    http://www.ti.com/lit/swru270

    CC2540 -> CC2540DK-MINI Quick Start Guide
    http://www.ti.com/lit/swru272

    in those documents, they say to write 01:00 to characteristic handle 0x0048 in order to enable button notifications.
    this is incorrect.
    as explained here: http://e2e.ti.com/support/low_power_rf/f/538/t/311270.aspx
    in order to enable button notifications in the keyfob found in BLE-CC254x-1.3.2 and BLE-CC254x-1.4.0,
    we need to write 01:00 to characteristic handle 0x0037.

    Could you please update your wiki page with the correct links of the "CC2540DK-MINI User’s Guide" and "CC2540DK-MINI Quick Start Guide"?
    (or update those two documents if they do not yet exist)

    Best regards,
    David

  • Hello,

    My question is about driving an LCD with the TI BLE-stack.

    I want to drive a New Haven CoG LCD using the TI BLE-stack running on a connectBlue OLP425.  If I use the same cc2540 pins as those defined in the TI BLE-stack file hal_lcd.c, lines 85-102, to connect to their corresponding inputs on the New Haven LCD CoG will the TI LCD driver make the New Haven LCD work?  If not, what other LCD would work?

    reference info:

    connectBlue OLP425

    http://support.connectblue.com/display/PRODBTSPA/cB-OLP425+cB-OLS425+cB-OLS426+Electrical+Mechanical+Data+Sheet

    New Haven Chip on Glass LCD

    http://www.newhavendisplay.com/specs/NHD-C12832A1Z-FSW-FBW-3V3.pdf

    Thanks,

    Pat Dolan