• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 2 answers
  • Subscribers 40 subscribers
  • Views 439 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.

Original question:

BOOSTXL-CC3120MOD: STM32L152RE

CC3120MOD: Porting host driver to Cypress CY8C5868AXI-LP032 MCU

Wai Yeung
Prodigy 230 points
Part Number: CC3120MOD


I'm attempting to port the host driver to Cypress CY8C5868AXI-LP032 MCU.

I am referring to the following links:

I have many question in regards to the porting process.

The first couple of questions:

1. Does the user.h file require "cc_pal.h"

2. If I want to use a particular silo, I would just need to include the file with the silo name, correct?

Thanks,

Wai

Thanks,

Wai

  • 0
    TI__Mastermind 30820 points
    Hi Wai,

    I think there is a more complete description of the porting process in chapter 16 of the network processor guide. I recommend you refer to it.
    http://www.ti.com/lit/swru455

    The user.h file and the cc_pal.h file perform two different functions. Generally, the cc_pal contains the platform specific interface. user.h is more for setting the different build options for the host driver and connecting the platform specific calls to the common interface used inside the host driver core.

    It's a little trickier to remove the silo just by taking out the source files with those names. That would work for most of the removal, but there may be a few leftover references to the callbacks or functions for a specific silo in other pieces of the driver core. If possible, it is recommended to stick with one of the existing build configurations or the full driver.

    Best,
    Ben M
  • 0 in reply to Benjamin Moore
    Prodigy 230 points

    Hello Ben,

    Thanks for the quick response. 

    Just for others that might be reading this post, the link (directed to SWRU455G.pdf ) you provided had "Provisioning" in chapter 16.  It's chapter 19 that has "Porting the Host Driver".  In older versions of the document (ie one of the links I referred to in my original post)  Ch. 16 was "Porting the Host Driver".

    Based on the document in your link, only the user.h file needs to be modified to port the driver.  However, if cc_pal contains the platform specific interface, should that need modification as well?

    Thanks for clarifying the part about silos.  Where can I find the full driver?  Google searches and searches on the TI website did not result in a package. Closest I could find are the files from the simplelink_sdk_wifi_plugin_2_30_00_10\source\ti\drivers\net\wifi in the "SimpleLink SDK WiFi Plug-in"

    Following the "Porting the Host Driver" procedure, it states that "TI recommends using the static memory management model", but I found it odd that the user.h file in simplelink_sdk_wifi_plugin_2_30_00_10 SDK had SL_MEMORY_MGMT_DYNAMIC defined.  I removed the definition per TI recommendation unless there you recommend otherwise.

    Further background information:

    I'm using the cypress PSoC Creator 4.2 IDE and we won't be using a RTOS 

    Thanks,

    Wai

  • 0 in reply to Wai Yeung
    TI__Mastermind 30820 points
    Hi Wai,

    Yes, cc_pal will need to be modified or replaced (more likely) to complete the porting.

    Yes, that location in the Wi-Fi plugin is the host driver. For those that don't have the link, it is here:
    www.ti.com/.../SIMPLELINK-WIFI-CC3120-SDK-PLUGIN

    The memory allocation can be set based on what you believe is best for the application. The standard trade-offs for static vs dynamic memory allocation apply.

    Best,
    Ben M