• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 2 answers
  • Subscribers 30 subscribers
  • Views 274 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

AM2732-Q1: Could U15, V16 be used as RCSS_I2CB_SCL/SDA

Lei Tao Tao
Prodigy 170 points
Part Number: AM2732-Q1
Other Parts Discussed in Thread: AWR2243, TIDA-020047, AM2732

Hi,

The ball U15 and V16 are MSS_I2C only when used as I2C, and in TIDA-020047(Dual MMIC cascade reference design) they are connected with master AWR2243.

On the contrary, slave AWR2243 connects with RCSS_I2CA. Why not use RCSS_I2CB to connect with slave AWR2243?

This  reference design https://www.ti.com/tool/TIDA-020047

  • 0
    TI__Mastermind 22685 points

    Hi,

    I suspect that separate I2C buses were used so that communication to both AWR2243 devices could happen simultaneously.  If both AWR2243 devices were on the same bus, the AM2732 could only communicate with one at a time, and the delay in comms to the second AWR2243 may impact the performance of the design.

    Thanks,
    Mike

  • 0 in reply to Mike Pridgen
    Prodigy 170 points

    Hi Mike,

    Understood!

    Additionally, the only MSS I2C (F16,F18) is used as SOC_I2C, so U15 and V16 could not setting as MSS I2C simultaneously, right?

    In functional block diagram, there are 2 × I2C in RCSS block, and it's reasonable to config RCSS_I2CA and RCSS_I2CB as AWR2243 control interface, or is there any other considerations？

    BR

  • 0 in reply to Lei Tao Tao
    TI__Mastermind 22685 points

    Hi,

    Yes, you are correct.  Both F16/F18 and U15/V16 have MSS_I2CA as a pinmux option (among other pins), and you should only have SCL and SDA be selected through the pinmux on a single pin each.

    It should be reasonable to configure RCSS_I2CA and RCSS_I2CB as AWR2243 control interface, that was just not how it was done on the reference design.

    Thanks,
    Mike