Nor Flash Forum Discussions

Hi,

Could you please give me access to the FFS source code ?

I use the S25FL064L with a PIC32MZ without OS.

Thanks,

Please see the attached document for a description of the issue being seen.  Here is a summary:

We are interfacing it with STM32L476VGT Cube 4.26.1. Our firmware is running on STM32Cube_FW_L4_V1.12.0 (equivalent to 1.13.0 qspi). We have been able to successfully read the device ID (0x01 0x60 0x19), erase block (cant verify). Below are the routines, and the capture from our Saleae analyzer. I am looking for any guidance to help understand what the cypress part is looking for.

Design Overview

We are using 2- Spansion 16 bit parallel NOR flash S29GL512S11DHI010 for one of our application. The address and data lines from the  PowerPC(MPC8548E) are connected to the flash through BUS TRANSCEIVERS. 32 bit data from powerPC to be stored into the flash. WE to the flash generated by PowerPC which is routed through a bus switch. And CE to the flash is directly connected from PowerPC.

Problem Statement

We could download the program to the RAM where as the issue is in downloading program to the flash. We are able to write/read the data into/from the flash through shell commands. Because of which we could read the Manufacturer id, device id, protection verification state and basic feature set information from the device. We are able to perform sector erase, where as chip erase, PPB lock bit read commands are not working. 

Error Message

During flashing the chip we are getting an error  "Could not unlock block 496 Flash programming terminated" as shown in the attachment.

Requirements of the Device

Power supply to all the devices are intact.

CE to the Flash is getting asserted before the WE is asserted and CE is de-asserted after WE is de-asserted.

Address and data are stabilized before CE & WE are asserted.

OE, RST and WP of the device are intact.

Hi,

I'm using the Texas Instruments TCM320C6748 DSP with the EMIF interface to communicate with the S29AL016J NOR flash.

The point is that when i erase a sector, then go into a while loop checking DQ7# until it goes high the sector gets properly erased.

But when i erase a sector, then do some other tasks with the DSP without checking the DQ7#...if (after a few seconds) i check the sector (by reading) i realize that some address are not properly erased and keeps the value previous to the erasing command. And even some times it seems to be properly erased but when writing there the DQ5# goes high saying the program operation have failed.

I can't find the problema and i'm quite confused, do you have any clue? Does it is mandatory to check DQ[7:0]# always after erasing?

If you need more information about whatever just tell me.

Thanks in advance,

Juan