Re: [meta-xilinx] ZCU102 boot issue

2019-02-01 Thread Scott Ellis
I agree.

Much better then everyone that uses the pmu-firmware having to maintain
these same patches in their own custom layer to get a working system.

It would be nicer if the actual pmu_cfg_obj.c was not a patch, but just
a file in pmu-firmware/files that the recipe copied to the build dir
before the compilation task.

Easier to replace in custom layer that way.

The pm_binding.c modification would still be a patch.


-- 
___
meta-xilinx mailing list
meta-xilinx@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-xilinx


Re: [meta-xilinx] ZCU102 boot issue

2019-01-28 Thread Scott Ellis
This is the error you get if the PMU does not get a config object on boot.

When using a boot.bin object from the xilinx tools, the first stage
bootloader is Xilinx's FSBL which loads a config object into the PMU at
startup before it loads u-boot proper.

When you use the instructions in the README, the first stage boot loader
is u-boot's SPL, which does not know how to load a config object into
the PMU.

The config object I am talking about is the C file pmu_cfg_obj.c

The workaround is to patch the pmu-firmware (it's a simple two line
patch) to teach the PMU firmware to load a built-in config object.
And then you need to include the pmu_cfg_obj.c in the source. So the
pmu-firmware recipe needs two patches, but both are trivial.

There are multiple threads on the mailing list about this.

Here is a recent one that I initiated asking the same question as you in
a different way

https://lists.yoctoproject.org/pipermail/meta-xilinx/2019-January/004193.html

-- 
___
meta-xilinx mailing list
meta-xilinx@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-xilinx


Re: [meta-xilinx] Clarification on pmu_cfg_obj handling for zynqmp boards

2019-01-23 Thread Scott Ellis
Hi Luca,

What you describe is how I understand things.

And I do have a booting system using the patch to the pmu-firmware and a
pm_cfg_obj.c the customer provided.

And I have also used a boot.bin produced by the xilinx tools by the
customer with fsbl, pmu, etc... embedded. And that works fine too.

I think I get the gist of things.

What I am confused about is the usefulness of the meta-xilinx-standalone
layer and the pmu-firmware in particular without patches.

I don't think the license on the xilinx tool generated pm_cfg_obj.c
matters too much.

I wasn't suggesting the pm_cfg_obj.c be included in the layer since
every board probably needs it's own version anyway.

I was just asking about the patch to pm_binding.c to load an internal
config object. Shouldn't this be included?

I think it was you that suggested that the pmu-firmware recipe or
another new recipe could go out and fetch the pm_cfg_obj.c file from
somewhere else before the pmu-firmware compile step.

That seemed like a reasonable idea to me.

The pmu-firmware recipe as is doesn't seem too useful without these two
items.

But again I am new to these boards, maybe there is a bare-metal use for
the PMU firmware that does not require a config object.

But the multiconfig instructions imply that the layers should just work.

As for u-boot SPL unable to load a cfg object to the PMU, I started to
look at implementing that. SPL does already talk to the PMU, it
retrieves the PMU fw version for example.

But I stopped since it seems silly.

If I have the cfg object at build time, why not just build it into the
pmu-firmware as you do with the patch and skip the runtime loading at
every boot.

Regards,
Scott






-- 
___
meta-xilinx mailing list
meta-xilinx@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-xilinx


Re: [meta-xilinx] Clarification on pmu_cfg_obj handling for zynqmp boards

2019-01-23 Thread Scott Ellis
Hi Manju,

Thanks for answering.

I will look at the meta-xilinx-tools layer. I think I finally understand
what is required to boot.

But I am still not clear on the meta-xilinx multiconfig...

The meta-xilinx-bsp/README.building.md has no mention that a patch is
required to the pmu-firmware which is confusing.

Is this just an omission?

Is the pmu-firmware recipe useful without the patch?

Excuse the dumb questions.

I am new to xilinx boards.

Regards,
Scott





-- 
___
meta-xilinx mailing list
meta-xilinx@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-xilinx


[meta-xilinx] Clarification on pmu_cfg_obj handling for zynqmp boards

2019-01-19 Thread Scott Ellis
Is there a way to use the thud branch meta-xilinx-bsp and
meta-xilinx-standalone layers to build a bootable zynqmp system
without having to use an external patch to the pmu-firmware recipe?

-- 
___
meta-xilinx mailing list
meta-xilinx@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-xilinx