You don't need to run the *_init.m files yourself, matlab does that for you.
Click the "set path" button in matlab and make sure you see the directory
that will be something like .../mlib_devel/casper_library
I suspect that you don't have your startsg.local or startup.m
at the matlab prompt, what does
getenv('MLIB_DEVEL_PATH')
return?
It should point at your mlib_devel directory.
Glenn
On Thu, Nov 10, 2016 at 4:56 PM, Alec Josaitis <josai...@umich.edu> wrote:
> Dear Glenn,
>
> In trying to get to the root of this issue, I've started digging through
> the Casper Library files. In what seems to be the principle .mdl file,
> "casper_library.mdl", I notice that the first actions done are to load
> other .mdl files, such as "casper_library_ffts.mdl", and
> "casper_library_pfbs.mdl", and I assume that inside that inside these .mdl
> files are where the respective library blocks are instantiated. Inside the
> casper_library folder of my mlib_devel, I do indeed see the .dl files
> labelled ""casper_library_ffts". "casper_library_pfbs", etc. However, I do
> NOT see one labelled "casper_library_bus", but this is what is called in
> the "casper_library.mdl" file.
>
> I do see, however, a file called 'casper_library_bus_init.m'. This,
> according to the mlib_devel Github, is supposed to " Save auto-generated
> models as MDL files
> <https://github.com/casper-astro/mlib_devel/commit/3cbd5f97ab1bf4f0b885731d8810759ea15fe912>".
> When I tried running this script in Matlab (not sure if I should do this,
> but I did...), I receive the following errors:
>
> >> casper_library_bus_init
> Warning: Error evaluating 'PreSaveFcn' callback of block_diagram
> 'casper_library_bus'.
> Warning: error opening '/casper_library/casper_library_bus_init'
> Error using save_system (line 38)
> An error or warning occurred during a callback while saving
> '/casper_library/casper_library_bus.slx'. The previously saved version of
> this file (if any) has not been
> changed
>
> Error in casper_library_bus_init (line 285)
> filename = save_system(mdl,[getenv('MLIB_DEVEL_PATH'),
> '/casper_library/', 'casper_library_bus']);
>
> Best,
> Alec
>
> On Thu, Nov 10, 2016 at 4:26 PM, Alec Josaitis <josai...@umich.edu> wrote:
>
>> Dear Glenn,
>>
>> I've never been able to easily browse the DSP blockset in the Simulink
>> library browser, like I can the XPS blockset. The photos below will explain
>> what I mean, but for posterity (in writing), I will say that the sidebar of
>> the Simulink browser easily allows me to peruse the XPS blocks, which
>> appear by name, but the DSP blockset never generates images, and Simulink
>> says the blockset contains "No blocks", but nevertheless I can open the DSP
>> blockset library and all of the blocks/sub-libraries (*except
>> "Downconverter" and "Bus") * are there, empty, but can still be
>> implemented into a model. When I click on the Casper DSP "Bus" library to
>> see what is inside, the following error appears:
>>
>> --> Error evaluating 'OpenFcn' callback of SubSystem block
>> 'casper_library/Bus'. -->Undefined function or variable
>> 'casper_library_bus'.
>> So, it looks as though I don't actually have access to the bus library.
>> Do you have suggestions on how to fix that, aside from re-downloading the
>> entire mlib_devel library?
>>
>> Best,
>> Alec
>>
>> On Wed, Nov 9, 2016 at 10:03 PM, G Jones <glenn.calt...@gmail.com> wrote:
>>
>>> Hi Alec,
>>> I was working from memory and got it wrong: the library paths are in
>>> startup.m but shouldn't need to be modified. Are you running ./startsg in
>>> your casper toolflow git directory? When you open the simulink library
>>> browser, can you browse to CASPER DSP Blockset -> bus ?
>>> Glenn
>>>
>>> On Wed, Nov 9, 2016 at 6:08 PM, G Jones <glenn.calt...@gmail.com> wrote:
>>>
>>>> Something is not quite right with your library path setup. Did you
>>>> modify the startsg.sh local script to properly point to your casper
>>>> libraries? You definitely should have the casper bus library if things are
>>>> set up properly.
>>>>
>>>> Glenn
>>>> On Nov 9, 2016 5:59 PM, "Alec Josaitis" <josai...@umich.edu> wrote:
>>>>
>>>>> Dear Glenn,
>>>>>
>>>>> Yes, update_casper_blocks appears to run succesfully. First I ran it
>>>>> inasmuch as it said at the end "done updating ____ blocks in <filename>",
>>>>> but it does issue warnings at some points. See below.
>>>>>
>>>>> First, I tried updating my library, and at some point received this:
>>>>> updating block xps_library/Shared BRAM/mem/sim_munge_in...
>>>>> Simulink:Libraries:RefModificationViolation: Attempt to modify block
>>>>> in a linked subsystem. This can only be done by the block or its parent
>>>>> through their mask initialization code
>>>>> Backtrace 1: reuse_block:51
>>>>> Backtrace 2: munge_init:131
>>>>> Backtrace 3: shared_bram_mask:119
>>>>> Backtrace 4: update_casper_block:161
>>>>> Backtrace 5: update_casper_blocks:107
>>>>>
>>>>> Now, after updating my library, I ran the script on the .slx file
>>>>> (poco_wide_12_r316_new); it also completes successfully but only after
>>>>> providing these warning messages:
>>>>> updating block poco_wide_12_r316_new/fft_wideband_real...
>>>>> loading library casper_library_ffts
>>>>> MATLAB:MException:MultipleErrors: Error due to multiple causes.
>>>>> Backtrace 1: reuse_block:51
>>>>> Backtrace 2: fft_stage_n_init:287
>>>>> Backtrace 3: reuse_block:51
>>>>> Backtrace 4: biplex_core_init:173
>>>>> Backtrace 5: reuse_block:51
>>>>> Backtrace 6: fft_biplex_real_4x_init:235
>>>>> Backtrace 7: reuse_block:51
>>>>> Backtrace 8: fft_wideband_real_init:257
>>>>> Backtrace 9: update_casper_block:161
>>>>> Backtrace 10: update_casper_blocks:107
>>>>>
>>>>> I then updated my system diagram as you recommended, and received the
>>>>> following errors:
>>>>>
>>>>> Error in 'poco_wide_12_r316_new/fft_wideband_real/fft_biplex_real_4x':
>>>>> Initialization commands cannot be evaluated.
>>>>>
>>>>> Caused by:
>>>>> Error in 'poco_wide_12_r316_new/fft_wideband_real/fft_biplex_real_4x/
>>>>> biplex_core': Initialization commands cannot be evaluated.
>>>>> Error in 'poco_wide_12_r316_new/fft_wideband_real/fft_biplex_real_4x/
>>>>> biplex_core/fft_stage_1': Initialization commands cannot be evaluated.
>>>>> Error due to multiple causes.
>>>>> Unable to load block diagram 'casper_library_bus'
>>>>> There is no block named 'casper_library_bus/bus_single_port_ram'
>>>>> Do you have a recommendation on how to fix this error?
>>>>>
>>>>>
>>>>> Best,
>>>>> Alec
>>>>>
>>>>> On Mon, Nov 7, 2016 at 10:03 PM, G Jones <glenn.calt...@gmail.com>
>>>>> wrote:
>>>>>
>>>>>> Hi Alec,
>>>>>> Before running casper_xps, update your system diagram (Simulation
>>>>>> menu -> Update Diagram).
>>>>>> That should pop up messages indicating where the errors are.
>>>>>> The error messages you copied sound like there is still some
>>>>>> incompatibility between the model and your libraries. Did
>>>>>> update_casper_blocks run successfully?
>>>>>>
>>>>>> Glenn
>>>>>>
>>>>>> On Mon, Nov 7, 2016 at 6:39 PM, Alec Josaitis <josai...@umich.edu>
>>>>>> wrote:
>>>>>>
>>>>>>> Dear All,
>>>>>>>
>>>>>>> My apologies, above I meant to include the following hyperlink when
>>>>>>> I stated "...this .mdl
>>>>>>> <https://github.com/casper-astro/tutorials_devel/blob/master/tut4/poco_wide_12_r316_new.mdl.tar.gz>".
>>>>>>> Also, to clarify, I am indeed using the tutorial- recommended versions
>>>>>>> of
>>>>>>> software: Xilinx System Generator 14.7 and MATLAB 2012b.
>>>>>>>
>>>>>>> Best,
>>>>>>> Alec
>>>>>>>
>>>>>>> On Mon, Nov 7, 2016 at 6:34 PM, Alec Josaitis <josai...@umich.edu>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Dear Glenn and Jack,
>>>>>>>>
>>>>>>>> Thanks for the response. I've re-cloned mlib_devel and checked-out
>>>>>>>> the proper version ( 4c7ba5efb4
>>>>>>>> <https://github.com/casper-astro/mlib_devel/commit/4c7ba5efb421fda1cec0640cf0e3b830a9987640>).
>>>>>>>> I then re-downloaded, and un-tarred this .mdl, saved is as a .slx, and
>>>>>>>> then
>>>>>>>> opened it in matlab to run update_casper_blocks(bdroot).
>>>>>>>> I've copied below the errors that appear. Also, I should note there
>>>>>>>> are no .log files in any of the subdirectories inside the directory
>>>>>>>> created
>>>>>>>> by casper_xps.
>>>>>>>>
>>>>>>>> >> casper_xps
>>>>>>>> Detected Linux OS
>>>>>>>> #############################
>>>>>>>> ## System Update ##
>>>>>>>> #############################
>>>>>>>> MATLAB:MException:MultipleErrors: Error due to multiple causes.
>>>>>>>> Backtrace 1: reuse_block:51
>>>>>>>> Backtrace 2: fft_stage_n_init:287
>>>>>>>> Backtrace 3: reuse_block:138
>>>>>>>> Backtrace 4: biplex_core_init:173
>>>>>>>> Backtrace 5: reuse_block:138
>>>>>>>> Backtrace 6: fft_biplex_real_4x_init:235
>>>>>>>> Backtrace 7: gen_xps_files:203
>>>>>>>> Backtrace 8: run_Callback:155
>>>>>>>> Backtrace 9: casper_xps:88
>>>>>>>> Backtrace 10: @(hObject,eventdata)casper_xps
>>>>>>>> ('run_Callback',hObject,eventdata,guidata(hObject)):0
>>>>>>>> Simulink:Masking:Bad_Init_Commands: Error in
>>>>>>>> 'poco_wide_12_r316_new/fft_wideband_real/fft_biplex_real_4x/biplex_core/fft_stage_1':
>>>>>>>> Initialization commands cannot be evaluated.
>>>>>>>> Backtrace 1: reuse_block:138
>>>>>>>> Backtrace 2: biplex_core_init:173
>>>>>>>> Backtrace 3: reuse_block:138
>>>>>>>> Backtrace 4: fft_biplex_real_4x_init:235
>>>>>>>> Backtrace 5: gen_xps_files:203
>>>>>>>> Backtrace 6: run_Callback:155
>>>>>>>> Backtrace 7: casper_xps:88
>>>>>>>> Backtrace 8: @(hObject,eventdata)casper_xps
>>>>>>>> ('run_Callback',hObject,eventdata,guidata(hObject)):0
>>>>>>>> MATLAB:MException:MultipleErrors: Error due to multiple causes.
>>>>>>>> Backtrace 1: reuse_block:51
>>>>>>>> Backtrace 2: fft_stage_n_init:287
>>>>>>>> Backtrace 3: reuse_block:138
>>>>>>>> Backtrace 4: biplex_core_init:173
>>>>>>>> Backtrace 5: reuse_block:138
>>>>>>>> Backtrace 6: fft_biplex_real_4x_init:235
>>>>>>>> Backtrace 7: gen_xps_files:203
>>>>>>>> Backtrace 8: run_Callback:155
>>>>>>>> Backtrace 9: casper_xps:88
>>>>>>>> Backtrace 10: @(hObject,eventdata)casper_xps
>>>>>>>> ('run_Callback',hObject,eventdata,guidata(hObject)):0
>>>>>>>> Simulink:Masking:Bad_Init_Commands: Error in
>>>>>>>> 'poco_wide_12_r316_new/fft_wideband_real/fft_biplex_real_4x/biplex_core/fft_stage_1':
>>>>>>>> Initialization commands cannot be evaluated.
>>>>>>>> Backtrace 1: reuse_block:138
>>>>>>>> Backtrace 2: biplex_core_init:173
>>>>>>>> Backtrace 3: reuse_block:138
>>>>>>>> Backtrace 4: fft_biplex_real_4x_init:235
>>>>>>>> Backtrace 5: gen_xps_files:203
>>>>>>>> Backtrace 6: run_Callback:155
>>>>>>>> Backtrace 7: casper_xps:88
>>>>>>>> Backtrace 8: @(hObject,eventdata)casper_xps
>>>>>>>> ('run_Callback',hObject,eventdata,guidata(hObject)):0
>>>>>>>> Simulink:Masking:Bad_Init_Commands: Error in
>>>>>>>> 'poco_wide_12_r316_new/fft_wideband_real/fft_biplex_real_4x/biplex_core':
>>>>>>>> Initialization commands cannot be evaluated.
>>>>>>>> Backtrace 1: reuse_block:138
>>>>>>>> Backtrace 2: fft_biplex_real_4x_init:235
>>>>>>>> Backtrace 3: gen_xps_files:203
>>>>>>>> Backtrace 4: run_Callback:155
>>>>>>>> Backtrace 5: casper_xps:88
>>>>>>>> Backtrace 6: @(hObject,eventdata)casper_xps
>>>>>>>> ('run_Callback',hObject,eventdata,guidata(hObject)):0
>>>>>>>> Warning: did not properly cleanup after previous model
>>>>>>>> terminationWarning:
>>>>>>>> sync_period_bits =
>>>>>>>>
>>>>>>>> 28
>>>>>>>>
>>>>>>>> Error using gen_xps_files (line 203)
>>>>>>>> Error in 'poco_wide_12_r316_new/fft_wid
>>>>>>>> eband_real/fft_biplex_real_4x': Initialization commands cannot be
>>>>>>>> evaluated.
>>>>>>>> >>
>>>>>>>>
>>>>>>>> On Fri, Nov 4, 2016 at 5:22 PM, Jack Hickish <jackhick...@gmail.com
>>>>>>>> > wrote:
>>>>>>>>
>>>>>>>>> Hi Alec,
>>>>>>>>>
>>>>>>>>> What version of the casper libraries are you using?
>>>>>>>>>
>>>>>>>>> The top of the tutorials page on the wiki states:
>>>>>>>>> """
>>>>>>>>>
>>>>>>>>> These tutorials were constructed using Xilinx System Generator
>>>>>>>>> 14.7 and MATLAB 2012b. Other mutually compatible versions of Xilinx
>>>>>>>>> and
>>>>>>>>> MATLAB tools may work correctly, but have not been tested.
>>>>>>>>>
>>>>>>>>> These tutorials use the casper-astro repository, specifically git
>>>>>>>>> commit 4c7ba5efb4
>>>>>>>>> <https://github.com/casper-astro/mlib_devel/commit/4c7ba5efb421fda1cec0640cf0e3b830a9987640>
>>>>>>>>>
>>>>>>>>> If you plan to use these tutorials on your own system, you are
>>>>>>>>> most likely to have success if you use these libraries. You can
>>>>>>>>> obtain them
>>>>>>>>> from github:
>>>>>>>>>
>>>>>>>>> git clone git://github.com/casper-astro/mlib_devel.git
>>>>>>>>>
>>>>>>>>> cd mlib_devel
>>>>>>>>>
>>>>>>>>> git checkout 4c7ba5efb4
>>>>>>>>> """
>>>>>>>>>
>>>>>>>>> I've no idea if this information is up to date, but is this what
>>>>>>>>> you did?
>>>>>>>>> If you're using a newer version of the libraries than the model
>>>>>>>>> was saved in, you can try opening the model and running, in the matlab
>>>>>>>>> prompt:
>>>>>>>>>
>>>>>>>>> update_casper_blocks(bdroot)
>>>>>>>>>
>>>>>>>>> This will [try to] update all the blocks in the model to the
>>>>>>>>> latest versions (the argument bdroot is a shortcut to the top level
>>>>>>>>> of your
>>>>>>>>> design heirarchy). It'll take a while. After this script has
>>>>>>>>> completed, you
>>>>>>>>> shouldn't have any broken links remaining.
>>>>>>>>>
>>>>>>>>> Cheers
>>>>>>>>> Jack
>>>>>>>>>
>>>>>>>>> On Tue, 4 Oct 2016 at 16:51 Alec Josaitis <josai...@umich.edu>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> Dear Casperites,
>>>>>>>>>>
>>>>>>>>>> I've been trying to complete tutorial 4
>>>>>>>>>> <https://casper.berkeley.edu/wiki/Tutorial_Wideband_Pocket_Correlator>
>>>>>>>>>> for the Roach2, and have run into difficulty compiling either the
>>>>>>>>>> .slx
>>>>>>>>>> <https://github.com/casper-astro/tutorials_devel/blob/tutorials_update_2016/tut4/poco_wide_12_r316_new.slx.r2013a.tar.gz>
>>>>>>>>>> or .mdl
>>>>>>>>>> <https://github.com/casper-astro/tutorials_devel/blob/tutorials_update_2016/tut4/poco_wide_12_r316_new.mdl.tar.gz>files
>>>>>>>>>> given for the Roach 2, or uploading the precompoliled .fpg
>>>>>>>>>> <https://github.com/casper-astro/tutorials_devel/blob/tutorials_update_2016/tut4/poco_wide_1kat.fpg>
>>>>>>>>>> file onto my Roach2 (using either the python scripts given or simply
>>>>>>>>>> by
>>>>>>>>>> command-line uploading the .fpg using ipython). My error messages are
>>>>>>>>>> attached in this Google Drive document.
>>>>>>>>>> <https://docs.google.com/document/d/1RY5LSS7mRx3o2Zm6Gyy_a8jhEjJr2bM1k9CCN9ov0bw/edit?usp=sharing>
>>>>>>>>>>
>>>>>>>>>> For tutorials 1-3 I have had no trouble compiling the .slx files
>>>>>>>>>> and upload the corresponding .fpg files to my Roach2.
>>>>>>>>>>
>>>>>>>>>> I've made sure in the .slx I cite above (for tutorial 4) that the
>>>>>>>>>> XSG_core_config block does not have a broken link and that the
>>>>>>>>>> settings are
>>>>>>>>>> as follows:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> - Hardware platform: Roach2:sx475t
>>>>>>>>>> - User IP clock source: adc0_clk
>>>>>>>>>> - User IP clock rate (MHz): 200, (and that the adc1 and adc0
>>>>>>>>>> are correspondingly clocked to 800 MHz)
>>>>>>>>>> - Sample period: 1
>>>>>>>>>> - Synthesis tool: XST
>>>>>>>>>>
>>>>>>>>>> Any advice on how I can complete tutorial 4?
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Best,
>>>>>>>>>>
>>>>>>>>>> Alec
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>
>>
>
