Hey guys,
I'm trying to read and write to a ROACH1 using the BORPH filesystem. I
followed the tutorial at
https://safe.nrao.edu/wiki/pub/CICADA/FlashLights/BorphGettingStart.pdf,
but got somewhat different results
root@roach:/boffiles# ./asmls_roach0_2013_Mar_15_1123.bof
^Z
[1]+ Stopped
Hi Ryan,
Try echo -e \x00\x00\x00\x00 > register
Adam
On Mon, Mar 18, 2013 at 9:12 PM, Ryan Monroe wrote:
> Hey guys,
>
> I'm trying to read and write to a ROACH1 using the BORPH filesystem. I
> followed the tutorial at https://safe.nrao.edu/wiki/**
> pub/CICADA/FlashLights/**BorphGettingSt
root@roach:/proc/618/hw/ioreg# echo 0 > ../ioreg_mode
root@roach:/proc/618/hw/ioreg# echo -e \x00\x00\x00\x00 > acc_always_valid
-bash: echo: write error: Invalid argument
root@roach:/proc/618/hw/ioreg# echo -e \x00\x00\x00\x00 >
acc_always_validczx
-bash: acc_always_validczx: No such file or
i assumed the register was a 32bit word but didn't expect you to read x00x
back out! that is werid! have you tried the ?wordread and ?wordwrite
commands from tcpborphserver?
also try echo -ne
to ignore the trailing newline.
maybe there is some borph kernel weridness is there anything
in dmesg?
Hi, Ryan,
On Mar 18, 2013, at 2:21 PM, Ryan Monroe wrote:
> root@roach:/proc/618/hw/ioreg# echo 0 > ../ioreg_mode
> root@roach:/proc/618/hw/ioreg# echo -e \x00\x00\x00\x00 > acc_always_valid
> -bash: echo: write error: Invalid argument
You need to either double up the backslashes or put the \x0
ah yes
echo -ne "\x00\x00\x00\x00" | hd
00 00 00 00
On Mon, Mar 18, 2013 at 11:49 PM, David MacMahon
wrote:
> Hi, Ryan,
>
> On Mar 18, 2013, at 2:21 PM, Ryan Monroe wrote:
>
> > root@roach:/proc/618/hw/ioreg# echo 0 > ../ioreg_mode
> > root@roach:/proc/618/hw/ioreg# echo -e \x00\x00
Hi David, thanks for the response!
I guess I wasn't really sure which ioreg_mode value corresponded to
which, so I just tried them both. So <1=binary> and <0=ascii>. Armed
with that knowledge (plus your mad BASH chops), I successfully
controlled some registers through BORPH. Still no luck in
You can only use tcpborphserver's katcp interface if you program the FPGA
through that too. If you program the FPGA "behind its back" (ie from the
command line), then you can't read/write registers over katcp.
I strongly advise you to use katcp in your new design, because BORPH is not
provided
It's okay, I don't need compatibility this time around. I just want
need performance better than what a telnet to the ROACH can give me.
Future revisions of this project will be on a custom board anyways
Thanks for all of your (collective) help. Problem solved... for now ;-)
--Ryan
On
9 matches
Mail list logo