Ok.
I am starting to think that this can be a version problem. My .xsa is from
vivado 2020.1 and i am trying to use 2022.2 releases from meta-xilinx.
Sandeep, indeed my uart 1 is not enabled on Vivado design. I will try to use
uart 0. As soon i do that, i will update the result here.
Thanks
On 12/11/2022 11:48 AM, Mark Hatle via lists.yoctoproject.org wrote:
On 12/10/22 10:52 AM, Joao Paulo Silva Goncalves wrote:
(background)
All of the messages below come from xsct tool and it's hsi APIs (these
are part of Vivado, the HSI bits are being run by some tcl code in
order to
On 12/10/22 10:52 AM, Joao Paulo Silva Goncalves wrote:
(background)
All of the messages below come from xsct tool and it's hsi APIs (these are part
of Vivado, the HSI bits are being run by some tcl code in order to extract
required values from the XSA to configure and compile the firmware
Hi , Grzegorz.
I changed HAS_PLATFORM_INIT to *HAS_PLATFORM_INIT = xilinx_zynqmp_virt_config*
(as my board is based on zynqmp ) but the error remains and still the same.
I think that this is not the problem. The files in HAS_PLATFORM_INIT are u-boot
defconfigs and seem to be used to add init
On Sun, Dec 11, 2022 at 01:46 AM, Grzegorz Heldt wrote:
>
> HAS_PLATFORM_INIT += "mcomm"
Sorry, quickly looking at:
https://github.com/Xilinx/meta-xilinx/blob/master/meta-xilinx-core/recipes-bsp/u-boot/u-boot-xlnx_2022.1.bb
The line should be HAS_PLATFORM_INIT += "mcomm_defconfig" and assumes
Hi, Joao.
I was at this point a few weeks ago, I'm not really sure how I resolved that,
but you can give a try this:
In your layer, can you create bbappend for u-boot-xlnx, with the following
statement:
HAS_PLATFORM_INIT += "mcomm"
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent
