From: xixiguo Date: Tue, 25 Nov 2014 04:46:06 -0700 (MST) Subject: [U-Boot] [PATCH 1/3] sf: stmicro: Add support for N25Q32 In-Reply-To: <1359462897-11405-1-git-send-email-michal.simek@xilinx.com> References: <1359462897-11405-1-git-send-email-michal.simek@xilinx.com> Message-ID: <1416915966332-197460.post@n7.nabble.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de I add it's probe in stmicro.c as follow : /static const struct stmicro_spi_flash_params stmicro_spi_flash_table[] = { ... + { + .id = 0xba16, + .pages_per_sector = 256, + .nr_sectors = 64, + .name = "N25Q32", + }, ... struct spi_flash *spi_flash_probe_stmicro(struct spi_slave *spi, u8 * idcode) { ... + /* clear BP# bit for locked flash */ + spi_flash_cmd_write_status(flash, 0); .../ Then I add the macro definition of CONFIG_SPI_FLASH_STMICRO. I got the flash was detected : /U-Boot# sf probe SF:: Got idcodes 00000000: 20 ba 16 10 00 .... SF: Detected N25Q32 with page size 64 KiB, total 4 MiB/ Can it prove the drvier is correct? And when I erase the flash, it never come out error, it seemed erase correctly : /SF: erase d8 1 0 0 (20000) status=0x0 ... SF: erase d8 21 0 0 (220000) status=0x0 SF: Successfully erased 2228224 bytes @ 0x0/ But I read out the data, it is not 0xff. -- View this message in context: http://u-boot.10912.n7.nabble.com/PATCH-1-3-sf-stmicro-Add-support-for-N25Q32-tp145976p197460.html Sent from the U-Boot mailing list archive at Nabble.com.