Thanks Marc,
It seems I might have sent you the wrong output? I agree, that output
looks like things must have worked.
Here's my latest output:
?progdev mba15_obs2d_2014_Jan_31_1052.bof
#log debug 2130698889868 roach.mba
terminating\_subprocesses\_matching\_type\_1
#log debug 2130698889868 roach.mba
0\_terminated\_processes\_need\_to\_be\_collected
#log trace 2130698889869 roach.mba
attempting\_to\_terminate\_child\_process\_borph
#log debug 2130698889870 roach.mba
0\_terminated\_processes\_need\_to\_be\_collected
#log debug 2130698889870 roach.mba system\_deprogrammed
#log debug 2130698889870 roach.mba
attempting\_to\_program\_/boffiles/mba15_obs2d_2014_Jan_31_1052.bof
#log error 2130698920112 roach.mba
timed\_out\_while\_waiting\_for\_fpga\_status\_to\_change:\_No\_such\_file\_or\_directory
#log warn 2130698920115 roach.mba
timed\_out\_while\_waiting\_for\_status\_register,\_but\_returning\_ok\_because\_ioreg\_exists
#log warn 2130698920117 roach.mba
collected\_process\_id\_589\_with\_status\_0x4700
#log warn 2130698920120 roach.mba borph\_process\_exited
#log warn 2130698920122 roach.mba borph\_exited,\_but\_no\_image\_to\_clear
#log fatal 2130698920124 roach.mba unable\_to\_program\_gateware
!progdev fail program
On 02/24/2015 02:09 PM, Mar
Hello
Thanks Marc,
Good suggestion. I'd hat the log level set to debug, but hadn't thought
of lowering it. I get a lot of output, most of which I don't quite
understand (see below). At this point, I probably should add that we
are running a tcpborphserver with a mode we created for our own system,
'mba':
So
?progdev mba15_obs2d_2014_Jan_31_1052.bof
...
!progdev ok 537
the "!progdev ok" suggests that it managed to program the FPGA
successfully - there should be a borph process with pid 537
running - you should now be able to read/write the registers ?
#log error 151615780430 roach.mba
timed\_out\_while\_waiting\_for\_fpga\_status\_to\_change:\_No\_such\_file\_or\_directory
This I think relates to a particular status register which
certain revisions of the gateware supplied to show if the programming
completed - it is unclear if this is even a problem in your case, but I
probably don't the details completely. What matters is if you can see the
registers then the programming should have worked out - if you type
"?listdev" you can check your register set, if that disappears after
a short while then you might have problems with the elf executable
embedded in your .bof file
regards
marc
