Porting FMAC for Murata modules

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Porting FMAC for Murata modules

Jump to solution
1,477 Views
romitchatterjee
Contributor V

How difficult is it to port the latest FMAC to an older kernel (say 4.9.11), to be used o i.MX 6UL, Murata 1DX. Are there any guides I can use?

Labels (2)
Tags (1)
0 Kudos
1 Solution
1,334 Views
bill_chen1
Contributor III

With your case, you need to do backporting. Cypress offers packages for backporting in their fmac releases, and Murata integrated it in our Linux solution for older kernels, i.e. 4.9.123, 4.9.88, 4.9.11, and 4.1.15. For these versions of Linux Kernel,  you can simply run Murata's build script, and it will do the backporting and build the image for you. To learn more about how backporting is implemented, please refer to Murata's Linux user manual.

https://wireless.murata.com/datasheet?/RFM/data/murata_linux_user_manual_5.4.pdf 

If your kernel version is not supported by Murata, please refer to the README file in Cypress' fmac release. You can find the steps for backporting there.

View solution in original post

0 Kudos
3 Replies
732 Views
vinayharitsakp1
Contributor III

Team,

I am trying to connect uSD Adapter Fixed 3.3 V rev A board to micro SD slot of IMX8MM MINI LPD4-CPU2. on the muratha board i am connecting CYW54591.

 

Following are the DTS changes i am doing

&usdhc2{

compatible = "fsl,imx6q-usdhc";
reg = <0x02194000 0x4000>;
interrupts = <0 23 0x04>;
clocks = <&clks 164>, <&clks 164>, <&clks 164>;
clock-names = "ipg", "ahb", "per";
pinctrl-names = "default";
pinctrl-0 = <&pinctrl_usdhc2_1>;
cd-gpios = <&gpio2 2 0>;
wp-gpios = <&gpio2 3 0>;
bus-width = <8>;
no-1-8-v;
non-removable;
mmc-pwrseq = <&usdhc2_pwrseq>;
pm-ignore-notify;
cap-power-off-card;
// keep-power-in-suspend;
enable-sdio-wakeup;
mmc-hs200-1_8v;
mmc-hs400-1_8v;
bus-width = <8>;
status = "okay";


brcmf: bcrmf@1 {
reg = <1>;
compatible = "brcm,bcm4329-fmac";
};
};

 

I am getting the following error message:

[ 43.332028] mmc1: sdhci: ADMA Err: 0x00000000 | ADMA Ptr: 0x00000000
[ 43.338468] mmc1: sdhci-esdhc-imx: ========= ESDHC IMX DEBUG STATUS DUMP =========
[ 43.346037] mmc1: sdhci-esdhc-imx: cmd debug status: 0x2180
[ 43.351695] mmc1: sdhci-esdhc-imx: data debug status: 0x2200
[ 43.357440] mmc1: sdhci-esdhc-imx: trans debug status: 0x2300
[ 43.363273] mmc1: sdhci-esdhc-imx: dma debug status: 0x2400
[ 43.368932] mmc1: sdhci-esdhc-imx: adma debug status: 0x2500
[ 43.374678] mmc1: sdhci-esdhc-imx: fifo debug status: 0x2680
[ 43.380424] mmc1: sdhci-esdhc-imx: async fifo debug status: 0x2750
[ 43.386689] mmc1: sdhci: ============================================
[ 53.471645] mmc1: Timeout waiting for hardware cmd interrupt.
[ 53.477404] mmc1: sdhci: ============ SDHCI REGISTER DUMP ===========
[ 53.483847] mmc1: sdhci: Sys addr: 0x00000000 | Version: 0x00000002
[ 53.490286] mmc1: sdhci: Blk size: 0x00000000 | Blk cnt: 0x00000001
[ 53.496725] mmc1: sdhci: Argument: 0x00000000 | Trn mode: 0x00000000
[ 53.503165] mmc1: sdhci: Present: 0x00688009 | Host ctl: 0x00000001
[ 53.509605] mmc1: sdhci: Power: 0x00000000 | Blk gap: 0x00000080
[ 53.516045] mmc1: sdhci: Wake-up: 0x00000008 | Clock: 0x000010ff
[ 53.522486] mmc1: sdhci: Timeout: 0x0000008e | Int stat: 0x00000000
[ 53.528927] mmc1: sdhci: Int enab: 0x007f1003 | Sig enab: 0x007f1003
[ 53.535367] mmc1: sdhci: ACmd stat: 0x00000000 | Slot int: 0x00000502
[ 53.541808] mmc1: sdhci: Caps: 0x07eb0000 | Caps_1: 0x8000b407
[ 53.548249] mmc1: sdhci: Cmd: 0x00000502 | Max curr: 0x00ffffff
[ 53.554688] mmc1: sdhci: Resp[0]: 0x00000000 | Resp[1]: 0x00000000
[ 53.561126] mmc1: sdhci: Resp[2]: 0x00000000 | Resp[3]: 0x00000000
[ 53.567566] mmc1: sdhci: Host ctl2: 0x00000000
[ 53.572010] mmc1: sdhci: ADMA Err: 0x00000000 | ADMA Ptr: 0x00000000
[ 53.578450] mmc1: sdhci-esdhc-imx: ========= ESDHC IMX DEBUG STATUS DUMP =========
[ 53.586019] mmc1: sdhci-esdhc-imx: cmd debug status: 0x2180
[ 53.591676] mmc1: sdhci-esdhc-imx: data debug status: 0x2200
[ 53.597422] mmc1: sdhci-esdhc-imx: trans debug status: 0x2300
[ 53.603254] mmc1: sdhci-esdhc-imx: dma debug status: 0x2400
[ 53.608913] mmc1: sdhci-esdhc-imx: adma debug status: 0x2500
[ 53.614659] mmc1: sdhci-esdhc-imx: fifo debug status: 0x2680
[ 53.620407] mmc1: sdhci-esdhc-imx: async fifo debug status: 0x2750

Request you to guide me if the MicroSD slot on Imx8mm mini  evk board supports sdmmc/ reconfiguration of SDIO.

0 Kudos
1,335 Views
bill_chen1
Contributor III

With your case, you need to do backporting. Cypress offers packages for backporting in their fmac releases, and Murata integrated it in our Linux solution for older kernels, i.e. 4.9.123, 4.9.88, 4.9.11, and 4.1.15. For these versions of Linux Kernel,  you can simply run Murata's build script, and it will do the backporting and build the image for you. To learn more about how backporting is implemented, please refer to Murata's Linux user manual.

https://wireless.murata.com/datasheet?/RFM/data/murata_linux_user_manual_5.4.pdf 

If your kernel version is not supported by Murata, please refer to the README file in Cypress' fmac release. You can find the steps for backporting there.

0 Kudos
1,334 Views
gusarambula
NXP TechSupport
NXP TechSupport

Hello Romit Chatterjee,

This Quick Start Guide may help. These modules are manufactured and supported by Murata. Kernel 4.9.11 is supported fortunately.

https://wireless.murata.com/pub/RFM/data/murata_quick_start_guide_linux.pdf

I hope this helps!

Regards,