I2C and Motorola HC08
I2C and Motorola HC08
Hello everyone.
I have a LK202-25-R-V that I m trying to write to over the I2C bus using a Motorola M68HC908JK3CP. My code is written in assembly and is based exactly on the ping.be website MO recommends. I have read all the information on this forum that I can regarding I2C, however I still cannot get the display to display anything properly. I noticed on the manual that it says that the I2C bus runs "at 100 kBps." Now here is my question, does this mean that I have to output data over the bus at 100 kBps? And did you mean 100 kByte/s or 100 kbit/s? I thought that I2C allowed you to run basically any baud rate you desired since the master device provided the clock. I have interfaced this same microcontroller to temperature probes and real-time clocks over I2C with a good deal of success, but this display has me scrathing my head. Can anybody answer these questions for me? Thanks
I have a LK202-25-R-V that I m trying to write to over the I2C bus using a Motorola M68HC908JK3CP. My code is written in assembly and is based exactly on the ping.be website MO recommends. I have read all the information on this forum that I can regarding I2C, however I still cannot get the display to display anything properly. I noticed on the manual that it says that the I2C bus runs "at 100 kBps." Now here is my question, does this mean that I have to output data over the bus at 100 kBps? And did you mean 100 kByte/s or 100 kbit/s? I thought that I2C allowed you to run basically any baud rate you desired since the master device provided the clock. I have interfaced this same microcontroller to temperature probes and real-time clocks over I2C with a good deal of success, but this display has me scrathing my head. Can anybody answer these questions for me? Thanks
The 100kBps is meant that the display can communicate at 100k bits/second. You do not have to communicate at 100kBps. The 100KBps is the maximum bitrate the displays can communicate at, so you do not need to communicate at 100kBps.
Make sure you have the right addressing for the displays too. You might have read the information in this link already, just in case, the guide for I2C communication is at http://www.lcdforums.com/forums/viewtopic.php?t=910.
I hope it works out for you.
Best Regards,
Make sure you have the right addressing for the displays too. You might have read the information in this link already, just in case, the guide for I2C communication is at http://www.lcdforums.com/forums/viewtopic.php?t=910.
I hope it works out for you.
Best Regards,

Thanks for clearing up the Byte vs. bit issue. I was taught that a B means Byte and a b means bit so I was a tad confused.
I have read the I2C guide you provided, but it seems my display will respond to addresses that are not meant for it. I have been using the 0x50 address and get garbage characters out, but for trouble shooting changed the address to 0x60. The display still responded and outputted different garbage characters.
Any ideas?!?


Any ideas?!?
Hi,
For the LK202-25 rev 1.5, you wouldn't need any jumper settings to communicate via I2C. If you have revision 2.0 and up, you will need to remove two jumpers that is labeled 232, and solder two other jumpers labeled I^2C.
Here is a good sample c code for I2C communication at http://www.lcdforums.com/forums/viewtop ... a&start=15.
It isn't assember, but the idea is similar.
I hope this helps you out.
Best Regards,
For the LK202-25 rev 1.5, you wouldn't need any jumper settings to communicate via I2C. If you have revision 2.0 and up, you will need to remove two jumpers that is labeled 232, and solder two other jumpers labeled I^2C.
Here is a good sample c code for I2C communication at http://www.lcdforums.com/forums/viewtop ... a&start=15.
It isn't assember, but the idea is similar.
I hope this helps you out.
Best Regards,
Here is what I am trying to do, the microcontroller would communicate with the display over the I2C lines, and then would shut itself off, then a PC would communicate with the display over the RS-232 lines. So you are telling me this is not possible, right?
So, since the traces use the same data lines, the RS-232 chip would be connected to your controller as would the I2C at the same time right?
I apologize if I am being redundant, but when I ordered the display I was under the impression from the display's website that I would be able to run both protocols. I'm just tryig to get things straight beore I ruin a perfectly good display.
Thanks again for all you help and patience.
~David
So, since the traces use the same data lines, the RS-232 chip would be connected to your controller as would the I2C at the same time right?
I apologize if I am being redundant, but when I ordered the display I was under the impression from the display's website that I would be able to run both protocols. I'm just tryig to get things straight beore I ruin a perfectly good display.
Thanks again for all you help and patience.
~David
What you can do is have the normal RS-232 jumpers soldered, and have the display power normally through the power connector. You can then stick two wires on the left side of the I2C jumper. You can use the two vias beside the I2C jumper pad or the actual jumper pad. The top jumper is SCL, and the bottom jumper is SDA. DO NOT solder the I2C jumpers together, if you have the RS-232 jumpers on, or you can damage the pic.
For RS-232 you can talk normally via the DB-9.
This configuration should work out for you.
Best Regards,
For RS-232 you can talk normally via the DB-9.
This configuration should work out for you.
Best Regards,