Hi Team,
I am facing an issue with BLE on a custom board based on the NXP RW610.
Issue Description
I initially created a project using the NXP RW612 base SDK/project.
After that:
- Added the BLE stack and BLE-related components.
- Modified the project configuration to target RW610 instead of RW612.
- Successfully compiled the project without errors.
- The application boots correctly until BLE initialization.
However, once BLE is enabled/initialized, the MCU crashes/hangs.
Additional Information
- LEDs and other basic peripherals are functioning properly.
- The crash happens specifically after enabling BLE.
- This issue occurs on a custom RW610 board.
Request
I would like to know:
- Whether there are additional BLE-specific changes required when migrating from RW612 to RW610.
- Any differences in memory configuration, clock settings, linker settings, firmware blobs, or BLE controller initialization between RW612 and RW610.
- Whether anyone has faced a similar issue during SDK migration.
Any suggestions or debugging pointers would be helpful.
Thanks.
Hi,
SDK 2.16.100 is quite old. I would recommend updating to a newer version (e.g. 26.03), as it includes multiple fixes and improvements.
Regarding RW612 → RW610 migration, in general the application should be portable since both devices belong to the RW61x family, as long as it only relies on common BLE/Wi‑Fi features. However, this also assumes that the configuration of pins, clocks, memory, and peripherals has been properly adapted to your custom RW610 board.
Please also take a look at the “Migration from FRDM-RW612 to third-party module memories” article, as it highlights important differences at the board and memory configuration level.
Regards,
Daniel
Hi Daniel,
Thank you for the response.
Below are the details:
- NXP RW612 SDK
- SDK Version: 2.16.100
- Manifest Version: 3.14.0
- NXP RW610 SDK
- SDK Version: 2.16.100
- Manifest Version: 3.14.0
Base Example
I am using the edgefast_bluetooth_examples project as the base example.
Workflow Followed
- Initially created the project using the RW612 SDK and BLE example. worked fine in EVK.
- Later migrated/changed the project configuration to RW610 for my custom board, because no example available for R610.
- The project compiles successfully without errors.
- The crash occurs after BLE initialization/enable.
Could you please let me know if there are any additional changes required specifically for RW610 when migrating from RW612, especially for:
- BLE controller configuration
- Memory/linker settings
- Clock configuration
- Firmware or radio initialization
Regards,
Chellapandi
Hi,
What SDK version are you using?
What SDK example are you using as a base?
We strongly recommend you to use one of the BLE examples as a base to develop your application.
Regards,
Daniel.
Hi Daniel,
As suggested, I updated my development environment and SDK versions as follows:
RW610 SDK Version: 25.12
MCUXpresso IDE Version: 25.6
After updating, I tried running a simple BLE SDK example. However, I encountered the error shown in the attached screenshot.
For additional context, this project was originally created from an RW612 BLE SDK example. During the migration to RW610, I made the following changes:
Changed the MCU settings from RW612 to RW610.
Updated the preprocessor definitions from RW612 to RW610.
Rebuilt the project using the RW610 SDK.
Thank you for your support.
Regards,
Chellapandi
Hi,
I have a custom RW610 board that shows "Failed on connect: Ee(42). Could not connect to core.No connection to chip's debug port" in MCUXpresso IDE. I compared SWD voltages at idle between a working and non-working board:
| Signal | Working | Non-Working |
|---------|-------|-------------|
| SWDIO | 3.3V 1.4V |
| SWDCLK | 0V | 2.0V |
| RST | 3.3V | 2.8V |
Current pull resistors on the non-working board:
- SWDIO → 51K pull-up to 3.3V
- RST → 51K pull-up to 3.3V
- SWDCLK → nothing (floating)
We believe the floating SWDCLK is causing the 2.0V mid-rail and blocking SWD enumeration. Planning to add a 51K pull-down on SWDCLK to GND.
Questions:
1. Is a floating SWDCLK enough to cause complete SWD failure on RW610?
2. Does RW610 have internal pull resistors on SWD pins, or must they always be external?
3. Is 51K pull-down on SWDCLK acceptable, or is 10K better for signal integrity?
4. Can a Flexcomm peripheral accidentally mapped to SWD pins cause this, even before debugger connects?
5. If SWD stays inaccessible, what is the recommended RW610 recovery method via ISP/UART?
Thanks!