Wrong SPI NOR model detected by mx6sl

[Fabio Estevam]

Hi Huang,

On Thu, Apr 10, 2014 at 9:26 PM, Huang Shijie <shijie8 at gmail.com> wrote:
> On Thu, Apr 10, 2014 at 02:16:49PM -0300, Fabio Estevam wrote:
>> Hi Marek,
>>
>> On Thu, Apr 10, 2014 at 1:07 PM, Marek Vasut <marex at denx.de> wrote:
>>
>> > Can you share the JEDEC ID codes that both of the boards actually read from the
>> > SPI NOR ? You can dump those in the m25p80.c driver . That'd be helpful, I
>> > suspect some kind of an "offset" or "polarity inversion" in the SPI
>> > communication causing this.
>>
>> On mx6qsabresd:
>>
>> m25p80 spi0.0: JEDEC id: 0x202016
>> m25p80 spi0.0: m25p32 (4096 Kbytes)
>>
>> On mx6sl-evk:
>>
>> m25p80 spi0.0: JEDEC id: 0x000000
> It seems the kernel can not read out anything from the NOR.
> Please check the pinctrl or the schematic.

I also tried FSL 3.10 kernel and U-boot and also get 0x0000 as JEDEC
response on these cases.

Regards,

Fabio Estevam