If you are a registered user, all your settings are stored in the board database. To alter them, visit your User Control Panel; a link can usually be found by clicking on your username at the top of board pages. This system will allow you to change all your settings and preferences.

Only registered users can send email to other users via the built-in email form, and only if the administrator has enabled this feature. This is to prevent malicious use of the email system by anonymous users.

Either the administrator has not installed your language or nobody has translated this board into your language. Try asking a board administrator if they can install the language pack you need. If the language pack does not exist, feel free to create a new translation. 

It is possible the time displayed is from a timezone different from the one you are in. If this is the case, visit your User Control Panel and change your timezone to match your particular area, e.g. London, Paris, New York, Sydney, etc. Please note that changing the timezone, like most settings, can only be done by registered users. If you are not registered, this is a good time to do so.

Within your User Control Panel, under “Board preferences”, you will find the option Hide your online status. Enable this option and you will only appear to the administrators, moderators and yourself. You will be counted as a hidden user.

You may not have to, it is up to the administrator of the board as to whether you need to register in order to post messages. However; registration will give you access to additional features not available to guest users such as definable avatar images, private messaging, emailing of fellow users, usergroup subscription, etc. It only takes a few moments to register so it is recommended you do so.

“Delete cookies” deletes the cookies created by phpBB which keep you authenticated and logged into the board. Cookies also provide functions such as read tracking if they have been enabled by a board administrator. If you are having login or logout problems, deleting board cookies may help.

If you do not check the Remember me box when you login, the board will only keep you logged in for a preset time. This prevents misuse of your account by anyone else. To stay logged in, check the Remember me box during login. This is not recommended if you access the board from a shared computer, e.g. library, internet cafe, university computer lab, etc. If you do not see this checkbox, it means a board administrator has disabled this feature.

Don’t panic! While your password cannot be retrieved, it can easily be reset. Visit the login page and click I forgot my password. Follow the instructions and you should be able to log in again shortly.
However, if you are not able to reset your password, contact a board administrator.

It is possible an administrator has deactivated or deleted your account for some reason. Also, many boards periodically remove users who have not posted for a long time to reduce the size of the database. If this has happened, try registering again and being more involved in discussions.

There are several reasons why this could occur. First, ensure your username and password are correct. If they are, contact a board administrator to make sure you haven’t been banned. It is also possible the website owner has a configuration error on their end, and they would need to fix it.

First, check your username and password. If they are correct, then one of two things may have happened. If COPPA support is enabled and you specified being under 13 years old during registration, you will have to follow the instructions you received. Some boards will also require new registrations to be activated, either by yourself or by an administrator before you can logon; this information was present during registration. If you were sent an email, follow the instructions. If you did not receive an email, you may have provided an incorrect email address or the email may have been picked up by a spam filer. If you are sure the email address you provided is correct, try contacting an administrator.

It is possible a board administrator has disabled registration to prevent new visitors from signing up. A board administrator could have also banned your IP address or disallowed the username you are attempting to register. Contact a board administrator for assistance.

COPPA, or the Children’s Online Privacy Protection Act of 1998, is a law in the United States requiring websites which can potentially collect information from minors under the age of 13 to have written parental consent or some other method of legal guardian acknowledgment, allowing the collection of personally identifiable information from a minor under the age of 13. If you are unsure if this applies to you as someone trying to register or to the website you are trying to register on, contact legal counsel for assistance. Please note that phpBB Limited and the owners of this board cannot provide legal advice and is not a point of contact for legal concerns of any kind, except as outlined in question “Who do I contact about abusive and/or legal matters related to this board?”.

bls_ota_set_fwSize_and_fwBootAddr 同时支持两个功能: 修改最大 firmware size 和启动地址。这个启动地址指的是 OTA 设计中除了 0 地址外另一个存储 New_firmware 的地址（只能是 0x20000、 0x40000 或0x80000）。SDK 中默认的最大 firmware size 为 124K（ 由于一些特殊的原因， 启动地址为 0x20000 的 firmware size 不得大于 124K），对应的启动地址为 0x00000 和 0x20000。这两个值和前文的描述一致。

void bls_ota_set_fwSize_and_fwBootAddr(int firmware_size_k, int boot_addr);

firmware_size_k 的设置一定要 4K byte 对齐，比如 size 为 97K 时需要设为 100K。这个 API 只能在 main 函数中 cpu_wakeup_init 之前调用，否则无效。原因是 cpu_sleep_wakeup 函数中需要根据 firmware_size_k 和 boot_addr 的值做一些设置。

如果最大 firmware_size 发生变化，超过了 124K，此时需要将启动地址挪到 0x40000（ size 最大不得超过252K） ， 同理如果 firmware_size 超过 252K， 需要将启动地址挪到 0x80000（ size 最大不得超过 508K）， 比如最大 firmware size 可能到 200K，设置如下： bls_ota_set_fwSize_and_fwBootAddr(200, 0x40000);

drivers/9518/pm.h 文件中的 DEEP_ANA_REG，如下 code 所示：
#define DEEP_ANA_REG0 0x39 //initial value =0x00
#define DEEP_ANA_REG1 0x3a //initial value =0x00
#define DEEP_ANA_REG2 0x3b //initial value =0x00
#define DEEP_ANA_REG3 0x3c //initial value =0x00
#define DEEP_ANA_REG4 0x3d //initial value =0x00
#define DEEP_ANA_REG5 0x3e //initial value =0x00

#define DEEP_ANA_REG6 0x3f //initial value =0x0f
以上寄存器只有在掉电时才会恢复初始值，需要注意的是，客户不允许使用ana_39，该模拟寄存器的留给底层
stack使用，如果应用层代码有用到该寄存器，需要修改为ana_3a~ana_3f。因为不掉电模拟寄存器数量比较
少，建议客户使用其每一个bit指示不同的状态位信息。

#define DEEP_ANA_REG7 0x38 //initial value =0xff

以上 0x38 寄存器， 在硬件/软件 reset、 掉电和 watchdog 三种情况下会被初始化， 需要注意的是 bit0 位已经被
stack 使用，使用者在使用时需要避免该 bit 位。
使用者可以在 sys_init(power_mode_e power_mode)后使用 API pm_get_mcu_status(void)的返回值来判断 cpu 是
从哪种状态返回，返回值如下：
enum {
    MCU_STATUS_POWER_ON = BIT(0),
    MCU_STATUS_REBOOT_BACK = BIT(2),
    MCU_STATUS_DEEPRET_BACK = BIT(3),
    MCU_STATUS_DEEP_BACK = BIT(4),
};

CSRK -- Connection Signature Resolving Key，只用在非加密的连接中。

CSRK的初衷是考虑到早期芯片计算能力不足，连接建立后 发送一个 签名的ATT PDU 实现对设备的认证。 但是CSRK只是认证设备，后续数据的交互传输都是明文。现在BLE加密已经实现CSRK的功能，且整个数据的传输都是加密的。对于今天的芯片计算能力，已不再需要CSRK。

编译错误log:                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            原因是825x ble sdk工程默认配置retention 段最大为16k，而当前工程实际使用的retention 段超过了16k

解决方法（三步）：
1、cstartup选择32k retention的，配置方法如下图。                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            2、boot也选择相应的32k retention link，将其copy到boot.link中。

3、在user init中将系统默认retention模式由16k改为32k.

       blc_pm_setDeepsleepRetentionType(DEEPSLEEP_MODE_RET_SRAM_LOW32K);

Note:后续更新sdk版本时，针对这个工程会将默认配置为32k retention。

bls_ota_set_fwSize_and_fwBootAddr 同时支持两个功能: 修改最大 firmware size 和启动地址。这个启动地址指的是 OTA 设计中除了 0 地址外另一个存储 New_firmware 的地址（只能是 0x20000、 0x40000 或0x80000）。SDK 中默认的最大 firmware size 为 124K（ 由于一些特殊的原因， 启动地址为 0x20000 的 firmware size 不得大于 124K），对应的启动地址为 0x00000 和 0x20000。这两个值和前文的描述一致。

void bls_ota_set_fwSize_and_fwBootAddr(int firmware_size_k, int boot_addr);

firmware_size_k 的设置一定要 4K byte 对齐，比如 size 为 97K 时需要设为 100K。这个 API 只能在 main 函数中 cpu_wakeup_init 之前调用，否则无效。原因是 cpu_sleep_wakeup 函数中需要根据 firmware_size_k 和 boot_addr 的值做一些设置。

如果最大 firmware_size 发生变化，超过了 124K，此时需要将启动地址挪到 0x40000（ size 最大不得超过252K） ， 同理如果 firmware_size 超过 252K， 需要将启动地址挪到 0x80000（ size 最大不得超过 508K）， 比如最大 firmware size 可能到 200K，设置如下： bls_ota_set_fwSize_and_fwBootAddr(200, 0x40000);

drivers/9518/pm.h 文件中的 DEEP_ANA_REG，如下 code 所示：
#define DEEP_ANA_REG0 0x39 //initial value =0x00
#define DEEP_ANA_REG1 0x3a //initial value =0x00
#define DEEP_ANA_REG2 0x3b //initial value =0x00
#define DEEP_ANA_REG3 0x3c //initial value =0x00
#define DEEP_ANA_REG4 0x3d //initial value =0x00
#define DEEP_ANA_REG5 0x3e //initial value =0x00

#define DEEP_ANA_REG6 0x3f //initial value =0x0f
以上寄存器只有在掉电时才会恢复初始值，需要注意的是，客户不允许使用ana_39，该模拟寄存器的留给底层
stack使用，如果应用层代码有用到该寄存器，需要修改为ana_3a~ana_3f。因为不掉电模拟寄存器数量比较
少，建议客户使用其每一个bit指示不同的状态位信息。

#define DEEP_ANA_REG7 0x38 //initial value =0xff

以上 0x38 寄存器， 在硬件/软件 reset、 掉电和 watchdog 三种情况下会被初始化， 需要注意的是 bit0 位已经被
stack 使用，使用者在使用时需要避免该 bit 位。
使用者可以在 sys_init(power_mode_e power_mode)后使用 API pm_get_mcu_status(void)的返回值来判断 cpu 是
从哪种状态返回，返回值如下：
enum {
    MCU_STATUS_POWER_ON = BIT(0),
    MCU_STATUS_REBOOT_BACK = BIT(2),
    MCU_STATUS_DEEPRET_BACK = BIT(3),
    MCU_STATUS_DEEP_BACK = BIT(4),
};

CSRK -- Connection Signature Resolving Key，只用在非加密的连接中。

CSRK的初衷是考虑到早期芯片计算能力不足，连接建立后 发送一个 签名的ATT PDU 实现对设备的认证。 但是CSRK只是认证设备，后续数据的交互传输都是明文。现在BLE加密已经实现CSRK的功能，且整个数据的传输都是加密的。对于今天的芯片计算能力，已不再需要CSRK。

用户从wiki上下载最新的SDK，里面包含有对应的SDK文件夹和对应的所有的patch文件，patch文件下有相应的patch_list.txt文件，阅读其相关的补丁细节，然后将相关的补丁文件替换。

补丁文件一般为以下三种文件的组合

• .a 库文件
• .c文件
• .h文件

1. 如果patch文件包有三个，，patch1， patch2， patch3， 一般patch3包含了patch1， patch2以及patch3新增加的修补。
2. 如果patch1或者patch2中含有.c或者.h 文件，如果想要用patch3，除了需要打上patch3的所有文件，还需要将patch1和patch2的所有.c 和.h文件copy过来。