Tiny Core Base > piCore Final Releases

piCore64 13.0 released (64-bit)

<< < (2/4) > >>

Rich:
Hi Juanito

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

--- End quote ---
I thought FAT16 was limited to 2 or 4 Gbytes.


--- Quote ---
--- Code: ---mkfs.fat: "mkfs.fat: unable to open /dev/mmcblk0p1: No such file or directory
--- End code ---

--- End quote ---
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.
--- End quote ---

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

--- Code: ---sudo blockdev --rereadpt /dev/mmcblk0
--- End code ---

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...

Navigation

[0] Message Index

[#] Next page

[*] Previous page