• State Resolved
  • Locked Locked
  • Replies 19 replies
  • Subscribers 41 subscribers
  • Views 2690 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

runtime power management issue on wl1271 porting to imx6

shabeer badarudheen
Prodigy 130 points
Other Parts Discussed in Thread: WL1271

Hello,

2671.teraterm.log
Fullscreen
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
U-Boot 2013.10 (Apr 16 2014 - 10:46:22)
CPU: Freescale i.MX6Q rev1.2 at 792 MHz
Reset cause: POR
Board: MX6-SabreSD
DRAM: 1 GiB
MMC: FSL_SDHC: 0
No panel detected: default to HDMI
Display: HDMI (1024x768)
In: serial
Out: serial
Err: serial
i2c: I2C1 SDA is low, start i2c recovery...
I2C1 Recovery success
force_idle_bus: sda=0 scl=0 sda.gp=0x0 scl.gp=0x0
force_idle_bus: failed to clear bus, sda=0 scl=0
POT value := 64Net: Phy not found
PHY reset timed out
FEC [PRIME]
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
We are trying to port TiWi-BLE (WL1271) module in to imx6 processor. The BSP used is downloaded from freescale and the kernel version is 3.0.35.

Initially we face lot of issues. After refer the TI forum and look in to the wl12xx driver code we found some mismatches with our hardware. The WLAN_IRQ line used is negative logic. So we modify the function  wl1271_probe () in the file drivers/net/wireless/wl12xx/sdio.c. We just added                                                                    "irqflags = IRQF_TRIGGER_FALLING" before the function request_threaded_irq(). After this change the module is up and we are able to configure as both client and Access Point. ping command is also tested in the client mode.
    
 But the problem is that the module is up only if we comment the three lines in the function wl1271_sdio_power_on() on the file sdio.c,which  is shown below
        
    /* Make sure the card will not be powered off by runtime PM */
    ret = pm_runtime_get_sync(&func->dev);
    if (ret < 0)
          goto out;

    If we uncomment this code snippet we got some error messages, the log file is also attached.
    
    Could somebody help me?
    
    Best regards
    Shabeer

  • 0
    TI__Guru* 85400 points

    Hi Shabeer,

    It looks to me that you are not using the latest wl12xx release. Please confirm your release.
    The latest release is: ol_R5.SP7.01.

    The build instructions can be found at: https://github.com/TI-ECS/build-utilites/blob/master/wl12xx_build.sh

    Regards,
    Gigi Joseph.

  • 0 in reply to Joseph Gigi
    Prodigy 130 points

    Hi Gigi Joseph,

    How we know the release version of wl12xx driver? We got the driver from Free scale BSP(kernel version 3.0.35).

    if we give the "ifconfig wlan0 up" command we got the message -- wl1271: firmware booted (Rev 6.1.5.50.74)

    Also if we setup the module in  Access point mode the message is  -- wl1271: firmware booted (Rev 6.2.1.0.54)

    Is the driver islatest ?

    Regards

    Shabeer

  • 0 in reply to shabeer badarudheen
    TI__Guru* 85400 points

    Hi Shabeer,

    No, it is a very old release that you are using.

    To know the driver/firmware version, you can follow the below page:
    http://processors.wiki.ti.com/index.php/WL12xx_NLCP_Driver_Debug

    As I said earlier, you need to use the build script to build the correct version.

    Regards,
    Gigi Joseph.

  • 0 in reply to Joseph Gigi
    Prodigy 130 points

    Hi Gigi Joseph,

    Thanks for your support. We done based on the build script, it is working now...

    Regards

    Shabeer

  • 0 in reply to shabeer badarudheen
    Prodigy 130 points

    Hi Gigi Joseph,

    Now we are facing some issues in Calibration procedure.

    Calibration is really required? without calibration,  we are able to configure the wifi module as both host and client. communication is also possible...

    I am attaching the error messages also? How can i clear this error?

    Regards

    Shabeer

    8321.wifi_errorlog.txt
    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    shabeer wl1271_init 1.0 sdio.c
    in wl12xx_set_power delay added on=1
    wl12xx: shabeer wl12xx_probe ****** SET irqflags=IRQF_TRIGGER_FALLING******** main.c
    add wake up source irq 103
    shabeer wl12xx_sdio_power_on sdio.c
    in wl12xx_set_power delay added on=1
    in wl12xx_set_power delay added on=1
    shabeer in dri/host/mmc/sdhci--imx.c
    in wl12xx_set_power delay added on=1
    shabeer in dri/host/mmc/sdhci--imx.c
    in wl12xx_set_power delay added on=1
    shabeer in dri/host/mmc/sdhci--imx.c
    in wl12xx_set_power delay added on=1
    shabeer in dri/host/mmc/sdhci--imx.c
    in wl12xx_set_power delay added on=1
    shabeer in dri/host/mmc/sdhci--imx.c
    in wl12xx_set_power delay added on=1
    shabeer in dri/host/mmc/sdhci--imx.c
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

     

  • 0 in reply to shabeer badarudheen
    TI__Guru* 85400 points

    Hi Shabeer,

    wl12xx: ERROR command execute failure 2

    suggests a mismatch between driver/firmware(plt) versions.

    If you are using the ol_R5.SP7.01 release, the PLT fw version for the driver should be 6.3.10.0.137
    Please ensure that you are copying all the binaries generated by the build script to the target.

    Regards,
    Gigi Joseph.

  • 0 in reply to Joseph Gigi
    Prodigy 130 points

    Hi Gigi Joseph,

    From the script " https://github.com/TI-ECS/build-utilites/blob/master/wl12xx_build.sh" we just done wl12xx_build.sh wl12xx_modules install  and  wl12xx_build.sh firmware install only.

    The Driver and firmware version are shown below. Is it Latest one (PLT fw is 6.3.10.0.136)?

    root@imx6qsabresd:~# strings wl12xx.ko | grep ol_R
    ol_R5.SP4.01-2-g1aa2c8e
    ol_R5.SP4.01-2-g1aa2c8e
    root@imx6qsabresd:~# strings compat.ko | grep ol_R
    <6>Compat-wireless backport release: ol_R5.SP7.01
    <6>Backport based on wl12xx.git ol_R5.SP4.01-2-g1aa2c8e
    ol_R5.SP7.01
    ol_R5.SP4.01-2-g1aa2c8e
    root@imx6qsabresd:~# strings wl127x-fw-4-mr.bin | grep Rev
    Rev 6.5.7.0.46
    173369,69,release.c,ReadRevision,4|Firmware version: %0.4s%0.4s%0.4s%0.4s
    root@imx6qsabresd:~# strings wl127x-fw-4-plt.bin | grep Rev
    FRev 6.3.10.0.136
    root@imx6qsabresd:~# strings wl127x-fw-4-sr.bin | grep Rev
    FRev 6.3.10.0.136
    root@imx6qsabresd:~#strings wl1271-fw-multirole-plt.bin | grep Rev

    --
    root@imx6qsabresd:~#strings wl1271-fw-multirole-roc.bin | grep Rev
    FRev 6.3.3.0.79

    Regards,

    Shabeer

  • 0 in reply to shabeer badarudheen
    TI__Guru* 85400 points

    Hi Shabeer,

    No, its not the latest. Please try "./wl12xx_build.sh all build"
    Also, please modify gen_tag in script to "ol_R5.SP7.01" and try.

    Regards,
    Gigi Joseph.

  • 0 in reply to Joseph Gigi
    Prodigy 130 points

    Thanks Gigi .. Calibration is Success now....

    Also we are decide to upgrade the Linux kernel.  The current kernel version  used is 3.0.35  and we are upgraded to 3.10.17. The source code structure of  wl12xx chip was changed in 3.10. Do we need the wl12xx_build.sh script for compiling in 3.10 or the default 3.10 chip driver is the latest one?

    Regards

    Shabeer

  • 0 in reply to shabeer badarudheen
    TI__Guru* 85400 points

    Hi Shabeer,

    You must use the wl12xx_build.sh to compile the wl12xx drivers... But we have never tried building the wl12xx driver on the 3.10 kernel. So you might want to modify the source a bit to work with 3.10.

    Regards,
    Gigi Joseph.

  • 0 in reply to Joseph Gigi
    Prodigy 130 points

    Hi Gigi Joseph,

    I am out of office for the last three days. I have some doubts..

    1. wl12xx_build.sh is used for back porting a latest driver(3.2 series) in to the older kernel.is it write?. How can we use this  script for compiling the driver in 3.10 series. If we replace/modify the drivers/net/wireless/wl12xx, net/wireless/cfg80211,  net/mac80211 folders and also use the corresponding firmwares will it work in 3.10?

    2. I am not an expert in Linux kernel, i compare the vanilla kernel and free scale kernel(3.10 series) both are almost same,  my understanding is that the vanilla kernel contains the tested drivers only.Then why we need to use the wl12xx_build.sh script?. Is it because of driver-firmware combination?

    Regards

    Shabeer

  • 0 in reply to shabeer badarudheen
    TI__Guru* 85400 points

    Hi Shabeer,

    The latest wl12xx driver is not ported into the Linux mainline.
    This is why we use compat-wireless for build. The driver code downloaded by the wl12xx_build.sh script will be much newer than what you have in the vanilla kernel.

    So, like I told before, the build process remains the same - that is, using wl12xx_build.sh irrespective of which kernel you build it on. Of course, you will have to modify the "setup-env" parameters to reflect the new kernel.

    Regards,
    Gigi Joseph.

  • 0 in reply to Joseph Gigi
    Prodigy 130 points

    Hi Gigi joseph,

    We compiled the wl12xx driver using 3.10 kernel (after doing some changes on the source ). We just run the script after modifying the KLIB_BUILD variable on  "setup-env" file. Now we are trying to modify the board file changes. In 3.0 kernel the board file modifications are done based on " http://processors.wiki.ti.com/index.php/WL18xx_Platform_Integration_Guide". Since the 3.10 kernel using 'device tree concepts'  we don't no how to do the changes. Can you share any useful links / steps for modifying  the board files.

    Regards

    Shabeer

  • 0 in reply to shabeer badarudheen
    TI__Guru* 85400 points

    Hi Shabeer,

    I have the DT patches for WL8 - https://gforge.ti.com/gf/download/frsrelease/1161/6994/dt_pathces.zip
    Hopefully, it will help you.

    Regards,
    Gigi Joseph.

  • 0 in reply to Joseph Gigi
    Prodigy 130 points

    Thanks Gigi... It is very helpful for us..

    Also for the  power control mechanism we are using set_power function ( set and clear  WLAN_EN pin of wifi chip ) not the voltage regulator method. So do we need to implement the set_power  function or the above patches will take care about the power control operation?

    Regards

    Shabeer

  • 0 in reply to shabeer badarudheen
    Prodigy 130 points

    Hi Gigi,

    We ported wifi chip driver in 3.10.17 freescale BSP. 

    But we not used the build script " https://github.com/TI-ECS/build-utilites/blob/master/wl12xx_build.sh" because nitrogen6x(i.mx6 based development board ) had already ported using the freescale BSP. we follow the same procedure.

    But doing calibration we are facing some issues.

    we try calibration based on the link " http://www.armadeus.com/wiki/index.php?title=Wl12xx_driver" . While run the command " calibrator plt calibrate dual" we got some error message as shown below.

    Unknown arch. Not setting nvs ver 2.1Calibrate ./new-nvs.bin
    Writing calibration data to ./new-nvs.bin��v
    File 8�v not exists
    Fail to prepare calibrated NVS file

    dmesg out:

    [ 8717.946030] wlcore: power up
    [ 8718.341512] wlcore: firmware booted in PLT mode PLT_ON (PLT 6.3.10.0.133)
    [ 8718.410034] wlcore: testmode cmd: radio status=0
    [ 8718.417257] wlcore: power down

    may i know what is the issue?

    Regards

    Shabeer

  • 0 in reply to shabeer badarudheen
    TI__Guru* 85400 points

    Hi Shabeer,

    I am not familiar with the link that you mentioned.
    Please follow this link: http://processors.wiki.ti.com/index.php/WL12xx_NLCP_Calibration_Process

    Command: calibrator plt autocalibrate <dev> <kernel mod> <ini> <nvs> <mac>

    Anyway, the error from your current run seems to be that the "new-nvs.bin" does not exist in the said location... But please try the above command.

    Regards,
    Gigi Joseph.

  • 0 in reply to Joseph Gigi
    Prodigy 130 points

    Hi Gigi Joseph,

    Is Calibration is really required? Without also the wifi chip is working...

    In 3.10 kernel,wifi diver source structure and driver names are different one. Then how can we follow the link? (http://processors.wiki.ti.com/index.php/WL12xx_NLCP_Calibration_Process )

    Regards

    Shabeer

  • 0 in reply to shabeer badarudheen
    TI__Guru* 85400 points

    Hi Shabeer,

    Yes, calibration is required. It is a one time process.
    The calibration tool is a user space utility. I don't think that the link will be irrelevant for kernel 3.10.

    Regards,
    Gigi Joseph.