Skip to content

Commit fcd2f3d

Browse files
author
Deepika
committed
Sd-driver updated to 0.1.1 dependency:mbed-os-5.5.4
1 parent 38247b9 commit fcd2f3d

File tree

1 file changed

+57
-56
lines changed

1 file changed

+57
-56
lines changed

‎README.md

Lines changed: 57 additions & 56 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ Simon Hughes
55

66
20170329
77

8-
Version 0.1.0
8+
Version 0.1.1
99

1010

1111
# Executive Summary
@@ -84,16 +84,17 @@ The following versions of the mbed-os and sd-driver repositories are known to wo
8484
`K64F`, `NUCLEO_F429ZI` and `UBLOX_EVK_ODIN_W2` fopen and basic filesystem tests working.
8585
- {mbed-os, sd-driver} = {mbed-os-5.4.1, sd-driver-0.0.3-mbed-os-5.4.1}.
8686
- {mbed-os, sd-driver} = {mbed-os-5.5.1, sd-driver-0.1.0-mbed-os-5.5.1}.
87+
- {mbed-os, sd-driver} = {mbed-os-5.5.4, sd-driver-0.1.1-mbed-os-5.5.4}.
8788

8889
To find the latest compatible versions, use the following command to see the messages attached to the tags
8990
in the sd-driver repository:
9091

91-
ex_app7/$ cd sd-driver
92-
ex_app7/sd-driver$ git tag -n
93-
sd-driver-0.0.1-mbed-os-5.3.4 Version compatible with mbed-os-5.3.4, and private_mbedos_filesystems-0.0.1-mbed-os-5.3.4.
94-
sd-driver-0.0.2-mbed-os-5.4.0 Updated README.md to include worked exmaples and restructuring of information.
95-
sd-driver-0.0.3-mbed-os-5.4.1 Version compatible with mbed-os-5.4.1.
96-
sd-driver-0.1.0-mbed-os-5.5.1 Version compatible with mbed-os-5.5.1
92+
ex_app7/$ cd sd-driver
93+
ex_app7/sd-driver$ git tag -n
94+
sd-driver-0.0.1-mbed-os-5.3.4 Version compatible with mbed-os-5.3.4, and private_mbedos_filesystems-0.0.1-mbed-os-5.3.4.
95+
sd-driver-0.0.2-mbed-os-5.4.0 Updated README.md to include worked exmaples and restructuring of information.
96+
sd-driver-0.0.3-mbed-os-5.4.1 Version compatible with mbed-os-5.4.1.
97+
sd-driver-0.1.1-mbed-os-5.5.4 Version compatible with mbed-os-5.5.4
9798

9899

99100
### Known Issues With This Document
@@ -162,12 +163,12 @@ storage on SDCard:
162163
- mbed_retarget.cpp implements the libc back-end file OS handlers and maps them
163164
to the FileSystem.
164165
- The File System code (hosted in mbed-os) is composed of 2 parts:
165-
- The mbed OS file system wrapper classes (e.g. FileSystem, File, FileBase classes)
166-
which are used to present a consistent API to the retarget module for different
167-
(third-party) file system implementations.
168-
- The FAT filesystem implementation code.
169-
The [FATFS: Generic FAT File System Module](http://elm-chan.org/fsw/ff/00index_e.html)
170-
(ChanFS) has been integrated within mbed-os.
166+
- The mbed OS file system wrapper classes (e.g. FileSystem, File, FileBase classes)
167+
which are used to present a consistent API to the retarget module for different
168+
(third-party) file system implementations.
169+
- The FAT filesystem implementation code.
170+
The [FATFS: Generic FAT File System Module](http://elm-chan.org/fsw/ff/00index_e.html)
171+
(ChanFS) has been integrated within mbed-os.
171172
- The Block API Device Driver. The SDCard driver is an example of a persistent storage driver.
172173
It's maintained as a separate component from the mbed OS repository (in this repository).
173174
- The SPI module provides the mbed OS generic SPI API. This functionality is maintained in
@@ -472,20 +473,20 @@ Build the test cases for the K64F target using the following command:
472473
473474
The build trace is quite extensive but on a successful build you should see the following output at the end of the log:
474475
475-
Build successes:
476-
* K64F::GCC_ARM::MBED-BUILD
477-
* K64F::GCC_ARM::MBED-OS-FEATURES-FEATURE_LWIP-TESTS-MBEDMICRO-NET-CONNECTIVITY
478-
<trace removed>
479-
* K64F::GCC_ARM::MBED-OS-FEATURES-TESTS-FILESYSTEM-FAT_FILE_SYSTEM
480-
* K64F::GCC_ARM::MBED-OS-FEATURES-TESTS-FILESYSTEM-HEAP_BLOCK_DEVICE
481-
* K64F::GCC_ARM::MBED-OS-FEATURES-TESTS-FILESYSTEM-UTIL_BLOCK_DEVICE
482-
<trace removed>
483-
* K64F::GCC_ARM::SD-DRIVER-TESTS-FILESYSTEM-BASIC
484-
* K64F::GCC_ARM::SD-DRIVER-TESTS-FILESYSTEM-FOPEN
485-
486-
Build skips:
487-
* K64F::GCC_ARM::MBED-OS-FEATURES-FEATURE_LWIP-TESTS-MBEDMICRO-NET-TCP_PACKET_PRESSURE
488-
<trace removed>
476+
Build successes:
477+
* K64F::GCC_ARM::MBED-BUILD
478+
* K64F::GCC_ARM::MBED-OS-FEATURES-FEATURE_LWIP-TESTS-MBEDMICRO-NET-CONNECTIVITY
479+
<trace removed>
480+
* K64F::GCC_ARM::MBED-OS-FEATURES-TESTS-FILESYSTEM-FAT_FILE_SYSTEM
481+
* K64F::GCC_ARM::MBED-OS-FEATURES-TESTS-FILESYSTEM-HEAP_BLOCK_DEVICE
482+
* K64F::GCC_ARM::MBED-OS-FEATURES-TESTS-FILESYSTEM-UTIL_BLOCK_DEVICE
483+
<trace removed>
484+
* K64F::GCC_ARM::SD-DRIVER-TESTS-FILESYSTEM-BASIC
485+
* K64F::GCC_ARM::SD-DRIVER-TESTS-FILESYSTEM-FOPEN
486+
487+
Build skips:
488+
* K64F::GCC_ARM::MBED-OS-FEATURES-FEATURE_LWIP-TESTS-MBEDMICRO-NET-TCP_PACKET_PRESSURE
489+
<trace removed>
489490
490491
491492
Notice the following tests in the sd-driver tree are listed above:
@@ -553,35 +554,35 @@ To run the fopen test use:
553554
554555
On a successful run, results similar to the following will be shown:
555556
556-
mbedgt: test suite report:
557-
+--------------+---------------+-------------------------------------------+--------+--------------------+-------------+
558-
| target | platform_name | test suite | result | elapsed_time (sec) | copy_method |
559-
+--------------+---------------+-------------------------------------------+--------+--------------------+-------------+
560-
| K64F-GCC_ARM | K64F | sd-driver-features-tests-filesystem-fopen | OK | 151.46 | shell |
561-
+--------------+---------------+-------------------------------------------+--------+--------------------+-------------+
562-
mbedgt: test suite results: 1 OK
563-
mbedgt: test case report:
564-
+--------------+---------------+------------------------------------+----------------------------------------------------------------------------------------+--------+--------+--------+--------------------+
565-
| target | platform_name | test suite | test case | passed | failed | result | elapsed_time (sec) |
566-
+--------------+---------------+------------------------------------+----------------------------------------------------------------------------------------+--------+--------+--------+--------------------+
567-
| K64F-GCC_ARM | K64F | sd-driver-tests-filesystem-fopen | FSFAT_FOPEN_TEST_01: fopen()/fwrite()/fclose() directories/file in multi-dir filepath. | 1 | 0 | OK | 7.57 |
568-
| K64F-GCC_ARM | K64F | sd-driver-tests-filesystem-fopen | FSFAT_FOPEN_TEST_02: fopen(r) pre-existing file try to write it. | 1 | 0 | OK | 0.2 |
569-
| K64F-GCC_ARM | K64F | sd-driver-tests-filesystem-fopen | FSFAT_FOPEN_TEST_03: fopen(w+) pre-existing file try to write it. | 1 | 0 | OK | 0.41 |
570-
| K64F-GCC_ARM | K64F | sd-driver-tests-filesystem-fopen | FSFAT_FOPEN_TEST_04: fopen() with a filename exceeding the maximum length. | 1 | 0 | OK | 0.11 |
571-
| K64F-GCC_ARM | K64F | sd-driver-tests-filesystem-fopen | FSFAT_FOPEN_TEST_06: fopen() with bad filenames (minimal). | 1 | 0 | OK | 0.1 |
572-
| K64F-GCC_ARM | K64F | sd-driver-tests-filesystem-fopen | FSFAT_FOPEN_TEST_07: fopen()/errno handling. | 1 | 0 | OK | 0.07 |
573-
| K64F-GCC_ARM | K64F | sd-driver-tests-filesystem-fopen | FSFAT_FOPEN_TEST_08: ferror()/clearerr()/errno handling. | 1 | 0 | OK | 0.1 |
574-
| K64F-GCC_ARM | K64F | sd-driver-tests-filesystem-fopen | FSFAT_FOPEN_TEST_09: ftell() handling. | 1 | 0 | OK | 0.17 |
575-
| K64F-GCC_ARM | K64F | sd-driver-tests-filesystem-fopen | FSFAT_FOPEN_TEST_10: remove() test. | 1 | 0 | OK | 1.28 |
576-
| K64F-GCC_ARM | K64F | sd-driver-tests-filesystem-fopen | FSFAT_FOPEN_TEST_11: rename(). | 1 | 0 | OK | 2.3 |
577-
| K64F-GCC_ARM | K64F | sd-driver-tests-filesystem-fopen | FSFAT_FOPEN_TEST_12: opendir(), readdir(), closedir() test. | 1 | 0 | OK | 3.57 |
578-
| K64F-GCC_ARM | K64F | sd-driver-tests-filesystem-fopen | FSFAT_FOPEN_TEST_13: mkdir() test. | 1 | 0 | OK | 1.21 |
579-
| K64F-GCC_ARM | K64F | sd-driver-tests-filesystem-fopen | FSFAT_FOPEN_TEST_14: stat() test. | 1 | 0 | OK | 1.47 |
580-
| K64F-GCC_ARM | K64F | sd-driver-tests-filesystem-fopen | FSFAT_FOPEN_TEST_15: format() test. | 1 | 0 | OK | 26.12 |
581-
| K64F-GCC_ARM | K64F | sd-driver-tests-filesystem-fopen | FSFAT_FOPEN_TEST_16: write/check n x 25kB data files. | 1 | 0 | OK | 87.11 |
582-
+--------------+---------------+------------------------------------+----------------------------------------------------------------------------------------+--------+--------+--------+--------------------+
583-
mbedgt: test case results: 15 OK
584-
mbedgt: completed in 152.35 sec
557+
mbedgt: test suite report:
558+
+--------------+---------------+-------------------------------------------+--------+--------------------+-------------+
559+
| target | platform_name | test suite | result | elapsed_time (sec) | copy_method |
560+
+--------------+---------------+-------------------------------------------+--------+--------------------+-------------+
561+
| K64F-GCC_ARM | K64F | sd-driver-features-tests-filesystem-fopen | OK | 151.46 | shell |
562+
+--------------+---------------+-------------------------------------------+--------+--------------------+-------------+
563+
mbedgt: test suite results: 1 OK
564+
mbedgt: test case report:
565+
+--------------+---------------+------------------------------------+----------------------------------------------------------------------------------------+--------+--------+--------+--------------------+
566+
| target | platform_name | test suite | test case | passed | failed | result | elapsed_time (sec) |
567+
+--------------+---------------+------------------------------------+----------------------------------------------------------------------------------------+--------+--------+--------+--------------------+
568+
| K64F-GCC_ARM | K64F | sd-driver-tests-filesystem-fopen | FSFAT_FOPEN_TEST_01: fopen()/fwrite()/fclose() directories/file in multi-dir filepath. | 1 | 0 | OK | 7.57 |
569+
| K64F-GCC_ARM | K64F | sd-driver-tests-filesystem-fopen | FSFAT_FOPEN_TEST_02: fopen(r) pre-existing file try to write it. | 1 | 0 | OK | 0.2 |
570+
| K64F-GCC_ARM | K64F | sd-driver-tests-filesystem-fopen | FSFAT_FOPEN_TEST_03: fopen(w+) pre-existing file try to write it. | 1 | 0 | OK | 0.41 |
571+
| K64F-GCC_ARM | K64F | sd-driver-tests-filesystem-fopen | FSFAT_FOPEN_TEST_04: fopen() with a filename exceeding the maximum length. | 1 | 0 | OK | 0.11 |
572+
| K64F-GCC_ARM | K64F | sd-driver-tests-filesystem-fopen | FSFAT_FOPEN_TEST_06: fopen() with bad filenames (minimal). | 1 | 0 | OK | 0.1 |
573+
| K64F-GCC_ARM | K64F | sd-driver-tests-filesystem-fopen | FSFAT_FOPEN_TEST_07: fopen()/errno handling. | 1 | 0 | OK | 0.07 |
574+
| K64F-GCC_ARM | K64F | sd-driver-tests-filesystem-fopen | FSFAT_FOPEN_TEST_08: ferror()/clearerr()/errno handling. | 1 | 0 | OK | 0.1 |
575+
| K64F-GCC_ARM | K64F | sd-driver-tests-filesystem-fopen | FSFAT_FOPEN_TEST_09: ftell() handling. | 1 | 0 | OK | 0.17 |
576+
| K64F-GCC_ARM | K64F | sd-driver-tests-filesystem-fopen | FSFAT_FOPEN_TEST_10: remove() test. | 1 | 0 | OK | 1.28 |
577+
| K64F-GCC_ARM | K64F | sd-driver-tests-filesystem-fopen | FSFAT_FOPEN_TEST_11: rename(). | 1 | 0 | OK | 2.3 |
578+
| K64F-GCC_ARM | K64F | sd-driver-tests-filesystem-fopen | FSFAT_FOPEN_TEST_12: opendir(), readdir(), closedir() test. | 1 | 0 | OK | 3.57 |
579+
| K64F-GCC_ARM | K64F | sd-driver-tests-filesystem-fopen | FSFAT_FOPEN_TEST_13: mkdir() test. | 1 | 0 | OK | 1.21 |
580+
| K64F-GCC_ARM | K64F | sd-driver-tests-filesystem-fopen | FSFAT_FOPEN_TEST_14: stat() test. | 1 | 0 | OK | 1.47 |
581+
| K64F-GCC_ARM | K64F | sd-driver-tests-filesystem-fopen | FSFAT_FOPEN_TEST_15: format() test. | 1 | 0 | OK | 26.12 |
582+
| K64F-GCC_ARM | K64F | sd-driver-tests-filesystem-fopen | FSFAT_FOPEN_TEST_16: write/check n x 25kB data files. | 1 | 0 | OK | 87.11 |
583+
+--------------+---------------+------------------------------------+----------------------------------------------------------------------------------------+--------+--------+--------+--------------------+
584+
mbedgt: test case results: 15 OK
585+
mbedgt: completed in 152.35 sec
585586
586587
587588
# <a name="summary-posix-api-documentation"></a> Summary of POSIX File API Documentation

0 commit comments

Comments
 (0)