On 2014-12-02 06:21, Gary Thomas wrote:
On 2014-11-26 17:26, Gary Thomas wrote:
On 2014-11-26 12:26, Eric Nelson wrote:
Hi Gary,

On 11/26/2014 11:10 AM, Gary Thomas wrote:
On 2014-11-26 11:06, Gary Thomas wrote:
On 2014-11-23 18:57, Eric Nelson wrote:
This patch adds support for the 3.10.31_1.1.0_beta kernelfor Boundary
Devices BD-SL-i.MX6 (built to SABRE Lite), Nitrogen6X, Nitrogen6_Max
and and Nitrogen6_Lite boards.

To try it out, set PREFERRED_VERSION_linux-boundary = "3.10.31" in your
local.conf file.

Minimal testing has been performed at this point, so don't expect it
to be production-ready.

Note that the 3.10.31 kernel contains an update to provide fixed
numbering for /dev/mmcblk devices instead of numbering them by
order of initialization.

Support has been added into the boot script, but requires setting
a variable in U-Boot:

     U-Boot > setenv sdphys 1
     U-Boot > saveenv
     U-Boot > boot

See this post for some additional commentary:
     http://boundarydevices.com/root-equals

Signed-off-by: Eric Nelson <[email protected]>

When I tried this patchset, it fails to boot my SabreLite.  The
important bits seem to be the MMC device numbering.  From the boot log:
      <snip>
    mmc3: new high speed SDHC card at address aaaa
    mmcblk3: mmc3:aaaa SU04G 3.69 GiB
     mmcblk3: p1 p2
      <snip>
    ALSA device list:
      #0: imx6q-sabrelite-sgtl5000
    Waiting for root device /dev/mmcblk0p2...

I see no difference when setting 'sdphys' or not.  Perhaps I missed some
other patch (like to the boot scripts)?

BTW, I'm building the scripts from
u-boot-script-boundary/v2014.07+gitAUTOINC+f870252376
and there seems to be nothing in there about sdphys

You need this patch to support the 'sdphys' thing in the boot script:
    http://patches.openembedded.org/patch/83731/

Thanks, I had missed that one.  It's booting again.

Next problem - I have no video, neither with HDMI nor 7" LCD
Ideas?


Any progress with this (no video at all)?  I've tried the
latest Boundary Devices kernel (b76cf1c04) whose comment
implies this should be fixed, but still no-go.


For completeness, here are some relevant messages at boot:

Kernel command line: enable_wait_mode=off 
video=mxcfb0:dev=hdmi,1280x720M@60,if=RGB24 video=mxcfb1:dev=lcd,CLAA-WVGA,if=R
GB666 video=mxcfb2:off video=mxcfb3:off fbmem=28M,10M console=ttymxc1,115200 
vmalloc=400M consoleblank=0 rootwait root=/d
ev/mmcblk3p2 mxc_hdmi.only_cea=1

mxc_hdmi 20e0000.hdmi_video: Detected HDMI controller 0x13:0xa:0xa0:0xc1
fbcvt: 1280x720@60: CVT Name - .921M9
mxc_sdc_fb fb.27: registered mxc display driver hdmi
mxc_sdc_fb fb.27: 1280x720 h_sync,r,l: 40,110,220  v_sync,l,u: 5,5,20 
pixclock=74250000 Hz
imx-ipuv3 2800000.ipu: try ipu internal clk
imx-ipuv3 2800000.ipu: disp=0, pixel_clk=74250000 74250000 parent=74250000 div=1
imx-ipuv3 2800000.ipu: IPU DMFC DP HIGH RESOLUTION: 1(0,1), 5B(2~5), 5F(6,7)
imx-ipuv3 2800000.ipu: IPU Warning - IPU_INT_STAT_10 = 0x00080000
imx-ipuv3 2800000.ipu: IPU Warning - IPU_INT_STAT_10 = 0x00080000
mxc_sdc_fb fb.27: 1280x720 h_sync,r,l: 40,110,220  v_sync,l,u: 5,5,20 
pixclock=74250000 Hz
imx-ipuv3 2800000.ipu: try ipu internal clk
imx-ipuv3 2800000.ipu: disp=0, pixel_clk=74250000 74250000 parent=74250000 div=1
Console: switching to colour frame buffer device 160x45
imx-ipuv3 2800000.ipu: IPU Warning - IPU_INT_STAT_5 = 0x00800000
mxc_sdc_fb fb.27: timeout when waiting for flip irq
mxc_sdc_fb fb.28: NO mxc display driver found!
mxc_sdc_fb fb.29: mxcfb2 is turned off!
mxc_sdc_fb fb.30: mxcfb3 is turned off!

--
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------
--
_______________________________________________
meta-freescale mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/meta-freescale

Reply via email to