building meta-ti + poky HOWTO?

building meta-ti + poky HOWTO?

[Russell Senior]

I have been unable to get a booting image out of Angstrom in about
three weeks of trying and several unanswered queries to the mailing
list and elsewhere.  In my continuing effort to get a build system
that produces an image that boots on my beaglebone, I'd like to try
building meta-ti with poky, just to see if that fails for me too.

Is there a howto on combining meta-ti with poky?  Can anyone give
me brief but specific guidance on where I need to unpack stuff and
what configuration files I need to tweek and what those tweeks are?

Thanks!


-- 
Russell Senior, President
russell@personaltelco.net

Re: building meta-ti + poky HOWTO?

[Brian Hutchinson]

I may be out of the loop but if you follow the yocto way of doing
things .... poky will produce a BeagleBoard image without having to
use meta-ti and I think you can use that on beaglebone.  Some one
correct me if I'm sending Russell in the weeds.

I've been able to build yocto images for BeagleBoard but haven't tried
them on the bone yet.

Last I checked meta-ti with poky still had some issues.

Regards,

Brian

Re: building meta-ti + poky HOWTO?

[Denys Dmytriyenko]

On Thu, Apr 05, 2012 at 02:36:59PM -0400, Brian Hutchinson wrote:
> I may be out of the loop but if you follow the yocto way of doing
> things .... poky will produce a BeagleBoard image without having to
> use meta-ti and I think you can use that on beaglebone.  Some one
> correct me if I'm sending Russell in the weeds.
> 
> I've been able to build yocto images for BeagleBoard but haven't tried
> them on the bone yet.

You shouldn't be using BeagleBoard kernel images on the BeagleBone. You might 
get very basic ARM support, if you are lucky, but otherwise it won't work.

While both share "Beagle" in the name, they are based on different SOCs with 
different peripherals, etc.

-- 
Denys

Re: building meta-ti + poky HOWTO?

[Denys Dmytriyenko]

On Thu, Apr 05, 2012 at 11:09:21AM -0700, Russell Senior wrote:
> 
> I have been unable to get a booting image out of Angstrom in about
> three weeks of trying and several unanswered queries to the mailing
> list and elsewhere.  In my continuing effort to get a build system
> that produces an image that boots on my beaglebone, I'd like to try
> building meta-ti with poky, just to see if that fails for me too.

As far as I remember, you are having problems with rootfs images that generate 
an entire SD card disk image with multiple partitions, e.g. Cloud9 image. 
There are known issues with the tools used to do that, like sometimes fdisk 
not making the correct MBR and partition table that BootROM can boot from. So 
far it seems to depend on the host distro and their tools. This area still 
needs further investigation and probably the use of different tools...

But you should not be stuck on this - why don't you use the individual pieces, 
like kernel image, rootfs and load them on SD card yourself, manually? Try 
working around the issue...

-- 
Denys

Re: building meta-ti + poky HOWTO?

[Brian Hutchinson]

On Thu, Apr 5, 2012 at 3:07 PM, Denys Dmytriyenko <denis@denix.org> wrote:
> You shouldn't be using BeagleBoard kernel images on the BeagleBone. You might
> get very basic ARM support, if you are lucky, but otherwise it won't work.
>

Sorry! For some reason I thought early on the beagleboard images would
work.  I've actually not built anything from scratch for my beaglebone
yet.  But I can say the BeagleBoard image built by poky works without
meta-ti.

Russell, if you search the archives you'll see about a month ago some
folks (James Abernathy comes to mind) were having a discussion on how
to work around and get meta-ti working with poky.

Regards,

Brian

Re: building meta-ti + poky HOWTO?

[Russell Senior]

>>>>> "Denys" == Denys Dmytriyenko <denis@denix.org> writes:

Russell> I have been unable to get a booting image out of Angstrom in
Russell> about three weeks of trying and several unanswered queries to
Russell> the mailing list and elsewhere.  In my continuing effort to
Russell> get a build system that produces an image that boots on my
Russell> beaglebone, I'd like to try building meta-ti with poky, just
Russell> to see if that fails for me too.

Denys> As far as I remember, you are having problems with rootfs
Denys> images that generate an entire SD card disk image with multiple
Denys> partitions, e.g. Cloud9 image.  There are known issues with the
Denys> tools used to do that, like sometimes fdisk not making the
Denys> correct MBR and partition table that BootROM can boot from. So
Denys> far it seems to depend on the host distro and their tools. This
Denys> area still needs further investigation and probably the use of
Denys> different tools...

I am building on a Debian/unstable box with a core i7 cpu and 24 gig of RAM.

Denys> But you should not be stuck on this - why don't you use the
Denys> individual pieces, like kernel image, rootfs and load them on
Denys> SD card yourself, manually? Try working around the issue...

I have tried taking the pre-baked Angstrom image from here:

  http://www.angstrom-distribution.org/demo/beaglebone/Angstrom-Cloud9-IDE-eglibc-ipk-v2012.02-core-beaglebone-2012.02.14.img.xz

(which works for me), and replacing the uImage on the vfat partition
by copying over the existing one with one I built.  That boots, but the
rootfs isn't aligned (different kernel/module versions?).  

If I then try dropping in my rootfs, by reformatting the ext4fs and
untarring the rootfs tarball I built, I get 0.6 seconds into the boot
and then the boot stalls with some udevd messages, like so:

  U-Boot SPL 2011.09-00010-g81c8c79 (Feb 13 2012 - 14:48:03)
  Texas Instruments Revision detection unimplemented
  No AC power, disabling frequency switch
  OMAP SD/MMC: 0
  reading u-boot.img
  reading u-boot.img


  U-Boot 2011.09-00010-g81c8c79 (Feb 13 2012 - 14:48:03)

  I2C:   ready
  DRAM:  256 MiB
  No daughter card present
  NAND:  HW ECC Hamming Code selected
  nand_get_flash_type: unknown NAND device: Manufacturer ID: 0x10, Chip ID: 0x10
  No NAND device found!!!
  0 MiB
  MMC:   OMAP SD/MMC: 0
  *** Warning - readenv() failed, using default environment

  Net:   cpsw
  Hit any key to stop autoboot:  0 
  SD/MMC found on device 0
  reading uEnv.txt

  33 bytes read
  Loaded environment from uEnv.txt
  Importing environment from mmc ...
  reading uImage

  3140320 bytes read
  ## Booting kernel from Legacy Image at 80007fc0 ...
     Image Name:   Angstrom/3.2/beaglebone
     Image Type:   ARM Linux Kernel Image (uncompressed)
     Data Size:    3140256 Bytes = 3 MiB
     Load Address: 80008000
     Entry Point:  80008000
     Verifying Checksum ... OK
     XIP Kernel Image ... OK
  OK

  Starting kernel ...

  Uncompressing Linux... done, booting the kernel.
  [    0.120087] cpuidle-am33xx cpuidle-am33xx.0: failed to register driver
  [    0.251953] _omap_mux_get_by_name: Could not find signal leds-gpio
  [    0.635798] omap2_set_init_voltage: unable to get clk dpll1_ck
  [    0.642040] omap2_set_init_voltage: unable to set vdd_mpu_iva
  [    0.648112] omap2_set_init_voltage: unable to get clk l3_ick
  [    0.654099] omap2_set_init_voltage: unable to set vdd_core
  udevd[56]: worker [79] did not accept message -1 (Connection refused), kill it
  ^M
  udevd[56]: worker [80] did not accept message -1 (Connection refused), kill it
  ^M
  udevd[56]: worker [81] did not accept message -1 (Connection refused), kill it
  ^M
  udevd[56]: worker [85] did not accept message -1 (Connection refused), kill it
  ^M
  udevd[56]: worker [86] did not accept message -1 (Connection refused), kill it
  ^M
  udevd[56]: worker [87] did not accept message -1 (Connection refused), kill it
  ^M

I don't know what that means, nor where to go from there.


-- 
Russell Senior, President
russell@personaltelco.net

Re: building meta-ti + poky HOWTO?

[Russell Senior]

>>>>> "Russell" == Russell Senior <russell@personaltelco.net> writes:

Russell> [...] I have tried taking the pre-baked Angstrom image from here:

Russell>
Russell> http://www.angstrom-distribution.org/demo/beaglebone/Angstrom-Cloud9-IDE-eglibc-ipk-v2012.02-core-beaglebone-2012.02.14.img.xz

Russell> (which works for me), and replacing the uImage on the vfat
Russell> partition by copying over the existing one with one I built.
Russell> That boots, but the rootfs isn't aligned (different
Russell> kernel/module versions?).

Russell> If I then try dropping in my rootfs, by reformatting the
Russell> ext4fs and untarring the rootfs tarball I built, I get 0.6
Russell> seconds into the boot and then the boot stalls with some
Russell> udevd messages, like so: [...]

Let me start by saying that I'm an almost a complete newbie with
OpenEmbedded, so a certain amount of slack cutting is in order.  

With that in mind, I discovered that uEnv.txt had "quiet", so I tried
booting without that and got some new information:

  U-Boot SPL 2011.09-00010-g81c8c79 (Feb 13 2012 - 14:48:03)
  Texas Instruments Revision detection unimplemented
  No AC power, disabling frequency switch
  OMAP SD/MMC: 0
  reading u-boot.img
  reading u-boot.img


  U-Boot 2011.09-00010-g81c8c79 (Feb 13 2012 - 14:48:03)

  I2C:   ready
  DRAM:  256 MiB
  No daughter card present
  NAND:  HW ECC Hamming Code selected
  nand_get_flash_type: unknown NAND device: Manufacturer ID: 0x10, Chip ID: 0x10
  No NAND device found!!!
  0 MiB
  MMC:   OMAP SD/MMC: 0
  *** Warning - readenv() failed, using default environment

  Net:   cpsw
  Hit any key to stop autoboot:  0 
  SD/MMC found on device 0
  reading uEnv.txt

  28 bytes read
  Loaded environment from uEnv.txt
  Importing environment from mmc ...
  reading uImage

  3141656 bytes read
  ## Booting kernel from Legacy Image at 80007fc0 ...
     Image Name:   Angstrom/3.2/beaglebone
     Image Type:   ARM Linux Kernel Image (uncompressed)
     Data Size:    3141592 Bytes = 3 MiB
     Load Address: 80008000
     Entry Point:  80008000
     Verifying Checksum ... OK
     XIP Kernel Image ... OK
  OK

  Starting kernel ...

  Uncompressing Linux... done, booting the kernel.
  [    0.000000] Initializing cgroup subsys cpuset
  [    0.000000] Initializing cgroup subsys cpu
  [    0.000000] Linux version 3.2.13 (russell@frieda) (gcc version 4.5.4 20120305 (prerelease) (GCC) ) #1 Tue Apr 3 11:52:23 PDT 2012
  [    0.000000] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=50c53c7d
  [    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
  [    0.000000] Machine: am335xevm
  [    0.000000] Memory policy: ECC disabled, Data cache writeback
  [    0.000000] AM335X ES1.0 (sgx neon )
  [    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 65024
  [    0.000000] Kernel command line: console=ttyO0,115200n8 run_hardware_tests root=/dev/mmcblk0p2 ro rootfstype=ext4 rootwait ip=none
  [    0.000000] PID hash table entries: 1024 (order: 0, 4096 bytes)
  [    0.000000] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
  [    0.000000] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
  [    0.000000] allocated 1048576 bytes of page_cgroup
  [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
  [    0.000000] Memory: 256MB = 256MB total
  [    0.000000] Memory: 253776k/253776k available, 8368k reserved, 0K highmem
  [    0.000000] Virtual kernel memory layout:
  [    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
  [    0.000000]     fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
  [    0.000000]     vmalloc : 0xd0800000 - 0xff000000   ( 744 MB)
  [    0.000000]     lowmem  : 0xc0000000 - 0xd0000000   ( 256 MB)
  [    0.000000]     modules : 0xbf800000 - 0xc0000000   (   8 MB)
  [    0.000000]       .text : 0xc0008000 - 0xc041f7e0   (4190 kB)
  [    0.000000]       .init : 0xc0420000 - 0xc0457000   ( 220 kB)
  [    0.000000]       .data : 0xc0458000 - 0xc04a8040   ( 321 kB)
  [    0.000000]        .bss : 0xc04a8064 - 0xc04ef2cc   ( 285 kB)
  [    0.000000] NR_IRQS:410 nr_irqs:410 410
  [    0.000000] IRQ: Found an INTC at 0xfa200000 (revision 5.0) with 128 interrupts
  [    0.000000] Total of 128 interrupts on 1 active controller
  [    0.000000] OMAP clockevent source: GPTIMER1 at 24000000 Hz
  [    0.000000] OMAP clocksource: GPTIMER2 at 24000000 Hz
  [    0.000000] sched_clock: 32 bits at 24MHz, resolution 41ns, wraps every 178956ms
  [    0.000000] Console: colour dummy device 80x30
  [    0.000215] Calibrating delay loop... 498.89 BogoMIPS (lpj=2494464)
  [    0.058654] pid_max: default: 32768 minimum: 301
  [    0.058816] Security Framework initialized
  [    0.058890] Mount-cache hash table entries: 512
  [    0.059312] Initializing cgroup subsys cpuacct
  [    0.059358] Initializing cgroup subsys memory
  [    0.059403] Initializing cgroup subsys devices
  [    0.059419] Initializing cgroup subsys freezer
  [    0.059433] Initializing cgroup subsys blkio
  [    0.059460] Initializing cgroup subsys perf_event
  [    0.059552] CPU: Testing write buffer coherency: ok
  [    0.060620] devtmpfs: initialized
  [    0.064817] print_constraints: dummy: 
  [    0.065084] NET: Registered protocol family 16
  [    0.065199] GPMC revision 6.0
  [    0.066482] OMAP GPIO hardware version 0.1
  [    0.067788] omap_mux_init: Add partition: #1: core, flags: 0
  [    0.069341]  omap_i2c.1: alias fck already exists
  [    0.069748] failed to create an alias: icss_uart_gclk --> pruss
  [    0.069781] failed to create an alias: gfx_fclk --> sgx_ck
  [    0.069800] hw-breakpoint: debug architecture 0x4 unsupported.
  [    0.069980]  omap2_mcspi.1: alias fck already exists
  [    0.070111]  omap2_mcspi.2: alias fck already exists
  [    0.081295] bio: create slab <bio-0> at 0
  [    0.082771] SCSI subsystem initialized
  [    0.083762] usbcore: registered new interface driver usbfs
  [    0.083910] usbcore: registered new interface driver hub
  [    0.084091] usbcore: registered new device driver usb
  [    0.084462] registerd cppi-dma Intr @ IRQ 17
  [    0.084482] Cppi41 Init Done Qmgr-base(d083a000) dma-base(d0838000)
  [    0.084494] Cppi41 Init Done
  [    0.084526] musb-ti81xx musb-ti81xx: musb0, board_mode=0x13, plat_mode=0x3
  [    0.084691] musb-ti81xx musb-ti81xx: musb1, board_mode=0x13, plat_mode=0x1
  [    0.098713] omap_i2c omap_i2c.1: bus 1 rev2.4.0 at 100 kHz
  [    0.099971] Advanced Linux Sound Architecture Driver Version 1.0.24.
  [    0.100626] Switching to clocksource gp timer
  [    0.113537] musb-hdrc: version 6.0, ?dma?, otg (peripheral+host)
  [    0.113731] musb-hdrc musb-hdrc.0: dma type: dma-cppi41
  [    0.114774] musb-hdrc musb-hdrc.0: USB OTG mode controller at d081e000 using DMA, IRQ 18
  [    0.115086] musb-hdrc musb-hdrc.1: dma type: dma-cppi41
  [    0.115738] musb-hdrc musb-hdrc.1: MUSB HDRC host driver
  [    0.115849] musb-hdrc musb-hdrc.1: new USB bus registered, assigned bus number 1
  [    0.115978] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
  [    0.115999] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
  [    0.116018] usb usb1: Product: MUSB HDRC host driver
  [    0.116034] usb usb1: Manufacturer: Linux 3.2.13 musb-hcd
  [    0.116049] usb usb1: SerialNumber: musb-hdrc.1
  [    0.116757] hub 1-0:1.0: USB hub found
  [    0.116788] hub 1-0:1.0: 1 port detected
  [    0.117316] musb-hdrc musb-hdrc.1: USB Host mode controller at d0832800 using DMA, IRQ 19
  [    0.117743] NET: Registered protocol family 2
  [    0.117956] IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
  [    0.118432] TCP established hash table entries: 8192 (order: 4, 65536 bytes)
  [    0.118657] TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
  [    0.118794] TCP: Hash tables configured (established 8192 bind 8192)
  [    0.118810] TCP reno registered
  [    0.118828] UDP hash table entries: 256 (order: 0, 4096 bytes)
  [    0.118860] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
  [    0.119173] NET: Registered protocol family 1
  [    0.119522] RPC: Registered named UNIX socket transport module.
  [    0.119540] RPC: Registered udp transport module.
  [    0.119553] RPC: Registered tcp transport module.
  [    0.119565] RPC: Registered tcp NFSv4.1 backchannel transport module.
  [    0.120208] cpuidle-am33xx cpuidle-am33xx.0: failed to register driver
  [    0.132896] VFS: Disk quotas dquot_6.5.2
  [    0.132973] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
  [    0.134240] msgmni has been set to 495
  [    0.135343] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
  [    0.135466] io scheduler noop registered
  [    0.135482] io scheduler deadline registered
  [    0.135554] io scheduler cfq registered (default)
  [    0.137182] ecap: probe of ecap.2 failed with error -2
  [    0.138231] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
  [    0.139614] omap_uart.0: ttyO0 at MMIO 0x44e09000 (irq = 72) is a OMAP UART0
  [    0.762926] console [ttyO0] enabled
  [    0.767173] omap_uart.1: ttyO1 at MMIO 0x48022000 (irq = 73) is a OMAP UART1
  [    0.775064] omap_uart.2: ttyO2 at MMIO 0x48024000 (irq = 74) is a OMAP UART2
  [    0.782911] omap_uart.3: ttyO3 at MMIO 0x481a6000 (irq = 44) is a OMAP UART3
  [    0.790736] omap_uart.4: ttyO4 at MMIO 0x481a8000 (irq = 45) is a OMAP UART4
  [    0.798550] omap_uart.5: ttyO5 at MMIO 0x481aa000 (irq = 46) is a OMAP UART5
  [    0.807718] brd: module loaded
  [    0.815469] loop: module loaded
  [    0.818866] at24 1-0051: 32768 byte 24c256 EEPROM, writable, 64 bytes/write
  [    0.880679] No daughter card found
  [    0.884327] at24 1-0050: 32768 byte 24c256 EEPROM, writable, 64 bytes/write
  [    0.899624] Board name: A335BONE
  [    0.903045] Board version: 00A4
  [    0.906353] The board is a AM335x Beaglebone.
  [    0.911630] tps65217 1-0024: TPS65217 ID 0x7 version 1.0
  [    0.919124] print_constraints: DCDC1: 900 <--> 1800 mV at 1800 mV 
  [    0.927612] print_constraints: DCDC2: 900 <--> 3300 mV at 1275 mV 
  [    0.936066] print_constraints: DCDC3: 900 <--> 1500 mV at 1100 mV 
  [    0.944510] print_constraints: LDO1: 1000 <--> 3300 mV at 1800 mV 
  [    0.952951] print_constraints: LDO2: 900 <--> 3300 mV at 3300 mV 
  [    0.961293] print_constraints: LDO3: 1800 <--> 3300 mV at 3300 mV 
  [    0.969745] print_constraints: LDO4: 1800 <--> 3300 mV at 3300 mV 
  [    0.976704]  omap_i2c.3: alias fck already exists
  [    1.000738] omap_i2c omap_i2c.3: bus 3 rev2.4.0 at 100 kHz
  [    1.007353]  omap_hsmmc.0: alias fck already exists
  [    1.012909] _omap_mux_get_by_name: Could not find signal leds-gpio
  [    1.019709] w1-gpio connected to P8_6
  [    1.023964] at24 3-0054: 32768 byte 24c256 EEPROM, writable, 64 bytes/write
  [    1.110682] BeagleBone cape EEPROM: could not read eeprom at address 0x54
  [    1.117901] at24 3-0055: 32768 byte 24c256 EEPROM, writable, 64 bytes/write
  [    1.200679] BeagleBone cape EEPROM: could not read eeprom at address 0x55
  [    1.207881] at24 3-0056: 32768 byte 24c256 EEPROM, writable, 64 bytes/write
  [    1.290677] BeagleBone cape EEPROM: could not read eeprom at address 0x56
  [    1.297876] at24 3-0057: 32768 byte 24c256 EEPROM, writable, 64 bytes/write
  [    1.380678] BeagleBone cape EEPROM: could not read eeprom at address 0x57
  [    1.387834] BeagleBone cape: exporting ADC pins to sysfs
  [    1.394407] SCSI Media Changer driver v0.25 
  [    1.399311] CAN device driver interface
  [    1.403397] CAN bus driver for Bosch D_CAN controller 1.0
  [    1.450706] davinci_mdio davinci_mdio.0: davinci mdio revision 1.6
  [    1.457223] davinci_mdio davinci_mdio.0: detected phy mask fffffffe
  [    1.464837] davinci_mdio.0: probed
  [    1.468433] davinci_mdio davinci_mdio.0: phy[0]: device 0:00, driver SMSC LAN8710/LAN8720
  [    1.477277] usbcore: registered new interface driver catc
  [    1.482991] catc: v2.8:CATC EL1210A NetMate USB Ethernet driver
  [    1.489323] usbcore: registered new interface driver kaweth
  [    1.495221] pegasus: v0.6.14 (2006/09/27), Pegasus/Pegasus II USB Ethernet driver
  [    1.503205] usbcore: registered new interface driver pegasus
  [    1.509172] rtl8150: v0.6.2 (2004/08/27):rtl8150 based usb-ethernet driver
  [    1.516504] usbcore: registered new interface driver rtl8150
  [    1.522589] usbcore: registered new interface driver asix
  [    1.528349] usbcore: registered new interface driver cdc_ether
  [    1.534584] usbcore: registered new interface driver dm9601
  [    1.540524] usbcore: registered new interface driver cdc_subset
  [    1.546848] usbcore: registered new interface driver zaurus
  [    1.552783] cdc_ncm: 04-Aug-2011
  [    1.556253] usbcore: registered new interface driver cdc_ncm
  [    1.562360] usbcore: registered new interface driver cdc_acm
  [    1.568325] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
  [    1.576886] usbcore: registered new interface driver usblp
  [    1.582759] usbcore: registered new interface driver cdc_wdm
  [    1.588790] usbcore: registered new interface driver uas
  [    1.594405] Initializing USB Mass Storage driver...
  [    1.599682] usbcore: registered new interface driver usb-storage
  [    1.606032] USB Mass Storage support registered.
  [    1.611040] usbcore: registered new interface driver libusual
  [    1.617585] mousedev: PS/2 mouse device common for all mice
  [    1.624087] dev addr = c0478af0
  [    1.627402] pdev addr = c0478ae8
  [    1.631553] omap_rtc omap_rtc: rtc core: registered omap_rtc as rtc0
  [    1.638277] omap_rtc: already running
  [    1.642321] i2c /dev entries driver
  [    1.646468] Linux media interface: v0.10
  [    1.650811] lirc_dev: IR Remote Control driver registered, major 249 
  [    1.657600] IR NEC protocol handler initialized
  [    1.662392] IR RC5(x) protocol handler initialized
  [    1.667436] IR RC6 protocol handler initialized
  [    1.672224] IR JVC protocol handler initialized
  [    1.676999] IR Sony protocol handler initialized
  [    1.681875] IR RC5 (streamzap) protocol handler initialized
  [    1.687749] IR MCE Keyboard/mouse protocol handler initialized
  [    1.693911] IR LIRC bridge handler initialized
  [    1.698594] Linux video capture interface: v2.00
  [    1.703633] usbcore: registered new interface driver uvcvideo
  [    1.709691] USB Video Class driver (1.1.1)
  [    1.714103] Driver for 1-wire Dallas network protocol.
  [    1.720923] OMAP Watchdog Timer Rev 0x01: initial timeout 60 sec
  [    1.731561] usbcore: registered new interface driver usbhid
  [    1.737436] usbhid: USB HID core driver
  [    1.742548] usbcore: registered new interface driver snd-usb-audio
  [    1.749622] ALSA device list:
  [    1.752800]   No soundcards found.
  [    1.756782] TCP cubic registered
  [    1.760186] Initializing XFRM netlink socket
  [    1.764761] NET: Registered protocol family 17
  [    1.769501] NET: Registered protocol family 15
  [    1.774206] can: controller area network core (rev 20090105 abi 8)
  [    1.780843] NET: Registered protocol family 29
  [    1.785533] can: raw protocol (rev 20090105)
  [    1.790073] Registering the dns_resolver key type
  [    1.795124] VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3
  [    1.803237] ThumbEE CPU extension supported.
  [    1.807807] mux: Failed to setup hwmod io irq -22
  [    1.813641] omap2_set_init_voltage: unable to get clk dpll1_ck
  [    1.819794] omap2_set_init_voltage: unable to set vdd_mpu_iva
  [    1.825896] omap2_set_init_voltage: unable to get clk l3_ick
  [    1.831878] omap2_set_init_voltage: unable to set vdd_core
  [    1.837661] Power Management for AM33XX family
  [    1.847044] registered taskstats version 1
  [    1.851753] Detected MACID=d4:94:a1:79:81:c7
  [    1.857437] omap_rtc omap_rtc: setting system clock to 2000-01-01 00:00:51 UTC (946684851)
  [    1.867025] Waiting for root device /dev/mmcblk0p2...
  [    1.912487] mmc0: host does not support reading read-only switch. assuming write-enable.
  [    1.923354] mmc0: new high speed SDHC card at address 0007
  [    1.929746] mmcblk0: mmc0:0007 SD8GB 7.43 GiB 
  [    1.938278]  mmcblk0: p1 p2
  [    2.012939] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
  [    2.021593] VFS: Mounted root (ext4 filesystem) readonly on device 179:2.
  [    2.031519] devtmpfs: mounted
  [    2.035090] Freeing init memory: 220K

  Welcome to The Angstrom Distribution!

  [    2.529008] NET: Registered protocol family 10
  : Registered protocol family 10
  Started Security File System                                           [  OK  ]
  Starting POSIX Message Queue File System...                                    
  Started Huge Pages File System                                         [  OK  ]
  Starting Apply Kernel Variables...                                             
  Started Set Up Additional Binary Formats                               [  OK  ]
  Starting Debug File System...                                                  
  Starting Load Kernel Modules...                                                
  Starting Runtime Directory...                                                  
  Starting Lock Directory...                                                     
  Starting Remount API VFS...                                                    
  Starting File System Check on Root Device...                                   
  [    3.216235] Bluetooth: Core ver 2.16
  [    3.220114] NET: Registered protocol family 31
  [    3.224849] Bluetooth: HCI device and connection manager initialized
  [    3.231570] Bluetooth: HCI socket layer initialized
  [    3.236711] Bluetooth: L2CAP socket layer initialized
  [    3.242074] Bluetooth: SCO socket layer initialized
  [    3.260742] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
  Starting Media Directory...                                                    
  [    3.354048] NET: Registered protocol family 23
  Starting udev Coldplug all Devices...                                          
  Starting udev Kernel Device Manager...                                         
  Starting Journal Service...                                                    
  Started Journal Service                                                [  OK  ]
  Started POSIX Message Queue File System                                [  OK  ]
  Started Apply Kernel Variables                                         [  OK  ]
  Started Debug File System                                              [  OK  ]
  Started Runtime Directory                                              [  OK  ]
  Started Lock Directory                                                 [  OK  ]
  Started Media Directory                                                [  OK  ]
  [    3.473893] IrCOMM protocol (Dag Brattli)
  Started Remount API VFS                                                [  OK  ]
  [    3.593606] Bluetooth: RFCOMM TTY layer initialized
  [    3.599707] Bluetooth: RFCOMM socket layer initialized
  [    3.606514] Bluetooth: RFCOMM ver 1.11
  [    3.641075] udevd[67]: starting version 182
  Started udev Kernel Device Manager                                     [  OK  ]
  Started Load Kernel Modules                                            [  OK  ]
  Started FUSE Control File System                                       [  OK  ]
  Started Configuration File System                                      [  OK  ]
  Starting Journal Service...                                                    
  Started Journal Service                                                [  OK  ]
  Starting Journal Service...                                                    
  Started Journal Service                                                [  OK  ]
  Starting Journal Service...                                                    
  Started Journal Service                                                [  OK  ]
  Starting Journal Service...                                                    
  Started Journal Service                                                [  OK  ]
  Starting Journal Service...                                                   
  Started Journal Service                                                [  OK  ]
  Starting Journal Service...                                                    
  Failed to start Journal Service                                        [FAILED]
  See 'systemctl status systemd-journald.service' for details.                   
  Started udev Coldplug all Devices                                      [  OK  ]
  Started File System Check on Root Device                               [  OK  ]
  Starting Remount Root FS...                                                    
  Failed to start Remount Root FS                                        [FAILED]
  See 'systemctl status remount-rootfs.service' for details.                     
  Starting /tmp...                                                               
  Starting Machine ID first boot configure...                                    
  Starting Run pending postinsts...                                              
  Failed to start /tmp                                                   [FAILED]
  See 'systemctl status tmp.mount' for details.                                  
  Dependency failed. Aborted start of Serial Getty on ttyO0              [ABORT]
  Dependency failed. Aborted start of Getty on tty1                      [ABORT]
  udevd[67]: timeout, giving up waiting for workers to finish

This looks like the same problem as here: 

  http://lists.linuxtogo.org/pipermail/angstrom-distro-devel/2012-March/005762.html

That was a month ago.  Why hasn't this been fixed?  I'm running a stock/very-recent checkout.


-- 
Russell Senior, President
russell@personaltelco.net

Re: building meta-ti + poky HOWTO?

[Gary Thomas]

[-- Attachment #1: Type: text/plain, Size: 2249 bytes --]

On 2012-04-05 12:36, Brian Hutchinson wrote:
> I may be out of the loop but if you follow the yocto way of doing
> things .... poky will produce a BeagleBoard image without having to
> use meta-ti and I think you can use that on beaglebone.  Some one
> correct me if I'm sending Russell in the weeds.
>
> I've been able to build yocto images for BeagleBoard but haven't tried
> them on the bone yet.
>
> Last I checked meta-ti with poky still had some issues.

Yes, there are some issues, but they can be worked around.  I have successfully
built core-image-minimal for both beagleboard and beaglebone with this configuration:

OE Build Configuration:
BB_VERSION        = "1.15.1"
TARGET_ARCH       = "arm"
TARGET_OS         = "linux-gnueabi"
MACHINE           = "beaglebone"
DISTRO            = "poky"
DISTRO_VERSION    = "1.1+snapshot-20120406"
TUNE_FEATURES     = "armv7a vfp neon cortexa8"
TARGET_FPU        = "vfp-neon"
meta
meta-yocto        = "(nobranch):723c91297d833f989b762c661d05eef6a5e2fe5c"
meta-ti           = "master:246cb75a970e9aab0a3974a55e72c6d90f1df151"

Simply add the meta-ti to your conf/bblayers.conf

Workarounds:
* There is still one recipe in meta-ti that causes a parse error
     ERROR: ParseError at /home/local/poky-multi/meta-ti/recipes-misc/payload/bonescript.bb:5: Could not inherit file classes/systemd.bbclass
   To work around this, add this to your conf/local.conf
     BBMASK ?= ".*/meta-ti/recipes-misc/payload/bonescript*"
* The beaglebone kernel can't be built with its default configuration using the
   GCC-4.6.x/BINUTILS-2.22.  It will build with the attached patch which disables
   THUMB2_KERNEL mode.  Simply apply it to your local copy of meta-ti
* If you want to build the TI kernel for the beagleboard, add this to conf/local.conf
     PREFERRED_PROVIDER_virtual/kernel ?= "linux-omap-psp"

That said, I've only tested the bare minimum builds.  Depending on what you need to
accomplish, this may or may not be the way to go.

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

[-- Attachment #2: beaglebone-no-thumb2-kernel-mode.patch --]
[-- Type: text/x-patch, Size: 674 bytes --]

diff --git a/recipes-kernel/linux/linux-ti33x-psp-3.2/beaglebone/defconfig b/recipes-kernel/linux/linux-ti33x-psp-3.2/beaglebone/defconfig
index 782f52d..179c568 100644
--- a/recipes-kernel/linux/linux-ti33x-psp-3.2/beaglebone/defconfig
+++ b/recipes-kernel/linux/linux-ti33x-psp-3.2/beaglebone/defconfig
@@ -420,8 +420,8 @@ CONFIG_PREEMPT_NONE=y
 # CONFIG_PREEMPT_VOLUNTARY is not set
 # CONFIG_PREEMPT is not set
 CONFIG_HZ=100
-CONFIG_THUMB2_KERNEL=y
-CONFIG_THUMB2_AVOID_R_ARM_THM_JUMP11=y
+# CONFIG_THUMB2_KERNEL is not set
+# CONFIG_THUMB2_AVOID_R_ARM_THM_JUMP11 is not set
 CONFIG_ARM_ASM_UNIFIED=y
 CONFIG_AEABI=y
 CONFIG_ARCH_HAS_HOLES_MEMORYMODEL=y

Re: [Angstrom-devel] building meta-ti + poky HOWTO?

[Khem Raj]

On Thu, Apr 5, 2012 at 6:40 PM, Russell Senior
<russell@personaltelco.net> wrote:
>
> This looks like the same problem as here:
>
>  http://lists.linuxtogo.org/pipermail/angstrom-distro-devel/2012-March/005762.html
>
> That was a month ago.  Why hasn't this been fixed?  I'm running a stock/very-recent checkout.

Do you know the reason for the failure? if anybody was bothered enough
then someone would have debugged it and sent a patch or atleast
described the problem in more detail.

Re: building meta-ti + poky HOWTO?

[Jack Mitchell]

On 05/04/2012 21:43, Russell Senior wrote:
>>>>>> "Denys" == Denys Dmytriyenko<denis@denix.org>  writes:
> Russell>  I have been unable to get a booting image out of Angstrom in
> Russell>  about three weeks of trying and several unanswered queries to
> Russell>  the mailing list and elsewhere.  In my continuing effort to
> Russell>  get a build system that produces an image that boots on my
> Russell>  beaglebone, I'd like to try building meta-ti with poky, just
> Russell>  to see if that fails for me too.
>
> Denys>  As far as I remember, you are having problems with rootfs
> Denys>  images that generate an entire SD card disk image with multiple
> Denys>  partitions, e.g. Cloud9 image.  There are known issues with the
> Denys>  tools used to do that, like sometimes fdisk not making the
> Denys>  correct MBR and partition table that BootROM can boot from. So
> Denys>  far it seems to depend on the host distro and their tools. This
> Denys>  area still needs further investigation and probably the use of
> Denys>  different tools...
>
> I am building on a Debian/unstable box with a core i7 cpu and 24 gig of RAM.
>
> Denys>  But you should not be stuck on this - why don't you use the
> Denys>  individual pieces, like kernel image, rootfs and load them on
> Denys>  SD card yourself, manually? Try working around the issue...
>
> I have tried taking the pre-baked Angstrom image from here:
>
>    http://www.angstrom-distribution.org/demo/beaglebone/Angstrom-Cloud9-IDE-eglibc-ipk-v2012.02-core-beaglebone-2012.02.14.img.xz
>
> (which works for me), and replacing the uImage on the vfat partition
> by copying over the existing one with one I built.  That boots, but the
> rootfs isn't aligned (different kernel/module versions?).
>
> If I then try dropping in my rootfs, by reformatting the ext4fs and
> untarring the rootfs tarball I built, I get 0.6 seconds into the boot
> and then the boot stalls with some udevd messages, like so:
>
>    U-Boot SPL 2011.09-00010-g81c8c79 (Feb 13 2012 - 14:48:03)
>    Texas Instruments Revision detection unimplemented
>    No AC power, disabling frequency switch
>    OMAP SD/MMC: 0
>    reading u-boot.img
>    reading u-boot.img
>
>
>    U-Boot 2011.09-00010-g81c8c79 (Feb 13 2012 - 14:48:03)
>
>    I2C:   ready
>    DRAM:  256 MiB
>    No daughter card present
>    NAND:  HW ECC Hamming Code selected
>    nand_get_flash_type: unknown NAND device: Manufacturer ID: 0x10, Chip ID: 0x10
>    No NAND device found!!!
>    0 MiB
>    MMC:   OMAP SD/MMC: 0
>    *** Warning - readenv() failed, using default environment
>
>    Net:   cpsw
>    Hit any key to stop autoboot:  0
>    SD/MMC found on device 0
>    reading uEnv.txt
>
>    33 bytes read
>    Loaded environment from uEnv.txt
>    Importing environment from mmc ...
>    reading uImage
>
>    3140320 bytes read
>    ## Booting kernel from Legacy Image at 80007fc0 ...
>       Image Name:   Angstrom/3.2/beaglebone
>       Image Type:   ARM Linux Kernel Image (uncompressed)
>       Data Size:    3140256 Bytes = 3 MiB
>       Load Address: 80008000
>       Entry Point:  80008000
>       Verifying Checksum ... OK
>       XIP Kernel Image ... OK
>    OK
>
>    Starting kernel ...
>
>    Uncompressing Linux... done, booting the kernel.
>    [    0.120087] cpuidle-am33xx cpuidle-am33xx.0: failed to register driver
>    [    0.251953] _omap_mux_get_by_name: Could not find signal leds-gpio
>    [    0.635798] omap2_set_init_voltage: unable to get clk dpll1_ck
>    [    0.642040] omap2_set_init_voltage: unable to set vdd_mpu_iva
>    [    0.648112] omap2_set_init_voltage: unable to get clk l3_ick
>    [    0.654099] omap2_set_init_voltage: unable to set vdd_core
>    udevd[56]: worker [79] did not accept message -1 (Connection refused), kill it
>    ^M
>    udevd[56]: worker [80] did not accept message -1 (Connection refused), kill it
>    ^M
>    udevd[56]: worker [81] did not accept message -1 (Connection refused), kill it
>    ^M
>    udevd[56]: worker [85] did not accept message -1 (Connection refused), kill it
>    ^M
>    udevd[56]: worker [86] did not accept message -1 (Connection refused), kill it
>    ^M
>    udevd[56]: worker [87] did not accept message -1 (Connection refused), kill it
>    ^M
>
> I don't know what that means, nor where to go from there.
>
>
Russel,

I took the time to post a brief guide[1] on how to build Angstrom for 
the BeagleBone, it takes you through the steps and also uses the 
separate images built rather than the big 'sd card partition' image it 
has been noted you are having problems with.

I don't know if it will help in your situation but it's something else 
you can inspect.

Regards,
Jack.

[1] http://communistcode.co.uk/blog/blogPost.php?blogPostID=2

Re: building meta-ti + poky HOWTO?

[Russell Senior]

>>>>> "Jack" == Jack Mitchell <ml@communistcode.co.uk> writes:

Jack> I took the time to post a brief guide[1] on how to build
Jack> Angstrom for the BeagleBone, it takes you through the steps and
Jack> also uses the separate images built rather than the big 'sd card
Jack> partition' image it has been noted you are having problems with.

Jack> I don't know if it will help in your situation but it's
Jack> something else you can inspect.

Jack> [1] http://communistcode.co.uk/blog/blogPost.php?blogPostID=2

Thanks.  Doesn't help, unfortunately.  Still get the same FAILs.  I
did learn that the modules aren't in the systemd-image rootfs, though.
That was a surprise.  Unfortunately, adding them doesn't help.

  [...]
  Starting Journal Service...
  Failed to start Journal Service                                        [FAILED]
  See 'systemctl status systemd-journald.service' for details.
  Started udev Coldplug all Devices                                      [  OK  ]
  Started File System Check on Root Device                               [  OK  ]
  Starting Remount Root FS...
  Failed to start Remount Root FS                                        [FAILED]
  See 'systemctl status remount-rootfs.service' for details.
  Starting /tmp...
  Starting Machine ID first boot configure...
  Starting Run pending postinsts...
  Failed to start /tmp                                                   [FAILED]
  See 'systemctl status tmp.mount' for details.
  Dependency failed. Aborted start of Serial Getty on ttyO0              [ABORT]
  Dependency failed. Aborted start of Getty on tty1                      [ABORT]
  udevd[67]: timeout, giving up waiting for workers to finish
  [...]


-- 
Russell Senior, President
russell@personaltelco.net

Re: building meta-ti + poky HOWTO?

[Denys Dmytriyenko]

On Thu, Apr 05, 2012 at 06:40:15PM -0700, Russell Senior wrote:
> >>>>> "Russell" == Russell Senior <russell@personaltelco.net> writes:
> 
> Russell> [...] I have tried taking the pre-baked Angstrom image from here:
> 
> Russell>
> Russell> http://www.angstrom-distribution.org/demo/beaglebone/Angstrom-Cloud9-IDE-eglibc-ipk-v2012.02-core-beaglebone-2012.02.14.img.xz
> 
> Russell> (which works for me), and replacing the uImage on the vfat
> Russell> partition by copying over the existing one with one I built.
> Russell> That boots, but the rootfs isn't aligned (different
> Russell> kernel/module versions?).
> 
> With that in mind, I discovered that uEnv.txt had "quiet", so I tried
> booting without that and got some new information:
> 
>   Failed to start Journal Service                                        [FAILED]
>   See 'systemctl status systemd-journald.service' for details.                   
>   Started udev Coldplug all Devices                                      [  OK  ]
>   Started File System Check on Root Device                               [  OK  ]
>   Starting Remount Root FS...                                                    
>   Failed to start Remount Root FS                                        [FAILED]
>   See 'systemctl status remount-rootfs.service' for details.                     
>   Starting /tmp...                                                               
>   Starting Machine ID first boot configure...                                    
>   Starting Run pending postinsts...                                              
>   Failed to start /tmp                                                   [FAILED]
>   See 'systemctl status tmp.mount' for details.                                  
>   Dependency failed. Aborted start of Serial Getty on ttyO0              [ABORT]
>   Dependency failed. Aborted start of Getty on tty1                      [ABORT]
>   udevd[67]: timeout, giving up waiting for workers to finish
> 
> This looks like the same problem as here: 
> 
>   http://lists.linuxtogo.org/pipermail/angstrom-distro-devel/2012-March/005762.html
> 
> That was a month ago.  Why hasn't this been fixed?  I'm running a stock/very-recent checkout.

Russell,

It appears your kernel configuration may not have all the required options 
enabled to work properly with latest udev and systemd, according to this post:
http://lists.linuxtogo.org/pipermail/angstrom-distro-devel/2012-March/005793.html

As it was mentioned in the reply, enabling those options fixes the [FAILED] 
issues above with the Journal Service:
http://lists.linuxtogo.org/pipermail/angstrom-distro-devel/2012-March/005798.html

Also, please follow the rest of the thread for additional info:
http://thread.gmane.org/gmane.linux.distributions.angstrom.devel/6142

-- 
Denys

[PATCH] apply recommended kernel config for beaglebone

[Russell Senior]

Apply recommended kernel config per:

  http://dominion.thruhere.net/koen/cms/recommended-kernel-config-options-for-a-modern-angstrom-system


Signed-off-by: Russell Senior <russell@personaltelco.net>
---
 .../linux/linux-ti33x-psp-3.2/beaglebone/defconfig |    7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/recipes-kernel/linux/linux-ti33x-psp-3.2/beaglebone/defconfig b/recipes-kernel/linux/linux-ti33x-psp-3.2/beaglebone/defconfig
index 782f52d..6cb725b 100644
--- a/recipes-kernel/linux/linux-ti33x-psp-3.2/beaglebone/defconfig
+++ b/recipes-kernel/linux/linux-ti33x-psp-3.2/beaglebone/defconfig
@@ -82,7 +82,8 @@ CONFIG_IKCONFIG=y
 CONFIG_IKCONFIG_PROC=y
 CONFIG_LOG_BUF_SHIFT=17
 CONFIG_CGROUPS=y
-# CONFIG_CGROUP_DEBUG is not set
+CONFIG_CGROUP_DEBUG=y
+CONFIG_CGROUP_NS=y
 CONFIG_CGROUP_FREEZER=y
 CONFIG_CGROUP_DEVICE=y
 CONFIG_CPUSETS=y
@@ -3150,8 +3151,8 @@ CONFIG_QUOTA_TREE=m
 CONFIG_QFMT_V2=m
 CONFIG_QUOTACTL=y
 CONFIG_AUTOFS4_FS=y
-CONFIG_FUSE_FS=m
-CONFIG_CUSE=m
+CONFIG_FUSE_FS=y
+CONFIG_CUSE=y
 CONFIG_GENERIC_ACL=y

 #
--
1.7.9.5



-- 
Russell Senior, President
russell@personaltelco.net

Re: [PATCH] apply recommended kernel config for beaglebone

[Koen Kooi]

Op 9 apr. 2012, om 10:42 heeft Russell Senior het volgende geschreven:

> 
> Apply recommended kernel config per:
> 
>  http://dominion.thruhere.net/koen/cms/recommended-kernel-config-options-for-a-modern-angstrom-system
> 
> 
> Signed-off-by: Russell Senior <russell@personaltelco.net>
> ---
> .../linux/linux-ti33x-psp-3.2/beaglebone/defconfig |    7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
> 
> diff --git a/recipes-kernel/linux/linux-ti33x-psp-3.2/beaglebone/defconfig b/recipes-kernel/linux/linux-ti33x-psp-3.2/beaglebone/defconfig
> index 782f52d..6cb725b 100644
> --- a/recipes-kernel/linux/linux-ti33x-psp-3.2/beaglebone/defconfig
> +++ b/recipes-kernel/linux/linux-ti33x-psp-3.2/beaglebone/defconfig
> @@ -82,7 +82,8 @@ CONFIG_IKCONFIG=y
> CONFIG_IKCONFIG_PROC=y
> CONFIG_LOG_BUF_SHIFT=17
> CONFIG_CGROUPS=y
> -# CONFIG_CGROUP_DEBUG is not set
> +CONFIG_CGROUP_DEBUG=y
> +CONFIG_CGROUP_NS=y
> CONFIG_CGROUP_FREEZER=y
> CONFIG_CGROUP_DEVICE=y
> CONFIG_CPUSETS=y
> @@ -3150,8 +3151,8 @@ CONFIG_QUOTA_TREE=m
> CONFIG_QFMT_V2=m
> CONFIG_QUOTACTL=y
> CONFIG_AUTOFS4_FS=y
> -CONFIG_FUSE_FS=m
> -CONFIG_CUSE=m
> +CONFIG_FUSE_FS=y
> +CONFIG_CUSE=y
> CONFIG_GENERIC_ACL=y

Apart from the missing PR bump, the changes have no effect on systemd, c/fuse can be a module and cgroup debugging isn't needed.

Re: [PATCH] apply recommended kernel config for beaglebone

[Russell Senior]

>>>>> "Koen" == Koen Kooi <koen@dominion.thruhere.net> writes:

Koen> Apart from the missing PR bump, the changes have no effect on
Koen> systemd, c/fuse can be a module and cgroup debugging isn't
Koen> needed.

Sorry for my sloppy patching.  

With that patch applied, I managed to actually boot my own
kernel/rootfs for the first time in a month of trying.  The inital
boot looked the same, with the [ FAIL ]'s and udevd messages, but when
I went to capture the console in a screen.log and reset (using the
reset button near the LEDs), amazingly on the second boot it came up
cleanly to a login prompt.  I know that in all previous cases I had
reset like that before, the second (and subsequent) boots had remained
failing.


-- 
Russell Senior, President
russell@personaltelco.net

Re: building meta-ti + poky HOWTO?

[Marco Monguzzi]

[-- Attachment #1: Type: text/plain, Size: 1131 bytes --]

Hi Gary,

this may work for me too.

Is there a way to stick with the TI recommended toolchain?
(gcc-4.5 + Linaro patches and binutils-2.20.1)

Adding:

GCCVERSION = "4.5%"
BINUVERSION = "2.20.1"

to my conf/local.conf appears being ignored (tried with a 1.2_M4.rc3
snapshot).

Thanks in advance for your time.

Regards.


> Workarounds:
> * There is still one recipe in meta-ti that causes a parse error
>    ERROR: ParseError at /home/local/poky-multi/meta-**
> ti/recipes-misc/payload/bonesc**ript.bb:5 <http://bonescript.bb:5>: Could
> not inherit file classes/systemd.bbclass
>  To work around this, add this to your conf/local.conf
>    BBMASK ?= ".*/meta-ti/recipes-misc/**payload/bonescript*"
> * The beaglebone kernel can't be built with its default configuration
> using the
>  GCC-4.6.x/BINUTILS-2.22.  It will build with the attached patch which
> disables
>  THUMB2_KERNEL mode.  Simply apply it to your local copy of meta-ti
> * If you want to build the TI kernel for the beagleboard, add this to
> conf/local.conf
>    PREFERRED_PROVIDER_virtual/**kernel ?= "linux-omap-psp"
>
>

[-- Attachment #2: Type: text/html, Size: 1596 bytes --]

Re: building meta-ti + poky HOWTO?

[Denys Dmytriyenko]

On Thu, Apr 12, 2012 at 04:42:19PM +0200, Marco Monguzzi wrote:
> Hi Gary,
> 
> this may work for me too.
> 
> Is there a way to stick with the TI recommended toolchain?
> (gcc-4.5 + Linaro patches and binutils-2.20.1)
> 
> Adding:
> 
> GCCVERSION = "4.5%"
> BINUVERSION = "2.20.1"
> 
> to my conf/local.conf appears being ignored (tried with a 1.2_M4.rc3
> snapshot).

You add those 2 lines to your local.conf when you use a distro-less setup 
(i.e. openembedded-core+meta-ti+toolchain-layer). Poky has own distribution 
configuration and that overwrites those variables. You can try forcing it:

GCCVERSION_forcevariable = "4.5%"
BINUVERSION_forcevariable = "2.20.1"

And don't forget to add toolchain-layer to your bblayers.conf

-- 
Denys


> > Workarounds:
> > * There is still one recipe in meta-ti that causes a parse error
> >    ERROR: ParseError at /home/local/poky-multi/meta-**
> > ti/recipes-misc/payload/bonesc**ript.bb:5 <http://bonescript.bb:5>: Could
> > not inherit file classes/systemd.bbclass
> >  To work around this, add this to your conf/local.conf
> >    BBMASK ?= ".*/meta-ti/recipes-misc/**payload/bonescript*"
> > * The beaglebone kernel can't be built with its default configuration
> > using the
> >  GCC-4.6.x/BINUTILS-2.22.  It will build with the attached patch which
> > disables
> >  THUMB2_KERNEL mode.  Simply apply it to your local copy of meta-ti
> > * If you want to build the TI kernel for the beagleboard, add this to
> > conf/local.conf
> >    PREFERRED_PROVIDER_virtual/**kernel ?= "linux-omap-psp"
> >
> >

> _______________________________________________
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti