Hello,
We would like to ask about an issue related to NBU Core initialization while debugging a KW47 application using IAR.
Screenshots of the IAR debugger configuration are attached for reference.
After performing "Download and Debug" in IAR, if we press Go without first executing a Hardware Reset, an ASSERT occurs during BLE initialization.
We traced the issue to the following call sequence:
However, if we perform the following sequence:
the application starts normally and no ASSERT occurs.
Based on the observed behavior, we suspect the following sequence may be occurring:
Thank you for your support.
Best regards,
hyama
Hi, @hyama
Thanks for creating case to us.
Before answer your questions, can you please help to check whether the NBU version is matched with your SDK version?
If you are not sure, please help to update the NBU which located in your SDK directory:mcuxsdk\middleware\wireless\ble_controller\bin\kw47_nbu_ble_hosted.bin
About how to flash nbu, you can refer to below:
(1) Methods to update NBU firmware on KW47 and MCX W72 - NXP Community
After upgrade the NBU to the same version with SDK, then have a try.
BR,
Christine.
Hi @Christine_Li ,
Thank you for your reply.
We have already programmed the NBU firmware included with SDK version 26.03.00.
However, we have not yet verified whether the NBU firmware was written correctly or whether the currently running NBU firmware version actually matches the SDK version.
Is there a way to check the version of the NBU firmware currently programmed on the device?
If there is a recommended method to verify the NBU firmware version, please let us know.
Best regards,
hyama
Hi, @hyama
Usually we think the NBU update successfully if you follow the link I provided to you and it returns successful. To double confirm, we provide this API: int PLATFORM_GetNbuInfo(NbuInfo_t *nbu_info_p); to get the NBU info.
To move forward your initial issue, I still wants to know below info:
1.Do you have our KW47-EVK or KW47-LOC board, if you have, can you please have a try with our EVK or LOC board to see whether have same issue on our boards?
2. Did you use our default example in SDK release? Or you have modifies anything based on our example code?
3. If do not use HW reset, but with software reset in IAR, still can reproduce this issue or not?
BR,
Christine.
Hi @Christine_Li
Apologies for the delay. I haven't had a chance to try it yet, and I'm planning to work on it starting next week.
BR,
hyama.
Hi, @hyama
How is it now on your side?
Did you get any chance to try with my recommendations?
BR,
Christine.
Hi, @Christine_Li
Thank you for your support.
I investigated the requested items and obtained the following results.
I tested the same software on a KW47-LOC board.
The issue is reproducible on the KW47-LOC as well.
HAL_RpmsgMcmgrInit() returns kStatus_HAL_RpmsgTimeout, and then the application reaches assert(false).
The current project is not using an SDK example in its original form.
The software has been customized over time, and at this time I am unable to determine which SDK example, if any, was originally used as the project baseline.
Therefore, I cannot identify a specific SDK example that this project is based on.
I also tested using Software Reset instead of Hardware Reset in IAR.
The same behavior occurs with Software Reset.
HAL_RpmsgMcmgrInit() returns kStatus_HAL_RpmsgTimeout, and then the application reaches assert(false).
I checked the NBU version using the API below:
int PLATFORM_GetNbuInfo(NbuInfo_t *nbu_info_p);
The returned values are:
Based on these values, the reported NBU version appears to be 1.9.20.
Could you please confirm whether NBU version 1.9.20 is the expected and compatible version for SDK 26.03.00?
Please let me know if you need any additional information or logs.
BR,
hyama.