??? 09/20/05 03:42 Read: times |
#101240 - Hello Mehdi Responding to: ???'s previous message |
Yep I've hacked the code apart multiple different ways and still can't see the its working with the I2C device I've got.
I only mentioned it in case there were some other routines not quite I2C compliant possibly. Like I said I've modified the way that I interepreted what was required, and it hasn't helped either. |
Topic | Author | Date |
Using IIC.ASM | 01/01/70 00:00 | |
address, speed | 01/01/70 00:00 | |
Yes | 01/01/70 00:00 | |
two things | 01/01/70 00:00 | |
Is HW I2C easier? | 01/01/70 00:00 | |
That may have been true then, this is no | 01/01/70 00:00 | |
Replies. | 01/01/70 00:00 | |
Check SBCMON | 01/01/70 00:00 | |
SBCMON | 01/01/70 00:00 | |
try a serial memory | 01/01/70 00:00 | |
let us try another tack | 01/01/70 00:00 | |
another tack. | 01/01/70 00:00 | |
you have created just about the worst co | 01/01/70 00:00 | |
Worst conditions. | 01/01/70 00:00 | |
oscilloscope | 01/01/70 00:00 | |
oscilloscope | 01/01/70 00:00 | |
To verify that your programming ("burnin | 01/01/70 00:00 | |
verifying. | 01/01/70 00:00 | |
Without a scope you are kind of stuck, s | 01/01/70 00:00 | |
Success.![]() | 01/01/70 00:00 | |
back to the roots | 01/01/70 00:00 | |
Success. | 01/01/70 00:00 | |
To Mike! | 01/01/70 00:00 | |
Hello Mehdi | 01/01/70 00:00 | |
Or... | 01/01/70 00:00 | |
this is a bootleg, use the original | 01/01/70 00:00 | |
i2cbits | 01/01/70 00:00 | |
you may want to go here | 01/01/70 00:00 | |
Clock width is only 2 uSec in IIC_ASM ex | 01/01/70 00:00 |