On 02/25/2015 12:51 PM, David MacMahon wrote:
Hi, Paul,
Probably you are, but just to verify, are you running tcpborphserver2 from the
command line as root?
yes.
It sounds like something changes between boot time and command line time. Are
you sure it's the same tcpborphserver2 executable that is getting executed?
Are you running additional processes post-boot that might be
locking/hogging/clobbering some resource(s) that tcpborphserver2 needs? Have
you tried running tcpborphserver2 under strace to see if that helps pinpoint
what is failing?
Those are great ideas, thanks Dave. I'm not sure how to answer some of
them, but I'll look into it.
Paul
Just some ideas,
Dave
On Feb 25, 2015, at 3:16 AM, Paul Marganian wrote:
Thanks Marc,
No, the *only* difference between being able to program the fpga with 'progdev'
is whether or not I'm running tcpborphserver2 from the command-line, or
whether it is running from when the board booted up. It makes no difference
what bof I use.
Paul
On 02/25/2015 02:46 AM, Marc Welz wrote:
?progdev mba15_obs2d_2014_Jan_31_1052.bof
So this is the same bof file which sometimes works and sometimes does not ? Or
is this subsequent to some upgrade of the roach ? If it is a sometimes work/not
work issue maybe
you are not marking it executable (chmod +x) on transfer or the transfer is
garbled.
If it is subsequent to an upgrade: Note that at some point we moved to a
different kernel+driver+tcpborphserver combination, which uses a mmap
interface - if you change to that you will have to update both kernel and
tcpborphserver, but for roach1 this is a backport, so probably something for
experts ...
regards
marc
