nuttx-apps/testing/smart
2019-10-17 11:33:59 -06:00
..
.gitignore testing/: Move all file system tests from examples/ to testing/ (fstest, nxffs, smart, smart_test). 2019-01-24 14:44:54 -06:00
Kconfig testing/: Move all file system tests from examples/ to testing/ (fstest, nxffs, smart, smart_test). 2019-01-24 14:44:54 -06:00
Make.defs apps/: In all Make.def files, append to CONFIGURED_APPS patch with the absolute path. 2019-10-17 11:33:59 -06:00
Makefile Makefiles: This reverts part of commit cf0365ea9. It restores 'conditional' inclusion of TOPDIR/Make.defs. Otherwise all make targets fail if the board has not been configured. That is okay most of the time, but not for things like clean and distclean which should not depend on being configured. 2019-10-15 09:25:48 +08:00
README.txt testing/: Move all file system tests from examples/ to testing/ (fstest, nxffs, smart, smart_test). 2019-01-24 14:44:54 -06:00
smart_main.c Application.mk and main.c files: Change builtin's entry point from main to xxx_main by macro expansion. This change make the entry point fully compliant with POSIX/ANSI standard. 2019-10-06 06:14:56 -06:00

README
======

  This is a test of the SMART file system that derives from
  testing/nxffs.

  * CONFIG_TESTING_SMART: - Enable the SMART file system example
  * CONFIG_TESTING_SMART_ARCHINIT: The default is to use the RAM MTD
    device at drivers/mtd/rammtd.c.  But an architecture-specific MTD
    driver can be used instead by defining CONFIG_TESTING_SMART_ARCHINIT.  In
    this case, the initialization logic will call smart_archinitialize()
    to obtain the MTD driver instance.
  * CONFIG_TESTING_SMART_NEBLOCKS: When CONFIG_TESTING_SMART_ARCHINIT is not
    defined, this test will use the RAM MTD device at drivers/mtd/rammtd.c
    to simulate FLASH.  In this case, this value must be provided to give
    the nubmer of erase blocks in MTD RAM device.  The size of the allocated
    RAM drive will be: CONFIG_RAMMTD_ERASESIZE * CONFIG_TESTING_SMART_NEBLOCKS
  * CONFIG_TESTING_SMART_MAXNAME: Determines the maximum size of names used
    in the filesystem
  * CONFIG_TESTING_SMART_MAXFILE: Determines the maximum size of a file
  * CONFIG_TESTING_SMART_MAXIO: Max I/O, default 347.
  * CONFIG_TESTING_SMART_MAXOPEN: Max open files.
  * CONFIG_TESTING_SMART_MOUNTPT: SMART mountpoint
  * CONFIG_TESTING_SMART_NLOOPS: Number of test loops. default 100
  * CONFIG_TESTING_SMART_VERBOSE: Verbose output