I received a Beaglebone Black to develop a homework project on. I plugged
in the board to my USB and installed the Windows driver. I next wanted to
develop a simple "Hello world" C project and debug it on this board. I
didn't want to be a Newbie so I researched how to develop programs for thi
>
> *It will take days or weeks to learn the tools to develop a 10 minute
> program. This is how I debugged in the 1980's. There has got to be a
> better environment than this.*
>
This is not the fault of the hardware or the designers of the hardware.
This is your fault for not knowing the tools
William Hermans
Sent: Tuesday, September 02, 2014 10:13 PM
To: beagleboard@googlegroups.com
Subject: Re: [beagleboard] Yet another newbie "how to get started"
It will take days or weeks to learn the tools to develop a 10 minute program.
This is how I debugged in the 1980
As an alternative to eclipse-based IDEs there is the qt creator. After changing
code, with a single command it cross-compiles (gcc-arm), automatically deploys
the compiled code on target (though ssh), starts it under the remote gdb
server, runs the local gdb client, and I get a full graphical de
You can also use code::blocks IDE, and setup a custom toolchain. I did this
last year with linaro's WIndows armhf toolchain binary.
On Wed, Sep 3, 2014 at 12:27 PM, Ivan Nazarenko
wrote:
> As an alternative to eclipse-based IDEs there is the qt creator. After
> changing code, with a single comm
*This is not the fault of the hardware or the designers of the hardware.
This is your fault for not knowing the tools. Harsh as it may seem, this is
a fact. This is why professional software engineers with the skills to
setup / use said tools get paid big money.*
It is very much the responsibil
On Wed, Sep 3, 2014 at 8:57 PM, wrote:
> This is not the fault of the hardware or the designers of the hardware. This
> is your fault for not knowing the tools. Harsh as it may seem, this is a
> fact. This is why professional software engineers with the skills to setup /
> use said tools get paid
Thanks, Ivan, for giving a plausible solution. My project has to be in
ANSI C and not C++. If Qt can accomplish that, I'll try it.
On Wednesday, September 3, 2014 3:27:31 PM UTC-4, ivan_n wrote:
>
> As an alternative to eclipse-based IDEs there is the qt creator. After
> changing code, with a
On Wednesday, September 3, 2014 10:00:11 PM UTC-4, RobertCNelson wrote:
>
> On Wed, Sep 3, 2014 at 8:57 PM, >
> wrote:
> > This is not the fault of the hardware or the designers of the hardware.
> This
> > is your fault for not knowing the tools. Harsh as it may seem, this is a
> > fact. Th
>
> I'm working with an industrial class board that costs $375 in single
> quantities. The single-seat QNX development license cost my company $1500,
> but I was porting code to it in a day.
Okay, good for you! You must be a QNX expert, i don't know crap about
that os. But i can bring up debian/l
On Wednesday, September 3, 2014 8:22:12 PM UTC-4, William Hermans wrote:
>
> You can also use code::blocks IDE, and setup a custom toolchain. I did
> this last year with linaro's WIndows armhf toolchain binary.
>
Can you put this into an installation package, document it, and get the
Beaglebo
On Wed, Sep 3, 2014 at 9:11 PM, wrote:
>
>
> On Wednesday, September 3, 2014 8:22:12 PM UTC-4, William Hermans wrote:
>>
>> You can also use code::blocks IDE, and setup a custom toolchain. I did
>> this last year with linaro's WIndows armhf toolchain binary.
>
>
>
> Can you put this into an insta
On Wednesday, September 3, 2014 10:10:09 PM UTC-4, RobertCNelson wrote:
>
> >
> > I'm working with an industrial class board that costs $375 in single
> > quantities. The single-seat QNX development license cost my company
> $1500,
> > but I was porting code to it in a day.
>
> Okay, good f
On Wed, Sep 3, 2014 at 9:15 PM, wrote:
>
>
> On Wednesday, September 3, 2014 10:10:09 PM UTC-4, RobertCNelson wrote:
>>
>> >
>> > I'm working with an industrial class board that costs $375 in single
>> > quantities. The single-seat QNX development license cost my company
>> > $1500,
>> > but I w
Already did, "someone" had to create the default debian image. ;)
>
> http://beagleboard.org/latest-images
> http://elinux.org/Beagleboard:BeagleBoneBlack_Debian
> http://elinux.org/BeagleBoardDebian
> http://elinux.org/BeagleBoardUbuntu
> http://eewiki.net/display/linuxonarm/Home
>
> Regar
> But I don't need a Linux image. I found several Linux images using Google
> search (I don't recall seeing yours). The board came with Linux installed.
> I need a development environment so I can write and debug my own programs.
Well, gcc/gdb/nano are installed in the base development image. s
On Wed, Sep 3, 2014 at 9:28 PM, Robert Nelson wrote:
>> But I don't need a Linux image. I found several Linux images using Google
>> search (I don't recall seeing yours). The board came with Linux installed.
>> I need a development environment so I can write and debug my own programs.
>
> Well,
>
> *But I don't need a Linux image. I found several Linux images using
> Google search (I don't recall seeing yours). The board came with Linux
> installed. I need a development environment so I can write and debug my
> own programs.*
>
You're awfully demanding. Tell you what. continue using y
From:
Reply-To: "beagleboard@googlegroups.com"
Date: Wednesday, September 3, 2014 at 7:07 PM
To: "beagleboard@googlegroups.com"
Subject: Re: [beagleboard] Yet another newbie "how to get started"
>
>
> On Wednesday, September 3, 2014 10:00:11 P
On Wed, Sep 3, 2014 at 10:01 PM, wrote:
> Thanks, Ivan, for giving a plausible solution. My project has to be in ANSI
> C and not C++. If Qt can accomplish that, I'll try it.
Eh, it's hard to figure out when you're kidding and when you're
serious but Qt is a C++ based environment, so this may
On 09/03/2014 07:07 PM, murre...@ameritech.net wrote:
>
>
> On Wednesday, September 3, 2014 10:00:11 PM UTC-4, RobertCNelson wrote:
>
> On Wed, Sep 3, 2014 at 8:57 PM, wrote:
> > This is not the fault of the hardware or the designers of the
> hardware. This
> > is your fault for n
So you want to compare a $45 board with a $375 one with a $1500 development
> license? Come on you can't be serious. Seems logic of a common variety is
> lacking here.
>
> It's no ones fault but your own you're behind in the skills required for
> your "homework" project. Step off the fricken h
On Thu, Sep 4, 2014 at 12:14 PM, wrote:
>
>
>> So you want to compare a $45 board with a $375 one with a $1500
>> development license? Come on you can't be serious. Seems logic of a common
>> variety is lacking here.
>>
>> It's no ones fault but your own you're behind in the skills required for
>
For a super-newb wanting a GUI, you can always start by
1) plugging in your board
2) visiting http://192.168.7.2:3000 or http://beaglebone.local:3000
(depending if you are on USB or Ethernet)
3) typing in:
void setup() {
printf("Hello world\n");
}
void loop() {
}
3) saving it as "hello.ino" and
4)
On 09/04/2014 09:14 AM, murre...@ameritech.net wrote:
>
>
> So you want to compare a $45 board with a $375 one with a $1500
> development license? Come on you can't be serious. Seems logic of
> a common variety is lacking here.
>
> It's no ones fault but your own you're behind in th
Funny thing is Don, If he ( assuming He because of the adversarial stance )
took the time to read a book on the gcc toolchain he'd have figured it out
by now. But NOO, we must blame everyone else but ourselves, because
"we're" always right. RIGHT ?
On Thu, Sep 4, 2014 at 10:49 AM, Don deJua
On 09/04/2014 10:56 AM, William Hermans wrote:
> Funny thing is Don, If he ( assuming He because of the adversarial
> stance ) took the time to read a book on the gcc toolchain he'd have
> figured it out by now. But NOO, we must blame everyone else but
> ourselves, because "we're" always right.
I'm probably going to kick myself for getting into this, but here goes
nothing.
Getting into *any *new community can be difficult. You're the new kid and
you don't know who's who. You wonder what's a sensible question, what's a
naive question, and what's a bloody annoying question. I think most
Tim, what you need to do is figure out what you want to do, and then start
googling / reading. There is no "easy reading list" because no one thinks
just like you ( or me / anyone else for that matter ).
I understand this is not very optimal, especially if you have a deadline.
But that is how it w
Agreed -- you can't learn a damned thing without putting in your own skull
time. Perhaps I'm too distrustful of internet search engines -- I like a
good reference handbook. If there isn't one available, I'll just have to
make do.
On Thursday, September 4, 2014 6:24:04 PM UTC-4, William Hermans
From: Tim Cole
Reply-To: "beagleboard@googlegroups.com"
Date: Thursday, September 4, 2014 at 2:41 PM
To: "beagleboard@googlegroups.com"
Subject: Re: [beagleboard] Yet another newbie "how to get started"
> I'm probably going to kick myself for gett
quot;beagl...@googlegroups.com " <
> beagl...@googlegroups.com >
> Date: Thursday, September 4, 2014 at 2:41 PM
> To: "beagl...@googlegroups.com " >
> Subject: Re: [beagleboard] Yet another newbie "how to get started"
>
> I'm probably going to
On Thursday, September 4, 2014 2:57:45 AM UTC+1, murr...@ameritech.net
wrote:
>
> *This is not the fault of the hardware or the designers of the hardware.
> This is your fault for not knowing the tools. Harsh as it may seem, this is
> a fact. This is why professional software engineers with th
33 matches
Mail list logo