Hi Adam,
I think your work-around will result in a file from the development
machine being routed directly into the fpga. Is that right?
Does this imply that listbof simply won't work in a soloboot
environment? And that I cannot keep files in flash for programming the
fpga?
Thanks,
Rich
On 7/3/2013 8:39 AM, Adam Barta wrote:
Hi
It might be useful to try this command
In tcpborphserver3
?upload 3000
!upload ok 3000
Then from a local terminal type
gzip -c -9 < some-image.bof | nc -w 2 -q 2 localhost 3000
Regards
Adam
On Wed, Jul 3, 2013 at 2:24 PM, Rich Lacasse <[email protected]
<mailto:[email protected]>> wrote:
Hi Marc,
Thanks for the help. I am now able to transfer bof files to
/usr/bof. However, the katcp does not find them: "?listbof"
simply returns "ok 0". I'll bet it is looking in /boffiles which
does not exist. Is there an easy way around this?
Thanks,
Rich
On 7/3/2013 4:22 AM, Marc Welz wrote:
Hello
cockroach3 / $ ls
bin dev etc lib mnt proc root sbin sys tmp
usr var
On the solobooted filesystem, bof files live in /usr/bof
When I try to create a boffiles directory, I find that the
system does not
allow it (soloboot):
Yes, / is readonly, /usr is writable. We have had cases where
gateware
bus timing
bugs have done antisocial things on the EPB bus of the powerpc
- we
believe that this
can corrupt flash IO, making it essential for a part of the
system to
be readonly to recover
from corruption.
regards
marc
--
*Adam Barta*
c: +27 72 105 8611
e: [email protected] <mailto:[email protected]>
w: www.ska.ac.za <http://www.ska.ac.za>
