Open agv100 opened 10 months ago
Hello, Yes DDR3 is not working and is a WIP. Sipeed example uses Gowin's DDR3 encrypted IP. But since Gowin doesn't provides real documentation about primitives required to add this support it's more difficult/long to have a working support. If you need SDRAM it's possible to plug a Mister SDRAM extension into SDRAM dock's connector.
@agv100: We've planned some to work on this in the following weeks/months. This will probably happen soon but we are working on others features in priority on other features for now.
While continuing this work, it could be worth checking if a specific LOC constraint is required to get the DDR3 working, as it is for the AE350 SOC:
@enjoy-digital @trabucayre
I would like to give it a try on the modified board. The background is because before 19.9 is released the DDR3 IP cannot run AE350 with non-Micron DDR. You can read more on here about what we had done: https://github.com/briansune/Tang-Mega-138K-AE350-Demo
If such design is based on the default official board hardware then my current hardware is 100% aligned.
Meanwhile from the generated verilog file. I can see the DDR clock is using a 1:2 rather than 1:4? GW5AST do not support 1:2 physical timing it will fail surely.
Hello, Just found new commit, adding both sipeed and mister SDRAMs. So, if I build (without today commit on litedram/litedram/frontend/wishbone.py as it fails on assertion assert wishbone.addressing == "byte" ), with options:
I still can see sdram init failed, but, when I manually read-write upto 4-byte words, it works well:
Initializing SDRAM @0x40000000...
Switching SDRAM to software control.
Switching SDRAM to hardware control.
Memtest at 0x40000000 (2.0MiB)...
Write: 0x40000000-0x40200000 2.0MiB
Read: 0x40000000-0x40200000 2.0MiB
bus errors: 128/256
addr errors: 0/8192
data errors: 524288/524288
Memtest KO
litex> mem_write 0x40100000 0xabcd
litex> mem_read 0x40100000
Memory dump:
0x40100000 cd ab 00 00 ....
litex>
Anything I have to do to get it fully working?
@agv100
I think you had an misunderstand on what the last commission.
Read and think is what you need. The commit is for external SDRAM PMOD. Not the default DDR3 memory.
End of story.
Bests, Brian
Hello, I'm trying to build litex bytestream with DDR3 support. Previously, on-board DDR3 wa checked with GAO/simple example in sipeed github examples, so, should be operational.
But, when I load litex bitstream, build with --with-ddr3 support, I see, initially ddr3 could be seen:
But it's tests are failed:
And, when I try to access memory manually, it looks not working:
What could be a problem?