From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id DF8F7E0073A; Fri, 23 May 2014 17:18:17 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=0.6 required=5.0 tests=RCVD_IN_DNSWL_LOW,RDNS_NONE autolearn=no version=3.3.1 X-Spam-HAM-Report: * -0.7 RCVD_IN_DNSWL_LOW RBL: Sender listed at http://www.dnswl.org/, low * trust * [209.85.220.45 listed in list.dnswl.org] * 1.3 RDNS_NONE Delivered to internal network by a host with no rDNS Received: from mail-pa0-f45.google.com (unknown [209.85.220.45]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 7C47AE00716 for ; Fri, 23 May 2014 17:18:15 -0700 (PDT) Received: by mail-pa0-f45.google.com with SMTP id ey11so4780169pad.18 for ; Fri, 23 May 2014 17:18:15 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=hwUO/SRbIWHTJzhIfrN/RNj15ZrE0+lXHhll+APlQVU=; b=Xe0CzbfvIgEi6lZoXfGrFZbPFYsMeUeDb4B6IzTaydM/Wt/bdnyER1X8Rtxav401r9 bnCvBpbzqwxetUPIxJkR9Jf2vFNtMDqvqe8vgRzmEGYzpMWHHAOvAMwBKyq5CTBY/ylT CycOkGtq3A/kqbMJphVT3RCBZU2jg8+XkZc0UwsT6R96SoECN++hoUEV0N4++rXmlugJ qhcgb49UxU5Vz63fpUlqs4GWQUvQ9gjpRyet7LJgd5z4nmwCYUD9eJQJbh2wBGV0tNL9 wEKUz0vnPcUAj22k8pVoDiyGO3UKqOnNLYG/VuUyCbdUUsGfBCY8TtiZFT6NrZimzn8+ T6Og== X-Gm-Message-State: ALoCoQl08O5maHvSabDpJW5Qi1deoyuJGQdw3PbvxzGqvcOaXafMUah51SQnBohpP2mB0/ST1TPc X-Received: by 10.66.243.225 with SMTP id xb1mr10176407pac.49.1400890695352; Fri, 23 May 2014 17:18:15 -0700 (PDT) Received: from [192.168.0.124] ([63.226.49.26]) by mx.google.com with ESMTPSA id as12sm20639620pac.43.2014.05.23.17.18.13 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 23 May 2014 17:18:14 -0700 (PDT) Message-ID: <537FE543.10108@boundarydevices.com> Date: Fri, 23 May 2014 17:18:11 -0700 From: Eric Nelson User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: Otavio Salvador , Peter Bergin References: <43F0718C449F6A46B393DA2BEC8E01280C4F2C34@post.tritech.se> In-Reply-To: Cc: "meta-freescale@yoctoproject.org" Subject: Re: No HDMI signal from Nitrogen6x board with daisy X-BeenThere: meta-freescale@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Usage and development list for the meta-fsl-* layers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 May 2014 00:18:17 -0000 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Hello Peter, On 05/23/2014 05:16 AM, Otavio Salvador wrote: > > On Fri, May 23, 2014 at 4:23 AM, Peter Bergin > wrote: > > I have trouble with my Nitrogen6x board after upgrade to daisy > build. I can not get any HDMI signal out of the board after boot. > During boot u-boot can show content on screen but when booted the > monitor does not detect the signal. > > I have updated to u-boot 2014.04. I have tried with the pre-built > image found at Boundary Devices with same result as my own build. > This is not likely to be a U-Boot level thing. > I see this printout on the console after boot: > mxc_sdc_fb fb.27: timeout when waiting for flip irq > mxc_sdc_fb fb.27: MXCFB_WAIT_FOR_VSYNC: timeout 0 > mxc_sdc_fb fb.27: timeout when waiting for flip irq > mxc_sdc_fb fb.27: MXCFB_WAIT_FOR_VSYNC: timeout 0 > mxc_sdc_fb fb.27: timeout when waiting for flip irq > mxc_sdc_fb fb.27: MXCFB_WAIT_FOR_VSYNC: timeout 0 > > I have also posted a, still unanswered, question on the Freescale > community page (https://community.freescale.com/message/405002). > I saw that post, but have been struggling to find time to reproduce it. A nominal build of Daisy/fsl-image-machine-test just seemed to work for me at 1080P60. Are you also running 1080P (i.e. with a custom boot script)? Can you forward the content of /proc/cmdline? > Any help is really appreciated! Any ideas? > > I think it might be your monitor do not support the frequency it is using. > If your monitor supports EDID, you should be able to tell by looking in sysfs: # cat /sys/class/graphics/fb0/mode ... currently negotiated mode here # cat /sys/class/graphics/fb0/modes ... list of supported modes should be here > I am adding Eric in Cc so he can comment on this. > I'm afraid I have more questions than advice. Can you tell me more about what image you're running? Is it based on X, DFB, Wayland? Do you see the penguins during Linux boot? Please advise, Eric