02-20-2019 03:28 PM
We recently updated from Vivado 2018.2 to Vivado 2018.3. Yeah, we have to with knowing that as a risk.
We use petalinux-config <hdf file path> to configure and make new fsbl etc. docs. The new fsbl.elf hang immediately without any print. With the XFSBL_DEBUG option open, it shows the DDR_INIT failed. We find that code in xfsbl_initilization.c. That's totally new code in release 2018.3 and that is initializing DRAM as the 2nd time. I have to comment out that for debugging.
Also, the flash configuration in config disappeared. So, we have to do all of these things manually. After that petalinux-config still CAN'T recognize the new config file.
We end up to use 2018.2 fsbl.elf as a temporary solution.
Could anyone share your success story of release 2018.3 fsbl?
02-21-2019 08:07 AM
I don't know if it can help but when I tried to use our project with Petalinux 2018.3 it failed.
I had to create a new project under Petalinux 2018.3, merge our stuff in and build.
(Our project was initially created under Petalinux 2018.1 and converted to 2018.2).
But FSBL is working fine...
(Only issue, for us, is the phy driver. It is now using a generic one instead of the manufacturer one).
02-24-2019 07:42 AM
I tried that trick of creating a brand new project and then merge in, it didn't work for me.
The root cause of that DRAM error comes from the second time DRAM initialization which is NEW code in 2018.3. So, I just commented out. Since there are some many other new codes. I temporarily use 2018.2 FSBL for now because I have more important tasks to handle.
We used Fidus board instead of zcu102 which is the default for a zynpMP project.