IWR6843AOP: Can I use the IWR6843AOP with a MMWAVEICBOOST Launch Pad SPI connections

Hi,

Have you reviewed the SDK documentation on the SPI driver found at C:\ti\mmwave_sdk_03_06_00_00-LTS\packages\ti\drivers\spi\docs\doxygen\html\index.html?

You could also drag the SPI source into your project to build it yourself in order to debug it to see where it gets hung up. Have you tried this?

Best,

Nate

I have read the SPI documentation in detail and can't see where i'm going wrong. I've reviewed the test code and noticed some calls to Pinmux function call which i'm investigating now. Unsure what you mean drag the SPI source into my project are you referring to the test or the library ?

Debugging with a fine toothcombe i have found where i hang. in the file mibspi_dma.c @ line 2274, 

semaStatus = SemaphoreP_pend(ptrMibSpiDriver->transferCompleteSem, ptrMibSpiDriver->params.transferTimeout);

We have checked ptrMibSpiDriver->params.transferTimeout to discover a timeout of 4294967295, I am left with 2 question How do i change the timeout and how is the semaphore triggered. Either of these question will help me understand what is going wrong. 

I have applied the Logic Analyser and no data was seen, also, SPI_Transfer only operates in BLOCKING Mode according to the docs

Hi Duncan,

Do you see any traffic on the PICO line? SPI traffic should begin with data sent from controller to peripheral, so if there is no traffic from the central device first, then I would expect there to be problems with the peripheral communicating.

Best

Nate

We saw the clock and chip select line behaving as expected, do we have to put data on the PICO line I'm expecting data on the POCI line as that what software is trying to do, do i need to send some data to the radar chip in order to active the data out?

Hi Duncan,

A typical SPI configuration would have the Central Device requesting information from the peripheral device, but I suppose you could simply broadcast right from the peripheral to the central unprompted. When you pend on the ptrMibSpiDriver->transferCompleteSem, the semaphor there should have a value of 1. When I see it being initialized in MISPPI_open() though, it seems to be initialized with a value of zero (line 1959 of mibspi_dma.c).

I have followed the code through and i see the the semaphore created, however the value of 1/0 is a little confusion as its a void* and all i see in the debugger is a memory location. In order to dereference and inspect the contents of the struct i would need to what type to cast it to.

Hi Duncan,

I believe a uint8_t would be fine to cast it to, you could also just look directly in the memory in the memory tab.

Best,

Nate

cheers Nate, done this and we're see a 0 once we create the semaphore

is this likely to be the cause if so what controls this semaphore creation

it does not get set to 1 in the spi_write function we sit there with a 0

Thankyou so so much