Hi,
I am new to OMAP developement and our company has just recently chosen OMAP-L138 as our base platform for future product development.
One of the first products we are going to use OMAP-L138 will require wireless connectivity which we found out that the WL1271 can provide (Wifi + bluetooth).
However, base on the post I've read from the forum I only found support for the WL1271 on the OMAP35xx.
Can you please clarify if the OMAP-L138 can be interfaced with the WL1271?
Also are their available any Linux device drivers for the WL1271 which can be installed in the Linux package for the OMAP-L138.
Please advice.
Grant Hatamosa
Senior Software Engineer
Inderjit,
From your e-mail I understand that libnl-2.0 is installed under ~/SDK/targetfs/lib, and it is as should be. Also, please, check ~/SDK/targetfs/lib/pkgconfig directory is created and there are "*.pc" files there for libnl. You can put config.log files of iw and other logs to zip archive and upload to e2e. In any way, I'll send you my email to send files easier.
Best regards,
Vita.
~/SDK/targetfs/lib/pkgconfig has one .pc file: libnl-2.0.pc. I have uploaded the BT build log - let me know if it reveals anything.
Inderjit
Is this being looked at?
The reason because of bluetooth build fails is that configure process of dbus fails to find expat.h on your target root file system. From the log you've sent expat
is built, but still it cannot be found. To understand what is the reason I need you to perform the following:
1. check if your root file system has expat.h (shoudl be in <rootfs>/usr/include)
2. upload dbus-1.4.1/config.log to see what is the reason why configure doesn't find expat.
There is no expat.h in <rootfs>/usr/include. I'm using tisdk-rootfs-am180x-evm.tar.gz. This is the file system that comes with SDK 5.04. If a different file system should be used, please provide the link.
dbus-1.4.1/config.log is attached.
Hi, Inderjit.
I'm working on reproducing the problem and fixing it. Once build is fixed I'll upload the new bluetooth build script.
Best regards,Vita.
Any progress? It's past the previous error (not sure why), and gets stuck on:
libtool: link: arm-none-linux-gnueabi-ar cru .libs/libiconv.a objects/iconv.o objects/localcharset.o objects/relocatable.olibtool: link: arm-none-linux-gnueabi-ranlib .libs/libiconv.alibtool: link: ( cd ".libs" && rm -f "libiconv.la" && ln -s "../libiconv.la" "libiconv.la" )cp .libs/libiconv.so preloadable_libiconv.socp: cannot stat `.libs/libiconv.so': No such file or directorymake[1]: *** [preloadable_libiconv.so] Error 1make[1]: Leaving directory `/home/ib/SDK/temp/libiconv-1.13.1/preload'make: *** [all] Error 2
This is for the BT Build (command: ./wl12xx_build_bt.sh all build)
Please download new version of script from this location: https://gforge.ti.com/gf/download/frsrelease/919/5953/wl12xx_build_BT_blueZ4_98.sh.
Run it on clean file system without previous build.
If you encounter any problems, please, inform me.
It runs for a lot longer, but still doesn't finish. Build log is attached for a clean filesystem.
Hello,
I want to make omapl138 evm to conect internet through marvell88W8686 wifi chip . But when I insmod two .ko files , the print message shows
I have move two .bin files in /lib/firmware/mrvl dictionary.
can you give me some advices?
thank you very much !
Any update on this?
I can make their firmware in the kenel, the wlan modules works well.
But,when system start, the eth0 can't work well.the log shows it had been interrupted!
thank you !
Sorry Lee, I was referring to my question above.
I don't encounter such problems on other systems. Is it possible to upload the archived entire $WORK_SPACE directory? I need to see how every component configured itself on your building environment to understand where the problem is, since the problem is in building environment.
Also if you work with Ubuntu, please run "dpkg --get-selections > file" and send me the output.
The tar'd and GZip'd $WORK_SPACE directory including both WLAN and BT builds is 101MB. BT alone is 34MB. Both are well above the 20MB limit for e2e. If there is another way to upload it, let me know.
The dpkg command results are attached:
7851.dpkg_file.txt