sergiotarxz/nuttx-apps
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
c6b678fa60
nuttx-apps/testing/smart
History
YAMAMOTO Takashi c304624fab Replace "STACKSIZE = 2048" with CONFIG_DEFAULT_TASK_SIZE 
For now, I left the following instances because it isn't
clear to me why they are using the different values.
Maybe they need one-by-one inspection.

    examples/igmp/Makefile:STACKSIZE = 1024
    examples/powerled/Makefile:STACKSIZE = 1024
    examples/powermonitor/Makefile:STACKSIZE = 768
    examples/relays/Makefile:STACKSIZE = 512
    examples/smps/Makefile:STACKSIZE = 1024
    graphics/screenshot/Makefile:STACKSIZE = 4096
    system/flash_eraseall/Makefile:STACKSIZE = 1024
    testing/cxxtest/Makefile:STACKSIZE = 4096
    testing/smart_test/Makefile:STACKSIZE = 4096
2020-03-27 02:43:11 -05:00
..
.gitignore Revert "Don't generate .depend anymore" 2020-03-22 23:09:40 -05:00
Kconfig Run codespell -w with the latest dictonary again 2020-02-23 07:10:14 -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 Replace "STACKSIZE = 2048" with CONFIG_DEFAULT_TASK_SIZE 2020-03-27 02:43:11 -05:00
README.txt Run codespell -w with the latest dictonary again 2020-02-23 07:10:14 -06:00
smart_main.c Remove extra whitespace from files (#43) 2020-01-31 08:29:24 -06:00

README.txt 

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 number 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