Sound like you have it under control then. Glad you got it working. A
couple of side notes . . .
I use Debian Wheezy i386 ( 32bit ) for all my dev machines for the
beaglebone. Have had great success with all. Virtual machine, or real.
However, I do not use X at all. Just a basic command line interface.
Also I did not think through what I was saying about sshfs . . . with
sshfs, you mount a remote file system, so technically, you *could* mount
the home directory in your virtual machine, and run tools like dd, bmap, or
whatever on the file - remotely. It might be a little slower, but it should
work.
Good luck Phil !
On Wed, Sep 9, 2015 at 1:04 PM, Phil Mills <phil.mi...@gmail.com> wrote:
> Win32Imager definitely works better for my setup (and resulted in a
> bootable SD card). I'm happy leaving the VM out of this part of the
> process - detection and mounting of USB devices that get transferred to it
> from the host is INCREDIBLY hit-or-miss on this VM.
>
> First pass at running with a card processed by Win32Imager resulted in
> failure (but I neglected to save out the logs). It booted (yay) and looked
> like it had gotten just to where it wanted to begin writing from the image
> on the USB stick and failed there with a kernel panic.
>
> After that, I tried booting off of a flasher image uSD card, but
> apparently the EEPROM had not been successfully written prior to the
> failure.
>
> Re-built my USB stick and tried again, and it /looks/ like it's going
> better:
>
> - Serial monitor shows an fsck failure , but it continued ("error 2
> (no such file or directory) while executing fsck.ext4 for /dev/mmcblk0p1")
> - Serial monitor stopped on "B" with the USR LED's cycling back and
> forth in a "hey, world, I'm copying your image!" way that I like to see.
>
> LED's eventually settled at "all on", so I've powered down, pulled the uSD
> cards, put power back in and it /looks/ like it's running from the LEDs, but
> * No output on the serial console
>
> After one more hard power cycle (failed to respond to power button) the
> USB network adapter showed up in Windows (still no console output?) and I
> can SSH into the board.
>
> I think that's got me running - now to verify it on a few more boards in
> my pile.
>
>
> Much thanks, Robert.
>
>
> On Wednesday, September 9, 2015 at 11:59:03 AM UTC-6, RobertCNelson wrote:
>
>> On Wed, Sep 9, 2015 at 12:52 PM, Phil Mills <phil....@gmail.com> wrote:
>> > Robert,
>> >
>> > I'm not having success - the serial monitor continues to display
>> "CCCCC" as
>> > soon as it's powered up, so that seems to indicate that it's not
>> finding
>> > anything bootable on that SD card with the blank flasher image.
>>
>> Yeah... "VirtualBox"....
>>
>> Just use 'win32imager" on the base *.img.xz with Windows 7...
>>
>> All the vm's are crap when it comes to writing to a microSD card..
>>
>> >
>> > My setup: 64-bit Debian Jessie (as VirtualBox VM on a Win7 host);
>> > 2GB uSD card, freshly formatted & overwritten in a uSD->USB converter
>> > (Virtualbox won't pass the built-in card reader on my laptop into the
>> VMs)
>> > 16GB uSD card, freshly formatted in a uSD->SD converter
>> > Installed bmaptool ver3.2 via apt-get
>> > Brought 2GB card over to VM
>> >
>> > mounted as /dev/sdd1; did "umount /dev/sdd1" to allow bmaptool to open
>> w/
>> > exclusive access
>> > Ran bmaptool as described above - no errors indicated.
>> > Ejected uSD from VM image, host.
>> >
>> > Inserted 16GB uSD into Win7 system,
>> >
>> > copied 2015-03-01 debian 7.8 image
>> > copied eeprom dump
>> > created new job.txt file with contents as described above (UNIX line
>> > endings)
>> > ejected uSD from Win7
>> >
>> > 2GB uSD into reader on BBB
>> > 16GB uSD into USB adapter, then to USB on BBB
>> > Serial cable connected
>> > TP4 grounded to P8-1
>> > Power applied via mini-USB cable
>> > "CCCCCCCC"
>> >
>> > Suggestions or troubleshooting steps?
>> > I have erased/re-formatted/reloaded the cards 2x with same results.
>>
>> Regards,
>>
>> --
>> Robert Nelson
>> https://rcn-ee.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 beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
--
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 beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
