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.

1.1/1.1a versions of the KeyFobDemo images

Other Parts Discussed in Thread: CC2540

Where can I find 1.1/1.1a hex images of the KeyFob Demo?

http://processors.wiki.ti.com/index.php/Category:KeyFobDemo              
    cc2540_ble1.0_slave_keyfobdemo.hex -->KeyFob
    cc2540_ble1.0_master_usb_dongle.hex -->USB Dongle

I can only find references to the 1.0 hex files

Also would those images work with the JavaSimplePeripheral app?

greg

  • Hi Greg,

     

    Greg Sampson said:

    Where can I find 1.1/1.1a hex images of the KeyFob Demo?

    http://processors.wiki.ti.com/index.php/Category:KeyFobDemo              
        cc2540_ble1.0_slave_keyfobdemo.hex -->KeyFob
        cc2540_ble1.0_master_usb_dongle.hex -->USB Dongle

    Have you tried to look in the latest version of BLE stack?

     

  • Yes Igor, the source is there but no hex files. I am sure I could build them, but I am running very short on time and need to integrate this functionality into a much larger project.

    If anyone could upload the two hex files for the 1.1/1.1a stack, it would be most appreciated!!

    greg

  • Hi Greg,

    Read this thread, tell me if it helps.

  • Hi Igor,

    Not quite. Right now I am using the following files in the Fob and Dongle respectively:

    cc2540_ble1.0_slave_keyfobdemo.hex

    cc2540_ble1.0_USBdongle_HostTestRelease_Master.hex

    Both are from the 1.0 BLE Stack. My ultimate goal is to have them work with the JavaSimplePeripheral app. I have been able to get the Dongle and single Fob combination to work. But because I have to support more than one Fob talking to a single Dongle, I need the 1.1 or 1.1a version of the same files.  Per an earlier post, multiple Fobs is supported in v1.1 or v1.1a (cant remember which).

    I am really surprised that on of the TI guys has not just posted the binaries!?!? What's the deal!?!?

    greg

  • Hi,

    May be you'll find attached binaries useful. I have downloaded and installed BLE stack v1.1a,

    found these binaries in Accessories folder.

    8666.Hex_Files.zip

    Greg Sampson said:
    I am really surprised that on of the TI guys has not just posted the binaries!?!? What's the deal!?!?

    Perhaps the holidays?

  • Thanx much Igor,

    But I do have those binaries. The 'cc2540_ble1.1_keyfob_SimpleBLEPeripheral.hex' only has the simple GATT profiles in it. I need to leverage the keyfobdemo as I need the accelometer and eventually the proximity profiles.

    greg

  • The simpleBLEPeripheral is different to the complete keyfob application. I can't help you since I've just reinsatlled and I'm on Linux but please keep in mind the TI guys are not here to solve your problems immediately. In fact it is quite easy to build such binaries. If you can wait till January 2nd, I'll be able to send you these binaries :) Bye!

  • Hi Kazola,

    I was not expecting TI to 'solve' my problem. I was just surprised that pre-compiled version of those profile applications were not either included in the install executable or available for download. Surely someone at TI already has those sitting on his/her hard drive. That is why I expected on of the TI guys to chime in.

    With regard to your offer to send the compiled binaries for the keyfob and dongle, I would graciously accept. I got the JavaSimplePeripheral to work with the unmodified, 1.0 stack implementation of the keyfob (and can post that Java code if anyone is interested). But due to time constraints, I had to move on to other things rather than install the IAR trial, request and wait for the license file, and then compile the code. If you have them already compiled it would surely save me some precious time.

    thanx much,

    greg

  • On January 5th 2012 I've downloaded the latest BLE stack and compiled both things with IAR trial version.

    Please find both attached in this link :) Tell me when you are done with it since they are on my dropbox and I'll delete them. Bye!

  • "Genius" does not begin to describe your worth! Thank you very much. I assume 'CC2540MiniDkDemoSlave.hex' is the hex file for the keyfob? I will give these a go in a few hours.

    greg

  • Tx a lot, iPhone4S demo is working fine with the zip file you have provided !!!

  • Verify the thread then. This way other people can take profit of your experience! :)

  • Hi Kazola,

    Thank you very much for your files. I downloaded them and it works like a dream..

    However I am intrigued though. Because I used the source files from TI, complied them. In fact I got the hex file that is the exact same size as yours. Yet when I loaded my hex file into my keyfob, the accelerometer could not connect. I could connect when I used your hex files.

    My question is then, what are the source files you used to compile this hex file? Did you make any changes to the existing keyfob demo?

    Thanks very much

    Best

    D

  • The sources are the ones provided with the current BLE stack.

    Can anybody verify this thread? I think it is over :)

  • I'm seeing the same things. The accelerometer profile seems to be missing. Guess I need to break out the compiler LOL.

    greg

  • Hi,

    As mentioned in the forum, You need to compile and use the HEX file generated after sources compilation in the C:\Texas Instruments\BLE-CC2540-1.1a\Projects\ble\KeyFob\CC2540DB\CC2540DK-mini Keyfob Slave\Exe

    Compiling the sources to get the HEX is really easy :)

    Works for me !!

    Do no forget to "verify the answer"

    Fred

  • I compiled the source and got a working executable... to a degree. There must be an incompatibility in the configuration that 'JavaSimplePerpherial' does, because I can not get through the init sequence :/  Looks like BLE byte parsing for me.

    greg

  • I'll go ahead and verify the thread, but note that the GATT profile is very different for this code than the existing documentation would suggest. Once I have it all mapped out, I will post the details. I am a huge TI fan, but I have to say that in general the supplementary docs on the CC2450 family really leave a lot to be desired. I certainly appreciate the efforts to create example applications and all the work that went into this (that came out of someone's budget), but I wish they had just spent a week or so revising the docs, consolidating the source, and making hex/binary images for all of the sample apps..

    greg

  • 3808.Keyfob Application - Complete Attribute Table.xls

    I've uploaded the BLE 1.1 Sample app Keyfob Attributes table. As you can see, the handle addresses are very different from the docs you might find on the TI Wiki. I am not sure about the Proximity profile. I believe it starts at handle address 0x20. I also did not fill in the 'Type' field as this changed from v1.0 to 1.1a as well. Feel free to update to add additional information and/or corrections.

    greg

  • Is this the same info as in this thread?

    http://e2e.ti.com/support/low_power_rf/f/538/t/134385.aspx

    I think the link I'm posting already updated the handles.

  • Hi Kazola,

    Could you please upload these files again? 

    Cheers!

  • Not really. I'm on a trip so I do not have IAR here.

    But... come on. You only have to install IAR and compile a single project! It is the KeyFobApp project. When 1.2 is out I'll do a wiki entry. Bye.

  • Hi. The link is dead, could you please repost?

  • Hi

    Thanks for posting the file, but it still doesn't work. No buzzer, no accelerometer, no light and no battery info. 

    Not even the buttons work! :(

    Also I can't run IAR in my virtual windows 7 x86 machine, so I can't even build my own..

    I'm starting to get annoyed with this now! Grrrr

    lol

    Thanks for your attempt though.

  • In fact, running the default iOS project from TI gives me these errors in the output window:

    Found characteristic <ffe1>

    Finished discovering characteristicsCould not find service with UUID <ffa0> on peripheral with UUID 00000000-0000-0000-977E-33047BCBC30E

    Could not find service with UUID <ffa0> on peripheral with UUID 00000000-0000-0000-977E-33047BCBC30E

    Could not find service with UUID <ffa0> on peripheral with UUID 00000000-0000-0000-977E-33047BCBC30E

    Could not find service with UUID <ffa0> on peripheral with UUID 00000000-0000-0000-977E-33047BCBC30E

    Enabling accelerometer

    Could not find service with UUID <1804> on peripheral with UUID 00000000-0000-0000-977E-33047BCBC30E

    Updated notification state for characteristic with UUID <ffe1> on service with  UUID <ffe0> on peripheral with UUID 00000000-0000-0000-977E-33047BCBC30E

    Could not find service with UUID <ffb0> on peripheral with UUID 00000000-0000-0000-977E-33047BCBC30E

    Could not find service with UUID <ffb0> on peripheral with UUID 00000000-0000-0000-977E-33047BCBC30E

    Could not find service with UUID <ffb0> on peripheral with UUID 00000000-0000-0000-977E-33047BCBC30E

    Could not find service with UUID <ffb0> on peripheral with UUID 00000000-0000-0000-977E-33047BCBC30E

    Could not find service with UUID <ffb0> on peripheral with UUID 00000000-0000-0000-977E-33047BCBC30E

    Could not find service with UUID <ffb0> on peripheral with UUID 00000000-0000-0000-977E-33047BCBC30E

    Could not find service with UUID <ffb0> on peripheral with UUID 00000000-0000-0000-977E-33047BCBC30E

    Could not find service with UUID <ffb0> on peripheral with UUID 00000000-0000-0000-977E-33047BCBC30E


    This last one repeats forever.


    This is using your .hex file and the one that comes with BLEStack 1.2.1



  • Hey,

    Well, try to download this file again (from my previous post, I have uploaded new version).

  • I'm not familiar with the outcome, nor BLE... so I guess my help ends here. sorry pal