• State TI Thinks Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 41 subscribers
  • Views 806 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Linux/WL1835MODCOM8B: wlan0 interface not created on TMDXEVM3358. WL1835modcom8b is inserted into the EVM slot.

Neeraj Sallh
Intellectual 685 points
Part Number: WL1835MODCOM8B
Other Parts Discussed in Thread: TMDXEVM3358,

Tool/software: Linux

       Since I am using the TMDXEVM3358 along with the WL1835modcom8b, and doing the complete build/install/integrate/verify WiFi functionality

thing for the first time.  And also because I am posting this after trying a number of things first on my own end, this mail is long.  

It first explains all that I tried and the problems I faced.

And then asks the questions that I need to have an answer to.

Please bear, and help.

All that was tried

Building and installation of Platform Linux SDK on EVM was done.

Setup.sh was run as per the links:

  1. http://processors.wiki.ti.com/index.php/Processor_SDK_Linux_Installer
  2. http://processors.wiki.ti.com/index.php/Processor_SDK_Linux_Setup_Script

Our expectation was that with the WL1835modcom8b inserted into the slot of EVM, and above setup.sh already carried out, 

power up of the EVM should show us the "wlan0" interface in the "ifconfig" output.

That did not happen. 

Then we figured out that the wlcore.ko, wlcore_sdio.ko and wl18xx.ko images in the directory structure under "board-support/...." were 

more recent than those in the directory structure under "targetNFS/....".  (We had opted for NFS in the setup.sh execution).

Therefore, we copied these .ko files from "board-support/...." to "targetNFS/.....".

This time around on power up we got to see the "wlan0" interface.

But then we couldn't figure out how to configure an AP/STA/mesh on this.

We did try a "wl" command for creation of "virtual wireless interface".  It gave an error, based upon which we ran the hostapd daemon, using a .conf file "/etc/hostapd.conf".

However, even after this we could not succeed in creating a "virtual wireless interface".

After this we moved over to following the instructions of below two links, thinking that perhaps this might be the missing thing:

  1. http://processors.wiki.ti.com/index.php/WL18xx_Platform_Integration_Guide
  2. http://processors.wiki.ti.com/index.php/WL18xx_System_Build_Scripts

We first did Platform integration instructions and then picked up system build scripts.

Currently we are stuck in system build scripts.

The following step:

./build_wl18xx.sh update R8.7_SP2

fails with an error:

"Can't locate strict.pm in @INC (you may need to install the module strict)"

Queries part

Here are my queries:

  1. My main purpose being just getting to see the functionality of WiFi on an EVM with WL1835modcom8b module installed,
    1. Wasn't the build and install of Processor Linux SDK enough? 
    2. Am I right to expect to see a wlan0 interface on power up of EVM if everything is right?
    3. Am I right to expect to be able to create a virtual interface over this wlan0 (I assume wlan0 is the PHY)?
    4. What will be the CLI commands/scripts that can be run to achieve the functionality of an AP/mesh/Adhoc operation/an STA?
  2. Was it at all required to go in for carrying out the steps mentioned in the following links.  My understanding from documentation elsewhere is that one of these is required for integration of WL18xx on non-EVM platforms, and the other one is required in case I wish to use some other version of the WiLink drivers than those available in the Processor Linux SDK build?  The links being:
    1. http://processors.wiki.ti.com/index.php/WL18xx_Platform_Integration_Guide
    2. http://processors.wiki.ti.com/index.php/WL18xx_System_Build_Scripts
  3. If yes:
    1. Then what is the correct order of execution of the instructions mentioned in these two links?  First Integration and then build scripts or vice-versa?
    2. How do I overcome this problem of "you might need to install strict.pm" mentioned above?

Regards,

Neeraj Sallh

  • 0
    TI__Expert 6335 points
    Neeraj,

    We have assigned your post to the relevant engineer and will get back to you.
  • 0 in reply to dale
    TI__Mastermind 27080 points
    Humm.. If, you are using AM335x EVM with COM8 module, please try with the TISDK binaries first.. Below, is the link to TISDK -
    software-dl.ti.com/.../index_FDS.html

    Thanks
  • 0 in reply to Hari Nagalla
    Intellectual 685 points
    Hari,
    We did refer this link. And as per a document "processor-sdk-linux-gsg-04.01.00.06.pdf" mentioned
    on this page we did even run setup.sh.
    However the wlan0 was not created in the EVM after having run this setup.sh.
    Then we carried out the copy of wlcore.ko, wl18xx.ko and wlcore_sdio.ko as mentioned in my original post.
    After this, when we power cycle the EVM the wlan0 was seen as created.

    But beyond this we couldn't figure out a way to use the EVM with WL1835modcom8b mounted, as AP/mesh/STA etc.
    That's why I had these queries:
    1. Wasn't the build and install of Processor Linux SDK enough?
    2. Am I right to expect to see a wlan0 interface on power up of EVM if everything is right?
    3. Am I right to expect to be able to create a virtual interface over this wlan0 (I assume wlan0 is the PHY)?
    4. What will be the CLI commands/scripts that can be run to achieve the functionality of an AP/mesh/Adhoc
    operation/an STA?

    --
    Regards,
    Neeraj