| 12 Jul 2023 |
Pratham Patel | Just a sec | 17:42:10 |
Pratham Patel | I use this partition layout for the first two partitions
https://github.com/thefossguy/archlinux-visionfive2/blob/master/create-image.sh#L85 | 17:42:46 |
Pratham Patel | Then, you dd u-boot-spl.bin.normal.out to part1 and visionfive2_fw_payload.img to part2 | 17:44:13 |
Alex | So 4 partitions:
- SPL (u-boot metadata)
- u-boot (flat binary)
- boot (FAT)
- root
Makes sense. | 17:44:29 |
Pratham Patel | So instead of reading firmware from flash, the firmware is entirely read from the SD card ;) | 17:44:31 |
Pratham Patel | In reply to @alex:tunstall.xyz
So 4 partitions:
- SPL (u-boot metadata)
- u-boot (flat binary)
- boot (FAT)
- root
Makes sense. Exactly! | 17:44:44 |
Pratham Patel | But be vary of the sectors where the partions start and end | 17:44:56 |
Pratham Patel | There's a reason why my script starts the first partition at 4096 ;) | 17:45:19 |
Alex | Oh does the bootloader expect the partitions to be at specific offsets? | 17:45:20 |
Pratham Patel | Yes :) | 17:45:48 |
Pratham Patel | But that's the ZSBL so it won't ever change | 17:46:03 |
Pratham Patel | That's permanent now. For better or for worse | 17:46:12 |
Pratham Patel | In reply to @alex:tunstall.xyz
$ cat /proc/mtd
dev: size erasesize name
mtd0: 00020000 00001000 "spl"
mtd1: 00300000 00001000 "uboot"
mtd2: 00100000 00001000 "data"
mtd0 has a size of 128KiB, but the latest versions of u-boot exceed that. Nothing like this, where the partition table layout breaks ;) | 17:46:46 |