> Building a cross-build tool chain for an ARM Linux target is hard enough on a Linux host, it is going to be even harder with a MS-Windows host. > GCC's build infrastructure depends on make and the autotools, which are not really available, natively, under MS-Windows.
I've documented cross-compiling '(and debugging) on Windows with Linaro GCC, and/or ARM DS-5/ CCS IDE: https://www.element14.com/community/people/jancumps/blog/2016/07/31/beaglebone-cross-compile-c-on-windows https://www.element14.com/community/community/designcenter/single-board-computers/next-gen_beaglebone/blog/2019/05/18/build-and-debug-a-linux-c-program-with-code-composer-studio I believe that the steps, if taken exactly, are repeatable. I'm currently working on how to do that on the new Arm Developer Studio with their non-commercially-licensed option. I can build and debug, but not automatically deploy on that environment (yet). Regards, Jan On Mon, Sep 9, 2019 at 2:07 PM Robert Heller <[email protected]> wrote: > At Sun, 8 Sep 2019 20:20:01 -0700 [email protected] wrote: > > > > > > > I'll admit I'm a newbie at this. I'm following Derek Molloy's book and > > videos, specifically chapter 7 in his book, > > http://exploringbeaglebone.com/chapter7/ > > He uses a windows host and VirtualBox running debian to set up a tool > chain > > using Eclipse CDT and QEMU to write & debug code for the Beaglebone, > > including remote debug on the BB. The BB is running an arm hard float > > debian. I'll post a progress report when I get it working, > > This *sounds* like what is going on is running x86 debian in VirtualBox > and > then using a cross-build tool chain. (The "remote debug" is the give away > here.) Although, QEMU appears to include an ARM "emulator", but it is not > really a *BBB* oriented. Building a cross-build tool chain for an ARM > Linux > target is hard enough on a Linux host, it is going to be even harder with > a > MS-Windows host. GCC's build infrastructure depends on make and the > autotools, which are not really available, natively, under MS-Windows. > > *I* expect it is going to easier (at this point) to just get a Raspberry > Pi > and use that as a build/debug host. Raspberry Pis are dirt cheap ($35, > even > for a Raspberry Pi 4) and have all of the user-friendly features -- GUI, > etc. > And being a quad-core, 64bit processor, means it is fast enough to use as > a > desktop build box, even running an IDE (eg Eclipse). Code compiled > *natively* > on a Raspberry Pi will run on a Beagle, just by copying the ELF binary > over. > > The only thing "missing" from a Raspberry Pi is a powerful GPU and SATA > ports, > but these are "minor" issues... *I* am probably going to not bother > getting a > newer laptop once my current laptop gets too old to be usable and will > likely > just build a battery powered Raspberry Pi based system. I may end up with > only > two Intel x86 processor machines: a desktop tower, that will be mostly > functioning as a LAN server (dhcpd, named, and amanda backup host) and x86 > Linux build host and a MacMini as a MacOSX build host. > > > > > Brian > > > > On Sun, Sep 8, 2019 at 7:45 PM Robert Heller <[email protected]> > wrote: > > > > > At Sun, 8 Sep 2019 15:54:36 -0700 (PDT) [email protected] > > > wrote: > > > > > > > > > > > > > > > > > > > Thank you! My immediate problem was I was using the armhf iso on the > VM. > > > I > > > > changed this to the debian i386 iso and it booted. I'm ready to > install. > > > I > > > > guess my next lurking issue will be QEMM. I'm using Derek Molloy's > book > > > and > > > > video as a guideline in this adventure, > > > > > > The i386 processor type matches what the x86_64 processors can run as > > > virtual > > > machines. Note: the i386 iso is not a BBB iso and cannot run > beagleboard > > > programs. > > > > > > > > > > > Thanks, > > > > Brian > > > > > > > > On Sunday, September 8, 2019 at 2:02:30 PM UTC-7, shabaz wrote: > > > > > > > > > > Hi Brian, > > > > > > > > > > It could be I don't understand something fundamental, or something > > > very > > > > > strange is being attempted. > > > > > > > > > > A Windows 10 PC, if it has an x86 or x64 processor, cannot use > > > VirtualBox > > > > > in this manner, to run a Linux image intended for a BBB. The BBB > > > doesn't > > > > > have an x86 or x64 processor, and VirtualBox isn't intended for > > > emulating > > > > > ARM processors (unless things have changed significantly.. I have > not > > > tried > > > > > VirtualBox for years). > > > > > > > > > > ------------------------------ > > > > > *From:* [email protected] <javascript:> < > > > [email protected] > > > > > <javascript:>> on behalf of Brian Tremaine <[email protected] > > > > > <javascript:>> > > > > > *Sent:* 08 September 2019 17:57 > > > > > *To:* BeagleBoard <[email protected] <javascript:>> > > > > > *Subject:* [beagleboard] Setting up Debian VM for BBB > > > > > > > > > > Hi All, > > > > > I realize my question is VirtualBox related but I'm stuck trying to > > > set up > > > > > Debian 'Buster' as my VM for my BBB. > > > > > I've gone through several blogs on the setup but it still won't > boot > > > > > Debian. > > > > > > > > > > My iso image is: debian-10.0.0-armhf-netinst.iso > > > > > When I start the VM it drops me into a UEFI shell. If I then go to > > > FS0: > > > > > and do a directory I can 'see' the Debian files. > > > > > > > > > > [image: Capture1.PNG] > > > > > > > > > > > > > > > > > > > > [image: Capture2.PNG] > > > > > > > > > > I have no idea what the UEFI shell is or why I'm there ???? Can you > > > help > > > > > me boot Debian? Here is a screenshot of my VM setup: > > > > > > > > > > [image: Capture3.PNG] > > > > > > > > > > Thanks in advance !!!! > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > For more options, visit http://beagleboard.org/discuss > > > > > --- > > > > > You received this message because you are subscribed to the Google > > > Groups > > > > > "BeagleBoard" group. > > > > > To unsubscribe from this group and stop receiving emails from it, > send > > > an > > > > > email to [email protected] <javascript:>. > > > > > To view this discussion on the web visit > > > > > > > > > https://groups.google.com/d/msgid/beagleboard/9c5d802a-6ee7-4c52-baf7-9d4528aabaa0%40googlegroups.com > > > > > < > > > > https://groups.google.com/d/msgid/beagleboard/9c5d802a-6ee7-4c52-baf7-9d4528aabaa0%40googlegroups.com?utm_medium=email&utm_source=footer > > > > > > > > > . > > > > > > > > > > > > > > > -- > > > Robert Heller -- 978-544-6933 > > > Deepwoods Software -- Custom Software Services > > > http://www.deepsoft.com/ -- Linux Administration Services > > > [email protected] -- Webhosting Services > > > > > > > > > -- > > > For more options, visit http://beagleboard.org/discuss > > > --- > > > You received this message because you are subscribed to the Google > Groups > > > "BeagleBoard" group. > > > To unsubscribe from this group and stop receiving emails from it, send > an > > > email to [email protected]. > > > To view this discussion on the web visit > > > > https://groups.google.com/d/msgid/beagleboard/20190909024506.9A8D826C07E4%40sharky3.deepsoft.com > > > . > > > > > > > > > -- > Robert Heller -- 978-544-6933 > Deepwoods Software -- Custom Software Services > http://www.deepsoft.com/ -- Linux Administration Services > [email protected] -- Webhosting Services > > > -- > For more options, visit http://beagleboard.org/discuss > --- > You received this message because you are subscribed to the Google Groups > "BeagleBoard" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/beagleboard/20190909120647.EC32A26C07E8%40sharky3.deepsoft.com > . > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CABjVgnBTd%3DNWL6JvUfa-A6tGvZhUv-PNYF%2Br8LyEGCzSL7-YOQ%40mail.gmail.com.
