Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Yi_S_Intel
Employee
3,409 Views

Critial Issue: Edison I2C crash

Hi,

I'm trying to read mpu6050 data by the I2C bus, but the I2C bus is likely very unstable.

Sometimes it is crashed and never recovered, unless re-plug in power.

This issue can be reproduced 100%.

 

Attachment is the log when I2C is crashed.

I'm using edison-image-ww25.5-15, but not sure it's the latest version.

I search on page https://software.intel.com/en-us/iot/hardware/edison/downloads https://software.intel.com/en-us/iot/hardware/edison/downloads

Likely 25.5 is the latest one.

Any further info anyone needs, feel free let me know.

Thanks

--Sun, Yi

16 Replies
Sergio_A_Intel
Employee
167 Views

Hi ysun,

Yes, other users have reported issues with I2C as well. This issues are mostly on release 2.1 but not in 2.0. I'd suggest you to flash your board with the 2.0 image release. It can be found here https://software.intel.com/en-us/iot/hardware/edison/downloads IoT - Intel® Edison Board Download | Intel® Developer Zone .

You can see more information here

Sergio

Yi_S_Intel
Employee
167 Views

Thank Alvarado for your reply.

But from the "i2c bus freezes randomly", this bug is reported from Aug, 2015. Do you have schedule to fix it?

Just telling customer rolling back to version 2.0 is very bad I think, because IIC is so common for a IOT device.

Looking forward your bug fix!

Thanks

--Sun, Yi

Yi_S_Intel
Employee
167 Views

Hi Alvarado,

Could you tell me the update information from version 2.0 to 2.1.

I have to use IIC but I'm concerned to introduce some other issue once I change v2.1 to 2.0.

Thanks.

--Sun, Yi

Sergio_A_Intel
Employee
167 Views

Can you please provide us the code you're using so we can try to replicate this issue? Also send us any other detail you consider necessary for reproduction. If you'd like you can send me the code through a private message.

Sergio

Yi_S_Intel
Employee
167 Views

Thanks Alvarado for your reply!

It's a very simple demo, and you can get it from:

https://github.com/ysun/EdisonGY521.git https://github.com/ysun/EdisonGY521.git

After compiling source file src/Runner.cpp, you only run the binary parallelly in two terminals.

Then the i2c can be frozen.

Not sure whether that's enough, anything you need, feel free ping me.

Thanks

--Sun, Yi

Sergio_A_Intel
Employee
167 Views

Hi ysun,

We wanted to let you know we've ordered the sensor and will some tests once it arrives. Please be patient.

Sergio

Yi_S_Intel
Employee
167 Views

Thanks Alvarado,

Nice to know you're looking into it.

And looking forward your root cause.

If anything I can do for you, feel free ping me.

 

Thanks

--Sun, Yi

Yi_S_Intel
Employee
167 Views

Hi Alvarado,

Just follow the progress. What's the status now.

Thanks

--Sun, Yi

Sergio_A_Intel
Employee
167 Views

Hi ysun,

We're still waiting for the sensor to arrive. Once the sensor arrives, we'll try and reproduce your case right away.

Sergio

Sergio_A_Intel
Employee
167 Views

We are unable to read the sensor with the code you linked (https://github.com/ysun/EdisonGY521 https://github.com/ysun/EdisonGY521). We are able to compile and run the code but the sensor readings are 0's, Is this the same behavior you are seeing? The Edison board has the latest image (159.devkit) and the sensor has the following connections:

MPU6050 Edison

VCC <-> 3.3V

GND <-> GND

SCL <-> SCL

SDA <-> SDA

We are using the Intel Edison Arduino Expansion board with 12V power supply. Is there anything different from our setup to yours?

root@Edison:~# ./mpu6050-new

WELCOME TO MPU6050 MARK 2

SAMPLE RATE IS:8 kHz

GYRO CONFIG:8

Calibration values:x_accel: 0 y_accel: 0 z_accel: 0 temperature: 36.53 x_gyro: 0 y_gyro: 0 z_gyro: 0

Current reading:x_accel: 0 y_accel: 0 z_accel: 0 temperature: 36.53 x_gyro: 0 y_gyro: 0 z_gyro: 0

Raw values:x_accel: 0 y_accel: 0 z_accel: 0 temperature: 36.53 x_gyro: 0 y_gyro: 0 z_gyro: 0

Calibrrated values:x_accel: 0 y_accel: 0 z_accel: 0 temperature: 36.53 x_gyro: 0 y_gyro: 0 z_gyro: 0

Raw values:x_accel: 0 y_accel: 0 z_accel: 0 temperature: 36.53 x_gyro: 0 y_gyro: 0 z_gyro: 0

Calibrrated values:x_accel: 0 y_accel: 0 z_accel: 0 temperature: 36.53 x_gyro: 0 y_gyro: 0 z_gyro: 0

Raw values:x_accel: 0 y_accel: 0 z_accel: 0 temperature: 36.53 x_gyro: 0 y_gyro: 0 z_gyro: 0

Calibrrated values:x_accel: 0 y_accel: 0 z_accel: 0 temperature: 36.53 x_gyro: 0 y_gyro: 0 z_gyro: 0

Sergio

Yi_S_Intel
Employee
167 Views

Hi Sergio,

 

The example should work with mpu6050 module, I can double check when I home.

One difference from mine that I was using 5V as MPU6050 vcc. But I guess that module support both 3.3 and 5v.

 

Which intel site are you at? I guess I can mail you my MPU6050 to you by internal mail service, though I don't know the exactly process.

I'm working at PRC shanghai.

 

Thanks

--Sun, Yi

Yi_S_Intel
Employee
167 Views

Hi Sergio,

I recorded one thing! I didn't read the data successfully previously as you.

Hence if you bought the same module, you can connect pin 'AD0' to GND.

Hope that can solve that problem!

Thanks

--Sun, Yi

Sergio_A_Intel
Employee
167 Views

Thank you for providing this additional information. It helped us reproduce the issue. We will submit a bug to the engineering team.

Regards

Sergio

Yi_S_Intel
Employee
167 Views

Hi Sergio,

Glad to know you reproduced that problem!

Is there any place where you tracking bug reports? If so I can follow the status of the issue.

Besides, I can help file other bugs there.

Looking forwarding to the bug fix!

Thanks

--Sun, Yi

Sergio_A_Intel
Employee
167 Views

The bug tracking is not available to anyone outside the direct team. Hopefully the bug fix will be available soon.

Sergio

Yi_S_Intel
Employee
167 Views

Hi Sergio,

It's more than 2 months since I reported this IIC issue. Is it such difficult to fix it?

Or Intel may give up Edison supporting?

it's a little bit disappointing! Nobody else care about Edison IIC?

Besides, I'm also disappoint with the latest v3.0. Likely mraa doesn't work well, either.

.......

GOOD LUCK!

Thanks

--Sun, Yi

Reply