ERROR building fsl-image-test for i.MX6SL eVK

ERROR building fsl-image-test for i.MX6SL eVK

[Michael Urbaniak]

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

Please see output below that was generated by attempting to build
fsl-image-test.

Any suggestions?

 

Thanks

Mike

 

 

 

mikeu@ubuntu:~/Yocto/fsl-community-bsp/build$ bitbake fsl-image-test

Loading cache: 100%
|#######################################################################
#################################| ETA:  00:00:00

Loaded 1627 entries from dependency cache.

 

Build Configuration:

BB_VERSION        = "1.17.1"

BUILD_SYS         = "i686-linux"

NATIVELSBSTRING   = "Ubuntu-12.04"

TARGET_SYS        = "arm-poky-linux-gnueabi"

MACHINE           = "imx6slevk"

DISTRO            = "poky"

DISTRO_VERSION    = "1.3+snapshot-20130326"

TUNE_FEATURES     = "armv7a vfp neon"

TARGET_FPU        = "vfp-neon"

meta              

meta-yocto        =
"(nobranch):f36926a264190e6202830e8520b41b30ae77ea43"

meta-oe           =
"(nobranch):7c27c81a1bfc7b11ae7d7747b5c669776cbc328f"

meta-fsl-arm      =
"(nobranch):2ea1d2c944c63a078a1921cf8b8abfbc04d5adaa"

meta-fsl-arm-extra =
"(nobranch):2ceee4eecbfdf43af65802c07c61ce19c9c1b791"

meta-fsl-demos    =
"(nobranch):4036190439b3051c9e6adae7ee372ad36a380884"

 

NOTE: Resolving any missing task queue dependencies

NOTE: multiple providers are available for jpeg (jpeg, libjpeg-turbo)

NOTE: consider defining a PREFERRED_PROVIDER entry to match jpeg

NOTE: multiple providers are available for jpeg-native (jpeg-native,
libjpeg-turbo-native)

NOTE: consider defining a PREFERRED_PROVIDER entry to match jpeg-native

NOTE: Preparing runqueue

NOTE: Executing SetScene Tasks

NOTE: Executing RunQueue Tasks

ERROR: debugedit failed with exit code 1 (cmd was
'/home/mikeu/Yocto/fsl-community-bsp/build/tmp/sysroots/i686-linux/usr/l
ib/rpm/bin/debugedit' -b
'/home/mikeu/Yocto/fsl-community-bsp/build/tmp/work/imx6slevk-poky-linux
-gnueabi' -d '/usr/src/debug' -i -l
'/home/mikeu/Yocto/fsl-community-bsp/build/tmp/work/imx6slevk-poky-linux
-gnueabi/libfslcodec/3.0.5-r1/debugsources.list'
'/home/mikeu/Yocto/fsl-community-bsp/build/tmp/work/imx6slevk-poky-linux
-gnueabi/libfslcodec/3.0.5-r1/package/usr/lib/lib_png_dec_arm11_elinux.s
o.1')

ERROR: Function failed: split_and_strip_files

ERROR: Logfile of failure stored in:
/home/mikeu/Yocto/fsl-community-bsp/build/tmp/work/imx6slevk-poky-linux-
gnueabi/libfslcodec/3.0.5-r1/temp/log.do_package.20509

ERROR: Task 2521
(/home/mikeu/Yocto/fsl-community-bsp/sources/meta-fsl-arm/recipes-multim
edia/libfslcodec/libfslcodec_3.0.5.bb, do_package) failed with exit code
'1'

NOTE: Tasks Summary: Attempted 2589 tasks of which 2579 didn't need to
be rerun and 1 failed.

Waiting for 0 running tasks to finish:

 

Summary: 1 task failed:

 
/home/mikeu/Yocto/fsl-community-bsp/sources/meta-fsl-arm/recipes-multime
dia/libfslcodec/libfslcodec_3.0.5.bb, do_package

Summary: There were 2 ERROR messages shown, returning a non-zero exit
code.

 

 

Here are the log file contents:

DEBUG: Executing python function sstate_task_prefunc

DEBUG: Python function sstate_task_prefunc finished

DEBUG: Executing python function do_package

DEBUG: Executing python function package_get_auto_pr

DEBUG: Python function package_get_auto_pr finished

DEBUG: Executing python function perform_packagecopy

DEBUG: Python function perform_packagecopy finished

DEBUG: Executing python function split_and_strip_files

c6ec60c2bcda5d46310af58fad418ae4701cc55b

Failed to write file: invalid section alignment

ERROR: debugedit failed with exit code 1 (cmd was
'/home/mikeu/Yocto/fsl-community-bsp/build/tmp/sysroots/i686-linux/usr/l
ib/rpm/bin/debugedit' -b
'/home/mikeu/Yocto/fsl-community-bsp/build/tmp/work/imx6slevk-poky-linux
-gnueabi' -d '/usr/src/debug' -i -l
'/home/mikeu/Yocto/fsl-community-bsp/build/tmp/work/imx6slevk-poky-linux
-gnueabi/libfslcodec/3.0.5-r1/debugsources.list'
'/home/mikeu/Yocto/fsl-community-bsp/build/tmp/work/imx6slevk-poky-linux
-gnueabi/libfslcodec/3.0.5-r1/package/usr/lib/lib_png_dec_arm11_elinux.s
o.1')

DEBUG: Python function split_and_strip_files finished

DEBUG: Python function do_package finished

ERROR: Function failed: split_and_strip_files

 


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

Re: ERROR building fsl-image-test for i.MX6SL eVK

[Otavio Salvador]

On Tue, Mar 26, 2013 at 2:16 PM, Michael Urbaniak <MikeU@ebtron.com> wrote:
> Please see output below that was generated by attempting to build
> fsl-image-test.
>
> Any suggestions?

I just sent a patch which should fix it, please give it a try.

--
Otavio Salvador                             O.S. Systems
E-mail: otavio@ossystems.com.br  http://www.ossystems.com.br
Mobile: +55 53 9981-7854              http://projetos.ossystems.com.br

Re: ERROR building fsl-image-test for i.MX6SL eVK

[Daiane Angolini]

On 03/26/2013 02:36 PM, Otavio Salvador wrote:
> On Tue, Mar 26, 2013 at 2:16 PM, Michael Urbaniak <MikeU@ebtron.com> wrote:
>> Please see output below that was generated by attempting to build
>> fsl-image-test.
>>
>> Any suggestions?
>
> I just sent a patch which should fix it, please give it a try.

I haven't double checked if this multimedia version if compatible with 
imx6sl boards.

So, I'm not sure they just work or not.

Daiane


-- 
Daiane

Re: ERROR building fsl-image-test for i.MX6SL eVK

[Fabio Estevam]

On Tue, Mar 26, 2013 at 3:14 PM, Daiane Angolini
<daiane.angolini@freescale.com> wrote:
> On 03/26/2013 02:36 PM, Otavio Salvador wrote:
>>
>> On Tue, Mar 26, 2013 at 2:16 PM, Michael Urbaniak <MikeU@ebtron.com>
>> wrote:
>>>
>>> Please see output below that was generated by attempting to build
>>> fsl-image-test.
>>>
>>> Any suggestions?
>>
>>
>> I just sent a patch which should fix it, please give it a try.
>
>
> I haven't double checked if this multimedia version if compatible with
> imx6sl boards.
>
> So, I'm not sure they just work or not.

mx6solo lite does not have VPU, so we could use the standard Gstreamer
plugins instead.

Regards,

Fabio Estevam

Re: ERROR building fsl-image-test for i.MX6SL eVK

[Michael Urbaniak]

That allowed the build to complete.
I created the sd card but it seems to hang at different points during
boot.

For example:
Waiting for root device /dev/mmcblk0p2...
mmc1: new high speed SDHC card at address aaaa
mmcblk0: mmc1:aaaa SU08G 7.40 GiB

or next reset

VFS: Mounted root (ext3 filesystem) on device 179:2.
devtmpfs: mounted
Freeing init memory: 180K
INIT: version 2.88 booting

or next reset
VFS: Mounted root (ext3 filesystem) on device 179:2.
devtmpfs: mounted
Freeing init memory: 180K

I have to go to some meetings so I will look closer tomorrow.

Thanks
Mike



-----Original Message-----
From: otavio.salvador@gmail.com [mailto:otavio.salvador@gmail.com] On
Behalf Of Otavio Salvador
Sent: Tuesday, March 26, 2013 1:36 PM
To: Michael Urbaniak
Cc: meta-freescale@yoctoproject.org
Subject: Re: [meta-freescale] ERROR building fsl-image-test for i.MX6SL
eVK

On Tue, Mar 26, 2013 at 2:16 PM, Michael Urbaniak <MikeU@ebtron.com>
wrote:
> Please see output below that was generated by attempting to build 
> fsl-image-test.
>
> Any suggestions?

I just sent a patch which should fix it, please give it a try.

--
Otavio Salvador                             O.S. Systems
E-mail: otavio@ossystems.com.br  http://www.ossystems.com.br
Mobile: +55 53 9981-7854              http://projetos.ossystems.com.br

Re: ERROR building fsl-image-test for i.MX6SL eVK

[Daiane Angolini]

On 03/26/2013 05:43 PM, Michael Urbaniak wrote:
> That allowed the build to complete.
> I created the sd card but it seems to hang at different points during
> boot.
>
> For example:
> Waiting for root device /dev/mmcblk0p2...
> mmc1: new high speed SDHC card at address aaaa
> mmcblk0: mmc1:aaaa SU08G 7.40 GiB
>
> or next reset
>
> VFS: Mounted root (ext3 filesystem) on device 179:2.
> devtmpfs: mounted
> Freeing init memory: 180K
> INIT: version 2.88 booting
>
> or next reset
> VFS: Mounted root (ext3 filesystem) on device 179:2.
> devtmpfs: mounted
> Freeing init memory: 180K

Very first boot is really slow. (and I always get confused about what is 
a slow boot and a boot crash when using very first boot sdcards)

So, could you, please, give some time to the very first boot?

I mean, only to make sure this is not the case ;)


Thanks a lot in advance,
Daiane

Re: ERROR building fsl-image-test for i.MX6SL eVK

[Michael Urbaniak]

It seems very random where it hangs.
One time it went as far as displaying Yocto on the lcd and a progress bar.
The last time it was six minutes at 
mmcblk0: p1 p2
EXT3-fs: barriers not enabled

Here is the boot console info.

U-Boot 2009.08-dirty (Mar 25 2013 - 16:14:18)

CPU: Freescale i.MX6 family TO0.0 at 396 MHz
Temperature:   34 C, calibration data 0x5c05335f
mx6q pll1: 792MHz
mx6q pll2: 528MHz
mx6q pll3: 480MHz
mx6q pll8: 50MHz
ipg clock     : 49500000Hz
ipg per clock : 49500000Hz
uart clock    : 80000000Hz
cspi clock    : 60000000Hz
ahb clock     : 99000000Hz
axi clock   : 198000000Hz
emi_slow clock: 99000000Hz
ddr clock     : 396000000Hz
usdhc1 clock  : 198000000Hz
usdhc2 clock  : 198000000Hz
usdhc3 clock  : 198000000Hz
usdhc4 clock  : 198000000Hz
Board: MX6SoloLite-EVK:[ POR ]
Boot Device: SD
I2C:   ready
DRAM:  512 MB
MMC:   FSL_USDHC: 0,FSL_USDHC: 1,FSL_USDHC: 2
In:    serial
Out:   serial
Err:   serial
Found PFUZE100! deviceid=10,revid=11
Net:   got MAC address from IIM: 00:04:9f:02:76:dd
FEC0
Hit any key to stop autoboot:  0
reading uImage

3553484 bytes read
Booting from mmc ...
## Booting kernel from Legacy Image at 80800000 ...
   Image Name:   Linux-3.0.35-3.0.0+yocto+g7e8c89
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3553420 Bytes =  3.4 MB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Linux version 3.0.35-3.0.0+yocto+g7e8c89c (mikeu@ubuntu) (gcc version 4.7.2 (GCC) ) #1 PREEMPT Mon Mar 25 16:28:40 EDT 2013
CPU: ARMv7 Processor [412fc09a] revision 10 (ARMv7), cr=10c53c7d
CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine: Freescale i.MX 6SoloLite EVK Board
Memory policy: ECC disabled, Data cache writeback
CPU identified as i.MX6SoloLite, silicon rev 1.0
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 121856
Kernel command line: console=ttymxc0,115200 root=/dev/mmcblk0p2 rw rootfstype=ext3 rootwait
PID hash table entries: 2048 (order: 1, 8192 bytes)
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 480MB = 480MB total
Memory: 476148k/476148k available, 48140k reserved, 0K highmem
Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
    DMA     : 0xf4600000 - 0xffe00000   ( 184 MB)
    vmalloc : 0xa0800000 - 0xf2000000   (1304 MB)
    lowmem  : 0x80000000 - 0xa0000000   ( 512 MB)
    pkmap   : 0x7fe00000 - 0x80000000   (   2 MB)
    modules : 0x7f000000 - 0x7fe00000   (  14 MB)
      .init : 0x80008000 - 0x80035000   ( 180 kB)
      .text : 0x80035000 - 0x80a1fcb8   (10156 kB)
      .data : 0x80a20000 - 0x80a6e9a0   ( 315 kB)
       .bss : 0x80a6e9c4 - 0x80a932f8   ( 147 kB)
SLUB: Genslabs=13, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Preemptible hierarchical RCU implementation.
NR_IRQS:496
MXC GPIO hardware
sched_clock: 32 bits at 3000kHz, resolution 333ns, wraps every 1431655ms
MXC_Early serial console at MMIO 0x2020000 (options '115200')
bootconsole [ttymxc0] enabled
Console: colour dummy device 80x30
Calibrating delay loop... 789.70 BogoMIPS (lpj=3948544)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
hw perfevents: enabled with ARMv7 Cortex-A9 PMU driver, 7 counters available
devtmpfs: initialized
print_constraints: dummy:
NET: Registered protocol family 16
print_constraints: vddpu: 725 <--> 1300 mV at 700 mV fast normal
print_constraints: vddcore: 725 <--> 1300 mV at 1100 mV fast normal
print_constraints: vddsoc: 725 <--> 1300 mV at 1200 mV fast normal
print_constraints: vdd2p5: 2000 <--> 2775 mV at 2400 mV fast normal
print_constraints: vdd1p1: 800 <--> 1400 mV at 1100 mV fast normal
print_constraints: vdd3p0: 2625 <--> 3400 mV at 3000 mV fast normal
hw-breakpoint: found 6 breakpoint and 1 watchpoint registers.
hw-breakpoint: 1 breakpoint(s) reserved for watchpoint single-step.
hw-breakpoint: maximum watchpoint size is 4 bytes.
L310 cache controller enabled
l2x0: 16 ways, CACHE_ID 0x410000c8, AUX_CTRL 0x02030000, Cache size: 262144 B
IMX usb wakeup probe
bio: create slab <bio-0> at 0
print_constraints: vmmc: 3300 mV
print_constraints: SPKVDD: 4325 mV
SCSI subsystem initialized
spi_imx imx6q-ecspi.0: probed
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
Freescale USB OTG Driver loaded, $Revision: 1.55 $
add wake up source irq 75
mc_pfuze 0-0008: ID: 0,Full lay: 1 ,Metal lay: 1
mc_pfuze 0-0008: FAB: 0 ,FIN: 0
print_constraints: PFUZE100_SW1A: 300 <--> 1875 mV at 1250 mV
print_constraints: PFUZE100_SW1B: 300 <--> 1875 mV at 300 mV
print_constraints: PFUZE100_SW1C: 300 <--> 1875 mV at 1200 mV
print_constraints: PFUZE100_SW2: 800 <--> 3950 mV at 3150 mV
print_constraints: PFUZE100_SW3A: 400 <--> 1975 mV at 1200 mV
print_constraints: PFUZE100_SW3B: 400 <--> 1975 mV at 1200 mV
print_constraints: PFUZE100_SW4: 800 <--> 3950 mV at 3300 mV
print_constraints: PFUZE100_SWBST: 5000 <--> 5150 mV at 5000 mV
print_constraints: PFUZE100_VSNVS: 1200 <--> 3000 mV at 1800 mV
print_constraints: PFUZE100_VREFDDR: at 750 mV
print_constraints: PFUZE100_VGEN1: 800 <--> 1550 mV at 1200 mV
print_constraints: PFUZE100_VGEN2: 800 <--> 1550 mV at 800 mV
print_constraints: PFUZE100_VGEN3: 1800 <--> 3300 mV at 1800 mV
print_constraints: PFUZE100_VGEN4: 1800 <--> 3300 mV at 1800 mV
print_constraints: PFUZE100_VGEN5: 1800 <--> 3300 mV at 2500 mV
print_constraints: PFUZE100_VGEN6: 1800 <--> 3300 mV at 1800 mV
i2c i2c-1: Invalid 7-bit I2C address 0x00
i2c i2c-1: Can't create device at 0x00
MIPI CSI2 driver module loaded
Advanced Linux Sound Architecture Driver Version 1.0.24.
Bluetooth: Core ver 2.16
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: L2CAP socket layer initialized
Bluetooth: SCO socket layer initialized
cfg80211: Calling CRDA to update world regulatory domain
max17135 0-0048: Max17135 PMIC not found!
max17135 regulator init failed: -6
i2c-core: driver [max17135] using legacy suspend method
i2c-core: driver [max17135] using legacy resume method
Switching to clocksource mxc_timer1
NET: Registered protocol family 2
IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
TCP established hash table entries: 16384 (order: 5, 131072 bytes)
TCP bind hash table entries: 16384 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 16384 bind 16384)
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 named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
etb: probe of etb failed with error -2
etm: probe of etm.0 failed with error -2
Static Power Management for Freescale i.MX6
wait mode is enabled for i.MX6
cpaddr = a0820000 suspend_iram_base=a0840000
PM driver module loaded
IMX usb wakeup probe
_regulator_get: get() with no identifier
mx6_cpu_regulator_init: failed to get pu regulator
i.MXC CPU frequency driver
JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
msgmni has been set to 929
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
i2c-core: driver [sii902x] using legacy suspend method
i2c-core: driver [sii902x] using legacy resume method
Console: switching to colour frame buffer device 100x30
imx-sdma imx-sdma: loaded firmware 1.1
imx-sdma imx-sdma: initialized
Serial: IMX driver
imx-uart.0: ttymxc0 at MMIO 0x2020000 (irq = 58) is a IMX
console [ttymxc0] enabled, bootconsole disabled
console [ttymxc0] enabled, bootconsole disabled
fsl_rngc fsl_rngc.0: FSL RNGC Registered.
loop: module loaded
m25p80 spi0.0: m25p32 (4096 Kbytes)
Creating 2 MTD partitions on "m25p32":
0x000000000000-0x000000100000 : "bootloader"
0x000000100000-0x000000400000 : "kernel"
vcan: Virtual CAN interface driver
CAN device driver interface
flexcan netdevice driver
FEC Ethernet Driver
fec_enet_mii_bus: probed
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
fsl-ehci fsl-ehci.0: Freescale On-Chip EHCI Host Controller
fsl-ehci fsl-ehci.0: new USB bus registered, assigned bus number 1
fsl-ehci fsl-ehci.0: irq 75, io base 0x02184000
fsl-ehci fsl-ehci.0: USB 2.0 started, EHCI 1.00
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
add wake up source irq 74
fsl-ehci fsl-ehci.1: Freescale On-Chip EHCI Host Controller
fsl-ehci fsl-ehci.1: new USB bus registered, assigned bus number 2
fsl-ehci fsl-ehci.1: irq 74, io base 0x02184200
fsl-ehci fsl-ehci.1: USB 2.0 started, EHCI 1.00
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 1 port detected
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
ARC USBOTG Device Controller driver (1 August 2005)
mousedev: PS/2 mouse device common for all mice
input: imx-keypad as /devices/platform/imx-keypad/input/input0
elan - Read Hello Packet Failed
elan-touch: probe of 0-0010 failed with error -22
i2c-core: driver [isl29023] using legacy suspend method
i2c-core: driver [isl29023] using legacy resume method
snvs_rtc snvs_rtc.0: rtc core: registered snvs_rtc as rtc0
i2c /dev entries driver
Linux video capture interface: v2.00
pxp-v4l2 pxp-v4l2: initialized
i2c-core: driver [mag3110] using legacy suspend method
i2c-core: driver [mag3110] using legacy resume method
check mma8450 chip ID
mma8450 0-001c: read chip ID 0xfffffffb is not equal to 0xc6!
read chip ID failed
mma8450: probe of 0-001c failed with error -22
i2c-core: driver [mma8450] using legacy suspend method
i2c-core: driver [mma8450] using legacy resume method
add mma8450 i2c driver
imx2-wdt imx2-wdt.0: IMX2+ Watchdog Timer enabled. timeout=60s (nowayout=1)
Bluetooth: Virtual HCI driver ver 1.3
Bluetooth: HCI UART driver ver 2.2
Bluetooth: HCIATH3K protocol initialized
Bluetooth: Generic Bluetooth USB driver ver 0.6
usbcore: registered new interface driver btusb
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
mmc0: SDHCI controller on platform [sdhci-esdhc-imx.0] using DMA
mmc1: SDHCI controller on platform [sdhci-esdhc-imx.1] using DMA
sdhci sdhci-esdhc-imx.2: no write-protect pin available!
mmc2: SDHCI controller on platform [sdhci-esdhc-imx.2] using DMA
Thermal calibration data is 0x5c05335f
Anatop Thermal registered as thermal_zone0
anatop_thermal_probe: default cooling device is cpufreq!
dcp dcp.0: DCP crypto enabled.!
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
usbcore: registered new interface driver snd-usb-audio
mxc_spdif mxc_spdif.0: MXC SPDIF Audio
Cirrus Logic CS42888 ALSA SoC Codec Driver
i2c-core: driver [cs42888] using legacy suspend method
i2c-core: driver [cs42888] using legacy resume method
wm8962 1-001a: customer id 0 revision D
input: WM8962 Beep Generator as /devices/platform/imx-i2c.1/i2c-1/1-001a/input/input1
asoc: wm8962 <-> imx-ssi.1 mapping ok
imx_3stack asoc driver
asoc: mxc-spdif <-> imx-spdif-dai.0 mapping ok
ALSA device list:
  #0: wm8962-audio
  #1: imx-spdif
TCP cubic registered
NET: Registered protocol family 17
can: controller area network core (rev 20090105 abi 8)
NET: Registered protocol family 29
can: raw protocol (rev 20090105)
can: broadcast manager protocol (rev 20090105 t)
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM ver 1.11
Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Bluetooth: BNEP filters: protocol multicast
Bluetooth: HIDP (Human Interface Emulation) ver 1.2
lib80211: common routines for IEEE802.11 drivers
VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
Bus freq driver module loaded
Bus freq driver Enabled
mxc_dvfs_core_probe
DVFS driver module loaded
imx_epdc_fb imx_epdc_fb: Unable to get display PMIC regulator.err = 0xffffffed
regulator_init_complete: PFUZE100_VGEN5: incomplete constraints, leaving on
snvs_rtc snvs_rtc.0: setting system clock to 1970-01-01 00:30:06 UTC (1806)
Waiting for root device /dev/mmcblk0p2...
mmc1: new high speed SDHC card at address aaaa
mmcblk0: mmc1:aaaa SU08G 7.40 GiB
 mmcblk0: p1 p2
EXT3-fs: barriers not enabled







-----Original Message-----
From: Daiane Angolini [mailto:daiane.angolini@freescale.com] 
Sent: Wednesday, March 27, 2013 8:23 AM
To: Michael Urbaniak
Cc: Otavio Salvador; meta-freescale@yoctoproject.org
Subject: Re: [meta-freescale] ERROR building fsl-image-test for i.MX6SL eVK

On 03/26/2013 05:43 PM, Michael Urbaniak wrote:
> That allowed the build to complete.
> I created the sd card but it seems to hang at different points during 
> boot.
>
> For example:
> Waiting for root device /dev/mmcblk0p2...
> mmc1: new high speed SDHC card at address aaaa
> mmcblk0: mmc1:aaaa SU08G 7.40 GiB
>
> or next reset
>
> VFS: Mounted root (ext3 filesystem) on device 179:2.
> devtmpfs: mounted
> Freeing init memory: 180K
> INIT: version 2.88 booting
>
> or next reset
> VFS: Mounted root (ext3 filesystem) on device 179:2.
> devtmpfs: mounted
> Freeing init memory: 180K

Very first boot is really slow. (and I always get confused about what is a slow boot and a boot crash when using very first boot sdcards)

So, could you, please, give some time to the very first boot?

I mean, only to make sure this is not the case ;)


Thanks a lot in advance,
Daiane

Re: ERROR building fsl-image-test for i.MX6SL eVK

[Michael Urbaniak]

I went back to the core-image-minimal and the same issue occurs although
not every time.
It will hang 7 out of 10 attempts.
Mostly here:
EXT3-fs (mmcblk0p2): mounted filesystem with writeback data mode
VFS: Mounted root (ext3 filesystem) on device 179:2.
devtmpfs: mounted
Freeing init memory: 180K

I tried different sd cards all with the same result.
I then copied my LTIB image's to the same cards and they boot every
time.

Strange......


-----Original Message-----
From: Daiane Angolini [mailto:daiane.angolini@freescale.com] 
Sent: Wednesday, March 27, 2013 8:23 AM
To: Michael Urbaniak
Cc: Otavio Salvador; meta-freescale@yoctoproject.org
Subject: Re: [meta-freescale] ERROR building fsl-image-test for i.MX6SL
eVK

On 03/26/2013 05:43 PM, Michael Urbaniak wrote:
> That allowed the build to complete.
> I created the sd card but it seems to hang at different points during 
> boot.
>
> For example:
> Waiting for root device /dev/mmcblk0p2...
> mmc1: new high speed SDHC card at address aaaa
> mmcblk0: mmc1:aaaa SU08G 7.40 GiB
>
> or next reset
>
> VFS: Mounted root (ext3 filesystem) on device 179:2.
> devtmpfs: mounted
> Freeing init memory: 180K
> INIT: version 2.88 booting
>
> or next reset
> VFS: Mounted root (ext3 filesystem) on device 179:2.
> devtmpfs: mounted
> Freeing init memory: 180K

Very first boot is really slow. (and I always get confused about what is
a slow boot and a boot crash when using very first boot sdcards)

So, could you, please, give some time to the very first boot?

I mean, only to make sure this is not the case ;)


Thanks a lot in advance,
Daiane

Re: ERROR building fsl-image-test for i.MX6SL eVK

[Otavio Salvador]

On Wed, Mar 27, 2013 at 10:04 AM, Michael Urbaniak <MikeU@ebtron.com> wrote:
> I tried different sd cards all with the same result.
> I then copied my LTIB image's to the same cards and they boot every
> time.

Please try to use the U-Boot from LTIB with the sdcard from Yocto so
we can find out if it is in U-Boot or Kernel?

--
Otavio Salvador                             O.S. Systems
E-mail: otavio@ossystems.com.br  http://www.ossystems.com.br
Mobile: +55 53 9981-7854              http://projetos.ossystems.com.br

Re: ERROR building fsl-image-test for i.MX6SL eVK

[Fabio Estevam]

On Wed, Mar 27, 2013 at 10:23 AM, Otavio Salvador
<otavio@ossystems.com.br> wrote:
> On Wed, Mar 27, 2013 at 10:04 AM, Michael Urbaniak <MikeU@ebtron.com> wrote:
>> I tried different sd cards all with the same result.
>> I then copied my LTIB image's to the same cards and they boot every
>> time.
>
> Please try to use the U-Boot from LTIB with the sdcard from Yocto so
> we can find out if it is in U-Boot or Kernel?

Michael's log indicates that he is using U-boot 2009.08.

Re: ERROR building fsl-image-test for i.MX6SL eVK

[Otavio Salvador]

On Wed, Mar 27, 2013 at 10:44 AM, Fabio Estevam <festevam@gmail.com> wrote:
> On Wed, Mar 27, 2013 at 10:23 AM, Otavio Salvador
> <otavio@ossystems.com.br> wrote:
>> On Wed, Mar 27, 2013 at 10:04 AM, Michael Urbaniak <MikeU@ebtron.com> wrote:
>>> I tried different sd cards all with the same result.
>>> I then copied my LTIB image's to the same cards and they boot every
>>> time.
>>
>> Please try to use the U-Boot from LTIB with the sdcard from Yocto so
>> we can find out if it is in U-Boot or Kernel?
>
> Michael's log indicates that he is using U-boot 2009.08.

Yes but it does not states the branch.

--
Otavio Salvador                             O.S. Systems
E-mail: otavio@ossystems.com.br  http://www.ossystems.com.br
Mobile: +55 53 9981-7854              http://projetos.ossystems.com.br

Re: ERROR building fsl-image-test for i.MX6SL eVK

[Michael Urbaniak]

I was using u-boot-v2009.08-imx_12.10.02 for my LTIB setup.
The only thing I changed from the original was the #define in
mx6sl_evk.h that specifies the ram amount.
It was set for 512M and the board has 1G.
I also believe the rootfs image was ext2 not ext3........

Unfortunately I have some other "fires" to put out this am but I will
get back on this as soon as I possibly can.

Thanks in advance for the help!

Mike


-----Original Message-----
From: otavio.salvador@gmail.com [mailto:otavio.salvador@gmail.com] On
Behalf Of Otavio Salvador
Sent: Wednesday, March 27, 2013 9:47 AM
To: Fabio Estevam
Cc: Michael Urbaniak; meta-freescale@yoctoproject.org
Subject: Re: [meta-freescale] ERROR building fsl-image-test for i.MX6SL
eVK

On Wed, Mar 27, 2013 at 10:44 AM, Fabio Estevam <festevam@gmail.com>
wrote:
> On Wed, Mar 27, 2013 at 10:23 AM, Otavio Salvador 
> <otavio@ossystems.com.br> wrote:
>> On Wed, Mar 27, 2013 at 10:04 AM, Michael Urbaniak <MikeU@ebtron.com>
wrote:
>>> I tried different sd cards all with the same result.
>>> I then copied my LTIB image's to the same cards and they boot every 
>>> time.
>>
>> Please try to use the U-Boot from LTIB with the sdcard from Yocto so 
>> we can find out if it is in U-Boot or Kernel?
>
> Michael's log indicates that he is using U-boot 2009.08.

Yes but it does not states the branch.

--
Otavio Salvador                             O.S. Systems
E-mail: otavio@ossystems.com.br  http://www.ossystems.com.br
Mobile: +55 53 9981-7854              http://projetos.ossystems.com.br

Re: ERROR building fsl-image-test for i.MX6SL eVK

[Daiane Angolini]

On 03/27/2013 11:13 AM, Michael Urbaniak wrote:
> I was using u-boot-v2009.08-imx_12.10.02 for my LTIB setup.

I used 2009.08_3.0.0 tag that is a newer u-boot version.

So, it's a difference.......

> The only thing I changed from the original was the #define in
> mx6sl_evk.h that specifies the ram amount.
> It was set for 512M and the board has 1G.
> I also believe the rootfs image was ext2 not ext3........
>
> Unfortunately I have some other "fires" to put out this am but I will
> get back on this as soon as I possibly can.
No problem. Thanks a lot for testing and reporting bugs.


Daiane

Re: ERROR building fsl-image-test for i.MX6SL eVK

[Michael Urbaniak]

Both core-image-minimal and fsl-image-test boot fine if I use
u-boot-v2009.08-imx_12.10.02.


-----Original Message-----
From: Daiane Angolini [mailto:daiane.angolini@freescale.com] 
Sent: Wednesday, March 27, 2013 10:17 AM
To: Michael Urbaniak
Cc: Otavio Salvador; Fabio Estevam; meta-freescale@yoctoproject.org
Subject: Re: [meta-freescale] ERROR building fsl-image-test for i.MX6SL
eVK

On 03/27/2013 11:13 AM, Michael Urbaniak wrote:
> I was using u-boot-v2009.08-imx_12.10.02 for my LTIB setup.

I used 2009.08_3.0.0 tag that is a newer u-boot version.

So, it's a difference.......

> The only thing I changed from the original was the #define in 
> mx6sl_evk.h that specifies the ram amount.
> It was set for 512M and the board has 1G.
> I also believe the rootfs image was ext2 not ext3........
>
> Unfortunately I have some other "fires" to put out this am but I will 
> get back on this as soon as I possibly can.
No problem. Thanks a lot for testing and reporting bugs.


Daiane

Re: ERROR building fsl-image-test for i.MX6SL eVK

[Fabio Estevam]

On Wed, Mar 27, 2013 at 2:00 PM, Michael Urbaniak <MikeU@ebtron.com> wrote:
> Both core-image-minimal and fsl-image-test boot fine if I use
> u-boot-v2009.08-imx_12.10.02.

Daiane, looks like that only imx_12.10.02 was tested on mx6sololite.

Please use this U-boot version instead.

Re: ERROR building fsl-image-test for i.MX6SL eVK

[Otavio Salvador]

On Wed, Mar 27, 2013 at 2:02 PM, Fabio Estevam <festevam@gmail.com> wrote:
> On Wed, Mar 27, 2013 at 2:00 PM, Michael Urbaniak <MikeU@ebtron.com> wrote:
>> Both core-image-minimal and fsl-image-test boot fine if I use
>> u-boot-v2009.08-imx_12.10.02.
>
> Daiane, looks like that only imx_12.10.02 was tested on mx6sololite.
>
> Please use this U-boot version instead.

What about the kernel?

--
Otavio Salvador                             O.S. Systems
E-mail: otavio@ossystems.com.br  http://www.ossystems.com.br
Mobile: +55 53 9981-7854              http://projetos.ossystems.com.br

Re: ERROR building fsl-image-test for i.MX6SL eVK

[Daiane Angolini]

On 03/27/2013 02:02 PM, Fabio Estevam wrote:
> On Wed, Mar 27, 2013 at 2:00 PM, Michael Urbaniak <MikeU@ebtron.com> wrote:
>> Both core-image-minimal and fsl-image-test boot fine if I use
>> u-boot-v2009.08-imx_12.10.02.
>
> Daiane, looks like that only imx_12.10.02 was tested on mx6sololite.
>
> Please use this U-boot version instead.
>
Sure, I will create the patch to downgrade it

-- 
Daiane

Re: ERROR building fsl-image-test for i.MX6SL eVK

[Fabio Estevam]

On Wed, Mar 27, 2013 at 2:05 PM, Otavio Salvador
<otavio@ossystems.com.br> wrote:
> On Wed, Mar 27, 2013 at 2:02 PM, Fabio Estevam <festevam@gmail.com> wrote:
>> On Wed, Mar 27, 2013 at 2:00 PM, Michael Urbaniak <MikeU@ebtron.com> wrote:
>>> Both core-image-minimal and fsl-image-test boot fine if I use
>>> u-boot-v2009.08-imx_12.10.02.
>>
>> Daiane, looks like that only imx_12.10.02 was tested on mx6sololite.
>>
>> Please use this U-boot version instead.
>
> What about the kernel?

Just checked that the latest release for sololite was 12.10.