BeagleBoard verification

Hello Gerald, jason

Thank you for that but there is a problem I don't know Linux, I am a
windows based person can you tell me is there any way to put a windows
based operating system on the board and is there any command manual
for the board so that I can control the hardware I mean programming
(commands to access the pins of processor, audio jacks, etc)

Thank you.

The closest thing to a Windows type OS is WinCE. But, it isn’t XP or Windows7 for sure. It is similar, but there are differences and will put you in a different world than a desktop OS found on a PC. I suggest you go to the discussion board and do a search on WinCE.

http://groups.google.com/group/beagleboard

Gerald

WinCE is painful, there’s a reason its letters spell wince. If I were you, I would take this opportunity to learn Linux. It is easier than you probably think it is, and the skills (and programs, and APIs) you pick up for the BB will transfer over to full-blown Linux on servers or desktops.

A few years ago, I was a Windows guy, but I picked it up and now I use Linux almost completely exclusively (Win7 for iTunes is my only non-Linux box) on my servers, my home desktop, my work desktop, and my laptop.

Just my thoughts, I hope they help.
– @

hey, then can you tell me how do I learn linux(fastest that I can
program bb) and how can I program bb just sending code through
terminal programs like hyperterminal

Thank you.

General Linux knowledge:

  • install Linux on your laptop, just to get an idea of (a) how easy it is to install and use, and (b) the overall installation process

  • learn to use apt-get on Debian or Ubuntu Linux distributions to install software from repositories (this is like Apple’s app store, except all the apps are open source, meaning free)

  • learn to use emacs (everything and the kitchen sink) or vim (minimalistic) or both, but pick one and use it until you are comfortable with it - they both have CLI’s and GUI’s

  • compile simple program using gcc (plenty of manuals on the internet)

  • compile a more complex program using a hand-written make file

  • learn the basics of automake or cmake (cmake is recommended, although I don’t know it yet)

  • learn version control with git - a LOT of projects are moving to get at this point, so it’s a skill that’s very useful

  • if doing gui programming, follow a few tutorials on GTK+ (if coding in C) or Qt (if coding in C++). Python also works with both, so learning Python would pay off double (additionally, it would also pay off because development time would be shorter).

  • learn the basics of ssh, I recommend learning how to setup X forwarding, even though you will have to be running linux on your desktop for this

  • presuming you already know hyperterminal, ssh into the BB and you’re ready to program directly on the BB

  • alternatively use cutecom or gtkterm on Linux to ssh into the BB

Look at the BB wiki pages to find RCN’s Ubuntu Linux distribution for the BB (he has a good guide, but make sure to seed your image with build-essentials and git-core for a compiler and version control, respectively), or use Angstrom from angstrom-distribution.org .

Other than that, make sure you do some research before you ask questions anywhere. It is incredibly annoying to be pestered with questions that are answered on wikipedia, google, or the project’s own homepage. This email is fine, but I suggest using the #ubuntu IRC channel on freenode.net for help in the future, as they are very helpful and nice to beginners. Ubuntuforums.org is also a good resource, although you may have to wait a few days for answers on that site.

Good luck, I hope this helps.
– @

I would also suggest "synaptic" as it has everything under the one roof in a GUI so one can browse through available packages and their descriptions.
What is often forgotten is that Linux users for the most part came from a Windows environment, their first encounter with software. They learned and that's how they became very familiar, both as users and developers.
As one of my erstwhile colleagues used to say, it's all code.
Regards
Sid.