SDCard Using FatFS without SDK doesn't compile

[warcomeb-am]

Hi,

During the development of the firmware over nRF5340, I need to modify the ffconf.h file without changing the SDK. Based on this post I copied the FATFS files into the application root in this way: src/fatfs/<files> and into pro.conf I modified the file in this way:

# SDCard & Filesystem
CONFIG_DISK_DRIVERS=y
CONFIG_DISK_DRIVER_SDMMC=y
CONFIG_DISK_ACCESS=y

# Added FATFS library into application project folder!
CONFIG_FILE_SYSTEM=n
CONFIG_FAT_FILESYSTEM_ELM=n

When I try to compile (pristine build) the project, I receive the following errors:

Y:\Projects\X\src\fatfs\ff.c:4989: multiple definition of `f_mkdir'; app/libapp.a(ff.c.obj):Y:\Projects\X\src\fatfs\ff.c:4989: first defined here
c:/users/warcomeb/ncs/toolchains/v2.1.2/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/10.3.0/../../../../arm-zephyr-eabi/bin/ld.exe: app/libapp.a(file.c.obj): in function `f_rename':
Y:\Projects\X\src\fatfs\ff.c:5074: multiple definition of `f_rename'; app/libapp.a(ff.c.obj):Y:\Projects\X\src\fatfs\ff.c:5074: first defined here
c:/users/warcomeb/ncs/toolchains/v2.1.2/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/10.3.0/../../../../arm-zephyr-eabi/bin/ld.exe: app/libapp.a(file.c.obj): in function `f_mkfs':
Y:\Projects\X\src\fatfs\ff.c:5808: multiple definition of `f_mkfs'; app/libapp.a(ff.c.obj):Y:\Projects\X\src\fatfs\ff.c:5808: first defined here
c:/users/warcomeb/ncs/toolchains/v2.1.2/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/10.3.0/../../../../arm-zephyr-eabi/bin/ld.exe: app/libapp.a(file.c.obj): in function `File_directoryChange':
Y:\Projects\X\src\file.c:177: undefined reference to `fs_opendir'
c:/users/warcomeb/ncs/toolchains/v2.1.2/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/10.3.0/../../../../arm-zephyr-eabi/bin/ld.exe: app/libapp.a(file.c.obj): in function `File_init':
Y:\Projects\X\src\file.c:155: undefined reference to `fs_mount'

I can't delete the reference to zephyr module...

Where is it the problem?

Thanks 

[Simonr]

Hi

It seems like you're mixing the two SDKs we have, as the case you're referring to shows how to add files to projects in the nRF5 SDK. The nRF Connect SDK based on the Zephyr RTOS is another beast entirely, so setting the CONFIG_FILE_SYSTEM and FAT_FILESYSTEM configs to N is expected to result in these errors I believe. To build outside the SDK in NCS/Zephyr I think you need to add a path prefix as described in the West manifest documentation here: https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/zephyr/develop/west/manifest.html#example-3-4-import-into-a-subdirectory Some experimentation might be necessary.

Best regards,

Simon

[warcomeb-am]

Hi Simon,

Thanks for your time. The problem is that I need a custom ffconf.h and I don't want modify the file into sdk (it is a multi-developer project, so the custom configurations must be in the repository and not into the sdk of each developer). For this reason, I follow the trick of the other post that suggests including the FatFS into the src folder of the application.

I want to disable the include of zephyr module fatfs and use only the code that put inside the directory!

Best regards

Marco

[warcomeb-am]

Casper Kronborg Pedersen Sorry. Can you tell me how you solve this issue into your project?

[Casper Kronborg Pedersen]

Hi Marco,

In earlier versions of SEGGER embedded studio (I think before 5.30) and with SDK version 15.3.0 I was able to make it work.

I was not an elegant solution, but I duplicated the ffconf.h file into my source folder and prepended it with the line "#pragma once"

Then my FatFS would use the configuration file in my source folder over the one in the SDK.

However, after updating to newer versions of both the SDK and SEGGER this no longer works for me. I would also suggest trying to move the entire FatFS into your source folder. I have not done this myself yet.

Br. Casper

[warcomeb-am]

Hi Casper,

reading your post I understood that you were able to get the FATFS into your source folder works. ;(

Thanks

Marco

[Casper Kronborg Pedersen]

Hi Marco,

Disregard my previous answer, I was thinking about my previous solution.

The current solution that is working is as you write.

I have copied this folder from the SDK into my project source file:

<SDK location>\nRF5_SDK_17.1.0_ddde560\external\fatfs\src

Then, in the <myProject>.emProject file (xml), I am making sure that I am no longer referencing the SDK copy of the fatfs, by removing any references to it in the "c_user_include_directories"

I am also using "Dynamic Folders" instead of "Virtual Folders" for my source folder in SEGGER Embedded studio. They are folders that are synchronized with my disk. They are denoted like this in my .emProject file:

    <folder Name="Source" exclude="" filter="" path="Source" recurse="Yes" /> 

I used this forum post to find out how to make them:

https://forum.segger.com/index.php/Thread/4750-SOLVED-Feedback-on-SES/

Hope this helps,

Br. Casper

Edit: It is specifically the "src" of the fatfs that I have included directly in my project.

[warcomeb-am]

Thanks for your time.

This solutions doesn't work for me because I am using nRF53 with NCS SDK (2.1.2).

Simonr do you have found any solution for me?