Whitepapers are taking over the lost TechXclusives

Thanks, John , for the friendly comment. Some TechXclusives are now reborn as White Papers. And not without problems. The TechXclusive process had been extremely informal, hardly any peer review, no formal Tech-writing, and no legal "censorship". It was built on trust, kind of like my postings in this newsgroup. A White Paper goes through tech-writing and through peer review, and if somebody does not like it, he can veto and stall the project. Since I often stick my head out with unconvential solutions, I thus encounter these problems. Makes you wish for the good old days... Peter

Just FYI, there are also some other uses described in XAPP463 starting on page 24. Although this is written for Spartan-3, the block RAM is compatible with Spartan-3A/-3E, Virtex-II/Pro, etc.

-- Steve Knapp Prevailing Technology, Inc.

Peter, for the read-modify-write trick, don't you need to forward the write in case the previous cycle wrote the same location?

Tommy

Here is my dilemma, I like to show solutions to unconventional problems. (I started in circuit design before there were Integrated Circuits) What to do when you move data between asynchronous clocks, or how to generate a stable slow clock, or how to double the clock frequency when the DCM cannot do it, or what to do when the incoming clock has hick-ups stemming from pc-board reflections that it is too late to fix. All these are "dirty tricks" that purists frown upon, especially when they have never been in these ugly predicaments. It is fine to be digitally pure, but the world can be dirty and ugly. Band-Aids are not the highest form of medicine, but they are nice to have when you need them... Peter