6 Replies Latest reply on Nov 17, 2016 10:57 AM by Paul_B

    I2C connection getting unstable

    hemantt

      Hello

      We are using Arduino Extension board and I see following error  some time

       

      [  196.122678] i2c-designware-pci 0000:00:09.1: i2c_dw_handle_tx_abort: lost arbitration

      [  197.444035] i2c-designware-pci 0000:00:09.1: i2c_dw_handle_tx_abort: lost arbitration

      [  198.125144] i2c-designware-pci 0000:00:09.1: i2c_dw_handle_tx_abort: lost arbitration

      [  201.010012] i2c-designware-pci 0000:00:09.1: i2c_dw_handle_tx_abort: lost arbitration

      [  201.589591] i2c-designware-pci 0000:00:09.1: i2c_dw_handle_tx_abort: lost arbitration

      [  204.114065] i2c-designware-pci 0000:00:09.1: i2c_dw_handle_tx_abort: lost arbitration

      [  208.158045] i2c-designware-pci 0000:00:09.1: i2c_dw_handle_tx_abort: lost arbitration

      [  209.399666] i2c-designware-pci 0000:00:09.1: i2c_dw_handle_tx_abort: lost arbitration

      [  209.761383] i2c-designware-pci 0000:00:09.1: i2c_dw_handle_tx_abort: lost arbitration

      [  210.281141] i2c-designware-pci 0000:00:09.1: i2c_dw_handle_tx_abort: lost arbitration

      [  210.641395] i2c-designware-pci 0000:00:09.1: i2c_dw_handle_tx_abort: lost arbitration

      [  211.282296] i2c-designware-pci 0000:00:09.1: i2c_dw_handle_tx_abort: lost arbitration

       

      This is the thread talks about it .

      GPIO access from linux can crash the GEN2

       

       

      IS there a solution for  this problem.

       

      Thanks,

      Hemant

        • 1. Re: I2C connection getting unstable
          Intel_Peter

          Hello hemantt,

           

          Do you have the same behavior? Does your I2C also show corrupted data? And the only way for you to correct this is to cold reset the Intel® Galileo?

           

          Peter.

          • 2. Re: I2C connection getting unstable
            hemantt

            Hi,

            We are using "Intel® Edison kit for Arduino* expansion board". The I2C data seems to be correct. cold reset means "flash the Edison" ?

            Is this the only solution .

            We are looking to use this for production system , so this has to me stable . Do  you know what is root cause and  if this will be released in future releases ?

             

             

            Thanks,

             

            Hemant

            • 3. Re: I2C connection getting unstable
              Intel_Peter

              No, by cold reset I meant to completely remove all power from the board. Since the thread you mentioned was about a Galileo known issue, I doubt that you are having the issue on your Edidon. But if the data is correct, what is your question? Are you just concerned about the "i2c-designware-pci 0000:00:09.1: i2c_dw_handle_tx_abort: lost arbitration" lines?

               

              Peter.

              • 4. Re: I2C connection getting unstable
                cbradley4466

                Hi All,

                 

                Is there a fix for this? I'm having the same problem and cold starting the Edison doesn't seem to help at all. This problem makes the I2C unusable.

                 

                I'm using the Sparkfun blocks, not the Galileo but having the same problem.

                 

                Along with the above error, I also get this.

                 

                [  133.365792] i2c-designware-pci 0000:00:08.0: i2c_dw_handle_tx_abort: lost arbitration

                [  136.370054] i2c-designware-pci 0000:00:08.0: ===== REGISTER DUMP (i2c) =====

                [  136.370153] i2c-designware-pci 0000:00:08.0: DW_IC_CON:               0x65

                [  136.370227] i2c-designware-pci 0000:00:08.0: DW_IC_TAR:               0x1e

                [  136.370300] i2c-designware-pci 0000:00:08.0: DW_IC_SS_SCL_HCNT:       0x2f8

                [  136.370372] i2c-designware-pci 0000:00:08.0: DW_IC_SS_SCL_LCNT:       0x37b

                [  136.370445] i2c-designware-pci 0000:00:08.0: DW_IC_FS_SCL_HCNT:       0x87

                [  136.370516] i2c-designware-pci 0000:00:08.0: DW_IC_FS_SCL_LCNT:       0x10a

                [  136.370589] i2c-designware-pci 0000:00:08.0: DW_IC_INTR_STAT:         0x0

                [  136.370660] i2c-designware-pci 0000:00:08.0: DW_IC_INTR_MASK:         0x246

                [  136.370732] i2c-designware-pci 0000:00:08.0: DW_IC_RAW_INTR_STAT:     0x10

                [  136.370803] i2c-designware-pci 0000:00:08.0: DW_IC_RX_TL:             0x20

                [  136.370875] i2c-designware-pci 0000:00:08.0: DW_IC_TX_TL:             0x20

                [  136.370946] i2c-designware-pci 0000:00:08.0: DW_IC_ENABLE:            0x1

                [  136.371017] i2c-designware-pci 0000:00:08.0: DW_IC_STATUS:            0x2

                [  136.371088] i2c-designware-pci 0000:00:08.0: DW_IC_TXFLR:             0x1

                [  136.371159] i2c-designware-pci 0000:00:08.0: DW_IC_RXFLR:             0x0

                [  136.371230] i2c-designware-pci 0000:00:08.0: DW_IC_TX_ABRT_SOURCE:    0x0

                [  136.371302] i2c-designware-pci 0000:00:08.0: DW_IC_DATA_CMD:          0xfd

                [  136.371372] i2c-designware-pci 0000:00:08.0: ===============================

                [  136.371475] CPU: 0 PID: 385 Comm: Serial Tainted: G        W  O 3.10.17-poky-edison+ #1

                [  136.371481] Hardware name: Intel Corporation Merrifield/BODEGA BAY, BIOS 542 2015.01.21:18.19.48

                [  136.371488] task: f505b210 ti: f517a000 task.ti: f517a000

                [  136.371548] Stack:

                [  136.371617] Call Trace:

                [  136.372117] Code: b3 ff ff 89 f8 09 d0 80 ce 04 83 ff 02 0f 44 c2 8b 15 54 4b ba c1 89 82 00 b3 ff ff f7 c6 00 02 00 00 74 14 e8 e7 f8 0a 00 56 9d <83>                                                                                   c4 04 5b 5e 5f 5d c3 90 8d 74 26 00 56 9d e8 d1 f4 0a 00 83

                [  136.372142] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G        W  O 3.10.17-poky-edison+ #1

                [  136.372147] Hardware name: Intel Corporation Merrifield/BODEGA BAY, BIOS 542 2015.01.21:18.19.48

                [  136.372155] task: f6c83d30 ti: f6e1e000 task.ti: f6e1e000

                [  136.372217] Stack:

                [  136.372285] Call Trace:

                [  136.372496] Code: 8b 42 08 a8 08 75 24 31 c9 8d 42 08 89 ca 0f 01 c8 0f ae f0 89 f6 89 e0 25 00 e0 ff ff 8b 40 08 a8 08 75 07 b1 01 89 f0 0f 01 c9 <85>                                                                                   1d 18 b4 bd c1 75 0d 8d 55 f0 b8 05 00 00 00 e8 cd 45 d8 ff

                [  136.373127] i2c-1: try to abort xfer, scl_gpio 19, sda_gpio 20

                [  136.374980] i2c-1: scl_gpio val 1, sda_gpio val 0

                [  136.375063] i2c-1: toggle begin

                [  136.375235] i2c-1: toggle SCL loop 0

                [  136.375290] i2c-1: scl_gpio val 0, sda_gpio val 1

                [  136.375454] i2c-1: toggle SCL loop 1

                [  136.375509] i2c-1: scl_gpio val 0, sda_gpio val 1

                [  136.375673] i2c-1: toggle SCL loop 2

                [  136.375728] i2c-1: scl_gpio val 0, sda_gpio val 1

                [  136.375899] i2c-1: toggle SCL loop 3

                [  136.375954] i2c-1: scl_gpio val 0, sda_gpio val 1

                [  136.376125] i2c-1: toggle SCL loop 4

                [  136.376290] i2c-1: toggle SCL loop 5

                [  136.376345] i2c-1: scl_gpio val 0, sda_gpio val 1

                [  136.376515] i2c-1: toggle SCL loop 6

                [  136.376571] i2c-1: scl_gpio val 0, sda_gpio val 1

                [  136.376733] i2c-1: toggle SCL loop 7

                [  136.376788] i2c-1: scl_gpio val 0, sda_gpio val 1

                [  136.376959] i2c-1: toggle SCL loop 8

                [  136.377007] i2c-1: toggle end

                • 5. Re: I2C connection getting unstable
                  ankur2

                  Hi cbradley4466,

                  Did you manage to solve this issue? I am having the same problem with Sparkfun blocks for Edison.

                   

                  Thanks

                  Ankur

                  • 6. Re: I2C connection getting unstable
                    Paul_B

                    me either..