[J-core] numato CFG_DDR_CK_CYCLE = ?

[Davor Emard]

HI

I was trying to extract J2 DDR driver for numato but I have up
after several hours of trying

I copied some DDR related files with rtl and packages that I "thought"
should be
enough but j2 appeared so intermixed with vhdl "package" files, so attempt to
isolating DDR as "black box" appeared too difficult for me

I'd like if I could have some subdirectory which contains all DDR
related files which has a toplevel glue that provides a simple
32-bit clk-synchronous CPU interface, something like
addr,data_in,data_out,rw,request,ready,byte_select
(maybe burst length also)

It would be cool you can help or already have DDR cleanup'd or blackbox
version

if you need to take any of f32c stuff (video, fpu, cpu) (probably you
won't need
last item he-he :), you are free to do so. Mostly the parts are
blackboxed alike.

Davor


On 8/24/16, D. Jeff Dionne <Jeff at se-instruments.com> wrote:
> Goran,
>
> Can you tell us what the sticking point is?   Is it integrated but not
> working, or is the problem knowing how to get it connected, configured and
> synthesised?
>
> We will definitely look at your cores, we would very much like to build
> ecosystem.  We have some thoughts on that... Geoff's SoC top level generator
> tool is proof that a high level of automation is both possible and
> useful...
>
> Cheers,
> J.
>
>> On Aug 24, 2016, at 17:49, Goran Mahovlić <goran.mahovlic at gmail.com>
>> wrote:
>>
>> We still have no luck with implementing your DDR driver into our designs.
>>
>> If someone have bit of time and could solve this, that would be great.
>>
>> Recently he added Floating point vector processor, and some DDR3 AXI
>> driver for other boards, but numato gives us trouble.
>>
>> https://github.com/f32c/f32c
>>
>> And feel free to use our modules for your CORE to...
>>
>>> On Tue, Jun 7, 2016 at 3:20 PM, Geoff Salmon <gsalmon at se-instruments.com>
>>> wrote:
>>> Hi Goran
>>>
>>> CFG_DDR_CK_CYCLE = 20 in the mimas_v2 build. If you run a build you can
>>> see the values of these CFG_ and CONFIG_ values in the output directory's
>>> config sub-directory. You can build just the config files if you want too
>>> like this
>>>
>>> $ make mimas_v2 TARGET=config/config.vhd
>>> $ cat last_output/config/config.vhd
>>> -- This file is generated by the makefile
>>> package config is
>>>  constant CFG_CLK_BITLINK_PERIOD_NS : integer := 8;
>>>   constant CFG_CLK_CPU_DIVIDE : integer := 20;
>>>   constant CFG_CLK_CPU_PERIOD_NS : integer := 20;
>>>   constant CFG_CLK_MEM_2X_DIVIDE : integer := 10;
>>>   constant CFG_CLK_MEM_PERIOD_NS : integer := 20;
>>>   constant CFG_DDRDQ_WIDTH : integer := 16;
>>>   constant CFG_DDR_CK_CYCLE : integer := 20;
>>>   constant CFG_DDR_READ_SAMPLE_TM : integer := 2;
>>>   constant CFG_SA_WIDTH : integer := 13;
>>>
>>> end;
>>>
>>> - Geoff
>>>
>>>
>>>> On 16-06-07 08:02 AM, Goran Mahovlić wrote:
>>>> My colege Emard is trying to fit your DDR driver to our f32c core, so
>>>> if
>>>> you can help him a bit.
>>>> Does someone know what should be constant value for numato
>>>>
>>>> CFG_DDR_CK_CYCLE = ?
>>>>
>>>> Tnx ,
>>>> Goran
>>>>
>>>>
>>>> _______________________________________________
>>>> J-core mailing list
>>>> J-core at lists.j-core.org
>>>> http://lists.j-core.org/mailman/listinfo/j-core
>>
>> _______________________________________________
>> J-core mailing list
>> J-core at lists.j-core.org
>> http://lists.j-core.org/mailman/listinfo/j-core
>