Hi Aravind, The pull request in casper-astro/mlib_devel was just approved - try that and let me know, thanks. This should sort your issue out.
https://github.com/casper-astro/mlib_devel Kind regards, Adam Isaacson South African Radio Astronomy Observatory (SARAO) Hardware Manager Cell: (+27) 825639602 Tel: (+27) 215067300 email: aisaac...@ska.ac.za On Wed, Apr 15, 2020 at 8:41 AM Adam Isaacson <aisaac...@ska.ac.za> wrote: > Hi Aravind, > > I suspect the issue lies with your snap shot (accum0_snap_ss) - it is 64 > bits wide now and the others are 32 bit. You are probably using a version > of the toolflow and xml2vhdl repo that does not support asymmetric bram > usage - I just confirmed that. I would suggest you verify this, by > installing the following mlib_devel: > > https://github.com/ska-sa/mlib_devel > <https://github.com/ska-sa/mlib_devel> (devel branch) > > You will need to do the following: > > 1) git clone https://github.com/ska-sa/mlib_devel.git > 2) git checkout devel > 3) cd <path to>/mlib_devel > 4) follow install in > https://casper-toolflow.readthedocs.io/en/latest/src/Installing-the-Toolflow.html > > You will notice there is a pull request on casper-astro/mlib_devel > awaiting a review. I will discuss with Jack this evening during our CASPER > meeting. Once that is approved then you will be able to use your slx file > as is - https://github.com/casper-astro/mlib_devel/pull/123. We were > unable to support any BRAM size other than 32 bits originally. I am now > pleased to report we can support all sizes again. > > Kind regards, > > Adam Isaacson > South African Radio Astronomy Observatory (SARAO) > Hardware Manager > Cell: (+27) 825639602 > Tel: (+27) 215067300 > email: aisaac...@ska.ac.za > > > > On Tue, Apr 14, 2020 at 8:56 PM Aravind Venkitasubramony < > aravind.venkitasubram...@colorado.edu> wrote: > >> Thanks for that fix,Adam. >> >> I understand what I did wrong on 2,3 and 4. I am still unclear on 1. I >> will dig deeper to see what I did there to break it. >> >> The compilation went through and I generated the fpg file, but when I run >> the python code, I get an error in the line where it is uploading the fpg >> file to the ram and programming. I am not sure what error this is >> corresponding to. I ran the python file line by line as well in the >> terminal and also see the same error. I downloaded the py file from github. >> From what I can understand, there is no need to change anything in here. >> >> Connecting to Red Pitaya: rp-F07516.local >> Uploading: >> /home/cet/RP_work/models/rp_tut3/tut_spec_adam/outputs/tut_spec_adam_2020-04-14_1158.fpg >> Traceback (most recent call last): >> File "tut_spec.py", line 23, in <module> >> fpga.upload_to_ram_and_program(file_fpg) >> File "build/bdist.linux-x86_64/egg/casperfpga/casperfpga.py", line 319, >> in upload_to_ram_and_program >> File "build/bdist.linux-x86_64/egg/casperfpga/casperfpga.py", line 747, >> in get_system_information >> File "build/bdist.linux-x86_64/egg/casperfpga/casperfpga.py", line 588, >> in _create_memory_devices >> File "build/bdist.linux-x86_64/egg/casperfpga/snap.py", line 59, in >> from_device_info >> RuntimeError: accum0_snap_ss has mask length_bytes 32768 bytes, but mem >> map length_bytes 16384 bytes >> >> On Tue, Apr 14, 2020 at 3:12 AM Adam Isaacson <aisaac...@ska.ac.za> >> wrote: >> >>> Hi Aravind, >>> >>> I have found the following issues: >>> >>> 1) The ADC yellow block was modified and the link to the library was >>> broken. This meant that the number of bits parameter did not propagate down >>> to the cast blocks and so they were still set at 10 bits. I see you added >>> some simulation blocks, but probably broke the links in the process. >>> >>> 2) The constant xilinx blocks for the imaginary inputs to the FFT were >>> set at 10 bits and not 14 bits. >>> >>> 3) The accumdat_snap snapshot had the incorrect number of bits for the >>> "in_Ch_acc". This should not have been modified, as it is not influenced by >>> the ADC number of bits. >>> >>> 4) I fixed the bit growth through your system - hopefully this is >>> correct now. >>> >>> Please see attached modified version. It should compile now. >>> >>> Kind regards, >>> >>> Adam Isaacson >>> South African Radio Astronomy Observatory (SARAO) >>> Hardware Manager >>> Cell: (+27) 825639602 >>> Tel: (+27) 215067300 >>> email: aisaac...@ska.ac.za >>> >>> >>> >>> On Mon, Apr 13, 2020 at 10:49 PM Aravind Venkitasubramony < >>> aravind.venkitasubram...@colorado.edu> wrote: >>> >>>> Hi Adam >>>> >>>> I revisited the spectrometer tutorial after finishing the second >>>> tutorial. I have attached the slx file along with. I have modified >>>> everything I could understand but I still get the following error while >>>> compiling >>>> >>>> The input type propagated to this block did not match the specified >>>> type. >>>> Expected Type: Fix_14_0 >>>> Actual Type: Fix_10_0 >>>> >>>> It would be great if you could take a look and tell me what I am doing >>>> wrong. >>>> >>>> On Tue, Apr 7, 2020 at 2:22 AM Adam Isaacson <aisaac...@ska.ac.za> >>>> wrote: >>>> >>>>> Dear Aravind, >>>>> >>>>> You can do any tutorial in any order, but as a beginner it is better >>>>> to do it in order. The spectrometer tutorial should be able to work for a >>>>> 14 bit board, but if you go through the steps you will see that the >>>>> spectrometer bit growth is based on an input of 10 bits. You would need to >>>>> change that based on an input of 14 bits. The python script would also >>>>> need >>>>> to be updated to handle 14 bits or so I think. This could be why you are >>>>> experiencing these issues reading back from the snapshots. >>>>> >>>>> I would have to see your script and your slx file that you have >>>>> updated in order to see if they are correct. Send that to me and I will >>>>> glance over it. >>>>> >>>>> Kind regards, >>>>> >>>>> Adam Isaacson >>>>> South African Radio Astronomy Observatory (SARAO) >>>>> Hardware Manager >>>>> Cell: (+27) 825639602 >>>>> Tel: (+27) 215067300 >>>>> email: aisaac...@ska.ac.za >>>>> >>>>> >>>>> >>>>> On Tue, Apr 7, 2020 at 1:04 AM Aravind Venkitasubramony < >>>>> arve9...@colorado.edu> wrote: >>>>> >>>>>> I guess I have to complete the tutorial 2 first before jumping on the >>>>>> third one to get an answer why. I will see if that helps. >>>>>> >>>>>> On Monday, April 6, 2020 at 4:35:34 PM UTC-6, Aravind >>>>>> Venkitasubramony wrote: >>>>>>> >>>>>>> Sorry for the confusion. I meant the wide(ish) spectrometer tutorial >>>>>>> 3 >>>>>>> >>>>>>> On Monday, April 6, 2020 at 3:58:50 PM UTC-6, Aravind >>>>>>> Venkitasubramony wrote: >>>>>>>> >>>>>>>> Does the spectrometer tutorial work with the 14 bit Red Pitaya >>>>>>>> board as well? The tutorial mentions the 10 bit board, but I am using >>>>>>>> the >>>>>>>> 14 bit board version. >>>>>>>> >>>>>>>> Also, going through the spectrometer tutorial with the 14 bit >>>>>>>> board, I get the following message at the terminal when executing the >>>>>>>> python command. Can someone help me with what might be the issue here? >>>>>>>> >>>>>>>> Connecting to Red Pitaya: rp-F07516.local >>>>>>>> Uploading: tut_spec.fpg >>>>>>>> These are the devices in your design ... >>>>>>>> ['acc_cnt', 'acc_len', 'accum0_snap_ss_bram', >>>>>>>> 'accum0_snap_ss_ctrl', 'accum0_snap_ss_status', 'accum1_snap_ss_bram', >>>>>>>> 'accum1_snap_ss_ctrl', 'accum1_snap_ss_status', >>>>>>>> 'accumdat_snap_ss_bram', >>>>>>>> 'accumdat_snap_ss_ctrl', 'accumdat_snap_ss_status', 'adc_dv', >>>>>>>> 'adc_sample_cnt', 'adc_voltage_snap_ss_bram', >>>>>>>> 'adc_voltage_snap_ss_ctrl', >>>>>>>> 'adc_voltage_snap_ss_status', 'fft_sync_inc0', 'fft_sync_inc1', >>>>>>>> 'reg_cntrl', 'snap_gap', 'sync_cnt', 'sync_reg', 'sys_block', >>>>>>>> 'sys_board_id', 'sys_clkcounter', 'sys_rev', 'sys_rev_rcs', >>>>>>>> 'sys_scratchpad'] >>>>>>>> Traceback (most recent call last): >>>>>>>> File "tut_spec.py", line 38, in <module> >>>>>>>> spec0=fpga.snapshots.accum0_snap_ss.read(arm=False)['data'] >>>>>>>> File "/usr/local/lib/python2.7/dist-packages/casperfpga/snap.py", >>>>>>>> line 227, in read >>>>>>>> rawdata, rawtime = self.read_raw(**kwargs) >>>>>>>> File "/usr/local/lib/python2.7/dist-packages/casperfpga/snap.py", >>>>>>>> line 333, in read_raw >>>>>>>> bram_dmp['length'] / (self.width_bits / 8))) >>>>>>>> RuntimeError: accum0_snap_ss.read_uint() - expected 16384 bytes, >>>>>>>> got 32 >>>>>>>> >>>>>>>> -- >>>>>> 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/77f027f3-c878-43c1-ab28-b77f3582d4f8%40lists.berkeley.edu >>>>>> <https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/77f027f3-c878-43c1-ab28-b77f3582d4f8%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/CADTJ%3DnF22fvRt-WuwViLJ1qmAwEE4nPkKaieMXX7-HXKpXoaMQ%40mail.gmail.com >>>>> <https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CADTJ%3DnF22fvRt-WuwViLJ1qmAwEE4nPkKaieMXX7-HXKpXoaMQ%40mail.gmail.com?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/CAFQ_oEiET5aZo-n_J%2BaxxYfOLdXC3x7kh3L8oOXnYsmchZgRYA%40mail.gmail.com >>>> <https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CAFQ_oEiET5aZo-n_J%2BaxxYfOLdXC3x7kh3L8oOXnYsmchZgRYA%40mail.gmail.com?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/CADTJ%3DnF0Z9%3DPYeAjQsN9v3G_F5KCC7rksB59Tv9RSpr10K3BdA%40mail.gmail.com >>> <https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CADTJ%3DnF0Z9%3DPYeAjQsN9v3G_F5KCC7rksB59Tv9RSpr10K3BdA%40mail.gmail.com?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/CAFQ_oEh%2B9Jq3%2BTyn3bis3qU%3D1jRu2HwzE-3Q-JKGO%3D41FwqLXg%40mail.gmail.com >> <https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CAFQ_oEh%2B9Jq3%2BTyn3bis3qU%3D1jRu2HwzE-3Q-JKGO%3D41FwqLXg%40mail.gmail.com?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/CADTJ%3DnHn%3DrgmvaraUK58AY4WJAaOVaV48DK-J8_9JfOTcHSmTw%40mail.gmail.com.
