cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Highlighted
Observer
Observer
353 Views
Registered: ‎07-14-2017

Opening two block designs result in error: bad lexical cast

Jump to solution

On Ubuntu 18.04 when using Vivado 2018.3 and running two instances of Vivado, opening a second block design (to compare them for example) results in several errors: 

[BD 41-1273] Error running init TCL procedure: bad lexical cast: source type value could not be interpreted as target
adi_device_spec Line 58
 
[BD 41-1273] Error running post_config_ip TCL procedure: ERROR: [Common 17-55] 'set_property' expects at least one object.
::xilinx.com_ip_clk_wiz_6.0::post_config_ip Line 62
 
[BD 41-1273] Error running post_config_ip TCL procedure: unexpected "," outside function argument list
::xilinx.com_ip_zynq_ultra_ps_e_3.2::post_config_ip Line 47
 
Closing the two projects and reopening one sometimes removes these errors but other times the errors persist. 
 
Can you please have a look if you experience the same behavior and hopefully provide a solution? Do you know if it results in unpredictable results when continue editing with these errors?
 
 
 
 
0 Kudos
1 Solution

Accepted Solutions
Highlighted
Xilinx Employee
Xilinx Employee
292 Views
Registered: ‎02-13-2020

Hi @rhabraken,

 

This error with lexical cast might be due to a Regional Format settings. Try to set them to English (US). 

You can follow the link below to see how this is done. 

https://help.ubuntu.com/stable/ubuntu-help/session-formats.html.en

View solution in original post

2 Replies
Highlighted
Xilinx Employee
Xilinx Employee
293 Views
Registered: ‎02-13-2020

Hi @rhabraken,

 

This error with lexical cast might be due to a Regional Format settings. Try to set them to English (US). 

You can follow the link below to see how this is done. 

https://help.ubuntu.com/stable/ubuntu-help/session-formats.html.en

View solution in original post

Highlighted
Observer
Observer
252 Views
Registered: ‎07-14-2017

Thanks for pointing me into this direction! Indeed the solution came from changing the regional and language settings to US-English. I did not want to change the settings of my system and following https://www.xilinx.com/support/answers/51331.html solved the error(s).

Thanks again.

 

 
 
0 Kudos