* Wrong SPI NOR model detected by mx6sl
@ 2014-04-10 15:49 Fabio Estevam
2014-04-10 16:07 ` Marek Vasut
0 siblings, 1 reply; 9+ messages in thread
From: Fabio Estevam @ 2014-04-10 15:49 UTC (permalink / raw)
To: linux-arm-kernel
Hi,
On the imx6sl-evk there is a m25p32 spi nor flash, but in the kernel
probe we get:
m25p80 spi0.0: found mr25h256, expected m25p32
m25p80 spi0.0: mr25h256 (32 Kbytes)
On the mx6qsabresd there is also a m25p32, which is correctly detected:
m25p80 spi0.0: m25p32 (4096 Kbytes)
Any ideas as to why mx6sl detects the wrong spi nor model?
Regards,
Fabio Estevam
^ permalink raw reply [flat|nested] 9+ messages in thread
* Wrong SPI NOR model detected by mx6sl
2014-04-10 15:49 Wrong SPI NOR model detected by mx6sl Fabio Estevam
@ 2014-04-10 16:07 ` Marek Vasut
2014-04-10 17:16 ` Fabio Estevam
0 siblings, 1 reply; 9+ messages in thread
From: Marek Vasut @ 2014-04-10 16:07 UTC (permalink / raw)
To: linux-arm-kernel
On Thursday, April 10, 2014 at 05:49:18 PM, Fabio Estevam wrote:
> Hi,
>
> On the imx6sl-evk there is a m25p32 spi nor flash, but in the kernel
> probe we get:
>
> m25p80 spi0.0: found mr25h256, expected m25p32
> m25p80 spi0.0: mr25h256 (32 Kbytes)
>
> On the mx6qsabresd there is also a m25p32, which is correctly detected:
> m25p80 spi0.0: m25p32 (4096 Kbytes)
>
> Any ideas as to why mx6sl detects the wrong spi nor model?
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.
Best regards,
Marek Vasut
^ permalink raw reply [flat|nested] 9+ messages in thread
* Wrong SPI NOR model detected by mx6sl
2014-04-10 16:07 ` Marek Vasut
@ 2014-04-10 17:16 ` Fabio Estevam
2014-04-11 0:26 ` Huang Shijie
0 siblings, 1 reply; 9+ messages in thread
From: Fabio Estevam @ 2014-04-10 17:16 UTC (permalink / raw)
To: linux-arm-kernel
Hi Marek,
On Thu, Apr 10, 2014 at 1:07 PM, Marek Vasut <marex@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
m25p80 spi0.0: found mr25h256, expected m25p32
m25p80 spi0.0: mr25h256 (32 Kbytes)
Will need to dump the SPI registers to understand why mx6sl behaves like this.
Thanks,
Fabio Estevam
^ permalink raw reply [flat|nested] 9+ messages in thread
* Wrong SPI NOR model detected by mx6sl
2014-04-10 17:16 ` Fabio Estevam
@ 2014-04-11 0:26 ` Huang Shijie
2014-04-11 2:09 ` Fabio Estevam
2014-04-11 11:43 ` Fabio Estevam
0 siblings, 2 replies; 9+ messages in thread
From: Huang Shijie @ 2014-04-11 0:26 UTC (permalink / raw)
To: linux-arm-kernel
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@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.
> m25p80 spi0.0: found mr25h256, expected m25p32
> m25p80 spi0.0: mr25h256 (32 Kbytes)
>
> Will need to dump the SPI registers to understand why mx6sl behaves like this.
i am not in the office today, else i can test the imx6sl-evk.
thanks
Huang Shijie
^ permalink raw reply [flat|nested] 9+ messages in thread
* Wrong SPI NOR model detected by mx6sl
2014-04-11 0:26 ` Huang Shijie
@ 2014-04-11 2:09 ` Fabio Estevam
2014-04-11 11:43 ` Fabio Estevam
1 sibling, 0 replies; 9+ messages in thread
From: Fabio Estevam @ 2014-04-11 2:09 UTC (permalink / raw)
To: linux-arm-kernel
Hi Huang,
On Thu, Apr 10, 2014 at 9:26 PM, Huang Shijie <shijie8@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@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
^ permalink raw reply [flat|nested] 9+ messages in thread
* Wrong SPI NOR model detected by mx6sl
2014-04-11 0:26 ` Huang Shijie
2014-04-11 2:09 ` Fabio Estevam
@ 2014-04-11 11:43 ` Fabio Estevam
2014-04-11 11:59 ` Marek Vasut
1 sibling, 1 reply; 9+ messages in thread
From: Fabio Estevam @ 2014-04-11 11:43 UTC (permalink / raw)
To: linux-arm-kernel
On Thu, Apr 10, 2014 at 9:26 PM, Huang Shijie <shijie8@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@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.
Yes, there was a pinmux issue in U-boot and I have fixed it.
SPI NOR is properly detected in U-boot and kernel now.
Regards,
Fabio Estevam
^ permalink raw reply [flat|nested] 9+ messages in thread
* Wrong SPI NOR model detected by mx6sl
2014-04-11 11:43 ` Fabio Estevam
@ 2014-04-11 11:59 ` Marek Vasut
2014-04-11 12:11 ` Fabio Estevam
0 siblings, 1 reply; 9+ messages in thread
From: Marek Vasut @ 2014-04-11 11:59 UTC (permalink / raw)
To: linux-arm-kernel
On Friday, April 11, 2014 at 01:43:50 PM, Fabio Estevam wrote:
> On Thu, Apr 10, 2014 at 9:26 PM, Huang Shijie <shijie8@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@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.
>
> Yes, there was a pinmux issue in U-boot and I have fixed it.
>
> SPI NOR is properly detected in U-boot and kernel now.
This means there's also a pinmux issue in kernel, did you fix it in kernel as
well please ?
Best regards,
Marek Vasut
^ permalink raw reply [flat|nested] 9+ messages in thread
* Wrong SPI NOR model detected by mx6sl
2014-04-11 11:59 ` Marek Vasut
@ 2014-04-11 12:11 ` Fabio Estevam
2014-04-11 12:16 ` Marek Vasut
0 siblings, 1 reply; 9+ messages in thread
From: Fabio Estevam @ 2014-04-11 12:11 UTC (permalink / raw)
To: linux-arm-kernel
On Fri, Apr 11, 2014 at 8:59 AM, Marek Vasut <marex@denx.de> wrote:
>
> This means there's also a pinmux issue in kernel, did you fix it in kernel as
> well please ?
Just sent the patch.
Regards,
Fabio Estevam
^ permalink raw reply [flat|nested] 9+ messages in thread
* Wrong SPI NOR model detected by mx6sl
2014-04-11 12:11 ` Fabio Estevam
@ 2014-04-11 12:16 ` Marek Vasut
0 siblings, 0 replies; 9+ messages in thread
From: Marek Vasut @ 2014-04-11 12:16 UTC (permalink / raw)
To: linux-arm-kernel
On Friday, April 11, 2014 at 02:11:23 PM, Fabio Estevam wrote:
> On Fri, Apr 11, 2014 at 8:59 AM, Marek Vasut <marex@denx.de> wrote:
> > This means there's also a pinmux issue in kernel, did you fix it in
> > kernel as well please ?
>
> Just sent the patch.
Thanks
Best regards,
Marek Vasut
^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2014-04-11 12:16 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-04-10 15:49 Wrong SPI NOR model detected by mx6sl Fabio Estevam
2014-04-10 16:07 ` Marek Vasut
2014-04-10 17:16 ` Fabio Estevam
2014-04-11 0:26 ` Huang Shijie
2014-04-11 2:09 ` Fabio Estevam
2014-04-11 11:43 ` Fabio Estevam
2014-04-11 11:59 ` Marek Vasut
2014-04-11 12:11 ` Fabio Estevam
2014-04-11 12:16 ` Marek Vasut
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).