SD Card with NRF54L15 and 3.1.0 SDK and 3.0.0 toolchain

RE: SD Card with NRF54L15 and 3.1.0 SDK and 3.0.0 toolchain

Menon — Fri, 30 Jan 2026 09:53:58 GMT

Hello Jade,

I see that you already have a similar case open where you are discussing the same issue with my colleague. In that case, I would recommend closing this ticket and continuing the discussion in the original thread you created.

Please share the logs in the older ticket, along with details on whether you used a logic analyzer.

I’m closing this ticket as it is a duplicate of 355696.

Kind regards,
Abhijith

RE: SD Card with NRF54L15 and 3.1.0 SDK and 3.0.0 toolchain

jade08 — Thu, 29 Jan 2026 14:25:54 GMT

Hello,

Thank you for your answer!
This is my error message : SEGGER J-Link V8.86 - Real time terminal output
SEGGER J-Link (unknown) V1.0, SN=1057762330
Process: JLink.exe
*** Booting nRF Connect SDK v2.9.2-4ab7b98fc76f ***
*** Using Zephyr OS v3.7.99-aa34a5632971 ***
[00:00:00.448,347] <inf> sd: Card does not support CMD8, assuming legacy card
[00:00:00.449,781] <err> main: Storage init ERROR!
Impossible de lire le MBR (disk_access_read)
[00:00:00.468,956] <inf> sd: Card does not support CMD8, assuming legacy card
[00:00:00.470,382] <err> fs: fs mount error (-5)
Partition SD1 non montée (code -5)
[00:00:00.489,532] <inf> sd: Card does not support CMD8, assuming legacy card
[00:00:00.490,957] <err> fs: fs mount error (-5)
Partition SD2 non montée (code -5)
OKOKOK[00:00:00.491,011] <err> fs: mount point not found!!
OK[00:00:00.491,023] <err> main: Erreur d'ouverture du fichier (-2)
[00:00:00.491,032] <err> fs: fs not mounted (mp == 0x20000ee0)
Partition SD1 non demontée (code -22)
[00:00:00.491,054] <err> fs: fs not mounted (mp == 0x20000f04)
Partition SD2 no

RE: SD Card with NRF54L15 and 3.1.0 SDK and 3.0.0 toolchain

Menon — Thu, 29 Jan 2026 10:52:41 GMT

Hello,

Have you collected any logs from the device to see what might be going wrong, or are you seeing any error messages from the device? I would also recommend checking the SPI communication lines, try using a logic analyzer if possible.

To verify whether there are any configuration changes in SDK v3.2.x, I suggest reviewing the Migration Guide.

Kind regards,
Abhijith