From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: linux-i2c@vger.kernel.org
Subject: Re: can't write more than one byte to AT24C64 EEPROM using "eeprog"
Date: Wed, 26 Jul 2017 14:30:33 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.20.1707261427010.32595@localhost.localdomain> (raw)
In-Reply-To: <alpine.LFD.2.20.1707251344110.20856@localhost.localdomain>
i've tossed all the previous post since it appears(?) i've
discovered the issue, which is explained here:
https://www.toradex.com/community/questions/10243/write-issue-with-eeprog-in-eeprom.html
if i read that correctly, "eeprog" is not leaving anywhere *near*
enough time for a byte write to complete, with a patch suggested here:
https://share.toradex.com/s07bedxtxfdc4wj?direct
that cranks up the wait period from 10 usec to 5 msec. does this make
sense, since that is *exactly* the symptom i'm seeing.
thoughts? is no one else seeing this issue?
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
next prev parent reply other threads:[~2017-07-26 18:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-25 12:51 can't write more than one byte to AT24C64 EEPROM using "eeprog" rpjday
2017-07-25 17:51 ` Robert P. J. Day
2017-07-26 18:30 ` Robert P. J. Day [this message]
2017-07-26 20:57 ` Wolfram Sang
2017-07-26 21:31 ` Robert P. J. Day
2017-07-26 21:57 ` Wolfram Sang
2017-07-27 8:40 ` Robert P. J. Day
2017-07-27 9:34 ` Wolfram Sang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LFD.2.20.1707261427010.32595@localhost.localdomain \
--to=rpjday@crashcourse.ca \
--cc=linux-i2c@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).