SRAM Forum Discussions
I was wondering if the act of placing the CY14B101 RTC in calibration mode, upsets the time the device is maintaining. For example, if the RTC is in calibrate mode for x milliseconds, will the RTC still maintain time for those x milliseconds. Or does the RTC lose the time it is in calibration mode?
Thank you
Show LessWorking on a retro style CPU using mostly HC logic chips for fun.
I wanted to try something different with the register file.
I could build it too with 8 bit wide logic chips but thought I'd try using a small ram as the register file.
The cpu in question will work as follows.
On the low level of the clock the control lines will be setup
- a "read" address on the register file whose value will be fed into the ALU and also
- a "write" address on the register file where the ALU result will be written
On the rising edge of the clock the result of the ALU is latched into the slot identified by the write address.
The write address might be the same as the read address or a different location.
So in a single cycle data is fetched from the register file and looped back into the register file.
The general idea is as shown below. Though actually there are two "Read" addresses and one "write" address.
The thing below is build at the moment using a bunch of +ve edge triggered latches and a demultiplexer to select the "In" and "Out" instances.
To make the above work in a single clock cycle I need only the "In" data to be latched.
The Write/Read Addr and the "Out" are async (combinatorial) values.
I had considered putting a dual port SRAM in there instead of my edge triggered latches.
In this setup one of the ports would be always for "write" and the other port always for "read" (just like the sides of my existing 8 bit latches).
But a dual port async SRAM alone won't work as this potentially sets up a feedback loop from the "Out" back to the "In" via the ALU.
This feedback would happen whenever the WriteAddr and ReadAddr have the same value.
This feedback doesn't happen with my existing latches as the input to the latch only happens on the +ve edge.
Additionally there are these SRAM caveats in the docs about problems (busy and interrupts) when the Read and Write addresses are matching.
I noticed that dual port synchronous sram have this "flow through" feature and a latched input, which sounds promising.
However, these products also seem to have a latch on the output too.
And also latching on the addresses which will get in the way of the single cycle approach.
Does anyone have advice on these devices and concerns, and in particular whether this is even possible?
Thanks
Show LessWe want use NXP MPC5777C MCU to extend Sync. SRAM externally.
https://www.nxp.com/files-static/32bit/doc/data_sheet/MPC5777C.pdf
But the NXP MPC5777C some pins are ADMUX bus.
Cloud you guide us how to implement the connection?
Thanks,
Mitchell
Show LessHi dear friends,
I have CY7C2670KV18-550BZI
and the marking on the parts is a bit different.
There is no country of manufacturing, but I'm not sure it should cause I use https://www.cypress.com/file/41321/download It's for 2019, but my parts are 2014 & 2018
I think the marking could be a little different, isn't it?
Can U advise pls is it alright?
Best regards
Paolo
Show LessCY7C1356C - Ok so I am looking at the data sheet, adn I do not see how you set the address. can I mix any of the A's around and get somewhere, my gut is saying no. Most parts have A0 - A15 or something of that nature. But I do not see anything like this. More information would be nice.
Show LessI am building a homebrew CPU and have now reached the point of designing the SRAM part. I plan of using a simple 32K x 8bit static RAM (such as the Cyprus CY62256N). My concern is that the part is asynchronous but I want it to act like a synchronous part.
In the the rest of my design, registers are written to on the rising edge of the clock with the required new value already on the data lines.During the rest of the clock period the new instruction is processed and a new value might be placed on the data lines. This is fine because the register only updates on the rising edge and not later on, even though the clock happens to still be high.
I presume this approach will not work with asynchronous SRAM. I am concerned that the rising edge of the clock will update the SRAM, but if the clock happens to still be high when the value of the data lines is updated for the next instruction it will cause another update that is not wanted.
Is there some common technique to achieve what I need?
Show LessHello I was reviewing the specs for this product and would like to know what the power dissipation is in Watts. I look forward to your response, thank you.
Show LessHi.cypress
in the website(http://www.cypress.com/cypress-semiconductor-conflict-mineral-policy), I can't find the CMRT5.12 newly version form. the customer hope we may provide the newly CMRT5.12 version as the attachment. I only former 5.1 version via the my case number 00371009(MyCase 00371009).
Show Less