Issue with I2C at startup

[VCozz]

Hi,

I've flashed my Intel Edison (with breakout board) with the latest Yocto release grabbed from https://software.intel.com/en-us/iot/hardware/edison/downloads Downloads for Intel® Edison Module | IoT | Intel® Software but I see the following error in the serial console as soon as the board starts (the error is non-blocking, the board reaches the login prompt):

SCU IPC: 0x800000d0 0xfffce92c

PSH miaHOB version: TNG.B0.VVBD.0000000c

microkernel built 11:24:08 Feb 5 2015

******* PSH loader *******

PCM page cache size = 192 KB

Cache Constraint = 0 Pages

Arming IPC driver ..

Adding page store pool ..

PagestoreAddr(IMR Start Address) = 0x04899000

pageStoreSize(IMR Size) = 0x00080000

*** Ready to receive application ***

U-Boot 2014.04 (Jun 06 2016 - 14:40:07)

Watchdog enabled

DRAM: 980.6 MiB

MMC: tangier_sdhci: 0

In: serial

Out: serial

Err: serial

Hit any key to stop autoboot: 0

Target:blank

Partitioning already done...

Flashing already done...

GADGET DRIVER: usb_dnl_dfu

reading vmlinuz

5461344 bytes read in 135 ms (38.6 MiB/s)

Valid Boot Flag

Setup Size = 0x00003c00

Magic signature found

Using boot protocol version 2.0c

Linux kernel version 3.10.98-poky-edison+ (neck@flax) # 1 SMP PREEMPT Mon Jun 6 14:32:08 PDT 2016

Building boot_params at 0x00090000

Loading bzImage at address 00100000 (5445984 bytes)

Magic signature found

Kernel command line: "rootwait root=PARTUUID=012b3303-34ac-284d-99b4-34e03a2335f4 rootfstype=ext4 console=ttyMFD2 earlyprintk=ttyMFD2,keep loglevel=4 g_multi.ethernet_config=rndis systemd.unit=multi-user.target hardware_id=00 g_multi.iSerialNumber=3b70a810440e21d5ac3373d88369189c g_multi.dev_addr=02:00:86:69:18:9c platform_mrfld_audio.audio_codec=dummy"

Starting kernel ...

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

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

[ 3.736726] i2c-designware-pci 0000:00:08.0: DW_IC_TAR: 0x20

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

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

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

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

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

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

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

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

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

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

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

[ 3.737623] i2c-designware-pci 0000:00:08.0: DW_IC_TXFLR: 0x3

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

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

[ 3.737844] i2c-designware-pci 0000:00:08.0: DW_IC_DATA_CMD: 0x0

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

[ 3.738027] CPU: 1 PID: 1 Comm: swapper/0 Tainted: G W 3.10.98-poky-edison+ # 1

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

[ 3.738040] task: f6880000 ti: f6888000 task.ti: f6888000

[ 3.738102] Stack:

[ 3.738173] Call Trace:

[ 3.739168] Code: 10 b3 ff ff 89 f8 09 d0 80 ce 04 83 ff 02 0f 45 d0 a1 d4 32 be c1 89 90 00 b3 ff ff f7 c6 00 02 00 00 74 15 e8 50 65 0b 00 56 9d <83> c4 04 5b 5e 5f 5d c3 8d b6 00 00 00 00 56 9d e8 69 68 0b 00

[ 3.739190] CPU: 0 PID: 0 Comm: swapper/0 Tainted: G W 3.10.98-poky-edison+ # 1

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

[ 3.739203] task: c1bda1c0 ti: c1bd4000 task.ti: c1bd4000

[ 3.739266] Stack:

[ 3.739338] Call Trace:

[ 3.739531] Code: e9 7c fe ff ff 66 90 66 90 55 89 e5 57 56 53 3e 8d 74 26 00 e8 70 ce 2d 00 89 c7 a1 7c ce c6 c1 85 c0 75 25 e8 10 0e 0d 00 fb f4 59 ce 2d 00 89 c7 a1 7c ce c6 c1 85 c0 75 5e 5b 5e 5f 5d c3

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

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

[ 3.754724] i2c-1: toggle begin

[ 3.754883] i2c-1: toggle SCL loop 0

[ 3.755041] i2c-1: toggle SCL loop 1

[ 3.755202] i2c-1: toggle SCL loop 2

[ 3.755361] i2c-1: toggle SCL loop 3

[ 3.755521] i2c-1: toggle SCL loop 4

[ 3.755679] i2c-1: toggle SCL loop 5

[ 3.755831] i2c-1: toggle SCL loop 6

[ 3.755990] i2c-1: toggle SCL loop 7

[ 3.756141] i2c-1: toggle SCL loop 8

[ 3.756186] i2c-1: toggle end

[ 3.756558] pca953x 1-0020: failed reading register

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

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

[ 6.756138] i2c-designware-pci 0000:00:08.0: DW_IC_TAR: 0x21

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

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

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

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

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

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

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

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

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

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

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

[ 6.756953] i2c-designware-pci 0000:00:08.0: DW_IC_TXFLR: 0x3

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

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

[ 6.757154] i2c-designware-pci 0000:00:08.0: DW_IC_DATA_CMD: 0x0

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

[ 6.757320] CPU: 0 PID: 0 Comm: swapper/0 Tainted: G W 3.10.98-poky-edison+ # 1

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

[ 6.757333] task: c1bda1c0 ti: c1bd4000 task.ti: c1bd4000

[ 6.757395] Stack:

[ 6.757466] Call Trace:

[ 6.757657] C...

[idata]

Hi Vit,

Are you having the same issue with previous images? I would like to know if this hardware or software related, so if you could load a previous image onto your Edison and try again I would appreciate it.It would also be a good idea to try with I2C6 and see if the Edison crashes too, have you tried that?Regards,-Pablo

[VCozz]

Hi,

I receive the exact same error on the previous version. Additionally, if I run i2cdetect -y -r 6 the board doesn't crashes but I don't see any device connected after I try to plug-in a sensor (the sensor itself is working without problems on other boards).

At this point I'm starting to believe that I'm facing an hardware problem.

Cheers,

Vittorio

[idata]

Hi Vittorio,

Thank you for your answers.I've been running some tests myself and haven't been able to reproduce your issue. So that makes me think that this is hardware related, as you also mentioned. Right now, just to discard any other issue, I would like to know how you're powering the Breakout board, could you please show/explaining us your configuration? Do you have something connected to the board when booting or just wait for the board to end the booting process and then connect the sensor?I would like you to try changing USB cables and computer ports in case you're connecting it this way.Regards,-Pablo

[VCozz]

Hi,

I've madte my tests without anything connected to the board, just the power adapter and the USB cable for the serial connection. I plugged in the sensor only after the boot-up phase. Moreover, I have used the same USB cable and power adapter for different Intel Edison boards without any problems.

Cheers,

Vittorio

[idata]

Hi Vit,

Thank you very much for the information.Please go ahead and open a ticket using this link https://customercare.intel.com/?lang=en-US https://customercare.intel.com/?lang=en-US, explain in the Description field of the ticket your issue and paste the link to this thread, this seems to be a warranty issue.Regards,-Pablo