Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
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.
Where is it written that everything you learn is supposted to be a thrill ?bassnut;677460.. said: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.
Yes! Very eloquently put, 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.
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".
In the end though, especially in a commercial enviroment, coding yet another stupid device driver gets to be expensive and time wasteing.
It is hard to study this sort of thing with a family to support. People have done it successfuly but it means a lot of difficult work and doing without...If not how does one get a job doing embedded systems and stuff.
In general a 4 year degree is EE or CS is required. Some people have a MS (masters of science) which is another couple of years. There are two year degrees in programming but I do not know how useful they are. From what I have seen a 2 year job will land a technician level job, engineering and higher require at least 4 years.
Also what do you mean by hardware where no drivers exist?
Many designs include FPGA's or semi-custom or full custom chips. These chips are often controled by a uC. But because it is all new there are no existing drivers. But even existing devices can be used differently then expected and that requires unique driver code too.
Are you referring to someone building something with a uC and not programming it? If so then ok .
Not sure what you mean. A uC without somthing around it is mostly useless. Execpt maybe as a learning tool.
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.