Thanks. I looked at FTM_IC usage in that example you mentioned and added the FTM_IC component to the existing work project which is based on LPSPI_DMA sample. The LPSPI_DMA sample loop does 1000 xfers (each size is 16B) and checks the result.
I added calls like below:
- FTM_DRV_Init();
- FTM_DRV_InitInputCapture();
- FTM_DRV_DeinitInputCapture();
- FTM_DRV_Deinit();
before entering the SPI test loop. Everything seems fine here.
However, if I comment out step 3 and 4 so that to keep FTM_IC running, I then noticed the SPI test loop never ends, at least for more than 400 loops. It does end if loop count is 350. I am guessing the FTM component initialization might have some interferences with the LPSPI DMA sample but not sure what it is. Things might be fine if the SPI xfer count is small... but it will happen if there are many xfers (such as 375 times).
For your reference, I am using fixed frequency configuration as my FTM_IC clock source as I want an effective 1Mhz clock. I have overflow interrupt enabled but didn't do anything meaningful yet.
Do you experience the same behavior there?