Hi Mark and Wes,

The document has been updated and pushed to git.

Kind regards,

Adam

On Thu, Jun 22, 2017 at 10:36 AM, Wesley New <[email protected]> wrote:

> Hi Mark,
>
> By changing branches you would have over written any changes to your
> vivado_config.sh script. You will need to make those changes again. I just
> point them to the Vivado and Matlab install directories (Not the
> executables) and to where mlib_devel is cloned. Make these changes to lines
> 1,3 & 4 in the script.
>
> Dont worry about *cp:* cannot stat ‘/opt/Vivado2016_2/Vivado/2016
> .2/lib/lnx64.o:/opt/Vivado2016_2/Vivado/2016.2/lib/lnx64.o/libstdc++.so.6’:
> No such file or directory
> we all get this issue.
>
> Your problem is that it cant find the Matlab executable at *cp:* cannot
> stat ‘/usr/local/bin/glnxa64/MATLAB’: No such file or directory
>
> Ill update the documentation accordingly.
>
> Regards
>
> Wes
>
> Wesley New
> South African SKA Project
> +2721 506 7300 <+27%2021%20506%207300>
> www.ska.ac.za
>
>
>
> On Wed, Jun 21, 2017 at 7:24 PM, Peryer, Mark A. <
> [email protected]> wrote:
>
>> Hi Wesley,
>>
>> When using the jasper_vivado_2016_2 branch I was able to successfully run
>> and compile jasper designs using Vivado 2016.2 and Matlab 2016b. However,
>> now when I use the master branch and run the 'startsg' script I receive the
>> following errors:
>>
>> *mperyer@nirvana:~/Jasper/mlib_devel$* ./startsg
>> *Using default configuration:* /home/mperyer/Jasper/mlib_deve
>> l/vivado_config.sh
>> /opt/Matlab/R2016b/bin:/opt/Vivado2016_2/Vivado/2016.2/bin:/
>> opt/Vivado2016_2/Vivado_HLS/2016.2/bin:/opt/Vivado2016_2/
>> SDK/2016.2/bin:/opt/Vivado2016_2/SDK/2016.2/gnu/
>> microblaze/lin/bin:/opt/Vivado2016_2/SDK/2016.2/gnu/arm/lin/
>> bin:/opt/Vivado2016_2/SDK/2016.2/gnu/microblaze/linux_
>> toolchain/lin64_be/bin:/opt/Vivado2016_2/SDK/2016.2/gnu/
>> microblaze/linux_toolchain/lin64_le/bin:/opt/Vivado2016_
>> 2/SDK/2016.2/gnu/aarch32/lin/gcc-arm-linux-gnueabi/bin:/
>> opt/Vivado2016_2/SDK/2016.2/gnu/aarch32/lin/gcc-arm-none-
>> eabi/bin:/opt/Vivado2016_2/SDK/2016.2/gnu/aarch64/lin/
>> aarch64-linux/bin:/opt/Vivado2016_2/SDK/2016.2/gnu/
>> aarch64/lin/aarch64-none/bin:/opt/Vivado2016_2/SDK/2016.2/
>> gnu/armr5/lin/gcc-arm-none-eabi/bin:/opt/Vivado2016_2/
>> SDK/2016.2/tps/lnx64/cmake-3.3.2/bin:/opt/Vivado2016_2/Viva
>> do/2016.2/bin:/opt/Vivado2016_2/Vivado_HLS/2016.2/bin:/opt/
>> Vivado2016_2/SDK/2016.2/bin:/opt/Vivado2016_2/SDK/2016.2/
>> gnu/microblaze/lin/bin:/opt/Vivado2016_2/SDK/2016.2/gnu/
>> arm/lin/bin:/opt/Vivado2016_2/SDK/2016.2/gnu/microblaze/
>> linux_toolchain/lin64_be/bin:/opt/Vivado2016_2/SDK/2016.2/
>> gnu/microblaze/linux_toolchain/lin64_le/bin:/opt/
>> Vivado2016_2/SDK/2016.2/gnu/aarch32/lin/gcc-arm-linux-gnue
>> abi/bin:/opt/Vivado2016_2/SDK/2016.2/gnu/aarch32/lin/gcc-
>> arm-none-eabi/bin:/opt/Vivado2016_2/SDK/2016.2/gnu/aarch64/
>> lin/aarch64-linux/bin:/opt/Vivado2016_2/SDK/2016.2/gnu/
>> aarch64/lin/aarch64-none/bin:/opt/Vivado2016_2/SDK/2016.2/
>> gnu/armr5/lin/gcc-arm-none-eabi/bin:/opt/Vivado2016_2/
>> SDK/2016.2/tps/lnx64/cmake-3.3.2/bin:/opt/Vivado2016_2/Viva
>> do/2016.2/bin:/opt/Vivado2016_2/Vivado_HLS/2016.2/bin:/opt/
>> Vivado2016_2/SDK/2016.2/bin:/opt/Vivado2016_2/SDK/2016.2/
>> gnu/microblaze/lin/bin:/opt/Vivado2016_2/SDK/2016.2/gnu/
>> arm/lin/bin:/opt/Vivado2016_2/SDK/2016.2/gnu/microblaze/
>> linux_toolchain/lin64_be/bin:/opt/Vivado2016_2/SDK/2016.2/
>> gnu/microblaze/linux_toolchain/lin64_le/bin:/opt/
>> Vivado2016_2/SDK/2016.2/gnu/aarch32/lin/gcc-arm-linux-gnue
>> abi/bin:/opt/Vivado2016_2/SDK/2016.2/gnu/aarch32/lin/gcc-
>> arm-none-eabi/bin:/opt/Vivado2016_2/SDK/2016.2/gnu/aarch64/
>> lin/aarch64-linux/bin:/opt/Vivado2016_2/SDK/2016.2/gnu/
>> aarch64/lin/aarch64-none/bin:/opt/Vivado2016_2/SDK/2016.2/
>> gnu/armr5/lin/gcc-arm-none-eabi/bin:/opt/Vivado2016_2/
>> SDK/2016.2/tps/lnx64/cmake-3.3.2/bin:/opt/Vivado2016_2/Viva
>> do/2016.2/bin:/opt/Vivado2016_2/Vivado_HLS/2016.2/bin:/opt/
>> Vivado2016_2/SDK/2016.2/bin:/opt/Vivado2016_2/SDK/2016.2/
>> gnu/microblaze/lin/bin:/opt/Vivado2016_2/SDK/2016.2/gnu/
>> arm/lin/bin:/opt/Vivado2016_2/SDK/2016.2/gnu/microblaze/
>> linux_toolchain/lin64_be/bin:/opt/Vivado2016_2/SDK/2016.2/
>> gnu/microblaze/linux_toolchain/lin64_le/bin:/opt/
>> Vivado2016_2/SDK/2016.2/gnu/aarch32/lin/gcc-arm-linux-gnue
>> abi/bin:/opt/Vivado2016_2/SDK/2016.2/gnu/aarch32/lin/gcc-
>> arm-none-eabi/bin:/opt/Vivado2016_2/SDK/2016.2/gnu/aarch64/
>> lin/aarch64-linux/bin:/opt/Vivado2016_2/SDK/2016.2/gnu/
>> aarch64/lin/aarch64-none/bin:/opt/Vivado2016_2/SDK/2016.2/
>> gnu/armr5/lin/gcc-arm-none-eabi/bin:/opt/Vivado2016_2/
>> SDK/2016.2/tps/lnx64/cmake-3.3.2/bin:/usr/local/sbin:/usr/
>> local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
>>
>> *EXECUTING:* /opt/Vivado2016_2/Vivado/2016.2/bin/sysgen
>>
>> *cp:* cannot stat ‘/opt/Vivado2016_2/Vivado/2016
>> .2/lib/lnx64.o:/opt/Vivado2016_2/Vivado/2016.2/lib/lnx64.o/libstdc++.so.6’:
>> No such file or directory
>>
>> *cp:* cannot stat ‘/usr/local/bin/glnxa64/MATLAB’: No such file or
>> directory
>>
>> Configuring MATLAB runtime using Xilinx Supplied .matlab7rc.sh file
>> copied to your home directory
>>
>> */home/mperyer/.matlab7rc.sh:* line 145: /usr/local/bin/util/arch.sh: No
>> such file or directory
>>
>> */usr/local/bin/matlab:* line 1246: /usr/local/bin/matlab-glselector.sh:
>> No such file or directory
>>
>> */opt/Vivado2016_2/Vivado/2016.2/bin/sysgen:* line 495:
>> /home/mperyer/.XILINX_MATLAB_RUNTIME/SG_2016.2_local/MATLAB: No such
>> file or directory
>>
>>
>> I installed the Matlab symbolic links in the default location
>> /usr/local/bin. Are there any paths I need to update in order for the
>> scripts to find the associated files?
>>
>>
>> Also, could you update the document "How_To_Run_the_JASPER_Toolflow.pdf"
>> in the skarab_docs repo (https://github.com/ska-sa/skarab_docs) to
>> indicate to use of the master branch of mlib_devel. This specifically
>> refers to the following steps:
>>
>> *9)* Using the terminal, type the following:
>>     “​ git checkout jasper ​ ” in the “mlib_devel” folder.
>>     This will change the local repository from the master branch to the
>>     jasper branch, which will contain the “jasper_library” folder under
>>     “mlib_devel”.
>>
>> *10)*  Using the terminal, type the following:
>>       “git status” ​ in the “mlib_devel” folder.
>>        This should indicate that the jasper branch has been selected.
>>
>>
>> Thanks,
>>
>> Mark Peryer
>>
>> On Wed, Jun 21, 2017 at 9:53 AM, Wesley New <[email protected]> wrote:
>>
>>> Hi Mark,
>>>
>>> The jasper_vivado_2016_2 is an older branch that has now been merged
>>> into Master. There are a lot of changes that have happened subsequent to
>>> that in master. So please use Master to rebuild the fpg file and try to
>>> program again.
>>>
>>> Ill remove that old branch shortly.
>>>
>>> Regards
>>>
>>> Wes
>>>
>>> Wesley New
>>> South African SKA Project
>>> +2721 506 7300 <+27%2021%20506%207300>
>>> www.ska.ac.za
>>>
>>>
>>>
>>> On Wed, Jun 21, 2017 at 3:46 PM, Peryer, Mark A. <
>>> [email protected]> wrote:
>>>
>>>> Hello,
>>>>
>>>> I am currently trying to upload a .fpg file to a SKARAB created with
>>>> the jasper_vivado_2016_2 branch (commit 6172a4b) of
>>>> https://github.com/ska-sa/mlib_devel. Using the latest version of
>>>> casperfpga (commit ec0c355) from the devel branch,
>>>> https://github.com/ska-sa/casperfpga/tree/devel, I receive the
>>>> following error.
>>>>
>>>>
>>>> import casperfpga
>>>> fpga = casperfpga.CasperFpga('skarab-02')
>>>> fpga.is_connected()
>>>> True
>>>> fpga.upload_to_ram_and_program('/home/mark.peryer/realtimeap
>>>> hids_6_20_2017-6-20_1515.fpg')
>>>>
>>>> ERROR:casperfpga.transport_skarab:An older version of mlib_devel
>>>> generated /home/mark.peryer/realtimeaphids_6_20_2017-6-20_1515.fpg.
>>>> Please update to include the md5sum on the bitstream in the .fpg header.
>>>>
>>>> Any help would be appreciated.
>>>>
>>>> Thanks,
>>>>
>>>> Mark Peryer
>>>>
>>>> --
>>>> 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 post to this group, send email to [email protected].
>>>>
>>>
>>>
>>
> --
> 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 post to this group, send email to [email protected].
>



-- 
[image: SKA_banner]

Best Regards / Vriendelike Groete

*Adam Isaacson*
FPGA Engineer

[image: SKA_banner][image: SKA_banner]
[image: SKA_banner]   (+27) 82 563 9602 [image: SKA_banner]   3rd Floor,
The Park, Park Road,
[image: SKA_banner]   (+27) 21 506 7300     Pinelands
[image: SKA_banner]   (+27) 21 506 7375     7405
[image: SKA_banner]   www.ska.ac.za     South Africa

-- 
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 post to this group, send email to [email protected].

Reply via email to