Support for UBLOX MAYA W476 Module on MIMXRT1176

[Tarak_777]

Hi all,

I am working on a custom board based on the MIMXRT1176  and would like to integrate the UBLOX MAYA W476 module, which is part of the IW610 chipset family. I reviewed the recent MCUXpresso SDK 25.09 release notes but did not find this module explicitly listed.

Could you please confirm if support for this module is available? If so, I would appreciate your guidance on the integration process.

Best regards,
Tarak.

[lucindaschatz]

wow best work

[DanielRuvalcaba]

Hi,

Please try using the RT1170-EVKB SDK and enabling one of these macros:

WIFI_IW610_BOARD_MURATA_2LL_USD

WIFI_IW610_BOARD_MURATA_2LL_M2

The macro should be defined in the preprocessor. By default, IW612 is enabled.

Regards,

Daniel.

[Tarak_777]

Hi @DanielRuvalcaba 

Thanks for the reply. 

Actually I have tried using SDK 25.09 example code Wireless Uart.

The SDIO initialization is working successfully, and I am attempting to download the firmware to the MAYA W476 module. However, I am encountering an issue in the function static fwdnld_intf_ret_t sdio_interface_send() within fwdnld_sdio.c. During execution, the length value is 16 for 2–3 iterations, after which an error occurs. I have attached an image for reference showing the exact point where it stops.

Please guide me regarding this issue. 

Best regards, 

Tarak. 

[DanielRuvalcaba]

Hi,

Does this also happen when you try a Wi-Fi only example i.e. wifi_cli?

In UM11441, only the combination of IW610 and RT1060-EVKC is mentioned, which might be why you're encountering that error.

Regards,

Daniel.

[Tarak_777]

Hi @DanielRuvalcaba ,

I have tested using the Wi-Fi client example code and encountered the same issue. While command transfers are responding correctly — confirmed using the following function, which returns a length of 16 or 17:

t_u16 wlan_card_read_f1_base_regs(void)
{
t_u16 reg;
uint32_t resp = 0;

(void)sdio_drv_creg_read(READ_BASE_0_REG, 1, &resp);
reg = (t_u16)(resp & 0xFFU);
(void)sdio_drv_creg_read(READ_BASE_1_REG, 1, &resp);
reg |= (t_u16)((resp & 0xFFU) << 8);

return reg;
}

However, when attempting to send firmware data, the transfer fails within the SDMMCHOST_TransferFunction. The function detects a data transfer failure by using flags in else condition and sets error = kStatus_Fail.

I have attached an image of the function for your reference. Could you please provide guidance on how to resolve this data transfer issue?

Thanks & regards,
Tarak.

[DanielRuvalcaba]

Hi,

By the way, what macro did you use?

Regards,

Daniel.

[Tarak_777]

Hi @DanielRuvalcaba ,

I am using the MACRO WIFI_IW610_BOARD_MURATA_2LL_USD.

Best regards,

Tarak.

[DanielRuvalcaba]

Hi,

By any chance, have you tested it with RT1170-EVKB and a Murata 2LL module?

Regards,

Daniel.

[Tarak_777]

Hi @DanielRuvalcaba ,

I have an update regarding my progress,

I have modified the sdio_interface_send() function by introducing small delays and using continue to retry reading the card status registers in case of failure. With these changes, the firmware transfer completes successfully, confirmed by transfer_len = 0 before the function exits.

However, after the firmware download, when polling the firmware ready registers (CARD_FW_STATUS0_REG / CARD_FW_STATUS1_REG), the response value remains 1, indicating the firmware is not reporting as ready. Actual Value we are comparing with is FIRMWARE_READY 0xfedcU

I would like to confirm if my approach for sending the firmware is correct, or if additional steps—such as a proper firmware reset sequence via CARD_FW_RESET_REG or other host-side initialization—are required to ensure the firmware becomes fully operational.

I have attached code here:

static fwdnld_intf_ret_t sdio_interface_send(fwdnld_intf_t *intf,
const uint8_t *buffer,
uint32_t transfer_len,
uint32_t *len)
{
uint32_t tx_blocks = 0, txlen = 0, buflen = 0, offset = 0;
uint32_t outbuf_len;
uint8_t *loutbuf = NULL;
uint32_t resp;
uint32_t tries = 0, ioport;
fwdnld_intf_ret_t ret = FWDNLD_INTF_SUCCESS;

loutbuf = GET_INTF_OUTBUF(intf);
outbuf_len = GET_INTF_OUTBUFLEN(intf);
(void)memset(loutbuf, 0, outbuf_len);
*len = 0;

do
{
/* Read CARD_STATUS_REG (0X30) FN =1 */
for (tries = 0; tries < MAX_POLL_TRIES; tries++)
{
vTaskDelay(pdMS_TO_TICKS(1)); // Add 1 ms delay
if (wlan_card_status(DN_LD_CARD_RDY | CARD_IO_READY) == true)
{
vTaskDelay(pdMS_TO_TICKS(10)); // Add 10 ms delay
*len = wlan_card_read_f1_base_regs();
}
else
{
sdio_io_e("Error in wlan_card_status()");
continue;
// break;
}

// (void)PRINTF("len %d =>\r\n", *len);
if (*len != 0U)
{
break;
}
else if (offset > 0)
{
return FWDNLD_INTF_SUCCESS;
}
else
{ /* Do Nothing */
}
}

if (*len == 0U)
{
if (offset > 0)
{
return FWDNLD_INTF_SUCCESS;
}
sdio_io_e("Card timeout %s:%d", __func__, __LINE__);
return FWDNLD_INTF_FAIL;
}
else if (*len > outbuf_len)
{
sdio_io_e("FW Download Failure. Invalid len");
return FWDNLD_INTF_FAIL;
}
else
{ /* Do Nothing */
}

txlen = *len;

/* Set blocksize to transfer - checking for last block */
if (transfer_len < txlen)
{
txlen = transfer_len;
*len = txlen;
}

ioport = GET_INTF_SDIO_IOPORT(intf);
(void)memcpy((void *)loutbuf, (const void *)(buffer + offset), txlen);
calculate_sdio_write_params(txlen, (unsigned int *)&tx_blocks, (unsigned int *)&buflen);
(void)sdio_drv_write(ioport, 1, tx_blocks, buflen, (uint8_t *)loutbuf, &resp);

if (*len <= transfer_len)
{
transfer_len -= *len;
offset += *len;
}
else
{
ret = FWDNLD_INTF_FAIL;
break;
}
*len = 0;

} while (transfer_len > 0);

return ret;
}

Please advise if any additional steps are required to ensure the firmware is fully operational.

Best regards,

Tarak.

[DanielRuvalcaba]

Hi,

I'm sorry for the late reply.

I currently don’t have an IW610 module available to test on my side. I’ve asked some colleagues to help me by running the test and confirming whether this combination is supported.

If everything works correctly on the EVK board, then the issue might not be software-related but rather hardware.

Please allow me some time to gather this feedback.

Regards,

Daniel.

[Tarak_777]

Hi @DanielRuvalcaba ,

No problem regarding the delay. I completely understand. I’ve been held up with development activities for the past two weeks, and I would really appreciate it if you could share the confirmation as soon as possible, since this is currently blocking my progress.

Thank you for your support.

Best regards,
Tarak.

[DanielRuvalcaba · Accepted solution]

Hi, 

Thank you for understanding. 

I have an update from my colleague: he was able to bring up a 2LL module (IW610) with the RT1170-EVKB.
He used the wifi_cli example without any modifications, and it is working correctly

wifi cli demo                                                                                                                 
========================================                                                                                      
Initialize CLI                                                                                                                
========================================                                                                                      
CLI Build: Oct  7 2025 [16:18:05]                                                                                             
Copyright  2024  NXP                                                                                                          
MCU Board: MIMXRT1170-EVKB                                                                                                    
========================================                                                                                      
Initialize WLAN Driver                                                                                                        
========================================                                     
STA MAC Address: 78:F5:05:7B:CD:30 
board_type: 0, board_type mapping: 
0----CSP
1----QFN
board_type: 0, board_type mapping: 
0----CSP
1----QFN
app_cb: WLAN initialized
========================================
WLAN CLIs are initialized
========================================
ENHANCED WLAN CLIs are initialized
========================================
CLIs Available:
========================================

help 
clear 
mcu-suspend 
wlan-version 
wlan-mac 
wlan-thread-info 
wlan-net-stats 
wlan-set-mac <MAC_Address>
wlan-scan 
wlan-scan-opt ssid <ssid> bssid ...
wlan-add <profile_name> ssid <ssid> bssid...
wlan-remove <profile_name>
wlan-list 
wlan-connect <profile_name>
wlan-connect-opt <profile_name> ...
wlan-reassociate 
wlan-start-network <profile_name>
wlan-stop-network 
wlan-disconnect 
wlan-stat 
wlan-info 
wlan-address 
wlan-uap-disconnect-sta <mac address>
wlan-get-uap-channel 
wlan-get-uap-sta-list 
wlan-ieee-ps <0/1>
wlan-set-ps-cfg <null_pkt_interval>
wlan-deep-sleep-ps <0/1>
wlan-get-beacon-interval 
wlan-get-ps-cfg 
wlan-set-max-clients-count <max clients count>
wlan-get-max-clients-count 
wlan-rts <sta/uap> <rts threshold>
wlan-frag <sta/uap> <fragment threshold>
wlan-host-11k-enable <0/1>
wlan-host-11k-neighbor-req [ssid <ssid>]
wlan-host-11v-bss-trans-query <0..16>
wlan-mbo-enable <0/1>
wlan-mbo-nonprefer-ch <ch0> <Preference0: 0/1/255> <ch1> <Preference1: 0/1/255>
wlan-get-log <sta/uap> <ext>
wlan-roaming <0/1> <rssi_threshold>
wlan-multi-mef <ping/arp/multicast/del> [<action>]
wlan-wakeup-condition <mef/wowlan wake_up_conds>
wlan-add-packet-filter  sta/uap 0/1 <patterns number> <ptn_len> <pkt_offset> <ptn> ...........
wlan-auto-host-sleep <enable> <mode> <rtc_timer> <periodic>
wlan-send-hostcmd 
wlan-ext-coex-uwb 
wlan-set-uap-hidden-ssid <0/1/2>
wlan-eu-crypto-rc4 <EncDec>
wlan-eu-crypto-aes-wrap <EncDec>
wlan-eu-crypto-aes-ecb <EncDec>
wlan-eu-crypto-ccmp-128 <EncDec>
wlan-eu-crypto-ccmp-256 <EncDec>
wlan-eu-crypto-gcmp-128 <EncDec>
wlan-eu-crypto-gcmp-256 <EncDec>
wlan-set-antcfg <ant mode> [evaluate_time]
wlan-get-antcfg 
wlan-scan-channel-gap <channel_gap_value>
wlan-wmm-stat <bss_type>
wlan-reset 
wlan-set-regioncode <region-code>
wlan-get-regioncode 
wlan-11d-enable <sta/uap> <0/1>
wlan-uap-set-ecsa-cfg <block_tx> <oper_class> <new_channel> <switch_count> <bandwidth>
wlan-csi-cfg 
wlan-set-csi-param-header  <sta/uap> <csi_enable> <head_id> <tail_id> <chip_id> <band_config> <channel> <csi_monitor_enable> <ra4us>
wlan-set-csi-filter <opt> <macaddr> <pkt_type> <type> <flag>
wlan-txrx-histogram <action> <enable>
wlan-subscribe-event <action> <type> <value> <freq>
wlan-uapsd-enable <uapsd_enable>
wlan-uapsd-qosinfo <qos_info>
wlan-uapsd-sleep-period <sleep_period>
wlan-tx-ampdu-prot-mode <mode>
wlan-rssi-low-threshold <threshold_value>
wlan-rx-abort-cfg 
wlan-set-rx-abort-cfg-ext enable <enable> margin <margin> ceil <ceil_thresh> floor <floor_thresh>
wlan-get-rx-abort-cfg-ext 
wlan-cck-desense-cfg 
wlan-net-monitor-cfg 
wlan-set-monitor-filter <opt> <macaddr>
wlan-set-monitor-param <action> <monitor_activity> <filter_flags> <radio_type> <chan_number>
wlan-set-mgmtframetx-cfg 
wlan-set-mgmtframetx-header <PktType> <PktSubType> <FromDS> <ToDS> <SeqNum> <FragNum> <Addr1> <Addr2> <Addr3> <Addr4>
wlan-set-mgmtframetx-payload <Data0 Data1 ... Datan>
wlan-set-tsp-cfg <enable> <backoff> <highThreshold> <lowThreshold> <dutycycstep> <dutycycmin> <highthrtemp> <lowthrtemp>
wlan-get-tsp-cfg 
wlan-get-signal 
wlan-set-bandcfg 
wlan-get-bandcfg 
wlan-set-ips <option>
wlan-enable-disable-htc <option>
wlan-set-su <0/1>
wlan-set-forceRTS <0/1>
wlan-set-mmsf <enable> <Density> <MMSF>
wlan-get-mmsf 
wlan-get-turbo-mode <STA/UAP>
wlan-set-turbo-mode <STA/UAP> <mode>
wlan-set-multiple-dtim <value>
wlan-set-country <country_code_str>
wlan-set-country-ie-ignore <0/1>
wlan-single-ant-duty-cycle <enable/disable> [<Ieee154Duration> <TotalDuration>]
wlan-dual-ant-duty-cycle <enable/disable> [<Ieee154Duration> <TotalDuration> <Ieee154FarRangeDuration>]
wlan-set-indrstcfg <mode> <gpio_pin>
wlan-get-indrstcfg 
wlan-independent-reset <mode>
wlan-sta-inactivityto <n> <m> <l> [k] [j]
wlan-auto-null-tx <sta/uap> <start/stop>
wlan-get-channel-load <set/get> <duration>
wlan-get-txpwrlimit <subband>
wlan-set-chanlist 
wlan-get-chanlist 
wlan-set-txratecfg <sta/uap> <format> <index> <nss> <rate_setting> <autoTx_set>
wlan-get-txratecfg <sta/uap>
wlan-get-data-rate <sta/uap>
wlan-get-pmfcfg 
wlan-uap-get-pmfcfg 
wlan-set-ed-mac-mode <interface> <ed_ctrl_2g> <ed_offset_2g> <ed_ctrl_5g> <ed_offset_5g>
wlan-get-ed-mac-mode <interface>
wlan-set-tx-omi <interface> <tx-omi> <tx-option> <num_data_pkts>
wlan-set-toltime <value>
wlan-set-rutxpwrlimit 
wlan-11ax-cfg <11ax_cfg>
wlan-11ax-bcast-twt <set/get>
wlan-11ax-twt-setup <dump/set/done> [<param_id> <param_data>]
wlan-11ax-twt-teardown <dump/set/done> [<param_id> <param_data>]
wlan-11ax-twt-report 
wlan-11ax-twt-information <flow_identifier> <suspend_duration>
wlan-get-tsfinfo <format-type>
wlan-set-clocksync <mode> <role> <gpio_pin> <gpio_level> <pulse width>
ping [-s <packet_size>] [-c <packet_count>] [-W <timeout in sec>] <ipv4/ipv6 address>
iperf [-s|-c <host>|-a|-h] [options]
dhcp-stat 
========================================

# 
# 
# wlan-version
WLAN Driver Version   : v1.3.r48.p48
WLAN Firmware Version : iw610w-V0, SDIO, FP99, 18.99.5.p76, PVE_FIX 1

 The IW610 is supported and working correctly on the EVK.
Since it is working on the EVK and you are using a custom board, this makes me think that your issue might not be software-related, but rather hardware-related.

Regards,

Daniel.

[Tarak_777]

Hi @DanielRuvalcaba ,

I was able to download the firmware successfully, and the board bring-up is done. Thank you for your support.

I have one doubt regarding the configuration below:

#define WIFI_BT_TX_PWR_LIMITS "wlan_txpwrlimit_cfg_murata_NH.h"
#define IW610
#define SDMMCHOST_OPERATION_VOLTAGE_1V8
#define SD_TIMING_MAX kSD_TimingDDR50Mode
#define WIFI_BT_USE_USD_INTERFACE
#define WLAN_ED_MAC_CTRL { .ed_ctrl_2g = 0x1, .ed_offset_2g = 0xA, .ed_ctrl_5g = 0x1, .ed_offset_5g = 0xA }

Since I am using the Murata 2LL module (based on the same IW610 chip family), can I continue using the same transmitter power limits and WLAN_ED_MAC_CTRL settings as provided for the Murata NH module?

Best regards,
Tarak.

[DanielRuvalcaba]

Hi,

Thank you for confirming it is working correctly.

Regarding your TX power question:
Since those files were originally intended for the Murata module and not specifically for the u-blox one you're using, I recommend checking directly with the module manufacturer. They might have specific configuration files tailored for their hardware.

Regards,
Daniel.

[Tarak_777]

Hi @DanielRuvalcaba ,

Thanks for the input. I will confirm with manufacturer accordingly. By the way, Thank you so much for your support and time. 

Have a wonderful day.

Best regards,

Tarak.

[Tarak_777]

Hi @DanielRuvalcaba ,

Thanks for the update and clarifiation.

I have updated all my hardware connections correctly. However, the MAYA module documentation suggests adding external pull-ups for SD1, SD2, and SD3. After adding these pull-ups, the CMD response stops coming, whereas without the pull-ups, the response works fine. Currently, all data lines have 10 kΩ pull-ups, and the CMD line also has a 10 kΩ pull-up. Could these resistors be affecting the SDIO communication?

Best regards,

Tarak.

[DanielRuvalcaba]

Hi,

This is a good point.
I would recommend double-checking with the module manufacturer about this. They might be able to provide more detailed information.

Regards,
Daniel.

[Tarak_777]

Hi @DanielRuvalcaba ,

We have ordered the new MIMXRT1170-EVKB. I will review it once received and provide you with an update as soon as possible.

Best regards,
Tarak.

[Tarak_777]

Hi @DanielRuvalcaba,

Thanks for the input. Please give me some time; I will update you with information from my side.

Best regards,

Tarak.

[Tarak_777]

Hi @DanielRuvalcaba ,

I don’t have the Murata 2LL module and the RT1170-EVKB board; I’m working with a custom board instead.
By the way, could you please confirm if this combination is officially supported?

Regards,
Tarak.