SPIFFS: updated for recent vfs.h changes#1
Closed
jnohlgard wants to merge 51 commits intoOTAkeys:pr/spiffsfrom
Closed
SPIFFS: updated for recent vfs.h changes#1jnohlgard wants to merge 51 commits intoOTAkeys:pr/spiffsfrom
jnohlgard wants to merge 51 commits intoOTAkeys:pr/spiffsfrom
Conversation
Some USEMODULE parts (e.g. defined in ${BOARD}/Makefile.dep) were not
being properly exported to CFLAGS -DMODULE_xxx options.
The VFS layer provides file system abstractions to allow using a unified interface to access files from mounted file systems.
usage: vfs r /path/to/file nbytes offset Only reading is currently supported
mtdi stands for memory technology device interface. It's a generic interface which can be used to implement flash drivers.
This implements basic features with the VFS interface
pkg/spiffs/include/spiffs_config.h
Outdated
|
|
||
| #define ENABLE_DEBUG (0) | ||
| #include <debug.h> | ||
|
|
Member
There was a problem hiding this comment.
I wanted to find a better solution, but if not defined here, we cannot use the SPIFFS_DBG* macros.
But it sucks...
Member
|
@gebart Thanks ! |
Member
|
merged, thanks ! |
vincent-d
pushed a commit
that referenced
this pull request
Dec 20, 2018
* drivers/ccs811: fix types in debug messages * drivers/driver_ccs811_full: fix unused variable build error
toonst
pushed a commit
that referenced
this pull request
Jul 19, 2019
The evtimer_msg test is expanded to also delete entries. Furthermore the messages that are printed should now show numbers that are very close (if not equal). Something like this: At 740 ms received msg 0: "#2 supposed to be 740" At 1081 ms received msg 1: "#0 supposed to be 1081" At 1581 ms received msg 2: "#1 supposed to be 1581" At 4035 ms received msg 3: "#3 supposed to be 4035" The function evtimer_print is also called to show the intermediate status of evtimer entries.
vincent-d
pushed a commit
that referenced
this pull request
Sep 6, 2019
The test randomly fails on `native` due to timers being not accurate but
it cannot be otherwise. So better disable it than raising fake errors.
main(): This is RIOT! (Version: buildtest)
Testing generic evtimer
This should list 2 items
ev #1 offset=1000
ev #2 offset=500
This should list 4 items
ev #1 offset=659
ev #2 offset=341
ev #3 offset=500
ev #4 offset=2454
Are the reception times of all 4 msgs close to the supposed values?
At 662 ms received msg 0: "#2 supposed to be 659"
At 1009 ms received msg 1: "#0 supposed to be 1000"
At 1511 ms received msg 2: "#1 supposed to be 1500"
Traceback (most recent call last):
File "/tmp/dwq.0.3125418833043728/ef3af88c4b3615788b164464a437df5c/tests/evtimer_msg/tests/01-run.py", line 33, in <module>
sys.exit(run(testfunc))
File "/tmp/dwq.0.3125418833043728/ef3af88c4b3615788b164464a437df5c/dist/pythonlibs/testrunner/__init__.py", line 29, in run
testfunc(child)
File "/tmp/dwq.0.3125418833043728/ef3af88c4b3615788b164464a437df5c/tests/evtimer_msg/tests/01-run.py", line 26, in testfunc
assert(actual in range(expected - ACCEPTED_ERROR, expected + ACCEPTED_ERROR))
AssertionError
vincent-d
pushed a commit
that referenced
this pull request
May 6, 2020
The ROM size is encoded in the part number of the Atmel SAM chips. RAM size is not encoded directly, so get it by parsing the chip's vendor file. The file remains in the page cache for the compiler to use, so the overhead should be minimal: on master: Benchmark #1: make BOARD=samr21-xpro -j Time (mean ± σ): 527.9 ms ± 4.9 ms [User: 503.1 ms, System: 69.6 ms] Range (min … max): 519.7 ms … 537.2 ms 10 runs with this patch: Benchmark #1: make BOARD=samr21-xpro -j Time (mean ± σ): 535.6 ms ± 4.0 ms [User: 507.6 ms, System: 75.1 ms] Range (min … max): 530.6 ms … 542.0 ms 10 runs
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
These are the updates required to get SPIFFS running on the current state of RIOT-OS#5616
(rebase on RIOT-OS#5616 after merging)