How to you confirm this issue?

Could you test on default soc-empty just set DEBUG_LEVEL to 1 for confirm?

Please also test on my attached hex file and feedback, below is my test log.

Hi Vincent,

Not familiar with the certification RF test. 

We usually use soc-dtm or ncp tagert example on Simplicity Studio for the RF test.

Please check if this link can help?

Best Regards,

Eric Su

Hi Vincent,

Not familiar with the certification RF test. 

We usually use soc-dtm or ncp tagert example on Simplicity Studio for the RF test.

Please check if this link can help?

Best Regards,

Eric Su

For PS Store API, it can access 0x40000-0x4FFFF, user data can be save in PS Store if the BLE stack is not occupied all the PS Store area.

For NVM3 API, it can access all the NVM valid area.

Just found I can not find a BRD4183A  on my hand, check on BRD4184A.

SWO can work when the application is not install yet, have you check the GPIO? Missed this step to guide you.

I found your projects can boot and OTA well.

If we use WSTK + radio board, we usually use the bootloader as default, we don't need the step for check on a spi device, but don't think this will cause the OTA fail. Have test on check and uncheck the MX25R8035F.

Here is my advice for this issue.

Cloud you check on BRD4184A?

How about use application level OTA for check, it have OTA log. So we can check the OTA progress.

I think we can check the OTA on BLE application first, may sure it works then porting on BT Mesh application.

Just found I can not find a BRD4183A  on my hand, check on BRD4184A.

SWO can work when the application is not install yet, have you check the GPIO? Missed this step to guide you.

I found your projects can boot and OTA well.

If we use WSTK + radio board, we usually use the bootloader as default, we don't need the step for check on a spi device, but don't think this will cause the OTA fail. Have test on check and uncheck the MX25R8035F.

Here is my advice for this issue.

Cloud you check on BRD4184A?

How about use application level OTA for check, it have OTA log. So we can check the OTA progress.

Just found I can not find a BRD4183A  on my hand, check on BRD4184A.

SWO can work when the application is not install yet, have you check the GPIO? Missed this step to guide you.

I found your projects can boot and OTA well.

If we use WSTK + radio board, we usually use the bootloader as default, we don't need the step for check on a spi device, but don't think this will cause the OTA fail. Have test on check and uncheck the MX25R8035F.

Here is my advice for this issue.

Cloud you check on BRD4184A?

How about use application level OTA for check, it have OTA log. So we can check the OTA progress.

Checked your project files, they work well on the BRD4184A, I don't have a BRD4183A for check now.

Could you use tera term for check the log?

Could you enable the log for debug bootloader?