Vivado 2015.1 Bug Report: Adding Required Port without Default Value in Custom Interface Definition

Question

When adding a port using the Custom Interface Definition window and not defining a Default Value, the attached error message appears.  Not only are the html tags visible, but this error should not be thrown in the first place if both Master/Slave Presense is set to "required".  As it is, a port can only be added if a Default Value is given, but can be removed later from the ports table.

Answer 1

yes,I have successfully install petalinux2015.2,but,the issue still be the same as before,the axi 16550 is not working,when I run echo 123 > /dev/ttyS1,my ttyPS0 stop working and axi com keeping null output...
then,I try petalinux2014.4+petalinux2014.4,the difference is the ttyPS0 still alive but axi-com still null...
I found that pl.dtsi file is quite different between the three mode:
M1,petalinux2014.4+vivado2015.1
M2,petalinux2015.2+vivado2015.1
M3,petalinux2014.4+vivado2014.4
most confuse for me is the interrupt ID,
in vivado I connect the axi intterrupt to ID 62 but I get different auto generate dts file
M1:nothing about interrupt and i add manuually in system-top.file
M2:vivado ID is 61 but dts "interrupts = <0 30 4>"
M3:vivado ID is 62 but dts "interrupts = <0 31 4>"
does petalinux auto detect the vivado interrupt connection and ID and write to dts file right or User have to verify and rewrite in ststem-top.dts?
working hard for the issue and hope for a axi demo including petalinux + vivado ,help please