This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

AWR2243: 4 pcs AWR2243 cascaded, FPGA use one I2C and one SPI to connect 4 PCS AWR2243? 4 PCS AWR2243 have different I2C device address(GPIO set), SPI CLK/MOSI/MISO of 4 pcs 2243 connect together.

Part Number: AWR2243

Hello team,

    my solution is 4 pcs AWR2243+FPGA, for save I/O of FPGA and connector, I want to use one I2C to control  4 pcs AWR2243( 4 pcs 2243 have different device address---GPIO configure), at the same time, I use one SPI to control 4 pcs AWR2243---it share CLK/MOSI/MISO, of course,  CS and INTR are independent(every 2243 has independent CS and INTR). I don't use QSPI interface,  so leave this interface NC, is it ok for this design?

    2.  AWR2243 has 3 GPIO and I use it to set I2C device address, beside this function, GPIO has other function? need I connect GPIO to FPGA?  

3. JTAG of 2243 is useful for customer?  I only leave test point for JTAG, is it ok?

your comment is welcome!

  • Hello Simon,

    You mention that you use I2C interface and you also mention you use one SPI interface. You can use either one of them, not both, to control the AWR2243 device. There are 3 different I2C addresses possible using the GPIO 0:2 pins (refer to the datasheet), so 4 devices could be an issue while using I2C interface.

    Leaving QSPI pins NC is not an issue. JTAG is needed only for debug, so you can leave them connected to test points.

    Regards,

    Vivek

  • Dear Vivek,

       thanks for your advice!

       I prepare to use SPI to configure 2243 first, I2C is only backup. 

       because GPIO have 3 pin, so I think I2C device address can be set to 8 different address. you mean I2C device address only have three: 0x000 0x001  0x111, is it right?(lists below).

    the function of GPIO has only set I2C address, is it right? I don't need to connect GPIO to FPGA(MCU)?thanks!

  • Hello ,

    You are right, we can support 8 I2C addresses with the 3 GPIO configurations, I double checked that now.

    In I2C mode the function of the GPIO is only to set the address. But in SPI mode the GPIO0 is used for debug purpose to send failure logs incase the SPI interface has issues.

    Regards,
    Vivek

  • Dear Vivek,

       thank so great for your suggestions, could you give more information about GPIO0? when it will give failure log? what's the meaning of the host needs to be able to drive a pulse on this pin? why host give one pulse to GPIO0, how long time this pulse needs if FPGA gives this pulse?

  • Hello Simon,

    Incase the  host does not get the ack over the SPI interface the host can get stuck waiting for the ack. In this state the host can toggle the GPIO0 to get debug information sent out. Below is the flow diagram.

    Regards,
    Vivek