After changing QSPI to SPI, prj_release.conf can no longer be used

[SunHuang]

As stated in the title, when I set CONFIG_CHIP_FACTORY_DATA_BUILD to n, the following compilation error occurs.

log_n.zip

However, if I keep it as y, the MCU fails to function and gets stuck in the following code.

FUNC_NORETURN __weak void arch_system_halt(unsigned int reason)
{
    ARG_UNUSED(reason);

    /* TODO: What's the best way to totally halt the system if SMP
     * is enabled?
     */

    (void)arch_irq_lock();
    for (;;) {
        /* Spin endlessly */
    }
}

These issues do not occur in prj.conf.

Please note that I am using a clean NCS 2.9.0 Matter Lock project.

The attachment below contains the modifications I made

0456.config.zip

[AHaug]

Hi SunHuang,

How is the project going?

I was able to successfully replace QSPI with SPI in a sample by following https://academy.nordicsemi.com/courses/nrf-connect-sdk-intermediate/lessons/lesson-9-bootloaders-and-dfu-fota/topic/exercise-3-dfu-with-external-flash/. Have you followed these steps?

Kind regards,
Andreas

[SunHuang]

Hi,

Here is the memory report I generated. My current situation is that I can run it normally with prj.conf, but prj_release.conf causes the MCU to crash.

Can you run it normally with prj_release.conf? If possible, please share your configuration for my reference. Thank you!

[AHaug]

https://github.com/NordicDeveloperAcademy/ncs-inter/tree/main/v2.9.0-v2.7.0/l9/l9_e3_sol/spi 

SunHuang said:

Can you run it normally with prj_release.conf?

If the release configuration has the relevant configurations, yes. Add the file suffix "west build -b <board_name> -- -DFILE_SUFFIX=release"

Kind regards,
Andreas