Some ref material -
http://www.cypress.com/?rID=102512 AN91445 - Antenna Design Guide
http://www.cypress.com/?rID=102505 AN94020 - Getting Started with PRoC™ BLE
http://www.cypress.com/?rID=110007 AN92584 - Designing for Low Power and Estimating Battery Life for BLE Applications
http://www.cypress.com/?rID=109900 AN91162 - Creating a BLE Custom Profile
http://www.cypress.com/?rID=110107 AN91184 - PSoC 4 BLE - Designing BLE Applications
http://www.cypress.com/?rID=102504 AN91267 - Getting Started with PSoC® 4 BLE
PSoC 4BLE/PRoC BLE only supports BLE and is not compatible with Bluetooth BR/EDR. So it is not possible to change these values.
Hi BMAH, thanks for reply. However if the kit cannot support Bluetooth BR/EDR, in 100 Project in 100 days, for Project #009: Dynamic Broadcaster - Changing Advertising Packets and Project #008: GAP Broadcaster, How you could approach the function of advertising packets to nearby iBeacons? In my view the flag of ibeacon packet should be 0x1a?
In those projects we haven't updated the specific fields in the flags that you mentioned in the first post.
We can update the field only related to discovery mode(even in firmware).
Only in Dynamix broadcaster we are updating the advertising data(manufacturer specific data).
Ibceacon spec hasn't mentioned requirement of 0x1A for the fields.We have to select the fields of the flags as per the capability fo the chip. 0x1A field is the "length of the manufacturer specific data+type of data field (0xFF)".Refer the link http://www.warski.org/blog/2014/01/how-ibeacons-work/ which gives more details about the advertising data for ibeacon.