• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 51 subscribers
  • Views 622 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Powering Up Simple BLE Peripheral

Andrey5924
Intellectual 350 points

Other Parts Discussed in Thread: CC2540

I am just starting with CC2450, sorry if my questions are mandane.

I download file:
CC2540_USBdongle_HostTestRelease_All.hex into Dongle

and file: CC2540_keyfob_SimpleBLEPeripheral.hex into Fob.

I followed the instructions in
User Guide and used BTool to interrogate Complete Attribute Table provided in
User Guide. It works as described only the Handles are shifted. In User Guide
UUID 0xFFF1 corresponds to Handle 0x22; 0xFFF2 – 0x25; 0xFFF3 – 0x28; 0xFFF4 – 0x2B; 0xFFF5 – 0x2F; 0xFFE1 – 0x33.

I have it: 0xFFF1 – handle 0x25; 0xFFF2 – 0x28; 0xFFF3 – 0x2B; 0xFFF4 – 0x2E; 0xFFF5 – 0x32; 0xFFE1 – 0x36.

I am not sure what caused this shift. After I discovered the shift in handles I re-downloaded .hex files
into both Dongle and Fob but no changes.

What causes the shift?

Should I expect to find the same Attribute able in another programs, like HIDEmuKbd.hex ?

  • 0
    Intellectual 490 points

    The shift involves the changes that were made to the newer version of these files. The versions that you downloaded to the keyfob and dongle are version 1.2. The user guide was written using examples from 1.1 or 1.1a. Because of the new additions to 1.2, the program enumerated the handles for the UUIDs differently, and that caused a shift in the handles. TI has yet to update the User Guide to take into account version 1.2. You should be fine with just following the instructions of discovering characteristics by UUID and following those handles rather than ones shown on the guide and I would do the same for any other program. Hope that explains it.

  • 0 in reply to Misael
    Intellectual 350 points

    Thank you Misael,

    This explains ...some of the problems I am having here.

    Maybe you can help me more? I can not make HIDEmuKbd program going. There is no pre-compiled file for this program in the kit.

    I compile my own with IAR, write it to Keyfob. The keyfob advertises, (seemingly) connects to Bluetooth inside my Laptop and then communications stop. Nothing happens when I press the Fob buttons and (this is the most critical part for me) nothing happen when I press 'Caps Lock' on my keyboard (LED supposed to come up according to description)

    Do you have any suggestions? 

    ...

    In addition, I see that connection made by HIDEmuKbd and SimpleBLEPeripheral is different then connection made by file CC2540MiniDkDemoSlave.hex

    When I write CC2540MiniDkDemoSlave.hex in the Fob and connect as new device an extra section opens up in Bluetooth panel in Laptop. It allows me to do proximity detection and when i press Button (on Laptop Bluetooth Panel) Find Device Fob starts beeping and LED blinks. I believe this difference has something to do with Pairing/Bonding/Secure Connection but do not have yet accurate interpretation. I suspect my HIDEmuKbd program does not work because something is wrong with  Pairing/Bonding/Secure Connection.

    Any ideas?

    My immediate goal is to make HIDEmuKbd working.