Non Volatile RAM (F-RAM & NVSRAM) Forum Discussions
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 LessHello,
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,
I am having trouble getting read responses from a 4Mb fram. I have tried utilizing two different TI launchpads (C2000/Tiva) to communicate with the device. I have been running the clk speed in the 1Mhz to 2Mhz range. Also, I am utilizing a GPIO pin as a chip select as the spi CS peripheral de-asserts after each byte is transmitted. Pseudo code is as follows in my testing program:
set "CS" line high.
setup spi periph for Mode 0
// software reset.
write(0x66)
write(0x99)
delay for 300us
write(0x06)
write(0x02, 0x01, 0x12, 0x34, 0xaa, 0x55)
read(0x03, 0x01, 0x12, 0x34, 0x00, 0x00)
end program.
The parenthesis open indicates CS going low, and parenthesis closed indicates CS going high. In the program, my receive bytes are 0xFF, 0xFF. In other testing programs, I have tried writing to the status/config registers and I am getting 0xFF bytes as well.
I am including scope shots from the TI C2000 based board. Are there any steps that I am missing in getting the device to function? Thanks for the help.
Show Less
Hello,
I'm inquiring whether there exists a dedicated Linux device driver or a compatible one for facilitating communication with the FM31256-G chip via the I2C protocol.
Your assistance on this matter would be greatly appreciated.
Thank you in advance.
Show Less
Hi team ,
For part series CY15B004Q-SXE* under operating range ambient temperature range is define can we use it as a
recomended operating temperature range . under the thermal data junction-case thermal resistance and junction-ambient thermal resistance is present we also need the value of junction-board thermal resistance.
looking for your soonest response.
Show Less
I 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
Regarding CY14B101LA-BA45XIT, is there any command to read device ID or UID like flash memory?
The data sheet doesn't mention it, so can you tell me?