USB mass storage for the NRF7002DK development board using on board chip

RE: USB mass storage for the NRF7002DK development board using on board chip

Elfving — Fri, 19 Sep 2025 11:23:32 GMT

[quote user="Tudor B."] I'll get back to you with the results in the next few days.[/quote]

Any update on this from your side?

[quote user="Tudor B."]

This brings me back to my request: could you get Alex's sample that's attached above, and make it work for _ns; having these three CONFIG_ options enabled and then send it my way? :) :

[/quote]

Here is something that builds. Sorry about the delay.

devzone.nordicsemi.com/.../mass_5F00_ns.7z

Regards,

Elfving

RE: USB mass storage for the NRF7002DK development board using on board chip

Tudor B. — Tue, 02 Sep 2025 07:44:33 GMT

Hello Elfving.

The sample Alex provided was never meant to work with sysbuild. It doesn't work with sysbuild for me either. Alex tried getting a build working that also has TFM and sysbuild and yesterday provided a sample that should work. I'll get back to you with the results in the next few days.

[quote userid="103347" url="~/f/nordic-q-a/122517/usb-mass-storage-for-the-nrf7002dk-development-board-using-on-board-chip/547205"]Did you also decide to use FATFS?[/quote]

Yes, to hasten things we decided to move forward with FATFS for now and in the near future we'll try to switch back to LittleFS.

RE: USB mass storage for the NRF7002DK development board using on board chip

Elfving — Fri, 29 Aug 2025 13:37:29 GMT

Hi,

I realized that you decided/needed to use sysbuild for this? Like I mentioned earlier I think the sample wasn't made with sysbuild in mind, though I agree that you might need it for TFM. Did the sample Alex made for you there work with sysbuild for you? It doesn't for me.

Did you also decide to use FATFS?

RE: USB mass storage for the NRF7002DK development board using on board chip

Tudor B. — Fri, 22 Aug 2025 15:52:00 GMT

Indeed, that is the case. Yet we've faced no issues having MicroPython in the project until now.

RE: USB mass storage for the NRF7002DK development board using on board chip

Elfving — Fri, 22 Aug 2025 13:28:40 GMT

Sorry to keep you hanging here, though I tried to do it myself but I am running into some issues here. I'll have to continue this next week.

Btw, what is with the micropython path? Are you running micropython on the chip as well?

Regards,

Elfving

RE: USB mass storage for the NRF7002DK development board using on board chip

Tudor B. — Thu, 14 Aug 2025 17:51:59 GMT

Hey Elfving.

I tried what you suggested and it didn't work.

At first I got these build errors:

----- Installing platform NS -----
[25/287] Building C object zephyr/drivers/disk/CMakeFiles/drivers__disk.dir/flashdisk.c.obj
FAILED: [code=1] zephyr/drivers/disk/CMakeFiles/drivers__disk.dir/flashdisk.c.obj
ccache /Users/tudor/zephyr-sdk-0.17.0/arm-zephyr-eabi/bin/arm-zephyr-eabi-gcc -DKERNEL -DK_HEAP_MEM_POOL_SIZE=65536 -DMBEDTLS_CONFIG_FILE=\"nrf-config.h\" -DMBEDTLS_PSA_CRYPTO_CONFIG_FILE=\"nrf-psa-crypto-config.h\" -DNRF5340_XXAA_APPLICATION -DNRF_SKIP_FICR_NS_COPY_TO_RAM -DNRF_TRUSTZONE_NONSECURE -DPICOLIBC_DOUBLE_PRINTF_SCANF -DUSE_PARTITION_MANAGER=1 -D__LINUX_ERRNO_EXTENSIONS__ -D__PROGRAM_START -D__ZEPHYR_SUPERVISOR__ -D__ZEPHYR__=1 -I/Users/tudor/Documents/GitHub/micropython_nRF/ports/zephyr/build/zephyr/zephyr/include/generated/zephyr -I/opt/nordic/ncs/v3.0.0/zephyr/include -I/Users/tudor/Documents/GitHub/micropython_nRF/ports/zephyr/build/zephyr/zephyr/include/generated -I/opt/nordic/ncs/v3.0.0/zephyr/soc/nordic -I/opt/nordic/ncs/v3.0.0/zephyr/include/zephyr/posix -I/opt/nordic/ncs/v3.0.0/zephyr/soc/nordic/nrf53/. -I/opt/nordic/ncs/v3.0.0/zephyr/soc/nordic/common/. -I/opt/nordic/ncs/v3.0.0/zephyr/subsys/usb/device -I/opt/nordic/ncs/v3.0.0/zephyr/drivers/usb/common/nrf_usbd_common/. -I/opt/nordic/ncs/v3.0.0/nrf/include -I/Users/tudor/Documents/GitHub/micropython_nRF/ports/zephyr/build/zephyr/tfm/api_ns/interface/include -I/opt/nordic/ncs/v3.0.0/nrf/modules/trusted-firmware-m/. -I/opt/nordic/ncs/v3.0.0/nrf/include/tfm -I/opt/nordic/ncs/v3.0.0/nrf/tests/include -I/opt/nordic/ncs/v3.0.0/modules/hal/cmsis/CMSIS/Core/Include -I/opt/nordic/ncs/v3.0.0/zephyr/modules/cmsis/. -I/opt/nordic/ncs/v3.0.0/nrf/modules/hal_nordic/. -I/opt/nordic/ncs/v3.0.0/modules/hal/nordic/nrfx -I/opt/nordic/ncs/v3.0.0/modules/hal/nordic/nrfx/drivers/include -I/opt/nordic/ncs/v3.0.0/modules/hal/nordic/nrfx/mdk -I/opt/nordic/ncs/v3.0.0/zephyr/modules/hal_nordic/nrfx/. -I/Users/tudor/Documents/GitHub/micropython_nRF/ports/zephyr/build/zephyr/certs -I/Users/tudor/Documents/GitHub/micropython_nRF/ports/zephyr/build/zephyr/generated/interface_nrf_security_psa -I/opt/nordic/ncs/v3.0.0/nrf/subsys/nrf_security/include -I/opt/nordic/ncs/v3.0.0/modules/crypto/oberon-psa-crypto/include -I/opt/nordic/ncs/v3.0.0/nrf/subsys/nrf_security/src/utils -I/opt/nordic/ncs/v3.0.0/modules/crypto/oberon-psa-crypto/library -I/opt/nordic/ncs/v3.0.0/modules/crypto/mbedtls/library -I/opt/nordic/ncs/v3.0.0/modules/crypto/mbedtls/include -I/opt/nordic/ncs/v3.0.0/modules/crypto/mbedtls/include/library -I/opt/nordic/ncs/v3.0.0/nrfxlib/crypto/nrf_oberon/include -I/opt/nordic/ncs/v3.0.0/nrfxlib/crypto/nrf_oberon/include/mbedtls -isystem /opt/nordic/ncs/v3.0.0/zephyr/lib/libc/common/include -Wshadow -fno-strict-aliasing -Os -flto=auto -imacros /Users/tudor/Documents/GitHub/micropython_nRF/ports/zephyr/build/zephyr/zephyr/include/generated/zephyr/autoconf.h -fno-common -g -gdwarf-4 -fdiagnostics-color=always -mcpu=cortex-m33 -mthumb -mabi=aapcs -mfpu=fpv5-sp-d16 -mfloat-abi=hard -mfp16-format=ieee -mtp=soft --sysroot=/Users/tudor/zephyr-sdk-0.17.0/arm-zephyr-eabi/arm-zephyr-eabi -imacros /opt/nordic/ncs/v3.0.0/zephyr/include/zephyr/toolchain/zephyr_stdint.h -Wall -Wformat -Wformat-security -Wno-format-zero-length -Wdouble-promotion -Wno-pointer-sign -Wpointer-arith -Wexpansion-to-defined -Wno-unused-but-set-variable -Werror=implicit-int -fno-pic -fno-pie -fno-asynchronous-unwind-tables -ftls-model=local-exec -fno-reorder-functions --param=min-pagesize=0 -fno-defer-pop -fmacro-prefix-map=/Users/tudor/Documents/GitHub/micropython_nRF/ports/zephyr=CMAKE_SOURCE_DIR -fmacro-prefix-map=/opt/nordic/ncs/v3.0.0/zephyr=ZEPHYR_BASE -fmacro-prefix-map=/opt/nordic/ncs/v3.0.0=WEST_TOPDIR -ffunction-sections -fdata-sections -specs=picolibc.specs -D_POSIX_THREADS -std=c99 -MD -MT zephyr/drivers/disk/CMakeFiles/drivers__disk.dir/flashdisk.c.obj -MF zephyr/drivers/disk/CMakeFiles/drivers__disk.dir/flashdisk.c.obj.d -o zephyr/drivers/disk/CMakeFiles/drivers__disk.dir/flashdisk.c.obj -c /opt/nordic/ncs/v3.0.0/zephyr/drivers/disk/flashdisk.c
/opt/nordic/ncs/v3.0.0/zephyr/drivers/disk/flashdisk.c:533:1: error: return type defaults to 'int' [-Werror=implicit-int]
  533 | PM_FOREACH_AFFILIATED_TO_disk(DEFINE_FLASHDISKS_CACHE)
      | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/opt/nordic/ncs/v3.0.0/zephyr/drivers/disk/flashdisk.c: In function 'PM_FOREACH_AFFILIATED_TO_disk':
/opt/nordic/ncs/v3.0.0/zephyr/drivers/disk/flashdisk.c:572:30: error: storage class specified for parameter 'flash_disks'
  572 | static struct flashdisk_data flash_disks[] = {
      |                              ^~~~~~~~~~~
/opt/nordic/ncs/v3.0.0/zephyr/drivers/disk/flashdisk.c:572:15: error: parameter 'flash_disks' is initialized
  572 | static struct flashdisk_data flash_disks[] = {
      |               ^~~~~~~~~~~~~~
/opt/nordic/ncs/v3.0.0/zephyr/drivers/disk/flashdisk.c:573:39: error: 'DEFINE_FLASHDISKS_DEVICE' undeclared (first use in this function)
  573 |         PM_FOREACH_AFFILIATED_TO_disk(DEFINE_FLASHDISKS_DEVICE)
      |                                       ^~~~~~~~~~~~~~~~~~~~~~~~
/opt/nordic/ncs/v3.0.0/zephyr/drivers/disk/flashdisk.c:573:39: note: each undeclared identifier is reported only once for each function it appears in
/opt/nordic/ncs/v3.0.0/zephyr/drivers/disk/flashdisk.c:582:1: error: expected declaration specifiers before 'PM_FOREACH_AFFILIATED_TO_disk'
  582 | PM_FOREACH_AFFILIATED_TO_disk(VERIFY_CACHE_SIZE_IS_NOT_ZERO_IF_NOT_READ_ONLY)
      | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from /opt/nordic/ncs/v3.0.0/zephyr/include/zephyr/toolchain/gcc.h:98,
                 from /opt/nordic/ncs/v3.0.0/zephyr/include/zephyr/toolchain.h:50,
                 from /opt/nordic/ncs/v3.0.0/zephyr/include/zephyr/sys/__assert.h:11,
                 from /opt/nordic/ncs/v3.0.0/zephyr/drivers/disk/flashdisk.c:10:
/opt/nordic/ncs/v3.0.0/zephyr/include/zephyr/init.h:141:44: error: storage class specified for parameter '__init_disk_flash_init'
  141 | #define Z_INIT_ENTRY_NAME(init_id) _CONCAT(__init_, init_id)
      |                                            ^~~~~~~
/opt/nordic/ncs/v3.0.0/zephyr/include/zephyr/toolchain/common.h:137:26: note: in definition of macro '_DO_CONCAT'
  137 | #define _DO_CONCAT(x, y) x ## y
      |                          ^
/opt/nordic/ncs/v3.0.0/zephyr/include/zephyr/init.h:141:36: note: in expansion of macro '_CONCAT'
  141 | #define Z_INIT_ENTRY_NAME(init_id) _CONCAT(__init_, init_id)
      |                                    ^~~~~~~
/opt/nordic/ncs/v3.0.0/zephyr/include/zephyr/init.h:241:17: note: in expansion of macro 'Z_INIT_ENTRY_NAME'
  241 |                 Z_INIT_ENTRY_NAME(name) = {.init_fn = {.sys = (init_fn_)},                \
      |                 ^~~~~~~~~~~~~~~~~
/opt/nordic/ncs/v3.0.0/zephyr/include/zephyr/init.h:223:9: note: in expansion of macro 'SYS_INIT_NAMED'
  223 |         SYS_INIT_NAMED(init_fn, init_fn, level, prio)
      |         ^~~~~~~~~~~~~~
/opt/nordic/ncs/v3.0.0/zephyr/drivers/disk/flashdisk.c:612:1: note: in expansion of macro 'SYS_INIT'
  612 | SYS_INIT(disk_flash_init, POST_KERNEL, CONFIG_KERNEL_INIT_PRIORITY_DEFAULT);
      | ^~~~~~~~
/opt/nordic/ncs/v3.0.0/zephyr/include/zephyr/init.h:239:42: error: parameter '__init_disk_flash_init' is initialized
  239 |         static const Z_DECL_ALIGN(struct init_entry)                                      \
      |                                          ^~~~~~~~~~
/opt/nordic/ncs/v3.0.0/zephyr/include/zephyr/toolchain/common.h:195:55: note: in definition of macro 'Z_DECL_ALIGN'
  195 | #define Z_DECL_ALIGN(type) __aligned(__alignof(type)) type
      |                                                       ^~~~
/opt/nordic/ncs/v3.0.0/zephyr/include/zephyr/init.h:223:9: note: in expansion of macro 'SYS_INIT_NAMED'
  223 |         SYS_INIT_NAMED(init_fn, init_fn, level, prio)
      |         ^~~~~~~~~~~~~~
/opt/nordic/ncs/v3.0.0/zephyr/drivers/disk/flashdisk.c:612:1: note: in expansion of macro 'SYS_INIT'
  612 | SYS_INIT(disk_flash_init, POST_KERNEL, CONFIG_KERNEL_INIT_PRIORITY_DEFAULT);
      | ^~~~~~~~
/opt/nordic/ncs/v3.0.0/zephyr/include/zephyr/init.h:141:44: error: section attribute not allowed for '__init_disk_flash_init'
  141 | #define Z_INIT_ENTRY_NAME(init_id) _CONCAT(__init_, init_id)
      |                                            ^~~~~~~
/opt/nordic/ncs/v3.0.0/zephyr/include/zephyr/toolchain/common.h:137:26: note: in definition of macro '_DO_CONCAT'
  137 | #define _DO_CONCAT(x, y) x ## y
      |                          ^
/opt/nordic/ncs/v3.0.0/zephyr/include/zephyr/init.h:141:36: note: in expansion of macro '_CONCAT'
  141 | #define Z_INIT_ENTRY_NAME(init_id) _CONCAT(__init_, init_id)
      |                                    ^~~~~~~
/opt/nordic/ncs/v3.0.0/zephyr/include/zephyr/init.h:241:17: note: in expansion of macro 'Z_INIT_ENTRY_NAME'
  241 |                 Z_INIT_ENTRY_NAME(name) = {.init_fn = {.sys = (init_fn_)},                \
      |                 ^~~~~~~~~~~~~~~~~
/opt/nordic/ncs/v3.0.0/zephyr/include/zephyr/init.h:223:9: note: in expansion of macro 'SYS_INIT_NAMED'
  223 |         SYS_INIT_NAMED(init_fn, init_fn, level, prio)
      |         ^~~~~~~~~~~~~~
/opt/nordic/ncs/v3.0.0/zephyr/drivers/disk/flashdisk.c:612:1: note: in expansion of macro 'SYS_INIT'
  612 | SYS_INIT(disk_flash_init, POST_KERNEL, CONFIG_KERNEL_INIT_PRIORITY_DEFAULT);
      | ^~~~~~~~
/opt/nordic/ncs/v3.0.0/zephyr/include/zephyr/init.h:239:42: warning: 'used' attribute ignored [-Wattributes]
  239 |         static const Z_DECL_ALIGN(struct init_entry)                                      \
      |                                          ^~~~~~~~~~
/opt/nordic/ncs/v3.0.0/zephyr/include/zephyr/toolchain/common.h:195:55: note: in definition of macro 'Z_DECL_ALIGN'
  195 | #define Z_DECL_ALIGN(type) __aligned(__alignof(type)) type
      |                                                       ^~~~
/opt/nordic/ncs/v3.0.0/zephyr/include/zephyr/init.h:223:9: note: in expansion of macro 'SYS_INIT_NAMED'
  223 |         SYS_INIT_NAMED(init_fn, init_fn, level, prio)
      |         ^~~~~~~~~~~~~~
/opt/nordic/ncs/v3.0.0/zephyr/drivers/disk/flashdisk.c:612:1: note: in expansion of macro 'SYS_INIT'
  612 | SYS_INIT(disk_flash_init, POST_KERNEL, CONFIG_KERNEL_INIT_PRIORITY_DEFAULT);
      | ^~~~~~~~
/opt/nordic/ncs/v3.0.0/zephyr/include/zephyr/init.h:141:44: error: alignment may not be specified for '__init_disk_flash_init'
  141 | #define Z_INIT_ENTRY_NAME(init_id) _CONCAT(__init_, init_id)
      |                                            ^~~~~~~
/opt/nordic/ncs/v3.0.0/zephyr/include/zephyr/toolchain/common.h:137:26: note: in definition of macro '_DO_CONCAT'
  137 | #define _DO_CONCAT(x, y) x ## y
      |                          ^
/opt/nordic/ncs/v3.0.0/zephyr/include/zephyr/init.h:141:36: note: in expansion of macro '_CONCAT'
  141 | #define Z_INIT_ENTRY_NAME(init_id) _CONCAT(__init_, init_id)
      |                                    ^~~~~~~
/opt/nordic/ncs/v3.0.0/zephyr/include/zephyr/init.h:241:17: note: in expansion of macro 'Z_INIT_ENTRY_NAME'
  241 |                 Z_INIT_ENTRY_NAME(name) = {.init_fn = {.sys = (init_fn_)},                \
      |                 ^~~~~~~~~~~~~~~~~
/opt/nordic/ncs/v3.0.0/zephyr/include/zephyr/init.h:223:9: note: in expansion of macro 'SYS_INIT_NAMED'
  223 |         SYS_INIT_NAMED(init_fn, init_fn, level, prio)
      |         ^~~~~~~~~~~~~~
/opt/nordic/ncs/v3.0.0/zephyr/drivers/disk/flashdisk.c:612:1: note: in expansion of macro 'SYS_INIT'
  612 | SYS_INIT(disk_flash_init, POST_KERNEL, CONFIG_KERNEL_INIT_PRIORITY_DEFAULT);
      | ^~~~~~~~
In file included from /opt/nordic/ncs/v3.0.0/zephyr/include/zephyr/device.h:13,
                 from /opt/nordic/ncs/v3.0.0/zephyr/include/zephyr/sw_isr_table.h:18,
                 from /opt/nordic/ncs/v3.0.0/zephyr/include/zephyr/arch/arm/irq.h:19,
                 from /opt/nordic/ncs/v3.0.0/zephyr/include/zephyr/arch/arm/arch.h:24,
                 from /opt/nordic/ncs/v3.0.0/zephyr/include/zephyr/arch/cpu.h:19,
                 from /opt/nordic/ncs/v3.0.0/zephyr/include/zephyr/kernel_includes.h:36,
                 from /opt/nordic/ncs/v3.0.0/zephyr/include/zephyr/kernel.h:17,
                 from /opt/nordic/ncs/v3.0.0/zephyr/include/zephyr/drivers/disk.h:30,
                 from /opt/nordic/ncs/v3.0.0/zephyr/drivers/disk/flashdisk.c:12:
/opt/nordic/ncs/v3.0.0/zephyr/drivers/disk/flashdisk.c:612:10: error: 'disk_flash_init' undeclared (first use in this function)
  612 | SYS_INIT(disk_flash_init, POST_KERNEL, CONFIG_KERNEL_INIT_PRIORITY_DEFAULT);
      |          ^~~~~~~~~~~~~~~
/opt/nordic/ncs/v3.0.0/zephyr/include/zephyr/init.h:241:64: note: in definition of macro 'SYS_INIT_NAMED'
  241 |                 Z_INIT_ENTRY_NAME(name) = {.init_fn = {.sys = (init_fn_)},                \
      |                                                                ^~~~~~~~
/opt/nordic/ncs/v3.0.0/zephyr/drivers/disk/flashdisk.c:612:1: note: in expansion of macro 'SYS_INIT'
  612 | SYS_INIT(disk_flash_init, POST_KERNEL, CONFIG_KERNEL_INIT_PRIORITY_DEFAULT);
      | ^~~~~~~~
/opt/nordic/ncs/v3.0.0/zephyr/drivers/disk/flashdisk.c:533:1: error: type of 'DEFINE_FLASHDISKS_CACHE' defaults to 'int' [-Werror=implicit-int]
  533 | PM_FOREACH_AFFILIATED_TO_disk(DEFINE_FLASHDISKS_CACHE)
      | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/opt/nordic/ncs/v3.0.0/zephyr/include/zephyr/init.h:141:44: error: declaration for parameter '__init_disk_flash_init' but no such parameter
  141 | #define Z_INIT_ENTRY_NAME(init_id) _CONCAT(__init_, init_id)
      |                                            ^~~~~~~
/opt/nordic/ncs/v3.0.0/zephyr/include/zephyr/toolchain/common.h:137:26: note: in definition of macro '_DO_CONCAT'
  137 | #define _DO_CONCAT(x, y) x ## y
      |                          ^
/opt/nordic/ncs/v3.0.0/zephyr/include/zephyr/init.h:141:36: note: in expansion of macro '_CONCAT'
  141 | #define Z_INIT_ENTRY_NAME(init_id) _CONCAT(__init_, init_id)
      |                                    ^~~~~~~
/opt/nordic/ncs/v3.0.0/zephyr/include/zephyr/init.h:241:17: note: in expansion of macro 'Z_INIT_ENTRY_NAME'
  241 |                 Z_INIT_ENTRY_NAME(name) = {.init_fn = {.sys = (init_fn_)},                \
      |                 ^~~~~~~~~~~~~~~~~
/opt/nordic/ncs/v3.0.0/zephyr/include/zephyr/init.h:223:9: note: in expansion of macro 'SYS_INIT_NAMED'
  223 |         SYS_INIT_NAMED(init_fn, init_fn, level, prio)
      |         ^~~~~~~~~~~~~~
/opt/nordic/ncs/v3.0.0/zephyr/drivers/disk/flashdisk.c:612:1: note: in expansion of macro 'SYS_INIT'
  612 | SYS_INIT(disk_flash_init, POST_KERNEL, CONFIG_KERNEL_INIT_PRIORITY_DEFAULT);
      | ^~~~~~~~
/opt/nordic/ncs/v3.0.0/zephyr/drivers/disk/flashdisk.c:572:30: error: declaration for parameter 'flash_disks' but no such parameter
  572 | static struct flashdisk_data flash_disks[] = {
      |                              ^~~~~~~~~~~
/opt/nordic/ncs/v3.0.0/zephyr/drivers/disk/flashdisk.c:613: error: expected '{' at end of input
/opt/nordic/ncs/v3.0.0/zephyr/drivers/disk/flashdisk.c:613: warning: control reaches end of non-void function [-Wreturn-type]
/opt/nordic/ncs/v3.0.0/zephyr/drivers/disk/flashdisk.c: At top level:
/opt/nordic/ncs/v3.0.0/zephyr/drivers/disk/flashdisk.c:464:37: warning: 'flash_disk_ops' defined but not used [-Wunused-const-variable=]
  464 | static const struct disk_operations flash_disk_ops = {
      |                                     ^~~~~~~~~~~~~~
cc1: some warnings being treated as errors
[36/287] Generating genhdr/moduledefs.split
ninja: build stopped: subcommand failed.
FAILED: [code=1] _sysbuild/sysbuild/images/zephyr-prefix/src/zephyr-stamp/zephyr-build /Users/tudor/Documents/GitHub/micropython_nRF/ports/zephyr/build/_sysbuild/sysbuild/images/zephyr-prefix/src/zephyr-stamp/zephyr-build
cd /Users/tudor/Documents/GitHub/micropython_nRF/ports/zephyr/build/zephyr && /Applications/CMake.app/Contents/bin/cmake --build .
ninja: build stopped: subcommand failed.
FATAL ERROR: command exited with status 1: /Applications/CMake.app/Contents/bin/cmake --build /Users/tudor/Documents/GitHub/micropython_nRF/ports/zephyr/build

Note: I got the partitions.yml, renamed it to pm_static.yml, put it in the project folder, and added the final segment ("external_storage:") to have an external storage. The file itself (had to change extension to .txt to be able to upload):

devzone.nordicsemi.com/.../7183.pm_5F00_static.txt

Then I added these to the board_ns.conf:

CONFIG_FILE_SYSTEM=y
CONFIG_FAT_FILESYSTEM_ELM=y
CONFIG_MASS_STORAGE_DISK_NAME="NAND"

Which brings out a new error:

thon.dir/nvmc.c.obj -c /Users/tudor/Documents/GitHub/micropython_nRF/ports/zephyr/nvmc.c
In file included from /opt/nordic/ncs/v3.0.0/zephyr/include/zephyr/sys/util_macro.h:34,
                 from /opt/nordic/ncs/v3.0.0/zephyr/include/zephyr/sys/util.h:17,
                 from /opt/nordic/ncs/v3.0.0/zephyr/include/zephyr/sys/atomic.h:18,
                 from /opt/nordic/ncs/v3.0.0/zephyr/include/zephyr/kernel_includes.h:25,
                 from /opt/nordic/ncs/v3.0.0/zephyr/include/zephyr/kernel.h:17,
                 from /Users/tudor/Documents/GitHub/micropython_nRF/ports/zephyr/nvmc.c:32:
/Users/tudor/Documents/GitHub/micropython_nRF/ports/zephyr/nvmc.c: In function 'nvmc_init':
/opt/nordic/ncs/v3.0.0/nrf/include/flash_map_pm.h:56:18: error: 'PM_PM_PM_storage_partition_ID_LABEL_OFFSET' undeclared (first use in this function)
   56 |         UTIL_CAT(PM_, UTIL_CAT(UTIL_CAT(PM_, UTIL_CAT(PM_ID(label), _LABEL)), x))
      |                  ^~~
/opt/nordic/ncs/v3.0.0/zephyr/include/zephyr/sys/util_internal.h:105:36: note: in definition of macro 'UTIL_PRIMITIVE_CAT'
  105 | #define UTIL_PRIMITIVE_CAT(a, ...) a##__VA_ARGS__
      |                                    ^
/opt/nordic/ncs/v3.0.0/nrf/include/flash_map_pm.h:56:9: note: in expansion of macro 'UTIL_CAT'
   56 |         UTIL_CAT(PM_, UTIL_CAT(UTIL_CAT(PM_, UTIL_CAT(PM_ID(label), _LABEL)), x))
      |         ^~~~~~~~
/opt/nordic/ncs/v3.0.0/nrf/include/flash_map_pm.h:59:39: note: in expansion of macro 'FIXED_PARTITION_DATA_FIELD'
   59 | #define FIXED_PARTITION_OFFSET(label) FIXED_PARTITION_DATA_FIELD(label, _OFFSET)
      |                                       ^~~~~~~~~~~~~~~~~~~~~~~~~~
/Users/tudor/Documents/GitHub/micropython_nRF/ports/zephyr/nvmc.c:46:33: note: in expansion of macro 'FIXED_PARTITION_OFFSET'
   46 | #define NVS_PARTITION_OFFSET    FIXED_PARTITION_OFFSET(NVS_PARTITION)
      |                                 ^~~~~~~~~~~~~~~~~~~~~~
/Users/tudor/Documents/GitHub/micropython_nRF/ports/zephyr/nvmc.c:74:26: note: in expansion of macro 'NVS_PARTITION_OFFSET'
   74 |         nvmc_fs.offset = NVS_PARTITION_OFFSET;
      |                          ^~~~~~~~~~~~~~~~~~~~
/opt/nordic/ncs/v3.0.0/nrf/include/flash_map_pm.h:56:18: note: each undeclared identifier is reported only once for each function it appears in
   56 |         UTIL_CAT(PM_, UTIL_CAT(UTIL_CAT(PM_, UTIL_CAT(PM_ID(label), _LABEL)), x))
      |                  ^~~
/opt/nordic/ncs/v3.0.0/zephyr/include/zephyr/sys/util_internal.h:105:36: note: in definition of macro 'UTIL_PRIMITIVE_CAT'
  105 | #define UTIL_PRIMITIVE_CAT(a, ...) a##__VA_ARGS__
      |                                    ^
/opt/nordic/ncs/v3.0.0/nrf/include/flash_map_pm.h:56:9: note: in expansion of macro 'UTIL_CAT'
   56 |         UTIL_CAT(PM_, UTIL_CAT(UTIL_CAT(PM_, UTIL_CAT(PM_ID(label), _LABEL)), x))
      |         ^~~~~~~~
/opt/nordic/ncs/v3.0.0/nrf/include/flash_map_pm.h:59:39: note: in expansion of macro 'FIXED_PARTITION_DATA_FIELD'
   59 | #define FIXED_PARTITION_OFFSET(label) FIXED_PARTITION_DATA_FIELD(label, _OFFSET)
      |                                       ^~~~~~~~~~~~~~~~~~~~~~~~~~
/Users/tudor/Documents/GitHub/micropython_nRF/ports/zephyr/nvmc.c:46:33: note: in expansion of macro 'FIXED_PARTITION_OFFSET'
   46 | #define NVS_PARTITION_OFFSET    FIXED_PARTITION_OFFSET(NVS_PARTITION)
      |                                 ^~~~~~~~~~~~~~~~~~~~~~
/Users/tudor/Documents/GitHub/micropython_nRF/ports/zephyr/nvmc.c:74:26: note: in expansion of macro 'NVS_PARTITION_OFFSET'
   74 |         nvmc_fs.offset = NVS_PARTITION_OFFSET;
      |                          ^~~~~~~~~~~~~~~~~~~~
[62/178] Building C object zephyr/lib/posix/options/CMakeFiles/lib__posix__options.dir/mqueue.c.obj
ninja: build stopped: subcommand failed.
FAILED: [code=1] _sysbuild/sysbuild/images/zephyr-prefix/src/zephyr-stamp/zephyr-build /Users/tudor/Documents/GitHub/micropython_nRF/ports/zephyr/build/_sysbuild/sysbuild/images/zephyr-prefix/src/zephyr-stamp/zephyr-build
cd /Users/tudor/Documents/GitHub/micropython_nRF/ports/zephyr/build/zephyr && /Applications/CMake.app/Contents/bin/cmake --build .
ninja: build stopped: subcommand failed.
FATAL ERROR: command exited with status 1: /Applications/CMake.app/Contents/bin/cmake --build /Users/tudor/Documents/GitHub/micropython_nRF/ports/zephyr/build

Although, I personally suspect that the new error doesn't fix the previous flash_disks error, but rather masks it because it appears before the "flash_disks" error in the build process.

This brings me back to my request: could you get Alex's sample that's attached above, and make it work for _ns; having these three CONFIG_ options enabled and then send it my way? :) :

CONFIG_ARM_TRUSTZONE_M=y

CONFIG_BUILD_WITH_TFM=y

CONFIG_TFM_PROFILE_TYPE_MINIMAL=y

RE: USB mass storage for the NRF7002DK development board using on board chip

Elfving — Thu, 14 Aug 2025 13:27:00 GMT

Heheh okay. Things are always moving fast here, though that is a good thing.

So this is referring to the/a sample that Alex provided you with which works, but does not with TFM.

[quote user="Tudor B."] This implicitly requires SB_CONFIG_PARTITION_MANAGER to be enabled.[/quote]

Yeah, I guess it makes sense that you can not use TFM with dts partitioning. If you are new to partition manager you can for instance see here, though the general idea is that you enable CONFIG_PARTITION_MANAGER_ENABLED (which will also overwrite dts partitions), which will let it choose the partition sizes dynamically. You'll then be able to tweak this yourself by having a look at the resulting partitions.yaml file, move it out to the project folder, tweak it, and name it pm_static.yaml.

So I wouldn't expect this to lead to any major issues. Could you see if you are able to do this?

Regards,

Elfving

RE: USB mass storage for the NRF7002DK development board using on board chip

Tudor B. — Wed, 13 Aug 2025 09:55:14 GMT

Hello and welcome back once again Elfving! Glad to hear you're better!

Things have evolved yet again since our last chat here. I'll paste the mail that I've sent to Alexander here:

Me and two colleagues have tried to integrate the sample that you provided into our project. Although the sample that you provided works perfectly as a standalone project, I think it's impossible for us to integrate it since we're building for non secure and implicitly using a small TFM partition to store some data. This implicitly requires SB_CONFIG_PARTITION_MANAGER to be enabled. By leaving it disabled (as it is in the sample), we get a plethora of TFM partition issues (the attached build log).

In essence, could you provide a sample that has this TFM configuration enabled, together with the USB mass storage?:

CONFIG_ARM_TRUSTZONE_M=y

CONFIG_BUILD_WITH_TFM=y

CONFIG_TFM_PROFILE_TYPE_MINIMAL=y

Thanks for the support Elfving. Hope we can sort it out fast. :)

RE: USB mass storage for the NRF7002DK development board using on board chip

Elfving — Wed, 13 Aug 2025 08:29:59 GMT

Sorry about the wait again, this time I've been OOO sick. Though I am very glad that Alexander can once again swoop in and help out when I'm unable to 😛

[quote user="Tudor B."]The sample as Alex gave me (with 2MB) works exactly as intended for both me and him. Our issue is that I tried increasing it to 8MB and it stayed at 2MB, then I gave it to a colleague and told him to increase it to 8MB and for him it worked.[/quote][quote user="Tudor B."]Alexander returned to the office and after presenting the current state of things to him, he suggested that I simply format the mass storage when I connect it to my PC. -> it worked perfectly![/quote]

Heheh perfect! I wouldn't have thought of that myself. Though I guess it would have to be something silly at fault when it works on your coworkers side and not yours.

[quote user="Tudor B."]The only question that remains: can we get it working using LittleFS also? :)[/quote]

Hopefully you just need an additional config and some dts changes for that to work (see here)

[quote user="Tudor B."]

Currently our architect and CEO are pushing for LittleFS for both File System and USB Mass Storage since it's more reliable and has error correction (theoretically). There's something called LittleFS FUSE that helps OSes recognise disks that have the LittleFS File System. I've played with it a bit but at this point I'm not sure if LFS FUSE ain't working correctly or if my config of the sample project is erroneous so LFS FUSE won't read the disk correctly.

[/quote]

I see that you have some arguments for littleFS here, though consider whether it would actually work with the OS you are using first. I've seen a lot of people claiming that Fat has more native OS support.

Regards,

Elfving

RE: USB mass storage for the NRF7002DK development board using on board chip

Tudor B. — Thu, 07 Aug 2025 19:59:13 GMT

Quick update:

Alexander returned to the office and after presenting the current state of things to him, he suggested that I simply format the mass storage when I connect it to my PC. -> it worked perfectly!

Now we finally have the full 8MB of the external chip accessible as a USB Mass Storage disk! Yay!

The only question that remains: can we get it working using LittleFS also? :)

RE: USB mass storage for the NRF7002DK development board using on board chip

Tudor B. — Fri, 01 Aug 2025 16:29:11 GMT

Writing a separate message to not make things confusing (not sure if you get notifications if I edit my reply or not, but I didn't when you edited yours).

The sample as Alex gave me (with 2MB) works exactly as intended for both me and him. Our issue is that I tried increasing it to 8MB and it stayed at 2MB, then I gave it to a colleague and told him to increase it to 8MB and for him it worked.

RE: USB mass storage for the NRF7002DK development board using on board chip

Tudor B. — Fri, 01 Aug 2025 13:23:30 GMT

Interesting point! Just tried it with 1MB: "reg = <0x00000000 0x00100000>;"

And indeed MacOS detected a 1MB disk. Will try to slowly increase the size to see what happens.
No pm_static.yml is present. The sample is identical to the most recent .zip that I attached here, but with the change to make the disk 8MB: reg = <0x00000000 0x00800000>;

Can't wait for next week then! :)

Edit:

Played around with it a bit more. If I set the limit to 3MB, this happens:

(in a high level layer, the disk is still reported as 2MB)

But also!:

(low level, it's correctly detected as 3MB)

I tried connecting it to Windows, but still it appears as a 2MB usb mass storage.

Edit 2:

I manually added the three CONFIG_ options that my colleague had; more exactly:

CONFIG_FS_FATFS_LFN=y
CONFIG_FS_FATFS_MAX_LFN=255
CONFIG_FS_FATFS_CODEPAGE=437

And now the only difference between our builds is that he has Python 3.12 and I have Python 3.13. Yet the behaviour is the same as described above.

Edit 3:

Interestingly enough, I put a 1.7MB image in a folder on the mass storage. The curious part is: even after "nrfjprog --eraseall" AND "nrfjprog --recover", the folder and image are still there! This suggests to me that whatever I did on my own (before getting this sample from Alexander) using the pm_static and the partition manager might have configured the mx25r64 chip to have 2MB in size and now with Alex's sample I can't really reconfigure it to 8MB.

RE: USB mass storage for the NRF7002DK development board using on board chip

Elfving — Fri, 01 Aug 2025 13:16:01 GMT

I agree that the size does look right, unfortunately :P Does changing it have an effect? Ie. can you make it claim to be 3 and 1 MB by changing the size parameter? And although 67108864 should imply 0x800000, could you try adding that as well, and see if it reacts in any way?

Are you using any overlay that might overwrite these partitions, like a pm_static file?

[quote user="Tudor B."]Edit: I'll try once again: is it possible to have a short call please so that we can quickly sort these kinks out and test really fast?[/quote]

I guess we could give this a go sometime next week, as it might also be practical to come up to speed in regards to what has been done while I was away. Though the thing is that it won't necessarily make anything go faster, as I won't necessarily immediately see what is wrong. I would typically have to search around.

EDIT: Didnt see your latest reply. That it works for Alex could also be a sign that there is an overlay file or something build-wise that is different between you two.. though I am not really seeing any sign of a pm file in the buildlog.

Regards,

Elfving

RE: USB mass storage for the NRF7002DK development board using on board chip

Tudor B. — Fri, 01 Aug 2025 07:22:28 GMT

Also a VERY interesting point:

I gave the same archive that Alexander provided to a colleague and told him about the modification to:

reg = <0x00000000 0x00800000>;

And to him, the full 8MB are exposed, but he had issues with using folders: creating a folder on the mass storage, ejecting and reconnecting it, lead to that folder being seen as a file. Repeating the previous process. but with the extra step of adding a file inside the folder, lead to the same behaviour. He mentioned that he might have some local SDK modifications related to his current task (external XIP), but he suspects that shouldn't have any impact.

He also said that he thinks the culprit would be a CMAKE version mismatch since I have "cmake version 4.0.3" and he has "cmake version 3.31.6". Personally I doubt that the difference in CMAKE causes the issue, but I'll provide my most recent build log just in case:

root@admins-MacBook-Air-2 mass_Alex_test # west build -b nrf7002dk/nrf5340/cpuapp --pristine ; west flash
-- west build: making build dir /opt/nordic/ncs/v3.0.0/zephyr/samples/subsys/usb/mass_Alex_test/build pristine
-- west build: generating a build system
Loading Zephyr module(s) (Zephyr base): sysbuild_default
-- Found Python3: /opt/homebrew/opt/python@3.13/bin/python3.13 (found suitable version "3.13.3", minimum required is "3.10") found components: Interpreter
-- Cache files will be written to: /Users/tudor/Library/Caches/zephyr
-- Found west (found suitable version "1.3.0", minimum required is "0.14.0")
-- Board: nrf7002dk, qualifiers: nrf5340/cpuapp
Parsing /opt/nordic/ncs/v3.0.0/zephyr/share/sysbuild/Kconfig
Loaded configuration '/opt/nordic/ncs/v3.0.0/zephyr/samples/subsys/usb/mass_Alex_test/build/_sysbuild/empty.conf'
Merged configuration '/opt/nordic/ncs/v3.0.0/zephyr/samples/subsys/usb/mass_Alex_test/sysbuild.conf'
Configuration saved to '/opt/nordic/ncs/v3.0.0/zephyr/samples/subsys/usb/mass_Alex_test/build/zephyr/.config'
Kconfig header saved to '/opt/nordic/ncs/v3.0.0/zephyr/samples/subsys/usb/mass_Alex_test/build/_sysbuild/autoconf.h'
--
   ************************************
   * Running CMake for mass_Alex_test *
   ************************************

Loading Zephyr default modules (Zephyr base).
-- Application: /opt/nordic/ncs/v3.0.0/zephyr/samples/subsys/usb/mass_Alex_test
-- CMake version: 4.0.3
-- Found Python3: /opt/homebrew/bin/python3 (found suitable version "3.13.3", minimum required is "3.10") found components: Interpreter
-- Cache files will be written to: /Users/tudor/Library/Caches/zephyr
-- Zephyr version: 4.0.99 (/opt/nordic/ncs/v3.0.0/zephyr)
-- Found west (found suitable version "1.3.0", minimum required is "0.14.0")
-- Board: nrf7002dk, qualifiers: nrf5340/cpuapp
-- ZEPHYR_TOOLCHAIN_VARIANT not set, trying to locate Zephyr SDK
-- Found host-tools: zephyr 0.17.0 (/Users/tudor/zephyr-sdk-0.17.0)
-- Found toolchain: zephyr 0.17.0 (/Users/tudor/zephyr-sdk-0.17.0)
-- Could NOT find Dtc (missing: DTC) (Required is at least version "1.4.6")
Hint: The project() command has not yet been called.  It sets up system-specific search paths.
-- Found BOARD.dts: /opt/nordic/ncs/v3.0.0/zephyr/boards/nordic/nrf7002dk/nrf7002dk_nrf5340_cpuapp.dts
-- Found devicetree overlay: /opt/nordic/ncs/v3.0.0/zephyr/samples/subsys/usb/mass_Alex_test/boards/nrf7002dk_nrf5340_cpuapp.overlay
-- Generated zephyr.dts: /opt/nordic/ncs/v3.0.0/zephyr/samples/subsys/usb/mass_Alex_test/build/mass_Alex_test/zephyr/zephyr.dts
-- Generated pickled edt: /opt/nordic/ncs/v3.0.0/zephyr/samples/subsys/usb/mass_Alex_test/build/mass_Alex_test/zephyr/edt.pickle
-- Generated zephyr.dts: /opt/nordic/ncs/v3.0.0/zephyr/samples/subsys/usb/mass_Alex_test/build/mass_Alex_test/zephyr/zephyr.dts
-- Generated devicetree_generated.h: /opt/nordic/ncs/v3.0.0/zephyr/samples/subsys/usb/mass_Alex_test/build/mass_Alex_test/zephyr/include/generated/zephyr/devicetree_generated.h
-- Including generated dts.cmake file: /opt/nordic/ncs/v3.0.0/zephyr/samples/subsys/usb/mass_Alex_test/build/mass_Alex_test/zephyr/dts.cmake
Parsing /opt/nordic/ncs/v3.0.0/zephyr/samples/subsys/usb/mass_Alex_test/Kconfig
Loaded configuration '/opt/nordic/ncs/v3.0.0/zephyr/boards/nordic/nrf7002dk/nrf7002dk_nrf5340_cpuapp_defconfig'
Merged configuration '/opt/nordic/ncs/v3.0.0/zephyr/samples/subsys/usb/mass_Alex_test/prj.conf'
Merged configuration '/opt/nordic/ncs/v3.0.0/zephyr/samples/subsys/usb/mass_Alex_test/build/mass_Alex_test/zephyr/.config.sysbuild'
Configuration saved to '/opt/nordic/ncs/v3.0.0/zephyr/samples/subsys/usb/mass_Alex_test/build/mass_Alex_test/zephyr/.config'
Kconfig header saved to '/opt/nordic/ncs/v3.0.0/zephyr/samples/subsys/usb/mass_Alex_test/build/mass_Alex_test/zephyr/include/generated/zephyr/autoconf.h'
-- Found GnuLd: /Users/tudor/zephyr-sdk-0.17.0/arm-zephyr-eabi/arm-zephyr-eabi/bin/ld.bfd (found version "2.38")
-- The C compiler identification is GNU 12.2.0
-- The CXX compiler identification is GNU 12.2.0
-- The ASM compiler identification is GNU
-- Found assembler: /Users/tudor/zephyr-sdk-0.17.0/arm-zephyr-eabi/bin/arm-zephyr-eabi-gcc
CMake Warning at /opt/nordic/ncs/v3.0.0/zephyr/subsys/usb/device/CMakeLists.txt:22 (message):
  CONFIG_USB_DEVICE_VID has default value 0x2FE3.

  This value is only for testing and MUST be configured for USB products.


-- Using ccache: /opt/homebrew/bin/ccache
-- Configuring done (3.9s)
-- Generating done (0.2s)
-- Build files have been written to: /opt/nordic/ncs/v3.0.0/zephyr/samples/subsys/usb/mass_Alex_test/build/mass_Alex_test
-- Configuring done (6.0s)
-- Generating done (0.0s)
-- Build files have been written to: /opt/nordic/ncs/v3.0.0/zephyr/samples/subsys/usb/mass_Alex_test/build
-- west build: building application
[5/8] Performing build step for 'mass_Alex_test'
[1/198] Preparing syscall dependency handling

[6/198] Generating include/generated/zephyr/version.h
-- Zephyr version: 4.0.99 (/opt/nordic/ncs/v3.0.0/zephyr), build: v4.0.99-ncs1
[198/198] Linking C executable zephyr/zephyr.elf
Memory region         Used Size  Region Size  %age Used
           FLASH:       75664 B         1 MB      7.22%
             RAM:       22328 B       448 KB      4.87%
        IDT_LIST:          0 GB        32 KB      0.00%
Generating files from /opt/nordic/ncs/v3.0.0/zephyr/samples/subsys/usb/mass_Alex_test/build/mass_Alex_test/zephyr/zephyr.elf for board: nrf7002dk
[8/8] Completed 'mass_Alex_test'
-- west flash: rebuilding
[0/3] Performing build step for 'mass_Alex_test'
ninja: no work to do.
[3/3] Completed 'mass_Alex_test'
-- west flash: using runner nrfutil
-- runners.nrfutil: reset after flashing requested
Using board 001050707950
-- runners.nrfutil: Flashing file: /opt/nordic/ncs/v3.0.0/zephyr/samples/subsys/usb/mass_Alex_test/build/mass_Alex_test/zephyr/zephyr.hex
-- runners.nrfutil: Erasing address ranges touched by firmware
-- runners.nrfutil: Programming image
-- runners.nrfutil: Verifying image
-- runners.nrfutil: Reset
-- runners.nrfutil: Board with serial number 1050707950 flashed successfully.

Edit:

Going down the build comparison rabbit hole, we discovered that:

- the cmake version installed doesn't make a difference

- I didn't have DTC installed (in my build log we can find: "-- Could NOT find Dtc (missing: DTC) (Required is at least version "1.4.6")"

- I installed DTC and now I get: "-- Found Dtc: /opt/homebrew/bin/dtc (found suitable version "1.7.2", minimum required is "1.4.6")"

- there are still two differences between our builds:

* he has python version is "python@3.12" and mine is "python@3.13".

* he has three extra options enabled via the menuconfig build:

warning: FS_FATFS_LFN (defined at subsys/fs/Kconfig.fatfs:116) was assigned the value 'y' but got
the value 'n'. Check these unsatisfied dependencies: FAT_FILESYSTEM_ELM (=n), FILE_SYSTEM (=n). See
http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_FS_FATFS_LFN and/or look up FS_FATFS_LFN in
the menuconfig/guiconfig interface. The Application Development Primer, Setting Configuration
Values, and Kconfig - Tips and Best Practices sections of the manual might be helpful too.


warning: FS_FATFS_MAX_LFN (defined at subsys/fs/Kconfig.fatfs:161) was assigned the value '255' but
got the value ''. Check these unsatisfied dependencies: FS_FATFS_LFN (=n), FAT_FILESYSTEM_ELM (=n),
FILE_SYSTEM (=n). See http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_FS_FATFS_MAX_LFN
and/or look up FS_FATFS_MAX_LFN in the menuconfig/guiconfig interface. The Application Development
Primer, Setting Configuration Values, and Kconfig - Tips and Best Practices sections of the manual
might be helpful too.


warning: FS_FATFS_CODEPAGE (defined at subsys/fs/Kconfig.fatfs:172) was assigned the value '437' but
got the value ''. Check these unsatisfied dependencies: FAT_FILESYSTEM_ELM (=n), FILE_SYSTEM (=n).
See http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_FS_FATFS_CODEPAGE and/or look up
FS_FATFS_CODEPAGE in the menuconfig/guiconfig interface. The Application Development Primer, Setting
Configuration Values, and Kconfig - Tips and Best Practices sections of the manual might be helpful
too.

For the sake of completeness, this is his build:

root@SANDAs-MacBook-Air mass_Alex_test # west build -b nrf7002dk/nrf5340/cpuapp --pristine
-- west build: making build dir /Users/sandabogdanmadalin/ncs/nrf/applications/mass_Alex_test/build pristine
-- west build: generating a build system
Loading Zephyr module(s) (Zephyr base): sysbuild_default
-- Found Python3: /opt/homebrew/opt/python@3.12/bin/python3.12 (found suitable version "3.12.10", minimum required is "3.10") found components: Interpreter
-- Cache files will be written to: /Users/sandabogdanmadalin/Library/Caches/zephyr
-- Found west (found suitable version "1.3.0", minimum required is "0.14.0")
-- Board: nrf7002dk, qualifiers: nrf5340/cpuapp
Parsing /Users/sandabogdanmadalin/ncs/nrf/zephyr/share/sysbuild/Kconfig
Loaded configuration '/Users/sandabogdanmadalin/ncs/nrf/applications/mass_Alex_test/build/_sysbuild/empty.conf'
Merged configuration '/Users/sandabogdanmadalin/ncs/nrf/applications/mass_Alex_test/sysbuild.conf'
Configuration saved to '/Users/sandabogdanmadalin/ncs/nrf/applications/mass_Alex_test/build/zephyr/.config'
Kconfig header saved to '/Users/sandabogdanmadalin/ncs/nrf/applications/mass_Alex_test/build/_sysbuild/autoconf.h'
-- 
   ************************************
   * Running CMake for mass_Alex_test *
   ************************************

Loading Zephyr default modules (Zephyr base).
-- Application: /Users/sandabogdanmadalin/ncs/nrf/applications/mass_Alex_test
-- CMake version: 3.31.6
-- Found Python3: /opt/homebrew/opt/python/libexec/bin/python (found suitable version "3.13.3", minimum required is "3.10") found components: Interpreter
-- Cache files will be written to: /Users/sandabogdanmadalin/Library/Caches/zephyr
-- Zephyr version: 4.0.99 (/Users/sandabogdanmadalin/ncs/nrf/zephyr)
-- Found west (found suitable version "1.3.0", minimum required is "0.14.0")
-- Board: nrf7002dk, qualifiers: nrf5340/cpuapp
-- ZEPHYR_TOOLCHAIN_VARIANT not set, trying to locate Zephyr SDK
-- Found host-tools: zephyr 0.17.0 (/opt/zephyr-sdk-0.17.0)
-- Found toolchain: zephyr 0.17.0 (/opt/zephyr-sdk-0.17.0)
-- Found Dtc: /opt/homebrew/bin/dtc (found suitable version "1.7.2", minimum required is "1.4.6")
-- Found BOARD.dts: /Users/sandabogdanmadalin/ncs/nrf/zephyr/boards/nordic/nrf7002dk/nrf7002dk_nrf5340_cpuapp.dts
-- Found devicetree overlay: /Users/sandabogdanmadalin/ncs/nrf/applications/mass_Alex_test/boards/nrf7002dk_nrf5340_cpuapp.overlay
-- Generated zephyr.dts: /Users/sandabogdanmadalin/ncs/nrf/applications/mass_Alex_test/build/mass_Alex_test/zephyr/zephyr.dts
-- Generated pickled edt: /Users/sandabogdanmadalin/ncs/nrf/applications/mass_Alex_test/build/mass_Alex_test/zephyr/edt.pickle
-- Generated zephyr.dts: /Users/sandabogdanmadalin/ncs/nrf/applications/mass_Alex_test/build/mass_Alex_test/zephyr/zephyr.dts
-- Generated devicetree_generated.h: /Users/sandabogdanmadalin/ncs/nrf/applications/mass_Alex_test/build/mass_Alex_test/zephyr/include/generated/zephyr/devicetree_generated.h
-- Including generated dts.cmake file: /Users/sandabogdanmadalin/ncs/nrf/applications/mass_Alex_test/build/mass_Alex_test/zephyr/dts.cmake

warning: FS_FATFS_LFN (defined at subsys/fs/Kconfig.fatfs:116) was assigned the value 'y' but got
the value 'n'. Check these unsatisfied dependencies: FAT_FILESYSTEM_ELM (=n), FILE_SYSTEM (=n). See
http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_FS_FATFS_LFN and/or look up FS_FATFS_LFN in
the menuconfig/guiconfig interface. The Application Development Primer, Setting Configuration
Values, and Kconfig - Tips and Best Practices sections of the manual might be helpful too.


warning: FS_FATFS_MAX_LFN (defined at subsys/fs/Kconfig.fatfs:161) was assigned the value '255' but
got the value ''. Check these unsatisfied dependencies: FS_FATFS_LFN (=n), FAT_FILESYSTEM_ELM (=n),
FILE_SYSTEM (=n). See http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_FS_FATFS_MAX_LFN
and/or look up FS_FATFS_MAX_LFN in the menuconfig/guiconfig interface. The Application Development
Primer, Setting Configuration Values, and Kconfig - Tips and Best Practices sections of the manual
might be helpful too.


warning: FS_FATFS_CODEPAGE (defined at subsys/fs/Kconfig.fatfs:172) was assigned the value '437' but
got the value ''. Check these unsatisfied dependencies: FAT_FILESYSTEM_ELM (=n), FILE_SYSTEM (=n).
See http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_FS_FATFS_CODEPAGE and/or look up
FS_FATFS_CODEPAGE in the menuconfig/guiconfig interface. The Application Development Primer, Setting
Configuration Values, and Kconfig - Tips and Best Practices sections of the manual might be helpful
too.

Parsing /Users/sandabogdanmadalin/ncs/nrf/applications/mass_Alex_test/Kconfig
Loaded configuration '/Users/sandabogdanmadalin/ncs/nrf/zephyr/boards/nordic/nrf7002dk/nrf7002dk_nrf5340_cpuapp_defconfig'
Merged configuration '/Users/sandabogdanmadalin/ncs/nrf/applications/mass_Alex_test/prj.conf'
Merged configuration '/Users/sandabogdanmadalin/ncs/nrf/applications/mass_Alex_test/build/mass_Alex_test/zephyr/.config.sysbuild'
Configuration saved to '/Users/sandabogdanmadalin/ncs/nrf/applications/mass_Alex_test/build/mass_Alex_test/zephyr/.config'
Kconfig header saved to '/Users/sandabogdanmadalin/ncs/nrf/applications/mass_Alex_test/build/mass_Alex_test/zephyr/include/generated/zephyr/autoconf.h'
-- Found GnuLd: /opt/zephyr-sdk-0.17.0/arm-zephyr-eabi/arm-zephyr-eabi/bin/ld.bfd (found version "2.38")
-- The C compiler identification is GNU 12.2.0
-- The CXX compiler identification is GNU 12.2.0
-- The ASM compiler identification is GNU
-- Found assembler: /opt/zephyr-sdk-0.17.0/arm-zephyr-eabi/bin/arm-zephyr-eabi-gcc
CMake Warning at /Users/sandabogdanmadalin/ncs/nrf/zephyr/subsys/usb/device/CMakeLists.txt:22 (message):
  CONFIG_USB_DEVICE_VID has default value 0x2FE3.

  This value is only for testing and MUST be configured for USB products.


-- Using ccache: /opt/homebrew/bin/ccache
-- Configuring done (3.8s)
-- Generating done (0.2s)
-- Build files have been written to: /Users/sandabogdanmadalin/ncs/nrf/applications/mass_Alex_test/build/mass_Alex_test
-- Configuring done (5.8s)
-- Generating done (0.0s)
-- Build files have been written to: /Users/sandabogdanmadalin/ncs/nrf/applications/mass_Alex_test/build
-- west build: building application
[5/8] Performing build step for 'mass_Alex_test'
[1/190] Preparing syscall dependency handling

[6/190] Generating include/generated/zephyr/version.h
-- Zephyr version: 4.0.99 (/Users/sandabogdanmadalin/ncs/nrf/zephyr), build: v4.0.99-ncs1
[190/190] Linking C executable zephyr/zephyr.elf
Memory region         Used Size  Region Size  %age Used
           FLASH:       63444 B         1 MB      6.05%
             RAM:       21296 B       448 KB      4.64%
        IDT_LIST:          0 GB        32 KB      0.00%
Generating files from /Users/sandabogdanmadalin/ncs/nrf/applications/mass_Alex_test/build/mass_Alex_test/zephyr/zephyr.elf for board: nrf7002dk
[8/8] Completed 'mass_Alex_test'
root@SANDAs-MacBook-Air mass_Alex_test # west flash
-- west flash: rebuilding
[0/3] Performing build step for 'mass_Alex_test'
ninja: no work to do.
[3/3] Completed 'mass_Alex_test'
-- west flash: using runner nrfutil
-- runners.nrfutil: reset after flashing requested
Using board 001050784114
-- runners.nrfutil: Flashing file: /Users/sandabogdanmadalin/ncs/nrf/applications/mass_Alex_test/build/mass_Alex_test/zephyr/zephyr.hex
-- runners.nrfutil: Erasing address ranges touched by firmware
-- runners.nrfutil: Programming image
-- runners.nrfutil: Verifying image
-- runners.nrfutil: Reset
-- runners.nrfutil: Board with serial number 1050784114 flashed successfully.

And this is my build:

root@192 mass_Alex_test # west build -b nrf7002dk/nrf5340/cpuapp --pristine ; west flash
-- west build: making build dir /opt/nordic/ncs/v3.0.0/zephyr/samples/subsys/usb/mass_Alex_test/build pristine
-- west build: generating a build system
Loading Zephyr module(s) (Zephyr base): sysbuild_default
-- Found Python3: /opt/homebrew/opt/python@3.13/bin/python3.13 (found suitable version "3.13.3", minimum required is "3.10") found components: Interpreter
-- Cache files will be written to: /Users/tudor/Library/Caches/zephyr
-- Found west (found suitable version "1.3.0", minimum required is "0.14.0")
-- Board: nrf7002dk, qualifiers: nrf5340/cpuapp
Parsing /opt/nordic/ncs/v3.0.0/zephyr/share/sysbuild/Kconfig
Loaded configuration '/opt/nordic/ncs/v3.0.0/zephyr/samples/subsys/usb/mass_Alex_test/build/_sysbuild/empty.conf'
Merged configuration '/opt/nordic/ncs/v3.0.0/zephyr/samples/subsys/usb/mass_Alex_test/sysbuild.conf'
Configuration saved to '/opt/nordic/ncs/v3.0.0/zephyr/samples/subsys/usb/mass_Alex_test/build/zephyr/.config'
Kconfig header saved to '/opt/nordic/ncs/v3.0.0/zephyr/samples/subsys/usb/mass_Alex_test/build/_sysbuild/autoconf.h'
--
   ************************************
   * Running CMake for mass_Alex_test *
   ************************************

Loading Zephyr default modules (Zephyr base).
-- Application: /opt/nordic/ncs/v3.0.0/zephyr/samples/subsys/usb/mass_Alex_test
-- CMake version: 3.31.6
-- Found Python3: /opt/homebrew/bin/python3 (found suitable version "3.13.3", minimum required is "3.10") found components: Interpreter
-- Cache files will be written to: /Users/tudor/Library/Caches/zephyr
-- Zephyr version: 4.0.99 (/opt/nordic/ncs/v3.0.0/zephyr)
-- Found west (found suitable version "1.3.0", minimum required is "0.14.0")
-- Board: nrf7002dk, qualifiers: nrf5340/cpuapp
-- ZEPHYR_TOOLCHAIN_VARIANT not set, trying to locate Zephyr SDK
-- Found host-tools: zephyr 0.17.0 (/Users/tudor/zephyr-sdk-0.17.0)
-- Found toolchain: zephyr 0.17.0 (/Users/tudor/zephyr-sdk-0.17.0)
-- Found Dtc: /opt/homebrew/bin/dtc (found suitable version "1.7.2", minimum required is "1.4.6")
-- Found BOARD.dts: /opt/nordic/ncs/v3.0.0/zephyr/boards/nordic/nrf7002dk/nrf7002dk_nrf5340_cpuapp.dts
-- Found devicetree overlay: /opt/nordic/ncs/v3.0.0/zephyr/samples/subsys/usb/mass_Alex_test/boards/nrf7002dk_nrf5340_cpuapp.overlay
-- Generated zephyr.dts: /opt/nordic/ncs/v3.0.0/zephyr/samples/subsys/usb/mass_Alex_test/build/mass_Alex_test/zephyr/zephyr.dts
-- Generated pickled edt: /opt/nordic/ncs/v3.0.0/zephyr/samples/subsys/usb/mass_Alex_test/build/mass_Alex_test/zephyr/edt.pickle
-- Generated zephyr.dts: /opt/nordic/ncs/v3.0.0/zephyr/samples/subsys/usb/mass_Alex_test/build/mass_Alex_test/zephyr/zephyr.dts
-- Generated devicetree_generated.h: /opt/nordic/ncs/v3.0.0/zephyr/samples/subsys/usb/mass_Alex_test/build/mass_Alex_test/zephyr/include/generated/zephyr/devicetree_generated.h
-- Including generated dts.cmake file: /opt/nordic/ncs/v3.0.0/zephyr/samples/subsys/usb/mass_Alex_test/build/mass_Alex_test/zephyr/dts.cmake
Parsing /opt/nordic/ncs/v3.0.0/zephyr/samples/subsys/usb/mass_Alex_test/Kconfig
Loaded configuration '/opt/nordic/ncs/v3.0.0/zephyr/boards/nordic/nrf7002dk/nrf7002dk_nrf5340_cpuapp_defconfig'
Merged configuration '/opt/nordic/ncs/v3.0.0/zephyr/samples/subsys/usb/mass_Alex_test/prj.conf'
Merged configuration '/opt/nordic/ncs/v3.0.0/zephyr/samples/subsys/usb/mass_Alex_test/build/mass_Alex_test/zephyr/.config.sysbuild'
Configuration saved to '/opt/nordic/ncs/v3.0.0/zephyr/samples/subsys/usb/mass_Alex_test/build/mass_Alex_test/zephyr/.config'
Kconfig header saved to '/opt/nordic/ncs/v3.0.0/zephyr/samples/subsys/usb/mass_Alex_test/build/mass_Alex_test/zephyr/include/generated/zephyr/autoconf.h'
-- Found GnuLd: /Users/tudor/zephyr-sdk-0.17.0/arm-zephyr-eabi/arm-zephyr-eabi/bin/ld.bfd (found version "2.38")
-- The C compiler identification is GNU 12.2.0
-- The CXX compiler identification is GNU 12.2.0
-- The ASM compiler identification is GNU
-- Found assembler: /Users/tudor/zephyr-sdk-0.17.0/arm-zephyr-eabi/bin/arm-zephyr-eabi-gcc
CMake Warning at /opt/nordic/ncs/v3.0.0/zephyr/subsys/usb/device/CMakeLists.txt:22 (message):
  CONFIG_USB_DEVICE_VID has default value 0x2FE3.

  This value is only for testing and MUST be configured for USB products.


-- Using ccache: /opt/homebrew/bin/ccache
-- Configuring done (3.5s)
-- Generating done (0.2s)
-- Build files have been written to: /opt/nordic/ncs/v3.0.0/zephyr/samples/subsys/usb/mass_Alex_test/build/mass_Alex_test
-- Configuring done (5.2s)
-- Generating done (0.0s)
-- Build files have been written to: /opt/nordic/ncs/v3.0.0/zephyr/samples/subsys/usb/mass_Alex_test/build
-- west build: building application
[5/8] Performing build step for 'mass_Alex_test'
[1/190] Preparing syscall dependency handling

[6/190] Generating include/generated/zephyr/version.h
-- Zephyr version: 4.0.99 (/opt/nordic/ncs/v3.0.0/zephyr), build: v4.0.99-ncs1
[190/190] Linking C executable zephyr/zephyr.elf
Memory region         Used Size  Region Size  %age Used
           FLASH:       63580 B         1 MB      6.06%
             RAM:       21296 B       448 KB      4.64%
        IDT_LIST:          0 GB        32 KB      0.00%
Generating files from /opt/nordic/ncs/v3.0.0/zephyr/samples/subsys/usb/mass_Alex_test/build/mass_Alex_test/zephyr/zephyr.elf for board: nrf7002dk
[8/8] Completed 'mass_Alex_test'
-- west flash: rebuilding
[0/3] Performing build step for 'mass_Alex_test'
ninja: no work to do.
[3/3] Completed 'mass_Alex_test'
-- west flash: using runner nrfutil
-- runners.nrfutil: reset after flashing requested
Using board 001050707950
-- runners.nrfutil: Flashing file: /opt/nordic/ncs/v3.0.0/zephyr/samples/subsys/usb/mass_Alex_test/build/mass_Alex_test/zephyr/zephyr.hex
-- runners.nrfutil: Erasing address ranges touched by firmware
-- runners.nrfutil: Programming image
-- runners.nrfutil: Verifying image
-- runners.nrfutil: Reset
-- runners.nrfutil: Board with serial number 1050707950 flashed successfully.

RE: USB mass storage for the NRF7002DK development board using on board chip

Tudor B. — Thu, 31 Jul 2025 08:29:05 GMT

I found the related .dts. Path: /opt/nordic/ncs/v3.0.0/zephyr/boards/nordic/nrf7002dk/nrf5340_cpuapp_common.dtsi

What we're interested in:

&spi4 {
	compatible = "nordic,nrf-spim";
	status = "okay";
	pinctrl-0 = <&spi4_default>;
	pinctrl-1 = <&spi4_sleep>;
	pinctrl-names = "default", "sleep";
	cs-gpios = <&gpio0 11 GPIO_ACTIVE_LOW>;
	mx25r64: mx25r6435f@0 {
		compatible = "jedec,spi-nor";
		reg = <0>;
		spi-max-frequency = <33000000>;
		jedec-id = [c2 28 17];
		sfdp-bfp = [
			e5 20 f1 ff ff ff ff 03 44 eb 08 6b 08 3b 04 bb
			ee ff ff ff ff ff 00 ff ff ff 00 ff 0c 20 0f 52
			10 d8 00 ff 23 72 f5 00 82 ed 04 cc 44 83 68 44
			30 b0 30 b0 f7 c4 d5 5c 00 be 29 ff f0 d0 ff ff
		];
		size = <67108864>;
		has-dpd;
		t-enter-dpd = <10000>;
		t-exit-dpd = <5000>;
	};
};

As far as I can tell, "size = <67108864>;" is technically correct since based on the memory's datasheet (which can be found here: https://www.macronix.com/Lists/Datasheet/Attachments/8868/MX25R6435F,%20Wide%20Range,%2064Mb,%20v1.6.pdf), we have:

1. FEATURES 
GENERAL
• Supports Serial Peripheral Interface -- Mode 0 and Mode 3
• 67,108,864 x 1 bit structure or 33,554,432 x 2 bits (two I/O mode) structure or 16,777,216 x 4 bits (four I/O mode) structure

So, I suspect that <size> isn't the problem.

RE: USB mass storage for the NRF7002DK development board using on board chip

Tudor B. — Thu, 31 Jul 2025 08:17:20 GMT

Thank you for the hasty reply Elfving!

I'll check those points out and get back to you in 1H tops.

Edit: I'll try once again: is it possible to have a short call please so that we can quickly sort these kinks out and test really fast?

RE: USB mass storage for the NRF7002DK development board using on board chip

Elfving — Thu, 31 Jul 2025 08:14:05 GMT

HAhah gotya

[quote user="Tudor B."]

- when connecting it to Windows, if you copy a file to it and then decide to delete it, the file doesn't go to my computer's Recycle Bin, but rather a hidden folder is created that's named ".Trashed". To truly delete the file; you must delete it from inside the .Trashed folder. Is this a bug or a feature?

[/quote]

Hehe a strange feature I guess. Sounds a bit confusing, though I guess windows doesn't want to just move any file to its own recycle bin. This soft delete function in the app should be possible to simply remove though.

[quote user="Tudor B."]

- if you restart/ power on your Windows machine and left the usb mass storage connected, the explorer.exe doesn't start correctly until you unplug the devkit.

[/quote]

Odd. Though the machine does otherwise start up? Is it set to boot from USB? It looks like this is a general issue others have faced as well. You could try delaying opening the MSD interface until after explorer.exe presumably starts.

[quote user="Tudor B."]

- for the life of me, I can't get it to expose the full 8MB of flash as a mass storage. I tried modifying the related register in the overlay file into: reg = <0x00000000 0x00800000>; but to no effect. I also tried "nrfjprog --eraseall" and "nrfjprog --recover" but whatever I do, the usb mass storage created is always 2MB in size.

[/quote]

That is interesting. I assume the issue is related to something like this and this. Does changing the size change anything? Could you make sure that your changes to that parameter are having an effect?

[quote user="Tudor B."]

- also we'd like to access it from the code as to be able to read/ write those files. I assume that'll be possible, right?

[/quote]

Yeah, though you might have to turn off this interface for the computer while doing it. See here and here.

Regards,

Elfving

RE: USB mass storage for the NRF7002DK development board using on board chip

Tudor B. — Wed, 30 Jul 2025 19:34:35 GMT

ELFVIIIING! Welcome back!

[quote userid="103347" url="~/f/nordic-q-a/122517/usb-mass-storage-for-the-nrf7002dk-development-board-using-on-board-chip/544119"]

Is everything really working the way it should now?

[/quote]

A succinct answer:

But memes aside, here's the sample that Alexander sent me:

devzone.nordicsemi.com/.../7282.mass.zip

I have a few notes regarding it:

- if you restart/ power on your Windows machine and left the usb mass storage connected, the explorer.exe doesn't start correctly until you unplug the devkit.

- also we'd like to access it from the code as to be able to read/ write those files. I assume that'll be possible, right?

Further points we can discuss after we wrap the above up.

Have a great day/ night and hope to hear from you soon! :)

RE: USB mass storage for the NRF7002DK development board using on board chip

Elfving — Wed, 30 Jul 2025 14:41:11 GMT

Hi, and sorry about the wait Tudor! I have been OOO for a while, and assumed this would be picked up by someone else.

I'll try to get back to you on your questions later this week. Seems like a you've gone through a lot here, though I am glad you've gotten help from Alexander while I was away. Is everything really working the way it should now?

Regards,

Elfving

RE: USB mass storage for the NRF7002DK development board using on board chip

Tudor B. — Mon, 28 Jul 2025 09:34:54 GMT

After a few tries, Alexander Rawstone managed to get a FAT FS usb mass storage sample going.

The sample provided by him: devzone.nordicsemi.com/.../1884.mass.zip

It works flawlessly with files, folders and is recognised by both MacOS and Windows.

I played around with it a bit and found some interesting points:

- when connecting it to Windows, if you copy a file to it and then decide to delete it, the file doesn't go to the computer's Recycle Bin, but rather a hidden folder is created that's named ".Trashed". To truly delete the file; you must delete it from inside the .Trashed folder. Is this a bug or a feature?

- if you restart/ power on your Windows machine and left the usb mass storage connected, the explorer.exe process doesn't start correctly (after login, a black screen is presented, not the desktop) until you unplug the devkit (then the desktop appears).

- whatever I do, I can't get it to expose the full 8MB of flash as a mass storage. I tried modifying the related register in the overlay file into: reg = <0x00000000 0x00800000>; but to no effect. I also tried "nrfjprog --eraseall" and "nrfjprog --recover" but whatever I do, the usb mass storage created is always 2MB in size.

- based on the sample in the archive, the board's startup log is:

*** Booting nRF Connect SDK v3.0.0-3bfc46578e42 ***
*** Using Zephyr OS v4.0.99-a0e545cb437a ***
Dead here...point 1
[00:00:00.337,188] <inf> flashdisk: Initialize device NAND
[00:00:00.337,188] <inf> flashdisk: offset 0, sector size 512, page size 4096, volume size 8388608
Dead here...Error code: 0
Area 0 at 0x0 on mx25r6435f@0 for 8388608 bytes
[00:00:00.340,698] <inf> main: No file system selected
[00:00:00.340,881] <inf> main: The device is put in USB mass storage mode.

The fact that I prints "No file system selected", leads me to main.c, in the function "

setup_disk()", where this message is printed. The fact that this message is printed towards the beginning of the function and then returns out of it, and the fact that there is more code/ logic that would normally run if the function wouldn't return so soon (especially the call to "mount_app_fs()"), suggests that this sample is potentially incomplete.

RE: USB mass storage for the NRF7002DK development board using on board chip

Tudor B. — Mon, 21 Jul 2025 07:03:31 GMT

An extra test that I did: I tried copying a 25kb text file to the mass storage.

The file contained ~25kilobytes of text. Again the "Copying..." popup window appeared, it froze a bit, then dropped the copy process and the mass storage got ejected.

I restarted the board and the mass storage contained a text file with the same name and metadata, but instead of the ~480 lines of text that the original file had, it had 1 line, which contained exactly 256 characters from the original text (implicitly 256 bytes), and the rest were 24911 the same character:

ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ

Interestingly enough, if you simply copy the text file from the mass storage to the local drive, the file remains 25kb in size. But if instead you open it up and copy the text to a new text file, the new file will have a size of 49kb (double the original).

This leads to the suspicion that the parameters of the usb mass storage are somehow "off", meaning that cache/ read/ write sizes or block/ page sizes are incongruent with the actual specifications of the mx25r64 chip.

RE: USB mass storage for the NRF7002DK development board using on board chip

Tudor B. — Thu, 17 Jul 2025 13:39:58 GMT

Today me and a colleague had a short call with Alexander Rawstone in hopes of hastening the processing of this ticket.

RE: USB mass storage for the NRF7002DK development board using on board chip

Tudor B. — Tue, 15 Jul 2025 06:54:33 GMT

After some more testing, here are some conclusions of the current state of things:

FAT FS seems to work on Windows but crashes HORRIBLY on MacOS. Board bootup log (note, this is after I connected it to a Windows machine and created a text file on it named AAA.txt):

I'm using the Disk Utility App to check if MacOS detects the mass storage. Disk Utility freezes, then it forcefully ejects the Zephyr storage (which it sees as " ") and somehow formats it.

I also tried using a bash command: diskutil list. But the behaviour is the same: terminal does nothing for ~20 seconds and then lists all disks except the Zephyr disk (again ejecting and formatting the disk).

On the Windows side: the drive mounts up, you can create a file and save data to it, you can eject it/ power off the board and upon power on the file is still there:

This morning I decided to dig deeper on the Windows side since the board logs show that the internal flash is still used. So I decided to try and put a 2.1 MB image on the drive:

Windows popped up the "Copying" window, it thought for a few seconds, then closed it and forcefully ejected the drive. I restarted the board and the text file that I created was there together with the picture that I tried copying. So I tried copying the picture back to my drive to check if it was correctly stored. This is the picture that I got from the drive:

The name and size are the same as the original image, but the actual data inside the file is corrupted/ inacessible. -> most likely just metadata about the file was copied (name, size, date created, etc.), but the contents themselves weren't since they wouldn't fit in the internal flash.

I opened the serial port for COM4 to see what're the board's logs:

Serial port COM4 opened
[00:00:00.322,021] [1;33m<wrn> spi_nor: Waiting until flash is ready[0m
[00:00:00.324,401] [0m<inf> spi_nor: mx25r6435f@0: 8 MiBy flash[0m
*** Booting nRF Connect SDK v3.0.0-3bfc46578e42 ***
*** Using Zephyr OS v4.0.99-a0e545cb437a ***
[00:00:00.326,721] [0m<inf> flashdisk: Initialize device NAND[0m
[00:00:00.326,751] [0m<inf> flashdisk: offset 0, sector size 512, page size 4096, volume size 8388608[0m
Area 6 at 0xfc000 on flash-controller@39000 for 8192 bytes
/NAND:: bsize = 512 ; frsize = 4096 ; blocks = 2043 ; bfree = 1499
[1;31m--- 353 messages dropped ---
[0m  D 4294967295 ÿÿÿÿ.ÿ{FF}
[1;31m--- 20 messages dropped ---
[0m  D 4294967295 ÿÿÿÿ.ÿ{FF}
  D 4294967295 ÿÿÿÿ.ÿ{FF}
  D 4294967295 ÿÿÿÿ.ÿ{FF}
  D 4294967295 ÿÿÿÿ.ÿ{FF}
  D 4294967295 ÿÿÿÿ.ÿ{FF}
  D 4294967295 ÿÿÿÿ.ÿ{FF}
  D 4294967295 ÿÿÿÿ.ÿ{FF}
  D 4294967295 ÿÿÿÿ.ÿ{FF}
  D 4294967295 ÿÿÿÿ.ÿ{FF}
  D 4294967295 ÿÿÿÿ.ÿ{FF}
  D 4294967295 ÿÿÿÿ.ÿ{FF}
  D 4294967295 ÿÿÿÿ.ÿ{FF}
  D 0 FSEV~384
  D 0 SYSTEM~1
  F 19 AAA.TXT
  F 2207741 DMC_VE~1.PNG
End of files
[00:00:00.414,947] [0m<inf> main: The device is put in USB mass storage mode.
[0m
[00:00:01.053,253] [1;31m<err> usb_msc: LBA out of range[0m
[00:00:01.522,308] [1;31m<err> usb_msc: LBA out of range[0m
Serial port COM4 closed

So, although it KINDA works on Windows, unless I see "Area 4 at 0x0 on MX25R64 for" in the board's bootup logs, the external flash isn't used for USB mass storage.

RE: USB mass storage for the NRF7002DK development board using on board chip

Tudor B. — Mon, 14 Jul 2025 15:53:37 GMT

Hey Elfving,

Today our architect convened that we try the FATFS route. Sadly that didn't work.

Initially I tried following the example from the link that you gave and adapt it to my board (empty the *.conf file, leave just the suggested changes in the *.overlay file). -> failed since no disk was exposed towards the partition manager:

[88/206] Building C object zephyr/drivers/disk/CMakeFiles/drivers__disk.dir/flashdisk.c.obj
FAILED: zephyr/drivers/disk/CMakeFiles/drivers__disk.dir/flashdisk.c.obj
ccache /Users/tudor/zephyr-sdk-0.17.0/arm-zephyr-eabi/bin/arm-zephyr-eabi-gcc -DKERNEL -DK_HEAP_MEM_POOL_SIZE=0 -DMBEDTLS_CONFIG_FILE=\"nrf-config.h\" -DMBEDTLS_PSA_CRYPTO_CONFIG_FILE=\"nrf-psa-crypto-config.h\" -DNRF5340_XXAA_APPLICATION -DNRF_SKIP_FICR_NS_COPY_TO_RAM -DNRF_TRUSTZONE_NONSECURE -DPICOLIBC_LONG_LONG_PRINTF_SCANF -DUSE_PARTITION_MANAGER=1 -D__LINUX_ERRNO_EXTENSIONS__ -D__PROGRAM_START -D__ZEPHYR_SUPERVISOR__ -D__ZEPHYR__=1 -I/opt/nordic/ncs/v3.0.0/zephyr/samples/subsys/usb/mass/build/mass/zephyr/include/generated/zephyr -I/opt/nordic/ncs/v3.0.0/zephyr/include -I/opt/nordic/ncs/v3.0.0/zephyr/samples/subsys/usb/mass/build/mass/zephyr/include/generated -I/opt/nordic/ncs/v3.0.0/zephyr/soc/nordic -I/opt/nordic/ncs/v3.0.0/zephyr/soc/nordic/nrf53/. -I/opt/nordic/ncs/v3.0.0/zephyr/soc/nordic/common/. -I/opt/nordic/ncs/v3.0.0/zephyr/subsys/usb/device -I/opt/nordic/ncs/v3.0.0/zephyr/subsys/settings/include -I/opt/nordic/ncs/v3.0.0/zephyr/drivers/usb/common/nrf_usbd_common/. -I/opt/nordic/ncs/v3.0.0/nrf/include -I/opt/nordic/ncs/v3.0.0/zephyr/samples/subsys/usb/mass/build/mass/tfm/api_ns/interface/include -I/opt/nordic/ncs/v3.0.0/nrf/subsys/settings/include -I/opt/nordic/ncs/v3.0.0/nrf/modules/trusted-firmware-m/. -I/opt/nordic/ncs/v3.0.0/nrf/include/tfm -I/opt/nordic/ncs/v3.0.0/nrf/tests/include -I/opt/nordic/ncs/v3.0.0/modules/hal/cmsis/CMSIS/Core/Include -I/opt/nordic/ncs/v3.0.0/zephyr/modules/cmsis/. -I/opt/nordic/ncs/v3.0.0/nrf/modules/hal_nordic/. -I/opt/nordic/ncs/v3.0.0/modules/hal/nordic/nrfx -I/opt/nordic/ncs/v3.0.0/modules/hal/nordic/nrfx/drivers/include -I/opt/nordic/ncs/v3.0.0/modules/hal/nordic/nrfx/mdk -I/opt/nordic/ncs/v3.0.0/zephyr/modules/hal_nordic/nrfx/. -I/opt/nordic/ncs/v3.0.0/zephyr/samples/subsys/usb/mass/build/mass/input_files -I/opt/nordic/ncs/v3.0.0/zephyr/samples/subsys/usb/mass/build/mass -I/opt/nordic/ncs/v3.0.0/zephyr/samples/subsys/usb/mass/build/mass/generated/interface_nrf_security_psa -I/opt/nordic/ncs/v3.0.0/nrf/subsys/nrf_security/include -I/opt/nordic/ncs/v3.0.0/modules/crypto/oberon-psa-crypto/include -I/opt/nordic/ncs/v3.0.0/nrf/subsys/nrf_security/src/utils -I/opt/nordic/ncs/v3.0.0/modules/crypto/oberon-psa-crypto/library -I/opt/nordic/ncs/v3.0.0/modules/crypto/mbedtls/library -I/opt/nordic/ncs/v3.0.0/modules/crypto/mbedtls/include -I/opt/nordic/ncs/v3.0.0/modules/crypto/mbedtls/include/library -I/opt/nordic/ncs/v3.0.0/nrfxlib/crypto/nrf_oberon/include -I/opt/nordic/ncs/v3.0.0/nrfxlib/crypto/nrf_oberon/include/mbedtls -isystem /opt/nordic/ncs/v3.0.0/zephyr/lib/libc/common/include -Wshadow -fno-strict-aliasing -Os -imacros /opt/nordic/ncs/v3.0.0/zephyr/samples/subsys/usb/mass/build/mass/zephyr/include/generated/zephyr/autoconf.h -fno-printf-return-value -fno-common -g -gdwarf-4 -fdiagnostics-color=always -mcpu=cortex-m33 -mthumb -mabi=aapcs -mfp16-format=ieee -mtp=soft --sysroot=/Users/tudor/zephyr-sdk-0.17.0/arm-zephyr-eabi/arm-zephyr-eabi -imacros /opt/nordic/ncs/v3.0.0/zephyr/include/zephyr/toolchain/zephyr_stdint.h -Wall -Wformat -Wformat-security -Wno-format-zero-length -Wdouble-promotion -Wno-pointer-sign -Wpointer-arith -Wexpansion-to-defined -Wno-unused-but-set-variable -Werror=implicit-int -fno-pic -fno-pie -fno-asynchronous-unwind-tables -ftls-model=local-exec -fno-reorder-functions --param=min-pagesize=0 -fno-defer-pop -fmacro-prefix-map=/opt/nordic/ncs/v3.0.0/zephyr/samples/subsys/usb/mass=CMAKE_SOURCE_DIR -fmacro-prefix-map=/opt/nordic/ncs/v3.0.0/zephyr=ZEPHYR_BASE -fmacro-prefix-map=/opt/nordic/ncs/v3.0.0=WEST_TOPDIR -ffunction-sections -fdata-sections -specs=picolibc.specs -std=c99 -MD -MT zephyr/drivers/disk/CMakeFiles/drivers__disk.dir/flashdisk.c.obj -MF zephyr/drivers/disk/CMakeFiles/drivers__disk.dir/flashdisk.c.obj.d -o zephyr/drivers/disk/CMakeFiles/drivers__disk.dir/flashdisk.c.obj -c /opt/nordic/ncs/v3.0.0/zephyr/drivers/disk/flashdisk.c
/opt/nordic/ncs/v3.0.0/zephyr/drivers/disk/flashdisk.c:533:1: error: return type defaults to 'int' [-Werror=implicit-int]
  533 | PM_FOREACH_AFFILIATED_TO_disk(DEFINE_FLASHDISKS_CACHE)
      | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/opt/nordic/ncs/v3.0.0/zephyr/drivers/disk/flashdisk.c: In function 'PM_FOREACH_AFFILIATED_TO_disk':
/opt/nordic/ncs/v3.0.0/zephyr/drivers/disk/flashdisk.c:572:30: error: storage class specified for parameter 'flash_disks'
  572 | static struct flashdisk_data flash_disks[] = {
      |                              ^~~~~~~~~~~
/opt/nordic/ncs/v3.0.0/zephyr/drivers/disk/flashdisk.c:572:15: error: parameter 'flash_disks' is initialized
  572 | static struct flashdisk_data flash_disks[] = {
      |               ^~~~~~~~~~~~~~
/opt/nordic/ncs/v3.0.0/zephyr/drivers/disk/flashdisk.c:573:39: error: 'DEFINE_FLASHDISKS_DEVICE' undeclared (first use in this function)
  573 |         PM_FOREACH_AFFILIATED_TO_disk(DEFINE_FLASHDISKS_DEVICE)
      |                                       ^~~~~~~~~~~~~~~~~~~~~~~~
/opt/nordic/ncs/v3.0.0/zephyr/drivers/disk/flashdisk.c:573:39: note: each undeclared identifier is reported only once for each function it appears in
/opt/nordic/ncs/v3.0.0/zephyr/drivers/disk/flashdisk.c:582:1: error: expected declaration specifiers before 'PM_FOREACH_AFFILIATED_TO_disk'
  582 | PM_FOREACH_AFFILIATED_TO_disk(VERIFY_CACHE_SIZE_IS_NOT_ZERO_IF_NOT_READ_ONLY)
      | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from /opt/nordic/ncs/v3.0.0/zephyr/include/zephyr/toolchain/gcc.h:98,
                 from /opt/nordic/ncs/v3.0.0/zephyr/include/zephyr/toolchain.h:50,
                 from /opt/nordic/ncs/v3.0.0/zephyr/include/zephyr/sys/__assert.h:11,
                 from /opt/nordic/ncs/v3.0.0/zephyr/drivers/disk/flashdisk.c:10:
/opt/nordic/ncs/v3.0.0/zephyr/include/zephyr/init.h:141:44: error: storage class specified for parameter '__init_disk_flash_init'
  141 | #define Z_INIT_ENTRY_NAME(init_id) _CONCAT(__init_, init_id)
      |                                            ^~~~~~~
/opt/nordic/ncs/v3.0.0/zephyr/include/zephyr/toolchain/common.h:137:26: note: in definition of macro '_DO_CONCAT'
  137 | #define _DO_CONCAT(x, y) x ## y
      |                          ^
/opt/nordic/ncs/v3.0.0/zephyr/include/zephyr/init.h:141:36: note: in expansion of macro '_CONCAT'
  141 | #define Z_INIT_ENTRY_NAME(init_id) _CONCAT(__init_, init_id)
      |                                    ^~~~~~~
/opt/nordic/ncs/v3.0.0/zephyr/include/zephyr/init.h:241:17: note: in expansion of macro 'Z_INIT_ENTRY_NAME'
  241 |                 Z_INIT_ENTRY_NAME(name) = {.init_fn = {.sys = (init_fn_)},                \
      |                 ^~~~~~~~~~~~~~~~~
/opt/nordic/ncs/v3.0.0/zephyr/include/zephyr/init.h:223:9: note: in expansion of macro 'SYS_INIT_NAMED'
  223 |         SYS_INIT_NAMED(init_fn, init_fn, level, prio)
      |         ^~~~~~~~~~~~~~
/opt/nordic/ncs/v3.0.0/zephyr/drivers/disk/flashdisk.c:613:1: note: in expansion of macro 'SYS_INIT'
  613 | SYS_INIT(disk_flash_init, POST_KERNEL, CONFIG_KERNEL_INIT_PRIORITY_DEFAULT);
      | ^~~~~~~~
/opt/nordic/ncs/v3.0.0/zephyr/include/zephyr/init.h:239:42: error: parameter '__init_disk_flash_init' is initialized
  239 |         static const Z_DECL_ALIGN(struct init_entry)                                      \
      |                                          ^~~~~~~~~~
/opt/nordic/ncs/v3.0.0/zephyr/include/zephyr/toolchain/common.h:195:55: note: in definition of macro 'Z_DECL_ALIGN'
  195 | #define Z_DECL_ALIGN(type) __aligned(__alignof(type)) type
      |                                                       ^~~~
/opt/nordic/ncs/v3.0.0/zephyr/include/zephyr/init.h:223:9: note: in expansion of macro 'SYS_INIT_NAMED'
  223 |         SYS_INIT_NAMED(init_fn, init_fn, level, prio)
      |         ^~~~~~~~~~~~~~
/opt/nordic/ncs/v3.0.0/zephyr/drivers/disk/flashdisk.c:613:1: note: in expansion of macro 'SYS_INIT'
  613 | SYS_INIT(disk_flash_init, POST_KERNEL, CONFIG_KERNEL_INIT_PRIORITY_DEFAULT);
      | ^~~~~~~~
/opt/nordic/ncs/v3.0.0/zephyr/include/zephyr/init.h:141:44: error: section attribute not allowed for '__init_disk_flash_init'
  141 | #define Z_INIT_ENTRY_NAME(init_id) _CONCAT(__init_, init_id)
      |                                            ^~~~~~~
/opt/nordic/ncs/v3.0.0/zephyr/include/zephyr/toolchain/common.h:137:26: note: in definition of macro '_DO_CONCAT'
  137 | #define _DO_CONCAT(x, y) x ## y
      |                          ^
/opt/nordic/ncs/v3.0.0/zephyr/include/zephyr/init.h:141:36: note: in expansion of macro '_CONCAT'
  141 | #define Z_INIT_ENTRY_NAME(init_id) _CONCAT(__init_, init_id)
      |                                    ^~~~~~~
/opt/nordic/ncs/v3.0.0/zephyr/include/zephyr/init.h:241:17: note: in expansion of macro 'Z_INIT_ENTRY_NAME'
  241 |                 Z_INIT_ENTRY_NAME(name) = {.init_fn = {.sys = (init_fn_)},                \
      |                 ^~~~~~~~~~~~~~~~~
/opt/nordic/ncs/v3.0.0/zephyr/include/zephyr/init.h:223:9: note: in expansion of macro 'SYS_INIT_NAMED'
  223 |         SYS_INIT_NAMED(init_fn, init_fn, level, prio)
      |         ^~~~~~~~~~~~~~
/opt/nordic/ncs/v3.0.0/zephyr/drivers/disk/flashdisk.c:613:1: note: in expansion of macro 'SYS_INIT'
  613 | SYS_INIT(disk_flash_init, POST_KERNEL, CONFIG_KERNEL_INIT_PRIORITY_DEFAULT);
      | ^~~~~~~~
/opt/nordic/ncs/v3.0.0/zephyr/include/zephyr/init.h:239:42: warning: 'used' attribute ignored [-Wattributes]
  239 |         static const Z_DECL_ALIGN(struct init_entry)                                      \
      |                                          ^~~~~~~~~~
/opt/nordic/ncs/v3.0.0/zephyr/include/zephyr/toolchain/common.h:195:55: note: in definition of macro 'Z_DECL_ALIGN'
  195 | #define Z_DECL_ALIGN(type) __aligned(__alignof(type)) type
      |                                                       ^~~~
/opt/nordic/ncs/v3.0.0/zephyr/include/zephyr/init.h:223:9: note: in expansion of macro 'SYS_INIT_NAMED'
  223 |         SYS_INIT_NAMED(init_fn, init_fn, level, prio)
      |         ^~~~~~~~~~~~~~
/opt/nordic/ncs/v3.0.0/zephyr/drivers/disk/flashdisk.c:613:1: note: in expansion of macro 'SYS_INIT'
  613 | SYS_INIT(disk_flash_init, POST_KERNEL, CONFIG_KERNEL_INIT_PRIORITY_DEFAULT);
      | ^~~~~~~~
/opt/nordic/ncs/v3.0.0/zephyr/include/zephyr/init.h:141:44: error: alignment may not be specified for '__init_disk_flash_init'
  141 | #define Z_INIT_ENTRY_NAME(init_id) _CONCAT(__init_, init_id)
      |                                            ^~~~~~~
/opt/nordic/ncs/v3.0.0/zephyr/include/zephyr/toolchain/common.h:137:26: note: in definition of macro '_DO_CONCAT'
  137 | #define _DO_CONCAT(x, y) x ## y
      |                          ^
/opt/nordic/ncs/v3.0.0/zephyr/include/zephyr/init.h:141:36: note: in expansion of macro '_CONCAT'
  141 | #define Z_INIT_ENTRY_NAME(init_id) _CONCAT(__init_, init_id)
      |                                    ^~~~~~~
/opt/nordic/ncs/v3.0.0/zephyr/include/zephyr/init.h:241:17: note: in expansion of macro 'Z_INIT_ENTRY_NAME'
  241 |                 Z_INIT_ENTRY_NAME(name) = {.init_fn = {.sys = (init_fn_)},                \
      |                 ^~~~~~~~~~~~~~~~~
/opt/nordic/ncs/v3.0.0/zephyr/include/zephyr/init.h:223:9: note: in expansion of macro 'SYS_INIT_NAMED'
  223 |         SYS_INIT_NAMED(init_fn, init_fn, level, prio)
      |         ^~~~~~~~~~~~~~
/opt/nordic/ncs/v3.0.0/zephyr/drivers/disk/flashdisk.c:613:1: note: in expansion of macro 'SYS_INIT'
  613 | SYS_INIT(disk_flash_init, POST_KERNEL, CONFIG_KERNEL_INIT_PRIORITY_DEFAULT);
      | ^~~~~~~~
In file included from /opt/nordic/ncs/v3.0.0/zephyr/include/zephyr/device.h:13,
                 from /opt/nordic/ncs/v3.0.0/zephyr/include/zephyr/sw_isr_table.h:18,
                 from /opt/nordic/ncs/v3.0.0/zephyr/include/zephyr/arch/arm/irq.h:19,
                 from /opt/nordic/ncs/v3.0.0/zephyr/include/zephyr/arch/arm/arch.h:24,
                 from /opt/nordic/ncs/v3.0.0/zephyr/include/zephyr/arch/cpu.h:19,
                 from /opt/nordic/ncs/v3.0.0/zephyr/include/zephyr/kernel_includes.h:36,
                 from /opt/nordic/ncs/v3.0.0/zephyr/include/zephyr/kernel.h:17,
                 from /opt/nordic/ncs/v3.0.0/zephyr/include/zephyr/drivers/disk.h:30,
                 from /opt/nordic/ncs/v3.0.0/zephyr/drivers/disk/flashdisk.c:12:
/opt/nordic/ncs/v3.0.0/zephyr/drivers/disk/flashdisk.c:613:10: error: 'disk_flash_init' undeclared (first use in this function)
  613 | SYS_INIT(disk_flash_init, POST_KERNEL, CONFIG_KERNEL_INIT_PRIORITY_DEFAULT);
      |          ^~~~~~~~~~~~~~~
/opt/nordic/ncs/v3.0.0/zephyr/include/zephyr/init.h:241:64: note: in definition of macro 'SYS_INIT_NAMED'
  241 |                 Z_INIT_ENTRY_NAME(name) = {.init_fn = {.sys = (init_fn_)},                \
      |                                                                ^~~~~~~~
/opt/nordic/ncs/v3.0.0/zephyr/drivers/disk/flashdisk.c:613:1: note: in expansion of macro 'SYS_INIT'
  613 | SYS_INIT(disk_flash_init, POST_KERNEL, CONFIG_KERNEL_INIT_PRIORITY_DEFAULT);
      | ^~~~~~~~
/opt/nordic/ncs/v3.0.0/zephyr/drivers/disk/flashdisk.c:533:1: error: type of 'DEFINE_FLASHDISKS_CACHE' defaults to 'int' [-Werror=implicit-int]
  533 | PM_FOREACH_AFFILIATED_TO_disk(DEFINE_FLASHDISKS_CACHE)
      | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/opt/nordic/ncs/v3.0.0/zephyr/include/zephyr/init.h:141:44: error: declaration for parameter '__init_disk_flash_init' but no such parameter
  141 | #define Z_INIT_ENTRY_NAME(init_id) _CONCAT(__init_, init_id)
      |                                            ^~~~~~~
/opt/nordic/ncs/v3.0.0/zephyr/include/zephyr/toolchain/common.h:137:26: note: in definition of macro '_DO_CONCAT'
  137 | #define _DO_CONCAT(x, y) x ## y
      |                          ^
/opt/nordic/ncs/v3.0.0/zephyr/include/zephyr/init.h:141:36: note: in expansion of macro '_CONCAT'
  141 | #define Z_INIT_ENTRY_NAME(init_id) _CONCAT(__init_, init_id)
      |                                    ^~~~~~~
/opt/nordic/ncs/v3.0.0/zephyr/include/zephyr/init.h:241:17: note: in expansion of macro 'Z_INIT_ENTRY_NAME'
  241 |                 Z_INIT_ENTRY_NAME(name) = {.init_fn = {.sys = (init_fn_)},                \
      |                 ^~~~~~~~~~~~~~~~~
/opt/nordic/ncs/v3.0.0/zephyr/include/zephyr/init.h:223:9: note: in expansion of macro 'SYS_INIT_NAMED'
  223 |         SYS_INIT_NAMED(init_fn, init_fn, level, prio)
      |         ^~~~~~~~~~~~~~
/opt/nordic/ncs/v3.0.0/zephyr/drivers/disk/flashdisk.c:613:1: note: in expansion of macro 'SYS_INIT'
  613 | SYS_INIT(disk_flash_init, POST_KERNEL, CONFIG_KERNEL_INIT_PRIORITY_DEFAULT);
      | ^~~~~~~~
/opt/nordic/ncs/v3.0.0/zephyr/drivers/disk/flashdisk.c:572:30: error: declaration for parameter 'flash_disks' but no such parameter
  572 | static struct flashdisk_data flash_disks[] = {
      |                              ^~~~~~~~~~~
/opt/nordic/ncs/v3.0.0/zephyr/drivers/disk/flashdisk.c:614: error: expected '{' at end of input
/opt/nordic/ncs/v3.0.0/zephyr/drivers/disk/flashdisk.c:614: warning: control reaches end of non-void function [-Wreturn-type]
/opt/nordic/ncs/v3.0.0/zephyr/drivers/disk/flashdisk.c: At top level:
/opt/nordic/ncs/v3.0.0/zephyr/drivers/disk/flashdisk.c:464:37: warning: 'flash_disk_ops' defined but not used [-Wunused-const-variable=]
  464 | static const struct disk_operations flash_disk_ops = {
      |                                     ^~~~~~~~~~~~~~
cc1: some warnings being treated as errors
[99/206] Building C object zephyr/drivers/usb/device/CMakeFiles/drivers__usb__device.dir/usb_dc_nrfx.c.obj
ninja: build stopped: subcommand failed.
FAILED: _sysbuild/sysbuild/images/mass-prefix/src/mass-stamp/mass-build /opt/nordic/ncs/v3.0.0/zephyr/samples/subsys/usb/mass/build/_sysbuild/sysbuild/images/mass-prefix/src/mass-stamp/mass-build
cd /opt/nordic/ncs/v3.0.0/zephyr/samples/subsys/usb/mass/build/mass && /opt/homebrew/bin/cmake --build .
ninja: build stopped: subcommand failed.
FATAL ERROR: re-build in /opt/nordic/ncs/v3.0.0/zephyr/samples/subsys/usb/mass/build failed (no --build-dir given)

I then enabled my pm_static.yml:

storage_partition:
  address: 0x0
  end_address: 0x800000
  device: MX25R64
  region: external_flash
  size: 0x800000
  affiliation: disk
  extra_params:
    disk_name: "ZEPHYR"
    disk_cache_size: 4096
    disk_sector_size: 512
    disk_read_only: 0
  placement:
    before:
      - end

But still that generated no positive result:

[00:00:00.439,331] <inf> spi_nor: mx25r6435f@0: 8 MiBy flash
*** Booting nRF Connect SDK v3.0.0-3bfc46578e42 ***
*** Using Zephyr OS v4.0.99-a0e545cb437a ***
[00:00:00.441,711] <inf> flashdisk: Initialize device ZEPHYR
[00:00:00.441,711] <inf> flashdisk: offset 0, sector size 512, page size 4096, volume size 8388608
Area 6 at 0xfc000 on flash-controller@39000 for 8192 bytes
[00:00:00.445,343] <err> fs: fs mount error (-5)
[00:00:00.445,343] <err> main: Failed to mount filesystem
[00:00:00.445,587] <inf> main: The device is put in USB mass storage mode.

The disk exposed towards MacOS is just like the disk created with LittleFS: disk is 8Mb, visible, inaccessible, unformattable, and Zephyr is still pointing towards the internal memory.

In the meantime, I discovered the command:

west build -t partition_manager_report

Which yields some interesting information:

root@admins-MacBook-Air-2 mass # west build -t partition_manager_report
-- west build: running target partition_manager_report
[1/1] cd /opt/nordic/ncs/v3.0.0/zephyr/samples/subsys/usb/mass/build/_sysbuild && /opt/homebrew/opt/py...n_manager_report.py --input /opt/nordic/ncs/v3.0.0/zephyr/samples/subsys/usb/mass/build/partitions.yml
  external_flash (0x800000 - 8192kB):
+--------------------------------------------+
| 0x0: storage_partition (0x800000 - 8192kB) |
| 0x800000: external_flash (0x0 - 0B)        |
+--------------------------------------------+

  flash_primary (0x100000 - 1024kB):
+---------------------------------------------+
+---0x0: tfm_secure (0x8000 - 32kB)-----------+
| 0x0: tfm (0x8000 - 32kB)                    |
+---0x8000: tfm_nonsecure (0xf4000 - 976kB)---+
| 0x8000: app (0xf4000 - 976kB)               |
+---0xfc000: nonsecure_storage (0x2000 - 8kB)-+
| 0xfc000: settings_storage (0x2000 - 8kB)    |
+---------------------------------------------+
| 0xfe000: EMPTY_0 (0x2000 - 8kB)             |
+---------------------------------------------+

  otp (0x2fc - 764B):
+------------------------------+
| 0xff8100: otp (0x2fc - 764B) |
+------------------------------+

  sram_primary (0x80000 - 512kB):
+------------------------------------------------+
+---0x20000000: sram_secure (0x8000 - 32kB)------+
| 0x20000000: tfm_sram (0x8000 - 32kB)           |
+---0x20008000: sram_nonsecure (0x78000 - 480kB)-+
| 0x20008000: sram_primary (0x68000 - 416kB)     |
| 0x20070000: rpmsg_nrf53_sram (0x10000 - 64kB)  |
+------------------------------------------------+

Based on the partition_manager_report and the board's bootup log, the area allocated as the external storage is:

+---0xfc000: nonsecure_storage (0x2000 - 8kB)-+
| 0xfc000: settings_storage (0x2000 - 8kB)    |

Which is very strange and completely out of sync with the mx25r64.

I then decided that probably I did something wrong, so I went 100% with the example and built for the adafruit_feather_nrf52840_sense. Sadly, the results were even worse:

root@admins-MacBook-Air-2 mass # west build -b adafruit_feather_nrf52840_sense -- -DCONFIG_APP_MSC_STORAGE_FLASH_FATFS=y
-- west build: generating a build system
Loading Zephyr module(s) (Zephyr base): sysbuild_default
-- Found Python3: /opt/homebrew/opt/python@3.13/bin/python3.13 (found suitable version "3.13.3", minimum required is "3.10") found components: Interpreter
-- Cache files will be written to: /Users/tudor/Library/Caches/zephyr
-- Found west (found suitable version "1.3.0", minimum required is "0.14.0")
No board named 'adafruit_feather_nrf52840_sense' found.

Please choose one of the following boards:

thingy91
nrf7120pdk
nrf52kbd
thingy91x
nrf52833dongle
nrf52840gmouse
nrf54lm20apdk
nrf54lv10apdk
nrf52820dongle
nrf52dmouse
samr34_xpro
samc21n_xpro
same54_xpro
saml21_xpro
samd21_xpro
samd20_xpro
samr21_xpro
sam_e70_xplained
sam_v71_xult
sam4l_ek
sam4s_xplained
sam4e_xpro
wio_terminal
lora_e5_mini
xiao_esp32c3
lora_e5_dev_board
xiao_ble
xiao_rp2040
xiao_esp32c6
xiao_esp32s3
seeeduino_xiao
mercury_xu
cc26x2r1_launchxl
cc3220sf_launchxl
cc1352p1_launchxl
cc1352p7_lp
msp_exp432p401r_launchxl
sk_am62
cc3235sf_launchxl
cc1352r1_launchxl
cc1352r_sensortag
robokit1
acrn
acrn_ehl_crb
gr716a_mini
generic_leon3
rpi_5
rpi_4b
rpi_pico
rpi_pico2
pan1770_evb
pan1783_evb
pan1783a_evb
pan1783a_pa_evb
pan1781_evb
pan1780_evb
pan1782_evb
rv32m1_vega
esp32_ethernet_kit
esp32_devkitc_wrover
esp8684_devkitm
esp32c3_devkitm
esp32c3_devkitc
esp_wrover_kit
esp32c3_rust
esp32s2_saola
esp32s3_devkitc
esp32c6_devkitc
esp32s3_devkitm
esp32_devkitc_wroom
esp32s2_devkitc
esp32s3_eye
contextualelectronics_abc
odroid_go
da1469x_dk_pro
ek_ra4w1
rcar_salvator_xs
rcar_h3ulcb
rcar_spider_s4
ek_ra6e2
ek_ra6m1
ek_ra4m2
ek_ra8d1
ek_ra8m1
fpb_ra6e2
ek_ra4m3
da14695_dk_usb
ek_ra4e2
rzg3s_smarc
rzt2m_starter_kit
ek_ra6m5
ek_ra6m2
mck_ra8t1
ek_ra2a1
ek_ra6m3
ek_ra6m4
fpb_ra6e1
rcar_salvator_x
particle_xenon
nrf52_blenano2
particle_argon
nrf51_blenano
particle_boron
esp32c3_luatos_core
esp32s3_luatos_core
tlsr9518adk80d
az3166_iotdevkit
it8xxx2_evb
it82xx2_evb
pinetime_devkit0
weact_stm32g431_core
mini_stm32h743
usb2canfdv1
blackpill_f401cc
blackpill_f401ce
blackpill_f411ce
weact_stm32f405_core
mini_stm32h7b0
bcm958402m2
bcm958401m2
esp32s2_lolin_mini
slstk3401a
slstk3402a
slstk3701a
slstk3400a
efm32wg_stk3800
xg24_ek2703a
xg24_dk2601b
sltb004a
sltb009a
sltb010a
xg27_dk2602a
sim3u1xx_dk
xg23_rb4210a
slwrb4161a
slwrb4104a
slwrb4170a
slwrb4321a
xg24_rb4187c
slwrb4255a
slwrb4250b
slwrb4180a
v2m_beetle
fvp_base_revc_2xaemv8a
v2m_musca_b1
v2m_musca_s1
fvp_baser_aemv8r
mps3
mps2
acn52832
ucan
cyw920829m2evk_02
xmc45_relax_kit
cy8cproto_063_ble
cy8ckit_062s2_ai
cy8cproto_062_4343w
xmc47_relax_kit
cy8ckit_062s4
cortex_r8_virtual
riscv32_virtual
adafruit_itsybitsy
adafruit_feather_m0_basic_proto
adafruit_feather_m4_express
adafruit_feather_m0_lora
adafruit_trinket_m0
adafruit_kb2040
adafruit_feather_nrf52840
nrf52_adafruit_feather
adafruit_itsybitsy_m4_express
adafruit_qt_py_rp2040
adafruit_qt_py_esp32s3
adafruit_grand_central_m4_express
adafruit_feather_stm32f405
sgrm
nrf52_sparkfun
sparkfun_thing_plus_matter_mgm240p
micromod
sparkfun_thing_plus
sparkfun_red_v_things_plus
sparkfun_pro_micro_rp2040
gd32vf103v_eval
gd32vf103c_starter
gd32e507v_start
gd32e103v_eval
gd32a503v_eval
gd32f403z_eval
gd32f450i_eval
gd32f470i_eval
gd32f407v_start
gd32e507z_eval
gd32f450z_eval
gd32f350r_eval
gd32l233r_eval
gd32f450v_start
ast1030_evb
ip_k66f
segger_trb_stm32f407
altera_max10
blueclover_plt_demo_v2
nrf52840_blip
nrf52840_papyr
w5500_evb_pico
npcx7m6fb_evb
npcm400_evb
numaker_pfm_m467
npcx9m6f_evb
numaker_m2l31ki
npcx4m8f_evb
numaker_pfm_m487
nrf51_vbluno51
nrf52_vbluno52
up_squared
up_squared_pro_7000
qemu_kvm_arm64
qemu_riscv64
qemu_riscv32_xip
qemu_xtensa
qemu_cortex_m3
qemu_cortex_a9
qemu_riscv32e
qemu_cortex_r5
qemu_cortex_a53
qemu_riscv32
qemu_x86
qemu_x86_lakemont
qemu_x86_64
qemu_x86_tiny
qemu_cortex_m0
qemu_leon3
qemu_malta
qemu_arc
qemu_nios2
waveshare_open103z
nrf51_ble400
rp2040_zero
esp32s3_touch_lcd_1_28
dragino_nbsn95
dragino_lsn50
teensy40
teensy41
mec172xevb_assy6906
mpfs_icicle
m2gl025_miv
mec1501modular_assy6885
mec172xmodular_assy6930
mec15xxevb_assy6853
ev11l78a
kb1200_evb
apollo3_evb
apollo4p_blue_kxr_evb
apollo4p_evb
apollo3p_evb
m5stack_atoms3_lite
m5stack_atoms3
m5stack_core2
m5stack_cores3
m5stack_atom_lite
m5stack_stamps3
stamp_c3
m5stickc_plus
ganymed_bob
udoo_neo_full
pico_pi
arduino_nicla_sense_me
arduino_nicla_vision
arduino_portenta_h7
arduino_due
arduino_nano_33_ble
arduino_zero
arduino_opta
arduino_giga_r1
arduino_mkrzero
arduino_nano_33_iot
arduino_uno_r4_minima
arduino_uno_r4_wifi
ruuvi_ruuvitag
esp32s2_franzininho
acp_6_0_adsp
kv260_r5
mm_feather
mm_swiftio
mks_canable_v20
nucleo_l4r5zi
nucleo_f031k6
nucleo_f030r8
nucleo_f334r8
stm32l496g_disco
nucleo_l011k4
b_g474e_dpow1
stm32f413h_disco
stm32f7508_dk
nucleo_f091rc
stm32u083c_dk
nucleo_l073rz
stm32f746g_disco
stm32f072_eval
nucleo_f103rb
nucleo_h533re
stm32h573i_dk
stm32f072b_disco
nucleo_f446ze
stm32f769i_disco
stm32wb5mm_dk
nucleo_l4a6zg
nucleo_g031k8
nucleo_f303re
stm32f412g_disco
stm32f429i_disc1
nucleo_l031k6
nucleo_g431rb
nucleo_f413zh
nucleo_wb09ke
sensortile_box
stm32mp157c_dk2
nucleo_c031c6
stm32c0116_dk
nucleo_wb05kz
steval_stwinbx1
nucleo_l496zg
nucleo_f207zg
sensortile_box_pro
stm32f723e_disco
nucleo_l552ze_q
nucleo_g071rb
stm32wb5mmg
nucleo_h7a3zi_q
stm32373c_eval
nucleo_f410rb
nucleo_h563zi
nucleo_f303k8
nucleo_h723zg
nucleo_f302r8
nucleo_l433rc_p
nucleo_l412rb_p
nucleo_h7s3l8
nucleo_g431kb
nucleo_l152re
nucleo_u575zi_q
stm32l476g_disco
stm32f469i_disco
stm32g0316_disco
stm32h745i_disco
stm32f411e_disco
nucleo_g474re
nucleo_f756zg
nucleo_h753zi
stm32h7s78_dk
nucleo_f412zg
nucleo_f070rb
nucleo_h745zi_q
st25dv_mb1283_disco
nucleo_f401re
stm32h750b_dk
nucleo_u031r8
nucleo_l432kc
nucleo_f411re
nucleo_wb55rg
nucleo_h755zi_q
nucleo_f767zi
nucleo_g070rb
steval_fcu001v1
stm32f3_disco
nucleo_l452re
nucleo_g0b1re
nucleo_f429zi
nucleo_f042k6
disco_l475_iot1
stm32h747i_disco
nucleo_f746zg
nucleo_wba52cg
nucleo_h743zi
stm32f4_disco
stm32l4r9i_disco
nucleo_h503rb
stm32g071b_disco
stm32u5a9j_dk
nucleo_l053r8
b_l072z_lrwan1
stm32vl_disco
stm3210c_eval
nucleo_f446re
nucleo_l476rg
nucleo_u5a5zj_q
stm32h7b3i_dk
nucleo_wba55cg
b_u585i_iot02a
stm32l562e_dk
stm32l1_disco
stm32l152c_disco
nucleo_u083rc
stm32h735g_disco
nucleo_c071rb
stm32f0_disco
b_l4s5i_iot01a
nucleo_wl55jc
nucleo_f722ze
stm32g081b_eval
khadas_edgev
quick_feather
qomu
heltec_wireless_stick_lite_v3
heltec_wifi_lora32_v2
legend
faze
walter
we_proteus2ev
we_ophelia1ev
we_orthosie1ev
we_proteus3ev
mt8195
mt8186
mt8188
mt8196
adp_xc7k
beaglebone_ai64
beaglev_fire
beagleconnect_freedom
beagleplay
promicro_nrf52840
candlelightfd
stm32f103_mini
stm32f030_demo
candlelight
stm32f401_mini
icev_wireless
stm32_min_dev
esp32c3_supermini
neorv32
serpente
black_f407zg_pro
black_f407ve
nrf52840_mdk_usb_dongle
nrf52840_mdk
nrf52832_mdk
circuitdojo_feather
visionfive2
raytac_mdbt50q_db_33
raytac_mdbt53v_db_40
raytac_mdbt53_db_40
raytac_mdbt50q_db_40
litex_vexriscv
croxel_cx1825
pandora_stm32l475
fk7b0m1_vbt6
fk750m1_vbt6
96b_meerkat96
96b_neonkey
96b_carbon
96b_argonkey
96b_nitrogen
96b_aerocore2
96b_stm32_sensor_mez
96b_wistrio
96b_avenger96
ctcc
titanium_ti60_f225
warp7
rak11720
rak5010
rak4631
ch32v003evt
mikroe_stm32_m4_clicker
mikroe_mini_m4_for_stm32
mikroe_clicker_ra4m1
mikroe_clicker_2
verdin_imx8mp
verdin_imx8mm
colibri_imx7d
swan_r5
google_twinkie_v2
google_icetower
google_dragonclaw
bytesensi_l
bbc_microbit
bbc_microbit_v2
ubx_bmd360eval
ubx_evkannab1
ubx_bmd300eval
ubx_evkninab4
ubx_evkninab3
ubx_bmd330eval
ubx_bmd380eval
ubx_bmd340eval
ubx_evkninab1
ubx_bmd345eval
opentitan_earlgrey
ronoth_lodev
ttgo_t8c3
ttgo_t7v1_5
ttgo_t8s3
ttgo_lora32
innblue21
innblue22
mg100
bt610
bl654_usb
bt510
bl653_dvk
bl652_dvk
bl5340_dvk
bl654_dvk
rm1xx_dvk
pinnacle_100_dvk
bl654_sensor_board
actinius_icarus
actinius_icarus_som_dk
actinius_icarus_bee
actinius_icarus_som
hifive1
hifive_unmatched
hifive_unleashed
native_sim
native_posix
nrf52_bsim
nrf5340bsim
nrf54l15bsim
xt-sim
holyiot_yj16019
zybo
arty_a7
cy8ckit_062_wifi_bt
cy8ckit_062_ble
yd_stm32h750vb
yd_esp32
longan_nano
imx8mm_evk
mimxrt1020_evk
ucans32k1sic
frdm_k22f
lpcxpresso51u68
frdm_k82f
lpcxpresso55s36
mimxrt1180_evk
vmu_rt1170
imx8mn_evk
twr_ke18f
lpcxpresso55s06
frdm_kl25z
frdm_kw41z
frdm_ke17z
frdm_mcxc444
lpcxpresso11u68
mimxrt1024_evk
imx95_evk
rddrone_fmuk66
twr_kv58f220m
lpcxpresso54114
frdm_mcxa156
usb_kw24d512
mimxrt1040_evk
frdm_mcxn947
frdm_ke17z512
imx93_evk
mimxrt1050_evk
mimxrt1062_fmurt6
frdm_k64f
s32z2xxdc2
mimxrt1060_evk
mimxrt595_evk
lpcxpresso55s69
imx8qxp_mek
mimxrt1064_evk
frdm_mcxc242
frdm_rw612
mimxrt1015_evk
mimxrt1160_evk
frdm_ke15z
imx8mp_evk
imx8mq_evk
ls1046ardb
frdm_mcxw71
hexiwear
mr_canhubk3
rd_rw612_bga
lpcxpresso55s16
frdm_mcxn236
mimxrt685_evk
imx8ulp_evk
mimxrt1170_evk
mimxrt1010_evk
imx8qm_mek
lpcxpresso55s28
reel_board
phyboard_pollux
phyboard_polis
phyboard_electra
phyboard_nash
phyboard_lyra
kincony_kc868_a32
linum
apard32690
max32672fthr
max32666fthr
max32672evkit
max32690evkit
max32662evkit
max32655evkit
max32680evkit
max32675evkit
max78002evkit
adi_eval_adin2111ebz
max32690fthr
adi_eval_adin1110ebz
max32666evkit
adi_sdp_k1
max32670evkit
max32655fthr
olimex_stm32_h103
olimexino_stm32
olimex_stm32_h407
olimex_lora_stm32wl_devkit
olimex_esp32_evb
olimex_stm32_h405
olimex_stm32_p405
olimex_stm32_e407
hsdk
hsdk4xd
emsdp
iotdk
em_starterkit
nsim
nsim_arc_v
scobc_module1
octopus_io_board
octopus_som
degu_evk
stm32f3_seco_d23
xenvm
ebyte_e73_tbb
thingy52
nrf52833dk
nrf54l15dk
nrf54h20dk
thingy53
nrf5340_audio_dk
nrf52dk
nrf9151dk
nrf54l20pdk
nrf9160dk
nrf51dk
nrf9131ek
nrf9161dk
nrf52840dk
nrf5340dk
nrf52840dongle
nrf21540dk
nrf51dongle
nrf9280pdk
nrf54l09pdk
nrf7002dk
intel_ehl_crb
intel_ish_5_4_1
intel_ish_5_6_0
intel_ish_5_8_0
niosv_m
intel_adl_crb
intel_adl_rvp
niosv_g
intel_adsp
intel_rpl_p_crb
intel_rpl_s_crb
cyclonev_socdk
intel_socfpga_agilex_socdk
intel_socfpga_agilex5_socdk
decawave_dwm1001_dev
decawave_dwm3001cdk
roc_rk3568_pc
rts5912_evb
esp32c3_042_oled
CMake Error at /opt/nordic/ncs/v3.0.0/zephyr/cmake/modules/boards.cmake:228 (message):
  Invalid BOARD; see above.
Call Stack (most recent call first):
  cmake/modules/sysbuild_default.cmake:15 (include)
  /opt/nordic/ncs/v3.0.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:75 (include)
  /opt/nordic/ncs/v3.0.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:92 (include_boilerplate)
  /opt/nordic/ncs/v3.0.0/zephyr/share/sysbuild-package/cmake/SysbuildConfig.cmake:8 (include)
  template/CMakeLists.txt:10 (find_package)


-- Configuring incomplete, errors occurred!
FATAL ERROR: command exited with status 1: /opt/homebrew/bin/cmake -DWEST_PYTHON=/opt/homebrew/opt/python@3.13/bin/python3.13 -B/opt/nordic/ncs/v3.0.0/zephyr/samples/subsys/usb/mass/build -GNinja -DBOARD=adafruit_feather_nrf52840_sense -DCONFIG_APP_MSC_STORAGE_FLASH_FATFS=y -S/opt/nordic/ncs/v3.0.0/zephyr/share/sysbuild -DAPP_DIR:PATH=/opt/nordic/ncs/v3.0.0/zephyr/samples/subsys/usb/mass

which I suspect is because there's no *.dts for that board configuration.

My main suspicion is that both the How To from the link and the mass storage sample itself are simply outdated. Main reason for this conclusion is the huge discrepancy between the Zephyr OS reported in the sample (*** Booting Zephyr OS build zephyr-v2.3.0-1991-g4c8d1496eafb ***) and the Zephyr OS reported when I flashed the board (*** Using Zephyr OS v4.0.99-a0e545cb437a ***).

Could you please prepare a working usb mass storage sample code for the nrf7002dk board that works out of the box for ncs v3.0.0 sdk and add it here as an archive?

In parallel I'll keep tinkering with it. I think the partition_manager_report will be the key to finding a solution!

RE: USB mass storage for the NRF7002DK development board using on board chip

Tudor B. — Fri, 11 Jul 2025 16:43:33 GMT

That aside, if you have a proposal that combats LFS for both FS and USB Mass Storage, then I can present your argument to my superiors and maybe we can switch to something that's much easier to set up and just as good. 😉😁