zephyr/tests/fs/fat_fs
Anas Nashif 66cfcc26bc tests: introduce Makefile.test
To customise test builds and support test related features such as time
stamps and a boot banner, introduce a Makefile variant that is dedicated
to testing.

Initially we introduce a new config overlay that is used for all tests, in
this case we enable BOOT_BANNER and BUILD_TIMESTAMP. This will print the
current version and the date, useful when reporting bugs and also an
indicator that the system has booted before the test has started.

For example:

[QEMU] CPU: qemu32
***** BOOTING ZEPHYR OS v1.6.99 - BUILD: Dec 21 2016 19:57:13 *****
tc_start() - Test Nanokernel CPU and thread routines
Initializing nanokernel objects
...
..

Change-Id: I224318cdeb55a301964ea366dbc577e2e3a09175
Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2017-01-03 17:48:44 +00:00
..
src
Makefile tests: introduce Makefile.test 2017-01-03 17:48:44 +00:00
README.txt
prj.conf fs: expose generic ramdisk/flash disk access functions 2016-11-09 02:45:45 +00:00
testcase.ini samples: tests: remove obsolete KERNEL_TYPE and kernel variables 2016-11-04 15:47:25 -04:00

README.txt

Title: Zephyr File System Demo

Description:

Demonstrates basic file and dir operations using the Zephyr file system.
--------------------------------------------------------------------------------

Building and Running Project:

The demo will run on Arduino 101 and will use the on-board SPI flash.

    make BOARD=arduino_101

--------------------------------------------------------------------------------

Troubleshooting:

Problems caused by out-dated project information can be addressed by
issuing one of the following commands then rebuilding the project:

    make clean          # discard results of previous builds
                        # but keep existing configuration info
or
    make pristine       # discard results of previous builds
                        # and restore pre-defined configuration info

--------------------------------------------------------------------------------

Sample Output:

File System Demo!

Creating new file testfile.txt
Opened file testfile.txt
Data successfully written!
Data written:"hello world!"

Data successfully read!
Data read:"hello world!"

Data read matches data written!

Truncate tests:
Testing shrink to 0 size
Testing write after truncating
Data successfully written!
Data written:"hello world!"

Original size of file = 12
File size after shrinking by 5 bytes = 7
Check original contents after shrinking file
Data successfully read!
Data read:"hello w"

File size after expanding by 10 bytes = 17
Check original contents after expanding file
Data successfully read!
Data read:"hello w"

Testing for zeroes in expanded region
Closed file testfile.txt
File (testfile.txt) deleted successfully!
Created dir sub1!
Creating new file testfile.txt
Opened file testfile.txt
Creating new file sub1/testfile.txt
Opened file sub1/testfile.txt
Data successfully written!
Data written:"1"

Data successfully written!
Data written:"12"

Closed file testfile.txt
Closed file sub1/testfile.txt

Listing dir /:
[DIR ] SUB1
[FILE] TESTFILE.TXT (size = 1)

Listing dir sub1:
[FILE] TESTFILE.TXT (size = 2)

Removing files and sub directories in sub1
Removing sub1/TESTFILE.TXT
Removed dir sub1!

Optimal transfer block size   = 512
Allocation unit size          = 512
Volume size in f_frsize units = 152
Free space in f_frsize units  = 151