• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 41 subscribers
  • Views 913 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.

WL1837MOD: Unable to run WiLink driver on Big Endian machine.

Waseem Abbas56
Prodigy 80 points
Part Number: WL1837MOD

I am trying to run WiLink8 driver on a big endian processor and I have replaced __BYTE_ORDER_LITTLE_ENDIAN #define with __BYTE_ORDER_BIG_ENDIAN but it turns out that we still need to make many changes in the source code like swapping the endianness of firmware binary, ini file and Mail Box commands etc for proper working of the wifi chip which is a very complicated task. Can you please confirm if WiLink8 driver is compatible with Big Endian machines. 

  • 0
    TI__Mastermind 20285 points
    What version of the drivers are you using and where are you changing the above #define?
    Are you using Linux?
    The firmware binary (wl18xx-fw.bin) is running inside the wl18xx memory so not really dependent on the host.

    BR,
    Eyal
  • 0 in reply to Eyal Reizer
    Prodigy 80 points

    Hi Eyal,

    Thank you for a quick response. I am using the MCP-8.0.0.47_Release version . I am changing the mentioned #define in wlan_cu_build_config.h and osTIType.h files and I am using Nucleus RTOS.
    I am using the hex dump of firmware binary (wl18xx-fw.bin) which is downloaded to wl18xx and if I download the hex dump array of firmware binary to the chip as it is, it doesn't work and I need to swap the endianness of every word (4 bytes) of firmware binary array before writing it to the chip.

    And same is the case with every byte array data type that is being sent to the WiFi chip after casting it to any 32 bit data type. 

    BR,
    Waseem

  • 0 in reply to Waseem Abbas56
    TI__Mastermind 20285 points
    Hi Waseem,

    MCP is not directly supported internally but rather through third parties.
    Internally we only support Linux NLCP.
    Did you do the original porting internally for LE and now need it for BE or was it done for you by a third party?

    Best Regards,
    Eyal
  • 0 in reply to Eyal Reizer
    Prodigy 80 points

    HI Eyal,

    We did the original porting for LE internally. 

    Thanks,
    Waseem

  • 0 in reply to Eyal Reizer
    Prodigy 80 points
    Hi Eyal,

    Just to confirm if we are putting our porting effort from LE to BE target in the right direction, can you please confirm if we actually need to update the WiLink8 MCP driver for BE target?

    Thanks,
    Waseem