TIDC-WL1837MOD-AUDIO-MULTIROOM-CAPE: Wireless Connectivity Cape Linux questions

Which cape are you using? Is it Multiroom audio cape or the WL8 wireless cape? Because the 'device tree'/DTBs are different.

And, i would suggest taking the processor SDK images (MLO,u-boot and rootfs) on to a SDcard and boot, instead of rebuilding everything..

Thanks

Hi Hari,

Sorry for the confusion. It's the WL8 wireless cape.

Thank you,

Franz

Ok. I suggest the following:

1) Take the SDcard image from processor SDK (below link), flash it to the SDcard

software-dl.ti.com/.../am335x-evm-linux-06.00.00.07.img.zip

2) You should be able to boot with this image. But, you may need to update the device tree for COM8 WL8 module. You can rebuild the device tree with the change. Or, you copy the attached DTB file to the rootfs, "/boot/am335x-boneblack.dtb"

http://processors.wiki.ti.com/index.php/WL18xx_Platform_Integration_Guide#Appendix_B:_Device_Tree_file_-_patching_and_updatingam335x-boneblack-elem14.dtb

Thanks

Hi Hari,

Following the steps you suggested. I have issues/questions listed below:

1) the image is larger than 16 GB, so i took a 32 GB card. Shall BBB only operate with max 16 GB cards or is it able to deal with sd cards larger in size?

2) after writing the image on the card with "dd" command,  I failed booting Linux on BBB  with it.

So I connected the serial cable interrupted booting and made the following changes to force it too boot throughly:

console=ttyO0,115200n8 root=/dev/mmcblk0p2 rw rootfstype=ext4 rootwait

load mmc 0:2 0x82000000 /boot/am335x-boneblack-elem14.dtb        //to load the device three

setenv bootargs console=ttyO0,115200n8 root=/dev/mmcblk0p2 rw rootfstype=ext4 rootwait

bootz 0x88000000 - 0x82000000

this enabled booting Linux.  But I do not know if these changes are interrupting something else, or maybe even some major configuration is missing even though the device boots.

Thanks,

Emine

Humm.. The disk images are generally smaller than that, and you should be able to directly boot from it. I wonder, if the beagle bone is booting directly from eMMC.

When, you booted with the u-boot commands mentioned in your post, did the WiFi come up ok?

Thanks

Hi Hari,

It was indeed trying to boot from eMMC even though I thoght it wasnt.

The device bootes now successfully. And after copying the device three file  also WiFi came up!

Thanks for the help!

Hi Hari,

I tried to test wifi-mesh after successfully booting Linux. After running following command:

#sh /usr/share/wl18xx/mesh_start.sh

I get this error message:

adding mesh0 interface
command failed: Operation not supported (-95)
Successfully initialized wpa_supplicant
Failed to open config file '/home/root/mesh_supplicant.conf', error: No such file or directory
Failed to read or parse configuration '/home/root/mesh_supplicant.conf'.
command failed: Resource temporarily unavailable (-11)
ifconfig: SIOCSIFADDR: No such device

I looked for the root cause of the problem and found this:

# zcat /proc/config.gz | grep MESH
# CONFIG_MAC80211_MESH is not set

Apparently mesh is not set in Linux kernel and because of that I cant run sh command for testing mesh.

Any hints, how I should proceed?

Thanks,

Emine

Hi,

Please, rebuild the kernel and modules as below -

a) rebuild the SDK6.0 (K4.19) kernel and kernel modules with the following build flags enabled: 

CONFIG_MAC80211_MESH=y

CONFIG_NL80211_TESTMODE=y

b) Download the zImage to rootfs/boot' folder and install the rebuilt kernel modules to the target file system.

c) Download the attached APKs to a folder in the target file system, ex: /opt/ipks

d) Install the ipks (check the README file, which also shows installing the IPKs)

e) start mesh.

Thankswpasupplicant-with-mesh-yacto-build.zip

Hi Hari,

originally I was failing to build the SDK, it was not recognizing my beagle bone board. I just copied the image you sent me to an SD Card and was able too boot everything.

After getting your response above I gave it another try to rebuild it with the flags enabled, but I am failing.
Steps I folllowed:

1)software-dl.ti.com/.../Overview_Getting_Started_Guide.html

2) Built the setup described here and followed the steps:

http://software-dl.ti.com/processor-sdk-linux/esd/docs/latest/linux/Overview_Getting_Started_Guide.html#run-setup-scripts 

here I stuck in uboot Setup, I get a message saying it does not recognize my beaglebone black and asks if I am using a standard board.

Since I could not come any further than this I cannot apply your solution. Are you familiar with the problem I am getting? I was looking for something similar in questions asked her but could not find anything directly related.

Thanks

It is not clear to me, which component build is failing. Is it when building wilink components with build scripts? 

Thanks

Hi Hari,

No my problem is unrelated to wireless cap, although I want to use it when I am done installing.
I am not coming so far yet.

The steps which one shall follow to build the SDK, which I mentioned above are the problem.
I stuck in building process.

After you send me a ready image I just added the device tree file for wifi-cape and was able to make it work.
But shortly afterwards I realized that wifi-mesh was not active in Linux-Kernel. So you suggested me to rebuild it with the flags set.
Since I did not build it in the first run, I cannot activate the flag.

I hope I could roughly explain the problem.

Thanks