Hi Nicky,
I'm just going to try to lay it out plainly for a moment, because it
seems like you are in significantly over your head here and/or are not
a native English speaker, and because I'm feeling like trying to be
helpful right now.
You're going to have a hard time finding a lot of help here, because
you seem to not have a very good idea of what you're even trying to
do. You ask about building things in Linux, but then mention two
(mostly) Windows-exclusive languages. You then mention wanting to
access the RS232 port, which is an all around terrible way to
interface with the BeagleBoard for anything other than what it is
intended for - debugging and remote access. And in your responses to
what help you have been getting, you seem to have little understanding
of programming in general, much less cross-compiling or interfacing
with a Beagleboard. So you've been getting some marginally helpful,
and often snarky responses.
And quickly: to clarify, Mans is making a clever pun in his response
about Stereo. Mono is the (mostly) in my paragraph above. Mono is a
project that is an effort to support C# compilation in Linux. It is
not really related to the BeagleBoard at all, other than that it is
for Linux, and the BeagleBoard can run Linux. I don't know about the
state of Mono support for ARM development, which is a bit of a
separate issue, but it appears from Vladimir's response that there is
some support there, at least.
If you want a GUI/IDE for coding, look at Eclipse - I've heard it
recommended for all kinds of development, and also for specifically
the BeagleBoard. I myself am only passingly familiar with it, I
generally am not a huge fan of GUIs because I am very focused on
details when I am coding and being able to control everything, and
IDEs tend to get in my way more than anything else. I am more of a
user of Vim myself. But if you are used to tooling around in Visual
Studio (Visual Basic/C#), you will have a hard enough time
transitioning to developing outside of Microsoft's bubble, much less
outside of an IDE, so I would very much recommend you stick with
Eclipse or something of the sort.
To that end: I am not terribly familiar with the BeagleBoard list
specifically, but it has been my experience that you will get a much
better response in these kinds of lists if you give us a good amount
of information about what you want to do (your end goal), and what
you've tried already. it's good to show some effort, and that you
have some understanding of at least what problems you're up against -
it's always good to have read relevant documentation like the
BeagleBoard docs, or stuff over on the eLinux Wiki
(http://elinux.org/BeagleBoardFAQ). Then ask questions - the more
specific, the better.
So for instance, from your several posts, it seems that you want to
access the BeagleBoard through a serial port from a client application
on a desktop and flash some LEDs.
There are already several problems with that - first of all, if the
bulk of this application is going to be on the client computer, that
doesn't even need to be in Linux. Second of all, the BeagleBoard is
way overpowered for connecting to a computer and flashing some LEDs.
You would be much better of using something like an Arduino, or even
something even more stripped down like a Teensy or an Atmel AVR or a
PIC controller. Which isn't to say you can't use the BeagleBoard -
you certainly can. But the bottom line is that at some point, in
order to flash the LEDs, you're probably going to have to just write
some C. Not C#, and certainly not Visual Basic. C, maybe C++, to
listen to whatever input you're getting from the computer and flashing
LEDs in response.
Another issue is that RS232 is a terrible way to interface with a
computer - no one has serial ports these days except for people who
are programming their microcontrollers. The RS232 port on the
BeagleBoard is mainly for debugging and remote access, as far as I can
tell, but if you want to use it that's fine, it's easy to access from
software.
So to sum up: ask better questions, give us a better idea of what
you're trying to do, and read the links that people give to you. Try
not to be too offended if people tell you you're wrong, either they're
probably right, or you haven't told us enough about what you're trying
to do. It's long, but there is an absolutely excellent essay on the
subject of asking good questions in forums like this here:
http://catb.org/~esr/faqs/smart-questions.html
If you've read this whole email, and are going to continue asking
questions in such forums, it is worth your time to read, and will save
you and everyone you're asking questions much unneeded frustration and
confusion.
And to sum up what you should actually do for your project: do what I
said in the previous paragraph - tell us more, read up, educate
yourself. Ask better questions, and we'll be able to give you better
answers. Mailing lists are not places to get walked through how to do
everything on your BeagleBoard - that's what wiki articles and
walkthroughs and tutorials are for. Mailing lists are generally for
help for specific issues ("I can't access the RS232 port from my C
program", "I don't know how to get Eclipse to compile for the
BeagleBoard", "Where should I start looking to write a kernel module
to access the McBSP ports"), or discussion of issues or items of
interest related to the topic.
All that said, just because I wrote a bunch of stuff here doesn't mean
I will be your personal assistant in getting up and running. I don't
actually even know that much about BeagleBoard development myself, but
I've hung around mailing lists and IRC channels enough (a youngster to
many, I'm sure, but enough) to be able to try to point you in a more
helpful direction.
Or maybe it's 1:30am and my brain has gone to strange places, and I'm
just going off on tangents, in which case convert this to binary and
use it as a really bad source of data for your next random number
generator.
Joel