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.

WL1807MOD: Integration into Raspberry Pi CM3

Part Number: WL1807MOD


Hi!

We want to integrate the WL1807MOD into our hardware design using a Raspberry Pi CM3 module. The hardware is ready and Linux is running so far.

Is there any easy to follow guide on how to compile the drivers for WiFi and to integrate it to the Linux environment. In the documentation I didn't really find any good hints... Also, where can I download the driver source code?

Thanks in advance,

Harald

  • Hi, 

    The E2E https://e2e.ti.com/support/wireless-connectivity/wifi/f/968/t/870138 contains the details of updating the driver for kernel 4.19 version.Let me know if you have already referred to it. 

    Regards, 

    Sudharshan K N

  • I was talking about the procedure. I downloaded the kernel for Raspberry Pi and the WL18xx build scripts. I am using cross-development (WSL with Ubuntu on Windows 10). I compiled the kernel which worked. Then I tried to build the driver with the commands ./build_wl18xx.sh init and./build_wl18xx.sh update R8.7_SP3. And this failed.

    So I am asking how to proceed with a generic Linux and especially the kernel for Raspberry PI CM3.

    My setup-env:

    #                            \\\//
    #                           -(o o)-
    #========================oOO==(_)==OOo=======================
    # This file contains the exports needed for automating the
    # build process of WLAN components.
    # Place this file in the same directory with wl18xx_build.sh
    # build scripts. No need to run 'source setup-env', the build
    # scripts will perfom it internaly.
    #===========================================================
    # User specific environment settings - use full PATH
    
    # if DEFAULT toolchain path is set toolchain will be downloaded to ./toolchain.
    export TOOLCHAIN_PATH=~/tools/arm-bcm2708/arm-linux-gnueabihf/bin
    
    # if DEFAULT path to root filesystem is set ./fs folder will be used.
    export ROOTFS=DEFAULT
    
    #if DEFAULT kernel path is set - kernel will be downloaded (set branch to match kernel version)
    export KERNEL_PATH=~/linux
    
    # if KERNEL_VARIANT below is set the build script will look for kernel specific
    # patches under the patches directory:
    # - patches under the pathces/driver_patches/$KERNEL_VARIANT directory would be
    #   applied during "modules" build.
    # - patches under the patches/kernel_patches/$/$KERNEL_VARIANT directory would
    #   be applied to the kernel pointed by KERNEL_PATH in case the "patch_kernel"
    #   command is used.
    #   Note: the kernel is not built automatically after the patches are applied
    export KERNEL_VARIANT=DEFAULT
    
    export CROSS_COMPILE=arm-linux-gnueabihf-
    export ARCH=arm
    [ "$TOOLCHAIN_PATH" != "DEFAULT" ] && export PATH=$TOOLCHAIN_PATH:$PATH

  • Hi, 

    Can you please let me know which version of the kernel you are using? for Kernel 4.19 and above the build scripts doesn't work directly. if the kernel version is 4.9 or greater and 4.14 or lesser then you need to build the individual components. This is because the backports, compact, compact wireless components are not needed (this statement also applies to 4.19). You can still use the build scripts but need to build the individual components manually i.e, openssl, libnl, wpa_supplicant, hostapd, utils, CRDA (in the same order). This can be done as below 

    1. ./sudo_build_wl18xx.sh openssl
    2. ./sudo_build_wl18xx.sh libnl
    3. ./sudo_build_wl18xx.sh iw
    4. ./sudo_build_wl18xx.sh wpa_supplicant
    5. ./sudo_build_wl18xx.sh hostapd
    6. ./sudo_build_wl18xx.sh firmware à install the FW
    7. ./sudo_build_wl18xx.sh crda

    Pl let me know if this was helpful to resolve the issue. 

    Regards, 

    Sudharshan K N