• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 40 subscribers
  • Views 821 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

sl_Start(0,0,0) - CC3200 - NON OS

Jon Reece
Prodigy 130 points

Hi,

I have ported (seemingly successfully) the provisioning_ap example to a non os based build. Removing the SL_PLATFORM_MULTI_THREADED define and references to osi.h. My project builds with no errors and I can start to debug however, I get stuck waiting for a semaphore to be set in _SlNonOsSemGet called from the first instance of sl_Start.

I have tried with both the latest production release of the service pack (CC31xx_CC32xx_ServicePack_1.0.0.10.0) as well as the beta (CC31xx_CC32xx_ServicePack_1.0.0.10-2.5.99.11-Beta) with similar results. I am using version 1.1.0 of the SDK.

Running the non-os connection policy example gives the same result.

I feel that I am missing a step but I'm not sure what it is. 

I have stripped my code out to be a board init:

	MAP_IntVTableBaseSet((unsigned long)&g_pfnVectors[0]);

    MAP_IntMasterEnable();
    MAP_IntEnable(FAULT_SYSTICK);

    PRCMCC3200MCUInit();

and I call sl_Start just after this.

Any ideas?

Thanks,

Jon

  • 0
    TI__Genius 16230 points
    Jon, Am I to understand that sl_start doesn't return irrespective of whether you are using OS or Non-OS environment, and you have the same observation when working w/ the standard SDK applications as well? Can you please check by reformatting the device once?

    -/Praneet
  • 0 in reply to Praneet Kumar
    Prodigy 130 points
    Hi,

    It works in the OS environment - however we don't want to be tied into using an RTOS - for our application it is massively overkill. I cannot get any of the non-os based applications to return from sl_Start.

    I have been formatting the device on a regular basis as this seems to be the most reliable way of ensuring that both core communicate between themselves (again I suspect I am missing something here but I am not really concerned about this yet).

    J
  • 0 in reply to Jon Reece
    Prodigy 130 points

    Hi,

    I found the problem - it was an attempt to get round the DNS -161 error left over in the simple link handlers from when I was using the TI-RTOS. It's now up and connecting to my network. 

    Still getting -161 errors though. As I understand it - this is due to more than 2 DNS servers setup on my network.

    Is there a way to override the DNS server if the IP address is null?

    Thanks,

    Jon

  • 0 in reply to Jon Reece
    TI__Genius 16230 points
    Jon, As you have created a separate thread on this topic (e2e.ti.com/.../491553), I'm closing this thread.

    -/Praneet