Forums - HTC Master/Slave Interrupt pin

3 posts / 0 new
Last post
HTC Master/Slave Interrupt pin
athiq_j
Join Date: 5 Jul 17
Posts: 1
Posted: Thu, 2019-06-06 03:20

Hi

We are running htc demo on two Qualcomm boards

We have 2 QCA4020 boards and want to use HTC (SPI) interface to communication with each other.

#define SPI_SLV_INTR_GPIO_NUM 21 in SPI_hal.h

HTC (MASTER)                                   HTC (Slave)

MASTER_MOSI (GPIO26)               SLAVE_MOSI(GPIO23)

MASTER_MISO(GPIO27)                SLAVE_MISO(GPIO20)

MASTER_CS(GPIO24)                     SLAVE_CS(GPIO19)

MASTER_CLOCK(GPIO25)           SLAVE_CLOCK(GPIO18)

SPI_INTERRUPT(GPIO21)               SPI_INTERRUPT(GPIO21)

There is no issue with the above setup. It works fine and communication happens.

The code that defines  #define SPI_SLV_INTR_GPIO_NUM 21 in SPI_hal.h is modified to PIN 29

   Say,     #define SPI_SLV_INTR_GPIO_NUM 29

We see this GPIO29 affects in MASTER side which acts as Input pin as per the GPIO configuration. The same pin doesn't affect on SLAVE board. We don't see anywhere GPIO configuration as Output in the code.

This test was done for GPIO 30 also.

   Say,     #define SPI_SLV_INTR_GPIO_NUM 30

GPIO change works only on Master side and doesn't work on Slave side.

On the Slave board, by default (irrespective of GPIO number configured) GPIO 21 works as Ouput always.

Question:

How to change the Interrupt Pin on Slave side?. (we don't have GPIO21 on our custom module, but we can try on Qualcomm board QCA4020)

 

Thanks

  • Up0
  • Down0
jaydenk
Join Date: 21 Jun 18
Posts: 64
Posted: Tue, 2019-08-27 12:13

Hi athiq_j,

GPIOs for SPI slave are not configurable.
So, please understand there is no way to configure SPI slave interrupt as other GPIOs.

Thanks
BR,
Jayden

  • Up0
  • Down0
jaydenk
Join Date: 21 Jun 18
Posts: 64
Posted: Tue, 2019-08-27 12:13

Hi athiq_j,

GPIOs for SPI slave are not configurable.
So, please understand there is no way to configure SPI slave interrupt as other GPIOs.

Thanks
BR,
Jayden

  • Up0
  • Down0
or Register

Opinions expressed in the content posted here are the personal opinions of the original authors, and do not necessarily reflect those of Qualcomm Incorporated or its subsidiaries (“Qualcomm”). The content is provided for informational purposes only and is not meant to be an endorsement or representation by Qualcomm or any other party. This site may also provide links or references to non-Qualcomm sites and resources. Qualcomm makes no representations, warranties, or other commitments whatsoever about any non-Qualcomm sites or third-party resources that may be referenced, accessible from, or linked to this site.