From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Problem with attaching UBI partition
Date: Tue, 1 Mar 2016 08:23:49 +0100 [thread overview]
Message-ID: <56D54385.80602@denx.de> (raw)
In-Reply-To: <1456815184.2100.5.camel@altera.com>
On 01.03.2016 07:53, Chin Liang See wrote:
> On Mon, 2016-02-29 at 23:55 +0100, Marek Vasut wrote:
>> On 02/24/2016 09:59 AM, Bakhvalov, Denis (Nokia - PL/Wroclaw) wrote:
>>> Hello Heiko,
>>>
>>>> Which U-Boot version? Which board?
>>>
>>> This is U-Boot v2016.03-rc1. I have custom board with socfpga
>>> Arria5
>>> onboard.
>>>
>>>> Where does this leading 0xff come from? There seems a problem
>>>> with
>>>> your spi nor flash driver?
>>>
>>> Yes, you're right. I have problems with the driver. As I mentioned
>>> in
>>> previous mail when I read the contents from the flash some data is
>>> corrupted.
>>>
>>> How to find out if the problem is because U-Boot has no support for
>>> my flash (Spansion S25FL512S NOR flash with SPI) or I have not
>>> proper
>>> configured SPI in U-Boot?
>>
>> I believe there is a problem with caches , which we still didn't
>> identify. CCing Dinh and Chin, as they were the last ones looking
>> into this problem.
>>
>> For now, try doing "dcache off" before using the QSPI NOR.
>>
>
> We managed to get it work for socfpga. One of the issue dragged me long
> is the CONFIG_SPI_FLASH_USE_4K_SECTORS. Need to ensure its not defined
> in the defconfig. Hope it helps
This is not clear to me. You mean you were able to reproduce and
solve this cache (S-bit) related issue by disabling
CONFIG_SPI_FLASH_USE_4K_SECTORS? This option is disabled for all
SoCFPGA board in mainline.
Could you please explain in more details what exactly you did to
solve this issue on SPI NOR?
Thanks,
Stefan
next prev parent reply other threads:[~2016-03-01 7:23 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-22 14:17 [U-Boot] Problem with attaching UBI partition Bakhvalov, Denis
2016-02-23 18:11 ` Heiko Schocher
2016-02-24 8:59 ` Bakhvalov, Denis
2016-02-29 6:36 ` Heiko Schocher
2016-02-29 6:47 ` Jagan Teki
2016-02-29 16:44 ` Bakhvalov, Denis
2016-02-29 17:17 ` Jagan Teki
2016-02-29 22:44 ` Marek Vasut
2016-03-01 13:04 ` Bakhvalov, Denis
2016-03-01 13:32 ` Jagan Teki
2016-03-01 13:53 ` Bakhvalov, Denis
2016-03-01 13:58 ` Marek Vasut
2016-03-04 9:03 ` Bakhvalov, Denis
2016-03-04 12:20 ` Marek Vasut
2016-03-04 12:24 ` Bakhvalov, Denis
2016-03-04 12:28 ` Marek Vasut
2016-03-22 13:18 ` Bakhvalov, Denis
2016-03-22 14:24 ` Marek Vasut
2016-03-01 13:46 ` Marek Vasut
2016-02-29 22:55 ` Marek Vasut
2016-03-01 6:53 ` Chin Liang See
2016-03-01 7:23 ` Stefan Roese [this message]
2016-03-01 13:38 ` Chin Liang See
2016-03-01 15:35 ` Stefan Roese
2016-03-02 12:24 ` Chin Liang See
2016-03-03 11:51 ` Stefan Roese
2016-03-03 12:43 ` Marek Vasut
-- strict thread matches above, loose matches on Subject: below --
2016-02-23 13:31 Bakhvalov, Denis
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=56D54385.80602@denx.de \
--to=sr@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