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.

CC2652RB: Does the TI Starter App cache services?

Part Number: CC2652RB
Other Parts Discussed in Thread: SENSORTAG-SW, SYSCONFIG

I've observed this a few times... I have been running project_zero and after removing everything having to do with buttons in the code/files, I still see it listed on my TI Starter app.

I assume this is cached on the app side, but could it be on the side of the CC2652? If I'm adding and modifying services, how do I make sure they are current in TI Starter?

These are the only services I'm adding:

LedService_AddService(selfEntity);
DataService_AddService(selfEntity);

  • Hi Matt,

    Project Zero and the accompanying TI SimpleLink Starter App is provided for out-of-box demonstration purposes and does not account for dynamic service changes.  The SENSORTAG-SW source code is available for both Android and IOS, you would need to modify this accordingly to fit your needs.

    Regards,
    Ryan

  • Totally get that. But open up LightBlue app and I still see a UUID for LED1 (there should only be a UUID for LED0 based on my code), which I removed, and the button services, which are neither registered nor do any button files/code exist in my project anymore. The only thing I can think is that they are cached somewhere on the chip and need to be purged?

  • I've also tried updating the LED service UUID and LED0 UUID without any update to the UUIDs in either iOS app. Oddly enough, I can still toggle my LED0 by writing to that service.

    This is still the case after a power cycle and loading empty.c then reloading project_zero.c. These files are definitely the ones being compiled, as the compilation throws errors if I remove any lines of code. I must be missing something...

  • Hi,

    Actually, this is not the app but the OS (iOS / Android) of the device which cache the profiles.

    You have to force your mobile phone to forget about the old profiles by power cycling it. In addition, you may have to manually remove the device from the list of the Bluetooth devices your smartphone is paired with. Please see here for more ideas or details.

    Best regards,

  • This makes a lot more sense. Since it's the name being cached, changing that in Sysconfig during development is also possible, or overwriting some random characters to these:

    // Device Name
    uint8_t attDeviceName[GAP_DEVICE_NAME_LEN]= "ESLO BAW 2";
    
    // Advertisement data
    uint8_t advData1[] =
    {
      0x0b,
      GAP_ADTYPE_LOCAL_NAME_COMPLETE,
      'E',
      'S',
      'L',
      'O',
      ' ',
      'B',
      'A',
      'W',
      ' ',
      '2',
    
      0x02,
      GAP_ADTYPE_FLAGS,
      GAP_ADTYPE_FLAGS_BREDR_NOT_SUPPORTED | GAP_ADTYPE_FLAGS_GENERAL,
    
    };

    Thanks,