7 Replies Latest reply on Jun 3, 2015 6:47 PM by hopstone

    i2c crash

    hopstone

      Hi,

      I2c is so easy to crash on Edison platform, following is the log. I'm using edison-image-ww05-15. Does anyone know how to fix it? Thanks a lot.

       

      [  776.483732] i2c-designware-pci 0000:00:09.1: ===== REGISTER DUMP (i2c) =====

      [  776.483831] i2c-designware-pci 0000:00:09.1: DW_IC_CON:               0x65

      [  776.483906] i2c-designware-pci 0000:00:09.1: DW_IC_TAR:               0x48

      [  776.483979] i2c-designware-pci 0000:00:09.1: DW_IC_SS_SCL_HCNT:       0x2f8

      [  776.484052] i2c-designware-pci 0000:00:09.1: DW_IC_SS_SCL_LCNT:       0x37b

      [  776.484124] i2c-designware-pci 0000:00:09.1: DW_IC_FS_SCL_HCNT:       0x87

      [  776.484196] i2c-designware-pci 0000:00:09.1: DW_IC_FS_SCL_LCNT:       0x10a

      [  776.484268] i2c-designware-pci 0000:00:09.1: DW_IC_INTR_STAT:         0x0

      [  776.484339] i2c-designware-pci 0000:00:09.1: DW_IC_INTR_MASK:         0x246

      [  776.484412] i2c-designware-pci 0000:00:09.1: DW_IC_RAW_INTR_STAT:     0x10

      [  776.484483] i2c-designware-pci 0000:00:09.1: DW_IC_RX_TL:             0x20

      [  776.484555] i2c-designware-pci 0000:00:09.1: DW_IC_TX_TL:             0x20

      [  776.484626] i2c-designware-pci 0000:00:09.1: DW_IC_ENABLE:            0x1

      [  776.484697] i2c-designware-pci 0000:00:09.1: DW_IC_STATUS:            0x2

      [  776.484769] i2c-designware-pci 0000:00:09.1: DW_IC_TXFLR:             0x3

      [  776.484840] i2c-designware-pci 0000:00:09.1: DW_IC_RXFLR:             0x0

      [  776.484911] i2c-designware-pci 0000:00:09.1: DW_IC_TX_ABRT_SOURCE:    0x0

      [  776.484982] i2c-designware-pci 0000:00:09.1: DW_IC_DATA_CMD:          0x0

      [  776.485052] i2c-designware-pci 0000:00:09.1: ===============================

      [  776.485155] CPU: 0 PID: 341 Comm: battery Tainted: G        W  O 3.10.17-poky-edison+ #1

      [  776.485160] Hardware name: Intel Corporation Merrifield/BODEGA BAY, BIOS 466 2014.06.23:19.20.05

      [  776.485167] task: f50d4850 ti: f56f6000 task.ti: f56f6000

      [  776.485228] Stack:

      [  776.485296] Call Trace:

      [  776.485736] Code: b3 ff ff 89 f8 09 d0 80 ce 04 83 ff 02 0f 44 c2 8b 15 54 4b b9 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

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

      [  776.485766] Hardware name: Intel Corporation Merrifield/BODEGA BAY, BIOS 466 2014.06.23:19.20.05

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

      [  776.485836] Stack:

      [  776.485905] Call Trace:

      [  776.486114] 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 58 a6 bc c1 75 0d 8d 55 f0 b8 05 00 00 00 e8 bd 31 d9 ff

      [  776.486745] i2c-6: recovery ignore

        • 1. Re: i2c crash
          Intel_Peter

          Hello hopstone,

           

          When does your Edison crash? Which device are you trying to communicate to?

          How is it being powered? I was just testing if my Edison could detect an I2C device with the command "i2cdetect -y -r 6". And I noticed that I was getting the same crash message as you. However I was powering the board (and my I2C device) with my USB cable. I then changed to a power supply and now my Edison can detect the device as it should. Maybe you are experiencing a similar issue, why don't you try it out?

           

          Peter.

          • 2. Re: i2c crash
            hopstone

            Hi Peter,

            Thanks for your quick reply. It will crash after several minutes when reading battery value( ADS1014 ) and flash red led( PCAL9555 ) periodically, both of them using I2c. I've tried both battery and power supply, and it crashed.

            • 3. Re: i2c crash
              Intel_Peter

              How much power is your PSU and battery able to supply?

               

              Peter.

              • 4. Re: i2c crash
                hopstone

                Hi Peter,

                I'm using a 3.8v battery, and external power supply is about 3.9v.

                • 5. Re: i2c crash
                  Intel_Peter

                  Hello hopstone,

                   

                  Sorry, I meant how many amp-hour are they able to supply? You are using the mini breakout board, right? How are you powering the I2C device?

                  I used a 1.2A PSU, that way that error message stopped appearing, maybe if you use a similar one the may disappear. Try it and let us know.

                   

                  Peter.

                  • 6. Re: i2c crash
                    CMata_Intel

                    Hi hopstone

                     

                    Do you have updates in this? Are you still having problems with I2C?

                    If you do, have you tried with a similar battery like the one Peter suggested?

                     

                     

                    Regards;

                    CMata

                    • 7. Re: i2c crash
                      hopstone

                      Hi,

                      Sorry for late feedback, we found it's interfered by power line on our own board. Thank all of you!