WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: piCore64 13.0 released (64-bit)  (Read 2436 times)

Offline Paul_123

  • Administrator
  • Hero Member
  • *****
  • Posts: 757
piCore64 13.0 released (64-bit)
« on: June 06, 2021, 09:46:12 AM »
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
« Last Edit: June 06, 2021, 12:57:35 PM by Paul_123 »

Offline Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 13343
Re: piCore64 13.0 released (64-bit)
« Reply #1 on: June 06, 2021, 10:09:45 AM »
It would maybe be good to put a link to the RPi4 boot loader  :)

Offline Paul_123

  • Administrator
  • Hero Member
  • *****
  • Posts: 757
Re: piCore64 13.0 released (64-bit)
« Reply #2 on: June 06, 2021, 12:56:21 PM »
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.
« Last Edit: June 06, 2021, 12:58:54 PM by Paul_123 »

Offline Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 13343
Re: piCore64 13.0 released (64-bit)
« Reply #3 on: June 07, 2021, 02:13:01 AM »
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  :(

Offline Rich

  • Administrator
  • Hero Member
  • *****
  • Posts: 9583
Re: piCore64 13.0 released (64-bit)
« Reply #4 on: June 07, 2021, 04:23:01 AM »
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? ???

Offline Rich

  • Administrator
  • Hero Member
  • *****
  • Posts: 9583
Re: piCore64 13.0 released (64-bit)
« Reply #5 on: June 07, 2021, 05:22:08 AM »
Hi Juanito
Quote
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.

Quote
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:
Quote
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
« Last Edit: June 07, 2021, 04:50:02 PM by Rich »

Offline rullolex

  • Full Member
  • ***
  • Posts: 134
    • Rullolex
Re: piCore64 13.0 released (64-bit)
« Reply #6 on: June 07, 2021, 09:23:40 AM »
Hi,

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

Offline Paul_123

  • Administrator
  • Hero Member
  • *****
  • Posts: 757
Re: piCore64 13.0 released (64-bit)
« Reply #7 on: June 07, 2021, 02:35:00 PM »
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.

Offline rullolex

  • Full Member
  • ***
  • Posts: 134
    • Rullolex
Re: piCore64 13.0 released (64-bit)
« Reply #8 on: June 07, 2021, 09:59:22 PM »
Hi,

I have booted piCore 64 on my rpi4without doing anything else and it works. sorry, for the mi misunderstanding
« Last Edit: June 07, 2021, 10:08:35 PM by rullolex »

Offline Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 13343
Re: piCore64 13.0 released (64-bit)
« Reply #9 on: June 08, 2021, 01:58:06 AM »
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...

Offline Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 13343
Re: piCore64 13.0 released (64-bit)
« Reply #10 on: June 12, 2021, 08:40:45 AM »
piCore64 13.0 seems to be working fine for me - using f2fs for mmcblk0p2  :)

Offline Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 13343
Re: piCore64 13.0 released (64-bit)
« Reply #11 on: June 12, 2021, 09:37:31 AM »
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

Offline Paul_123

  • Administrator
  • Hero Member
  • *****
  • Posts: 757
Re: piCore64 13.0 released (64-bit)
« Reply #12 on: June 12, 2021, 06:47:51 PM »
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.


Offline Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 13343
Re: piCore64 13.0 released (64-bit)
« Reply #13 on: June 13, 2021, 06:04:33 AM »
Ah - it's dtoverlay=vc4-kms-v3d-pi4 that's required  :-[

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

Offline Paul_123

  • Administrator
  • Hero Member
  • *****
  • Posts: 757
Re: piCore64 13.0 released (64-bit)
« Reply #14 on: June 13, 2021, 08:58:05 AM »
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