Nor Flash Forum Discussions
Hi,
S29GL01GT10TFI010 NOR Flash is used in our design.
We were using a sector to write and read for about months.
Now while trying to do erase using U-Boot erase command, particular address in that sector throws error that erase operation reached time out.
Other sectors excluding which contains that address is working file with erase , write and read operation.
Show LessHi,
I want to know how to repair of BGA after soldering.
Could I get the document regarding "Repair of BGA after Soldering?
P/N:S29AL016J70BFI010
Package:48-Pin FBGA
Best Regards
Show Less
Hi,
In S25FL256L is it possible to write single register ,I mean single write and read. Have some issues sector erase and page write
Regards,
Vignesh.V
Show LessI would like to cross Micron M28W640HCB70N6E to S29GL064S70TFI040. This looks like a direct cross, same package, pin out. Do you have an applications note for migrating from Micron M28W640HCB70N6E to S29GL064S70TFI040?
Show LessPlease show your Handling Storage Conditions generally.
・
・Anti-electrostatic measures
ex: Floors,Ionizers,Electrostatic mat、earth
・Baking condition
ex:125℃ 24Hours, How many hours will be opened?
Regards,
Show LessHello,
This is Sundar from Hardware team, ZF Automotive, we are using the S70FS01GS, 1-Gb device in ADAS programs.
We would like expand flash memory size so that let us know, is there any Flash device to replace S70FS01GS, 1-Gb (128 MB), 1.8 V FS-S Flash in the same footprint (BGA24).
Regards
Show LessDear All,
Currently we are trying to access the NOR flash from windows over USB-MS class device. FTL (block driver in Cypress FFS) integrated in our application and using FTL as block driver.
We are able to format the flash from windows. And able to copy the files to flash. But when we eject the device (which contains the flash) and again rec-connect to the PC, it is found files are corrupted. Files names and there sizes read successfully, but files are corrupted.
We suspect that this issues is due to wrong configuration and porting of FTL block driver. Below is the configuration for the FTL.
FTL configuration
#define NUMBER_OF_BYTES_PER_SECTOR (512)
#define SECTOR_SIZE (NUMBER_OF_BYTES_PER_SECTOR)
#define EBLOCK_SIZE (0x1000)
#define NUMBER_OF_ERASE_BLOCKS (4096)
Device side USB interface configuration as below,
Number of blocks --> 4096
Size of each block --> 4096 bytes
MSC media packet size --> 4096 bytes
NOR flash configuration
For NOR flash write we are using command PP (Page programming : 02h, max write size 256 bytes)
For NOR flash read we are using command Read (03h)
For NOR flash Erase we are using command Sector Erase (20h, sector size 4096 bytes)
Kindly provide us the appropriate inputs to overcome the mentioned issue, also help us to point out the mismatch in configuration.
Is there any specific initialization sequence for FTL and any specif eject (USB) sequence to store the data properly.
Show LessHi,
We are using S70GL02GS in our product. With the old u-boot version U-Boot SPL 2013.10 (Aug 05 2019 - 23:00:56) we are able to bring up the board and everything is fine.
We are porting the code to newer version of u-boot(U-Boot SPL 2018.01-00569-g7b4e473842-dirty) and kernel (V4.12) and we are facing the problem in flash being recognized.
Error is “## Unknown flash on Bank 1 - Size = 0x00000000 = 0 MB”.
Upon debugging we are noticing that in Flash_init() function of file drivers/mtd/cfi_flash.c, it is not able to recognize the flash.
Any input on this? Please let us know.
Regards
Srinivasa
Show LessI have a question about "Sector Erase Time" of S29JL032J.
Sector Erase Time = 0.5sec (Typ) is described in "18. Erase and Programming Performance" on page 54 of the data sheet.
→Q1.
Is this the performance of Sector Size = 64KByte?
If this understanding is correct,
→Q2.
How many seconds is Sector Erase Time of Sector Size = 8KByte?
Best Regards,
Harukawa
Show LessHi,
Using a Renesas RX111 MCU via RSPI @ 3V3 to a S25FS064SDSMFI010 device @1V8 via PI4ULS3V304ZMEX level translator.
Electrical interface is OK, I can read and write to the Spansion SPI flash.
Now, trying to use SpansionFFS, it seems stuck here (within ion_pim_spansion.c😞
With stuck I mean: does not matter whether I first try to read the sectors [ionFS_get_sectors(0)], or mount [ionFS_mount(_TC("/a/", 0, 0, 0)], or format[ionFS_format(_TC("/a/", 0, 0, 0, 8400, _TC("FAT16"), 0)], all of them of course all after calling ionFS_zero_init() and ionFS_init(, it always gets into the green highlighted line (line 274) and of course fails.
Serial console shows:
FTL Version: 04.00.05 2015.10.30 09.00 PM PST
ERROR: pim_ioctl_span_init: FTL_InitAll() 2
ERROR: FTL return code = 14
Through analysis and debugging I could see:
- When getting into line 272 the value of initStruct.format is still FTL_DONT_FORMAT (0), which is the reason why the second FTL_InitAll() takes place.
- The second FTL_InitAll() returns 14 = FTL_ERR_NOT_FORMATTED.
- The weird thing is that line 266 does not return any error, meaning the formatting took place.
Has anybody experienced such a situation and can provide hints on how to solve it?
Thanks and regards.
Show Less