Customer did follow the workaround mentioned in answer record but he still sees 
linker errors:

\ Building target: pmu-firmware.elf
Invoking: MicroBlaze gcc linker
mb-gcc -nostartfiles -Wl,-T -Wl,../src/lscript.ld 
-L../../pmu-firmware_bsp/psu_pmu_0/lib -mlittle-endian -mxl-barrel-shift 
-mxl-pattern-compare -mcpu=v9.2 -mxl-soft-mul -o "pmu-firmware.elf"  
./src/idle_hooks.o ./src/pm_api.o ./src/pm_binding.o ./src/pm_callbacks.o 
./src/pm_clock.o ./src/pm_common.o ./src/pm_config.o ./src/pm_core.o 
./src/pm_ddr.o ./src/pm_extern.o ./src/pm_gic_proxy.o ./src/pm_gpp.o 
./src/pm_master.o ./src/pm_mmio_access.o ./src/pm_node.o ./src/pm_node_reset.o 
./src/pm_notifier.o ./src/pm_periph.o ./src/pm_pll.o ./src/pm_power.o 
./src/pm_proc.o ./src/pm_requirement.o ./src/pm_reset.o ./src/pm_slave.o 
./src/pm_sram.o ./src/pm_system.o ./src/pm_usb.o ./src/xpfw_aib.o 
./src/xpfw_core.o ./src/xpfw_crc.o ./src/xpfw_error_manager.o 
./src/xpfw_events.o ./src/xpfw_interrupts.o ./src/xpfw_ipi_manager.o 
./src/xpfw_main.o ./src/xpfw_mod_dap.o ./src/xpfw_mod_em.o 
./src/xpfw_mod_legacy.o ./src/xpfw_mod_pm.o ./src/xpfw_mod_rtc.o 
./src/xpfw_mod_sched.o ./src/xpfw_mod_stl.o ./src/xpfw_mod_wdt.o 
./src/xpfw_module.o ./src/xpfw_platform.o ./src/xpfw_resets.o 
./src/xpfw_restart.o ./src/xpfw_rom_interface.o ./src/xpfw_scheduler.o 
./src/xpfw_start.o ./src/xpfw_user_startup.o ./src/xpfw_util.o ./src/xpfw_xpu.o 
  -Wl,--start-group,-lxil,-lgcc,-lc,--end-group 
-Wl,--start-group,-lxilfpga,-lxil,-lgcc,-lc,--end-group 
-Wl,--start-group,-lxilsecure,-lxil,-lgcc,-lc,--end-group
../../pmu-firmware_bsp/psu_pmu_0/lib/libxilsecure.a(xsecure_rsa.o): In function 
`XSecure_RsaSignVerification':
(.text.XSecure_RsaSignVerification+0x2c): undefined reference to 
`XGetPSVersion_Info'
collect2: error: ld returned 1 exit status
makefile:36: recipe for target 'pmu-firmware.elf' failed
make: *** [pmu-firmware.elf] Error 1

On Dec 8, 2017, at 10:26 PM, Manjukumar Harthikote Matha 
<manju...@xilinx.com<mailto:manju...@xilinx.com>> wrote:



-----Original Message-----
From: 
meta-xilinx-boun...@yoctoproject.org<mailto:meta-xilinx-boun...@yoctoproject.org>
 [mailto:meta-xilinx-
boun...@yoctoproject.org<mailto:boun...@yoctoproject.org>] On Behalf Of Syed 
Syed
Sent: Thursday, December 07, 2017 9:39 PM
To: meta-xilinx@yoctoproject.org<mailto:meta-xilinx@yoctoproject.org>
Subject: [meta-xilinx] pmu-firmware build failure

[This sender failed our fraud detection checks and may not be who they appear to
be. Learn about spoofing at http://aka.ms/LearnAboutSpoofing]

Hi
  One of our customers using 2017.1 based yocto release is having issues with 
pmu-
firmware not being built as part of bitbake core-image-minimal.

I don't know how this error can get triggered, nor was I able to reproduce this
behavior in any setting.
Any pointers?

-syed

DEBUG: Executing python function sstate_task_prefunc
DEBUG: Python function sstate_task_prefunc finished
DEBUG: Executing shell function do_deploy
install: cannot stat '/home/syeds/extra/TSN_2017.1/xilinx-TSN-
yocto/build/tmp/work/zcu102_zynqmp-xilinx-linux/pmu-
firmware/2017.1+gitAUTOINC+3813f14966-r0/build/pmu-firmware/Release/pmu-
firmware.elf': No such file or directory
WARNING: exit code 1 from a shell command.
ERROR: Function failed: do_deploy (log file is located at
/home/syeds/extra/TSN_2017.1/xilinx-TSN-yocto/build/tmp/work/zcu102_zynqmp-
xilinx-linux/pmu-firmware/2017.1+gitAUTOINC+3813f14966-
r0/temp/log.do_deploy.22510)

Check log.do_configure or log.do_compile to see if there were failures.

Thanks,
Manju

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

Reply via email to