QSPI cannot access on u-boot with sf probe 1:0 command

hideo_yamashiro — Mon, 13 Apr 2020 08:04:30 GMT

Hi, kindness people.

We try to check QSPI access on u-boot on our board.
But we cannot access to QSPI. the QSPI device is connect to same pins of MX7DSABRESD board.

We added define qspi and epdc. we refer imx7d-sdb-qspi.dtsi to modify device tree.
And we added asterisk on Device Drivers -> SPI support -> Freescale QSPI driver on 'make u-boot-menuconnfig'.

When we type command "sf probe 1:0" on u-boot prompt , device_fund_chip_select() is fail.
Because the 2nd parameter **devp of device_find_first_child() is NULL.

We would like to know how to modify to use qspi on u-boot sf command.

=====added contents in device tree(mx7d-sdb.dts)
/* disable epdc, conflict with qspi */
&epdc {
status = "disabled";
};

&iomuxc {
   qspi1 {
       pinctrl_qspi1_1: qspi1grp_1 {
           fsl,pins = <
               MX7D_PAD_EPDC_DATA00__QSPI_A_DATA0 0x51
               MX7D_PAD_EPDC_DATA01__QSPI_A_DATA1 0x51
               MX7D_PAD_EPDC_DATA02__QSPI_A_DATA2 0x51
               MX7D_PAD_EPDC_DATA03__QSPI_A_DATA3 0x51
               MX7D_PAD_EPDC_DATA05__QSPI_A_SCLK 0x51
               MX7D_PAD_EPDC_DATA06__QSPI_A_SS0_B 0x51
           >;
       };
   };
};

&qspi1 {
   pinctrl-names = "default";
   pinctrl-0 = <&pinctrl_qspi1_1>;
   status = "okay";
   ddrsmp=<0>;

   flash0: is25lp01g@0 {
       #address-cells = <1>;
       #size-cells = <1>;
       compatible = "spi-flash";
       spi-max-frequency = <29000000>;
       /* take off one dummy cycle */
       spi-nor,ddr-quad-read-dummy = <5>;
       reg = <0>;
   };

   flash1: mx25l51245g@1 {
       #address-cells = <1>;
       #size-cells = <1>;
       compatible = "spi-flash";
       spi-max-frequency = <29000000>;
       /* take off one dummy cycle */
       spi-nor,ddr-quad-read-dummy = <5>;
       reg = <0>;
   };

};

Re: QSPI cannot access on u-boot with sf probe 1:0 command

george — Thu, 16 Apr 2020 02:33:41 GMT

Dear Yamashiro-san,

I'm not sure if it's related to the problem you see now, but why not make a change corresponding to the patch below.

mtd: spi-nor: Add is25lp01g spi-nor support · kalray/barebox@631b4b1 · GitHub

In the case of spi_flash_ids.c, it would probably look like this:

{"is25lp01g", INFO(0x9d601b, 0x0, 64 * 1024, 2048, SECT_4K | RD_QUAD | RD_DUAL) },

Best Regards,

George

i.MX ProcessorsのトピックQSPI cannot access on u-boot with sf probe 1:0 command

QSPI cannot access on u-boot with sf probe 1:0 command

Re: QSPI cannot access on u-boot with sf probe 1:0 command