public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] FPGA detection failure on Cyclone V soc development kit
Date: Mon, 1 Feb 2016 23:50:45 +0100	[thread overview]
Message-ID: <201602012350.45798.marex@denx.de> (raw)
In-Reply-To: <56AFDB6A.3000309@opensource.altera.com>

On Monday, February 01, 2016 at 11:25:46 PM, Dinh Nguyen wrote:
> On 01/22/2016 10:35 AM, Dinh Nguyen wrote:
> > On 01/21/2016 10:31 AM, Marek Vasut wrote:
> >> On Thursday, January 21, 2016 at 05:20:33 PM, M?ns Rullg?rd wrote:
> >>> Tom Rini <trini@konsulko.com> writes:
> >>>> On Wed, Jan 20, 2016 at 08:31:30PM +0000, M?ns Rullg?rd wrote:
> >>>>> I'm having a problem with u-boot 2016.01 failing to detect the FPGA
> >>>>> on my Altera Cyclone V SoC Development Kit.  On startup, it simply
> >>>>> prints "FPGA: Not Altera chip ID" (the ID having been read as
> >>>>> all-zero).  No amount of messing with jumpers or switches makes a
> >>>>> difference.  The software on the SD card included in the box appears
> >>>>> to work, so on a whim I took the SPL pre-loader from this card and
> >>>>> combined it with the main 2016.01 u-boot.  This makes the detection
> >>>>> succeed, despite Marek baulking at this idea.  The "good" SPL
> >>>>> identifies as "U-Boot SPL 2013.01.01 (Dec 04 2014 - 08:59:41)" which
> >>>>> is a different build date than the main u-boot on the same SD card,
> >>>>> so which source code version it was built from is anyone's guess.
> >>>>> 
> >>>>> What's interesting is that Marek's board works with u-boot 2016.01
> >>>>> while mine fails even with the very same binary.  The boards are
> >>>>> different revisions (his 100-0321003-C1, mine -E1), and the main
> >>>>> Cyclone V chips are also different (his 5CSXFC6D6F31C8NES, mine
> >>>>> 5CSXFC6D6F31C6N).
> >>>>> 
> >>>>> Any suggestions for what to try next?
> >>>> 
> >>>> v2016.01 release or to of tree?  If top of tree, try
> >>>> http://patchwork.ozlabs.org/patch/570009/
> >>> 
> >>> Tried release, top of tree, and top of tree with that patch.  Nothing
> >>> works.
> >> 
> >> btw. you dropped Dinh from the CC .
> > 
> > Sorry, but I haven't had a chance to take a look at this. I'll try to
> > looking this in the following week.
> 
> It seems to work on older Cyclone V chips. I have the latest devkit,
> which has the 5CSXFC6D6F31C6N chip, and I cannot get an FPGA ID. My
> older devkit has a 5CSXFC6D6F31C8NES chip, and I can get the FPGA's ID.

This indeed matches my observations. My CV SoCDK also has an older chip,
ES even, and I can detect the FPGA ID.

> I'll have ask around on what changes were done with the later Cyclone V
> chips.

Thanks!

Best regards,
Marek Vasut

      reply	other threads:[~2016-02-01 22:50 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-20 20:31 [U-Boot] FPGA detection failure on Cyclone V soc development kit Måns Rullgård
2016-01-21 16:18 ` Tom Rini
2016-01-21 16:20   ` Måns Rullgård
2016-01-21 16:31     ` Marek Vasut
2016-01-22 16:35       ` Dinh Nguyen
2016-01-27 13:34         ` Chin Liang See
2016-01-27 13:46           ` Måns Rullgård
2016-01-27 14:16             ` Chin Liang See
2016-01-27 14:18               ` Måns Rullgård
2016-01-27 14:20                 ` Chin Liang See
2016-04-06 15:07                 ` Marek Vasut
2016-04-06 15:29                   ` Dinh Nguyen
2016-04-06 16:48                     ` Marek Vasut
2016-04-06 17:16                       ` Måns Rullgård
2016-04-06 19:28                         ` Marek Vasut
2016-04-12 13:54                           ` Dinh Nguyen
2016-04-12 14:00                             ` Marek Vasut
2016-04-12 14:17                               ` Dinh Nguyen
2016-04-12 14:21                                 ` Marek Vasut
2016-04-06 16:06                   ` Phil Reid
2016-02-01 22:25         ` Dinh Nguyen
2016-02-01 22:50           ` Marek Vasut [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201602012350.45798.marex@denx.de \
    --to=marex@denx.de \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox