Hello,
The 5-6 second delay from power up to the start of execution of your code is the
time the NB monitor program is running. It waits 5 seconds to give you a chance
to break into it and use the command-line, and then it jumps to your code. You
can shorten that time to as low as 1 second, I think, but I've seen warnings to
NOT set it to zero. The shorter you make the time, the harder it will be to
break into the monitor when you want to load a new program into your board. I
don't have a 5234, but you can definitely generate frequencies in the 2-5 MHz
range using the 32-bit timers or the eTPU. Read the sections on those
peripherals in the NB documentation and look at the sample programs. The eTPU is
a complex peripheral, but there may be a sample program that illustrates use of
the PWM function. With that function, you can set the frequency and duty cycle,
and change either one at run-time.
Joe
--- In netburner_group@yahoogroups.com, "Shahabuddin Inamdar" <shahab47@...>
wrote:
>
> Hello there.
>
> I have few questions about MOD 5234.
>
> I am using MOD5234 to program my FPGA.
> For this, I generate the PROGRAM PULSE so that the configuration process will
begin inside FPGA.
>
> I am successfully able to do that.
>
> However the problem is :
> 1. It takes 5-6 seconds before the PROGRAM pin goes low for 1 second.
> I want this PROGRAM pulse to occur as soon as NB is powered up.
> Does NB takes 5 seconds to boot up?
> Because generating the PROGRAM pulse is the first thing I am doing
> in my code.(thats what I think). Maybe there is something I am
> missing.
> (I am using MOD5234 J2-pin38 as PROG PIN which is connected to
> FPGA PROG pin.)
>
>
> 2. Also the CCLK, (again generated by NB on J2-pin29) going to the FPGA is
about 200Khz. How can I generate a clock in MHz using the NB timer or is there
any other method to generate a clock (which will act as CCLK for FPGA in the
range of 2-5MHz)
>
> NOTE: The FPGA is being programmed here as in SLAVE SERIAL MODE.
>
> Any help in this regard will be appreciated.
> Thanks.
>