I have some of the files saved, but there's not a whole lot of configuring to do in any case. Not a big deal to re-initialize. Probably good to do that, just in case there's some old cruft out there that I don't remember. Unless someone has any ideas on what might have caused this, I probably should re-init Flash and move on. I've not tried to create any files or such, to not protect the guilty by destroying evidence. Last chance... ? So, if we do come to that, what is the easiest way to re-init Flash? Buttons somewhere, if I recall, but I've never done that as yet. Thanks, Greg Stephen Casner wrote:
Well, Greg, it looks like your /store is scrogged and needs to be initialized anew. No idea how that happened.
If by chance you saved a copy of your files using scp then you could scp the copy back, again assuming CONFIG_OVMS_DEV_CONFIGVFS=y.
-- Steve
On Fri, 16 Feb 2018, Greg D. wrote:
Hi Steve,
No, it's just "cannot be opened:"
OVMS > vfs ls /store ????????????????????????.????????? ????????????????????????.????????? <snip 124 lines> ????????????????????????.????????? ????????????????????????.????????? ovms_config OVMS > vfs cat /store/ovms_config Error: VFS file cannot be opened OVMS > vfs stat /store/ovms_config Error: VFS file cannot be opened OVMS >
I just noticed that there are 128 lines of bogus files (power of 2 a coincidence?), prior to ovms_config.
Greg
Stephen Casner wrote:
Greg,
But, if I try to vfs cat the file, ovms complains that the file cannot be opened. Just checking... Is the complaint "Error: protected path"? If so, you have to set:
CONFIG_OVMS_DEV_CONFIGVFS=y
in sdkconfig to allow access with the vfs commands.
-- Steve
OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev