This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Linux/AM3715: Bitbake issues

Guru 20755 points

Part Number: AM3715
Other Parts Discussed in Thread: ADS7846

Tool/software: Linux

Hello,

Trying to build arago with bitbake, I follow the exact instructions as described in:

arago-project.org/.../Setting_Up_Build_Environment

./oe-layertool-setup.sh -f configs/arago-krogoth-config.txt

################################################################################
A setenv file has been created for you in the conf directory. Please verify
The contents of this file. Once you have verified the contents please source
this file to configure your environment for building:

. conf/setenv

You can then start building using the bitbake command. You will likely want
to set the MACHINE option if you have not done so in your local.conf file.

For example:
MACHINE=xxxxx bitbake <target>

Common targets are:
core-image-minimal
core-image-sato
meta-toolchain
meta-toolchain-sdk
adt-installer
meta-ide-support
user@user-VirtualBox:/media/yocto4/som37/OE/tisdk$ cd build/
user@user-VirtualBox:/media/yocto4/som37/OE/tisdk/build$ . conf/setenv
user@user-VirtualBox:/media/yocto4/som37/OE/tisdk/build$ MACHINE=am37x-evm bitbake arago-base-tisdk-image
NOTE: Your conf/bblayers.conf has been automatically updated.
Parsing recipes: 100% |#########################################| Time: 00:01:16
Parsing of 2344 .bb files complete (0 cached, 2344 parsed). 2940 targets, 510 skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION = "1.30.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "Ubuntu-14.04"
TARGET_SYS = "arm-linux-gnueabi"
MACHINE = "am37x-evm"
DISTRO = "arago"
DISTRO_VERSION = "2016.12"
TUNE_FEATURES = "arm armv7a vfp thumb neon callconvention-hard"
TARGET_FPU = "hard"
meta-processor-sdk = "HEAD:70283e8e915126b57e30cc7fcf5286a9435c3829"
meta-arago-distro
meta-arago-extras = "HEAD:c0e32cc7615f7483ae3a674221dd633205b28ee3"
meta-qt5 = "HEAD:2b1871f0d139dc3caaa779a32a1931409c245a36"
meta-networking
meta-ruby
meta-python
meta-oe
meta-gnome = "HEAD:55c8a76da5dc099a7bc3838495c672140cedb78e"
meta-ti = "HEAD:ed06c3bb58493a40b6fe584251a94f067fc9bdf7"
meta-linaro-toolchain
meta-optee = "HEAD:2f51d38048599d9878f149d6d15539fb97603f8f"
meta = "HEAD:ff8c8859434e56894accc5a63980c1b8904eb935"

NOTE: Preparing RunQueue
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
ERROR: external-linaro-toolchain-2016.11-r0.arago33 do_populate_sysroot: The recipe external-linaro-toolchain is trying to install files into a shared area when those files already exist. Those files and their manifest location are:
/media/yocto4/som37/OE/tisdk/build/arago-tmp-external-linaro-toolchain/sysroots/am37x-evm/usr/include/scsi/cxlflash_ioctl.h

I tried to delete build folder and use different config , for dylan, krogoth, sdk

But I keep getting this error.

I see other thread which mentioned this failure, which is not resolved in these e2e posts.

Is there any solution for this ?

Is it because the toolchain is already installed ?

Or is it that the git ( git://arago-project.org/git/projects/oe-layersetup.gitis too old ?

 

export PATH=$HOME/gcc-linaro-6.2.1-2016.11-x86_64_arm-linux-gnueabihf/bin:$PATH
$ MACHINE=am335x-evm bitbake tisdk-rootfs-image

Regards,

Ran

  • I've renamed the problematic file
    /media/yocto4/som37/OE/tisdk/build/arago-tmp-external-linaro-toolchain/sysroots/am37x-evm/usr/include/scsi/cxlflash_ioctl.h.old
    and now it continues,
    I hope it shall finish without more errors now. It will tak ~2 hours (I've cleaned it after seeing the error for the 1st time :( )
    Thanks
  • Hello Ran,

    The Processor SDK building link which you are referring is the old one. The new link is this.

    Best regards,
    Kemal

  • Hello Kemal,

    I have managed to bitbake the target.

    But on booting I have issues:


    After extract the files and trying to boot from nfs I get the follwing error:
    VFS: Mounted root (nfs filesystem) on device 0:12.
    Freeing init memory: 184K
    Failed to determine whether /sys is a mount point: Invalid argument
    Failed to determine whether /proc is a mount point: Invalid argument
    Failed to determine whether /dev is a mount point: Invalid argument
    Freezing execution.


    I checked why the working tar.gz supplied as prebuilt does work with nfs, and I see that the /dev folder in the prebuilt rootfs contain files, while in my image it is empty.
    I am not sure what the other error mean (for /sys and /proc), but I do also see that there is a change in permssions of that folders.
    In my image it is:
    drwxr-sr-x 2 root root 4096 Jul 5 2011 sys
    While in my image (the bitbaked image) it is:
    drwxr-xr-x 3 root root 4096 Jan 16 06:40 sys

    Can any of the above explain these errors in boot ?

    Regards,
    Ran

  • /sys, /dev, /proc are pseudo-file systems, they are empty in general when the system is not running. Can you post the complete boot log?

  • Texas Instruments X-Loader 1.46 (May 11 2011 - 19:19:54)


    U-Boot 2009.11 (May 17 2011 - 09:55:39)

    OMAP3630-GP ES2.1, CPU-OPP2 L3-165MHz
    VAR-SOM-OM3xxx Board + LPDDR/NAND
    I2C: ready
    DRAM: 256 MB
    NAND: 512 MiB
    In: serial
    Out: serial
    Err: serial
    Net: smc911x-0
    Warning: smc911x-0 MAC addresses don't match:
    Address in SROM is ff:ff:ff:ff:ff:ff
    Address in environment is ca:69:fc:e0:44:13

    Hit any key to stop autoboot: 0

    NAND read: device 0 offset 0x280000, size 0x300000
    err_loc=734
    3145728 bytes read: OK
    ## Booting kernel from Legacy Image at 80000000 ...
    Image Name: Linux-2.6.37
    Image Type: ARM Linux Kernel Image (uncompressed)
    Data Size: 2567200 Bytes = 2.4 MB
    Load Address: 80008000
    Entry Point: 80008000
    Verifying Checksum ... OK
    Loading Kernel Image ... OK
    OK

    Starting kernel ...

    Linux version 2.6.37 (vladik@odessa) (gcc version 4.3.3 (Sourcery G++ Lite 2009q1-203) ) #1 Fri Jul 8 13:04:49 IDT 2011
    CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7f
    CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache
    Machine: VARISCITE VAR-SOM-OM3X
    Reserving 4194304 bytes SDRAM for VRAM
    Memory policy: ECC disabled, Data cache writeback
    OMAP3630 ES1.2 (l2cache iva sgx neon isp 192mhz_clk )
    SRAM: Mapped pa 0x40200000 to va 0xfe400000 size: 0x10000
    Built 1 zonelists in Zone order, mobility grouping on. Total pages: 64000
    Kernel command line: mem=256M@0x80000000 console=ttyO2,115200n8 noinitrd rw consoleblank=0 omapdss.def_disp=lcd root=/dev/mtdblock4 rootfstype=jffs2 ip=192.168.1.100 ethaddr=CA:69:FC:E0:44:13
    PID hash table entries: 1024 (order: 0, 4096 bytes)
    Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
    Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
    Memory: 252MB = 252MB total
    Memory: 250536k/250536k available, 11608k reserved, 0K highmem
    Virtual kernel memory layout:
    vector : 0xffff0000 - 0xffff1000 ( 4 kB)
    fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
    DMA : 0xffc00000 - 0xffe00000 ( 2 MB)
    vmalloc : 0xd0800000 - 0xf8000000 ( 632 MB)
    lowmem : 0xc0000000 - 0xd0000000 ( 256 MB)
    modules : 0xbf000000 - 0xc0000000 ( 16 MB)
    .init : 0xc0008000 - 0xc0036000 ( 184 kB)
    .text : 0xc0036000 - 0xc04bc660 (4634 kB)
    .data : 0xc04be000 - 0xc04ff4c0 ( 262 kB)
    NR_IRQS:409
    Clocking rate (Crystal/Core/MPU): 26.0/400/800 MHz
    omap_hwmod: i2c1: softreset failed (waited 10000 usec)
    omap_hwmod: i2c2: softreset failed (waited 10000 usec)
    omap_hwmod: i2c3: softreset failed (waited 10000 usec)
    IRQ: Found an INTC at 0xfa200000 (revision 4.0) with 96 interrupts
    Total of 96 interrupts on 1 active controller
    GPMC revision 5.0
    Trying to install interrupt handler for IRQ402
    Trying to install interrupt handler for IRQ403
    Trying to install interrupt handler for IRQ404
    Trying to install interrupt handler for IRQ405
    Trying to install interrupt handler for IRQ406
    Trying to install interrupt handler for IRQ407
    Trying to install interrupt handler for IRQ408
    Trying to install type control for IRQ409
    Trying to set irq flags for IRQ409
    OMAP clockevent source: GPTIMER1 at 32768 Hz
    Console: colour dummy device 80x30
    Calibrating delay loop... 799.29 BogoMIPS (lpj=3121152)
    pid_max: default: 32768 minimum: 301
    Mount-cache hash table entries: 512
    CPU: Testing write buffer coherency: ok
    regulator: core version 0.5
    regulator: dummy:
    NET: Registered protocol family 16
    OMAP GPIO hardware version 2.5
    OMAP GPIO hardware version 2.5
    OMAP GPIO hardware version 2.5
    OMAP GPIO hardware version 2.5
    OMAP GPIO hardware version 2.5
    OMAP GPIO hardware version 2.5
    omap_mux_init: Add partition: #1: core, flags: 0
    OMAP DMA hardware revision 5.0
    bio: create slab <bio-0> at 0
    SCSI subsystem initialized
    usbcore: registered new interface driver usbfs
    usbcore: registered new interface driver hub
    usbcore: registered new device driver usb
    omap_device: omap_i2c.1: new worst case activate latency 0: 30517
    omap_i2c omap_i2c.1: bus 1 rev4.0 at 2600 kHz
    twl4030: PIH (irq 7) chaining IRQs 368..375
    twl4030: power (irq 373) chaining IRQs 376..383
    twl4030: gpio (irq 368) chaining IRQs 384..401
    regulator: VUSB1V5: 1500 mV normal standby
    regulator: VUSB1V8: 1800 mV normal standby
    regulator: VUSB3V1: 3100 mV normal standby
    twl4030_usb twl4030_usb: Initialized TWL4030 USB module
    regulator: VIO: 1800 mV normal standby
    regulator: VMMC1: 1850 <--> 3150 mV at 3000 mV normal standby
    regulator: VDAC: 1800 mV normal standby
    regulator: VAUX2_4030: 2800 mV normal standby
    regulator: VPLL2: 1800 mV normal standby
    regulator: VSIM: 1800 <--> 3000 mV at 1800 mV normal standby
    omap_device: omap_i2c.1: new worst case deactivate latency 0: 30517
    omap_i2c omap_i2c.2: bus 2 rev4.0 at 400 kHz
    omap_i2c omap_i2c.3: bus 3 rev4.0 at 400 kHz
    Advanced Linux Sound Architecture Driver Version 1.0.23.
    Switching to clocksource 32k_counter
    NET: Registered protocol family 2
    IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
    TCP established hash table entries: 8192 (order: 4, 65536 bytes)
    TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
    TCP: Hash tables configured (established 8192 bind 8192)
    TCP reno registered
    UDP hash table entries: 256 (order: 0, 4096 bytes)
    UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
    NET: Registered protocol family 1
    RPC: Registered udp transport module.
    RPC: Registered tcp transport module.
    RPC: Registered tcp NFSv4.1 backchannel transport module.
    NetWinder Floating Point Emulator V0.97 (double precision)
    omap-iommu omap-iommu.0: isp registered
    VFS: Disk quotas dquot_6.5.2
    Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
    JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
    msgmni has been set to 489
    io scheduler noop registered
    io scheduler deadline registered
    io scheduler cfq registered (default)
    OMAP DSS rev 2.0
    OMAP DISPC rev 3.0
    OMAP VENC rev 2
    OMAP DSI rev 1.0
    Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
    omap_uart.0: ttyO0 at MMIO 0x4806a000 (irq = 72) is a OMAP UART0
    omap_uart.1: ttyO1 at MMIO 0x4806c000 (irq = 73) is a OMAP UART1
    omap_uart.2: ttyO2 at MMIO 0x49020000 (irq = 74) is a OMAP UART2
    console [ttyO2] enabled
    omap_uart.3: ttyO3 at MMIO 0x49042000 (irq = 80) is a OMAP UART3
    brd: module loaded
    loop: module loaded
    omap2-nand driver initializing
    NAND device: Manufacturer ID: 0x2c, Chip ID: 0xbc (Micron )
    Creating 5 MTD partitions on "omap2-nand.0":
    0x000000000000-0x000000080000 : "X-Loader-NAND"
    0x000000080000-0x0000001c0000 : "U-Boot-NAND"
    0x0000001c0000-0x000000280000 : "Boot Env-NAND"
    0x000000280000-0x000000780000 : "Kernel-NAND"
    0x000000780000-0x000020000000 : "File System - NAND"
    smsc911x: Driver version 2008-10-21.
    smsc911x-mdio: probed
    eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=ffffffff:01, irq=-1)
    smsc911x: get mac from cmd line.
    ethaddr parsed from commandline: CA:69:FC:E0:44:13
    net eth0: MAC Address: ca:69:fc:e0:44:13
    ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
    ehci-omap ehci-omap.0: OMAP-EHCI Host Controller
    ehci-omap ehci-omap.0: new USB bus registered, assigned bus number 1
    ehci-omap ehci-omap.0: irq 77, io mem 0x48064800
    ehci-omap ehci-omap.0: USB 2.0 started, EHCI 1.00
    usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
    usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
    usb usb1: Product: OMAP-EHCI Host Controller
    usb usb1: Manufacturer: Linux 2.6.37 ehci_hcd
    usb usb1: SerialNumber: ehci-omap.0
    hub 1-0:1.0: USB hub found
    hub 1-0:1.0: 3 ports detected
    Initializing USB Mass Storage driver...
    usbcore: registered new interface driver usb-storage
    USB Mass Storage support registered.
    usbcore: registered new interface driver usbtest
    udc: OMAP UDC driver, version: 4 October 2004 (iso) (dma)
    mice: PS/2 mouse device common for all mice
    ads7846 spi1.0: touchscreen, irq 337
    input: ADS7846 Touchscreen as /devices/platform/omap2_mcspi.1/spi1.0/input/input0
    twl_rtc twl_rtc: rtc core: registered twl_rtc as rtc0
    twl_rtc twl_rtc: Power up reset detected.
    twl_rtc twl_rtc: Enabling TWL-RTC.
    i2c /dev entries driver
    lirc_dev: IR Remote Control driver registered, major 252
    IR NEC protocol handler initialized
    IR RC5(x) protocol handler initialized
    IR RC6 protocol handler initialized
    IR JVC protocol handler initialized
    IR Sony protocol handler initialized
    IR RC5 (streamzap) protocol handler initialized
    IR LIRC bridge handler initialized
    Linux video capture interface: v2.00
    omap_device: omap_wdt.-1: new worst case activate latency 0: 30517
    OMAP Watchdog Timer Rev 0x31: initial timeout 60 sec
    usbcore: registered new interface driver usbhid
    usbhid: USB HID core driver
    OMAP3 EVM SoC init
    asoc: twl4030-hifi <-> omap-mcbsp-dai.1 mapping ok
    ALSA device list:
    #0: omap3evm
    TCP cubic registered
    NET: Registered protocol family 17
    NET: Registered protocol family 15
    Registering the dns_resolver key type
    VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3
    Power Management for TI OMAP3.
    sr_init: No PMIC hook to init smartreflex
    smartreflex smartreflex.0: omap_sr_probe: SmartReflex driver initialized
    smartreflex smartreflex.1: omap_sr_probe: SmartReflex driver initialized
    clock: disabling unused clocks to save power
    platform mpu.0: omap_voltage_scale: Already at the requestedrate 800000000
    twl_rtc twl_rtc: setting system clock to 2000-01-01 00:00:00 UTC (946684800)
    omap_vout omap_vout: Buffer Size = 3686400
    omap_vout omap_vout: : registered and initialized video device 0
    omap_vout omap_vout: Buffer Size = 3686400
    omap_vout omap_vout: : registered and initialized video device 1
    usb 1-1: new high speed USB device using ehci-omap and address 2
    usb 1-1: New USB device found, idVendor=0424, idProduct=2514
    usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
    hub 1-1:1.0: USB hub found
    hub 1-1:1.0: 3 ports detected
    net eth0: SMSC911x/921x identified at 0xd085c000, IRQ: 189
    IP-Config: Guessing netmask 255.255.255.0
    IP-Config: Complete:
    device=eth0, addr=192.168.1.100, mask=255.255.255.0, gw=255.255.255.255,
    host=192.168.1.100, domain=, nis-domain=(none),
    bootserver=255.255.255.255, rootserver=255.255.255.255, rootpath=
    VFS: Mounted root (jffs2 filesystem) on device 31:4.
    Freeing init memory: 184K
    Failed to determine whether /sys is a mount point: Invalid argument
    Failed to determine whether /proc is a mount point: Invalid argument
    Failed to determine whether /dev is a mount point: Invalid argument
    Freezing execution.

    I am probably doing something very wrong.
    Probably the board can't work with the yocto arago bitbake for some reason.
    I use kernel not from bitbake, and only tried to use the bitbaked filesystem.

    Regards,
    Ran
  • Yes, most probably the older kernel version causes this issue. It also could be a SystemD or SystemV related.

  • I will stick to the tarball provided, moving to bitbake seems to be a bit problematic .
    Thanks