i2c bus hangs in master RPi access to MSP430G uC ~1 in 1000 accesses Announcing the arrival of...
Is there hard evidence that the grant peer review system performs significantly better than random?
Simple Line in LaTeX Help!
A term for a woman complaining about things/begging in a cute/childish way
Simple HTTP Server
Can you force honesty by using the Speak with Dead and Zone of Truth spells together?
"klopfte jemand" or "jemand klopfte"?
Can an iPhone 7 be made to function as a NFC Tag?
Special flights
In musical terms, what properties are varied by the human voice to produce different words / syllables?
Sally's older brother
The Nth Gryphon Number
What would you call this weird metallic apparatus that allows you to lift people?
What does Turing mean by this statement?
What order were files/directories output in dir?
How much damage would a cupful of neutron star matter do to the Earth?
Resize vertical bars (absolute-value symbols)
Delete free apps from library
Why is the change of basis formula counter-intuitive? [See details]
How to change the tick of the color bar legend to black
i2c bus hangs in master RPi access to MSP430G uC ~1 in 1000 accesses
What is the role of と after a noun when it doesn't appear to count or list anything?
What does it mean that physics no longer uses mechanical models to describe phenomena?
Can two people see the same photon?
Mounting TV on a weird wall that has some material between the drywall and stud
i2c bus hangs in master RPi access to MSP430G uC ~1 in 1000 accesses
Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 23, 2019 at 23:30 UTC (7:30pm US/Eastern)
Congratulation Joan for 50k!How to unbind i2c bus 0 from the i2c driver?Rpi Slave and Arduino MasterHow do I use the I2C bus?i2c requires restart before bus accessI2C Bus voltagepigpio: Bad I2C Busi2c dtoverlay bus numberEnabling Second I2C BUS Causes crashRPi I2C Master vs. slave with ArduinoI2C bus 0 not working, I2C bus 1 is
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
... resetting the MSP430 clears the hung state. I've slowed down the i2c clock freq, beefed up the PSupply, changed pull-up resistors - no change. However I made the "errors" increase significantly by busying the ARM with 2 calculation-intensive programs. I use Python in RPi, using smbus, SMBUS and
i2c_LCD_driver and try/except routines in the RPi to catch the bad access and reset the MSP - after that, accesses every 5 seconds continue fine until the next hang, ~1000 accesses later. I use C for the ISRs to manage interrupts in the MSP430.
I know both devices have hardware state machines that manage the i2c. Given that I can hang the bus by overworking the RPi, my suspicion was/is the implementation of the canned i2c python code. Is anyone aware of any weird
stuff about the Broadcom Serial Controller (BSC) i2c controller in the ARM that would hang a slave's state machine based on busy-ness of the OS managing the BSC ... or other cases of very intermittent bus hangs ?
i2c
New contributor
add a comment |
... resetting the MSP430 clears the hung state. I've slowed down the i2c clock freq, beefed up the PSupply, changed pull-up resistors - no change. However I made the "errors" increase significantly by busying the ARM with 2 calculation-intensive programs. I use Python in RPi, using smbus, SMBUS and
i2c_LCD_driver and try/except routines in the RPi to catch the bad access and reset the MSP - after that, accesses every 5 seconds continue fine until the next hang, ~1000 accesses later. I use C for the ISRs to manage interrupts in the MSP430.
I know both devices have hardware state machines that manage the i2c. Given that I can hang the bus by overworking the RPi, my suspicion was/is the implementation of the canned i2c python code. Is anyone aware of any weird
stuff about the Broadcom Serial Controller (BSC) i2c controller in the ARM that would hang a slave's state machine based on busy-ness of the OS managing the BSC ... or other cases of very intermittent bus hangs ?
i2c
New contributor
add a comment |
... resetting the MSP430 clears the hung state. I've slowed down the i2c clock freq, beefed up the PSupply, changed pull-up resistors - no change. However I made the "errors" increase significantly by busying the ARM with 2 calculation-intensive programs. I use Python in RPi, using smbus, SMBUS and
i2c_LCD_driver and try/except routines in the RPi to catch the bad access and reset the MSP - after that, accesses every 5 seconds continue fine until the next hang, ~1000 accesses later. I use C for the ISRs to manage interrupts in the MSP430.
I know both devices have hardware state machines that manage the i2c. Given that I can hang the bus by overworking the RPi, my suspicion was/is the implementation of the canned i2c python code. Is anyone aware of any weird
stuff about the Broadcom Serial Controller (BSC) i2c controller in the ARM that would hang a slave's state machine based on busy-ness of the OS managing the BSC ... or other cases of very intermittent bus hangs ?
i2c
New contributor
... resetting the MSP430 clears the hung state. I've slowed down the i2c clock freq, beefed up the PSupply, changed pull-up resistors - no change. However I made the "errors" increase significantly by busying the ARM with 2 calculation-intensive programs. I use Python in RPi, using smbus, SMBUS and
i2c_LCD_driver and try/except routines in the RPi to catch the bad access and reset the MSP - after that, accesses every 5 seconds continue fine until the next hang, ~1000 accesses later. I use C for the ISRs to manage interrupts in the MSP430.
I know both devices have hardware state machines that manage the i2c. Given that I can hang the bus by overworking the RPi, my suspicion was/is the implementation of the canned i2c python code. Is anyone aware of any weird
stuff about the Broadcom Serial Controller (BSC) i2c controller in the ARM that would hang a slave's state machine based on busy-ness of the OS managing the BSC ... or other cases of very intermittent bus hangs ?
i2c
i2c
New contributor
New contributor
New contributor
asked 2 hours ago
JoeMJoeM
161
161
New contributor
New contributor
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Question
... I've slowed down the i2c clock freq ...
Answer
I am using RPi3B+ stretch 2019apr python 3.5.3.
I surprisingly and sadly experienced, and read that Rpi3B+ stretch python 3.5x I2C is buggy.
I could never have slowed down the default I2C 100kHz. I tried to change speed up to 400kHz and down to 50kHz. But hardware did not respond - no nothing changed. :(
I read that it is a hardware bug. Are you sure you have actually successfully changed the speed? I vaguely remember that I could indeed change the speed when I was in jessie or earlier days.
I also found that python 3.5.3 block read does not fully implement to entertain all the parameter patterns. My projects were "hung" and much time wasted. :(
I am anxiously waiting for the coming soon Rpi4 to hopefully resume my couple of long stalled I2C related projects. In the meaning time I am switching to SPI (I2C MCP23017 to SPI MCP23S17, etc)
Update 2019apr21hkt1156
I did try smbus2 but sadly encountered other compatibility problems. :(
References
Rpi3 I2C Baud Rate Setting - samtal 2018aug04
/ to continue, ...
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
return StackExchange.using("schematics", function () {
StackExchange.schematics.init();
});
}, "cicuitlab");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "447"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
JoeM is a new contributor. Be nice, and check out our Code of Conduct.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fraspberrypi.stackexchange.com%2fquestions%2f96748%2fi2c-bus-hangs-in-master-rpi-access-to-msp430g-uc-1-in-1000-accesses%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Question
... I've slowed down the i2c clock freq ...
Answer
I am using RPi3B+ stretch 2019apr python 3.5.3.
I surprisingly and sadly experienced, and read that Rpi3B+ stretch python 3.5x I2C is buggy.
I could never have slowed down the default I2C 100kHz. I tried to change speed up to 400kHz and down to 50kHz. But hardware did not respond - no nothing changed. :(
I read that it is a hardware bug. Are you sure you have actually successfully changed the speed? I vaguely remember that I could indeed change the speed when I was in jessie or earlier days.
I also found that python 3.5.3 block read does not fully implement to entertain all the parameter patterns. My projects were "hung" and much time wasted. :(
I am anxiously waiting for the coming soon Rpi4 to hopefully resume my couple of long stalled I2C related projects. In the meaning time I am switching to SPI (I2C MCP23017 to SPI MCP23S17, etc)
Update 2019apr21hkt1156
I did try smbus2 but sadly encountered other compatibility problems. :(
References
Rpi3 I2C Baud Rate Setting - samtal 2018aug04
/ to continue, ...
add a comment |
Question
... I've slowed down the i2c clock freq ...
Answer
I am using RPi3B+ stretch 2019apr python 3.5.3.
I surprisingly and sadly experienced, and read that Rpi3B+ stretch python 3.5x I2C is buggy.
I could never have slowed down the default I2C 100kHz. I tried to change speed up to 400kHz and down to 50kHz. But hardware did not respond - no nothing changed. :(
I read that it is a hardware bug. Are you sure you have actually successfully changed the speed? I vaguely remember that I could indeed change the speed when I was in jessie or earlier days.
I also found that python 3.5.3 block read does not fully implement to entertain all the parameter patterns. My projects were "hung" and much time wasted. :(
I am anxiously waiting for the coming soon Rpi4 to hopefully resume my couple of long stalled I2C related projects. In the meaning time I am switching to SPI (I2C MCP23017 to SPI MCP23S17, etc)
Update 2019apr21hkt1156
I did try smbus2 but sadly encountered other compatibility problems. :(
References
Rpi3 I2C Baud Rate Setting - samtal 2018aug04
/ to continue, ...
add a comment |
Question
... I've slowed down the i2c clock freq ...
Answer
I am using RPi3B+ stretch 2019apr python 3.5.3.
I surprisingly and sadly experienced, and read that Rpi3B+ stretch python 3.5x I2C is buggy.
I could never have slowed down the default I2C 100kHz. I tried to change speed up to 400kHz and down to 50kHz. But hardware did not respond - no nothing changed. :(
I read that it is a hardware bug. Are you sure you have actually successfully changed the speed? I vaguely remember that I could indeed change the speed when I was in jessie or earlier days.
I also found that python 3.5.3 block read does not fully implement to entertain all the parameter patterns. My projects were "hung" and much time wasted. :(
I am anxiously waiting for the coming soon Rpi4 to hopefully resume my couple of long stalled I2C related projects. In the meaning time I am switching to SPI (I2C MCP23017 to SPI MCP23S17, etc)
Update 2019apr21hkt1156
I did try smbus2 but sadly encountered other compatibility problems. :(
References
Rpi3 I2C Baud Rate Setting - samtal 2018aug04
/ to continue, ...
Question
... I've slowed down the i2c clock freq ...
Answer
I am using RPi3B+ stretch 2019apr python 3.5.3.
I surprisingly and sadly experienced, and read that Rpi3B+ stretch python 3.5x I2C is buggy.
I could never have slowed down the default I2C 100kHz. I tried to change speed up to 400kHz and down to 50kHz. But hardware did not respond - no nothing changed. :(
I read that it is a hardware bug. Are you sure you have actually successfully changed the speed? I vaguely remember that I could indeed change the speed when I was in jessie or earlier days.
I also found that python 3.5.3 block read does not fully implement to entertain all the parameter patterns. My projects were "hung" and much time wasted. :(
I am anxiously waiting for the coming soon Rpi4 to hopefully resume my couple of long stalled I2C related projects. In the meaning time I am switching to SPI (I2C MCP23017 to SPI MCP23S17, etc)
Update 2019apr21hkt1156
I did try smbus2 but sadly encountered other compatibility problems. :(
References
Rpi3 I2C Baud Rate Setting - samtal 2018aug04
/ to continue, ...
edited 52 mins ago
answered 1 hour ago
tlfong01tlfong01
832312
832312
add a comment |
add a comment |
JoeM is a new contributor. Be nice, and check out our Code of Conduct.
JoeM is a new contributor. Be nice, and check out our Code of Conduct.
JoeM is a new contributor. Be nice, and check out our Code of Conduct.
JoeM is a new contributor. Be nice, and check out our Code of Conduct.
Thanks for contributing an answer to Raspberry Pi Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fraspberrypi.stackexchange.com%2fquestions%2f96748%2fi2c-bus-hangs-in-master-rpi-access-to-msp430g-uc-1-in-1000-accesses%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown