GithubHelp home page GithubHelp logo

hitomi2500 / wasca Goto Github PK

View Code? Open in Web Editor NEW
70.0 70.0 7.0 39.11 MB

Sega Saturn multipurporse cartridge

License: GNU General Public License v2.0

VHDL 3.70% Tcl 0.68% Verilog 10.74% SystemVerilog 5.53% Makefile 1.13% Shell 0.09% C 75.60% C++ 0.11% Assembly 1.46% HTML 0.84% GDB 0.02% OpenSCAD 0.04% Batchfile 0.06% QMake 0.01%

wasca's People

Contributors

cafe-alpha avatar hitomi2500 avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

wasca's Issues

SDRAM access timing adjustement in firmware v1.x

Long time no see ! Pseudo Saturn Kai development reached a milestone big enough so that I can finally put more time on Wasca development.

And, as indicated in the title, I'm currently experiencing SDRAM access issues in firmware v1.x (MAX 10-based) from a design to another, which improves by randomly changing settings in Qsys and heavy prayings ... in simpler words, I'm flooded with technical difficulty of firmware development.

So I would like to know how you managed to adjust access timing for SDRAM in v1.0 board (which was running Saturn test utility from emulated boot ROM, hence with working SDRAM access) : from my limited understanding, as this requires to dedicate one clock signal for SDRAM chip (and adjust its phase with slack from address/data signals), I was thinking to use second clock output from MAX10's PLL as clock signal for SDRAM.
But firmware v1.0/v1.1 uses only one clock output from PLL, so if there's another way to adjust SDRAM access timing, please inform me about it.

I suppose you still prefer the snickerdoodle-based architecture, but that would be really appreciated if you want to give an hand on MAX 10 one โ™ช

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.