logo elektroda
logo elektroda
X
logo elektroda

OpenBeken T102_V1.1. disappearing autoexec.bat file from LittleFS after update

Honsu 642 4
ADVERTISEMENT
Treść została przetłumaczona polish » english Zobacz oryginalną wersję tematu
  • #1 21018723
    Honsu
    Level 3  
    I own a smart socket with energy metering. Originally there was a T102_V1.1 module in it, which I changed to ESP-O2S.
    I have uploaded the OpenBeken Chipset BK7231T to it.
    After every software update via the Launch Web Application page, my autoexec.bat file disappears.
    Is this a software error? Where do I look for the cause?
  • ADVERTISEMENT
  • Helpful post
    #2 21020158
    p.kaczmarek2
    Moderator Smart Home
    Thanks for the report, I have corrected the title, I will take care of this problem.

    The situation with the occasionally disappearing autoexec.bat file is due to how LittleFS is placed. LittleFS is placed at the end of the partition used for OTA. Initially it occupied this whole partition, but we decided that this was pointless, so now we deduct the file system size from the end of the partition and allocate the system on the resulting offset.
    This solution works, but there is one problem - if the OTA file grows over time, LittleFS is again overwritten by this.
    Probably again the OTA file has grown enough that it reaches the LittleFS offset...
    This will be corrected, also we will probably add in the OTA a query whether to take a LittleFS dump just in case, and for now you can try for example the command:
    
    lfs_format 16384
    

    to reset the LFS to a smaller size as a test.
    Helpful post? Buy me a coffee.
  • ADVERTISEMENT
  • #3 21020265
    Honsu
    Level 3  
    After executing the command
    lfs_format 16384


    the autoexec.bat file did not disappear after another update.
    Problem solved. Thank you. The topic is gone
  • ADVERTISEMENT
  • #4 21020282
    p.kaczmarek2
    Moderator Smart Home
    I am glad to have helped. Admittedly, it's not a final solution because it's up to me to tweak the firmware myself so this doesn't occur, but it's good to know that such a "format" can at least cover the problem. I'll try to solve this better in future versions (at least declare a smaller default LFS size to respect that the OTA has grown over the year...).
    Helpful post? Buy me a coffee.
  • #5 21322450
    AndroidGeek
    Level 3  
    >>21020282 Hello! I have the very same issue however after running lfs_format 16384 it didn't solve the problem for me. The LFS is still missing. Current version is: version 1.17.777. Also logs say:
    Error:LFS:LFS media partition position 0x190000 while expected is 0x192000
    
ADVERTISEMENT