Sysupgrade image not created, why?

Hi All,

I try to define firmware creating rules, like

define Device/demoboard
  DEVICE_TITLE := Demoboard Camera
  DEVICE_DTS := rts3916n_evb
  SUPPORTED_DEVICES := qfn88_evb
  KERNEL_NAME := linux-$(LINUX_VERSION)/vmlinuz.bin
  KERNEL = kernel-bin
  FILESYSTEMS := squashfs
  IMAGES := sysupgrade.img
  IMAGE/sysupgrade.img := sysupgrade-tar | append-metadata
TARGET_DEVICES += demoboard

But, when I do "make V=s", sysupgrade.img did not be created. The log is

Exportable Squashfs 4.0 filesystem, xz compressed, data block size 262144
	compressed data, compressed metadata, compressed fragments,
	no xattrs, compressed ids
	duplicates are removed
Filesystem size 8848.19 Kbytes (8.64 Mbytes)
	30.22% of uncompressed filesystem size (29281.71 Kbytes)
Inode table size 12648 bytes (12.35 Kbytes)
	21.17% of uncompressed inode table size (59754 bytes)
Directory table size 17266 bytes (16.86 Kbytes)
	45.28% of uncompressed directory table size (38130 bytes)
Number of duplicate files found 195
Number of inodes 1796
Number of files 1371
Number of fragments 46
Number of symbolic links  278
Number of device nodes 1
Number of fifo nodes 0
Number of socket nodes 0
Number of directories 146
Number of ids (unique uids + gids) 1
Number of uids 1
	root (0)
Number of gids 1
	root (0)
**----> Firmware should be created here.**
# call file system function call to create rootfs

Anyone can help? why sysupgrade.img did not be created? any specific rule I missed? Thanks.

More like a guess from me because I have no idea what you are doing but are you sure about $(something) because my experience for Linux this far is that it should normally be like this ${something}

Hi flygarn12,

It should be fined. I have another platform which use $(something) works well.
And, I try to change $(something) to ${something} at .mk, still no luck.

Im still checking if there is a condition to check IMAGES and call build firmware.

1 Like

Anyone can help? Any suggestion would be grateful. Thanks.

Hi all,

I figure out the problem because of the wrong typo at

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.