Hello
A small correction - this shouldn't really affect your debugging
effort, but might be
important for people who would be interested in knowning more fpg file
details. I wrote:
> The programming step is unfortunately a bit complicated - the start of
> an fpg file is actually a set of
> katcp commands you can copy into the telnet session ("?register xxx
> ...") while the bitstream is sent across afterwards
> on a separate port using the "?uploadbin" request using the content of
> the fpg file after the "?quit" and where it turns into binary.
I got the order wrong. The bitstream is programmed beforehand, not afterwards.
This weird inversion has a reason: It means an fpg file not only can define
registers with the "?register" command, but also execute things like "?write"
or "?wordwrite".
So for designs which don't require any conditionals (if, while) or
feedback, then
adding the the right commands in the fpg file mean that it is possible
to launch an instrument by just
running the fpg file - a file which can be marked excutable on the
board. No client-side
libraries needed.
fpg files can be edited with an editor which does not mangle binary
(vim -b should work)
or, even better, generated programatically with a number of "echo
?command >> file.fpg"
and a final "cat bitstream >> file.fpg", making sure that the final
command before the bitstream
is a "?quit".
Running "less some-existing.fpg" should show you the commands without
too much trouble, and
once you see the "?quit" you have reached the final one.
regards
marc
--
The use of google poses numerous grave privacy risks
Disclaimer
The information contained in this communication from the sender is
confidential. It is intended solely for use by the recipient and others
authorized to receive it. If you are not the recipient, you are hereby notified
that any disclosure, copying, distribution or taking action in relation of the
contents of this information is strictly prohibited and may be unlawful.
--
You received this message because you are subscribed to the Google Groups
"casper@lists.berkeley.edu" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to casper+unsubscr...@lists.berkeley.edu.
To view this discussion visit
https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CAGrhWaQXq-1f7tc0x-56YXoie71v54fgVvPT-s6UQUP5eKCiYg%40mail.gmail.com.
