Hi Jason,
You was right about the .bof advice, actually I forgot including the
compilation date + .bof, now I'm wondering why the auto-completion drop
me an uncompleted filename... anyway, another stuff is that I don't know
why but if I copied the bof file into /boffiles folder into ROACH
filesystem (with NFS) I can run script without any problem (It seems
that there is an issue between NFS and corr + katcp + python copying a
bof inside the same system), from now I will put the file manually.
I have another problem related to wrong spectrums with spectrometers
compiled by myself (based on the original from tutorial) but I will
research more before preparing my enquiry, thanks a lot!
Regards,
Daniel.
On Fri, 8 Apr 2011 09:00:50 +0200, Jason Manley <[email protected]>
wrote:
192.168.100.2: #log warn 382067292210 poco borph\_process\_exited
This says that while the bof file was started, it then exited again.
Reply: !write fail program.
In other words, your FPGA is not programmed.
I saw in a past post, that there is an issue with correlator library
that is not checking if the bof file is actually programmed on FPGA.
You can do a ping() call to check that it is responding properly.
I can use BORPH and program the bof file without any problem (I can
access the PowerPC registers, and properly kill the process) but with
the script something is broken, I copied the bof file directly to the
/boffiles folder (I'm using NFS) and I could continue working I though
that was the problem (I could run the script for a while) but now I
step on the same trouble. What I must try from this? Thanks!
Programming FPGA with r_spec_2048_r105... done
Looks like perhaps you left out the ".bof" extension? It's maybe the
wrong filename in the programming script?
Jason
