YellowBlock classes have no access to the Jasper build directory. One
possible way around this is to override method add_build_dir_source() , as
is done in lines 110-111 in this file,
https://github.com/casper-astro/mlib_devel/blob/m2021a/jasper_library/yellow_blocks/axi4lite_interconnect.py
def add_build_dir_source(self):
return [{'files':'xml2vhdl_hdl_output/*.vhd',
'library':'xil_defaultlib'}]``
Below is the override in my own custom YellowBlock class. It attempts to
stall out the workflow with an exit or otherwise cause calling code
exceptions when trying to access the key, 'files'. To boot, it should
always write to a log file.
1. def add_build_dir_source(self):
2. with open("/tmp/jasper.log", "a") as fhandle :
3. fhandle.writelines( ["add_build_dir_source()"] )
4. sys.exit(-2)
5. return( [{'qqqqq':'zxcvbm'}, {'x':'zxcvbm'}, {'y':'zxcvbm'}]
)
None of these occur. Instead, jasper simply runs to completion and creates
a bitstream. How to cause the workflow to call this method in my custom
YellowBlock?
--
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/456ac520-83da-466a-8a87-86e59f7f7bdcn%40lists.berkeley.edu.
