cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
rjlu
Visitor
Visitor
1,744 Views
Registered: ‎07-10-2009

fail to build user module in petalinux 2017.2

Jump to solution

Hello,

 

I am using Petalinux 2017.2 running on Ubuntu 16.04.

 

I am generating a template module using 

petalinux-create -t modules -n laserCNTRL --enable

 After adding some simple lines to laserCNTRL.c file, run

   petalinux-build -c laserCNTRL

But  the module build fails, can anyone tell the reason?

 

~/Z7_project/z7_io_linux$ petalinux-build -c laserCNTRL
[INFO] building laserCNTRL
[INFO] sourcing bitbake
INFO: bitbake laserCNTRL
Loading cache: 100% |###################################################################| Time: 0:00:00
Loaded 3235 entries from dependency cache.
Parsing recipes: 100% |#################################################################| Time: 0:00:01
Parsing of 2447 .bb files complete (2414 cached, 33 parsed). 3237 targets, 224 skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies
Initialising tasks: 100% |##############################################################| Time: 0:00:06
Checking sstate mirror object availability: 100% |######################################| Time: 0:00:00
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
ERROR: petalinux-user-image-1.0-r0 do_rootfs: laserCNTRL not found in the feeds (plnx_arm cortexa9t2hf-neon cortexa9t2hf-vfp cortexa9hf-neon cortexa9hf-vfp armv7at2hf-neon armv7ahf-neon armv7at2hf-vfp armv7ahf-vfp armv6thf-vfp armv6hf-vfp armv5tehf-vfp armv5ehf-vfp armv5thf-vfp armv5hf-vfp noarch any all) in /home/owbama/Z7_project/z7_io_linux/build/tmp/deploy/rpm.
ERROR: petalinux-user-image-1.0-r0 do_rootfs: This is often caused by an empty package declared in a recipe's PACKAGES variable. (Empty packages are not constructed unless ALLOW_EMPTY_<pkg> = '1' is used.)
ERROR: petalinux-user-image-1.0-r0 do_rootfs: Function failed: do_rootfs
ERROR: Logfile of failure stored in: /home/owbama/Z7_project/z7_io_linux/build/tmp/work/plnx_arm-xilinx-linux-gnueabi/petalinux-user-image/1.0-r0/temp/log.do_rootfs.11231
ERROR: Task (/home/owbama/Z7_project/z7_io_linux/project-spec/meta-plnx-generated/recipes-core/images/petalinux-user-image.bb:do_rootfs) failed with exit code '1'
NOTE: Tasks Summary: Attempted 2403 tasks of which 2389 didn't need to be rerun and 1 failed.

Summary: 1 task failed:
/home/owbama/Z7_project/z7_io_linux/project-spec/meta-plnx-generated/recipes-core/images/petalinux-user-image.bb:do_rootfs
Summary: There were 3 ERROR messages shown, returning a non-zero exit code.
ERROR: Failed to build laserCNTRL
webtalk failed:PetaLinux statistics:extra lines detected:notsent_nofile!
webtalk failed:Failed to get PetaLinux usage statistics!

 

 

 

 

0 Kudos
1 Solution

Accepted Solutions
rjlu
Visitor
Visitor
2,586 Views
Registered: ‎07-10-2009

I figure out : there should not have any upper case letter in the module name.

View solution in original post

0 Kudos
4 Replies
rjlu
Visitor
Visitor
1,707 Views
Registered: ‎07-10-2009

Because it's a simplest try with module following UG1144, it seem to be some petalinux interal bugs. Did anyone has these problems with module creation in petalinux 2017.2??

0 Kudos
rjlu
Visitor
Visitor
1,694 Views
Registered: ‎07-10-2009

I check related directories:

    Under. /build/temp/work/plnx_arm-xilinx-linux-gnueabi/laserCNTRL/1.0-r0/deploy-rmps/plnx_arm, there are two subdirctories, one is ./kernel-module-lasercntrl-1.0-r0.plnx_arm.rpm, in which laserCNTRL.ko stays, the other is ./laserCNTRL-dev-1.0-r0.plnx_arm.rpm, an empty directory.

   At the same time, under . /build/temp/work/plnx_arm-xilinx-linux-gnueabi/petalinux-user-image/1.0-r0/rpms/plnx_arm/, a copy of laserCNTRL-dev-1.0-r0.plnx_arm.rpm exists, but is empty.

   So do_rootfs uses this empty package and claims an error.

   Why does the petalinux not copy  kernel-module-lasercntrl-1.0-r0.plnx_arm.rpm to be used by do_rootfs?

   How to creat and build modules with petalinux 2017.2 correctly??

   Thanks.

0 Kudos
rjlu
Visitor
Visitor
1,693 Views
Registered: ‎07-10-2009

At the same time, a copy of laserCNTRL-dev-1.0-r0.plnx_arm.rpm  which is also empty is found under . /build/temp/deploy/rpm/plnx_arm/.

0 Kudos
rjlu
Visitor
Visitor
2,587 Views
Registered: ‎07-10-2009

I figure out : there should not have any upper case letter in the module name.

View solution in original post

0 Kudos