QSPI flash hangs after BLE bonding on nRF54L15 (sQSPI / LittleFS)

RE: QSPI flash hangs after BLE bonding on nRF54L15 (sQSPI / LittleFS)

robonordic — Wed, 15 Apr 2026 16:30:58 GMT

We tried a number of configurations, time out etc. I'll try to put together a minimal sample, but it will take a few days. (deadlines loom)

For now we're saving the keys in retained memory, which is not optimal as they get erased on reset/program flash.

RE: QSPI flash hangs after BLE bonding on nRF54L15 (sQSPI / LittleFS)

Vidar Berg — Tue, 07 Apr 2026 06:10:13 GMT

robonordic , did you modify the driver to add the timeout like OP and are you also using the nRF54L15 chip? And do you have a minimal sample which I can use to reproduce this issue on my end?

RE: QSPI flash hangs after BLE bonding on nRF54L15 (sQSPI / LittleFS)

robonordic — Fri, 03 Apr 2026 20:26:05 GMT

We're also having problems with external flash not working after BT bonding. The external flash is using the FLPR soft peripheral. We can access the flash OK, but BT bonding is unable to save the keys.



*** Using Zephyr OS v4.1.99-ff8f0c579eeb *** 
[00:00:02.271,158]  ble: ble addr: 27:43:C5:46:40:E1 
[00:00:02.271,360]  main: BT mac addr: 27:43:C5:46:40:E1 
[00:00:02.271,603]  littlefs_storage: little_fs_test: Test r/w files on littlefs 
[00:00:02.285,021]  littlefs_storage: fs_statvfs, mount: /lfs1: block sz: 16; frag sz: 65536; blocks: 64; free blks: 59 
[00:00:02.285,357]  littlefs_storage: storage free space: 944 
[00:00:02.285,616]  littlefs_storage: little_fs_test: lfs_fs_stat, blocks: 0; size: 91389; vers: 131073; max name 0 
[00:00:02.440,956]  imu: IMU thread started 
[00:00:05.270,921]  nus: streaming data task start.. 
[00:10:01.129,651]  main: clock time: 01/01/1970 00:10:01 
[00:10:01.541,810]  flash_mspi_nor: perform_xfer: transceive() failed: -116 
[00:10:01.542,072]  flash_mspi_nor: Read xfer failed: -116 
[00:10:01.542,327]  fs: file open error (-5) 
[00:10:01.542,567]  ble: BT connected 
[00:10:01.659,059]  ble: Security changed: 14:14:7D:95:6F:46 (public) level 4 
[00:10:02.318,750]  ble: MTU exchanged: 247 
[00:10:02.319,263]  bt_l2cap: Ignoring data for unknown channel ID 0x003a 
[00:10:02.320,476]  littlefs: WEST_TOPDIR/modules/fs/littlefs/lfs.c:1386: Corrupted dir pair at {0x1, 0x0} 
[00:10:02.320,804]  fs: file open error (-14) 
[00:10:03.549,018]  nus: NUS notify - Enabled 
[00:10:03.609,015]  nus: nus_data_rcvd: nus data received, command 0x1, len 5

RE: QSPI flash hangs after BLE bonding on nRF54L15 (sQSPI / LittleFS)

markuckermann — Tue, 17 Mar 2026 14:50:23 GMT

Don't know if related but we also see sQSPI hangs, although on the LM20 rather than L15. See

devzone.nordicsemi.com/.../nrf54lm20-sqspi-lock-ups

RE: QSPI flash hangs after BLE bonding on nRF54L15 (sQSPI / LittleFS)

Vidar Berg — Mon, 16 Mar 2026 10:48:50 GMT

Hello,

The only relation I could think of between the bonding procedure and littlefs was if both were trying to store something to the same flash device and there was some potential issue with concurrency handling. Would you be able to provide a minimal project here or in a private ticket that would allow me to reproduce this issue here on a nRF54L15 DK?

Best regards,

Vidar

EDIT: Please also let me know what SDK version you are using. Perhaps the issue you are seeing may have been fixed in a later version?

RE: QSPI flash hangs after BLE bonding on nRF54L15 (sQSPI / LittleFS)

Toni — Fri, 13 Mar 2026 07:59:27 GMT

Hello,

In an internal storage, as could be seen from generated `partitions.yml` below.

app:
  address: 0x0
  end_address: 0x17b000
  region: flash_primary
  size: 0x17b000
bootconf:
  address: 0xffd080
  end_address: 0xffd084
  region: bootconf
  size: 0x4
external_flash:
  address: 0x0
  device: MX25R64
  end_address: 0x800000
  region: external_flash
  size: 0x800000
littlefs_storage:
  address: 0x0
  device: MX25R64
  end_address: 0x800000
  region: external_flash
  size: 0x800000
otp:
  address: 0xffd500
  end_address: 0xffd9fc
  region: otp
  size: 0x4fc
settings_storage:
  address: 0x17b000
  end_address: 0x17d000
  placement:
    after:
    - app
    before:
    - end
  region: flash_primary
  size: 0x2000
sram_primary:
  address: 0x20000000
  end_address: 0x2003c000
  region: sram_primary
  size: 0x3c000

I hope it helps. let me know if you need any additional information, please

RE: QSPI flash hangs after BLE bonding on nRF54L15 (sQSPI / LittleFS)

Vidar Berg — Thu, 12 Mar 2026 13:19:33 GMT

Hello,

Thanks for the detailed report. Before I attempt to investigate this further, could you please confirm if the bonding data (settings_storage) is located in the internal or external memory?

Thank you,

Vidar