• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 40 subscribers
  • Views 550 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.

issues with next application

Rotem Sasporta
Intellectual 265 points
Other Parts Discussed in Thread: CC3100, CC3200

Hello,

 

I see some issues when trying to port the "getting started with AP" example that comes with the CC3100 SDK.

 

I was able to port the "SPI Debug app" to Xilinx zynq FPGA, by modifying and using the correct SPI drivers for this host.

In the instructions PDF for this example I have a clear source list and files that I need to use in order to build the app correctly.

 

In the "getting started with AP", I only have a pre-built IAR or CCS project without a clear files list.

I trying to locate all the files by looking at project but I still see that I am missing defines that are needed.

 

Can someone provide a clear file and define list for the "getting started with ap" example application?

 

Thanks!

  • 0
    TI__Mastermind 26205 points
    Hi Rotem,

    In addition to the platform specific files that were used in 'SPI Debug App', you would need to build following file:
    - device.c
    - driver.c
    - flowcont.c
    - fs.c
    - netapp.c
    - netcfg.c
    - nonos.c
    - socket.c
    - spawn.c
    - wlan.c

    And, following include paths shall be added:
    - <sdk-installtion-dir>/cc3100-sdk/examples/common
    - <sdk-installtion-dir>/cc3100-sdk/simplelink/include
    - <sdk-installtion-dir>/cc3100-sdk/simplelink/source

    I suggest you open the project in one of the IDEs supported in the SDK and you will find the list of the files to be build.

    We have taken it as a comment and will add the required information in our documents.

    Regards,
    Ankur
  • 0 in reply to Ankur Baranwal
    TI__Mastermind 26205 points
    Hi Rotem,

    I am closing this thread, if you have follow up queries please open a new thread with a link to this one for reference.

    Regards,
    Ankur
  • 0 in reply to Ankur Baranwal
    Intellectual 265 points

    Hi Ankur,

     

    Just to clarify the situation at the moment:

     

    • what are we trying to do? We ran the SPI debug test and all is ok. When trying to run the 'Getting start with AP' that uses the SPI debug functions, it is stuck in below marked function (wait forever).
    • What chip is used, cc3100, cc3200? CC3100
      • If cc3100, what is the host processor? Zynq FPGA (internal ARM Cortex-A9)
    • Which phase are you? Porting, development? Development
    • Is something working, or nothing is working? SPI debug is working. Getting Started is stuck.
    • What is the use case which is getting the device stuck? Running an example design.
    • Did you pass init phase (sl_start)?
      • If so which command is stuck? Marked stuck function below is part of the sl_start.

    We have done some progress but we are stuck again and could use your help,

    I was able to build the application but at some we the application loop forever at this point :

    In device.c :

     

            if (NULL == pInitCallBack)

            {

                OSI_RET_OK_CHECK(sl_SyncObjWait(&g_pCB->ObjPool[ObjIdx].SyncObj, SL_OS_WAIT_FOREVER));

                /*release Pool Object*/

                _SlDrvReleasePoolObj(g_pCB->FunctionParams.AsyncExt.ActionIndex);

                return _sl_GetStartResponseConvert(AsyncRsp.Status);

            }

     

    I am able to see that the IRQ handler is reached,

     

    Any suggestion on points to look at?

     

    BR,

     

    Rotem

  • 0 in reply to Rotem Sasporta
    TI__Mastermind 26205 points
    Hi Rotem,

    This thread is already closed and I will suggest you to continue the discussion on the thread that we have split from this one to help us track the issue better. I will respond on the other thread
    Link to other thread.
    http://e2e.ti.com/support/wireless_connectivity/f/968/t/393314

    Regards,
    Ankur