Difference: MicroSdBlocks (99 vs. 100)

Revision 1002022-10-02 - PeterSchmid

Line: 1 to 1

META TOPICPARENT	name="WebHome"

%DASHBOARD{ section="banner"

Line: 114 to 114

The main flash array is divided into erase units called sectors. The sectors are organized either as a hybrid combination of 4-KB and 64-KB sectors, or as uniform 256-KB sectors.

Changed:

<
< 32 4 KiB sectors and 254 64 KiB sectors. What a pain, why use STM this Flash? To simplify writing, only the first 4 KiB of the 64 KiB sectors are used. That means (32 + 254) * 4 KiB = 1140 KiB are available for the volume.

>
>

32 4 KiB sectors and 254 64 KiB sectors. What a pain, why use STM this Flash? To simplify writing, only the first 4 KiB of the 64 KiB sectors are used. That means (32 + 254) * 4 KiB = 1140 KiB are available for the volume. To make it even simpler, I use only 64 KiB sectors, that means there are 256 sectors and therefore 1 MiB available for the volume.

Create a 1 MiB FAT filesystem as a loop device on Linux (or use the already prepared fd-1MiB.img):

$ dd if=/dev/zero of=fd-1MiB.img bs=512 count=2048
# losetup /dev/loop1 fd-1MiB.img
# mkfs -t vfat /dev/loop1
# mount -o loop /dev/loop1 /mnt

Copy the the files and directories with cp or tar to the mounted image, e.g.

# cd sdcard
# tar cf - etc fsr home man README.md | tar xvf - -C /mnt

Umount the loop-device and copy the file to a SD-card.

Copy the filesystem to the flash disk on the target Mecrisp-Cube WB5M Discovery system:

dd 1:/boot/fd-1MiB.img 0:

STM32WB Feather (SPI W25Q128)

View topic | History: r105 < r104 < r103 < r102 | More topic actions...