No one is going to do that for you.

You need to at least put some of your own effort into a project. We will help you with your work but we will not do it for you.

Even if we wanted to we could not because we do not know what processor, language or LCD you are using. Sort of like asking one to build a house without a plan. Do you want a mud hut or a pallace?

3v0

Most PIC development kits include drivers for LCD displays that just require a text write to an LCD command, if you cant code the details, just get a kit that that does it for you. If your using an LCD display with a serial input, the manual that came with it will explain all.

Originally Posted by bassnut

Most PIC development kits include drivers for LCD displays that just require a text write to an LCD command, if you cant code the details, just get a kit that that does it for you. If your using an LCD display with a serial input, the manual that came with it will explain all.

If the goal is to get the job done that is a great solution. If the goal is to learn it is wrong solution.

In general it is not a good thing to depend heavily on prepackaged solution when learning. Doing so lets the student feel they have acomplished somthing but at the cost of understanding.

Ballance is required.

Well 3vo, you have a point there, but coding drivers is a mind bend at times. I have found that the big picture application at hand is often the exciting reason for starting a project, not the the effort that gets buried in complicated device drivers. Nothing kills enthusiasm faster than problems with a seemingly simple LCD display message "full speed ahead".

Given the OP'ers OP I get the feeling that this is school work. If it were an application we would have heard about it.

A few week ago there was a post where the idea of building anything that already had been built was a yawn. The OP only wanted to build new and exciting things. How can anyone expect to build the new things when they are too lazy to learn the basics.

Originally Posted by bassnut;677460..

I feel driver code is so generic these days, its a boring disinsentive reinventing the wheel all the time. Application engineering these days is so competitive, efficient big picture innovation is more usefull, I dont think driver detail neccessraily breeds a better understanding of real world applications. ie, drivers should be just another basic command, supplied by the device vendor.

Where is it written that everything you learn is supposted to be a thrill ?

Embedded systems is all about interfacing to the real world. It is what sets it apart from other branches of computer science.

The goal of learning to drive well understood devices is not to drive these specific devices. It is to develop an understanding of driver code in a general sense. If you can not master the common devices your chances of writing code to drive custom hardware are nealy zero.

If your goal is to patch together existing bits then you may survive. But the first time you run into a custom chip or the hardware engineer changes the way a part is connected, you are toast.

3v0

Originally Posted by 3v0

A few week ago there was a post where the idea of building anything that already had been built was a yawn. The OP only wanted to build new and exciting things. How can anyone expect to build the new things when they are too lazy to learn the basics.


Where is it written that everything you learn is supposed to be a thrill ?

Embedded systems is all about interfacing to the real world. It is what sets it apart from other branches of computer science.

The goal of learning to drive well understood devices is not to drive these specific devices. It is to develop an understanding of driver code in a general sense. If you can not master the common devices your chances of writing code to drive custom hardware are nearly zero.

If your goal is to patch together existing bits then you may survive. But the first time you run into a custom chip or the hardware engineer changes the way a part is connected, you are toast.

Yes! Very eloquently put, 3v0.

Originally Posted by bassnut

Well 3vo, you have a point there, but coding drivers is a mind bend at times. I have found that the big picture application at hand is often the exciting reason for starting a project, not the the effort that gets buried in complicated device drivers. Nothing kills enthusiasm faster than problems with a seemingly simple LCD display message "full speed ahead".

While I accept that i am not an expert of software, what 3v0 said as reply to this post, is very apt and if i were to be in this position of the O P, I would coolly accept it, and start writing of my own, if get the problems, as it is more likely in early days, and come back only to discuss the problem.

I am of the opinion, that a person is only to pick up off shelf subroutines, and simply write a link patch, he could succeed for some time. When a problem is faced, where he is assigned to debug overnight, due to emergency of the situation, the person is likely to fumble.

It is just because, he/she never has tried to develop an organised habit of writing real software or real drivers.

Nice insight 3v0...

where do you suggest someone start learning from? A lot of people say learn basic electronics but the thing there is there is no good resource to learn from. They all leave you wanting more of an explanation.

That is why i think a bunch of people just jump into the subject of there choice and ask for help later. (like me)

Its like when i went to college to learn electronics they taught me other things i never knew why, such as english and compensation and other things. I found that its good to learn for the business part of any job but it throws you off the technical part.

I mentioned that because many tutorials and sites are the same. They want you to learn alot of things you might not need to and you get lost.

I know nothing about ATOMS, Protons etc... Yet i can do some things with electronics. I understand having basic knowledge of this is a good idea but to truly understand the basics of just that its a hassle since no one can write a descent electronics for dummies.

OK enough with my run on. The point is that there is no rule on what to learn first really.

Like when i first started i wondered what the hell is a resistor. I found out its a current limiter. But used in various ways it can cut voltages. Now if i read that i would be like ok i understand whats it for. The issue there is i never said how exactly to use it. Books don't really help. I get tired of reading a example over and over.

I want a real world example that is why i try and fail and ask you guys here. If not ill see whats on the web and copy it which isn't always a good idea. But like this guy who wanted "help" with LCD coding, he has no info on a starting point perhaps. That's why people copy code because no one can explain it to them they have to trial and error which sucks.

The sum of this would be if someone would help with the basics alone then they wouldn't be asking for help with the slightly difficult stuff. Now saying that... can someone be my tutor teach me the basics again. Resistors, capacitors, inductors, diodes, logic.

I know this was long but hey, I like to write even if it all doesn't make sense.

Originally Posted by bassnut

In the end though, especially in a commercial enviroment, coding yet another stupid device driver gets to be expensive and time wasteing.

You are still making excuses not not wanting to learn.

There are jobs where all you need to do is stitch together canned drivers with a bit of application code. It is the first to be outsourced because it is less difficult.

On the job one would not write a driver for kicks and giggles. But there will always be hardware where no driver exists. This is one of the areas where a good embedded programmer earns his keep.

On some projects the firmware engineer works with the chip designer. You have to keep up with his mostly undocumented and constantly changing design. He may come to you to solve problems he can not overcome in hardware. Or he may simply say I left this one for you.

Anyone can do the easy stuff.

3v0

3v0 it seems like you have a degree of some sort. If so what kind. If not how does one get a job doing embedded systems and stuff. Also what do you mean by hardware where no drivers exist?

Are you referring to someone building something with a uC and not programming it? If so then ok .

Please dont take this as me be mean or anything i just get lost easy
Being a hobby for me i would love to turn this into a job/career. If it was a job or even a school type of thing for me i bet i would know way more than i do now just because of the demand for me to know more.