Hi,
在documentat UM-B-016, I can read that if "DEVELOPMENT__NO_OTP" is defined, I am in "Development mode, OTP memory not used". If undefined, I am in production mode.
In my current application, I use an external EEPROM to keep flexibility. Do I need to keep "DEVELOPMENT__NO_OTP" defined?
Thanks for your help.
Kind regards,
Matt
Hi Matthieu,
When you are developing your application it is advisable to keep 'DEVELOPMENT__NO_OTP' defined.
It depends if your end product uses EEPROM only or if some parameters (XTAL16 trimming or BD address) will be programmed in OTP header. In the case of EEPROM only you need to take care that some parameters need to be added to the EEPROM (XTAL16 trimming, BD address and some factory parameters like IQ trimming value).
Bluetooth Support Team
Thanks for the answer.
For now, I am building a prototype so I will only work with EEPROM. Do you have any document explaining how I should proceed to store the parameters you mentionned in the EEPROM?
Thanks.
Matt
Hi Matt,
We do not have a document yet. We are planning to either make an application note or add it to the FAQ.
Bluetooth Support Team