• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 31 subscribers
  • Views 219 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.

AM2432: EEPROM Call I2C Caused Stuck

Kevin Peng
Expert 3762 points
Part Number: AM2432
Other Parts Discussed in Thread: SYSCONFIG

Tool/software:

Hi TI Experts,

Customer is working on AM2432 SDK9.2.

They have solved a similar question before I asked in the below thread, that after changing to the Polled mode in SPI, the stuck problem ethercat_slave_beckoff_ssc_demo will resolve.

https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1440913/am2432-call-spi-operations-in-appl_application-cause-system-reset/5542363?

Now customer has a new problem, when eeprom in ethercat_slave_beckoff_ssc_demo call the I2C module, there is some situations that the eeprom will stuck also.

Customer provides the I2C sysconfig below for your review.

Could you please review their sysconfig and see if there is some suggestions please?

Thanks,

Kevin

  • 0
    TI__Prodigy 560 points

    Hi Kevin.
    This looks like this could be the similar issue where I2C is in blocking mode and this mode is interfering with EtherCAT. Can you ask them to not use interrupt and check if this works. Also if possible can they share the I2C part of the code so that I can look at it further.

  • 0 in reply to Keshav Tiwari
    TI__Expert 3762 points

    Hi Keshav,

    Thanks a lot for your support, after trying not using the interrupt it works normally now!

    The additional question based on it is that customer wants to know why does using IIC interrupt mode cause task deadlock? Could it be that the interrupt was not triggered at a certain moment?

    Thanks,

    Kevin

  • 0 in reply to Kevin Peng
    TI__Mastermind 48578 points

    Hi Kevin,

    Can you please try once configuring the parameter I2C_MAX_CONSECUTIVE_ISRS from 1 to some other value. The parameter is located in ${MCU+SDK}\source\drivers\i2c\v0\lld\i2c_v0_lld.c file.

    Please try with below value.

    #define I2C_MAX_CONSECUTIVE_ISRS            ((uint32_t) 16U)

    Regards,

    Tushar