Non Volatile RAM (F-RAM & NVSRAM) Forum Discussions
Hello,
I am currently developing software for CY15FRAMKIT-002 with a STM32F7 Nucleo Board. I was able to read the Device ID (RDID, command 9Fh) as 0000000006825150 in SPI mode and perform a write to and read from the memory successfully. Now, I configured the device to QPI mode with the following settings in the following sequence:
1. Set the Memory Latency to 0x2 by setting bits 7:4 in Configuration Register 1
2. Set the Register Latency to 0x2 by setting bits 7:6 in Configuration Register 5
3. Enabled QPI mode by setting bit 6 in Configuration Register 2
Once in QPI mode, I tried reading the Device ID (RDID, command 9Fh) but always got the response as 8888888888888888. When I tried to read and write the memory in QPI mode, that seems to work successfully. Then why does the Device ID command not repond with the correct value when it is a supported command in QPI mode? Is this an issue with the GPIO state for IO3 pin or something else? For information, my GPIO pin states are set as below for the STM32:
nCS: NOPULL
SCK: NOPULL
IO0: NOPULL
IO1: NOPULL
IO2: NOPULL
IO3: NOPULL
If this is a GPIO pin state issue, I would wonder why my read and writes work in QPI mode with the set latency.
Regards,
Surabhi
Hello
We are using FRAM CY15B104QI memory in our project. We are using MSP430FR5994 microcontroller and we want to communicate with FRAM using SPI.
We have an issue with accessing the memory. We tried to read status register but we did not get expected values on MISO pin (MISO pin did not change its state at all). We made it work once but after that the same code did not work and we do not know what can be the issue.
I attached the archived image of workig example (the only one when we get the expected response). I also attached 2 screenshots of the signals on CS, CLK and MOSI that we measured using an osciloscope.
Are there any known issues with the memory or has this occurred to someone else?
Best regards
Show LessI am using CY14U256LA-BA35XI as replacement for STK12C68-L35M replacement. Not using A13 and A14 as only 64kbit is used. HSB not connected as only power ON/OFF autorecall/store function is used. Please review the design and part replacement.
Show Less
We used Infineon's IC (p/n: S25FL064LABMFV000) to enter QPI mode and it was locked and could not be unlocked.
smartconx_target@Q!w2e3r4t5y6u7i8o9p0||/t5/%E9%9D%9E%E6%98%93%E5%A4%B1%E6%80%A7RAM-F-RAM-NVSRAM/%E5%AD%98%E5%82%A8%E5%99%A8%E8%A2%AB%E9%94%81-%E6%97%A0%E6%B3%95%E7%BC%96%E7%A8%8B-%E5%86%99%E5%85%A5-%E5%A6%82%E4%BD%95%E8%A7%A3%E9%94%81/td-p/675343
Show LessHi,
Does Infineon / Cypress have radiation test data on FRAM CY15B104Q (full part number CY15B104Q-SXI or similar) or on this part family?
Specifically I am looking for a SEL or DSEE threshold. I've seen neutron data in this forum, but I am wondering if you have single event effects (SEE) / heavy ion test results.
(Total Ionizing Dose (gamma) would be great too, if you have it)
Thank you!
Todd
Hi
We are trying to use the fm25v02a-GTR device with AM335X processor we added below configuration in /driver/mtd/spi-nor/spansion.c file
static void fm25v02_post_sfdp_fixups(struct spi_nor *nor)
{
nor->addr_nbytes = 2;
}
static struct spi_nor_fixups fm25v02_fixups = {
.post_sfdp = fm25v02_post_sfdp_fixups,
};
static const struct flash_info spansion_nor_parts{
{ "fm25v02", INFO6(0x7f7f7f, 0x7f7f7f, 32 * 1024, 1)
FLAGS(SPI_NOR_NO_ERASE)
.fixups = &fm25v02_fixups,
},
}
By adding below path to driver we are able to get the FRAM device as mtd device (/dev/mtd0). We are using kernel version of 6.1.45, please let me know is any configuration is missing. We are verifying the mtd device using below commands
dd if=/dev/urandom of=write_test.img bs=1024 count=32
sudo dd if=write_test.img of=/dev/mtd0 status=progress
sudo dd if=/dev/mtd0 of=read_test.img status=progress
sha256sum write_test.img
4ca9d8b97a9a8f347720f1410076ffe9f0bb5e5a8d05a1d85b0a36bbb0297704 write_test.img
sha256sum read_test.img
ded04e84443454014a240b1eba70454073e9ea5a1d8567e82b782136713707f1 read_test.img
We are observing the file written to FRAM is corrupted when we read.
Show LessI want to find a drop-in replacement for FM25L04B because it has errata in writing procedure, I changed it to FM25CL64B but it does not work. any advice?
Thanks
Farah
Show Less