At 03:54 AM 2/13/2008, you wrote:

>I have an idea for a new project and I have zero experience with
>microcontrollers (I was a physics major) I have programmed before in Java,
>html, php, C somewhat....
>
>I'm not going to get into the details to what my project actually
>accomplishes so I'll just get into the nitty gritty technical side of it.
>
>Basically my project involves a keyboard, a flash memory card, and a small
>LCD screen. I want the keyboard to input text and have the text to appear on
>the small lcd screen, along with other text that is saved from the flash
>card. What I type will also be saved onto the flash card for future use.
>
> >From what I've gathered in the last 24 hours, to do this I need a
>microcontroller at the center of all these input/outputs. Correct me if I'm
>wrong but basically I will need a microcontroller that takes in information
>from a flash card via a flash card controller, and from what I enter in as
>text. Also the MC will send information to the lcd display controller based
>on the code I program into it.
>
>The program I write for these inputs/outputs rests in the physical
>microcontroller and can be installed via a programmer and basic/c compiler.
>
>So if I am right thus far, here are my questions..
>
>1) Can I get all this integrated into a board? I have a feeling that I can
>because I have seen some however not to the specific LCD that I want. I want
>a larger one than what is available.

Larger in pixels or size or both? Larger LCD modules typically don't have the
controller on board-- you have to provide it or pick a microcontroller or
a microprocessor with an on-board controller. Often that kind of micro will
not have on-board flash for the program memory, so you might have to allow
for a relatively wide bus involving a lot of pins going to one or more flash
chips for program memory storage.

>2) If I do buy an LCD, do the controllers usually handle C/basic code or
>assembly only? What exactly goes into telling an LCD what to display? Does
>the manufacturer give specific codes in assembler or C for the device? Also,
>is this the same case with the flash reader? Do most flash readers/writers
>that takes in say assembly? How exactly does do these deices all come
>together with the microcontroller?

The LCD module manufacturer, if they provide a controller, will tell you what
chip they use, and you can refer to the data sheet for that chip. If you are
using an on-chip controller, you have to configure it to talk to the LCD.
Maybe you can scab some code off of the net for it. Maybe you can 
integrate it and
maybe it will work well enough. Maybe you can get sample code with an 
eval board
that works well enough.

>3) What will be the biggest hurdle with this device?

Hard to tell where the hurdles will be for you. Have you done any hardware
design? Software wise, getting the various bits working, and working together
and if you need a file system on the flash card, getting that working could
be challenging. It might be a good idea to avoid anything that involves your
system being a USB host..

>4) Any good resources on the net on learning how to build this thing?

I suggest you start with an evaluation board that has a relatively
powerful micro (eg. ARM7), a flash card socket, and the LCD you want on board,
and has code (probably in C) that you can modify, and an easily installed free
toolchain. This will maximize your chances for success at a fairly
reasonable cost (should be less than $500, I'd guess) and in a short time.
Just buying a QVGA or larger LCD, the controller, micro, etc. and 
making a proto
board would probably set you back something approaching that much 
(although you'd
learn a lot in the process). If you require a file system on the flash card,
look for sample code for that to be included. You don't *need* a controller
for some flash cards (SPI is guaranteed to be present on some types) but
it's relatively slow if you don't use a more parallel interface. You can always
do a cost-reduction redesign if you want to make lots of whatever these things
are.. first thing is to get it going.

>I would really appreciate everyone's feedback on this, I understand my
>knowledge level is atrocious but I would really like to start this project.
>Gotta start from somewhere...


Best regards,

Spehro Pefhany --"it's the network..."            "The Journey is the reward"
speff@interlog.com             Info for manufacturers: http://www.trexon.com
Embedded software/hardware/analog  Info for designers:  http://www.speff.com



-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist