public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Dinh Nguyen <dinguyen@kernel.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] socfpga 2016.05, CV socdk Rev E1, SPL and u-boot fail when booting from QSPI
Date: Fri, 17 Jun 2016 11:45:39 -0500	[thread overview]
Message-ID: <57642933.4060806@kernel.org> (raw)
In-Reply-To: <AM4PR0401MB2369B99686291532068A0859C4570@AM4PR0401MB2369.eurprd04.prod.outlook.com>

Trying to respond inline:

On 06/17/2016 09:39 AM, Christian Didriksson wrote:
> Hi Marek,
> 
> I applied the two patches you suggested, but got no change in behavior:
> 
> U-Boot SPL 2016.05-ga0bd0e7-dirty (Jun 17 2016 - 16:32:35)
> drivers/ddr/altera/sequencer.c: Preparing to start memory calibration
> drivers/ddr/altera/sequencer.c: CALIBRATION PASSED
> drivers/ddr/altera/sequencer.c: Calibration complete
> Trying to boot from SPI
> 
> 

I haven't tested on QSPI. I tested my patch on a board with SD/MMC. I'll
check it on a QSPI board shortly.

> U-Boot 2016.05-ga0bd0e7-dirty (Jun 17 2016 - 16:32:35 +0200)
> 
> CPU:   Altera SoCFPGA Platform
> FPGA:  Altera Cyclone V, SE/A6 or SX/C6 or ST/D6, version 0x0
> BOOT:  QSPI Flash (1.8V)
>        Watchdog enabled
> I2C:   ready
> DRAM:  1 GiB
> 
> Best regards,
> 
> Christian
> 
>> On 06/16/2016 12:13 PM, Christian Didriksson wrote:
>>> Hi!
>>
>> Hi,
>>
>>>> On 06/15/2016 12:06 PM, Christian Didriksson wrote:
>>>>> Trying again.
>>>>
>>>> Hi!
>>>>
>>>>> I have reverted back to a vanilla u-boot-2016.05, added the
>>>>> not-enter-quad-mode patch
>>>>
>>>> What's this patch ? Can you share it ?
>>
>> [...]
>>
>> Thanks
>>
>>> Some comments:
>>>
>>> We want to run ECC, but I don't think the SPL supports scrubbing etc. yet so
>> I undefined those qts-parameters. Am I right regarding ECC for SDRAM?
>>

Yes, in order for ECC, you need to scrub the SDRAM. I'll look to see
what is needed.

Dinh

  parent reply	other threads:[~2016-06-17 16:45 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-09 18:15 [U-Boot] socfpga 2016.05, CV socdk Rev E1, SPL and u-boot fail when booting from QSPI Christian Didriksson
2016-06-15 10:06 ` Christian Didriksson
2016-06-15 22:36   ` Marek Vasut
2016-06-16 10:13     ` Christian Didriksson
2016-06-16 13:32       ` Marek Vasut
2016-06-17 14:39         ` Christian Didriksson
2016-06-17 14:48           ` Marek Vasut
2016-06-20 13:22             ` Christian Didriksson
2016-06-20 13:43               ` Marek Vasut
2016-06-20 16:04                 ` Christian Didriksson
2016-06-20 20:22                   ` Marek Vasut
2016-06-21  7:32                     ` Christian Didriksson
2016-06-29  7:03                   ` Pavel Machek
2016-06-17 16:45           ` Dinh Nguyen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-06-21 15:30 Christian Didriksson
2016-06-21 17:07 ` Marek Vasut
2016-06-21 19:22   ` Christian Didriksson
2016-06-22 16:37     ` Christian Didriksson
2016-06-23 13:07       ` Marek Vasut
2016-06-23 15:58         ` Sylvain Lesne
2016-06-23 16:14           ` Marek Vasut
2016-06-23 16:31             ` Sylvain Lesne
2016-06-23 18:42               ` Marek Vasut
2016-06-27  9:10                 ` Christian Didriksson
2016-06-27  9:38                   ` Sylvain Lesne
2016-06-27 10:43                     ` Christian Didriksson

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=57642933.4060806@kernel.org \
    --to=dinguyen@kernel.org \
    --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