Does that make me a NeuNew?)
I’ve read the FAQs and searched the news, but I still need your help
I’m trying to determine the best steps to take to get myself to a
somewhat competent level of embedded NTO programming skill.
Here’s where I am:
- I can program micros (like AVR) in ANSI C – no RTOS experience.
- I have never used C++ – unless my grades count.
- I have never written programs for any operating system.
- You don’t want me to administer your Linux server.
- I understand hardware.
- I understand (to a reasonable degree) TCP/IP-based networking.
- I do NOT understand message-based programming, but I barely have a
- I designed an oscillator that ended up on Mars! – I had to say that
because my list was depressing me. :[
Here’s where I want to be:
I want to be able to develop embedded NTO-enabled devices which
incorporate one or more of the following features:
- LCD interface (up to 1024x768 @ 256 colors)
- TCP/IP connectivity
- Terminal emulator like vt100
- Web browser
- RS-422 serial communications
- Customized GUI shell for sending/receiving RS-422 commands
- It works.
I certainly do not have any real-time requirements at this point, but
the possibility exist that I will want it in the future. (ie. I have no
real-time real-time requirement.)
Should I start with learning my way around Linux and programming in that
environment with GNU tools? Or, should I jump right in to RTP on a PC
and sink-or-swim using the upcoming CW tools? At some point I want to
take a 3-5 day course (from Parse or QSSL), but I also want to have a
chance of comprehending the material. Please let me know if I am
missing something or just doing it all wrong.
And, yes, I’m wearing Nomex.
Raylar Design, Inc.