Assert Error While Running BLE Example on FRDM-MCXW71 EVK

[Ramdev]

Hello Team,

I am currently working with the FRDM-MCXW71 EVK for a BLE application using Visual Studio Code.

The mcxw71evk_cmsis_button_toggle_led example builds, flashes, and runs successfully.

However, when I build and flash the mcxw71evk_adv_ext_peripheral_freertos example, the build and debug process completes successfully, but when I run the application, an assert error occurs.

Could you please help me understand what might be causing this issue? Please let me know if any additional configuration is required for the BLE example.

Thank you for your support.

Best regards,
Ramdev  #MCXW71 #BLE

[Christine_Li]

Hi, @Ramdev 

Thanks for creating case to us.

Can you please let me know your SDK version and detailed reproducing steps for this issue?

If possible, please also help to provide the screenshot and logs related.

I prefer to check on my local side to see whether can reproduce this issue.

Best regards,

Christine.

[Ramdev]

Hello Christine,

Thank you for your response.

I am using MCUXpresso SDK version 25.12.0.The project builds successfully and the debug session starts without any issues. However, once debugging completes and I click the Run option, the application immediately enters an assert error.

I have attached the terminal logs for your reference.

Could you please review the logs and advise on the possible cause of this issue?

Thank you for your support.

Best regards,
Ramdev

[Ramdev]

Hello NXP Team,
. Could you please provide an update at your convenience?
Please let me know if any additional information is required from my side.

Regards,
Ramdev

[Ramdev]

Hi NXP Team,
I would like to kindly follow up on my previous query. Could you please provide an update at your convenience?
Please let me know if any additional information is required from my side.

Regards,
Ramdev

[Christine_Li]

Hi, @Ramdev 

Sorry, I was blocked by another higher priority task.

I will try to check this issue today, and share my updates in time.

Best regards,

Christine.

[Christine_Li]

Hi， @Ramdev 

Thanks for your patience.

I tried on my local side, and not meet your errors.

I can build and debug and run it successfully.

Please see below for my test results outputs:

---- Opened the serial port COM4 ----

CMSIS GPIO Example!

Use Button to toggle LED!

CMSIS GPIO Example!

Use Button to toggle LED!

CMSIS GPIO Example!

Use Button to toggle LED!

CMSIS GPIO Example!

Use Button to toggle LED!

CMSIS GPIO Example!

Use Button to toggle LED!

BUTTON Pressed!

BUTTON Pressed!

BUTTON Pressed!

BUTTON Pressed!

BUTTON Pressed!

BUTTON Pressed!

BUTTON Pressed!

BUTTON Pressed!

Did you modify anywhere? 

I am using SDK25.12.00, and use this toolchain to build:

.mcuxpressotools/arm-gnu-toolchain-14.2.rel1-mingw-w64-x86_64-arm-none-eabi/bin/arm-none-eabi-objdump.exe

Please check the toolchain on your side.

And if you modified anywhere, please let me know.

Below attachment is my console logs, seems similar as yours.

But in your console logs, I saw ：

[21923]INFO:launcher.core.stub: [stub (2336)] Nc: state - running or following reset request - re-read of state failed - rc Nn(05). Wire ACK Fault in DAP access

Can you please have a try with other examples? like hello_world?

Best regards,

Christine.

[Ramdev]

Hi Christiane, CMSIS GPIO example working on my side too, The problem the ble examples like "mcxw71evk_adv_ext_peripheral_freertos" when i run this example assert error is coming,could you verify this??

[Christine_Li]

Hi， @Ramdev 

Do you modify anything? Or just use our default example?

Sure, I can try on my side for this example:adv_ext_peripheral_freertos  too.

Later will share my results to you.

Best regards,

Christine.

[Ramdev]

Hi Christine,
In launch.jason i have updated .elf file, other that that i have not changed anything.
same thing I did for led example too ,It was working fine.

Regards,
Ramdev

[Christine_Li]

Hi, @Ramdev 

Thanks for your reply.

I tried with this BLE example:frdmmcxw71_adv_ext_peripheral_freertos, and also meet same issue like yours.

Below is the error:

[11834]DEBUG:launcher.core.stub: stub (13333) -> GDB (2340): b'+'
[35169]INFO:launcher.core.stub: [stub (2340)] Nc: state - running or following reset request - re-read of state failed - rc Nn(05). Wire ACK Fault in DAP access
[35214]INFO:launcher.core.stub: [stub (2340)] Nc: state - running or following reset request - re-read of state failed - rc Nn(05). Wire ACK Fault in DAP access
[35259]INFO:launcher.core.stub: [stub (2340)] Nc: state - running or following reset request - re-read of state failed - rc Nn(05). Wire ACK Fault in DAP access
[35286]INFO:launcher.core.stub: [stub (2340)] Nc: state - running or following reset request - re-read of state failed - rc Nn(05). Wire ACK Fault in DAP access
[35333]INFO:launcher.core.stub: [stub (2340)] Nc: state - running or following reset request - re-read of state failed - rc Nn(05). Wire ACK Fault in DAP access
[35368]INFO:launcher.core.stub: [stub (2340)] Nc: state - running or following reset request - re-read of state failed - rc Nn(05). Wire ACK Fault in DAP access
[35401]INFO:launcher.core.stub: [stub (2340)] Nc: state - running or following reset request - re-read of state failed - rc Nn(05). Wire ACK Fault in DAP access
[35435]INFO:launcher.core.stub: [stub (2340)] Nc: state - running or following reset request - re-read of state failed - rc Nn(05). Wire ACK Fault in DAP access
[35520]INFO:launcher.core.stub: [stub (2340)] Nc: state - running or following reset request - re-read of state failed - rc Nn(05). Wire ACK Fault in DAP access

Let me check and feedback to you soon.

Best regards,

Christine.

[Ramdev]

Hi Christine,
Thank you for the update. I look forward to your response.

Regards,
Ramdev

[Christine_Li]

Hi， @Ramdev 

Please have a try with below:

1. modify frdm_mcxw71\mcuxsdk\middleware\wireless\bluetooth\boards\frdmmcxw71\bluetooth\adv_ext_peripheral\app_preinclude.h

#define gAppLowpowerEnabled_d           1 //From 0 to 1

2. Use blhost to Load the NBU FW located in the below directory:

mcuxsdk\middleware\wireless\ble_controller\bin\mcxw71_nbu_ble_hosted.sb3

If you don't know how to use blhost to flash NBU FW bin, please refer to below link:

https://community.nxp.com/t5/MCX-W71-Training-Secure-MCUs-for/FRDM-MXCW71-Hands-On-2-Recognize-NBU-I...

I already verified on my local side, it can work well now：

Extended Advertising Application - Peripheral
Press WAKESW to see the menu
Extended Advertising Application - Peripheral
Press WAKESW to see the menu
Extended Advertising Application - Peripheral
Press WAKESW to see the menu
Extended Advertising Application - Peripheral
Press WAKESW to see the menu
Extended Advertising Application - Peripheral
2 ss WAKESW to see the menu
Extended Scanable Advertising Started on handle 0

Please let me know your results and if it works for you, please help to mark my answer as a solution for this issue. So that we can close the case.

Thanks!

Best regards,

Christine.

[Christine_Li]

Hi， @Ramdev 

Does it work for you?

If it works on your side, would you please help to mark my answer as a solution for this case?

So that we can close it in time.

If you have any other topic questions, please feel free to create new case to us.

Best regards,

Christine.

[Ramdev]

Hi Christine,Sorry for the late response. I was stuck with another issue where the debug session is not starting.In MCUXpresso for VS Code, the following error appears:failed to launch: Remote connection closed
(from target select extended remote 172.0.0.1:2356)I also tried programming the board using LinkFlash (v25.12.83), but it shows the following error:Could not connect to core
Et:31: No connection to chip's debug port
Pc: (100) Target Operation Failed

On the hardware side, the USB_ACT green LED is ON, the ISP_EN_MLINK red LED is blinking, and the USB LED is also ON.

Earlier the board was working fine, but now I am unable to debug or flash any example on the FRDM-MCXW71 board.

Because of this issue, I was not able to check the assert error solution that you mentioned earlier.Could you please suggest how to resolve this issue?

Regards,
Ramdev

[Christine_Li]

Hi， @Ramdev 

For the new issue, can you please help to create a new thread?

To avoid confusion, we usually recommend customer to track one issue with one case.

I will take it and check for you next Monday, now I am in progress with another issue.

Thanks for your corporations.

Best regards,

Christine.

[Ramdev]

Hi Christine,

Thank you for the update. I have created a support link for this issue
link :https://community.nxp.com/t5/Wireless-MCU/FRDM-MCXW71-debug-issue/m-p/2327185#M20304
When you have time from Monday, could you please take a look at it?

Regards,
Ramdev

[Christine_Li]

Hi, @Ramdev 

Thanks for creating the new thread.

I saw our colleague has already been supporting you on the new thread.

Once the new issue is resolved, please continue to test this issue and let me know whether still need help from us.

Best regards,

Christine.

[Ramdev]

Hi Christine ,
Thank you for the update.
No problem, I understand.

Regards,
Ramdev