Re: fixed partitions issue

[Stefano Manni <stefano.manni@gmail.com>]

Hi Ahmad,

On mer, lug 30 2025 at 14:40:20 +02:00:00, Ahmad Fatoum 
<a.fatoum@pengutronix.de> wrote:
>> 
>>      barebox_state: partition@200000 {
>>          label = "barebox-state";
>>          reg = <0x0100000 0x100000>;
> 
> The first cell is the start address, so this should be 0x200000, not
> 0x0100000.

you are right I was in the mid of a change to resize partitions. Now 
the dts looks like:

barebox: partition@0 {
    label = "barebox";
    reg = <0x0 0x0200000>;
};

barebox_env: partition@200000 {
    label = "barebox-env";
    reg = <0x0200000 0x040000>;
};

barebox_state: partition@240000 {
    label = "barebox-state";
    reg = <0x0240000 0x040000>;
};

> 
> Do you maybe have board code that calls devfs_add_partition()?

no

> 
> The output of devinfo in both versions would be useful as well to
> understand this.

unfortunately devinfo reports the same information on both v2025.01.0 
and v2025.07.0

`-- 2008000.spi@2008000.of
   `-- flash@00
	  `-- nor0
		 `-- 0x00000000-0x00ffffff (    16 MiB): /dev/nor0
		 `-- nor0.barebox
			`-- 0x00000000-0x001fffff (     2 MiB): /dev/nor0.barebox
		 `-- nor0.barebox-env
			`-- 0x00000000-0x0003ffff (   256 KiB): /dev/nor0.barebox-env
		 `-- nor0.barebox-state
			`-- 0x00000000-0x0003ffff (   256 KiB): /dev/nor0.barebox-state


On v2025.07.0 every time I write barebox-env part (e.g. with nv 
command) also barebox
part is written. This on v2025.01.0 does not happen.

I supposed the problem was in the fixed-partition bindings but maybe it 
is somewhere
else, for example in the spinor driver.

Is that something I may test to understand more?

Best,
Stefano