How to install packages on rpb?

Products Support HiKey 960
#23

I trying to build it right now.
My next step is getting ssh server on this linux distro, and the ultimate goal is to write a device driver for hikey in order to support new hardware.

#24

My build didn’t generate the rootfs image .

I was expecting something like :
rpb-console-image-hikey960-20172-92.rootfs.img.gz

deploy
├── images
    └── hikey960
          ├── boot-0.0+AUTOINC+7efa39f363-c906d2a849-r0-hikey960-201709846.uefi.img
          ├── boot-hikey960.uefi.img -> boot-0.0+AUTOINC+7efa39f363-r0-hikey960-201709846.uefi.img
          ├── defconfig
          ├── Image -> Image--4.12+git0+2e79817517-r0-hikey960-20170912846.bin
          ├── Image--4.12+git0+2e79817517-r0-hi3660-hikey960-20170913846.dtb
          ├── Image--4.12+git0+2e79817517-r0-hikey960-20170912083846.bin
          ├── Image-hi3660-hikey960.dtb -> Image--4.12+git0+2e79817517-r0-hi3660-hikey960-20170946.dtb
          ├── Image-hikey960.bin -> Image--4.12+git0+2e79817517-r0-hikey960-2017083846.bin
          ├── modules--4.12+git0+2e79817517-r0-hikey960-20183846.tgz
          ├── modules-hikey960.tgz -> modules--4.12+git0+2e79817517-r0-hikey960-2017096.tgz
          ├── rpb-console-image-hikey960-20170983846.rootfs.ext4.gz
          ├── rpb-console-image-hikey960-2017083846.rootfs.manifest
          ├── rpb-console-image-hikey960-20170083846.rootfs.tar.xz
          ├── rpb-console-image-hikey960.ext4.gz -> rpb-console-image-hikey960-20173846.rootfs.ext4.gz
          ├── rpb-console-image-hikey960.manifest -> rpb-console-image-hikey960-20173846.rootfs.manifest
          └── rpb-console-image-hikey960.tar.xz -> rpb-console-image-hikey960-2017093846.rootfs.tar.xz
#25

Filesystem images use names more specific than .img.gz (in this case .ext4.gz).

#26

flashing this didn’t change the kernel :
boot-0.0+AUTOINC+7efa39f363-c906d2a849-r0-hikey960-20170912083846.uefi.img
rpb-console-image-hikey960-20170912083846.rootfs.ext4

I was expecting to see 4.12 on my board, but 4.13 is still there.

#27

As @domi mentioned earlier, updating SRCREV_kernel should result in a v4.13 kernel.

#28

I didn’t update the SRCREV_, but I saw :

Creating the image for HiKey

Creating the mixed tootfs image for HiKey is the same as for Dragonboard-410c, but requires an extra step, as HiKey reads the kernel image to boot from the rootfs (vs a boot partition in the case of Dragonboard-410c). So the 64-bit kernel image and the DTB file must be copied to the 32-bit rootfs, the /boot directory - this is where GRUB looks the kernel image for. E.g.:

mkdir root
mkdir root-64
gunzip -k rpb-minimal-image-hikey-20161014162659.rootfs.ext4.gz
sudo mount -o loop rpb-minimal-image-hikey-20161014162659.rootfs.ext4 root-64/
gunzip -k rpb-weston-image-hikey-32-20161014172406.rootfs.ext4.gz
resize2fs rpb-weston-image-hikey-32-20161014172406.rootfs.ext4 512M
sudo mount -o loop rpb-weston-image-hikey-32-20161014172406.rootfs.ext4 root
sudo cp -r root-64/boot/* root/boot/
cd root
sudo tar xzf …/modules–4.4.11+git-r0-hikey-20161014162659.tgz
cd …
sync
sudo umount root
sudo umount root-64
ext2simg rpb-weston-image-hikey-32-20161014172406.rootfs.ext4 rpb-weston-image-hikey.rootfs.img

SO, I need to manualy update the rootfs everytime

#29

I hate to contradict you but the list of files you shared earlier indicate that you did update SRCREV_kernel (I can’t see how else your kernel image version could include git0+2e79817517):

In the above versioning the 4.12 is not correct (because PV wasn’t updated in the patch I shared yesterday).

#30

Sorry, I mean, I didn’t change the PV line. I built a 4.12 kernel.
Anyhow, I was expecting to see a 4.12 kernel, not 4.13. So it seems that I know how to compile, but not how to flash.

#31

PV does not control what version of the kernel is built. It only controls what the package containing the kernel is called.