Re: [beagleboard] QEMU emulation of BeagleBone and Raring
Hi, Qemu static means you do not run vm, it is just chroot into /path/to/arm/root/filesystem having qemu-arm-static in /path/to/arm/root/filesystem/usr/bin You provided argument for qemu vm which is second option in my question and I have no network issues there, only uboot question. Thanks. On Thursday, April 3, 2014 12:37:42 AM UTC+1, Nuno wrote: On 04/02/2014 06:05 PM, Boris Rybalkin wrote: roblem here I have no network: You might want to try adding something like the following to your qemu calling parameters: -net nic,model=rtl8139 -net user regards, Nuno -- http://aeminium.org/nuno/ -- 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.
Re: [beagleboard] QEMU emulation of BeagleBone and Raring
Finally I figured out: http://geek.co.il/2010/03/14/how-to-build-a-chroot-jail-environment-for-centos losetup -o 101711872 /dev/loop0 BBB-eMMC-flasher-ubuntu-13.10-2014-02-16-2gb.img mount /dev/loop0 image sudo mount --bind /dev image/dev sudo mount --bind /proc image/proc mkdir image/run/resolvconf cp /run/resolvconf/resolv.conf image/run/resolvconf/resolv.conf That fixed chroot network problems. I also decided to build new images on device (no qemu at all) in chrooted environment in continuous integration mode. Thanks. On Thursday, April 3, 2014 8:29:48 AM UTC+1, Boris Rybalkin wrote: Hi, Qemu static means you do not run vm, it is just chroot into /path/to/arm/root/filesystem having qemu-arm-static in /path/to/arm/root/filesystem/usr/bin You provided argument for qemu vm which is second option in my question and I have no network issues there, only uboot question. Thanks. On Thursday, April 3, 2014 12:37:42 AM UTC+1, Nuno wrote: On 04/02/2014 06:05 PM, Boris Rybalkin wrote: roblem here I have no network: You might want to try adding something like the following to your qemu calling parameters: -net nic,model=rtl8139 -net user regards, Nuno -- http://aeminium.org/nuno/ -- 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.
Re: [beagleboard] QEMU emulation of BeagleBone and Raring
Hi,
I want to automate installation of additional packages to default BBB image
without using real device.
Option 1: qemu static
Problem here I have no network:
# ping 8.8.8.8
qemu: Unsupported syscall: 184
qemu: Unsupported syscall: 184
ping: cap_get_proc: Function not implemented
Do you have network working when you build images?
Option 2: Use full VM
qemu-system-arm -M versatilepb -cpu cortex-a8 -kernel ./vmlinuz -hda
BBB-eMMC-flasher-ubuntu-13.10-2014-01-24-2gb.img -m 256 -append
root=/dev/sda2 rootfstype=ext4 rw -redir tcp:5022::22
kernel:
http://ports.ubuntu.com/ubuntu-ports/dists/lucid/main/installer-armel/current/images/versatile/netboot/vmlinuz
On boot it says 'The disk drive for /boot/ubuut is not ready, press S to
skip'
If I press S it boots fine and I can run my build procedure.
Do you know if that uboot can disabled/auto skipped?
For the reference my similar raspberry image builder:
https://github.com/syncloud/owncloud-setup/blob/master/build-image.sh
Thanks you.
On Saturday, November 23, 2013 12:47:01 AM UTC, M Robinson wrote:
Slow down a bit...
On Thursday, September 19, 2013 7:42:43 AM UTC-4, Charles Steinkuehler
wrote:
On 9/19/2013 5:41 AM, garyamort wrote:
While digging through Robert Nelson's omap image builder, I noticed
that
he's using Qemu at some point to emulate the Beagle Bone from the PC
and
download/install packages.
Digging through his code left me confused... I understand he is using
the
qemu-arm-static executable in order to execute a sequence of commands,
but
he also seems to be pulling some code from linuxCnC for the emulator
image,
leaving me confused.
snip
Can someone give me a summary of how to invoke qemu-arm-system to use
the
latest released omap4 images from
http://ports.ubuntu.com/ubuntu-ports/dists/raring/main/installer-armhf/current/images/omap4/netboot/http://www.google.com/url?q=http%3A%2F%2Fports.ubuntu.com%2Fubuntu-ports%2Fdists%2Fraring%2Fmain%2Finstaller-armhf%2Fcurrent%2Fimages%2Fomap4%2Fnetboot%2Fsa=Dsntz=1usg=AFQjCNHq5GkpdfBYh075PkJNWzM6EkKPFQ
Robert's image builder isn't actually pulling in anything from LinuxCNC,
those are hooks for my MachineKit image:
http://bb-lcnc.blogspot.com/p/machinekit_16.htmlhttp://www.google.com/url?q=http%3A%2F%2Fbb-lcnc.blogspot.com%2Fp%2Fmachinekit_16.htmlsa=Dsntz=1usg=AFQjCNF8gaoh0QEDJ7jAment9Iv1RsW-dw
...which is built with Robert's scripts and a slightly different
configuration. Robert has pulled my changes to his scripts and left the
MachineKit configuration files as an example of how to build a custom
image. If you don't create a custom config file (based on
config.inhttp://www.google.com/url?q=http%3A%2F%2Fconfig.insa=Dsntz=1usg=AFQjCNFD_lndHNrr5UbhFINTE1ySWg3Apwor
config.machinekit), you'll get Robert's default build of various Debian
and Ubuntu images.
As for the qemu directions, it's super simple:
Setup a root filesystem for an ARM device. You can use debootstrap to
make one from scratch (the way Robert's scripts do), or use one of the
various pre-made root filesystems.
Which is this? It makes me think it's the SD card image, but...I'm not
flashing my real Beaglebone for this exercise!
Copy the qemu-arm-static binary into ${arm-root-fs}/usr/bin/
arm-root-fs=/path/to/arm/root/filesystem/
sudo cp $(which qemu-arm-static) ${arm-root-fs}/usr/bin/
Then all you do is:
sudo chroot ${arm-root-fs} /bin/sh
...and you're running a shell in your arm rootfs. Type uname -a and
notice you are no longer on an x86 CPU! :)
OK, this chroot procedure kind of reminds me of when my grub bootloader
kept dying on me everytime I tried to fix it. But I'm still not sure what
reference to use for building the root file system.
--
Charles Steinkuehler
cha...@steinkuehler.net
--
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.
[beagleboard] Build persinal device with owncloud preinstalled
Hi, I've been using BeagleBone Black combined with ownCloud for some time as my personal file storage. I am happy with the setup so I decided to share the instruction. I am doing this in top of Robert Nelson's Ubuntu 13.10 Flasher image (http://elinux.org/BeagleBoardUbuntu) I hope this is not against its license otherwise please let me know. We with my friend tried to make this as open as possible, so all the image building scripts are also available: https://github.com/syncloud (even site/instruction is open source! :)) If anyone is interested it is here syncloud.org Thanks! -- 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/groups/opt_out.
[beagleboard] Re: Durability of beaglebone black
Mine is pretty durable :) https://plus.google.com/107046161917805124062/posts/BaCemb9a25a On Friday, January 31, 2014 3:45:37 PM UTC, Ankush Grover wrote: I am planning to buy a Beaglebone black. I am new to this world of development boards. I wanna ask is whether the board is durable or not. Actually the region from where I belong, there is no such boom of these sort of development boards and embedded systems. But I am very interested in learning this stuff. Beaglebone black is pretty costly over here so i was pretty confused before giving it a shot. Anyone with information about the query please do help 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 beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [beagleboard] modifying flasher script
I think I understand what is happening. 1. microSD-flasher copies files and generates fstab on microSD 2. Then auto started eMMC-flasher copies files and generates its own fstab So I need to change /opt/scripts/tools/beaglebone-black-eMMC-flasher.sh And then run https://raw.github.com/RobertCNelson/tools/master/scripts/beaglebone-black-make-microSD-flasher-from-eMMC.sh On Friday, January 31, 2014 2:01:32 AM UTC, RobertCNelson wrote: On Thu, Jan 30, 2014 at 7:22 PM, Boris Rybalkin riba...@gmail.comjavascript: wrote: Hi, I am trying to create custom flasher image using https://raw.github.com/RobertCNelson/tools/master/scripts/beaglebone-black-make-microSD-flasher-from-eMMC.sh It works fine and flasher is doing its job, but when I try to modify this script to add fstab entry resulting flasher unable to finish flashing with all leds going on and off constantly. I am adding simple /dev/sda1 /data ext4 defaults 0 0 my modify script: wget https://raw.github.com/RobertCNelson/tools/master/scripts/beaglebone-black-make-microSD-flasher-from-eMMC.sh sed -i '/debugfs.*fstab/a \\techo /dev/sda1 /data ext4 defaults 0 0 /tmp/rootfs/etc/fstab' beaglebone-black-make-microSD-flasher-from-eMMC.sh chmod +x beaglebone-black-make-microSD-flasher-from-eMMC.sh ./beaglebone-black-make-microSD-flasher-from-eMMC.sh If I insert this line into /etc/fstab on a flashed device mounting works fine, but I would like it to come from flasher. Is this the right way to modify fstab for flasher? Well, that change shouldn't cause the condition you see. Your change is perfectly fine. I'd say it's more random bad luck, maybe an external cape plugged in on the eMMC pins? Regards, -- Robert Nelson http://www.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/groups/opt_out.
[beagleboard] modifying flasher script
Hi, I am trying to create custom flasher image using https://raw.github.com/RobertCNelson/tools/master/scripts/beaglebone-black-make-microSD-flasher-from-eMMC.sh It works fine and flasher is doing its job, but when I try to modify this script to add fstab entry resulting flasher unable to finish flashing with all leds going on and off constantly. I am adding simple /dev/sda1 /data ext4 defaults 0 0 my modify script: wget https://raw.github.com/RobertCNelson/tools/master/scripts/beaglebone-black-make-microSD-flasher-from-eMMC.sh sed -i '/debugfs.*fstab/a \\techo /dev/sda1 /data ext4 defaults 0 0 /tmp/rootfs/etc/fstab' beaglebone-black-make-microSD-flasher-from-eMMC.sh chmod +x beaglebone-black-make-microSD-flasher-from-eMMC.sh ./beaglebone-black-make-microSD-flasher-from-eMMC.sh If I insert this line into /etc/fstab on a flashed device mounting works fine, but I would like it to come from flasher. Is this the right way to modify fstab for flasher? Thanks. -- 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/groups/opt_out.
