You have ENABLE_ALL_EDIT_OPTIONS defined, however. So your config does now implicitly have the new sd mount option set.
IMO, this is a good thing. There’s no shortage of instances and cases where not having the sd card mounting be managed has lead to various forms of corruption of the disk files.
I mean, I think it’s better to have to manually enable the SD card for mass storage (aside from it being a little annoying if I just want to upload something quick. Because in my build it’s hard to get the SD card out.)
But maybe worth investigating, because in my case the behavior is different than the documentation?
It’s documented under the ENABLE_ALL_EDIT_OPTIONS stuff here:
Ok, so what I’m seeing is to be expected. Check.
I guess I was just confused about NoSloppy’s comment.
Sorry, I didn’t mean to confuse. Honestly, I wasn’t aware that MOUNT_SD_SETTING was blanketed under ENABLE_ALL_EDIT_OPTIONS since I don’t use that.
So yeah, the procedure is dead simple.
sd 1, it mounts to PC,
do your thing,
EJECT (unmount) it from the computer.
That’s all it is. sd 0 is already set once it remounts to the Proffieboard so it’s basically optional.
No problem! I’m glad it’s all clear now 