1) Have you gotten the Murata documentation that is listed here. If please get the same.
2) Look at the kernel logs and you should see some messages from the driver when the module is being loaded.
Murata has good documentation on its modules. It would be useful to get this documentation if you are using Murata modules. To get these documents you need to be registered. When you purchase the Murata modules (from Mouser) it comes with an activation code and this activation code enables access to these docs.
Below are the titles of some of the docs:
Murata Wi-Fi BT EVK for i.MX6 Quick Start Guide (Linux) 3.0
Murata Wi-Fi BT EVK for i.MX6 Linux User Manual 3.0
Murata Wi-Fi BT EVK for i.MX6 Hardware User Manual 1.0
Thank you for the links. I do have these documents and I have followed the Quick Start guide for Linux and I believe I have the latest SD card image programmed. It shows that I am running Linux version 4.1.15-2.0.0 from Sept 16, 2016.
My problem remains that the modprobe command returns but gives no feedback or error code when you run it. I also ran the suggested insmod command, but it cannot load the bcmdhd.ko file, because the "wireless" sub-directory does not exist inside the "net" directory.
1) When I look at the startup log, I see:
This indicates that the setenv commands did take effect.
2) Something is odd with the wifi initialization though:
CFG80211-ERROR) wl_setup_wiphy : Registering Vendor80211)
wl_create_event_handler(): thread:wl_event_handler:5e started
CFG80211-ERROR) wl_event_handler : tsk Enter, tsk = 0xa850143c
dhd_attach(): thread:dhd_watchdog_thread:5f started
dhd_attach(): thread:dhd_dpc:60 started
dhd_deferred_work_init: work queue initialized
Dongle Host Driver, version 1.141.92 (r)
Compiled in drivers/net/wireless/bcmdhd
Register interface [wlan0] MAC: 00:90:4c:11:22:33
CFG80211-ERROR) wl_event_handler : was terminated
wl_destroy_event_handler(): thread:wl_event_handler:5e terminated OK
3) During init I see what could be regulator measurements that are not OK:
anatop_regulator 20c8000.anatop:regulator-vddcore@140: Failed to read a valid default voltage selector.
anatop_regulator: probe of 20c8000.anatop:regulator-vddcore@140 failed with error -22
anatop_regulator 20c8000.anatop:regulator-vddsoc@140: Failed to read a valid default voltage selector.
anatop_regulator: probe of 20c8000.anatop:regulator-vddsoc@140 failed with error -22
4) I also see
EXT3-fs (mmcblk1p2): error: couldn't mount because of unsupported optional features (240)
EXT2-fs (mmcblk1p2): error: couldn't mount because of unsupported optional features (244)
EXT4-fs (mmcblk1p2): recovery complete
Populating dev cache
tar: dev/disk/by-label/Bootx20imx6sl: Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
udev-cache: update failed!
I am not sure which of the above errors are critical for the Type ZP module's operation.
1 of 1 people found this helpful
The problem was that I was given the 4.1.15-2 image for the SD card. The 3.14.52 version of the SD card image, which is the one described in the quick Start Guide version 3.0, does actually work.