stm32_ospi_abort return -EIO

[MaazSk]

I am using stm32h730 custom board everything works okay and the device works in XIP mode and I want to exit the device from memory mapped mode and write to memory location and then again enter memory mapped mode but when I perform flash_write the stm32_ospi_abort function fails with the return value as EIO. I have relocated the flash drivers and stm32 flash drivers to RAM. Is there a way to achieve this I am trying the below code for now

int main{
    LOG_INFO( "Doing a read operation..." );
    const device* dev = DEVICE_DT_GET( DT_NODELABEL( is25lp128 ) );
    uint8_t rdata[16] = { 1, 2, 3, 4, 5, 6, 7, 8, 9, 0, 1, 2, 3, 4, 5, 6 };
    int rc = flash_read( dev, 0x800000, rdata, 8 );
    if( rc == 0 )
    {
        for( int i = 0; i < 8; i++ )
        {
            printk( "Before data[%i]: 0x%X\n", i, rdata[i] );
        }
    }
    else
    {
        LOG_ERROR( "Initial read failed" );
    }

    uint8_t wdata[16] = { 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26 };
    rc = flash_write( dev, 0x800000, wdata, 8 );
    if( rc == 0 )
    {
        LOG_INFO( "FLASH_WRITE success!" );
    }
    else
    {
        LOG_ERROR( "FLASH_WRITE failed!" );
    }

    rc = flash_read( dev, 0x800000, rdata, 8 );
    if( rc == 0 )
    {
        for( int i = 0; i < 8; i++ )
        {
            printk( "After data[%i]: 0x%X\n", i, rdata[i] );
        }
    }
    else
    {
        LOG_ERROR( "Read after write FAILED" );
    }
    while( true )
    {
        k_sleep( K_MSEC( 1000 ) );
        LOG_INFO( "TICK" );
    }

    LOG_INFO( "Resetting device" );
    sys_reboot( SYS_REBOOT_COLD );
}

[FRASTM]

Hello @MaazSk

did you activate the log to see if an operation failed before the Abort ?
In your sample above, where do you abort the memory mapped mode ?

According to the stm32h730 refMan, Writing in memorymapped mode is possible (in case you do not execute from this external memory)
Memory-mapped mode configuration
In Memory-mapped mode, the external device is seen as an internal memory but with some
latency during the accesses. Read and write operations are allowed to the external device in
this mode.
Maybe you could try on your own target board

[MaazSk]

Hi @FRASTM,

I am using the external flash with XIP enabled. Sharing the logs for your reference.

The flash write calls the abort function I checked that through west debug and it does call the function stm32_ospi_abort and it fails over here

[MaazSk]

Hi @FRASTM,
I was able to resolve the abort issue as timeout was not set now I am getting the issue in the below command

This is available in zephyr/drivers/flash/flash_stm32_ospi.c function name stm32_ospi_mem_ready. Could you please help me with this

[FRASTM]

What is the external flash memory which is mounted on your hw ?
I am looking for stm32h7xx disco board with external flash (stm32h7b3i-dk or stm32h735g-disco)
to try w/o abort operation = my branch https://github.com/FRASTM/zephyr/tree/stm32h7_ospi_wr_memmap
maybe you could also have a look there

[MaazSk]

The external flash mounted is is25lp128. As I mentioned earlier the abort function is working. I have not included the timeout so it was failing but now it is working.

Also, is your application running in xip mode?

[FRASTM]

The external flash mounted is is25lp128. As I mentioned earlier the abort function is working. I have not included the timeout so it was failing but now it is working.

Also, is your application running in xip mode?

Yes, we have applications running in external flash with XIP, on the stm32h7b3i_dk (for the octospi on stm32h7 but not on the stm32h730)
that's the case with ./samples/application_development/code_relocation_nocopy