EBA0 is not 8-byte aligned error on imx6

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

EBA0 is not 8-byte aligned error on imx6

6,847 Views
alokkumar
Contributor III

Dear All,

I have been "EBA0 is not 8-byte aligned" error and not sure what it means.

Does this mean my display window should be 8 byte aligned 640x480 etc or size of file should be dividable by 8 ?

VSALPHA=1 gst-launch filesrc location=./01.jpg ! jpegdec ! imagefreeze ! mfw_i

sink

MFW_GST_ISINK_PLUGIN 3.0.5 build on Apr 17 2013 12:11:46.

Setting pipeline to PAUSED ...

Pipeline is PREROLLING ...

hwbuf allocator zone(4718592) created

Pipeline is PREROLLED ...

Setting pipeline to PLAYING ...

New clock: GstSystemClock

VS0 created. in fmt[I420] win(0,0-2048,1536:2048x1536) out win(0,0-1920,1080:1920x1080)

set deinterlace mode 0

hwbuf allocator zone(614400) createimx-ipuv3 imx-ipuv3.0: IDMAC12's EBA0 is not 8-byte aligned

d

imx-ipuv3 imx-ipuv3.0: IDMAC11's EBA0 is not 8-byte aligned

hwbuf allocator zone(614400) destroied.

hwbuf allocator zone(614400) created

imx-ipuv3 imx-ipuv3.0: IDMAC12's EBA0 is not 8-byte aligned

imx-ipuv3 imx-ipuv3.0: IDMAC11's EBA0 is not 8-byte aligned

hwbuf allocator zone(614400) destroied.

hwbuf allocator zone(614400) created

imx-ipuv3 imx-ipuv3.0: IDMAC12's EBA0 is not 8-byte aligned

imx-ipuv3 imx-ipuv3.0: IDMAC11's EBA0 is not 8-byte aligned

hwbuf allocator zone(614400) destroied.

imx-ipuv3 imx-ipuv3.0: IPU Warning - IPU_INT_STAT_10 = 0x00100000

imx-ipuv3 imx-ipuv3.0: IPU Warning - IPU_INT_STAT_10 = 0x00100000

imx-ipuv3 imx-ipuv3.0: IPU Warning - IPU_INT_STAT_10 = 0x00100000

imx-ipuv3 imx-ipuv3.0: IPU Warning - IPU_INT_STAT_10 = 0x00100000

^CCaught interrupt -- imx-ipuv3 imx-ipuv3.0: IPU Warning - IPU_INT_STAT_10 = 0x00100000

imx-ipuv3 imx-ipuv3.0: IPU Warning - IPU_INT_STAT_5 = 0x88800000

handling interrupt.

Interrupt: Stopping pipeline ...

Execution ended after 2265326666 ns.

Setting pipeline to PAUSED ...

imx-ipuv3 imx-ipuv3.0: IPU Warning - IPU_INT_STAT_5 = 0x88800000

imx-ipuv3 imx-ipuv3.0: IPU Warning - IPU_INT_STAT_10 = 0x00100000

imx-ipuv3 imx-ipuv3.0: IPU Warning - IPU_INT_STAT_5 = 0x88800000

imx-ipuv3 imx-ipuv3.0: IPU Warning - IPU_INT_STAT_10 = 0x00100000

mxc_sdc_fb mxc_sdc_fb.0: timeout when waiting for flip irq

vss/mfw_gst_vss_common.c:1003 ioctl error, return -1

Setting pipeline to READY ...

Setting pipeline to NULL ...

imx-ipuv3 imx-ipuv3.0: warning: wait for bg sync eof timeout

imx-ipuv3 imx-ipuv3.0: IPU Warning - IPU_INT_STAT_5 = 0x88800000

imx-ipuv3 imx-ipuv3.0: IPU Warning - IPU_INT_STAT_10 = 0x00100000

imx-ipuv3 imx-ipuv3.0: warning: wait for bg sync eof timeout

VS0 destroyed, force=0!

hwbuf allocator zone(4718592) destroied.

Freeing pipeline ...

Labels (4)
13 Replies

2,939 Views
LeonardoSandova
Specialist I

That is correct. Non 8 pixel aligned width and height is treated as not supported format in isink plugin. BTW, have you tried this on latest BSP (4.0.0)?


There is another artifact which we are investigating and happens when displaying >1080p images on a HDMI display. Let me know if this is your test case.


Leo

2,939 Views
alokkumar
Contributor III

Hi Leo,

I think I experience both issues. I noticed a jpeg file of 3264x2448 pixel had issues in display and image was split multiple times on display. When I down sampled to 1080P, it seems to work.

I am using latest from timesys, could you please let me how to check the BSP.

0 Kudos

2,939 Views
LeonardoSandova
Specialist I

Hi Alok,

For the >1080p issue on HDMI, it is a known issue and we are working to fix it. BTW, how did you downscale the image? A pre-processing step?

Last week, a new release for MX6Q SABRE boards was delivered (3.0.35_4.0.0), so let me check with this version these two issues. I will update this thread ASAP.

Leo

0 Kudos

2,939 Views
alokkumar
Contributor III

Hi Leo,

I am surprised to see this error on a 640x480 pixel file and even the display of 640x480.

Please see the gst-launch pipeline below.

VSALPHA=1 gst-launch -v filesrc location=/home/media/newjeep.jpg ! jpegdec !im

agefreeze ! mfw_isink axis-top=600 axis-left=1200 disp-width=640 disp-height=480

MFW_GST_ISINK_PLUGIN 3.0.5 build on May 17 2013 06:52:10.

Setting pipeline to PAUSED ...

Pipeline is PREROLLING ...

/GstPipeline:pipeline0/GstJpegDec:jpegdec0.GstPad:src: caps = video/x-raw-yuv, format=(fourcc)I420, width=(int)640, height=(int)480, framerate=(fraction)0/1

hwbuf allocator zone(462848) created

/GstPipeline:pipeline0/GstImageFreeze:imagefreeze0.GstPad:src: caps = video/x-raw-yuv, format=(fourcc)I420, width=(int)640, height=(int)480, framerate=(fraction)25/1

/GstPipeline:pipeline0/GstImageFreeze:imagefreeze0.GstPad:sink: caps = video/x-raw-yuv, format=(fourcc)I420, width=(int)640, height=(int)480, framerate=(fraction)0/1

/GstPipeline:pipeline0/MfwGstISink:mfwgstisink0.GstPad:sink: caps = video/x-raw-yuv, format=(fourcc)I420, width=(int)640, height=(int)480, framerate=(fraction)25/1

Pipeline is PREROLLED ...

Setting pipeline to PLAYING ...

New clock: GstSystemClock

VS0 created. in fmt[I420] win(0,0-640,480:640x480) out win(1200,600-1840,1080:640x480)

set deinterlace mode 0

hwbuf allocator zone(614400) created

imx-ipuv3 imx-ipuv3.0: IDMAC12's EBA0 is not 8-byte aligned

imx-ipuv3 imx-ipuv3.0: IDMAC11's EBA0 is not 8-byte aligned

hwbuf allocator zone(614400) destroied.

hwbuf allocator zone(614400) created

imx-ipuv3 imx-ipuv3.0: IDMAC12's EBA0 is not 8-byte aligned

imx-ipuv3 imx-ipuv3.0: IDMAC11's EBA0 is not 8-byte aligned

hwbuf allocator zone(614400) destroied.

hwbuf allocator zone(614400) created

imx-ipuv3 imx-ipuv3.0: IDMAC12's EBA0 is not 8-byte aligned

imx-ipuv3 imx-ipuv3.0: IDMAC11's EBA0 is not 8-byte aligned

hwbuf allocator zone(614400) destroied

0 Kudos

2,939 Views
LeonardoSandova
Specialist I

Interesting. Are you still using HDMI, right? These logs do not show up when displaying on LVDS, so it may be a rescaling issue done on the IPU.

Leo

0 Kudos

2,939 Views
alokkumar
Contributor III

Yes, I am using HDMI output.

I am surprised 640x480 pixel file and hdmi display of 640x480 (part of 1080P window).

Is there any adverse performance impact of this.

Thanks

Alok

0 Kudos

2,939 Views
LeonardoSandova
Specialist I

Alok, Could you try the above patch and let me know if issues (ipu logs and wrong image display) went away?

From 6ae2813aed1063143400de8fe111a9d9a6130a4a Mon Sep 17 00:00:00 2001

From: Oliver Brown <b37094@b37094-vmlinux.(none)>

Date: Wed, 24 Jul 2013 00:20:26 -0500

Subject: [PATCH] ENGR00272541 [IPU] -  IC_RSZ_MAX_RESIZE_RATIO should be set

to 0x2000

The max resize ratio should be set to 0x2000 (or 8192).

Signed-off-by: Oliver Brown <b37094@b37094-vmlinux.(none)>

---

drivers/mxc/ipu3/ipu_regs.h |    2 +-

1 file changed, 1 insertion(+), 1 deletion(-)

mode change 100644 => 100755 drivers/mxc/ipu3/ipu_regs.h

diff --git a/drivers/mxc/ipu3/ipu_regs.h b/drivers/mxc/ipu3/ipu_regs.h

old mode 100644

new mode 100755

index 94c587e..f089f7d

--- a/drivers/mxc/ipu3/ipu_regs.h

+++ b/drivers/mxc/ipu3/ipu_regs.h

@@ -465,7 +465,7 @@ enum {

     IC_CONF_RWS_EN = 0x40000000,

     IC_CONF_CSI_MEM_WR_EN = 0x80000000,

-    IC_RSZ_MAX_RESIZE_RATIO = 0x00004000,

+    IC_RSZ_MAX_RESIZE_RATIO = 0x00002000,

     IC_IDMAC_1_CB0_BURST_16 = 0x00000001,

     IC_IDMAC_1_CB1_BURST_16 = 0x00000002,

--

1.7.9.5

Leo

2,939 Views
jojorong
Contributor IV

Hi, i met this issue also, have you fixed this issue with change sets of "LeonardoSandovalGonzalez" ?

thanks

0 Kudos

2,939 Views
XXiao1z
Contributor III

same issue persists with this patch, on 4.1.0 release with all newest patches from git.freescale.com

is this harmless or serious?

keep seeing this on serial console concerns me, but I'm not sure how bad they really are:

imx-ipuv3 imx-ipuv3.0: IDMAC21's EBA0 is not 8-byte aligned

imx-ipuv3 imx-ipuv3.0: IDMAC21's EBA1 is not 8-byte aligned

imx-ipuv3 imx-ipuv3.0: IPU Warning - IPU_INT_STAT_10 = 0x00000001

imx-ipuv3 imx-ipuv3.1: IDMAC21's EBA0 is not 8-byte aligned

imx-ipuv3 imx-ipuv3.1: IDMAC21's EBA1 is not 8-byte aligned

imx-ipuv3 imx-ipuv3.1: IPU Warning - IPU_INT_STAT_10 = 0x00000001

imx-ipuv3 imx-ipuv3.0: IPU Warning - IPU_INT_STAT_10 = 0x00100000

imx-ipuv3 imx-ipuv3.0: IPU Warning - IPU_INT_STAT_5 = 0x00800000

0 Kudos

2,939 Views
XXiao1z
Contributor III

why am I seeing ipuv3.0 and ipuv3.1 two versions?

0 Kudos

2,939 Views
LeonardoSandova
Specialist I

Hi Alok. We are investigating this issue. I will update this thread ASAP.

Leo

0 Kudos

2,939 Views
varsmolta
Contributor V

I get the same warning when I use the v4l2src plugin (not mfw_v4lsrc) when streaming from the ov5642 camera on a sabrelite (using mxc camera interface). I don't get this warning if my sink is a file. I only get it when the sink is mfw_v4lsink (i.e. display). I am running 3.0.35_1.1.0 (yocto dylan). I also don't get this issue when using the mfw_v4lsrc plugin.

root@imx6qsabrelite:~# gst-launch --gst-debug-level=2 v4l2src ! video/x-raw-yuv,width=640,height=480 ! mfw_v4lsink

this is powerful mx6q

MFW_GST_V4LSINK_PLUGIN 3.0.1 build on Mar 11 2013 10:25:17.

Setting pipeline to PAUSED ...

mx6_csi0_powerdown: powerdown=0, power_gp=0x6

0:00:00.693983318  2104    0xa4c20 WARN   x6_csi0_powerdown: powerdown=0, power_gp=0x6

m                 v4l2 gstv4l2object.c:1923:gst_v4l2_object_probe_caps_for_format:<v4l2src0> Unknown frame sizeenum type for pixelformat YUYV: 0

0:00:00.694337727  2104    0xa4c20 WARN                    v4l2 gstv4l2object.c:1939:gst_v4l2_object_probe_caps_for_format:<v4l2src0> Could not probe minimum capture size for pix

elformat YUYV

0:00:00.694483818  2104    0xa4c20 WARN                    v4l2 gstv4l2object.c:1945:gst_v4l2_object_probe_caps_for_format:<v4l2src0> Could not probe maximum capture size for pix

elformat YUYV

Pipeline is live and does not need PREROLL ...

Setting pipeline to PLAYING ...

0:00:01.528697637  2104    0xa4c20 WARN                     bin gstbin.c:2399:gst_bin_do_latency_func:<pipeline0> failed to query latency

New clock: GstSystemClock

0:00:01.596073455  2104    0xaebb0 WARN             mfw_v4lsink mfw_gst_v4lsink.c:1299:mfw_gst_v4lsink_set_format: set to YUYV mode

0:00:01.598337546  2104    0xabcf0 WARN                     bin gstbin.c:2395:gst_bin_do_latency_func:<pipeline0> did not really configure latency of 0:00:00.010000000

full screen size:1280x720

0:00:01.599081909  2104    0xabcf0 WARN             mfw_v4lsink mfw_gst_v4l.c:1445:mfw_gst_v4l2_display_init: Wrong display width information

0:00:01.599226182  2104    0xabcf0 WARN             mfw_v4lsink mfw_gst_v4l.c:1449:mfw_gst_v4l2_display_init: Wrong display height information

[V4L Upimx-ipuv3 imx-ipuv3.0: IDMAC12's EBA0 is not 8-byte aligned

date Display]: left=0, top=0, width=1280, height=720

0:00:01.600163955  2104    0xaebb0 WARN             mfw_v4lsink mfw_gst_v4lsink.c:1299:mfw_gst_v4lsink_set_imx-ipuv3 imx-ipuv3.0: IDMAC12's EBA0 is not 8-byte aligned

format: set to YUYV mode

full screen size:1280x720

0:00:01.600591409  2104    0xaebb0 WARN             mfw_v4lsink mfw_gst_v4imx-ipuv3 imx-ipuv3.0: IDMAC12's EBA0 is not 8-byte aligned

l.c:1445:mfw_gst_v4l2_display_init: Wrong display width information

0:00:01.600704545  2104    0xaebb0 WARN             mfw_v4lsink mfw_gst_v4l.c:1449:mfw_gst_v4l2_display_init: Wrong display height information

>>V4L_SINK: Actually buffer status:

        hardware buffer : 12

        software buffer : 0

imx-ipuv3 imx-ipuv3.0: IDMAC12's EBA0 is not 8-byte aligned

imx-ipuv3 imx-ipuv3.0: IDMAC12's EBA0 is not 8-byte aligned

imx-ipuv3 imx-ipuv3.0: IDMAC12's EBA0 is not 8-byte aligned

imx-ipuv3 imx-ipuv3.0: IDMAC12's EBA0 is not 8-byte aligned

imx-ipuv3 imx-ipuv3.0: IDMAC12's EBA0 is not 8-byte aligned

imx-ipuv3 imx-ipuv3.0: IDMAC12's EBA0 is not 8-byte aligned

imx-ipuv3 imx-ipuv3.0: IDMAC12's EBA0 is not 8-byte aligned

imx-ipuv3 imx-ipuv3.0: IDMAC12's EBA0 is not 8-byte aligned

imx-ipuv3 imx-ipuv3.0: IDMAC12's EBA0 is not 8-byte aligned

imx-ipuv3 imx-ipuv3.0: IDMAC12's EBA0 is not 8-byte aligned

0 Kudos

2,939 Views
alokkumar
Contributor III

newjeep.jpg

Image for the earlier post is attached.

0 Kudos