Hi Jack, I did try installing casperfpga on the red pitaya, but it appears that one of the libraries (progska, if I recall correctly) requires 64-bit. It was giving me ELFCLASS64 error. Not sure if there's a work around, but I'm pretty comfortable writing C code to run on the red pitaya to manage the registers, so that's the direction I've gone.
Thanks! Sean On Monday, June 1, 2020 at 3:59:13 AM UTC-6, Jack Hickish wrote: > > Hi Sean, > > Just to explicitly add to wes's advice - in addition to the telnet > interface on localhost, you can "just" install full blown casperfpga to > your red pitaya, and connect via localhost using the scripts you already > have. Unless your performance requirements are such that python is out of > the question, this is probably the easiest thing to do. > > Cheers > Jack > > > On Sun, 31 May 2020, 10:45 pm Sean Mckee, <semc...@colorado.edu > <javascript:>> wrote: > >> Hi Wesley, >> >> Thank you, that's what I was looking for! >> >> On Sunday, May 31, 2020 at 12:54:31 PM UTC-6, wesley wrote: >>> >>> Hi Sean, >>> >>> These are all good questions and Ill try to point you in the right >>> direction. >>> >>> So if you followed this tutorial to setup your red pitaya: >>> https://casper-toolflow.readthedocs.io/projects/tutorials/en/latest/tutorials/redpitaya/red_pitaya_setup.html#running-the-script-on-a-preloaded-rp-sd-card >>> You should have tcpborphserver installed on the PS. You can telnet into >>> tcpborphserver and issue register read and writes that way. ie you could >>> telnet into tcpborphserver on localhost form the RP using a python script >>> and run your tasks that way. If I remember correctly tcpboprhserver can >>> address a register by name so you shouldnt need to worry about memory maps, >>> but if you are you can look at the fpg file that you uploaded and the >>> header will contain the memory map. You can also see the memory map in a >>> file called coreinfo.tab in your build directory. >>> >>> Hope this helps. >>> >>> Wesley New >>> South African SKA Project >>> +2721 506 7300 >>> www.ska.ac.za >>> >>> >>> >>> >>> On Sun, May 31, 2020 at 7:56 PM Sean Mckee <semc...@colorado.edu> wrote: >>> >>>> Hi all, >>>> >>>> I'm trying to determine how I would go about finding/using the >>>> addresses of the memory mapped registers being used by the FPGA, from the >>>> PS side of the Red Pitaya. For example, in the spectrometer tutorial, >>>> there >>>> are several registers used to control the design, and others to pull data >>>> out from the design. If I access the Red Pitaya from my computer using the >>>> casperfpga.py module, these registers are all conveniently named and the >>>> python module has tools to read data from snap blocks, write to the reset >>>> and trigger registers, etc. >>>> >>>> Is there a convenient way to have this same level of control on the red >>>> pitaya itself? I would like to write code that runs on the PS to monitor >>>> these registers and handle the data output. From what I can currently >>>> find, >>>> I will need to open the /dev/mem file and use the mmap() command. But how >>>> do I find out which physical register corresponds to which simulink block? >>>> And I assume that even a minor update to the simulink design could result >>>> in the registers being moved around, so what is a good way to account for >>>> this? >>>> >>>> Currently, I am trying to trace what happens when I call casperfpga >>>> commands from my computer. I understand the parsing of the commands and >>>> the >>>> hand off to tcpborphserver, but I can't seem to unravel what is happening >>>> when the red pitaya receives these commands. I'm assuming this code is >>>> somewhere in the katcp library (https://github.com/ska-sa/katcp)? >>>> >>>> Hopefully someone knows of a good resource to fill in my knowledge gaps. >>>> >>>> Thanks! >>>> Sean >>>> >>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "cas...@lists.berkeley.edu" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to cas...@lists.berkeley.edu. >>>> To view this discussion on the web visit >>>> https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/7fcb1398-42a3-45a0-8da5-1801f2274d71%40lists.berkeley.edu >>>> >>>> <https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/7fcb1398-42a3-45a0-8da5-1801f2274d71%40lists.berkeley.edu?utm_medium=email&utm_source=footer> >>>> . >>>> >>> -- >> You received this message because you are subscribed to the Google Groups >> "cas...@lists.berkeley.edu <javascript:>" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to cas...@lists.berkeley.edu <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/c4f0d757-d3ca-431f-b1de-f27392f68b3f%40lists.berkeley.edu >> >> <https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/c4f0d757-d3ca-431f-b1de-f27392f68b3f%40lists.berkeley.edu?utm_medium=email&utm_source=footer> >> . >> > -- 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 on the web visit https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/4246c7dd-1f25-46ab-8269-180a92c0a07f%40lists.berkeley.edu.
