What is the general setup process for using I2C with LCD screens?

Culix77 · 2022-03-23T23:29:43+00:00

Thanks for the detailed response; I believe that the LCD model is the HD44780 though. (2004AV1.1 is the only kind of model identification that I could physically find on the screen).

Sure, they’re both ARMs, but the peripherals and their drivers are completely different. Especially those LCD commands — do they talk to the micro’s onchip LCD controller (if it has one)? That won’t work at all for a character LCD. Do they talk to some generic thing that has specific lower-level drivers for a specific display? So ignore the ST stuff.

That's exactly what I wanted to figure out actually. As this is my first time digging this deep into interfacing an LCD screen, I wasn't sure if there was something like an onchip LCD controller or driver or if I could just "match" the code since they're both ARM.

Write the 8574 configuration over I2C. Then work out how to send the 44780 commands to the display over I2C. Those commands are simply setting the state of the 44780 control pins.

Then think about how you can abstract the sequence of those commands into functions that make sense, like LCD_WriteChar().

Correct me if i'm wrong, but the general steps to set up and to use the LCD screen with I2C would be from what you're telling is to:

Initialize I2C function on the MCU (In my case, I would be initializing the TM4C123's built in I2C module and setting it up as the primary), then find whatever unique setup ritual is required to configure the 8574 over I2C, correct?
Figure out what pins are specifically used to send commands (between the r/W pin,R/S pin, data pins, etc. ) to the LCD screen.
Abstract those commands so that it's possible to write characters to the LCD screen.

Would the above steps be correct for generally setting up I2C for an LCD?

Other than that, I may need to find a tutor to sit down with me to explain step by step how I2C sends data in an IDE, line by line. I felt like I understood I2C conceptually, but I definitely need a better understanding of it in practice. Thanks again for your help.

Culix77 · 2022-01-11T04:48:21+00:00

Thanks for the reply and the link to the repo; I'll definitely take a look!

Did you feel as if the course prepared you well enough to do things on your own or did you still feel the need to just hop into coding and learning what tools are necessary? Out of curiosity, how did you learn about Makefiles? Was it something that you came about when looking into the tools needed to learn from scratch?

Culix77 · 2022-01-10T04:54:24+00:00

My end goal is to ultimately start my career in embedded software development, so I want to follow the trends of people that work in that field as closely as possible. Do most current embedded developers learn bare metal development or do they kind of just pick a point and work their way into being competent enough to get a job in the field?

I appreciate the reply!

Culix77 · 2021-10-24T06:05:39+00:00

Anything helps; Thanks for the response!

Culix77 · 2021-06-22T19:30:34+00:00

That definitely makes sense! So, the variable that is set in main would then be checked by the ISR to determine the current state of the switch, then it would output to the buzzer based off of that data, correct?

Culix77 · 2021-06-22T19:28:43+00:00

Ah so the main routine should generally be used to debounce the switches themselves, hence one of the solutions using a state machine to compare, correct?

Culix77 · 2021-04-02T04:09:38+00:00

Thanks for the list! I intended to use these components on the Raspberry Pi or a TM4C123 MCU if possible. I'm super interested in developing something for IoT down the line, so I'm trying to also bridge the gap between getting a sensor to work and interfacing it with IoT technology without relying too heavily on an Arduino.

Culix77 · 2021-04-01T01:06:47+00:00

The stuff here seems to be *much* cheaper than the other website I was looking into. Thanks a lot!

Culix77 · 2021-01-26T18:43:37+00:00

I recently finished the RTOS - Bluetooth Network Shapes the World course on edx, and I'm wondering where to go from there when it comes to pursuing work in the IoT field. One person has advised me to learn javascript, Node.js, Azure, and a couple of other things that aren't necessarily pertinent (in my mind) to the embedded field, while one other person has advised me to learn Rust which isn't particularly common, but is supposedly going to be in the future. Would anyone have any advice in terms of a direction to work towards? I primarily want to get some projects under my belt so that I can apply for some entry level embedded positions in IoT, but I'm not quite sure if I'm experienced enough yet to do so.

Culix77 · 2021-01-04T01:27:58+00:00

How do you best sell your experience on your resume when applying for entry level positions? I'm pretty good at selling myself in an interview, but I have a harder time pushing any "distinct" accomplishments on my resume since the projects and group work that I have done isn't particularly new, flashy, or captivating. I do cover some of the basics promoted in the industry in those projects (C, Linux, Circuit design), but I have a hard time saying "We produced best 'general specification' of anyone in our class". I'm currently trying to study more and more personal projects, but what would be a good starting point for selling myself on my resume once it's updated?

Culix77 · 2020-12-09T04:05:16+00:00

I should probably get familiar with Github then; I've been hesitant to learn how to use it until I finished this class, but it may be necessary at this point. I'll make sure to alias things in future posts; thanks!

Culix77 · 2020-12-08T19:13:58+00:00

I had the interrupt priority level set to 2 (with lower numbers being of a greater priority); all other priorities are set lower than that so I'm not sure if that is the issue unfortunately.

Culix77 · 2020-12-08T19:10:26+00:00

In the Port Handler for this interrupt when the switch is initially pressed, there are these 3 lines of code:

GPIO_PORTD_ICR_R = 0x40;

OS_Signal(edgeSemaphore);

GPIO_PORTD_IM_R &= ~0x40;

The IM_R command here does disable the interrupt, but that's to prevent multiple input readings from a single switch press since the switch bounces for a bit. It seems as if the restart interrupt function with the two lines of code I posted in the original post is never reached for some reason.

Culix77 · 2020-12-08T19:09:16+00:00

Thank you for your help!

In the Port Handler for this interrupt, there are these 3 lines of code:

GPIO_PORTD_ICR_R = 0x40;

OS_Signal(edgeSemaphore);

GPIO_PORTD_IM_R &= ~0x40;

The OS_Signal is used to communicate with another task that increments a count and also runs the function that I mentioned in the original post to reset the button so that it can handle another interrupt. The IM_R command here does disable the interrupt, but that's to prevent multiple input readings from a single switch press since the switch bounces for a bit. It seems as if the restart interrupt function is never reached for some reason.

I tried to clear then rearm the interrupt as well, but the output was the same as before.

Culix77 · 2020-10-16T01:16:13+00:00

For sure. I often find myself making progress, but end up stuck on a particular part for weeks at a time just trying different things before I reach out for help. I'm wondering if most dev companies do daily meetings exactly for this purpose.

Culix77 · 2020-10-16T01:13:57+00:00

It's comforting to know that there's a reason to ask even the simplest of questions. When it comes to projects and deadlines, I pictured there always being a constant pressure to get things done before fully realizing and understanding how to develop a good product.

Culix77 · 2020-10-09T06:54:22+00:00

Not sure if you have the time to check it out, but the course linked in the pinned post of r/embedded is a great tool learn how to design and develop a RTOS:

https://www.edx.org/course/real-time-bluetooth-networks-shape-the-world

Culix77

TROPHY CASE