Partition manger : unable to specify ext_flash_dev

[Louis]

Relevant configuration and device tree snippets:

CONFIG_BOOTLOADER_MCUBOOT=y
CONFIG_PM_EXTERNAL_FLASH_MCUBOOT_SECONDARY=y
CONFIG_SPI_NOR=y

&spi3 {
compatible = "nordic,nrf-spim";
status = "okay";

sck-pin = <8>; /* P0.8 */
mosi-pin = <9>; /* P0.9 */
miso-pin = <10>; /* P0.10 */
    cs-gpios = <&gpio0 11 GPIO_ACTIVE_LOW>;

mx25r32: mx25r3235f@0 {
compatible = "jedec,spi-nor";
reg = <0>;
spi-max-frequency = <80000000>;
label = "MX25R32";
jedec-id = [c2 28 16];
size = <33554432>;
};
};

/ {
        chosen {
                nordic,pm-ext-flash = &mx25r32;
        };

};

Even if pm-ext-flash is defined as a SPI NOR, looks like the partition manager ignores the definition and uses on QSPI resulting in undefined macro expansions related to QSPI NOR.

I assume that dt_chosen(ext_flash_dev PROPERTY nordic,pm-ext-flash) does not apply and that the partition manager falls back on qspi.

[Håkon Alseth]

Hi,

 

Yes, there seems to be an issue declaring spi-nor device on a SoC that has qspi capabilities.

I'll report this internally.

 

Is there a specific reason why you're interfacing it as a standard SPI device, and not a QSPI flash? MX25R32 should be able to do up to quad SPI.

 

Kind regards,

Håkon

[Louis]

This is a custom board. The routing was a little tight so I was asked to check if I could work with an SPI Flash instead and that's how I hit the issue. No big deal for us. The designer managed to route his design using a QSPI Flash in the end.

[Håkon Alseth]

Hi,

 

Louis said:

This is a custom board. The routing was a little tight so I was asked to check if I could work with an SPI Flash instead and that's how I hit the issue. No big deal for us. The designer managed to route his design using a QSPI Flash in the end.

Its great to hear that you were able to work around this issue. My apologies for the inconvenience!

 

Kind regards,

Håkon