Hi Adam, Yes, I built the slx files and generated the fpg files for the first two tutorials.
For the third tutorial, I first opened the slx file in Simulink and compiled it but got an error when I tried to upload and program. Then I tried updating the model as described under "Updating an Existing Toolfow Installation" using update_casper_blocks(bdroot) before compiling again but got the same error report. Finally, I tried using the fpg file provided which also resulted in the same error. Thanks, Paul. <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link> <#m_7518126369254170950_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> On Wed, Aug 26, 2020 at 3:49 PM Adam Isaacson <[email protected]> wrote: > Hi Paul, > > Thanks for your email. It looks like your mlib_devel and casperfpga > version are fairly recent and contain the BRAM 32 bit fixes that we made. > It seems I committed this particular fpg file 9 months ago, so it might not > of contained all these fixes then. I am quite certain it was working for > me, but maybe I committed the incorrect file at the time. You say the first > two tutorials were successful and I know the second tutorial has a > snapshot, so your build environment must work. I am assuming you build the > slx files and generated the fpg files for the first two tuts, of course. > Correct me if wrong! > > Please try and rebuild the spectrometer slx file and test the fpg > generated file. Let me know if you get the same issue. If you don't then I > must have checked a suspect fpg file in this repo and we can easily fix > that, if that is the case. > > Kind regards, > > Adam Isaacson > South African Radio Astronomy Observatory (SARAO) > Hardware Manager > Cell: (+27) 825639602 > Tel: (+27) 215067300 > email: [email protected] > > > > On Mon, Aug 24, 2020 at 10:52 PM Paul Akumu <[email protected]> wrote: > >> Hello, >> >> I am new to the Toolfow and I have been following the Red Pitaya >> tutorials. I have Matlab 2018 and Vivado 2019 installed. I was able to >> follow the first two tutorials which compiled and uploaded via casperfpga >> successfully. When following the wide band spectrometer tutorial I tried to >> program the red Pitaya with the fpg file provided for the tutorial here >> <https://github.com/casper-astro/tutorials_devel/tree/master/red_pitaya/tut_spec>, >> but got the following response/error; >> >> Connecting to Red Pitaya: 192.168.200.151 >> 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 >> >> I also tried compiling the .slx file and got the same error while trying >> to upload and program. >> >> The version of casperfpga and mlib_devel are as follows: >> mlib_devel commit id = a9e87d994cf5f512fa0ea555ec7495d8dedc0855 >> caspserfpga commit id = c2258ea014340a7376d504e7128198ed2cfa5442 >> >> What could be the problem? >> >> Thanks, >> Paul. >> >> >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "[email protected]" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/ac1e497b-3ebd-420c-a6c2-41d0beef7102n%40lists.berkeley.edu >> <https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/ac1e497b-3ebd-420c-a6c2-41d0beef7102n%40lists.berkeley.edu?utm_medium=email&utm_source=footer> >> . >> > -- > You received this message because you are subscribed to the Google Groups " > [email protected]" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CADTJ%3DnHmA%2B%2BOVoa53Uqy%3D7f7EouqYFo%2Bz-n_hPiCOtDau9Tmxw%40mail.gmail.com > <https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CADTJ%3DnHmA%2B%2BOVoa53Uqy%3D7f7EouqYFo%2Bz-n_hPiCOtDau9Tmxw%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> -- You received this message because you are subscribed to the Google Groups "[email protected]" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CAADMYvW2YqjTavpsTvD%3DT%3Dq6%3DApSW3_OVTdL_onyj7tq1U1Ujw%40mail.gmail.com.
