piCore64 13.0 released (64-bit)

[Paul_123]

Team Tiny Core is pleased to announce the release of piCore64-13.0:

Core components

- kernel 5.10.39
- rpi firmware 2021/05/25 (Note rpi4 bootloader has to be upgraded manually. The easiest way is to use rpiImager to put the latest bootloader on a microsdcard and boot your pi)
- glibc-2.32
- busybox-1.33
- gcc-10.2.0
- micropython 1.13

http://www.tinycorelinux.net/13.x/aarch64/releases/RPi/piCore64-13.0.zip

[Juanito]

It would maybe be good to put a link to the RPi4 boot loader 

[Paul_123]

It used to be easier to direct link.   The bootloader repo is here.  https://github.com/raspberrypi/rpi-eeprom. Rpi imager will pull the latest from that repo.

The readme on the repo has basic instructions.

[Juanito]

I compiled rpi-imager for CorePure64 - it fails with:

Code: [Select]

sfdisk: "Checking that no-one is using this disk right now ... OK\n\nDisk /dev/mmcblk0: 14.45 GiB, 15510536192 bytes, 30294016 sectors\nUnits: sectors of 1 * 512 = 512 bytes\nSector size (logical/physical): 512 bytes / 512 bytes\nI/O size (minimum/optimal): 512 bytes / 512 bytes\nDisklabel type: dos\nDisk identifier: 0x2ddfd8be\n\nOld situation:\n\nDevice         Boot Start      End  Sectors  Size Id Type\n/dev/mmcblk0p1       8192 30294015 30285824 14.4G  e W95 FAT16 (LBA)\n\n>>> Created a new DOS disklabel with disk identifier 0xd35f0ab7.\n/dev/mmcblk0p1: Created a new partition 1 of type 'W95 FAT16 (LBA)' and of size 14.4 GiB.\nPartition #1 contains a vfat signature.\n/dev/mmcblk0p2: Ignoring partition.\n/dev/mmcblk0p3: Ignoring partition.\n/dev/mmcblk0p4: Ignoring partition.\n/dev/mmcblk0p5: Done.\n\nNew situation:\nDisklabel type: dos\nDisk identifier: 0xd35f0ab7\n\nDevice         Boot Start      End  Sectors  Size Id Type\n/dev/mmcblk0p1       8192 30294015 30285824 14.4G  e W95 FAT16 (LBA)\n\nThe partition table has been altered.\nCalling ioctl() to re-read partition table.\nSyncing disks.\n"
mkfs.fat: "mkfs.fat: unable to open /dev/mmcblk0p1: No such file or directory\nmkfs.fat 4.2 (2021-01-31)\n"

..when obviously there is a /dev/mmcblk0p1 

[Rich]

Hi Juanito

... right now ... OK\n\nDisk /dev/mmcblk0: 14.45 GiB, 15510536192 bytes, 30294016 sectors\nUnits: ...

What's with all of the escape sequences?

[Rich]

Hi Juanito

Code: [Select]

Device         Boot Start      End  Sectors  Size Id Type
/dev/mmcblk0p1       8192 30294015 30285824 14.4G  e W95 FAT16 (LBA)

I thought FAT16 was limited to 2 or 4 Gbytes.

Code: [Select]

mkfs.fat: "mkfs.fat: unable to open /dev/mmcblk0p1: No such file or directory

Looking here:
https://man7.org/linux/man-pages/man8/sfdisk.8.html
I noticed this:

NOTES         top

       Since version 2.26 sfdisk no longer provides the -R or --re-read
       option to force the kernel to reread the partition table.  Use
       blockdev --rereadpt instead.

Maybe you need to run this to tell the lernel about the partition change:

Code: [Select]

sudo blockdev --rereadpt /dev/mmcblk0

[rullolex]

Hi,

using balana etcher the micro sd is created propertely for rpi4.

[Paul_123]

We are not talking about burning the piCore image, but creating a bootloader disk to update the RPI4 bootloader on flash memory.

piCore has no automated mechanism to do that like RaspiOS.

[rullolex]

Hi,

I have booted piCore 64 on my rpi4without doing anything else and it works. sorry, for the mi misunderstanding

[Juanito]

Adding a delay to driveformatthread.cpp fixed things for running rpi-imager with sudo in CorePure64 and it successfully writes the bootloader update image to an sd card.

Given rpi-imager requires qt-5.x-all to be loaded copy2fs, I'm not sure if it's worth posting an extension...

[Juanito]

piCore64 13.0 seems to be working fine for me - using f2fs for mmcblk0p2 

[Juanito]

By default piCore64 has config.txt:

Code: [Select]

[ALL]
dtoverlay=vc4-kms-v3d
..but as far as I am aware, only vc4-fkms-v3d works with aarch64

[Paul_123]

From everything I can tell, the 64bt kernel supports kms in 5.10,  but perhaps there are userspace drivers that aren’t working for 64bit.

[Juanito]

Ah - it's dtoverlay=vc4-kms-v3d-pi4 that's required 

Both dtoverlay=vc4-kms-v3d-pi4 and dtoverlay=vc4-fkms-v3d work now.

[Paul_123]

That is interesting, as PhilE from RPi says that adding the rpi4 at the end is not to be used.  The firmware knows which dts to use.

https://www.raspberrypi.org/forums/viewtopic.php?f=29&t=288234&start=25#p1742971