Other Parts Discussed in Thread: LAUNCHXL-CC2640R2
Hello,
I am debugging an issue using sensor controller studio- two versions of the task function execution code, and the corresponding measured SPI_CLK waveforms
spiBegin(SPI_POL1_PHA1, AUXIO_SPI_CSN_ACCEL_CSN); spiTxRx8bit(SPI_POL1_PHA1, (bitMsk_RD + addr_WHO_AM_I); output.partID); spiEnd(SPI_POL1_PHA1, AUXIO_SPI_CSN_ACCEL_CSN);

spiBegin(SPI_POL1_PHA1, AUXIO_SPI_CSN_ACCEL_CSN); spiTx8bit(SPI_POL1_PHA1, (bitMsk_RD + addr_WHO_AM_I)); spiRx8bit(SPI_POL1_PHA1; output.partID); spiEnd(SPI_POL1_PHA1, AUXIO_SPI_CSN_ACCEL_CSN);

The difference in the two codesets is if the TxRx is done in a one or two lines; as described in the SPI Data Transfer section of Sensor Controller Studio Help Viewer, I would expect this to produce the same number of clock pulses- However, the single line waveform does not match my understanding of how this function works.
The hardware is custom board with a sensor attached to the SPI bus. I have experienced an issue pointing to the XTAL (Using the RCOSC build of simple_peripherial allows bluetooth functionality), and possibly further assembly issues, however, I expect this is independent of possible hardware bugs. I'm using SCS 2.9.0.208



