by support »
Hello,
To begin with, Vivado 2014.4 is currently not supported, so even if you managed to get something that apparently works, you're on slippery ice. In particular, the Xillybus interfaces may not work properly (but you don't use them, so maybe that's OK for you). The problem is that Vivado 2014.4 creates a slightly different environment to the processor than 2014.1 as the initiating Tcl script runs.
Now to your question -- In general, if you just made changes to the logic, there in no need to rebuild boot.bin. However if you changed the parameters of the processor (e.g. changes of the PS' I/O pins or PLL frequencies), the FSBL needs to be updated, and hence the boot.bin which contains it.
As for adding peripherals, that depends on how you connected them to the processor. If you needed to activate an HP port for example, odds are that the FSBL needs to be updated to reflect the change. If you added a peripheral to a bus connection that was used anyhow, there is no such need.
A last thing about detecting the hardware by Xillinux -- if you need a standard Linux driver to detect a standard peripheral (say, a UART), you'll need to modify the device tree to inform the kernel about the hardware it faces. The kernel can't guess which peripheral is mapped to what address, and which driver to apply to it. The device tree contains that information.
Regards,
Eli
Hello,
To begin with, Vivado 2014.4 is currently not supported, so even if you managed to get something that apparently works, you're on slippery ice. In particular, the Xillybus interfaces may not work properly (but you don't use them, so maybe that's OK for you). The problem is that Vivado 2014.4 creates a slightly different environment to the processor than 2014.1 as the initiating Tcl script runs.
Now to your question -- In general, if you just made changes to the logic, there in no need to rebuild boot.bin. However if you changed the parameters of the processor (e.g. changes of the PS' I/O pins or PLL frequencies), the FSBL needs to be updated, and hence the boot.bin which contains it.
As for adding peripherals, that depends on how you connected them to the processor. If you needed to activate an HP port for example, odds are that the FSBL needs to be updated to reflect the change. If you added a peripheral to a bus connection that was used anyhow, there is no such need.
A last thing about detecting the hardware by Xillinux -- if you need a standard Linux driver to detect a standard peripheral (say, a UART), you'll need to modify the device tree to inform the kernel about the hardware it faces. The kernel can't guess which peripheral is mapped to what address, and which driver to apply to it. The device tree contains that information.
Regards,
Eli