[meta-xilinx] Zynq spidev name

[Arno Steffens]

Hello,
I changed kernel from 4.9 to 4.14.
My previous /dev/spidev32766.0 is now listed as /dev/spidev0.0.
Honestly speaking, I have not been aware how the previous name "32766.0" is 
coming from. But why this has been changed?
I would suspecz the devicetree, but that I haven't changed it at all.

Have a few apps that use the devicename hardcoded. How to handle it best? 
Create a link in /dev ?

Thank you and best regards
Arno

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

Re: [meta-xilinx] PMUFW debugging with debug flags

[Giordon Stark]

So is the m-x-t layer using a recipe described by this page (
http://www.wiki.xilinx.com/PMU+Firmware) and not the m-x-bsp layer?

That's unfortunate if so. I'd rather not pull in m-x-t right now.

Giordon

On Thu, Jul 19, 2018 at 9:00 AM Peter Smith  wrote:

> The two recipes are different for sure, I noticed this only yesterday and
> yes you need xsct for m-x-t
>
> On Thu, 19 Jul 2018, 14:58 Giordon Stark,  wrote:
>
>> Hi JF,
>>
>> No, but I am on rocko so it's got the two different layers under
>> meta-xilinx and I'm using the meta-xilinx-bsp version. Is meta-xilinx-tools
>> completely different? The main reason I'm not using meta-xilinx-tools right
>> now is that my understanding is I need the SDK installed on the machine and
>> point m-x-t at it, and I'm just trying to get things in a way that doesn't
>> depend on something external to yocto...
>>
>> Giordon
>>
>> On Thu, Jul 19, 2018 at 8:55 AM Jean-Francois Dagenais <
>> jeff.dagen...@gmail.com> wrote:
>>
>>> Hi Giordon,
>>>
>>> > On Jul 19, 2018, at 8:58 AM, Giordon Stark  wrote:
>>> >
>>> > However, when recompiling and re-running -- I do not see extra debug
>>> information from the PMUFW -- so I'm patching the kernel
>>> drivers/clk/zynqmp/pll.c to get more information about the PLL hang itself
>>> in the meantime.
>>> >
>>> > Any ideas? Did I do something wrong in enabling the debug flags?
>>>
>>> Are you using the meta-xilinx-tools pmu_firmware recipe?
>>>
>>> I ask because, coincidently, I am discussing a patch in
>>> xsctbase:do_configure about cleaning the xsct workspace on do_configure
>>> start to avoid these kinds of behaviour. See
>>> https://lists.yoctoproject.org/pipermail/meta-xilinx/2018-June/003916.html
>>> and
>>> https://lists.yoctoproject.org/pipermail/meta-xilinx/2018-July/003986.html
>>>
>>> Turns out I had the manual "rm" in my local repo only, but the point
>>> remains.
>>>
>>> Hope this helps!
>>
>> --
>> Giordon Stark
>>
> --
>> ___
>> meta-xilinx mailing list
>> meta-xilinx@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/meta-xilinx
>>
> --
Giordon Stark
-- 
___
meta-xilinx mailing list
meta-xilinx@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-xilinx

Re: [meta-xilinx] PMUFW debugging with debug flags

[Jean-Francois Dagenais]

> On Jul 23, 2018, at 9:47 AM, Giordon Stark  wrote:
> 
> So is the m-x-t layer using a recipe described by this page 
> (http://www.wiki.xilinx.com/PMU+Firmware 
> ) and not the m-x-bsp layer?

Well, there's a recipe in m-x-t which compile the same (and only) PMUFW code 
using the xsct tools (Xilinx SDK "back-end"). Since the page you point to are 
using the Xilinx SDK GUI to perform the build, I would assume the m-x-t recipe 
matches that the closest.

I have not yet tried the m-x-bsp layer pmu fw recipe so I cannot offer much 
help as to what deviation one might expect. Perhaps other more experienced devs 
will chime in... Nathan perhaps?-- 
___
meta-xilinx mailing list
meta-xilinx@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-xilinx

Re: [meta-xilinx] PMUFW debugging with debug flags

[Peter Smith]

I think that's correct yes. It will get the source of the PMU firmware from
the repo below using the 2018.2 tag:
EMBEDDEDSW_REPO ?= "git://github.com/Xilinx/embeddedsw.git;protocol=https"
Best Regards
Peter


On Mon, 23 Jul 2018 at 14:47, Giordon Stark  wrote:

> So is the m-x-t layer using a recipe described by this page (
> http://www.wiki.xilinx.com/PMU+Firmware) and not the m-x-bsp layer?
>
> That's unfortunate if so. I'd rather not pull in m-x-t right now.
>
> Giordon
>
> On Thu, Jul 19, 2018 at 9:00 AM Peter Smith  wrote:
>
>> The two recipes are different for sure, I noticed this only yesterday and
>> yes you need xsct for m-x-t
>>
>> On Thu, 19 Jul 2018, 14:58 Giordon Stark,  wrote:
>>
>>> Hi JF,
>>>
>>> No, but I am on rocko so it's got the two different layers under
>>> meta-xilinx and I'm using the meta-xilinx-bsp version. Is meta-xilinx-tools
>>> completely different? The main reason I'm not using meta-xilinx-tools right
>>> now is that my understanding is I need the SDK installed on the machine and
>>> point m-x-t at it, and I'm just trying to get things in a way that doesn't
>>> depend on something external to yocto...
>>>
>>> Giordon
>>>
>>> On Thu, Jul 19, 2018 at 8:55 AM Jean-Francois Dagenais <
>>> jeff.dagen...@gmail.com> wrote:
>>>
 Hi Giordon,

 > On Jul 19, 2018, at 8:58 AM, Giordon Stark  wrote:
 >
 > However, when recompiling and re-running -- I do not see extra debug
 information from the PMUFW -- so I'm patching the kernel
 drivers/clk/zynqmp/pll.c to get more information about the PLL hang itself
 in the meantime.
 >
 > Any ideas? Did I do something wrong in enabling the debug flags?

 Are you using the meta-xilinx-tools pmu_firmware recipe?

 I ask because, coincidently, I am discussing a patch in
 xsctbase:do_configure about cleaning the xsct workspace on do_configure
 start to avoid these kinds of behaviour. See
 https://lists.yoctoproject.org/pipermail/meta-xilinx/2018-June/003916.html
 and
 https://lists.yoctoproject.org/pipermail/meta-xilinx/2018-July/003986.html

 Turns out I had the manual "rm" in my local repo only, but the point
 remains.

 Hope this helps!
>>>
>>> --
>>> Giordon Stark
>>>
>> --
>>> ___
>>> meta-xilinx mailing list
>>> meta-xilinx@yoctoproject.org
>>> https://lists.yoctoproject.org/listinfo/meta-xilinx
>>>
>> --
> Giordon Stark
>
-- 
___
meta-xilinx mailing list
meta-xilinx@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-xilinx

Re: [meta-xilinx] PMUFW debugging with debug flags

[Manjukumar Harthikote Matha]

Hi,

Can you try the following
EXTRA_COMPILER_FLAGS_append = " -DXPFW_DEBUG_DETAILED -DDEBUG_MODE -DENABLE_EM"

This should be reflected in the log.do_compile 
Also note, uart settings for PMU firmware matters to check the prints in 
appropriate console

Thanks,
Manju


> -Original Message-
> From: meta-xilinx-boun...@yoctoproject.org [mailto:meta-xilinx-
> boun...@yoctoproject.org] On Behalf Of Peter Smith
> Sent: Monday, July 23, 2018 6:55 AM
> To: Giordon Stark 
> Cc: meta-xilinx@yoctoproject.org
> Subject: Re: [meta-xilinx] PMUFW debugging with debug flags
> 
> I think that's correct yes. It will get the source of the PMU firmware from 
> the repo
> below using the 2018.2 tag:
> EMBEDDEDSW_REPO ?= "git://github.com/Xilinx/embeddedsw.git;protocol=https
>  "
> Best Regards
> Peter
> 
> 
> On Mon, 23 Jul 2018 at 14:47, Giordon Stark   > wrote:
> 
> 
>   So is the m-x-t layer using a recipe described by this page
> (http://www.wiki.xilinx.com/PMU+Firmware) and not the m-x-bsp layer?
> 
>   That's unfortunate if so. I'd rather not pull in m-x-t right now.
> 
>   Giordon
> 
>   On Thu, Jul 19, 2018 at 9:00 AM Peter Smith   > wrote:
> 
> 
>   The two recipes are different for sure, I noticed this only 
> yesterday
> and yes you need xsct for m-x-t
> 
>   On Thu, 19 Jul 2018, 14:58 Giordon Stark,   > wrote:
> 
> 
>   Hi JF,
> 
>   No, but I am on rocko so it's got the two different 
> layers
> under meta-xilinx and I'm using the meta-xilinx-bsp version. Is 
> meta-xilinx-tools
> completely different? The main reason I'm not using meta-xilinx-tools right 
> now is
> that my understanding is I need the SDK installed on the machine and point 
> m-x-t
> at it, and I'm just trying to get things in a way that doesn't depend on 
> something
> external to yocto...
> 
>   Giordon
> 
>   On Thu, Jul 19, 2018 at 8:55 AM Jean-Francois Dagenais
> mailto:jeff.dagen...@gmail.com> > wrote:
> 
> 
>   Hi Giordon,
> 
>   > On Jul 19, 2018, at 8:58 AM, Giordon Stark
> mailto:kra...@gmail.com> > wrote:
>   >
>   > However, when recompiling and re-running -- I
> do not see extra debug information from the PMUFW -- so I'm patching the 
> kernel
> drivers/clk/zynqmp/pll.c to get more information about the PLL hang itself in 
> the
> meantime.
>   >
>   > Any ideas? Did I do something wrong in
> enabling the debug flags?
> 
>   Are you using the meta-xilinx-tools pmu_firmware
> recipe?
> 
>   I ask because, coincidently, I am discussing a
> patch in xsctbase:do_configure about cleaning the xsct workspace on
> do_configure start to avoid these kinds of behaviour. See
> https://lists.yoctoproject.org/pipermail/meta-xilinx/2018-June/003916.html and
> https://lists.yoctoproject.org/pipermail/meta-xilinx/2018-July/003986.html
> 
>   Turns out I had the manual "rm" in my local repo
> only, but the point remains.
> 
>   Hope this helps!
> 
>   --
> 
>   Giordon Stark
> 
>   --
>   ___
>   meta-xilinx mailing list
>   meta-xilinx@yoctoproject.org  xil...@yoctoproject.org>
>   https://lists.yoctoproject.org/listinfo/meta-xilinx
> 
> 
>   --
> 
>   Giordon Stark

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