Buildroot question ?

[bianchi]

Everyone,

I have built a boot image for BeagleBone Black with buildroot,
until :

-rw-r--r-- 1 bianchi bianchi    37264 May  5 13:32 am335x-boneblack.dtb
-rw-r--r-- 1 bianchi bianchi    35372 May  5 13:32 am335x-bone.dtb
-rw-r--r-- 1 bianchi bianchi    42096 May  5 13:32 am335x-evm.dtb
-rw-r--r-- 1 bianchi bianchi    40888 May  5 13:32 am335x-evmsk.dtb
-rw-r--r-- 1 bianchi bianchi 16777216 May  5 16:26 boot.vfat
-rw-r--r-- 1 bianchi bianchi    78292 May  5 13:18 MLO
-rw-r--r-- 1 bianchi bianchi 14505984 May  5 16:26 rootfs.ext2
lrwxrwxrwx 1 bianchi bianchi       11 May  5 16:26 rootfs.ext4 -> rootfs.ext2
-rw-r--r-- 1 bianchi bianchi 10649600 May  5 16:26 rootfs.tar
-rw-r--r-- 1 bianchi bianchi  3424743 May  5 16:26 rootfs.tar.bz2
-rw-r--r-- 1 bianchi bianchi 31283712 May  5 16:26 sdcard.img
-rw-r--r-- 1 bianchi bianchi   625888 May  5 13:17 u-boot.img
-rwxr-xr-x 1 bianchi bianchi    77772 May  5 13:18 u-boot-spl.bin
-rw-r--r-- 1 bianchi bianchi      186 May  5 16:26 uEnv.txt
-rw-r--r-- 1 bianchi bianchi  4995616 May  5 13:32 zImage

My question is,
How can I make it boot until Linux prompt ?

Thanks

[sven.n...@sct.se]

As I see it you should raw copy sdcard.img (dd, etcher) to a sdcard and make sure it gets booted from.
/Sven

[scottellis...@gmail.com]

I don't use the default buildroot config for the BBB (I have my own custom one), but usually you just dd the sdcard.img

  sudo dd if=sdcard.img of=/dev/sdb bs=1M

Assuming your SD card shows up at /dev/sdb



 

[Riko Ho]

I have boot and root partition. And I have put sdcard.img on boot by cp command, will that work?

/*******/
Sent by Android 4.4.2,
Regards,
Riko Ho
/*******/

--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to a topic in the Google Groups "BeagleBoard" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/beagleboard/s1a4xmoJsyU/unsubscribe.
To unsubscribe from this group and all its topics, send an email to beagleboard+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/3769598d-baed-423a-a0d5-145c3aeda726%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[William Hermans]

On Sun, May 7, 2017 at 3:38 PM, Riko Ho <antoni...@gmail.com> wrote:

I have boot and root partition. And I have put sdcard.img on boot by cp command, will that work?

What is a "sdcard.img" ? Elaboration is required.

But typically, no it wont work. Typically, you'll want to use dd, or tar. Then the partition that is meant to be bootable, needs to be marked as bootable using a suitable tool. Such as fdisk, or perhaps sfdisk.

Such a workflow, would look something like this: https://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-RootFileSystem(smallflash)

Keep in mind this is Roberts build guide for  the beaglebone black, and is not intended in this context to be an exact steps example of what you need to do. But it should give you a rough idea of what all needs to be accomplished over all. *If* you're familiar enough with the Linux command line, and tools used.

[William Hermans]

Additionally, if you search the internet for "debootstrap how to" You'll probably find a lot of information on how one would create a rootfs, from scratch, and how to apply that knowledge for this purpose. But again, in this context, there will be a lot of superfluous information. So you'll have to parse what you read, understand what's going on, and take away what you need from it.

[Riko Ho]

Ok thanks for the info, here's about, sdcard.img

I have made two partitions from buildroot, those are files (output/image) I got from buildroot, I extracted and copied them manualy with "cp"

root@bianchi-HP-Pavilion-dv6-Notebook-PC:/media/bianchi/BOOT# ls -al
total 22208
drwxr-xr-x  2 bianchi bianchi    16384 Jan  1  1970 .
drwxr-x---+ 5 root    root        4096 May  7 19:59 ..

-rw-r--r--  1 bianchi bianchi    37264 May  5 13:32 am335x-boneblack.dtb
-rw-r--r--  1 bianchi bianchi    35372 May  5 13:32 am335x-bone.dtb
-rw-r--r--  1 bianchi bianchi    42096 May  5 13:32 am335x-evm.dtb
-rw-r--r--  1 bianchi bianchi    40888 May  5 13:32 am335x-evmsk.dtb

-rw-r--r--  1 bianchi bianchi 16777216 May  5 20:32 boot.vfat

-rw-r--r--  1 bianchi bianchi    78292 May  5 13:18 MLO

-rw-r--r--  1 bianchi bianchi   625888 May  5 13:17 u-boot.img
-rw-r--r--  1 bianchi bianchi    77772 May  5 13:18 u-boot-spl.bin
-rw-r--r--  1 bianchi bianchi      186 May  5 20:32 uEnv.txt

-rw-r--r--  1 bianchi bianchi  4995616 May  5 13:32 zImage

and root :
root@bianchi-HP-Pavilion-dv6-Notebook-PC:/media/bianchi/root# ls -alh
total 54M
drwxr-xr-x  2 root root 4.0K May  7 18:53 .
drwxr-x---+ 5 root root 4.0K May  7 19:59 ..
-rw-r--r--  1 root root  14M May  5 20:32 rootfs.ext2
lrwxrwxrwx  1 root root   11 May  7 18:53 rootfs.ext4 -> rootfs.ext2
-rw-r--r--  1 root root  11M May  5 20:32 rootfs.tar
-rw-r--r--  1 root root  30M May  5 20:32 sdcard.img

 do I need to "dd" sdcard.img to "root" ?

That images booted this far,
----------------------
U-Boot SPL 2016.09.01 (May 05 2017 - 13:17:29)
Trying to boot from MMC1
reading args
spl_load_image_fat_os: error reading image args, err - -1
reading u-boot.img
reading u-boot.img
reading u-boot.img
reading u-boot.img


U-Boot 2016.09.01 (May 05 2017 - 13:17:29 +0800)

DRAM:  512 MiB
NAND:  0 MiB
MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
reading uboot.env

** Unable to read "uboot.env" from mmc0:1 **
Using default environment

Net:  
Warning: ethernet@4a100000 using MAC address from ROM
eth0: ethernet@4a100000
Hit any key to stop autoboot:  0
switch to partitions #0, OK
mmc0 is current device
SD/MMC found on device 0
reading boot.scr
** Unable to read file boot.scr **
reading uEnv.txt
186 bytes read in 6 ms (30.3 KiB/s)
Loaded env from uEnv.txt
Importing environment from mmc0 ...
Running uenvcmd ...
reading /zImage
4995616 bytes read in 329 ms (14.5 MiB/s)
reading /am335x-boneblack.dtb
37264 bytes read in 10 ms (3.6 MiB/s)
bootargs=console=ttyO0,

115200n8 root=/dev/mmcblk0p2 rw rootfstype=ext4 rootwait
## Flattened Device Tree blob at 88000000
   Booting using the fdt blob at 0x88000000
   Loading Device Tree to 8fff3000, end 8ffff18f ... OK

Starting kernel ...

[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Initializing cgroup subsys cpuacct
[    0.000000] Linux version 4.4.32 (bianchi@bianchi-HP-Pavilion-dv6-Notebook-PC) (gcc version 5.4.0 (Buildroot 2017.02) ) #1 SMP Fri May 5 137
[    0.000000] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c5387d
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[    0.000000] Machine model: TI AM335x BeagleBone Black
[    0.000000] cma: Reserved 16 MiB at 0x9e800000
[    0.000000] Memory policy: Data cache writeback
[    0.000000] CPU: All CPU(s) started in SVC mode.
[    0.000000] AM335X ES2.1 (sgx neon )
[    0.000000] PERCPU: Embedded 14 pages/cpu @df912000 s24936 r8192 d24216 u57344
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 129408
[    0.000000] Kernel command line: console=ttyO0,115200n8 root=/dev/mmcblk0p2 rw rootfstype=ext4 rootwait
[    0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes)
[    0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
[    0.000000] Memory: 481840K/522240K available (6772K kernel code, 760K rwdata, 2276K rodata, 444K init, 8263K bss, 24016K reserved, 16384K )
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
[    0.000000]     vmalloc : 0xe0800000 - 0xff800000   ( 496 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xe0000000   ( 512 MB)
[    0.000000]     pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
[    0.000000]     modules : 0xbf000000 - 0xbfe00000   (  14 MB)
[    0.000000]       .text : 0xc0008000 - 0xc08de58c   (9050 kB)
[    0.000000]       .init : 0xc08df000 - 0xc094e000   ( 444 kB)
[    0.000000]       .data : 0xc094e000 - 0xc0a0c278   ( 761 kB)
[    0.000000]        .bss : 0xc0a0e000 - 0xc121fe20   (8264 kB)
[    0.000000] Running RCU self tests
[    0.000000] Hierarchical RCU implementation.
[    0.000000]  RCU lockdep checking is enabled.
[    0.000000]  Build-time adjustment of leaf fanout to 32.
[    0.000000]  RCU restricting CPUs from NR_CPUS=2 to nr_cpu_ids=1.
[    0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=32, nr_cpu_ids=1
[    0.000000] NR_IRQS:16 nr_irqs:16 16
[    0.000000] IRQ: Found an INTC at 0xfa200000 (revision 5.0) with 128 interrupts
[    0.000000] OMAP clockevent source: timer2 at 24000000 Hz
[    0.000017] sched_clock: 32 bits at 24MHz, resolution 41ns, wraps every 89478484971ns
[    0.000039] clocksource: timer1: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 79635851949 ns
[    0.000086] OMAP clocksource: timer1 at 24000000 Hz
[    0.000597] clocksource_probe: no matching clocksources found
[    0.001450] Console: colour dummy device 80x30
[    0.001506] Lock dependency validator: Copyright (c) 2006 Red Hat, Inc., Ingo Molnar
[    0.001515] ... MAX_LOCKDEP_SUBCLASSES:  8
[    0.001523] ... MAX_LOCK_DEPTH:          48
[    0.001530] ... MAX_LOCKDEP_KEYS:        8191
[    0.001537] ... CLASSHASH_SIZE:          4096
[    0.001545] ... MAX_LOCKDEP_ENTRIES:     32768
[    0.001552] ... MAX_LOCKDEP_CHAINS:      65536
[    0.001559] ... CHAINHASH_SIZE:          32768
[    0.001567]  memory used by lock dependency info: 5167 kB
[    0.001574]  per task-struct memory footprint: 1536 bytes
[    0.001600] Calibrating delay loop... 996.14 BogoMIPS (lpj=4980736)
[    0.078683] pid_max: default: 32768 minimum: 301
[    0.079046] Security Framework initialized
[    0.079166] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.079179] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.082145] Initializing cgroup subsys io
[    0.082249] Initializing cgroup subsys memory
[    0.082338] Initializing cgroup subsys devices
[    0.082462] Initializing cgroup subsys freezer
[    0.082536] Initializing cgroup subsys perf_event
[    0.082600] CPU: Testing write buffer coherency: ok
[    0.084093] CPU0: thread -1, cpu 0, socket -1, mpidr 0
[    0.084219] Setting up static identity map for 0x80008280 - 0x800082f0
[    0.087906] Brought up 1 CPUs
[    0.087929] SMP: Total of 1 processors activated (996.14 BogoMIPS).
[    0.087940] CPU: All CPU(s) started in SVC mode.
[    0.092001] devtmpfs: initialized
[    0.129733] VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3
[    0.229819] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[    0.232251] pinctrl core: initialized pinctrl subsystem
[    0.237416] NET: Registered protocol family 16
[    0.243292] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.245324] cpuidle: using governor ladder
[    0.245355] cpuidle: using governor menu
[    0.257989] OMAP GPIO hardware version 0.1
[    0.283457] No ATAGs?
[    0.283493] hw-breakpoint: debug architecture 0x4 unsupported.
[    0.284095] omap4_sram_init:Unable to allocate sram needed to handle errata I688
[    0.284112] omap4_sram_init:Unable to get sram pool needed to handle errata I688
[    0.325914] edma 49000000.edma: TI EDMA DMA engine driver
[    0.330365] SCSI subsystem initialized
[    0.332372] omap_i2c 44e0b000.i2c: could not find pctldev for node /ocp/l4_wkup@44c00000/scm@210000/pinmux@800/pinmux_i2c0_pins, deferring e
[    0.332479] omap_i2c 4819c000.i2c: could not find pctldev for node /ocp/l4_wkup@44c00000/scm@210000/pinmux@800/pinmux_i2c2_pins, deferring e
[    0.332749] pps_core: LinuxPPS API ver. 1 registered
[    0.332761] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giom...@linux.it>
[    0.332815] PTP clock support registered
[    0.336807] clocksource: Switched to clocksource timer1
[    0.475320] NET: Registered protocol family 2
[    0.477505] TCP established hash table entries: 4096 (order: 2, 16384 bytes)
[    0.477600] TCP bind hash table entries: 4096 (order: 5, 147456 bytes)
[    0.478801] TCP: Hash tables configured (established 4096 bind 4096)
[    0.479022] UDP hash table entries: 256 (order: 2, 20480 bytes)
[    0.479196] UDP-Lite hash table entries: 256 (order: 2, 20480 bytes)
[    0.480097] NET: Registered protocol family 1
[    0.481786] RPC: Registered named UNIX socket transport module.
[    0.481810] RPC: Registered udp transport module.
[    0.481821] RPC: Registered tcp transport module.
[    0.481830] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.484539] hw perfevents: enabled with armv7_cortex_a8 PMU driver, 5 counters available
[    0.489341] futex hash table entries: 256 (order: 2, 16384 bytes)
[    0.489585] audit: initializing netlink subsys (disabled)
[    0.489828] audit: type=2000 audit(0.480:1): initialized
[    0.494432] VFS: Disk quotas dquot_6.6.0
[    0.494708] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    0.497230] NFS: Registering the id_resolver key type
[    0.497631] Key type id_resolver registered
[    0.497648] Key type id_legacy registered
[    0.497838] jffs2: version 2.2. (NAND) (SUMMARY)  �© 2001-2006 Red Hat, Inc.
[    0.503282] io scheduler noop registered
[    0.503320] io scheduler deadline registered
[    0.503375] io scheduler cfq registered (default)
[    0.505468] pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800 size 568
[    0.508557] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[    0.514321] omap_uart 44e09000.serial: no wakeirq for uart0
[    0.514921] 44e09000.serial: ttyO0 at MMIO 0x44e09000 (irq = 158, base_baud = 3000000) is a OMAP UART0
[    1.236611] console [ttyO0] enabled
[    1.277485] brd: module loaded
[    1.303236] loop: module loaded
[    1.309348] mtdoops: mtd device (mtddev=name/number) must be supplied
[    1.376811] davinci_mdio 4a101000.mdio: davinci mdio revision 1.6
[    1.383196] davinci_mdio 4a101000.mdio: detected phy mask fffffffe
[    1.393416] libphy: 4a101000.mdio: probed
[    1.397780] davinci_mdio 4a101000.mdio: phy[0]: device 4a101000.mdio:00, driver SMSC LAN8710/LAN8720
[    1.408881] cpsw 4a100000.ethernet: Detected MACID = 88:c2:55:81:5a:33
[    1.416193] cpsw 4a100000.ethernet: cpts: overflow check period 850
[    1.427944] mousedev: PS/2 mouse device common for all mice
[    1.433803] i2c /dev entries driver
[    1.439378] omap_hsmmc 48060000.mmc: Got CD GPIO
[    1.514992] mmc0: host does not support reading read-only switch, assuming write-enable
[    1.524022] ledtrig-cpu: registered to indicate activity on CPUs
[    1.531676] oprofile: using arm/armv7
[    1.536338] Initializing XFRM netlink socket
[    1.541310] NET: Registered protocol family 10
[    1.547693] mmc0: Problem switching card into high-speed mode!
[    1.554080] mmc0: new SDHC card at address 0001
[    1.562458] sit: IPv6 over IPv4 tunneling driver
[    1.569690] NET: Registered protocol family 17
[    1.574431] NET: Registered protocol family 15
[    1.579562] Key type dns_resolver registered
[    1.584219] omap_voltage_late_init: Voltage driver support not added
[    1.590941] sr_dev_init: No voltage domain specified for smartreflex0. Cannot initialize
[    1.599424] sr_dev_init: No voltage domain specified for smartreflex1. Cannot initialize
[    1.609356] ThumbEE CPU extension supported.
[    1.613867] Registering SWP/SWPB emulation handler
[    1.619000] SmartReflex Class3 initialized
[    1.625579] mmcblk0: mmc0:0001 SD16G 14.6 GiB
[    1.634682]  mmcblk0: p1 p2
[    1.685441] tps65217 0-0024: TPS65217 ID 0xe version 1.2
[    1.691983] omap_i2c 44e0b000.i2c: bus 0 rev0.11 at 400 kHz
[    1.699023] mmc1: MAN_BKOPS_EN bit is not set
[    1.707089] omap_i2c 4819c000.i2c: bus 2 rev0.11 at 100 kHz
[    1.714543] hctosys: unable to open rtc device (rtc0)
[    1.719967] sr_init: No PMIC hook to init smartreflex
[    1.725496] sr_init: platform driver register failed for SR
[    1.760028] mmc1: new high speed MMC card at address 0001
[    1.771238] mmcblk1: mmc1:0001 S10004 3.56 GiB
[    1.777404] mmcblk1boot0: mmc1:0001 S10004 partition 1 4.00 MiB
[    1.786455] mmcblk1boot1: mmc1:0001 S10004 partition 2 4.00 MiB
[    1.798666]  mmcblk1: p1
[    1.809899] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[    1.818691] VFS: Mounted root (ext4 filesystem) on device 179:2.
[    1.827562] devtmpfs: error mounting -2
[    1.832397] Freeing unused kernel memory: 444K (c08df000 - c094e000)
[    1.839120] This architecture does not have kernel memory protection.
[    1.846348] Kernel panic - not syncing: No working init found.  Try passing init= option to kernel. See Linux Documentation/init.txt for gu.
[    1.860170] ---[ end Kernel panic - not syncing: No working init found.  Try passing init= option to kernel. See Linux Documentation/init.t.
[   80.376665] random: nonblocking pool is initialized

--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to a topic in the Google Groups "BeagleBoard" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/beagleboard/s1a4xmoJsyU/unsubscribe.

To unsubscribe from this group and all its topics, send an email to beagleboard...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CALHSORoXtN6S%2BoYbsp%2ByN3vopzSS1Do%3Dd00DzY7Sc4Q9Jpo4nw%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

--
/*******/
Sent by Ubuntu LTS 16.04,
谢谢,
Kind regards,
Riko Ho
/*******/

[Riko Ho]

Thanks for the clue, I'll keep posted ..

--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to a topic in the Google Groups "BeagleBoard" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/beagleboard/s1a4xmoJsyU/unsubscribe.

To unsubscribe from this group and all its topics, send an email to beagleboard...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CALHSORoXtN6S%2BoYbsp%2ByN3vopzSS1Do%3Dd00DzY7Sc4Q9Jpo4nw%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

[Riko Ho]

I hadn't done :

$ sudo dd if=buildroot/output/images/rootfs.ext4 of=/dev/sdb2

may be that's the problem ?

--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to a topic in the Google Groups "BeagleBoard" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/beagleboard/s1a4xmoJsyU/unsubscribe.

To unsubscribe from this group and all its topics, send an email to beagleboard...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CALHSORrOCow8%2BJR9T2wRZGcvQ5YEh3Y8t5q3yT2MABbPsZMCoA%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

[Robert Nelson]

On Sun, May 7, 2017 at 7:42 PM, Riko Ho <antoni...@gmail.com> wrote:
> I hadn't done :
>
> $ sudo dd if=buildroot/output/images/rootfs.ext4 of=/dev/sdb2
>
> may be that's the problem ?

NO that's another problem..

sudo dd if=./sdcard.img of=/dev/sdb

It's labled as "sdcard" so you might as well use it..

Regards,


--
Robert Nelson
https://rcn-ee.com/

[Riko Ho]

I've been reading on it, I'll follow it, hopefully it will work..

On 08/05/17 07:39, William Hermans wrote:

Such a workflow, would look something like this: https://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-RootFileSystem(smallflash)

[Robert Nelson]

On Sun, May 7, 2017 at 7:59 PM, Riko Ho <antoni...@gmail.com> wrote:
> So I will use the whole partition for sdcard.img ? I don't need /boot and
> /root ?
>
> I'm confused now..

Well it's labeled as "sdcard.img" not "rootfs.img" or "boot.img"...

So give

sudo dd if=./sdcard.img of=/dev/sdb

a try, if it dooesn't work then go to:

https://buildroot.org/support.html

[William Hermans]

On Sun, May 7, 2017 at 5:42 PM, Riko Ho <antoni...@gmail.com> wrote:

I hadn't done :

$ sudo dd if=buildroot/output/images/rootfs.ext4 of=/dev/sdb2

may be that's the problem ?

As Robert said, no that's not the problem. I'm kind of wondering how old the sources are that buildroot is using. Because all modern official images now days use a single partition. The date on uboot, looks reasonably new, but that's not to say the sources are current.

You know, if you're really good at working with images, you can actually use debootstrap to build your own image, add in beagleboard.org's repo, download a kernel image, and get it working reasonably quick, and easily. I've also no idea what kernel version you're using there *looks* looks like 4.4.32 it seems.

Just out of curiosity, is there any reason why you have to build your own images ?  The newer testing images are very stable from what I've experienced( a lot of experience by the way ), and have features you may want, that probably are not included in the ones buildroot is building for you. For instance uboot is now able to load device tree overlays, and someone, I'm not sure who, has made the TI kernel based images a pleasure to work with. e.g. there are no longer a ton of kernel modules loaded at boot if you do not need them. They only load as you need them, it seems.

[Riko Ho]

It works already with "dd" sdcard.img into /dev/sdb2,

I built my own image, for my knowledge on how to do it.

-- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to a topic in the Google Groups "BeagleBoard" group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/beagleboard/s1a4xmoJsyU/unsubscribe. To unsubscribe from this group and all its topics, send an email to beagleboard...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CALHSORqc8u3%2B5gp-xXvSORQvge905cvtQ1fNi9MjSw9xgjjtQQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.

[Riko Ho]

Everyone,

I tried to run :

./beagleboard.org_jessie_image.sh, and at the end I got below :

Processing triggers for libc-bin (2.19-18+deb8u9) ...
Processing triggers for initramfs-tools (0.120+deb8u3-1rcnee0~bpo80+20170219) ...
update-initramfs: Generating /boot/initrd.img-4.4.62-ti-r99
Processing triggers for dbus (1.8.22-0+deb8u1) ...
Processing triggers for python-support (1.0.15) ...
Processing triggers for systemd (230-7~bpo8+2) ...
Errors were encountered while processing:
 c9-core-installer
E: Sub-process /usr/bin/dpkg returned an error code (1)
Log: umount: [/home/bianchi/Documents/image-builder/ignore/tmp.6jaO2x0GNv/dev/pts]
Log: umount: [/home/bianchi/Documents/image-builder/ignore/tmp.6jaO2x0GNv/proc]
Log: umount: [/home/bianchi/Documents/image-builder/ignore/tmp.6jaO2x0GNv/sys]
Log: umount: [/home/bianchi/Documents/image-builder/ignore/tmp.6jaO2x0GNv/run]

Does anyone know what's wrong with it ?

[Robert Nelson]

It's a failure in qemu, run the image-builder on an arm target and it'll be fine.

Regards,

[Robert Nelson]

On Tue, May 9, 2017 at 9:11 PM, Riko Ho <antoni...@gmail.com> wrote:
> do you mean that I need to run qemu service on my ubuntu host system ? how
> to do that ?
>

No, it means qemu (google qemu to see what it is) choked on the armhf
-> x86 translation.. which is why the readme in the image-builder
project says to use a real ARM device.

[Robert Nelson]

On Tue, May 9, 2017 at 10:35 PM, Riko Ho <antoni...@gmail.com> wrote:
> so I copy img-builder and run it on my beagle board ?

I personally use, WandBoard's, omap5_uevm's, X15's, or Jetson's tk as
they have more ram and more processing power then teh BBB..

But if you want to run it on the BBB go right ahead..

> how can I modify the source code of LXDE ?

The same way you modify any source code.

Go find the source, download it, modify it, build it, run it.

I'm not a member of the lxde project, it's up to YOU to figure where
the source it located, to download it, to modify it, to build it and
to run it.

[Robert Nelson]

On Tue, May 9, 2017 at 10:48 PM, Riko Ho <antoni...@gmail.com> wrote:
> Hmm....in that case, I want to run qemu on my ubuntu host....

Nice thought, BUT the image-builder script is already using "qemu"
when you run it on an x86. So your not actually doing or changing
anything..

> I tried to rebuild debian 8 now...and see if I got qemu error again,

Oh you'll get the same issue "again", and i'll say once again it's
qemu, run it on an ARM platform.

[Robert Nelson]

On Tue, May 9, 2017 at 10:49 PM, Riko Ho <antoni...@gmail.com> wrote:
> Hi Robert,
> after I modify it, how can I hook it with my beagle ?

Hook what up?

I'm sorry, but it's pretty obvious..

You need to start with something "WAY" smaller.

LXDE is going to be too much of a project for your "first" build/hookup/etc..

[Robert Nelson]

On Wed, May 10, 2017 at 1:52 AM, Riko Ho <antoni...@gmail.com> wrote:
> What do you think "WAY" smaller ?
>
> Is there any other ways fixing "Errors were encountered while processing:
> c9-core-installer", beside running it on board ?
> I don't have other boards accept this BBB.

Sure, patches welcome.

[Robert Nelson]

On Wed, May 10, 2017 at 9:12 PM, Riko Ho <antoni...@gmail.com> wrote:
> Ok, I'll see what I can do with the patch, can you tell me in your script,
> where is that "c9-core-installer" residing in the script ?
>
> A clue please ?

Well it's a debian package.

The issue: c9-core-installer call's npm.. npm has issues running in a
qemu environment..

I've dealt with it enough in the past, it's not something i'm going to
waste time working on.

So patches welcome.

[Riko Ho]

Hello everyone,

Is there any possibilities for running beagle image on Virtual Machine
Manager ?

Thanks,

[ve7...@gmail.com]

I expect you've either given up or sorted it out but for anyone else reading this thread:

Buildroot packs the FAT and ext4 partitions into sdcard.img so all you need to do is dd them onto your card directly (/dev/mmcblk0 or /dev/sd? depending on your hosts card interface) ... extracting the files is going backwards !

Note the Buildroot image does not follow the newer RAW approach for MLO, u-boot.img and so in most you won't actually be using the BR u-boot version, unless you manually setup the card (and even then I'm having issues with my BBB using the uSD over the eMMC) but using the sdcard.img still lets you run from the BR generated uEnv.txt, kernel and rootfs.