We use cookies and similar technologies (also from third parties) to collect your device and browser information for a better understanding on how you use our online offerings. This enables us to optimize and personalize your experience with Infineon and to provide you with additional services and information based on your individual profile. Details are available in our privacy policy.
Privacy Policyand Imprint
View and change cookie settings
Accept
Reject
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Help

Tip / Sign in to post questions, reply, level up, and achieve exciting badges. Know more

PSoC™ 4

PaDo_1228851
Level 3
25 replies posted 10 replies posted 10 questions asked
Level 3
‎Nov 10, 2016 04:45 PM

peripheral.name vs. localName?

Jump to solution

My app uses both the peripheral.name AND the advertisementData[CBAdvertisementDataLocalNameKey].  But every time I update advertisementData[CBAdvertisementDataLocalNameKey] by means of the CyBle_GapSetLocalName(), the peripheral.name value takes on the old value of advertisementData[CBAdvertisementDataLocalNameKey].  Is there anyway to stabilize the peripheral.name value so that it never changes from the initial value given when the 4200BLE is initially programmed?

   

Thanks.

Labels
0 Likes
1 Solution
AnjanaM_61
Moderator
Moderator First comment on KBA 5 questions asked First question asked
Moderator
‎Nov 24, 2016 02:46 AM

Re: peripheral.name vs. localName?

Jump to solution

Hi ,

   

Do you mean you want to save the device name into flash , so that the last name should be stored even after power cycle?

   

If then, you can write the value into flash or sflash by the follwing APIs  CySysFlashWriteRow() , CySysSFlashWriteUserRow()

   

Please refer the system reference guide for API defenition.

   

Thanks,

   

Anjana

View solution in original post

0 Likes
3 Replies