4 Replies Latest reply on Aug 18, 2018 1:49 AM by stru
      • 1. Re: While I was porting driver of JODY-W164 module, I failed to find these two files mentioned in user manual: fw_bcmdhd_hu.bin and nvram.txt . Does anyone know about it?
        mifo

        gery_3531936

         

        This is an automotive module, so it is not supported in the Broad Market and here on the community.  Please reach out to the local Cypress sales team that engaged with you on this module and ask them to setup a direct support channel with the regional automotive team and engineering group.

        1 of 1 people found this helpful
        • 2. Re: While I was porting driver of JODY-W164 module, I failed to find these two files mentioned in user manual: fw_bcmdhd_hu.bin and nvram.txt . Does anyone know about it?
          stru

          Hi Gery,

           

          To answer your question:

          The nvram file is specific to the module design and should be obtained from U-blox.

          The filename listed is just an example.

          In the driver/firmware release (e.g. P8.2) you will find the folder 'firmwares'. This contains a number of different firmware binaries. The one to use depends on you application. Please refer to the pdf document '89359_pcie_fw_description.pdf'. This contains a description of each of the firmware binaries provided.

           

          Br, Steve

          • 3. Re: While I was porting driver of JODY-W164 module, I failed to find these two files mentioned in user manual: fw_bcmdhd_hu.bin and nvram.txt . Does anyone know about it?
            gery_3531936

            Hi, Steve,

                 Thanks for your answer. But I have another issue that the chip is not powered up successfully.

             

                 My kernel log:

             

            rockchip_headset_probe() headset have hook adc mode

            [    1.833438] input: rk_headset as /devices/platform/rk_headset/input/input0

            [    1.833880] wlreg_on: disabling

            [    1.834038] I : [File] : drivers/gpu/arm/mali400/mali/linux/mali_kernel_linux.c; [Line] : 414; [Func] : mali_module_init(); svn_rev_string_from_arm of this mali_ko is '-e044290', rk_ko_ver is '5', built at '14:14:00', on 'Aug 17 2018'.

            [    1.834195] Mali: Mali device driver loaded

            [    1.834207] dhd_module_init in

            [    1.834321] ZJW: JODY_W164 probe start:

            [    1.834435] of_get_named_gpiod_flags: parsed 'gpios' property of node '/bcmdhd_wlan@0[0]' - status (0)

            [    1.834440] Enter function: dhd_wifi_platform_load.

            [    1.834459] Enter function: dhd_wifi_platform_load_sdio.

            [    1.834464] Power-up adapter 'DHD generic adapter'

            [    1.834470]  - irq 69 [flags 1044], firmware: (null), nvram: (null)

            [    1.834475]  - bus type -1, bus num -1, slot num -1

            [    1.834475]

            [    1.834482] Enter function : sdio_func_reg_notify. to register sdio driver.

            [    1.834501] enter function: wifi_platform_set_power.

            [    1.961853] usb 2-1.1: new high-speed USB device number 3 using ehci-platform

            [    2.049796] usb 2-1.1: New USB device found, idVendor=1a40, idProduct=0101

            [    2.049842] usb 2-1.1: New USB device strings: Mfr=0, Product=1, SerialNumber=0

            [    2.049870] usb 2-1.1: Product: USB 2.0 Hub

            [    2.051284] hub 2-1.1:1.0: USB hub found

            [    2.051607] hub 2-1.1:1.0: 4 ports detected

            [    2.091420] vendor storage:20160801 ret = 0

            [    2.434979] leave function: wifi_platform_set_power.

            [    3.791854] usb 5-1: new high-speed USB device number 2 using xhci-hcd

            [    3.914839] usb 5-1: New USB device found, idVendor=05e3, idProduct=0718

            [    3.914884] usb 5-1: New USB device strings: Mfr=0, Product=1, SerialNumber=2

            [    3.914955] usb 5-1: Product: USB Storage

            [    3.914981] usb 5-1: SerialNumber: 000000000033

            [    3.917245] usb-storage 5-1:1.0: USB Mass Storage device detected

            [    3.918884] scsi host0: usb-storage 5-1:1.0

            [    4.435100] failed to power up DHD generic adapter, 3 retry left

            [    4.451279] enter function: wifi_platform_set_power.

            [    4.451340] leave function: wifi_platform_set_power.

            [    4.451362] Enter function : sdio_func_reg_notify. to register sdio driver.

            [    4.451430] enter function: wifi_platform_set_power.

            [    4.925109] scsi 0:0:0:0: Direct-Access     USB TO I DE/SATA Device   0016 PQ: 0 ANSI: 4

            [    4.928531] sd 0:0:0:0: Attached scsi generic sg0 type 0

            [    4.931789] sd 0:0:0:0: [sda] Test WP failed, assume Write Enabled

            [    4.933471] sd 0:0:0:0: [sda] Asking for cache data failed

            [    4.933547] sd 0:0:0:0: [sda] Assuming drive cache: write through

            [    4.938912] sd 0:0:0:0: [sda] Attached SCSI disk

            [    5.051860] leave function: wifi_platform_set_power.

            [    6.918052] rockchip-dsi ff960000.dsi: fin=24000000, prediv=4, fbdiv=166

            [    6.918076] rockchip-dsi ff960000.dsi: final DSI-Link bandwidth: 996 x 4 Mbps

            [    6.926534] _____rockchip_dsi_external_bridge_power_on

            [    6.928872] rockchip-dsi ff960000.dsi: test_code=0x44, test_data=0x34, monitor_data=0x34

            [    6.928934] rockchip-dsi ff960000.dsi: test_code=0x19, test_data=0x30, monitor_data=0x30

            [    6.928993] rockchip-dsi ff960000.dsi: test_code=0x17, test_data=0x03, monitor_data=0x03

            [    6.929049] rockchip-dsi ff960000.dsi: test_code=0x18, test_data=0x05, monitor_data=0x05

            [    6.929104] rockchip-dsi ff960000.dsi: test_code=0x18, test_data=0x85, monitor_data=0x05

            [    6.929155] rockchip-dsi ff960000.dsi: test_code=0x00, test_data=0x00, monitor_data=0x00

            [    7.051874] failed to power up DHD generic adapter, 2 retry left

            [    7.068317] enter function: wifi_platform_set_power.

            [    7.068395] leave function: wifi_platform_set_power.

            [    7.068419] Enter function : sdio_func_reg_notify. to register sdio driver.

            [    7.068494] enter function: wifi_platform_set_power.

            [    7.671869] leave function: wifi_platform_set_power.

            [    9.671860] failed to power up DHD generic adapter, 1 retry left

            [    9.688313] enter function: wifi_platform_set_power.

            [    9.688391] leave function: wifi_platform_set_power.

            [    9.688413] Enter function : sdio_func_reg_notify. to register sdio driver.

            [    9.688491] enter function: wifi_platform_set_power.

            [   10.291866] leave function: wifi_platform_set_power.

            [   12.291878] failed to power up DHD generic adapter, 0 retry left

            [   12.308321] enter function: wifi_platform_set_power.

            [   12.308399] leave function: wifi_platform_set_power.

            [   12.308422] failed to power up DHD generic adapter, max retry reached**

            [   12.308489] ZJW: JODY_W164 probe end!

            [   12.308611] dhd_module_init out

             

            My dts file:

             

            wlreg_on: fixedregulator@2 {

                    compatible = "regulator-fixed";

                    regulator-name = "wlreg_on";

                    gpio = <&gpio1 0 GPIO_ACTIVE_HIGH>;

                    startup-delay-us = <600000>;

                    enable-active-high;

                };

            bcmdhd_wlan_0: bcmdhd_wlan@0 {

                    compatible = "android,bcmdhd_wlan";

                    gpios = <&gpio0 3 GPIO_ACTIVE_HIGH>;

                    wlreg_on-supply = <&wlreg_on>;

                };

             

            I don't know how to get rid of this issue. Can you help me ?

            And the product type is JODY-W164-03A-01, does it support SDIO host interface?

            • 4. Re: While I was porting driver of JODY-W164 module, I failed to find these two files mentioned in user manual: fw_bcmdhd_hu.bin and nvram.txt . Does anyone know about it?
              stru

              Hi Gery,

               

              You will need to check with U-blox to confirm that JODY-W164-03A-01 supports SDIO host interface.

              Also U-blox should provide first line support. If they are unable to help then they will direct you to Cypress.

               

              For info, the JODY module uses Cypress 88359 chipset which is not supported by the General WICED community forum.

              I have created a MyCases Project 'IOT_UBLOX JODY-WXXX DHD NON-AUTOMOTIVE' and added you as a member of the team.

              When you login to your Cypress account you should see a 'MyProjects' link in the top right hand corner of the screen. You should be able to click on the link, find the project and then submit a MyCases ticket. Please include all the information you've listed here. I have include the U-blox AE team so they have visibility.

               

              Some additional comments:

              1. Which driver/firmware pacakge are you using? In my previous response I referred to P8.2. This is for PCIe and not SDIO. For SDIO, you need to be using the S5.2 package.

              2. We do not support ad-hoc mode. This was depricated from the IEEE standard a numbe rof yesrs ago and replaced with Wi-Fi Direct (P2P)

              3. The second line of the log you provided has: [    1.833880] wlreg_on: disabling. I'm not sure if this is with refernce to the JODY module but wlreg_ON needs to be enabled otherwise the Wi-Fi subsystem will be turned off.

               

              Br, Steve