• Join
  • Sign In with my.TI Login
Texas Instruments
  • Products
  • Applications
  • Tools & Software
  • Support & Community
  • Sample & Buy
  • About TI
Sample & Purchase Cart Sample & Purchase Cart
  • Search
  • Advanced
TI E2E™ Community
  • Support Forums
  • Blogs
  • Groups
  • Videos
  • 简体中文
  • More ...
TI Home » TI E2E Community » Support Forums » Low Power RF & Wireless Connectivity » WLAN Applications Forum » Wl12xx_probe not being called - Compat wireless porting
Share
Low Power RF & Wireless Connectivity
  • Forums
  • Announcements
  • Files
  • E2E Wiki
Options
  • Subscribe via RSS

Wl12xx_probe not being called - Compat wireless porting

Wl12xx_probe not being called - Compat wireless porting

This question is not answered
Ravi Chobey
Posted by Ravi Chobey
on Feb 10 2012 07:12 AM
Prodigy50 points

Hi All,

We are currently using wl1271 chip in our project and we are taking the driver from "Compact wireless package". We are not able to probe that device  and we are doing following steps to make it work:

We have made the following changes to load the wl12xx_sdio.ko.

  1. Added the platform data passing support to kernel.

Modified the “bps313xv1.c” file to pass the platform data

Calling “ wl12xx_set_platform_data(&lpc313x_wlan_data)” from “bps313x_init()” function.

 

The lpc313x_wlan_data is defined  as

struct wl12xx_platform_data  lpc313x_wlan_data  __initdata = {

        .irq = IRQ_WLAN_INT,

                .board_ref_clock = WL12XX_REFCLOCK_38, /* 38.4 MHz */

      //  .board_tcxo_clock = WL12XX_TCXOCLOCK_32_736;

};

  1. Modified the “wl1271_probe()” function in the sdio.c file under /compat-wireless-2012-01-23/drivers/net/wireless/wl12xx/sdio.c

Original Code:

                if (func->num != 0x02)

                {

                                return -ENODEV;

                }

 

Modified to:

                if (func->num != 0x01)

                {

                                return -ENODEV;

                }

Reason: We always get “func->num” value as “1” and we think that it is the sdio port number being passed from the kernel

 

With the above changes, the “wl1271_probe()” is successfully  returns.

 

Now, we have an issue with loading the wl12xx.ko as “wl12xx_probe()” function is not called. However, we have observed that “wl12xx_init()” is being called upon loading “wl12xx.ko”.

We think that related platform device is not registered in the kernel. We are trying to register a “wl1271” platform device.

Let us your comments/suggestions on the same.

Regards,

Ravi

Report Abuse
  • Reply
You have posted to a forum that requires a moderator to approve posts before they are publicly available.
All Replies
  • Eyal a
    Posted by Eyal a
    on Feb 15 2012 15:52 PM
    Genius9240 points

    Hi Ravi,

    we will try to get you more information, however meanwhile please refer to the following wiki pages:

    http://processors.wiki.ti.com/index.php/OMAP_Wireless_Connectivity_Hardware_Porting_for_new_Platform

    http://processors.wiki.ti.com/index.php/OMAP_Wireless_Connectivity_Hardware_Porting_for_AM37x_Platform

    http://processors.wiki.ti.com/index.php/OMAP_Wireless_Connectivity_WL12xx_Driver_Architecture

    Regards,

    Eyal

    Report Abuse
    • Reply
    You have posted to a forum that requires a moderator to approve posts before they are publicly available.
  • Eyal Reizer
    Posted by Eyal Reizer
    on Feb 16 2012 00:46 AM
    Intellectual1165 points

    Ravi,

    There is no change needed inside the wl12xx driver code.

    I believe that what is happening here is that the WLAN module is not being detected by the kernel sdio driver when the system boots up.

    Please make sure that during the kernel boot up process you see something like the below print:

    [    2.179005] mmc1: card claims to support voltages below the defined range. These will be ignored.
    [    2.199102] mmc1: queuing unknown CIS tuple 0x91 (3 bytes)
    [    2.206182] mmc1: new SDIO card at address 0001

    This should come up anyway, even if you dont load the compat-wireless modules.

    If that doesn't show up then either the SDIO bus pins are not muxed correctly, or the Enable pin is not set.

     

    Please refer to the following link and make sure that you have followed all the steps mentioned there

    http://processors.wiki.ti.com/index.php/OMAP_Wireless_Connectivity_Hardware_Porting_for_new_Platform

     

    Best Regards,

    Eyal Reizer

    Report Abuse
    • Reply
    You have posted to a forum that requires a moderator to approve posts before they are publicly available.
  • Eyal Reizer
    Posted by Eyal Reizer
    on Feb 16 2012 00:46 AM
    Intellectual1165 points

    Ravi,

    There is no change needed inside the wl12xx driver code.

    I believe that what is happening here is that the WLAN module is not being detected by the kernel sdio driver when the system boots up.

    Please make sure that during the kernel boot up process you see something like the below print:

    [    2.179005] mmc1: card claims to support voltages below the defined range. These will be ignored.
    [    2.199102] mmc1: queuing unknown CIS tuple 0x91 (3 bytes)
    [    2.206182] mmc1: new SDIO card at address 0001

    This should come up anyway, even if you dont load the compat-wireless modules.

    If that doesn't show up then either the SDIO bus pins are not muxed correctly, or the Enable pin is not set.

     

    Please refer to the following link and make sure that you have followed all the steps mentioned there

    http://processors.wiki.ti.com/index.php/OMAP_Wireless_Connectivity_Hardware_Porting_for_new_Platform

     

    Best Regards,

    Eyal Reizer

    Report Abuse
    • Reply
    You have posted to a forum that requires a moderator to approve posts before they are publicly available.
  • Ravi Chobey
    Posted by Ravi Chobey
    on Feb 16 2012 04:05 AM
    Prodigy50 points

    Hi Eyal,

    Thanks for your replies.

    In fact, i was also referring the OMAP pointers to get my work done.

    I am able to probe the chip, but i am facing problems in loading the firmware files.

    Please share your experience with me.

    Regards,

    Ravi

     

    Report Abuse
    • Reply
    You have posted to a forum that requires a moderator to approve posts before they are publicly available.
  • Eyal Reizer
    Posted by Eyal Reizer
    on Feb 16 2012 04:11 AM
    Intellectual1165 points

    Hi Ravi,

     

    Can you please post the console logs showing the errors when loading the firmware?

     

    Best Regards,

    Eyal Reizer

    Report Abuse
    • Reply
    You have posted to a forum that requires a moderator to approve posts before they are publicly available.
  • Hui Yang
    Posted by Hui Yang
    on Jul 26 2012 19:39 PM
    Prodigy210 points

    Hello Eyal:

               We also meet the same problem, wl1271_probe can't be work, and there is no log about mmc2, out platform is DRA64x, we use the third MMC(mmc2) to connect WL1271. The following log is more detail:

          The Wifi enable pin is always high from the system power up, our project doesn't plan to control wifi enable pin, when the system power up, the enable pin is high; Does this affect the wl1271_probe;

         
       The fact is  the EVM board 8148 use the second MMC,we use the third MMC, we don't know whether the third MMC can work correctly.

       Thanks!


    12288.57> U-Boot 2010.06-00011-g721b56c-dirty (Jul 26 2012 - 11:42:26)
    12288.57>
    12288.57> TI8148-GP rev 2.1
    12288.57>
    12288.57> ARM clk: 800MHz
    12288.57> DDR clk: 400MHz
    12288.57>
    12288.57> I2C:   ready
    12288.57> DRAM:  512 MiB
    12288.57> NAND:  HW ECC BCH8 Selected
    12288.59> 512 MiB
    12288.59> MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
    12289.46> *** Warning - bad CRC or NAND, using default environment
    12289.46>
    12289.54>                           .:;rrr;;.                  
    12289.54>                     ,5#@@@@#####@@@@@@#2,            
    12289.54>                  ,A@@@hi;;;r5;;;;r;rrSG@@@A,         
    12289.56>                r@@#i;:;s222hG;rrsrrrrrr;ri#@@r       
    12289.56>              :@@hr:r;SG3ssrr2r;rrsrsrsrsrr;rh@@:     
    12289.56>             B@H;;rr;3Hs;rrr;sr;;rrsrsrsrsrsr;;H@B    
    12289.56>            @@s:rrs;5#;;rrrr;r#@H:;;rrsrsrsrsrr:s@@   
    12289.57>           @@;;srs&X#9;r;r;;,2@@@rrr:;;rrsrsrsrr;;@@  
    12289.57>          @@;;rrsrrs@MB#@@@@@###@@@@@@#rsrsrsrsrr;;@@ 
    12289.57>         G@r;rrsrsr;#X;SX25Ss#@@#M@#9H9rrsrsrsrsrs;r@G
    12289.59>         @9:srsrsrs;2@;:;;:.X@@@@@H::;rrsrsrsrsrsrr:3@
    12289.59>        X@;rrsrsrsrr;XAi;;:&@@#@Bs:rrsrsrsrsrsrsrsrr;@X
    12289.59>        @#;rsrsrsrsrr;r2ir@@@###::rrsrsrsrsrsrsrsrsr:@@
    12289.61>        @A:rrsrsrsrr;:2@29@@M@@@;:;rrrrsrsrsrsrsrsrs;H@
    12289.61>        @&;rsrsrsrr;A@@@@@@###@@@s::;:;;rrsrsrsrsrsr;G@
    12289.61>        @#:rrsrsrsr;G@5Hr25@@@#@@@#9XG9s:rrrrsrsrsrs:#@
    12289.62>        M@;rsrsrsrs;r@&#;::S@@@@@@@M@@@@Grr:;rsrsrsr;@#
    12289.62>        :@s;rsrsrsrr:M#Msrr;;&#@@@@@@@@@@H@@5;rsrsr;s@,
    12289.62>         @@:rrsrsrsr;S@rrrsr;:;r3MH@@#@M5,S@@irrsrr:@@
    12289.64>          @A:rrsrsrsrrrrrsrsrrr;::;@##@r:;rH@h;srr:H@ 
    12289.64>          ;@9:rrsrsrsrrrsrsrsrsr;,S@Hi@i:;s;MX;rr:h@; 
    12289.64>           r@B:rrrrsrsrsrsrsrr;;sA@#i,i@h;r;S5;r:H@r  
    12289.64>            ,@@r;rrrsrsrsrsrr;2BM3r:;r:G@:rrr;;r@@,   
    12289.65>              B@Mr;rrrrsrsrsr@@S;;;rrr:5M;rr;rM@H     
    12289.65>               .@@@i;;rrrrsrs2i;rrrrr;r@M:;i@@@.      
    12289.65>                 .A@@#5r;;;r;;;rrr;r:r#AsM@@H.        
    12289.67>                    ;&@@@@MhXS5i5SX9B@@@@G;           
    12289.67>                        :ihM#@@@@@##hs,               
    12289.67>
    12289.67> Net:   <ethaddr> not set. Reading from E-fuse
    12289.68> Detected MACID:50:56:63:9d:6e:5a
    12289.70> cpsw
    12290.70> Hit any key to stop autoboot:  1 0
    12291.00> reading boot.scr
    12291.00>
    12291.00> 338 bytes read
    12291.01> Running bootscript from MMC/SD to set the ENV...
    12291.01> ## Executing script at 80900000
    12292.31> reading uImage
    12293.75>
    12293.75> 2664672 bytes read
    12293.76> ## Booting kernel from Legacy Image at 80009000 ...
    12293.76>    Image Name:   Linux-2.6.37
    12293.76>    Image Type:   ARM Linux Kernel Image (uncompressed)
    12293.78>    Data Size:    2664608 Bytes = 2.5 MiB
    12293.78>    Load Address: 80008000
    12293.78>    Entry Point:  80008000
    12295.14>    Loading Kernel Image ... OK
    12295.14> OK
    12295.14>
    12295.15> Starting kernel ...
    12295.15>
    12295.15> cache_disable
    12295.15> cache_disable
    12295.56> Uncompressing Linux... done, booting the kernel.
    12295.59> Linux version 2.6.37 (root@ubuntu) (gcc version 4.3.3 (Sourcery G++ Lite 2009q1-203) ) #3 Thu Jul 26 20:09:20 HKT 2012
    12295.61> CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7f
    12295.61> CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache
    12295.61> Machine: dra6xx
    12295.61> bootconsole [earlycon0] enabled
    12295.62> vram size = 52428800 at 0x0
    12295.62> reserved size = 52428800 at 0x0
    12295.62> FB: Reserving 52428800 bytes SDRAM for VRAM
    12295.62> Memory policy: ECC disabled, Data cache writeback
    12295.64> OMAP chip is TI8148 2.0
    12295.64> SRAM: Mapped pa 0x402f1000 to va 0xfe400000 size: 0xf000
    12295.65> Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 31904
    12295.67> Kernel command line: console=ttyO0,115200n8 mem=176M earlyprintk root=/dev/mmcblk1p2 rootfstype=ext3 rootwait rw noinitrd notifyk.vpssm3_sva=0xBF900000 vram=50M ti814xfb.vram=0:16M,1:16M,2:6M ip=off
    12295.68> PID hash table entries: 512 (order: -1, 2048 bytes)
    12295.68> Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
    12295.68> Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
    12295.70> Memory: 126MB = 126MB total
    12295.71> Memory: 121804k/121804k available, 58420k reserved, 0K highmem
    12295.71> Virtual kernel memory layout:
    12295.71>     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    12295.71>     fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
    12295.73>     DMA     : 0xffc00000 - 0xffe00000   (   2 MB)
    12295.73>     vmalloc : 0xcb800000 - 0xf8000000   ( 712 MB)
    12295.73>     lowmem  : 0xc0000000 - 0xcb000000   ( 176 MB)
    12295.73>     pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
    12295.75>     modules : 0xbf000000 - 0xbfe00000   (  14 MB)
    12295.75>       .init : 0xc0008000 - 0xc003a000   ( 200 kB)
    12295.75>       .text : 0xc003a000 - 0xc0508000   (4920 kB)
    12295.76>       .data : 0xc0508000 - 0xc054ef40   ( 284 kB)
    12295.76> SLUB: Genslabs=11, HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
    12295.76> NR_IRQS:407
    12295.78> IRQ: Found an INTC at 0xfa200000 (revision 5.0) with 128 interrupts
    12295.78> Total of 128 interrupts on 1 active controller
    12295.78> GPMC revision 6.0
    12295.78> Trying to install interrupt handler for IRQ400
    12295.79> Trying to install interrupt handler for IRQ401
    12295.79> Trying to install interrupt handler for IRQ402
    12295.79> Trying to install interrupt handler for IRQ403
    12295.79> Trying to install interrupt handler for IRQ404
    12295.81> Trying to install interrupt handler for IRQ405
    12295.81> Trying to install interrupt handler for IRQ406
    12295.81> Trying to install type control for IRQ407
    12295.82> Trying to set irq flags for IRQ407
    12295.82> OMAP clockevent source: GPTIMER1 at 20000000 Hz
    12295.82> Console: colour dummy device 80x30
    12296.06> Calibrating delay loop... 799.53 BogoMIPS (lpj=3997696)
    12296.06> pid_max: default: 32768 minimum: 301
    12296.06> Security Framework initialized
    12296.06> Mount-cache hash table entries: 512
    12296.07> CPU: Testing write buffer coherency: ok
    12296.07> devtmpfs: initialized
    12296.07> omap_voltage_early_init: voltage driver support not added
    12296.09> regulator: core version 0.5
    12296.09> regulator: dummy:
    12296.09> NET: Registered protocol family 16
    12296.09> omap_voltage_domain_lookup: Voltage driver init not yet happened.Faulting!
    12296.11> omap_voltage_add_dev: VDD specified does not exist!
    12296.11> OMAP GPIO hardware version 0.1
    12296.11> OMAP GPIO hardware version 0.1
    12296.11> OMAP GPIO hardware version 0.1
    12296.11> OMAP GPIO hardware version 0.1
    12296.12> omap_mux_init: Add partition: #1: core, flags: 4
    12296.12> omap2_i2c_mux_pins on board-dra6xx.c
    12296.12> omap2_i2c_mux_pins on board-dra6xx.c
    12296.14> omap2_i2c_mux_pins on board-dra6xx.c
    12296.14> nr_hsmmc 3
    12296.14> GPIO_NAV2BT_PWR_EN to 1
    12296.14> wl12xx_set_platform_data_yh
    12296.14> NAV2TFT_PWR_EN
    12296.15> Debugfs: Only enabling/disabling deep sleep and wakeup timer is supported now
    12296.15> registered ti81xx_vpss device
    12296.15> registered ti81xx_vidout device
    12296.15> registered ti81xx on-chip HDMI device
    12296.17> registered ti81xx_fb device
    12296.17> registered ti81xx_vin device
    12296.17> bio: create slab <bio-0> at 0
    12296.18> vgaarb: loaded
    12296.18> SCSI subsystem initialized
    12296.18> usbcore: registered new interface driver usbfs
    12296.18> usbcore: registered new interface driver hub
    12296.20> usbcore: registered new device driver usb
    12296.20> USBSS revision 4ea2080b
    12296.20> registerd cppi-dma Intr @ IRQ 17
    12296.20> Cppi41 Init Done
    12296.20> omap_i2c omap_i2c.1: bus 1 rev4.0 at 100 kHz
    12296.23> omap_i2c omap_i2c.2: bus 2 rev4.0 at 100 kHz
    12296.25> omap_i2c omap_i2c.3: bus 3 rev4.0 at 100 kHz
    12296.25> Advanced Linux Sound Architecture Driver Version 1.0.23.
    12296.26> Bluetooth: Core ver 2.15
    12296.26> NET: Registered protocol family 31
    12296.26> Bluetooth: HCI device and connection manager initialized
    12296.26> Bluetooth: HCI socket layer initialized
    12296.28> Switching to clocksource gp timer
    12296.28> musb-hdrc: version 6.0, host, debug=0
    12296.29> musb-hdrc musb-hdrc.0: dma type: dma-cppi41
    12296.29> MUSB controller-0 revision 4ea20800
    12296.29> musb-hdrc musb-hdrc.0: MUSB HDRC host driver
    12296.31> musb-hdrc musb-hdrc.0: new USB bus registered, assigned bus number 1
    12296.31> usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
    12296.31> usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
    12296.32> usb usb1: Product: MUSB HDRC host driver
    12296.32> usb usb1: Manufacturer: Linux 2.6.37 musb-hcd
    12296.32> usb usb1: SerialNumber: musb-hdrc.0
    12296.32> hub 1-0:1.0: USB hub found
    12296.34> hub 1-0:1.0: 1 port detected
    12296.34> musb-hdrc musb-hdrc.0: USB Host mode controller at cb81e000 using DMA, IRQ 18
    12296.34> musb-hdrc musb-hdrc.1: dma type: dma-cppi41
    12296.36> MUSB controller-1 revision 4ea20800
    12296.36> musb-hdrc musb-hdrc.1: MUSB HDRC host driver
    12296.36> musb-hdrc musb-hdrc.1: new USB bus registered, assigned bus number 2
    12296.37> usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
    12296.37> usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
    12296.37> usb usb2: Product: MUSB HDRC host driver
    12296.39> usb usb2: Manufacturer: Linux 2.6.37 musb-hcd
    12296.39> usb usb2: SerialNumber: musb-hdrc.1
    12296.39> hub 2-0:1.0: USB hub found
    12296.39> hub 2-0:1.0: 1 port detected
    12296.40> musb-hdrc musb-hdrc.1: USB Host mode controller at cb828800 using DMA, IRQ 19
    12296.40> NET: Registered protocol family 2
    12296.40> IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
    12296.42> TCP established hash table entries: 4096 (order: 3, 32768 bytes)
    12296.42> TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
    12296.42> TCP: Hash tables configured (established 4096 bind 4096)
    12296.42> TCP reno registered
    12296.43> UDP hash table entries: 256 (order: 0, 4096 bytes)
    12296.43> UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
    12296.43> NET: Registered protocol family 1
    12296.45> RPC: Registered udp transport module.
    12296.45> RPC: Registered tcp transport module.
    12296.45> RPC: Registered tcp NFSv4.1 backchannel transport module.
    12296.45> NetWinder Floating Point Emulator V0.97 (double precision)
    12296.46> PMU: registered new PMU device of type 0
    12296.46> omap-iommu omap-iommu.0: ducati registered
    12296.46> omap-iommu omap-iommu.1: sys registered
    12296.57> JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
    12296.59> msgmni has been set to 237
    12296.59> io scheduler noop registered
    12296.59> io scheduler deadline registered
    12296.59> io scheduler cfq registered (default)
    12296.61> Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
    12296.61> omap_uart.0: ttyO0 at MMIO 0x48020000 (irq = 72) is a OMAP UART0
    12296.61> console [ttyO0] enabled, bootconsole disabled
    12296.62> console [ttyO0] enabled, bootconsole disabled
    12296.62> omap_uart.1: ttyO1 at MMIO 0x48022000 (irq = 73) is a OMAP UART1
    12296.62> omap_uart.2: ttyO2 at MMIO 0x48024000 (irq = 74) is a OMAP UART2
    12296.64> omap_uart.3: ttyO3 at MMIO 0x481a6000 (irq = 44) is a OMAP UART3
    12296.64> omap_uart.4: ttyO4 at MMIO 0x481a8000 (irq = 45) is a OMAP UART4
    12296.65> omap_uart.5: ttyO5 at MMIO 0x481aa000 (irq = 46) is a OMAP UART5
    12296.65> brd: module loaded
    12296.65> loop: module loaded
    12296.67> m25p80 spi1.0: m25p40 (512 Kbytes)
    12296.67> Creating 2 MTD partitions on "spi_flash":
    12296.67> 0x000000000000-0x000000020000 : "MLO_SPI"
    12296.67> 0x000000020000-0x000000080000 : "Reserved"
    12296.68> omap2-nand driver initializing
    12296.68> NAND device: Manufacturer ID: 0x2c, Chip ID: 0xcc (Micron )
    12296.68> Creating 7 MTD partitions on "omap2-nand.0":
    12296.70> 0x000000000000-0x000000080000 : "MLO"
    12296.70> 0x000000080000-0x000000200000 : "IPL"
    12296.70> 0x000000200000-0x000000400000 : "Logo"
    12296.70> 0x000000400000-0x000000800000 : "kernel"
    12296.71> 0x000000800000-0x000001000000 : "ramdisk"
    12296.71> 0x000001000000-0x00000d000000 : "rootfs"
    12296.81> 0x00000d000000-0x000020000000 : "Reserved"
    12296.93> mcu_spi_init
    12296.93> mcu_spi_probe
    12296.98> davinci_mdio davinci_mdio.0: davinci mdio revision 1.6
    12297.00> davinci_mdio davinci_mdio.0: detected phy mask 0
    12297.01> davinci_mdio.0: probed
    12297.03> davinci_mdio davinci_mdio.0: phy[0]: device 0:00, driver unknown
    12297.03> davinci_mdio davinci_mdio.0: phy[1]: device 0:01, driver unknown
    12297.03> davinci_mdio davinci_mdio.0: phy[2]: device 0:02, driver unknown
    12297.04> davinci_mdio davinci_mdio.0: phy[3]: device 0:03, driver unknown
    12297.04> davinci_mdio davinci_mdio.0: phy[4]: device 0:04, driver unknown
    12297.04> davinci_mdio davinci_mdio.0: phy[5]: device 0:05, driver unknown
    12297.06> davinci_mdio davinci_mdio.0: phy[6]: device 0:06, driver unknown
    12297.06> davinci_mdio davinci_mdio.0: phy[7]: device 0:07, driver unknown
    12297.07> davinci_mdio davinci_mdio.0: phy[8]: device 0:08, driver unknown
    12297.07> davinci_mdio davinci_mdio.0: phy[9]: device 0:09, driver unknown
    12297.07> davinci_mdio davinci_mdio.0: phy[10]: device 0:0a, driver unknown
    12297.09> davinci_mdio davinci_mdio.0: phy[11]: device 0:0b, driver unknown
    12297.09> davinci_mdio davinci_mdio.0: phy[12]: device 0:0c, driver unknown
    12297.11> davinci_mdio davinci_mdio.0: phy[13]: device 0:0d, driver unknown
    12297.11> davinci_mdio davinci_mdio.0: phy[14]: device 0:0e, driver unknown
    12297.11> davinci_mdio davinci_mdio.0: phy[15]: device 0:0f, driver unknown
    12297.12> davinci_mdio davinci_mdio.0: phy[16]: device 0:10, driver unknown
    12297.12> davinci_mdio davinci_mdio.0: phy[17]: device 0:11, driver unknown
    12297.12> davinci_mdio davinci_mdio.0: phy[18]: device 0:12, driver unknown
    12297.14> davinci_mdio davinci_mdio.0: phy[19]: device 0:13, driver unknown
    12297.14> davinci_mdio davinci_mdio.0: phy[20]: device 0:14, driver unknown
    12297.15> davinci_mdio davinci_mdio.0: phy[21]: device 0:15, driver unknown
    12297.15> davinci_mdio davinci_mdio.0: phy[22]: device 0:16, driver unknown
    12297.15> davinci_mdio davinci_mdio.0: phy[23]: device 0:17, driver unknown
    12297.17> davinci_mdio davinci_mdio.0: phy[24]: device 0:18, driver unknown
    12297.17> davinci_mdio davinci_mdio.0: phy[25]: device 0:19, driver unknown
    12297.18> davinci_mdio davinci_mdio.0: phy[26]: device 0:1a, driver unknown
    12297.18> davinci_mdio davinci_mdio.0: phy[27]: device 0:1b, driver unknown
    12297.18> davinci_mdio davinci_mdio.0: phy[28]: device 0:1c, driver unknown
    12297.20> davinci_mdio davinci_mdio.0: phy[29]: device 0:1d, driver unknown
    12297.20> davinci_mdio davinci_mdio.0: phy[30]: device 0:1e, driver unknown
    12297.21> davinci_mdio davinci_mdio.0: phy[31]: device 0:1f, driver unknown
    12297.21> usbcore: registered new interface driver cdc_ether
    12297.21> usbcore: registered new interface driver dm9601
    12297.21> usbcore: registered new interface driver cdc_acm
    12297.23> cdc_acm: v0.26:USB Abstract Control Model driver for USB modems and ISDN adapters
    12297.23> Initializing USB Mass Storage driver...
    12297.23> usbcore: registered new interface driver usb-storage
    12297.25> USB Mass Storage support registered.
    12297.25> mice: PS/2 mouse device common for all mice
    12297.25> input: TSC2007 Touchscreen as /devices/virtual/input/input0
    12297.26> omap_rtc omap_rtc: rtc core: registered omap_rtc as rtc0
    12297.26> i2c /dev entries driver
    12297.26> Linux video capture interface: v2.00
    12297.28> usbcore: registered new interface driver uvcvideo
    12297.28> USB Video Class driver (v1.0.0)
    12297.28> OMAP Watchdog Timer Rev 0x00: initial timeout 60 sec
    12297.28> Bluetooth: HCI UART driver ver 2.2
    12297.29> Bluetooth: HCI H4 protocol initialized
    12297.29> Bluetooth: HCI BCSP protocol initialized
    12297.29> Bluetooth: HCILL protocol initialized
    12297.29> mmci-omap-hs: probe of mmci-omap-hs.2 failed with error -16
    12297.31> usbcore: registered new interface driver usbhid
    12297.31> usbhid: USB HID core driver
    12297.31> notify_init : notify drivercreated  for  remote proc id 2 at physical Address 0xbf900000
    12297.32> DRA6XX tlv320aic INIT
    12297.32> asoc: dra6xx-tlv320aic-dai-codec <-> davinci-mcasp.0 mapping ok
    12297.32> UDA1334_INIT
    12297.32> asoc: uda1334-dai-codec <-> davinci-mcasp.2 mapping ok
    12297.34> ALSA device list:
    12297.34>   #0: TI8148 DRA6XX
    12297.34> TCP cubic registered
    12297.34> NET: Registered protocol family 17
    12297.34> Bluetooth: L2CAP ver 2.15
    12297.34> Bluetooth: L2CAP socket layer initialized
    12297.36> Bluetooth: SCO (Voice Link) ver 0.6
    12297.36> Bluetooth: SCO socket layer initialized
    12297.36> Bluetooth: RFCOMM TTY layer initialized
    12297.36> Bluetooth: RFCOMM socket layer initialized
    12297.37> Bluetooth: RFCOMM ver 1.11
    12297.37> Bluetooth: BNEP (Ethernet Emulation) ver 1.3
    12297.37> Bluetooth: BNEP filters: protocol multicast
    12297.37> Bluetooth: HIDP (Human Interface Emulation) ver 1.2
    12297.39> Registering the dns_resolver key type
    12297.39> VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3
    12297.40> omap_voltage_late_init: Voltage driver support not added
    12297.40> Power Management for TI81XX.
    12297.40> Detected MACID=50:56:63:9d:6e:5a
    12297.42> omap_rtc omap_rtc: setting system clock to 2000-01-01 00:00:00 UTC (946684800)
    12297.42> Waiting for root device /dev/mmcblk1p2...
    12297.62> mmc0: new high speed MMC card at address 0001
    12297.62> mmcblk0: mmc0:0001 MMC04G 3.64 GiB
    12297.62>  mmcblk0: unknown partition table
    12297.92> mmc1: new high speed SD card at address 2162
    12297.92> mmcblk1: mmc1:2162 SD01G 982 MiB
    12297.92>  mmcblk1: p1 p2
    12297.96> EXT3-fs: barriers not enabled
    12297.96> kjournald starting.  Commit interval 5 seconds
    12298.15> EXT3-fs (mmcblk1p2): using internal journal
    12298.15> EXT3-fs (mmcblk1p2): recovery complete
    12298.15> EXT3-fs (mmcblk1p2): mounted filesystem with writeback data mode
    12298.15> VFS: Mounted root (ext3 filesystem) on device 179:10.
    12298.17> devtmpfs: mounted
    12298.17> Freeing init memory: 200K
    12298.31> INIT: version 2.86 booting
    12298.51> Error opening /dev/fb0: No such file or directory
    12298.51> Please wait: booting...
    12298.53> Starting udev
    12298.62> udevd (143): /proc/143/oom_adj is deprecated, please use /proc/143/oom_score_adj instead.
    12301.53> FAT: bogus number of reserved sectors
    12301.53> VFS: Can't find a valid FAT filesystem on dev mmcblk0.
    12302.03> Remounting root file system...
    12305.14> Caching udev devnodes
    12305.46> Configuring network interfaces...
    12305.48> CPSW phy found : id is : 0x0
    12305.48>
    12305.48> CPSW phy found : id is : 0x0
    12305.50> udhcpc (v1.13.2) started
    12305.54> Sending discover...
    12307.46> PHY: 0:01 - Link is Up - 0/Half
    12307.48> PHY: 0:01 - Link is Down
    12308.54> Sending discover...
    12311.54> Sending discover...
    12314.56> No lease, forking to background
    12314.56> done.
    12314.57> Setting up IP spoofing protection: rp_filter.
    12314.64> Thu Jun  7 11:29:00 UTC 2012
    12314.65> INIT: Entering runlevel: 5
    12314.67> Loading HDVICP2 Firmware
    12314.68> DM814X prcm_config_app version: 2.0.0.1
    12314.68> Doing PRCM settings...
    12314.70>  PRCM for IVHD0 is in Progress, Please wait..... 
    12314.70>    BW Phy Addr : 0x48180600 Data : 0x00000001
    12314.70>    AW Phy Addr : 0x48180600 Data : 0x00000002
    12314.71>    Phy Addr : 0x48180c04 Data : 0x00000037
    12314.71>    BW Phy Addr : 0x48180620 Data : 0x00070000
    12314.71>    AW Phy Addr : 0x48180620 Data : 0x00070002
    12314.71>    BW Phy Addr : 0x48180624 Data : 0x00030000
    12314.73>    AW Phy Addr : 0x48180624 Data : 0x00010002
    12314.73>    Phy Addr : 0x48180600 Data : 0x00000102
    12314.73>    BW Phy Addr : 0x48180c10 Data : 0x00000007
    12314.73>    AW Phy Addr : 0x48180c10 Data : 0x00000003
    12314.75>    Phy Addr : 0x48180c14 Data : 0x00000004
    12314.75>    BW Phy Addr : 0x58088000 Data : 0x4d9b63e0
    12314.75>    AW Phy Addr : 0x58088000 Data : 0xeafffffe
    12314.75>    BW Phy Addr : 0x58098000 Data : 0xf008ed2b
    12314.76>    AW Phy Addr : 0x58098000 Data : 0xeafffffe
    12314.76>    BW Phy Addr : 0x48180c10 Data : 0x00000003
    12314.76>    AW Phy Addr : 0x48180c10 Data : 0x00000000
    12314.76>    Phy Addr : 0x48180c14 Data : 0x00000007
    12314.78>  PRCM for IVHD0 is Done Successfully 
    12314.78> PRCM Initialization completed
    12315.07> SysLink version : 2.10.03.20
    12315.07> SysLink module created on Date:Jul 26 2012 Time:18:08:45
    12315.26> FIRMWARE: I2cInit will be done by M3
    12315.26> FIRMWARE: Memory map bin file not passed
    12315.28> Usage : firmware_loader <Processor Id> <Location of Firmware> <start|stop> [-mmap <memory_map_file>] [-i2c <0|1>]
    12315.28> ===Mandatory arguments===
    12315.28> <Processor Id>         0: DSP, 1: Video-M3, 2: Vpss-M3
    12315.29> <Location of Firmware> firmware binary file
    12315.29> <start|stop>           to start/stop the firmware
    12315.29> ===Optional arguments===
    12315.29> -mmap                  input memory map bin file name
    12315.31> -i2c                   0: i2c init not done by M3, 1(default): i2c init done by M3
    12315.31> FIRMWARE: isI2cInitRequiredOnM3: 1
    12315.31> FIRMWARE: Default memory configuration is used
    12315.32> MemCfg: DCMM (Dynamically Configurable Memory Map) Version :  2.1.2.1
    12316.01> FIRMWARE: Memory Configuration status : In Progress
    12316.01> FIRMWARE: 1 start Successful
    12316.01> Loading HDVPSS Firmware
    12316.01> FIRMWARE: I2cInit will be done by M3
    12316.03> FIRMWARE: Memory map bin file not passed
    12316.03> Usage : firmware_loader <Processor Id> <Location of Firmware> <start|stop> [-mmap <memory_map_file>] [-i2c <0|1>]
    12316.03> ===Mandatory arguments===
    12316.04> <Processor Id>         0: DSP, 1: Video-M3, 2: Vpss-M3
    12316.04> <Location of Firmware> firmware binary file
    12316.04> <start|stop>           to start/stop the firmware
    12316.04> ===Optional arguments===
    12316.06> -mmap                  input memory map bin file name
    12316.06> -i2c                   0: i2c init not done by M3, 1(default): i2c init done by M3
    12316.06> FIRMWARE: isI2cInitRequiredOnM3: 1
    12316.07> FIRMWARE: Default memory configuration is used
    12316.07> MemCfg: DCMM (Dynamically Configurable Memory Map) Version :  2.1.2.1
    12317.00> FIRMWARE: Memory Configuration status : In Progress
    12317.00> FIRMWARE: 2 start Successful
    12317.07> Configuring fb0 to LCD
    12317.31> Starting system message bus: dbus.
    12317.34> Starting telnet daemon.
    12317.37> Starting syslogd/klogd: done
    12317.51> NET: Registered protocol family 10
    12317.51> ADDRCONF(NETDEV_UP): eth0: link is not ready
    12318.07> Starting PVR
    12318.43> /dev/mem opened.
    12318.43> Memory mapped at address 0x402c2000.
    12318.45> Read at address  0x48180F04 (0x402c2f04): 0x00000001
    12318.45> Write at address 0x48180F04 (0x402c2f04): 0x00000000, readback 0x00000000
    12318.45> /dev/mem opened.
    12318.45> Memory mapped at address 0x40240000.
    12318.46> Read at address  0x48180900 (0x40240900): 0x00000102
    12318.46> Write at address 0x48180900 (0x40240900): 0x00000002, readback 0x00000002
    12318.46> /dev/mem opened.
    12318.48> Memory mapped at address 0x4008e000.
    12318.48> Read at address  0x48180920 (0x4008e920): 0x00040002
    12318.48> Write at address 0x48180920 (0x4008e920): 0x00000002, readback 0x00000002
    12319.48> Starting GUI application.
    12320.53>
    12320.54>  _____                    _____           _         _  
    12320.56> |  _  |___ ___ ___ ___   |  _  |___ ___  |_|___ ___| |_
    12320.56> |     |  _| .'| . | . |  |   __|  _| . | | | -_|  _|  _|
    12320.56> |__|__|_| |__,|_  |___|  |__|  |_| |___|_| |___|___|_| 
    12320.57>               |___|                    |___|           
    12320.57>
    12320.57> Arago Project http://arago-project.org dm814x-evm ttyO0
    12320.57>
    12320.57> Arago 2011.09 dm814x-evm ttyO0

     

    Report Abuse
    • Reply
    You have posted to a forum that requires a moderator to approve posts before they are publicly available.
  • Eyal Reizer
    Posted by Eyal Reizer
    on Jul 29 2012 23:38 PM
    Intellectual1165 points

    hi,

    i do not see in the log that the sdio module is being detected. did you add another entry for mmc2 into the mmc[] structure for wl12xxin addition you would need to be able to control the wlan enable pin as it is being used for resetting the chip on down/up of the interface and on firmware mode changes in case of recovery or even for perfeorming calibration.

    best regards,

    gards

    ey

    Report Abuse
    • Reply
    You have posted to a forum that requires a moderator to approve posts before they are publicly available.
  • Hui Yang
    Posted by Hui Yang
    on Aug 03 2012 00:48 AM
    Prodigy210 points

     

    Hello

            The wlan0 has no HWaddr ,I don't known why.

    8729.60> ifconfig -a
     8729.62> eth0      Link encap:Ethernet  HWaddr 50:56:63:9D:6E:5A 
     8729.62>      omap_hsmmc_context_restore
     8729.62>      UP BROADCAST ALLMULTI MULTICAST  MTU:1500  Metric:1
     8729.64>           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
     8729.64>           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
     8729.64>           collisions:0 txqueuelen:1000
     8729.64>           RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
     8729.65>           Interrupt:40
     8729.65>
     8729.65> lo        Link encap:Local Loopback 
     8729.65>           inet addr:127.0.0.1  Mask:255.0.0.0
     8729.65>           inet6 addr: ::1/128 Scope:Host
     8729.67>           UP LOOPBACK RUNNING  MTU:16436  Metric:1
     8729.67>           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
     8729.67>           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
     8729.68>           collisions:0 txqueuelen:0
     8729.68>           RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
     8729.68>
     8729.68> wlan0     Link encap:Ethernet  HWaddr 00:00:00:00:00:00 
     8729.68>           BROADCAST MULTICAST  MTU:1500  Metric:1
     8729.70>           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
     8729.70>           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
     8729.70>           collisions:0 txqueuelen:1000
     8729.71>           RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

     

     

     

     

     

     

     

     

     

     

    Report Abuse
    • Reply
    You have posted to a forum that requires a moderator to approve posts before they are publicly available.
  • Hui Yang
    Posted by Hui Yang
    on Aug 03 2012 01:51 AM
    Prodigy210 points

     

    This is the whole log.

     

    3376.04> mmc2: mmc_rescan: trying to init card at 400000 Hz
     3376.04> mmc_power_up
     3376.04> host->ocr 0
     3376.04> host->avail 128
     3376.04> host->ios.vdd 7
     3376.04> mmc_power_up
     3376.04> mmc2: clock 0Hz busmode 1 powermode 1 cs 0 Vdd 7 width 0 timing 0
     3376.06> omap_hsmmc_set_ios
     3376.06> MMC_POWER_UP
     3376.06> wl12xx_set_power
     3376.07> Powering on wl12xx
     3376.07> EXT3-fs: barriers not enabled
     3376.15> host->vdd7
     3376.17> mmc_power_on
     3376.18> mmc2: clock 400000Hz busmode 1 powermode 2 cs 0 Vdd 7 width 0 timing 0
     3376.18> omap_hsmmc_set_ios
     3376.18> MMC_POWER_ON
     3376.20> mmc2: clock 400000Hz busmode 1 powermode 2 cs 1 Vdd 7 width 0 timing 0
     3376.21> omap_hsmmc_set_ios
     3376.21> mmc2: clock 400000Hz busmode 1 powermode 2 cs 0 Vdd 7 width 0 timing 0
     3376.21> omap_hsmmc_set_ios
     3376.23> host->ocr_avail:128
     3376.23> ocr:2701131712
     3376.23>  before mmc_attach_sdio
     3376.23>  mmc_attach_sdio
     3376.23> mmc2: card claims to support voltages below the defined range. These will be ignored.
     3376.25> mmc_select_voltage ocr:a0ffff80
     3376.25> mmc_select_voltage
     3376.25> OCR (2701131648)
     3376.25> OCR in mmc_select_voltage(128)
     3376.25> host->ocr_avail in mmc_select_voltage (128)
     3376.26> bit in mmc_select_voltage(8)
     3376.26> host->ios.vdd in mmc_select_voltage(7)
     3376.26> mmc2: clock 400000Hz busmode 1 powermode 2 cs 0 Vdd 7 width 0 timing 0
     3376.26> omap_hsmmc_set_ios
     3376.26> mmc_select_voltage host->ocr:80
     3376.28> mmc_sdio_init_card
     3376.28> mmc2: clock 400000Hz busmode 2 powermode 2 cs 0 Vdd 7 width 0 timing 0
     3376.28> omap_hsmmc_set_ios
     3376.29> mmc2: clock 25000000Hz busmode 2 powermode 2 cs 0 Vdd 7 width 0 timing 0
     3376.29> omap_hsmmc_set_ios
     3376.31> mmc2: clock 25000000Hz busmode 2 powermode 2 cs 0 Vdd 7 width 2 timing 0
     3376.31> omap_hsmmc_set_ios
     3376.31> pm_runtime_set_active
     3376.31> mmc2: queuing unknown CIS tuple 0x91 (3 bytes)
     3376.32> mmc2: new SDIO card at address 0001
     3376.32> mmc_power_off
     3376.32> mmc2: clock 0Hz busmode 1 powermode 0 cs 0 Vdd 0 width 0 timing 0
     3376.34> omap_hsmmc_set_ios
     3376.34> MMC_POWER_OFF
     3376.34> wl12xx_set_power
     3376.34> Powering off wl12xx
     3376.34> mmc_power_up
     3376.34> host->ocr 128
     3376.34> host->avail 128
     3376.34> host->ios.vdd 7
     3376.34> mmc_power_up
     3376.36> mmc2: clock 0Hz busmode 1 powermode 1 cs 0 Vdd 7 width 0 timing 0
     3376.36> omap_hsmmc_set_ios
     3376.36> MMC_POWER_UP
     3376.36> wl12xx_set_power
     3376.36> Powering on wl12xx
     3376.45> host->vdd7
     3376.46> mmc_power_on
     3376.48> mmc2: clock 400000Hz busmode 1 powermode 2 cs 0 Vdd 7 width 0 timing 0
     3376.48> omap_hsmmc_set_ios
     3376.48> MMC_POWER_ON
     3376.50> mmc_sdio_init_card
     3376.51> mmc2: clock 400000Hz busmode 2 powermode 2 cs 0 Vdd 7 width 0 timing 0
     3376.51> omap_hsmmc_set_ios
     3376.53> mmc2: clock 25000000Hz busmode 2 powermode 2 cs 0 Vdd 7 width 0 timing 0
     3376.53> omap_hsmmc_set_ios
     3376.54> mmc2: clock 25000000Hz busmode 2 powermode 2 cs 0 Vdd 7 width 2 timing 0
     3376.54> omap_hsmmc_set_ios
     3376.54> wl1271_probe
     3376.56> wl1271_probe
     3376.56> wl1271_alloc_hw()
     3376.56> wl1271_alloc_hw
     3376.56> wl12xx_get_platform_data
     3376.56> request_irq
     3376.56> wl1271_init_ieee80211
     3376.56> wl1271_init_ieee80211
     3376.56> wl1271_register_hw
     3376.57> wl1271_register_hw
     3376.57> wl1271_dev_notify
     3376.57> wl1271_dev_notify
     3376.57> wl1271_dev_notify
     3376.57> wl1271: loaded
     3376.57> wl1271: initialized
     3376.57> initialized
     3376.57> mmc_power_off
     3376.59> mmc2: clock 0Hz busmode 1 powermode 0 cs 0 Vdd 0 width 0 timing 0
     3376.59> omap_hsmmc_set_ios
     3376.59> MMC_POWER_OFF
     3376.59> wl12xx_set_power
     3376.59> Powering off wl12xx
     3431.73> kjournald starting.  Commit interval 5 seconds
     3431.92> EXT3-fs (mmcblk1p2): using internal journal
     3431.92> EXT3-fs (mmcblk1p2): recovery complete
     3432.09> EXT3-fs (mmcblk1p2): mounted filesystem with writeback data mode
     3432.09> VFS: Mounted root (ext3 filesystem) on device 179:10.
     3432.09> devtmpfs: mounted
     3432.09> Freeing init memory: 204K
     3432.21> INIT: version 2.86 booting
     3432.42> Please wait: booting...
     3432.43> Error opening /dev/fb0: No such file or directory
     3432.45> Starting udev
     3432.54> udevd (153): /proc/153/oom_adj is deprecated, please use /proc/153/oom_score_adj instead.
     3433.84> FAT: bogus number of reserved sectors
     3433.84> VFS: Can't find a valid FAT filesystem on dev mmcblk0.
     3436.03> Remounting root file system...
     3438.84> Caching udev devnodes
     3439.06> chown: unknown user/group haldaemon:haldaemon
     3439.34> Configuring update-modules.
     3439.36> Configuring omap3-sgx-modules.
     3439.39> Configuring hicolor-icon-theme.
     3439.68> # GdkPixbuf Image Loader Modules file
     3439.68> # Automatically generated file, do not edit
     3439.70> # Created by gdk-pixbuf-query-loaders from gtk+-2.20.1
     3439.70> #
     3439.71> g_module_open() failed for /--update-cache: /--update-cache.so: cannot open shared object file: No such file or directory
     3439.95> Configuring pango-module-basic-x.
     3440.17> Configuring pango-module-basic-fc.
     3440.37> Configuring ttf-dejavu-common.
     3440.56> Configuring ttf-dejavu-sans.
     3440.57> Configuring gdk-pixbuf-loader-png.
     3440.64> Configuring gdk-pixbuf-loader-jpeg.
     3440.82> Configuring gdk-pixbuf-loader-gif.
     3441.01> Configuring gdk-pixbuf-loader-xpm.
     3441.20> Configuring dbus.
     3441.43>  System startup links for /etc/init.d/dbus-1 already exist.
     3441.43> Configuring hal.
     3441.93> Configuring policykit.
     3442.01> Configuring gnome-keyring.
     3464.43> Configuring network interfaces... wl1271_dev_notify
     3464.43> wl1271_dev_notify
     3464.46> wl1271_dev_notify
     3464.46>
     3464.46> CPSW phy found : id is : 0x0
     3464.46>
     3464.46> CPSW phy found : id is : 0x0
     3464.48> wl1271_dev_notify
     3464.48> udhcpc (v1.13.2)wl1271_dev_notify
     3464.48>  started
     3464.53> Sending discover...
     3466.46> PHY: 0:01 - Link is Up - 0/Half
     3466.46> wl1271_dev_notify
     3466.46> PHY: 0:01 - Link is Down
     3467.45> wl1271_dev_notify
     3467.53> Sending discover...
     3470.54> Sending discover...
     3473.56> No lease, forking to background
     3473.56> done.
     3473.56> Setting up IP spoofing protection: rp_filter.
     3473.64> Thu Jun  7 11:29:00 UTC 2012
     3473.65> INIT: Entering runlevel: 5
     3473.67> Loading HDVICP2 Firmware
     3473.68> DM814X prcm_config_app version: 2.0.0.1
     3473.68> Doing PRCM settings...
     3473.68>  PRCM for IVHD0 is in Progress, Please wait..... 
     3473.70>    BW Phy Addr : 0x48180600 Data : 0x00000001
     3473.70>    AW Phy Addr : 0x48180600 Data : 0x00000002
     3473.70>    Phy Addr : 0x48180c04 Data : 0x00000037
     3473.70>    BW Phy Addr : 0x48180620 Data : 0x00070000
     3473.71>    AW Phy Addr : 0x48180620 Data : 0x00070002
     3473.71>    BW Phy Addr : 0x48180624 Data : 0x00030000
     3473.71>    AW Phy Addr : 0x48180624 Data : 0x00010002
     3473.71>    Phy Addr : 0x48180600 Data : 0x00000102
     3473.73>    BW Phy Addr : 0x48180c10 Data : 0x00000007
     3473.73>    AW Phy Addr : 0x48180c10 Data : 0x00000003
     3473.73>    Phy Addr : 0x48180c14 Data : 0x00000004
     3473.73>    BW Phy Addr : 0x58088000 Data : 0x4d1b22e0
     3473.75>    AW Phy Addr : 0x58088000 Data : 0xeafffffe
     3473.75>    BW Phy Addr : 0x58098000 Data : 0xf008ed2b
     3473.75>    AW Phy Addr : 0x58098000 Data : 0xeafffffe
     3473.75>    BW Phy Addr : 0x48180c10 Data : 0x00000003
     3473.76>    AW Phy Addr : 0x48180c10 Data : 0x00000000
     3473.76>    Phy Addr : 0x48180c14 Data : 0x00000007
     3473.76>  PRCM for IVHD0 is Done Successfully 
     3473.76> PRCM Initialization completed
     3474.01> SysLink version : 2.10.03.20
     3474.01> SysLink module created on Date:Aug  1 2012 Time:11:05:38
     3474.64> FIRMWARE: I2cInit will be done by M3
     3474.65> FIRMWARE: Memory map bin file not passed
     3474.65> Usage : firmware_loader <Processor Id> <Location of Firmware> <start|stop> [-mmap <memory_map_file>] [-i2c <0|1>]
     3474.65> ===Mandatory arguments===
     3474.67> <Processor Id>         0: DSP, 1: Video-M3, 2: Vpss-M3
     3474.67> <Location of Firmware> firmware binary file
     3474.67> <start|stop>           to start/stop the firmware
     3474.67> ===Optional arguments===
     3474.68> -mmap                  input memory map bin file name
     3474.68> -i2c                   0: i2c init not done by M3, 1(default): i2c init done by M3
     3474.68> FIRMWARE: isI2cInitRequiredOnM3: 1
     3474.70> FIRMWARE: Default memory configuration is used
     3474.70> MemCfg: DCMM (Dynamically Configurable Memory Map) Version :  2.1.2.1
     3475.39> FIRMWARE: Memory Configuration status : In Progress
     3475.39> FIRMWARE: 1 start Successful
     3475.40> Loading HDVPSS Firmware
     3475.40> FIRMWARE: I2cInit will be done by M3
     3475.40> FIRMWARE: Memory map bin file not passed
     3475.42> Usage : firmware_loader <Processor Id> <Location of Firmware> <start|stop> [-mmap <memory_map_file>] [-i2c <0|1>]
     3475.42> ===Mandatory arguments===
     3475.42> <Processor Id>         0: DSP, 1: Video-M3, 2: Vpss-M3
     3475.42> <Location of Firmware> firmware binary file
     3475.43> <start|stop>           to start/stop the firmware
     3475.43> ===Optional arguments===
     3475.43> -mmap                  input memory map bin file name
     3475.45> -i2c                   0: i2c init not done by M3, 1(default): i2c init done by M3
     3475.45> FIRMWARE: isI2cInitRequiredOnM3: 1
     3475.45> FIRMWARE: Default memory configuration is used
     3475.45> MemCfg: DCMM (Dynamically Configurable Memory Map) Version :  2.1.2.1
     3476.36> FIRMWARE: Memory Configuration status : In Progress
     3476.36> FIRMWARE: 2 start Successful
     3476.43> Configuring fb0 to LCD
     3476.64> Starting system message bus: dbus.
     3476.65> Starting telnet daemon.
     3476.78> Starting syslogd/klogd: NET: Registered protocol family 10
     3476.79> ADDRCONF(NETDEV_UP): eth0: link is not ready
     3476.82> done
     3477.43> Starting PVR
     3477.76> /dev/mem opened.
     3477.76> Memory mapped at address 0x402de000.
     3477.76> Read at address  0x48180F04 (0x402def04): 0x00000001
     3477.78> Write at address 0x48180F04 (0x402def04): 0x00000000, readback 0x00000000
     3477.78> /dev/mem opened.
     3477.78> Memory mapped at address 0x4020e000.
     3477.78> Read at address  0x48180900 (0x4020e900): 0x00000102
     3477.79> Write at address 0x48180900 (0x4020e900): 0x00000002, readback 0x00000002
     3477.79> /dev/mem opened.
     3477.79> Memory mapped at address 0x402ba000.
     3477.81> Read at address  0x48180920 (0x402ba920): 0x00040002
     3477.81> Write at address 0x48180920 (0x402ba920): 0x00000002, readback 0x00000002
     3478.95> Starting GUI application.
     3479.98>
     3480.01>  _____                    _____           _         _  
     3480.01> |  _  |___ ___ ___ ___   |  _  |___ ___  |_|___ ___| |_
     3480.03> |     |  _| .'| . | . |  |   __|  _| . | | | -_|  _|  _|
     3480.03> |__|__|_| |__,|_  |___|  |__|  |_| |___|_| |___|___|_| 
     3480.03>               |___|                    |___|           
     3480.03>
     3480.04> Arago Project http://arago-project.org dm814x-evm ttyO0
     3480.04>
     3480.04> Arago 2011.09 dm814x-evm ttyO0
     3480.04>
     3825.79< ifconfig
     3825.82> dm814x-evm login: ifconfig
     3828.79< root
     3828.79> Password:
     3831.57> Login incorrect
     3831.57>
     3837.17< root
     3837.18> login: root
     3837.18>
     3837.23> root@dm814x-evm:~#
     3845.64< ifconfig -a
     3845.65> root@dm814x-evm:~# ifconfig -a
     3845.65> eth0      Link encap:Ethernet  HWaddr 50:56:63:9D:6E:5A 
     3845.67>           UP BROADCAST ALLMULTI MULTICAST  MTU:1500  Metric:1
     3845.67>           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
     3845.68>           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
     3845.68>           collisions:0 txqueuelen:1000
     3845.68>           RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
     3845.68>           Interrupt:40
     3845.68>
     3845.68> lo        Link encap:Local Loopback 
     3845.70>           inet addr:127.0.0.1  Mask:255.0.0.0
     3845.70>           inet6 addr: ::1/128 Scope:Host
     3845.70>           UP LOOPBACK RUNNING  MTU:16436  Metric:1
     3845.71>           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
     3845.71>           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
     3845.71>           collisions:0 txqueuelen:0
     3845.71>           RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
     3845.71>
     3845.73> wlan0     Link encap:Ethernet  HWaddr 00:00:00:00:00:00 
     3845.73>           BROADCAST MULTICAST  MTU:1500  Metric:1
     3845.73>           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
     3845.75>           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
     3845.75>           collisions:0 txqueuelen:1000
     3845.75>           RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
     3845.75>
     3845.75> root@dm814x-evm:~#

    Report Abuse
    • Reply
    You have posted to a forum that requires a moderator to approve posts before they are publicly available.
  • Eyal Reizer
    Posted by Eyal Reizer
    on Aug 03 2012 02:30 AM
    Intellectual1165 points

    hi

    please try using the "calibrator set nvs-mac..." command to program a mac adress for the interface into the NVS file and see if that helps.

    best regards

    eyal reizer

    Report Abuse
    • Reply
    You have posted to a forum that requires a moderator to approve posts before they are publicly available.
  • Hui Yang
    Posted by Hui Yang
    on Aug 03 2012 02:42 AM
    Prodigy210 points

    I'll try the method you said;

    I don't know why the wl12xx power off after wl1271_probe.

     

     

    3376.56> wl1271_probe
     3376.56> wl1271_alloc_hw()
     3376.56> wl1271_alloc_hw
     3376.56> wl12xx_get_platform_data
     3376.56> request_irq
     3376.56> wl1271_init_ieee80211
     3376.56> wl1271_init_ieee80211
     3376.56> wl1271_register_hw
     3376.57> wl1271_register_hw
     3376.57> wl1271_dev_notify
     3376.57> wl1271_dev_notify
     3376.57> wl1271_dev_notify
     3376.57> wl1271: loaded
     3376.57> wl1271: initialized
     3376.57> initialized
     3376.57> mmc_power_off
     3376.59> mmc2: clock 0Hz busmode 1 powermode 0 cs 0 Vdd 0 width 0 timing 0
     3376.59> omap_hsmmc_set_ios
     3376.59> MMC_POWER_OFF
     3376.59> wl12xx_set_power
     3376.59> Powering off wl12xx

    Report Abuse
    • Reply
    You have posted to a forum that requires a moderator to approve posts before they are publicly available.
  • Eyal Reizer
    Posted by Eyal Reizer
    on Aug 03 2012 03:35 AM
    Intellectual1165 points

    hi

    this is ok. pm_runtime shut it down after first detection until the interface is brought up using ifconfig.

    best regards

    eyal reizer

    Report Abuse
    • Reply
    You have posted to a forum that requires a moderator to approve posts before they are publicly available.
  • Hui Yang
    Posted by Hui Yang
    on Aug 03 2012 03:50 AM
    Prodigy210 points

    Hello :

    After I input the command: ./calibrator set nvs_mac /lib/firmware/ti-connectivity/wl1271-nvs.bin 50:56:63:9D:6E:5B

    the HWaddr is still 00:00:00:00:00:00 

     

    221.09> root@dm814x-evm:~# ßÿifconfig -a
       21.09> eth0      Link encap:Ethernet  HWaddr 50:56:63:9D:6E:5A 
       21.10>           UP BROADCAST ALLMULTI MULTICAST  MTU:1500  Metric:1
       21.10>           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
       21.10>           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
       21.12>           collisions:0 txqueuelen:1000
       21.12>           RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
       21.12>           Interrupt:40
       21.12>
       21.12> lo        Link encap:Local Loopback 
       21.14>           inet addr:127.0.0.1  Mask:255.0.0.0
       21.14>           inet6 addr: ::1/128 Scope:Host
       21.14>           UP LOOPBACK RUNNING  MTU:16436  Metric:1
       21.14>           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
       21.15>           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
       21.15>           collisions:0 txqueuelen:0
       21.15>           RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
       21.15>
       21.17> wlan0     Link encap:Ethernet  HWaddr 00:00:00:00:00:00 
       21.17>           BROADCAST MULTICAST  MTU:1500  Metric:1
       21.17>           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
       21.18>           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
       21.18>           collisions:0 txqueuelen:1000
       21.18>           RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
       21.18>
       21.18> root@dm814x-evm:~#
       32.84< ./calibrator set nvs_mac /lib/firmware/ti-connectivity/wl1271-nvs.bin 50:56:63:9D:6E:5B
       32.85: |--- Mark:14 --- COM-Error --- Date: 03.08.2012 --- Time: 16:43:14.83 ---|
        0.00> root@dm814x-evm:~# ÿû¿ÿ?°ÿÿÿü~ÿçÿþwÿÿüÿ±CaüÚb`aÇJ€s%t nvs^MAcolaB/diriSX®ö¿¿¿ÿ7Üü/ti-connectivity/wl1271
        0.00> -nvs.bin 50:56:63:9D:6E:5B
        0.01> Writing mac address 50:56:63:9D:6E:5B to file /lib/firmware/ti-connectivity/wl1271-nvs.bin
        0.01: |--- Mark:15 --- COM-Error --- Date: 03.08.2012 --- Time: 16:43:14.87 ---|
       12.01< ifconfig -a
       12.01> root@dm814x-evm:oot@dm814xvm:~# ßüifconfig -a
       12.03> eth0      Link encap:Ethernet  HWaddr 50:56:63:9D:6E:5A 
       12.03>           UP BROADCAST ALLMULTI MULTICAST  MTU:1500  Metric:1
       12.04>           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
       12.04>           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
       12.04>           collisions:0 txqueuelen:1000
       12.04>           RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
       12.06>           Interrupt:40
       12.06>
       12.06> lo        Link encap:Local Loopback 
       12.06>           inet addr:127.0.0.1  Mask:255.0.0.0
       12.06>           inet6 addr: ::1/128 Scope:Host
       12.07>           UP LOOPBACK RUNNING  MTU:16436  Metric:1
       12.07>           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
       12.07>           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
       12.09>           collisions:0 txqueuelen:0
       12.09>           RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
       12.09>
       12.09> wlan0     Link encap:Ethernet  HWaddr 00:00:00:00:00:00 
       12.09>           BROADCAST MULTICAST  MTU:1500  Metric:1
       12.10>           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
       12.10>           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
       12.10>           collisions:0 txqueuelen:1000
       12.12>           RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)1.09> root@dm814x-evm

     

    when I input ifconfig wlan0 up,

     

    12.12> root@dm814x-evm:~#
      296.92< ifconfig wlan0 up
      296.93> wl1271_dev_notify
      296.95> ifconfig: SIOCSIFFLAGS: Cannot assign requested address

    Report Abuse
    • Reply
    You have posted to a forum that requires a moderator to approve posts before they are publicly available.
  • Eyal Reizer
    Posted by Eyal Reizer
    on Aug 03 2012 05:00 AM
    Intellectual1165 points

    hi,

    what is the "COM error" messages printed when you try to set thw mac address?

    this is not a normal message. do you know where it is printed from?

    try to figue out why it is printed ans this might lead to the reasonit is not working correctly.

    Report Abuse
    • Reply
    You have posted to a forum that requires a moderator to approve posts before they are publicly available.
  • Hui Yang
    Posted by Hui Yang
    on Aug 04 2012 06:48 AM
    Prodigy210 points

     

    Hello

                The Com  error was solved.but, the HWaddr is still not correct.

     

     

    root@dm814x-evm:~# ./calibrator set nvs_mac /lib/firmware/ti-connectivity/wl1271

    -nvs.bin 50:56:63:9D:6E:5B
    Writing mac address 50:56:63:9D:6E:5B to file /lib/firmware/ti-connectivity/wl1271-nvs.bin
    root@dm814x-evm:~# ifconfig -a
    eth0      Link encap:Ethernet  HWaddr 50:56:63:9D:6E:5A 
              UP BROADCAST ALLMULTI MULTICAST  MTU:1500  Metric:1
              RX packets:0 errors:0 dropped:0 overruns:0 frame:0
              TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000
              RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
              Interrupt:40

    lo        Link encap:Local Loopback 
              inet addr:127.0.0.1  Mask:255.0.0.0
              inet6 addr: ::1/128 Scope:Host
              UP LOOPBACK RUNNING  MTU:16436  Metric:1
              RX packets:0 errors:0 dropped:0 overruns:0 frame:0
              TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:0
              RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

    wlan0     Link encap:Ethernet  HWaddr 00:00:00:00:00:00 
              BROADCAST MULTICAST  MTU:1500  Metric:1
              RX packets:0 errors:0 dropped:0 overruns:0 frame:0
              TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000
              RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

    root@dm814x-evm:~#

     

    I have other question that need your help: our project use TI DM8148,we use Hardware SD/MMC2 connect WL1271 WIFI, DM 8148 is work in 3.3V , we hope Hardware SD/MMC2 can work in 1.8, so,now we set   .ocr_mask             = MMC_VDD_165_195,  HCTL is 0x00000b00,   but we measure the voltage is still  3.3V, I don't know why.

    static struct omap2_hsmmc_info mmc[] = {

                    {

                                    .mmc                      = 1,                         /* Hardware SD/MMC0 */

                                    .caps                      = MMC_CAP_8_BIT_DATA,

                                    .gpio_cd                = -EINVAL,             /* Dedicated pins for CD and WP */

                                    .gpio_wp               = -EINVAL,

                                    .ocr_mask             = MMC_VDD_33_34,

                                    .nonremovable     = true,

                    },

                    {

                                    .mmc                      = 2,                         /* Hardware SD/MMC1 */

                                    .caps                      = MMC_CAP_4_BIT_DATA,

                                    .gpio_cd                = -EINVAL,             /* Dedicated pins for CD and WP */

                                    .gpio_wp               = -EINVAL,

                                    .ocr_mask             = MMC_VDD_33_34,

     

                    },

                    {

     

                    .name           ="wl1271",/* Hardware SD/MMC2 */

                    .mmc                      = 3,

                                    .caps                      = MMC_CAP_4_BIT_DATA | MMC_CAP_POWER_OFF_CARD,

                                    .gpio_cd                = -EINVAL,

                                    .gpio_wp               = -EINVAL,

                                    .ocr_mask             = MMC_VDD_165_195,

                                   .nonremovable      = true,

                    },

                    {}             /* Terminator */

    };

     

     

     

     

    Report Abuse
    • Reply
    You have posted to a forum that requires a moderator to approve posts before they are publicly available.
12
TI E2E™ Community
  • Support Forums
  • Blogs
  • Videos
  • Groups
  • Site Support & Feedback
  • Settings
TI E2E™ Community Groups
  • TI University Program
  • Make the Switch
  • Microcontroller Projects
  • Motor Drive & Control
Other Communities
  • Deyisupport
  • Designsomething.org
  • beagleboard.org
  • TI on Element 14
  • TI on TechXchangeSM
Other Technical & Support Resources
  • WEBENCH® Design Center
  • Product Information Centers
  • Technical Documents
  • TI Design Network
  • TI Technical Articles
  • TI Training

All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with respect to these materials. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.

Content on this site may contain or be subject to specific guidelines or limitations on use. All postings and use of the content on this site are subject to the Terms of Use of the site; third parties using this content agree to abide by any limitations or guidelines and to comply with the Terms of Use of this site. TI, its suppliers and providers of content reserve the right to make corrections, deletions, modifications, enhancements, improvements and other changes to the content and materials, its products, programs and services at any time or to move or discontinue any content, products, programs, or services without notice.

Follow Us Texas Instruments on Facebook Texas Instruments on Twitter Texas Instruments on LinkedIn Texas Instruments on Google+
TI Worldwide | Contact Us | my.TI Login | Site Map | Corporate Citizenship | mobile m.ti.com (Mobile Version)

TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs and
embedded processors, along with software, tools and the industry’s largest sales/support staff.

© Copyright 1995-2013 Texas Instruments Incorporated. All rights reserved.
Trademarks | Privacy Policy | Terms of Use