Attachments (1) Download All
Nordic Case Info
  • Case ID: 296021
Options

SPI Interface for MicroSD Card

Drew7997

Hello,

I am attempting to mount and write to a microSD card via SPI. I am using the Fat_fs example found under "zephyr/samples/subsys/fs/fat_fs" and I am getting an error code of -5 during disk initialization. 

When I run the same code without the card inserted, I get the exact same behavior. So it almost seems like the driver isn't detecting the card at all. I have check that the sd card is FAT formatted and is working on my computer.

Also when using a logic analyzer, I can see that the MISO, MOSI, CS, and SCK signals appear to be working. However, pretty much all responses from the card (such as the CSD) return empty with all zeros. 

Below is the dts, config, and some notes about the board.

* MISO is tied high by an external resistor. 

Thanks in advance for the help

Parents
  • 0

    Hi,

    Have you tried using a different GPIO for the MISO pin? By default, P0.10 is used for the NFCT peripheral antenna.

    If you have not set the Kconfig CONFIG_NFCT_PINS_AS_GPIOS, the NFCT pins may not be used for other purposes or peripherals.

    Best regards,
    Jørgen

  • 0 in reply to Jørgen Holmefjord

    After updating to v2.1.0 I am now getting and error with disk initialization

    After calling, disk_access_init the error happens here in disk_access_get_di(). The disk access list and node appear to be empty so nothing is ever initialized. 

    . 

    I actually ran into this same problem when I was using v.2.0.2. I fixed it then by adding these settings to my config file

    Are there more settings I need to define for the newer SDK? 

  • 0 in reply to Drew7997
    Drew7997 said:
    Where are the logs saved to? I'm new to developing/debugging in this environment. 

    The logs are output on the selected logger backend, typically UART or RTT. See Logging in nRF Connect SDK for more details.

    Drew7997 said:
    I have made no modifications to the sample.
    Drew7997 said:
    After calling, disk_access_init the error happens here in disk_access_get_di(). The disk access list and node appear to be empty so nothing is ever initialized. 

    Are you building for a custom board? Did you try the sample on a nRF52833 DK first? Did it work with the card?

    If you are using a custom board, can you upload the board files and any overlays you are using? There might be some missing config in for your board.

  • 0 in reply to Drew7997

    I too am getting this error after upgrade to 2.1.0 disk_agget_get_di() for drive "SD" is returning NULL.
    The disk access list is empty; this must have been populated by defalt in the old SDK and in the new not?

    Any progress on this one?

  • 0 in reply to OwainIncus

    Hi Owain,

    No unfortunately no progress yet on my end. I've run out of things to try at the moment. Are you also using the nrf52833?

Reply Children
  • 0 in reply to Drew7997

    Hi Drew,

    No I am 5340 based but I just noticed this in the 2.1.0 build log.
    Sounds suspicious. Just looking....


    -- open-amp version: 1.2.0 (C:/Users/Owain/incus/modules/lib/open-amp/open-amp)
    -- Host: Windows/AMD64
    -- Target: Generic/arm
    -- Machine: arm
    -- C_FLAGS : -Wall -Wextra
    -- Looking for include file fcntl.h
    -- Looking for include file fcntl.h - found
    CMake Warning at C:/Users/Owain/incus/zephyr/CMakeLists.txt:831 (message):
    No SOURCES given to Zephyr library: drivers__disk

    Excluding target from build.


    CMake Warning at C:/Users/Owain/incus/zephyr/CMakeLists.txt:1839 (message):
    __ASSERT() statements are globally ENABLED


    -- Configuring done
    --

  • 0 in reply to OwainIncus

    Interesting, I got that exact same message in 2.0.2 and adding these lines to the config file fixed it:

    In 2.1.0 the issue still persists with those settings

  • 0 in reply to OwainIncus

    Looks as if driver subsys has changed and we nolonger are pulling in driver...

    https://github.com/nrfconnect/sdk-zephyr/commit/a79f48548739839cc07274f7bf100351012a287d

  • 0 in reply to OwainIncus

    I think I have it going past my disk init; at least reading number of blocks and block size OK.

    Here my changes to prj.conf and to my dts file; might help you....

    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    &spi4 {
    status = "okay";
    compatible = "nordic,nrf-spim";
    compatible = "nordic,nrf-spim";
    pinctrl-0 = <&spi4_default>;
    pinctrl-1 = <&spi4_sleep>;
    pinctrl-names = "default", "sleep";
    cs-gpios = <&gpio0 11 GPIO_ACTIVE_LOW>;
    sdhc0: sdhc@0 {
    compatible = "zephyr,sdhc-spi-slot";
    reg = <0>;
    status = "okay";
    mmc {
    compatible = "zephyr,sdmmc-disk";
    status = "okay";
    };
    spi-max-frequency = <8000000>;
    };
    };
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    CONFIG_DISK_DRIVER_SDMMC=y
    CONFIG_SDMMC_SUBSYS=y
    CONFIG_SDHC=y
    CONFIG_SPI_SDHC=y
    CONFIG_SPI=y
    CONFIG_GPIO=y
    CONFIG_DISK_ACCESS=y
    CONFIG_FILE_SYSTEM=y
    CONFIG_FAT_FILESYSTEM_ELM=y
    #CONFIG_FILE_SYSTEM_SHELL=y
    CONFIG_FS_FATFS_LFN=y
    #CONFIG_FS_FATFS_EXFAT=y
    CONFIG_FS_FATFS_MOUNT_MKFS=y
    #CONFIG_FS_FATFS_LFN_MODE_STACK=y
    CONFIG_FS_FATFS_LFN_MODE_HEAP=y
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

Terms of service