Hi Richard, I have tried with the latest version of Zeus (d88d62c20d7d8da85f02edb170dae0280624ad7e) and the problem is not solved yet. Do you need more information on my side?
Regards, Adrian On 25.08.2020 17:16, Adrian Fiergolski wrote: > Hi Richard, > > Thank you for your reply. > > On 25.08.2020 15:05, Richard Purdie wrote: >> On Tue, 2020-08-25 at 14:47 +0200, Adrian wrote: >>> Hi, >>> >>> After recent update of poky, I started to experience an issue with >>> devtool. Currently, I am using the latest zeus version. I have a >>> multiconfig environment (Xilinx ZynqMP+ with ARM64 and Microblaze). I >>> am >>> modifying my recipe compiled from local sources. The custom target >>> machine configuration sets DEAULTTUNE="cortexa53" >>> >>> When I call: >>> >>> $> devtool build peary >>> $>devtool deploy-target peary root@192.168.33.167 >>> >>> I get the error: >>> >>> ERROR: No files to deploy - have you built the peary recipe? If so, >>> the >>> install step has not installed any files. >>> >>> In fact, I see that 'devtool build' creates image under >>> '/home/afiergol/poky/build/tmp/work/aarch64-poky- >>> linux/peary/1.0+git999-r0/image', >>> while 'devtool deploy-target' search for files under >>> '/home/afiergol/poky/build/tmp/work/cortexa53-poky-linux- >>> gnueabi/peary/1.0+git999-r0/image' >>> >>> If in the 'peary' recipe I add a line >>> >>> PACKAGE_ARCH = "${MACHINE_ARCH}" >>> >>> 'devtool deploy-target' starts to search under >>> '/home/afiergol/poky/build/tmp/work/aarch64-poky-linux- >>> gnueabi/peary/1.0+git999-r0/image' >>> >>> If further, I fix in the 'peary' recipe: >>> >>> TARGET_OS = "linux" >>> >>> 'devtool deploy-target' properly deploys the binaries to the target >>> machine. >>> >>> However, as I explained, I had to fix in the recipe PACKAGE_ARCH and >>> TARGET_OS variables. It is required only for devtool to work, as >>> bitbake >>> builds properly my custom Linux image containing the recipe without >>> those variables being set anywhere in my layer. >>> >>> Has anybody else experienced a similar issue? Could somebody give a >>> reference (I didn't find) to documentation which explains why and how >>> those variables need to be set (I especially concerned about >>> TARGET_OS)? >> devtool is working for other recipes in oe-core so this peary recipe is >> probably doing something which is confusing devtool. Or its perhaps the >> machine configuration. Is that a public recipe? If not, is there a >> recipe you could share which shows the issue? >> >> Basically we need some way to reproduce the issue to be able to >> comment. You certainly should not have to set those variables. >> >> Cheers, >> >> Richard >> > I am enclosing the recipe to this message (peary.bb). > > When it comes to the machine configuration, its an extension of > meta-xilinx > (https://github.com/adrianf0/meta-xilinx/tree/rel-v2020.1_fastree3d). > Though, I can't share with you the full conf file, the issue related parts: > > #@TYPE: Machine > #@NAME: falcon-zynqmp > #@DESCRIPTION: Machine support for Fastree SoC board. > # > SOC_VARIANT ?= "eg" > DEFAULTTUNE_falcon-zynqmp = "cortexa53" > require conf/machine/include/soc-zynqmp.inc > require conf/machine/include/machine-xilinx-default.inc > > MACHINE_FEATURES = "rtc ext2 ext3 vfat" > > SERIAL_CONSOLE = "115200 ttyPS0" > SERIAL_CONSOLES_CHECK = "${SERIAL_CONSOLES}" > > PREFERRED_PROVIDER_virtual/kernel ?= "linux-xlnx" > PREFERRED_PROVIDER_virtual/bootloader ?= "u-boot-xlnx" > > EXTRA_IMAGEDEPENDS += " \ > u-boot-zynq-scr \ > arm-trusted-firmware \ > virtual/boot-bin \ > virtual/bootloader \ > virtual/bitstream \ > " > > The local.conf, has nothing special, probably this is the most related > to the issue: MACHINE ??= "falcon-zynqmp" > > Regards, > > Adrian >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#50938): https://lists.yoctoproject.org/g/yocto/message/50938 Mute This Topic: https://lists.yoctoproject.org/mt/76406086/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-