Hi Jack， Thank you very much for your reply! I benefited a lot from your reply. I operated as you said, using Mlib-Devel-roach2,and these problems were solved.
BW， Kuma 在2022年8月26日星期五 UTC+8 16:32:15<[email protected]> 写道： > Hi Kuma, > > The two register options give you the ability to try to improve the timing > performance of the RAM by adding extra internal register stages in its > implementation. > With neither of those options checked, the RAM has a latency of 1 (after > presenting an address on the input, the value stored at that address is > presented on the data output 1 cycle later). With one or both of those > options checked, this increases to 2 or 3 cycles. > If the previous version of the block didn't have these options, then to > get the same behaviour with the new block you should leave these options > unchecked. The default latency has always been 1 (in fact the new AXI-based > platforms don't even support the larger latencies....). > > Your second error looks like the shared_bram blocks within some snapshot > blocks in your model need updating. Hopefully the library version of the > snapshot is OK, so that you could just replace the entire snapshot block to > fix the error underneath it in the shared_ram. > > In theory, you can update all the blocks in your model with (in the matlab > prompt) `update_casper_blocks(bdroot)` . You can also update a specific > block (which you have selected by clicking in simulink) with > `update_casper_block(gcs)`. (If you plan on doing this, do make sure you > save/backup your design before allowing an automated script to mess with > it!). > > As a general note, for ROACH2 you should be using the roach2 branch of > mlib_devel (which I assume you are) -- > https://github.com/casper-astro/mlib_devel/tree/roach2 > > Hope that helps a little, > > Jack > > On Fri, 26 Aug 2022 at 06:52, Bartholemew Kuma <[email protected]> wrote: > >> Hi all, >> >> I'm using Shared_BRAM block and there's something I don't understand. >> >> I don't quite understand when to use two of these parameters: Register >> primitive output and Register core output. >> I was compiling the 2012 Roach2 tutorial 2 (10GBE). >> The system prompts me that there is a problem with this block, so I >> replace it with the current version of Share_BRAM block, which can generate >> a .bof file at this time. >> But with these two extra parameters, it's not clear if you should check >> them or not. >> >> The second problem is that I am prompted for this during the compilation >> process: >> Warning: Shared BRAM block "tut2b824/snap_10gbe_tx/bram_lsb" is out of >> date (needs its >> link restored) >> > In shared_bram_mask at 70 >> In gen_xps_files at 212 >> In casper_xps>run_Callback at 163 >> In casper_xps at 88 >> In >> @(hObject,eventdata)casper_xps('run_Callback',hObject,eventdata,guidata(hObject)) >> >> >> Warning: Shared BRAM block "tut2b824/snap_10gbe_tx/bram_lsb" is out of >> date (needs its >> link restored) >> > In shared_bram_mask at 126 >> In gen_xps_files at 212 >> In casper_xps>run_Callback at 163 >> In casper_xps at 88 >> In >> @(hObject,eventdata)casper_xps('run_Callback',hObject,eventdata,guidata(hObject)) >> >> >> Warning: Shared BRAM block "tut2b824/snap_10gbe_tx/bram_lsb" is out of >> date (needs its >> link restored) >> > In shared_bram_mask at 126 >> In gen_xps_files at 212 >> In casper_xps>run_Callback at 163 >> In casper_xps at 88 >> In >> @(hObject,eventdata)casper_xps('run_Callback',hObject,eventdata,guidata(hObject)) >> >> >> Warning: Shared BRAM block "tut2b824/snap_10gbe_tx/bram_lsb" is out of >> date (needs its >> link restored) >> > In shared_bram_mask at 139 >> In gen_xps_files at 212 >> In casper_xps>run_Callback at 163 >> In casper_xps at 88 >> In >> @(hObject,eventdata)casper_xps('run_Callback',hObject,eventdata,guidata(hObject)) >> >> >> Warning: Shared BRAM block "tut2b824/snap_10gbe_tx/bram_lsb" is out of >> date (needs its >> link restored) >> > In shared_bram_mask at 139 >> In gen_xps_files at 212 >> In casper_xps>run_Callback at 163 >> In casper_xps at 88 >> In >> @(hObject,eventdata)casper_xps('run_Callback',hObject,eventdata,guidata(hObject)) >> >> How can I solve this problem? >> I would appreciate it if someone told me! >> >> BW, >> Kuma >> >> -- >> 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/9b27af07-6913-49f8-a888-93bf80f74f3fn%40lists.berkeley.edu >> >> <https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/9b27af07-6913-49f8-a888-93bf80f74f3fn%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/38907d01-e2bf-42ef-a78a-5c862f5756e4n%40lists.berkeley.edu.
