This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

is nrf52 dk support 3 wire spi interface

hello i am new to spi, i am doing project on 3 wire spi interface. I am using 3 wire interface as Sclk,ssn,MOSI pins only , I am not using MISO pin .I am tested spi example code but does not works well.so can any one tell me that nrf52 dk -spi support 3 wire interface ( with out using MISO pin). The issue is the serial clock was not generates signals .For sending data the function "nrf_drv_spi_transfer(&spi, m_tx_buf, m_length, m_rx_buf, m_length) " was used.Every time ssn pin is low to send the data & it is set to high after sending the data.Here i am using AD9837 module as slave & it works on spi interface only.I am facing 1 issue i.e., as follows. Here the data i hexa decimal but in the example code the tx buffer must be character type

Parents
  • slowly, slowly you add more information about what you're doing. I checked the datasheet for that chip, it's unidirectional SPI, data is only written to it, never read. So again, the SPI interface will work just fine, you just define the MISO pin as 0xffffffff, the driver will work, there is nothing special to do here.

    I said, in the link you pasted, that the 3-wire half duplex protocol was not supported. That's the one where one pin does transmit and receive. This is NOT that case with the chip you are using, this is a normal SPI interface where there is no data transfer from the slave, only writes TO the slave. That is supported, so now you need to start looking for your bug.

Reply
  • slowly, slowly you add more information about what you're doing. I checked the datasheet for that chip, it's unidirectional SPI, data is only written to it, never read. So again, the SPI interface will work just fine, you just define the MISO pin as 0xffffffff, the driver will work, there is nothing special to do here.

    I said, in the link you pasted, that the 3-wire half duplex protocol was not supported. That's the one where one pin does transmit and receive. This is NOT that case with the chip you are using, this is a normal SPI interface where there is no data transfer from the slave, only writes TO the slave. That is supported, so now you need to start looking for your bug.

Children
No Data
Related