[casper] PlanAhead to a working bof

[Gard, Johnathon D.]

Hello Casperites,



ROACH2, MATLAB 2012a (I think), ISE 14.7, Ubuntu 14.04 LTS


I am working on compiling firmware without timing errors. More like ignoring 
static configuration register timing errors. Any rate, I have been pulling my 
design into PlanAhead successfully and applying some DSP slice constraints with 
some success. When it comes time to generating a bof file, I used the mkbof_64 
executable located in the implementation directory that simulink creates. This 
seems to work fine. The problem arises when I move the generated bof file to my 
ROACH2 and try to program the FPGA. I upload the bof via python and call the 
progdev() command through python. This fails without anything meaningful in 
python. However when watching the serial output from the PPC, I get this:


/usr/bof # roach open config called
rdev gpio preconfig doneProgrammed fpga device id = 
Attempted to program incorrect configuration onto Virtex6 FPGAroach release 
config called


I am not sure what might be happening here. I was wondering if anyone else had 
tried this or ran into such a problem before.


Other notes and ideas:

I could be using the wrong mkbof, but when a design meets timing the casper_xps 
gui script makes a bof that works. So, maybe the script uses a different 
mkbof_64.


There is another mkbof executable, but that one does not seem to function. I am 
assuming it is the 32 bit version, which would mean I would need a bunch of 32 
bit libraries.


There are options in the PlanAhead bitfile generation and I could have those 
wrong. This could be very likely.


I  could alternatively use the system.ucf file updated by PlanAhead through the 
casper_xps process in matlab. However this would drop my control of the PAR 
which seems to have a strong influence on how well it meets timing. Ironically, 
timing driven placement gets the far worse timing results.


As far as what it running on the PPC and what katcp library I am using, That is 
a very good question which I truly don't know the answer to.


Any other ideas or solutions?


Johnathon Gard

National Institute of Standards and Technology

Re: [casper] Working with demux modes of 'ADC16x250-8 coax rev 2'

[Jack Hickish]

Hi Vishwa,

Is the syntax definitely -demux=1 andnot either --demux=1 or -d 1 ?


Jack

On Wed, 3 Feb 2016, 12:39 a.m. Vishwa Seneviratne 
wrote:

> Hi,
>
> I am working on how to work with different operating of the 'ADC16x250-8
> coax rev 2' for a very simple design to test how the ADC works. The design
> is compiled at an IP clock rate setting of 200MHz. My objective is to
> sample my input signal at higher sampling rate (preferably 400, 800 MHz).
>
> According to the user guide ''
> https://casper.berkeley.edu/wiki/images/4/4c/ADC16_user_guide.txt; by
> setting the demux parameter I should be able to switch between different
> sampling rates. I get the following error.
>
> $ adc16_init.rb -v -demux=1 192.168.10.5 poly_design.bof
>
> /var/lib/gems/1.9.1/gems/adc16-0.3.6/bin/adc16_init.rb:40:in ` (required)>': invalid option: -demux=2 (OptionParser::InvalidOption)
>
> from /usr/local/bin/adc16_init.rb:19:in `load'
>
> from /usr/local/bin/adc16_init.rb:19:in `'
>
> When I don't pass the 'demux' parameter the ADC board get initialized to 8
> analog inputs by default.
>
> How do I resolve this issue? or how can I set the ADC's to operate at
> different sampling rates?
>
> Thank you in advance
>
> Sincerely,
>
>
> *Vishwa Seneviratne*
>
> *Graduate Student*
>
> *Dept. of Electrical and Computer Engineering*
> *University of Akron*
>