External SPI Flash Memory + File System + NRF 52832

Hi,

I am trying to implement a lightweight file system in my external flash memory (ISSI). After the implementation of file system, I want to store a .bin file and later access the file through c program. I am a beginner in nrf52 board and need some assistance in understanding the implementation method for the above.

  1. I need some direction for implementing file system in nrf52832. I am using the following Software/Hardware tools:
  • nRF52832
  • NRF CONNECT SDK 2.5.1
  • SPI FLash Memory: IS25LP128-JBLE
  • vscode
  • Windows 11 64 bits

       2. I would also like to if I can implement FATFS on the SPI flash memory using the nrf 52832. Is there a link for the lastest version of FAT FS code.

       3. I need some help in understanding if I can use supported files from nrf SDK v 2.5.1 for nrf52832 board? IS there some alteration needed before I upload them to my nrf 52832 board.

Best,

AP

Parents
  • Will this work for nrf 52832 board?

    As I have gone through the document and for external flash : "This type of configuration requires external flash device to be available on DK board. Currently following boards support the configuration: nrf52840dk_nrf52840 by nrf52840dk_nrf52840_qspi configuration." . SInce I have a nrf 52832dk board it does not support this board right?

  • Hi AP,

    You could try to add following configuration options to your prj.conf:
    CONFIG_SPI_NOR_SFDP_DEVICETREE=y
    CONFIG_FLASH_JESD216_API=y

    Additionally, please have a look at spi overlay and spi conf (for nrf52840) as a reference.

    Best regards,
    Dejan

  • Hi dejans,

    I cannot add "CONFIG_SPI_NOR_SFDP_DEVICETREE=y and CONFIG_FLASH_JESD216_API=y" because the external spi_nor flash issi,is25lp128 doesnit have an SFDP table. Therefore I have avoided these parameters.

    I was able to resolve the errors for littlefs in spi_nor flash memory and flash the files to my device.

    This is my build and flash log to my device:1050370044 (nrf52dk) 

     *  Executing task: nRF Connect: Build: littlefs/build (active) 
    
    Building littlefs
    west build --build-dir c:/Users/prasa/Desktop/nrf52dk/littlefs/build c:/Users/prasa/Desktop/nrf52dk/littlefs
    
    [0/1] Re-running CMake...
    Loading Zephyr default modules (Zephyr base (cached)).
    -- Application: C:/Users/prasa/Desktop/nrf52dk/littlefs
    -- CMake version: 3.20.5
    -- Found Python3: C:/Users/prasa/Desktop/nrf52dk/toolchains/c57af46cb7/opt/bin/python.exe (found suitable version "3.8.2", minimum required is "3.8") found components: Interpreter 
    -- Cache files will be written to: C:/Users/prasa/Desktop/nrf52dk/v2.5.0/zephyr/.cache
    -- Zephyr version: 3.4.99 (C:/Users/prasa/Desktop/nrf52dk/v2.5.0/zephyr)
    -- Found west (found suitable version "1.1.0", minimum required is "0.14.0")
    -- Board: nrf52dk_nrf52832
    -- Found host-tools: zephyr 0.16.1 (C:/Users/prasa/Desktop/nrf52dk/toolchains/c57af46cb7/opt/zephyr-sdk)
    -- Found toolchain: zephyr 0.16.1 (C:/Users/prasa/Desktop/nrf52dk/toolchains/c57af46cb7/opt/zephyr-sdk)
    -- Found BOARD.dts: C:/Users/prasa/Desktop/nrf52dk/v2.5.0/zephyr/boards/arm/nrf52dk_nrf52832/nrf52dk_nrf52832.dts
    -- Found devicetree overlay: c:/Users/prasa/Desktop/nrf52dk/littlefs/nrf52dk_nrf52832.overlay
    'label' is marked as deprecated in 'properties:' in C:/Users/prasa/Desktop/nrf52dk/v2.5.0/zephyr/dts/bindings\mtd\jedec,spi-nor.yaml for node /soc/spi@40023000/IS25LP128@0.
    -- Generated zephyr.dts: C:/Users/prasa/Desktop/nrf52dk/littlefs/build/zephyr/zephyr.dts
    -- Generated devicetree_generated.h: C:/Users/prasa/Desktop/nrf52dk/littlefs/build/zephyr/include/generated/devicetree_generated.h
    -- Including generated dts.cmake file: C:/Users/prasa/Desktop/nrf52dk/littlefs/build/zephyr/dts.cmake
    
    warning: Deprecated symbol SETTINGS_FS is enabled.
    
    Parsing C:/Users/prasa/Desktop/nrf52dk/littlefs/Kconfig
    Loaded configuration 'C:/Users/prasa/Desktop/nrf52dk/littlefs/build/zephyr/.config'
    No change to configuration in 'C:/Users/prasa/Desktop/nrf52dk/littlefs/build/zephyr/.config'
    No change to Kconfig header in 'C:/Users/prasa/Desktop/nrf52dk/littlefs/build/zephyr/include/generated/autoconf.h'
    -- Found Python3: C:/Users/prasa/Desktop/nrf52dk/toolchains/c57af46cb7/opt/bin/python.exe (found version "3.8.2") found components: Interpreter 
    
    === child image mcuboot -  begin ===
    loading initial cache file C:/Users/prasa/Desktop/nrf52dk/littlefs/build/mcuboot/child_image_preload.cmake
    Loading Zephyr default modules (Zephyr base (cached)).
    -- Application: C:/Users/prasa/Desktop/nrf52dk/v2.5.0/bootloader/mcuboot/boot/zephyr
    -- CMake version: 3.20.5
    -- Cache files will be written to: C:/Users/prasa/Desktop/nrf52dk/v2.5.0/zephyr/.cache
    -- Zephyr version: 3.4.99 (C:/Users/prasa/Desktop/nrf52dk/v2.5.0/zephyr)
    -- Found west (found suitable version "1.1.0", minimum required is "0.14.0")
    -- Board: nrf52dk_nrf52832
    -- Found host-tools: zephyr 0.16.1 (C:/Users/prasa/Desktop/nrf52dk/toolchains/c57af46cb7/opt/zephyr-sdk)
    -- Found toolchain: zephyr 0.16.1 (C:/Users/prasa/Desktop/nrf52dk/toolchains/c57af46cb7/opt/zephyr-sdk)
    -- Found BOARD.dts: C:/Users/prasa/Desktop/nrf52dk/v2.5.0/zephyr/boards/arm/nrf52dk_nrf52832/nrf52dk_nrf52832.dts
    -- Found devicetree overlay: C:/Users/prasa/Desktop/nrf52dk/v2.5.0/bootloader/mcuboot/boot/zephyr/app.overlay
    -- Generated zephyr.dts: C:/Users/prasa/Desktop/nrf52dk/littlefs/build/mcuboot/zephyr/zephyr.dts
    -- Generated devicetree_generated.h: C:/Users/prasa/Desktop/nrf52dk/littlefs/build/mcuboot/zephyr/include/generated/devicetree_generated.h
    -- Including generated dts.cmake file: C:/Users/prasa/Desktop/nrf52dk/littlefs/build/mcuboot/zephyr/dts.cmake
    Parsing C:/Users/prasa/Desktop/nrf52dk/v2.5.0/bootloader/mcuboot/boot/zephyr/Kconfig
    Loaded configuration 'C:/Users/prasa/Desktop/nrf52dk/littlefs/build/mcuboot/zephyr/.config'
    No change to configuration in 'C:/Users/prasa/Desktop/nrf52dk/littlefs/build/mcuboot/zephyr/.config'
    No change to Kconfig header in 'C:/Users/prasa/Desktop/nrf52dk/littlefs/build/mcuboot/zephyr/include/generated/autoconf.h'
    CMake Warning at C:/Users/prasa/Desktop/nrf52dk/v2.5.0/zephyr/CMakeLists.txt:893 (message):
      No SOURCES given to Zephyr library: drivers__spi
    
      Excluding target from build.
    
    
    MCUBoot bootloader key file: C:/Users/prasa/Desktop/nrf52dk/v2.5.0/bootloader/mcuboot/root-rsa-2048.pem
    -- Configuring done
    -- Generating done
    -- Build files have been written to: C:/Users/prasa/Desktop/nrf52dk/littlefs/build/mcuboot
    === child image mcuboot -  end ===
    
    CMake Warning at C:/Users/prasa/Desktop/nrf52dk/v2.5.0/nrf/modules/mcuboot/CMakeLists.txt:320 (message):
      
    
              ---------------------------------------------------------
              --- WARNING: Using default MCUBoot key, it should not ---
              --- be used for production.                           ---
              ---------------------------------------------------------
              
    
    
    
    CMake Warning at C:/Users/prasa/Desktop/nrf52dk/v2.5.0/nrf/cmake/partition_manager.cmake:79 (message):
      
    
              ---------------------------------------------------------------------
              --- WARNING: Using a bootloader without pm_static.yml.            ---
              --- There are cases where a deployed product can consist of       ---
              --- multiple images, and only a subset of these images can be     ---
              --- upgraded through a firmware update mechanism. In such cases,  ---
              --- the upgradable images must have partitions that are static    ---
              --- and are matching the partition map used by the bootloader     ---
              --- programmed onto the device.                                   ---
              ---------------------------------------------------------------------
              
    
    Call Stack (most recent call first):
      C:/Users/prasa/Desktop/nrf52dk/v2.5.0/zephyr/cmake/modules/kernel.cmake:247 (include)
      C:/Users/prasa/Desktop/nrf52dk/v2.5.0/zephyr/cmake/modules/zephyr_default.cmake:138 (include)
      C:/Users/prasa/Desktop/nrf52dk/v2.5.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:66 (include)
      C:/Users/prasa/Desktop/nrf52dk/v2.5.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:97 (include_boilerplate)
      CMakeLists.txt:8 (find_package)
    
    
    -- Configuring done
    -- Generating done
    -- Build files have been written to: C:/Users/prasa/Desktop/nrf52dk/littlefs/build
    [0/149] Performing build step for 'mcuboot_subimage'
    [1/29] Generating misc/generated/syscalls.json, misc/generated/struct_tags.json
    [2/29] Building C object zephyr/CMakeFiles/zephyr.dir/subsys/storage/flash_map/flash_map_layout.c.obj
    [3/29] Building C object zephyr/CMakeFiles/zephyr.dir/subsys/storage/flash_map/flash_map.c.obj
    [4/29] Building C object zephyr/CMakeFiles/zephyr.dir/C_/Users/prasa/Desktop/nrf52dk/v2.5.0/nrf/subsys/partition_manager/flash_map_partition_manager.c.obj
    [5/29] Generating linker_zephyr_pre0.cmd
    [6/29] Building C object zephyr/lib/libc/common/CMakeFiles/lib__libc__common.dir/source/stdlib/malloc.c.obj
    [7/29] Building C object CMakeFiles/app.dir/main.c.obj
    [8/29] Building C object CMakeFiles/app.dir/flash_map_extended.c.obj
    [9/29] Building C object CMakeFiles/app.dir/C_/Users/prasa/Desktop/nrf52dk/v2.5.0/bootloader/mcuboot/boot/bootutil/src/image_validate.c.obj
    [10/29] Building C object CMakeFiles/app.dir/C_/Users/prasa/Desktop/nrf52dk/v2.5.0/bootloader/mcuboot/boot/bootutil/src/tlv.c.obj
    [11/29] Linking C static library zephyr\libzephyr.a
    [12/29] Linking C static library zephyr\lib\libc\common\liblib__libc__common.a
    [13/29] Building C object CMakeFiles/app.dir/C_/Users/prasa/Desktop/nrf52dk/v2.5.0/bootloader/mcuboot/boot/bootutil/src/image_rsa.c.obj
    [14/29] Building C object CMakeFiles/app.dir/C_/Users/prasa/Desktop/nrf52dk/v2.5.0/bootloader/mcuboot/boot/bootutil/src/bootutil_misc.c.obj
    [15/29] Building C object CMakeFiles/app.dir/C_/Users/prasa/Desktop/nrf52dk/v2.5.0/bootloader/mcuboot/boot/bootutil/src/swap_misc.c.obj
    [16/29] Building C object CMakeFiles/app.dir/C_/Users/prasa/Desktop/nrf52dk/v2.5.0/bootloader/mcuboot/boot/bootutil/src/loader.c.obj
    [17/29] Building C object CMakeFiles/app.dir/C_/Users/prasa/Desktop/nrf52dk/v2.5.0/bootloader/mcuboot/boot/bootutil/src/swap_scratch.c.obj
    [18/29] Building C object CMakeFiles/app.dir/C_/Users/prasa/Desktop/nrf52dk/v2.5.0/bootloader/mcuboot/boot/bootutil/src/swap_move.c.obj
    [19/29] Building C object CMakeFiles/app.dir/nrf_cleanup.c.obj
    [20/29] Linking C static library app\libapp.a
    [21/29] Building C object zephyr/soc/soc/arm/common/cortex_m/CMakeFiles/soc__arm__common__cortex_m.dir/arm_mpu_regions.c.obj
    [22/29] Linking C static library zephyr\soc\soc\arm\common\cortex_m\libsoc__arm__common__cortex_m.a
    [23/29] Building C object modules/mcuboot/boot/bootutil/zephyr/CMakeFiles/mcuboot_util.dir/C_/Users/prasa/Desktop/nrf52dk/v2.5.0/bootloader/mcuboot/boot/bootutil/src/bootutil_public.c.obj
    [24/29] Linking C static library modules\mcuboot\boot\bootutil\zephyr\libmcuboot_util.a
    [25/29] Linking C executable zephyr\zephyr_pre0.elf
    [26/29] Generating linker.cmd
    [27/29] Generating isr_tables.c, isrList.bin
    [28/29] Building C object zephyr/CMakeFiles/zephyr_final.dir/isr_tables.c.obj
    [29/29] Linking C executable zephyr\zephyr.elf
    Memory region         Used Size  Region Size  %age Used
               FLASH:       32120 B        48 KB     65.35%
                 RAM:       23744 B        64 KB     36.23%
            IDT_LIST:          0 GB         2 KB      0.00%
    [85/149] Building C object zephyr/drivers/console/CMakeFiles/drivers__console.dir/uart_console.c.obj
    [87/147] Linking C static library zephyr\drivers\console\libdrivers__console.a
    [88/147] Building C object zephyr/drivers/flash/CMakeFiles/drivers__flash.dir/soc_flash_nrf.c.obj
    [89/147] Building C object zephyr/drivers/flash/CMakeFiles/drivers__flash.dir/spi_nor.c.obj
    [90/147] Building C object zephyr/drivers/flash/CMakeFiles/drivers__flash.dir/flash_page_layout.c.obj
    [91/147] Building C object zephyr/drivers/flash/CMakeFiles/drivers__flash.dir/jesd216.c.obj
    [92/147] Linking C static library zephyr\drivers\flash\libdrivers__flash.a
    [93/147] Building C object zephyr/drivers/pinctrl/CMakeFiles/drivers__pinctrl.dir/pinctrl_nrf.c.obj
    [94/147] Building C object zephyr/drivers/pinctrl/CMakeFiles/drivers__pinctrl.dir/common.c.obj
    [95/147] Linking C static library zephyr\drivers\pinctrl\libdrivers__pinctrl.a
    [96/147] Building C object zephyr/drivers/gpio/CMakeFiles/drivers__gpio.dir/gpio_nrfx.c.obj
    [97/147] Linking C static library zephyr\drivers\gpio\libdrivers__gpio.a
    [98/147] Building C object zephyr/drivers/serial/CMakeFiles/drivers__serial.dir/uart_nrfx_uarte.c.obj
    [99/147] Building C object zephyr/drivers/spi/CMakeFiles/drivers__spi.dir/spi_nrfx_common.c.obj
    [100/147] Linking C static library zephyr\drivers\serial\libdrivers__serial.a
    [101/147] Building C object zephyr/drivers/timer/CMakeFiles/drivers__timer.dir/sys_clock_init.c.obj
    [102/147] Building C object zephyr/drivers/spi/CMakeFiles/drivers__spi.dir/spi_nrfx_spi.c.obj
    [103/147] Building C object zephyr/drivers/timer/CMakeFiles/drivers__timer.dir/nrf_rtc_timer.c.obj
    [104/147] Linking C static library zephyr\drivers\spi\libdrivers__spi.a
    [105/147] Building C object modules/segger/CMakeFiles/modules__segger.dir/SEGGER_RTT_zephyr.c.obj
    [106/147] Linking C static library zephyr\drivers\timer\libdrivers__timer.a
    [107/147] Linking C static library modules\segger\libmodules__segger.a
    [108/147] Building C object zephyr/kernel/CMakeFiles/kernel.dir/banner.c.obj
    [109/147] Building C object zephyr/kernel/CMakeFiles/kernel.dir/main_weak.c.obj
    [110/147] Building C object zephyr/kernel/CMakeFiles/kernel.dir/busy_wait.c.obj
    [111/147] Building C object zephyr/kernel/CMakeFiles/kernel.dir/init.c.obj
    [112/147] Building C object zephyr/kernel/CMakeFiles/kernel.dir/mem_slab.c.obj
    [113/147] Building C object zephyr/kernel/CMakeFiles/kernel.dir/errno.c.obj
    [114/147] Building C object zephyr/kernel/CMakeFiles/kernel.dir/device.c.obj
    [115/147] Building C object zephyr/kernel/CMakeFiles/kernel.dir/fatal.c.obj
    [116/147] Building C object zephyr/kernel/CMakeFiles/kernel.dir/kheap.c.obj
    [117/147] Building C object zephyr/kernel/CMakeFiles/kernel.dir/idle.c.obj
    [118/147] Building C object zephyr/kernel/CMakeFiles/kernel.dir/msg_q.c.obj
    [119/147] Building C object zephyr/kernel/CMakeFiles/kernel.dir/thread.c.obj
    [120/147] Building C object zephyr/kernel/CMakeFiles/kernel.dir/mailbox.c.obj
    [121/147] Building C object zephyr/kernel/CMakeFiles/kernel.dir/mutex.c.obj
    [122/147] Building C object zephyr/kernel/CMakeFiles/kernel.dir/queue.c.obj
    [123/147] Building C object zephyr/kernel/CMakeFiles/kernel.dir/system_work_q.c.obj
    [124/147] Building C object zephyr/kernel/CMakeFiles/kernel.dir/work.c.obj
    [125/147] Building C object zephyr/kernel/CMakeFiles/kernel.dir/sem.c.obj
    [126/147] Building C object zephyr/kernel/CMakeFiles/kernel.dir/sched.c.obj
    [127/147] Building C object zephyr/kernel/CMakeFiles/kernel.dir/stack.c.obj
    [128/147] Building C object zephyr/kernel/CMakeFiles/kernel.dir/condvar.c.obj
    [129/147] Building C object zephyr/kernel/CMakeFiles/kernel.dir/xip.c.obj
    [130/147] Building C object zephyr/kernel/CMakeFiles/kernel.dir/mempool.c.obj
    [131/147] Building C object zephyr/kernel/CMakeFiles/kernel.dir/timer.c.obj
    [132/147] Building C object zephyr/kernel/CMakeFiles/kernel.dir/timeout.c.obj
    [133/147] Building C object zephyr/kernel/CMakeFiles/kernel.dir/dynamic_disabled.c.obj
    [134/147] Linking C static library zephyr\kernel\libkernel.a
    [135/147] Linking C executable zephyr\zephyr_pre0.elf
    [136/147] Generating linker.cmd
    [137/147] Generating isr_tables.c, isrList.bin
    [138/147] Building C object zephyr/CMakeFiles/zephyr_final.dir/isr_tables.c.obj
    [139/147] Linking C executable zephyr\zephyr.elf
    Memory region         Used Size  Region Size  %age Used
               FLASH:       62132 B     237056 B     26.21%
                 RAM:       11372 B        64 KB     17.35%
            IDT_LIST:          0 GB         2 KB      0.00%
    [140/147] Generating zephyr/mcuboot_primary.hex
    [141/147] Generating zephyr/mcuboot_primary_app.hex
    [142/147] Generating ../../zephyr/app_signed.hex
    image.py: sign the payload
    [143/147] Generating ../../zephyr/app_update.bin
    image.py: sign the payload
    [144/147] Generating ../../zephyr/dfu_application.zip
    [145/147] Generating ../../zephyr/app_test_update.hex
    image.py: sign the payload
    [146/147] Generating ../../zephyr/app_moved_test_update.hex
    [147/147] Generating zephyr/merged.hex
     *  Terminal will be reused by tasks, press any key to close it. 
    
     *  Executing task: nRF Connect: Flash: littlefs/build (active) 
    
    Flashing build to 1050370044
    west flash -d c:\Users\prasa\Desktop\nrf52dk\littlefs\build --skip-rebuild --dev-id 1050370044 --erase
    
    -- west flash: using runner nrfjprog
    -- runners.nrfjprog: mass erase requested
    -- runners.nrfjprog: Flashing file: c:\Users\prasa\Desktop\nrf52dk\littlefs\build\zephyr\merged.hex
    [ #################### ]   0.150s | Erase file - Done erasing                                                          
    [ #################### ]   1.724s | Program file - Done programming                                                    
    [ #################### ]   0.639s | Verify file - Done verifying                                                       
    Enabling pin reset.
    Applying pin reset.
    -- runners.nrfjprog: Board with serial number 1050370044 flashed successfully.
     *  Terminal will be reused by tasks, press any key to close it. 


    The external flash memory is not properly connected with my nrf52dk device as I noticed some warning in the above flash log and device log.

    vCOM0 (COM4) log:

    *** Booting nRF Connect SDK v2.5.0 ***
    I: Starting bootloader
    I: Primary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
    I: Secondary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
    I: Boot source: none
    I: Image index: 0, Swap type: none
    I: Bootloader chainload address offset: 0xc000
    �E: Device id 00 00 00 does not match config 9d 60 18
    I: littlefs partition at /lfs1
    I: LittleFS version 2.5, disk version 2.0
    E: can't open flash area 0
    E: fs mount error (-19)
    E: Automount /lfs1 failed: -19
    *** Booting nRF Connect SDK v2.5.0 ***
    Sample program to r/w files on littlefs
    E: FAIL: unable to find flash area 0: -19


    The flash memory was not accessed during this flash. How do I correct this error and connect my external flash to nrf52dk? (the pins are connect to SCK=P0.22,SO=P0.23,SI=P0.24,CE=P0.25)

    MY OVERLAY:

    /delete-node/ &storage_partition;
    
    
    / {
        chosen {
            nordic,pm-ext-flash = &IS25LP128;
        };
    };
    
    
    &spi2 {
        compatible = "nordic,nrf-spi";
    
        status = "okay";
    
        pinctrl-0 = <&spi2_default>;
    
        pinctrl-1 = <&spi2_sleep>;
    
        pinctrl-names = "default", "sleep";
    
        cs-gpios = <&gpio0 25 (GPIO_PULL_UP | GPIO_ACTIVE_LOW)>;
        
        IS25LP128: IS25LP128@0 {
            compatible = "jedec,spi-nor";
            status = "okay";
            label = "25LP128";
            reg = <0>;
            spi-max-frequency = <8000000>; /* Adjust based on your flash specifications */
            size = <0x8000000>; /* Adjust based on your flash size */
            has-dpd;
            t-enter-dpd = <3000>;
            t-exit-dpd = <30000>;
            jedec-id = [ 9D 60 18 ]; /* Adjust based on your flash JEDEC ID */
            //page_size = <2048>;
            //block_size = <131072>;
    
            };
        };
    
    &pinctrl {
        spi2_default: spi2_default {
            group1 {
                psels = <NRF_PSEL(SPIM_SCK, 0, 22)>, /* gpio 0 pin P0.25 */
                        <NRF_PSEL(SPIM_MISO, 0, 24)>, /* gpio 0 pin P0.24 */
                        <NRF_PSEL(SPIM_MOSI, 0, 23)>; /* gpio 0 pin P0.23 */
            };
        };
    
        spi2_sleep: spi2_sleep {
            group1 {
                psels = <NRF_PSEL(SPIM_SCK, 0, 22)>, /* gpio 0 pin P0.25 */
                        <NRF_PSEL(SPIM_MISO, 0, 24)>, /* gpio 0 pin P0.24 */
                        <NRF_PSEL(SPIM_MOSI, 0, 23)>; /* gpio 0 pin P0.23 */
            };
        };
    };
    
    
    &IS25LP128 {
        partitions {
    		compatible = "fixed-partitions";
    		#address-cells = <1>;
    		#size-cells = <1>;
    
    		lfs1_part: partition@0 {
    			label = "storage";
    			reg = <0x00000000 0x00800000>;
    		};
    	};
    };
    / {
    	fstab {
    		compatible = "zephyr,fstab";
    		lfs1: lfs1 {
    			compatible = "zephyr,fstab,littlefs";
    			mount-point = "/lfs1";
    			partition = <&lfs1_part>;
    			automount;
    			read-size = <16>;
    			prog-size = <16>;
    			cache-size = <64>;
    			lookahead-size = <32>;
    			block-cycles = <512>;
    		};
    	};
    };
    /delete-node/ &{/pin-controller/pwm0_default/group1/};
    /delete-node/ &{/pin-controller/pwm0_sleep/group1/};
    


    Best regards,

    Aditi Prasad

  • Hi,

    Could you connect your pins SCK=P0.22, SO=P0.23, SI=P0.24 and CE=P0.25 to the logic analyzer and provide logic trace?

    Best regards,
    Dejan

  • Hi,

    At the moment I do not have access to a logic analyzer but I will try to aquire one. Meanwhile I was checking if my flash memory connection directly to the microcontroller could cause some error?

    As there is no resistors attached to the spi pins but as far I have seen in the flash memory a voltage range of 1.7v to 3.6v of the microcontroller should be enough to function the spi pins of the flash (https://www.mouser.de/datasheet/2/198/IS25LP032-064-128-463542.pdf). 

    Should I connect the HOLD and RESET pins to P0.11, P0.12 resp or conenct them to VDD here.

    This is the connection I have right now.
       

    Best regards,

    Aditi Prasad

  • Hi,

    There should be no need for additional resistors. It should also be fine to connect flash directly to the SoC. Regarding the pins, you could connect them directly to VDD.

    Best regards,
    Dejan

Reply Children
No Data
Related