public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Problem with attaching UBI partition
Date: Thu, 3 Mar 2016 12:51:16 +0100	[thread overview]
Message-ID: <56D82534.1060504@denx.de> (raw)
In-Reply-To: <1456921453.2086.4.camel@altera.com>

Hi Chin Liang,

On 02.03.2016 13:24, Chin Liang See wrote:
>> On 01.03.2016 14:38, Chin Liang See wrote:
>>> On Tue, 2016-03-01 at 08:23 +0100, Stefan Roese wrote:
>>>> 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?
>>>>
>>>
>>> Nope, I am not replicating the issue. My board is having Micron
>>> instead
>>> of Spansion flash. In previously, CONFIG_SPI_FLASH_USE_4K_SECTORS
>>> is
>>> defined in socfpga as most serial NOR flash are supporting 4k sub
>>> sector. With that, it would be good to ensure the 4K is undefined.
>>>
>>> In this case, wonder any details on the failure? Intermittent?
>>
>> I think we are talking about different things here. I'm referring
>> to Marek mentioning the cache problem (S-bit related) on current
>> SoCFPGA U-Boot mainline. With caches enabled you can experience
>> problems on QSPI and on USB (reported from Marek - I didn't test
>> USB yet).
>>
> 
> For QSPI, wonder the issue is on the read or write?

I'm not 100% sure here if this never happens on read. But it definitely
happens on write. saveeenv to SPI NOR causes serious problems here
for example.
 
>> So do you have any updated on this cache / S-bit problem?
> 
> I am still debugging this as I notice the hub is not able to detect the
> mass storage. This is only for certain pen drive.
> 
>> Or can you
>> use QSPI NOR without any issues on current mainline U-Boot with
>> caches enabled on your platforms?
>>
> 
> The issue I have is on USB only. For NOR, I can ubifsmount and
> ubifsload with Micron NOR flash without issue. This is with dcache
> enabled

Strange. I have Micron here on the SR1500 as well:

=> sf probe     
SF: Detected N25Q128 with page size 256 Bytes, erase size 64 KiB, total 16 MiB

Thanks,
Stefan

  reply	other threads:[~2016-03-03 11:51 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
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 [this message]
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=56D82534.1060504@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