• State TI Thinks Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 40 subscribers
  • Views 685 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.

CC3235SF: FATAL ERROR: No Cmd Ack detected [cmd opcode = 0x8432]

Jitendra Singh7
Expert 1435 points
Part Number: CC3235SF
Other Parts Discussed in Thread: SYSCONFIG

I am using cc3235 as SPI master( GPIO14, 15, 16 and 17 as SPI_DIN, SPI_DOUT, SPI_CLK, SPI_CS ).

The whole protocol works on a command ack kind of flow. Sometimes there is a delay in response from the slave device.

At that time, I get below error on SimpleLinkFatalErrorEventHandler(SlDeviceFatal_t *slFatalErrorEvent) and all the simple link apis start throwing errors.

FATAL ERROR: No Cmd Ack detected [cmd opcode = 0x8432]

I tried setting the priority of SL_task lower than the task waiting on the SPI semaphore.

I have a question: is CC3235 device internally using this SPI for interacting with a simple link device? If so, how to share the port properly among both tasks? The application task uses this port for a bitrate of about 3Mbps.

What should be the priority of sl_task()? lower or higher than application tasks?

Regards

  • 0
    TI__Mastermind 40965 points

    Hi,

    The CC3235 does indeed use an internal SPI bus to interface with the network processor. Whenever you use an sl_*() API, you will be sending a command on through internal SPI interface to the NWP.

    That being said, the SPI interface that you can control from the application side is a different hardware instance of the SPI peripheral. I have run tests in the past where I was able to run the apps SPI at 20MHz streaming data constantly and concurrently send it through the NWP SPI to a network server. So the SPI peripheral is physically capable of running full speed on both the apps SPI and the NWP SPI without issues.

    There isn't any special configuration you need to do in order to use both SPI interfaces at the same time. The demo programs should have the correct configuration for the apps SPI, especially if you are using SysConfig. The NWP SPI is configured in the SimpleLink host driver, and that is thoroughly tested every SDK release and should be stable as well.

    sl_task() should ideally be the highest priority task in your system. Is this not the case? If not, then try increasing the priority and seeing if that resolves things.

    Regards,

    Michael

  • 0 in reply to Michael Reymond
    TI__Mastermind 40965 points

    Hi,

    I assume that you have resolved your issue since I have not heard back from you. If not, feel free to post a response to this thread, or open a new thread regarding this issue.

    Regards,
    Michael