From: Alexander Stein <alexander.stein@systec-electronic.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/1] fsl_qspi: Pet the watchdog while reading/writing
Date: Wed, 25 Nov 2015 10:33:53 +0100 [thread overview]
Message-ID: <2770916.foob3x5q7r@ws-stein> (raw)
In-Reply-To: <BN3PR0301MB08678AD934C426B186439334FE050@BN3PR0301MB0867.namprd03.prod.outlook.com>
On Wednesday 25 November 2015 02:20:53, Huan Wang wrote:
> [Alison Wang] I didn't meet any issue when using sf commands to write and
> read the serial flash.
>
> Hi, Alexander,
>
> Could you show me the detail commands and process when you meet
> such issue? Then I can try to reproduce on my board.
Yep, here is the output:
> U-Boot 2015.01-00671-g78773b9 (Nov 25 2015 - 10:28:50)
>
> CPU: Freescale LayerScape LS1021E, Version: 2.0, (0x87081120)
>
> Clock Configuration:
> CPU0(ARMV7):960 MHz,
> Bus:288 MHz, DDR:800 MHz (1600 MT/s data rate),
> Reset Configuration Word (RCW):
> 00000000: 0608000a 00000000 00000000 00000000
> 00000010: 70000000 08407922 40000a00 21046000
> 00000020: 00000000 00000000 00000000 0021ef00
> 00000030: 20024800 0888f340 00000000 00000000
> QSPI
> Watchdog enabled
> I2C: ready
> DRAM: Initializing DDR....
> Detected UDIMM Fixed DDR on board
> 512 MiB (DDR3, 16-bit, CL=11, ECC off)
> Using SERDES1 Protocol: 112 (0x70)
> MMC: FSL_SDHC: 0
> SF: Detected S25FL512S_256K with page size 512 Bytes, erase size 256 KiB,
> In: serial
> Out: serial
> Err: serial
> SF: Detected S25FL512S_256K with page size 512 Bytes, erase size 256 KiB,
> total 64 MiB SF: 262144 bytes @ 0x180000 Read: OK
> Firmware 'Microcode version 0.0.1 for LS1021a r1.0' for 1021 V1.0
> QE: uploading microcode 'Microcode for LS1021a r1.0' version 0.0.1
> SCSI: Net: eTSEC2 is in sgmii mode.
> eTSEC1 [PRIME], eTSEC2
> Hit any key to stop autoboot: 0
> => sf read 0x81040000 0x200000 0x400000
>
>
> U-Boot 2015.01-00671-g78773b9 (Nov 25 2015 - 10:28:50)
>
> CPU: Freescale LayerScape LS1021E, Version: 2.0, (0x87081120)
>
> Clock Configuration:
> CPU0(ARMV7):960 MHz,
> Bus:288 MHz, DDR:800 MHz (1600 MT/s data rate),
> Reset Configuration Word (RCW):
> 00000000: 0608000a 00000000 00000000 00000000
> 00000010: 70000000 08407922 40000a00 21046000
> 00000020: 00000000 00000000 00000000 0021ef00
> 00000030: 20024800 0888f340 00000000 00000000
> QSPI
> Watchdog enabled
> I2C: ready
> DRAM: Initializing DDR....
> Detected UDIMM Fixed DDR on board
> [...]
and so on...
The actual command which results in a watchdog reset is 'sf read 0x81040000 0x200000 0x400000'. Please note that this uses an external watchdog which is enabled by default and resets after ~1.5s. The command itself takes about 2s (taken from my watch).
Best regards,
Alexander
--
Dipl.-Inf. Alexander Stein
SYS TEC electronic GmbH
alexander.stein at systec-electronic.com
Legal and Commercial Address:
Am Windrad 2
08468 Heinsdorfergrund
Germany
Office: +49 (0) 3765 38600-0
Fax: +49 (0) 3765 38600-4100
Managing Directors:
Director Technology/CEO: Dipl.-Phys. Siegmar Schmidt;
Director Commercial Affairs/COO: Dipl. Ing. (FH) Armin von Collrepp
Commercial Registry:
Amtsgericht Chemnitz, HRB 28082; USt.-Id Nr. DE150534010
next prev parent reply other threads:[~2015-11-25 9:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-04 8:19 [U-Boot] [PATCH 1/1] fsl_qspi: Pet the watchdog while reading/writing Alexander Stein
2015-11-23 18:51 ` York Sun
2015-11-24 7:19 ` Alexander Stein
2015-11-24 20:44 ` York Sun
2015-11-25 2:20 ` Huan Wang
2015-11-25 9:33 ` Alexander Stein [this message]
2015-12-03 9:49 ` Huan Wang
2015-12-03 10:04 ` Alexander Stein
2015-12-04 1:38 ` Huan Wang
2015-12-03 16:06 ` York Sun
2015-12-04 1:56 ` Huan Wang
2015-12-04 20:10 ` York Sun
2015-12-07 6:39 ` Alexander Stein
2015-12-02 17:49 ` York Sun
2015-12-04 20:54 ` Fabio Estevam
2015-12-04 21:00 ` York Sun
2015-12-07 6:35 ` Alexander Stein
2015-12-15 1:06 ` York Sun
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=2770916.foob3x5q7r@ws-stein \
--to=alexander.stein@systec-electronic.com \
--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