• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 51 subscribers
  • Views 303 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.

CC2340R5: Making Device Name configurable for production ready device

Harinder Singh
Intellectual 400 points
Other Parts Discussed in Thread: CC2340R5, SYSCONFIG

Dear Team,

Greeting of the day!

We are working on CC2340R5 platform and want to make the device name configurable from the user end after production, like initially device will have some default name but once the device is deployed in the field the user can change it.

Our idea of implementation is that we will store the Device Name configuration related data on the internal NVS of the CC2340R5 and user can configure it through some custom characteristics if required.

But the issue we are facing is the device name can only be modified using syscfg of the project, is their any way that we can control the device name through some variable and each time when device boots up it reads the configuration stored in the NVS into this variable and apply this variable to the BLE stack so that the same device name reflects back to the central devices once the stack is up. It will also help us to operate multiple devices into the same operational space.

Screenshot of syscfg of the project:

So how we can eliminate the dependency of Device Name from syscfg and make it user configurable, please let me know if you need more information from my end.

Thanks & Regards,

Harinder Singh 

  • 0
    TI__Mastermind 42250 points

    Hi Harinder,

    The device name string is stored in the attDeviceName variable which can be found in the ti_ble_config.c and ti_ble_config.h. The name that is advertised over the air is set in the  scanResData1 variable which can be modified during runtime.

    If desired, SysConfig generation may be disabled after it has run at least once to generate the files.

    Best Regards,

    Jan