HyperRAM is a mistake. I got it working 100%, but wow what a travesty
-
Show this thread
-
Here it is, 32byte fixed bursts. Datasheet is wrong, extra cycles are needed from launch to data latch. Maybe tomorrow i'll have Starfox2 booting from it.pic.twitter.com/3rSLRP2ZvW
3 replies 1 retweet 10 likesShow this thread -
Replying to @fpgashibe
If I remember correctly the number of cycles can be configured and different chips may have different default values. Or something like that ... it's been a while since I wrote a HyperRAM IP core.
1 reply 0 retweets 1 like -
Replying to @oe1cxw
Are/will any of those cores be available with a FOSS license?
1 reply 0 retweets 2 likes -
Replying to @Wallbraker
Claire Xen 🏳️⚧️ 🏳️🌈 🧙🏻♀️ BLM 🏴 🚩 Retweeted Claire Xen 🏳️⚧️ 🏳️🌈 🧙🏻♀️ BLM 🏴 🚩
Only this: http://svn.clifford.at/handicraft/2017/icohramtst/ … But that's not a HyperRAM core. It's just a test design that plays a fixed signal pattern from a ROM to test basic communications with the HyperRAM chip (see http://libretto.py for the pattern generator).https://twitter.com/oe1cxw/status/845912212090880000 …
Claire Xen 🏳️⚧️ 🏳️🌈 🧙🏻♀️ BLM 🏴 🚩 added,
2 replies 0 retweets 0 likes
Table 5.3 from HyperBus Specification (http://www.cypress.com/file/213356/download …). It is configurable and the default value is device dependent.pic.twitter.com/gavGGyyzdv
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.