Hello, thanks everyone, I've done the proposed changes, and now doesn't get an error instantly, but now it seems, from what I've searched, that this new error related more to Vivado, mlib_devel. In particular, log file at "/home/casper/Desktop/tuto1_208/myproj/myproj.runs/synth_1".
Has someone encountered this error with the Toolflow? Reposting because I think the last email got lost. ERROR: [Synth 8-2772] type t_axi4lite_mmap_addr_arr does not match with a string literal [/home/casper/Desktop/tuto1_208/myproj/myproj.srcs/ sources_1/imports/xml2vhdl_hdl_output/axi4lite_axi4lite_top_mmap_pkg.vhd:94] ERROR: [Synth 8-2772] type t_axi4lite_mmap_addr_arr does not match with a string literal [/home/casper/Desktop/tuto1_208/myproj/myproj.srcs/ sources_1/imports/xml2vhdl_hdl_output/axi4lite_axi4lite_top_mmap_pkg.vhd:95] INFO: [Synth 8-2810] unit axi4lite_axi4lite_top_mmap_pkg ignored due to previous errors [/home/casper/Desktop/tuto1_208/myproj/myproj.srcs/ sources_1/imports/xml2vhdl_hdl_output/axi4lite_axi4lite_top_mmap_pkg.vhd:67] ------------------------------------------------------------ --------------------- Finished RTL Elaboration : Time (s): cpu = 00:00:00.95 ; elapsed = 00:00:02 . Memory (MB): peak = 2973.926 ; gain = 244.625 ; free physical = 6723 ; free virtual = 11392 ------------------------------------------------------------ --------------------- RTL Elaboration failed INFO: [Common 17-83] Releasing license: Synthesis 10 Infos, 0 Warnings, 0 Critical Warnings and 3 Errors encountered. synth_design failed ERROR: [Common 17-69] Command failed: Synthesis failed - please see the console or run log file for details INFO: [Common 17-206] Exiting Vivado at Fri Oct 13 02:51:34 2023... Thanks again, Emiliano El miércoles, 11 de octubre de 2023 a las 3:21:44 UTC-3, Jack Hickish escribió: > > > On Tue, 10 Oct 2023, 22:46 Kaj Wiik, <kaj....@utu.fi> wrote: > >> Hi Jack, >> >> This is most interesting, especially the comment "Make KRM clock SPI >> work" sounds very promising! >> > > If only I remembered what that actually referred to :) > > >> We are using the 27DR variant but I guess the visible differences is in >> RFDC only. >> >> Have you succeeded to port casperfpga and RFDC drivers to Petalinux/Pynq? >> > > I use casperfpga, but not pynq. But I do have a viable Linux image, which > obviously you are welcome to. > > Cheers > Jack > > > >> Thanks! >> >> Kaj >> >> On 11.10.2023 0.27, Jack Hickish wrote: >> > Hi Kaj, >> > >> > I have KRM support at >> > https://github.com/realtimeradio/mlib_devel/tree/souk >> > <https://github.com/realtimeradio/mlib_devel/tree/souk> if that's >> useful. >> > I've probably diverged a bit from the main mlib repo though - probably >> > some of the hacks I used to support the board are no longer required >> now >> > the rfdc block is increasingly mature >> > >> > Cheers >> > Jack >> > >> > On Tue, 10 Oct 2023, 15:59 Kaj Wiik, <kjw...@utu.fi >> > <mailto:kjw...@utu.fi>> wrote: >> > >> > On 10.10.2023 17.32, Mitchell Burnett wrote: >> > > The `*_base.tcl` files are not being used in the toolflow for >> > RFSoC parts and so you do not need to worry about generating a new >> > base tcl file for the zcu208. >> > >> > This is interesting and useful information! One file less to worry >> > about when porting the KR module :-) (which I should start next >> week)! >> > >> > Cheers, >> > Kaj >> > >> > -- >> > You received this message because you are subscribed to the Google >> > Groups "cas...@lists.berkeley.edu >> > <mailto:cas...@lists.berkeley.edu>" group. >> > To unsubscribe from this group and stop receiving emails from it, >> > send an email to casper+un...@lists.berkeley.edu >> > <mailto:casper%2bunsu...@lists.berkeley.edu>. >> > To view this discussion on the web visit >> > >> https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/4cc09fe9-f739-73bc-1ca7-8aa9495ecdde%40utu.fi >> >> < >> https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/4cc09fe9-f739-73bc-1ca7-8aa9495ecdde%40utu.fi >> >. >> > >> > -- >> > You received this message because you are subscribed to the Google >> > Groups "cas...@lists.berkeley.edu" group. >> > To unsubscribe from this group and stop receiving emails from it, send >> > an email to casper+un...@lists.berkeley.edu >> > <mailto:casper+un...@lists.berkeley.edu>. >> > To view this discussion on the web visit >> > >> https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CAG1GKS%3D6orkWDwP_9jv4sK66kN%3D9UeWWmAgN2-ATaX8pfAJppA%40mail.gmail.com >> >> < >> https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CAG1GKS%3D6orkWDwP_9jv4sK66kN%3D9UeWWmAgN2-ATaX8pfAJppA%40mail.gmail.com?utm_medium=email&utm_source=footer >> >. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "cas...@lists.berkeley.edu" group. >> > To unsubscribe from this group and stop receiving emails from it, send an >> email to casper+un...@lists.berkeley.edu. >> To view this discussion on the web visit >> https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/cc922340-c38a-42a8-9dc9-16e18087963f%40utu.fi >> . >> > -- 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/d6ee1619-1217-4e79-99d8-766ecd2f5d27n%40lists.berkeley.edu.
