• State Resolved
  • Locked Locked
  • Replies 8 replies
  • Subscribers 52 subscribers
  • Views 870 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.

CC2541 as a standalone product

Robert Roth
Intellectual 575 points
Other Parts Discussed in Thread: CC2541

Can the CC2541 Keyfob be purchased without the developer kit.  A $100 beacon is going to be a tough sell.

Thanks,

Bob Roth

  • 0
    TI__Guru 56590 points
    Hello Robert,
    You could buy the CC2541 sensortag instead which is much cheaper:
    www.ti.com/.../cc2541dk-sensor
  • 0 in reply to Eirik V
    Intellectual 575 points
    Eirik,
    Unfortunately we have re-written the firmware on the CC2541 Keyfob and the Sensortag will not not run the app. Any suggestions?
    Thanks,
    Bob Roth
  • 0 in reply to Robert Roth
    Mastermind 8695 points

    Swap out the profiles and change the GPIOs associated with the buttons. The sensors are disabled by default. You could leave out the services that enable them. Unless the buzzer is important to you, the products should be interchangeable.

  • 0 in reply to Peter Borenstein
    Intellectual 575 points
    Thank you Peter! I'm looking at it now. When you say swap out the profile are you talking about all the files under profiles or just broadcaster.* for peripheral.* Or gap? I'm really unsure how to proceed.
    Bob
  • 0 in reply to Robert Roth
    Mastermind 8695 points
    You have two options: Put your App header and c files into the sensortag project OR copy the sensortag hardware files into your modified keyfob project, and copy the project defined symbols

    The first option sounds easier. You only need to copy over the broadcaster and peripheral files if you made edits to them. Swap out Sersortag.c/h, SersorTag_MAin.c, and OSAL_SensorTag.c for your own app files.

    The Sensortag has a bunch of additional sensor profiles like gyroservice.c and humidityservice.c. You can leave those in if you like. Since your App.c file doesn't include the header files, IAR should ignore them.

    The keyfob project uses proximity and battery service profiles. You will need to copy those over if your application uses them. The battery service doesn't work on the sensortag without edits. There have been a few E2E posts on the subject.
  • 0 in reply to Robert Roth
    Intellectual 410 points
    Hi Bob,
    Its better to get a new part from some other manufacturer. These TI employee are jsut toying with you. They know jack ***.
  • 0 in reply to melissa walraven
    Mastermind 8695 points

    That's the saltiest thing I've read all day. I'm not a TI employee.

    How about you go back to blinking LEDs on Arduino n00b.

  • 0 in reply to Peter Borenstein
    Intellectual 575 points

    Peter,

    Thanks for the insight.  The project is running and is back on track.

    As for Melissa, Hey this ain't Facebook!!  Although I understand your frustration with customer support, it is a industry wide problem.  It is not just Ti.  

    When you work at this level you may as well get used to being on your own.  Grab the schematic and dig into the code.

    That's why this forum is such an important resource.  We are all pulling together and supporting one another.  It is our Community.  We all have the same goal here; to create exciting products that hopefully will make a buck.

    Once again, thank you Peter for all your help.

    Bob Roth