Karl Fessel
Karl Fessel
some of the changes in 16001848c3b1c0e5ac0dd9fa90603d0fb8c843fb are part of #17950
This is fixed with #18425
> > I think there should be some kind of warning that this will not do wear leveling and advising a solution like littlefs2. > > Whaat? I thought that...
seems like the compactness of the written data (littlefs2 is more spacey when writing to different places) in the mtd threw me off -> it writes to different places (levels...
I had another look at the writes (native mtd debug)-> only writes are happening no erases (i assume until rollover) There is a huge number of small writes (sometimes to...
> Is there still something that speaks in principle against merging this PR? No, I just where not able to run the test on stm32 (most boards around me got...
I just tried to test this using a `nucleo-f103rb` and the `test/pkg_flashdb_vfs` (previously tried the mtd version which also failed), I am still not sure if this is not working...
i enabled some debugging in the stm driver. https://gist.github.com/kfessel/2d3bf88605d21652caf271226802be94 the mtd_flashpage test seems to run until the newly added [L247](https://github.com/RIOT-OS/RIOT/pull/18608/files#diff-ebe3dffdaf93069e4c8cf405f1fb5f4a1524d322390172f282095fa731ed9e23R247)
this is behavior change in git. when a file is clicked a git log containing the parameter `-m` is is run ``` git log --topo-order --no-color --log-size --parents --boundary -z...
your commits messages will need rewording https://github.com/RIOT-OS/RIOT/blob/master/CONTRIBUTING.md#commit-conventions