Need advise with u-boot on SH-7785LCR

[Simon Glass]

Hi John,

On Mon, 6 Nov 2023 at 15:00, John Paul Adrian Glaubitz
<glaubitz at physik.fu-berlin.de> wrote:
>
> Hi Simon,
>
> On Sun, 2023-11-05 at 16:29 +0000, Simon Glass wrote:
> > No, sorry I don't have any idea about that. You could check the
> > MAINTAINERS files in U-Boot and Linux for other people, perhaps, or
> > check commit / blame logs?
>
> It seems that the flash memory is mapped to block devices by the kernel:
>
> root at tirpitz:~> dmesg|grep -i flash
> [    1.592000] physmap-flash physmap-flash.0: physmap platform flash device: [mem 0x00000000-0x03ffffff]
> [    1.604000] physmap-flash.0: Found 2 x16 devices at 0x0 in 32-bit bank. Manufacturer ID 0x000001 Chip ID 0x002201
> [    1.632000] Creating 4 MTD partitions on "physmap-flash.0":
> root at tirpitz:~> ls -l /dev/mtdblock*
> brw-rw---- 1 root disk 31, 0 Sep 30 12:35 /dev/mtdblock0
> brw-rw---- 1 root disk 31, 1 Sep 30 12:35 /dev/mtdblock1
> brw-rw---- 1 root disk 31, 2 Sep 30 12:35 /dev/mtdblock2
> brw-rw---- 1 root disk 31, 3 Sep 30 12:35 /dev/mtdblock3
> root at tirpitz:~>
>
> So, I assume, I should just be able to write u-boot.bin to /dev/mtdblock0?

Maybe, but you will likely brick the device if you have no other way
to write to flash.

Regards,
Simon


>
> Adrian
>
> --
>  .''`.  John Paul Adrian Glaubitz
> : :' :  Debian Developer
> `. `'   Physicist
>   `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913