CY14V101QS EEPROM

取消
显示结果 
显示  仅  | 搜索替代 
您的意思是: 

CY14V101QS EEPROM

1,173 次查看
Jirik_1
Contributor I

Hi.

I try to make memory CY14V101QS working with iMX6UL on QSPI bus. I am able to read ID and made partition (Linux 4.9.18).

This memory is connected to QSPI_B bus. To QSPI_Abus is connected FLASH memory.

I am not able to attach this partition, or write to the memory. I am able to read some data (not sure that they are valid). When I wrote some data, read is different.

dts:

&qspi {
    pinctrl-names = "default";
    pinctrl-0 = <&pinctrl_qspi>;
    status = "okay";
    ddrsmp=<0>;

    fram2: cy14v101@1 {
         #address-cells = <1>;
         #size-cells = <1>;
         compatible = "m25p80", "jedec,spi-nor";
         spi-max-frequency = <40000000>;
         reg = <2>;
         partitions {
             compatible = "fixed-partitions";
             data@0 {
                 label = "spi-flash";
                 reg = <0x0 0x20000>;
             };
         };
     };
};

/* QSPI */
&pinctrl_qspi {
    fsl,pins = <
      MX6UL_PAD_NAND_WP_B__QSPI_A_SCLK 0x70a1
      MX6UL_PAD_NAND_READY_B__QSPI_A_DATA00 0x70a1
      MX6UL_PAD_NAND_CE0_B__QSPI_A_DATA01 0x70a1
      MX6UL_PAD_NAND_CE1_B__QSPI_A_DATA02 0x70a1
      MX6UL_PAD_NAND_CLE__QSPI_A_DATA03 0x70a1
      MX6UL_PAD_NAND_DQS__QSPI_A_SS0_B 0x70a1
      MX6UL_PAD_NAND_RE_B__QSPI_B_SCLK 0x70a1
      MX6UL_PAD_NAND_DATA02__QSPI_B_DATA00 0x70a1
      MX6UL_PAD_NAND_DATA03__QSPI_B_DATA01 0x70a1
      MX6UL_PAD_NAND_DATA04__QSPI_B_DATA02 0x70a1
      MX6UL_PAD_NAND_DATA05__QSPI_B_DATA03 0x70a1
      MX6UL_PAD_NAND_WE_B__QSPI_B_SS0_B 0x70a1
      MX6UL_PAD_NAND_DATA00__QSPI_B_SS1_B 0x70a1
    >;
};

Kernel log:

3 ofpart partitions found on MTD device 21e0000.qspi
Creating 3 MTD partitions on "21e0000.qspi":
0x000000000000-0x000000080000 : "bootloader"
0x000000080000-0x000000090000 : "environment"
0x000000090000-0x000004000000 : "filesystem"
fsl-quadspi 21e0000.qspi: cy14v101 (128 Kbytes)
1 ofpart partitions found on MTD device 21e0000.qspi
Creating 1 MTD partitions on "21e0000.qspi":
0x000000000000-0x000000020000 : "spi-flash"

Devices

/dev/mtd0
/dev/mtd0ro
/dev/mtd1
/dev/mtd1ro
/dev/mtd2
/dev/mtd2ro
/dev/mtd3
/dev/mtd3ro
/dev/mtdblock0
/dev/mtdblock1
/dev/mtdblock2
/dev/mtdblock3

ubiattach -m 3 /dev/ubi_ctrl -> ubi1 error: ubi_read_volume_table: the layout volume was not found.

# hexdump -n 100 /dev/mtd3
0000000 2222 2222 2222 222f 2222 2222 2222 22f2
0000010 2222 2222 f222 2222 2222 2222 222f 2222
0000020 2222 2f22 2222 2222 2222 f222 2222 2222
0000030 2222 223f 2222 2222 2f22 2222 2222 2222
0000040 f222 2222 2222 2222 22f2 2222 2222 2f22
0000050 2222 2222 2222 f223 2222 2222 2222 22f2
0000060 2222 2222
0000064
# flash_eraseall /dev/mtd3
Erasing 128 Kibyte @ 20000 - 100% complete.
# hexdump -n 100 /dev/mtd3
0000000 2222 2222 2222 222f 2222 2222 2222 22f2
0000010 2222 2222 f222 2222 2222 2222 222f 2222
0000020 2222 2f22 2222 2222 2222 f222 2222 2222
0000030 2222 223f 2222 2222 2f22 2222 2222 2222
0000040 f222 2222 2222 2222 22f2 2222 2222 2f22
0000050 2222 2222 2222 f222 2222 2222 2222 22f2
0000060 2222 2222
0000064

What I am doing wrong? Thank you so much for help.

标签 (1)
0 项奖励
回复
1 回复

1,132 次查看
Bio_TICFSL
NXP TechSupport
NXP TechSupport

Hello,

You must check you hardware connection since you are able to read but not write I guess some resistor is on the line, the software and dtb looks correct.

Regards

0 项奖励
回复