Alan C. Assis

@Feoggou isn't 10ms too low value for a SD Card timeout? Other thing that is raising concern: are you using 100HZ for clock tick? This is exactly 10ms too, if...

@Feoggou normally SDCards and eMMC have an internal software running inside it and from time to time it needs to "clear the house" and reorganize/consolidate the blocks inside to optimize...

@Feoggou yes, I'm not saying that the driver is right, just saying that the timeout could be caused that fact. About: "I tried with the value of 10 miliseconds, which...

@Donny9 please take a look on this issue. @SPRESENSE is that driver you are citing included into mainline? ping @xiaoxiang781216 @raiden00pl

@SPRESENSE It is possible to create a simple test to verify this issue on SIM or QEMU?

@W-M-R why don't we just add is by default instead of depending on Kconfig? Every user needs it and we can use it in the CI to warn about board...

@W-M-R maybe you can just ignore if for boards that doesn't support it. Since it is something that doesn't increase the final binary and it is very useful for all...

@W-M-R I think we don't even need a config for it, just keep is something expected at the end of the build process, like others RTOSes do

@W-M-R I think you need to ignore the parameter for SIM board/arch: ``` aarch64-none-elf-g++: error: unrecognized command-line option '--print-memory-usage' ninja: build stopped: subcommand failed. cp: cannot stat 'nuttx.hex': No such...

@SPRESENSE isn't it better to fix the existing applications using the old API instead bringing back those APIs to mainline? I agree that breaking APIs is not a good thing,...