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

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

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

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

> 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

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

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

[meta-xilinx] Zynq spidev name

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.