Before logging an issue, please update to the latest release of Visual Micro from the Downloads Page.

When Logging a Support Issue in the Forum, please ensure you have also:-

  • Enabled vMicro > Compiler > Show Build Properties
  • Re-Compile your program with these settings enabled
 
Save the new Output to a Text File and....
  • Click the Reply button and attach as .txt file OR
  • Click here to Email us with the file attached, and a link to your post
Support requests without the output above may be impossible to answer, so please help us to help you
 
Page Index Toggle Pages: 1 Send TopicPrint
Hot Topic (More than 8 Replies) LittleFS fail to initialze after VS and VSMicro update (Read 90 times)
Chevelle
Junior Member
**
Offline


Posts: 35
Joined: Feb 29th, 2020
LittleFS fail to initialze after VS and VSMicro update
May 14th, 2025 at 9:34pm
Print Post  
Argh!  I hate when this happens.  I received the latest version of the PCBs that I have designed that use the ESP32-S3.  The previous version worked fine and the changes had to do with the features of the display we are using, not the fundamental functions of the ESP32-32.  While I was waiting for the boards, both Visual Studio and VSMicro were updated.   I don't know if this was the cause but the code can't get past the LittleFS begin.

I then tried an ESP32-S3 DevKit board with the basic LittleFS example.  Still No Joy.  You guys are geniuses and so I figured I would bring the issue here.

Note that I am using the ESP32 2.0.14 Core.  This is because the library used for the TFT display is not compatible with later versions of the core.

Code and compile window attached.
  

Please Register or Login to the Forum to see File Attachments
Back to top
 
IP Logged
 
Simon@Visual Micro
Administrator
*****
Offline


Posts: 2704
Joined: Feb 13th, 2019
Re: LittleFS fail to initialze after VS and VSMicro update
Reply #1 - May 14th, 2025 at 10:02pm
Print Post  
Thanks for the report.

The log doesn't show the upload of the FileSystem files to the LItteFS Partition.  Have you run vMicro > Publish Server Data Files?

If you have an error when running this please attach the output as well.

There are 2 additional board options to make this happen each upload(at the bottom of the board options list on the vMicro menu):
  • vMicro > FileSystem Upload Tool = LittleFS
  • vMicro > Automatic FS Upload = On


« Last Edit: May 14th, 2025 at 10:03pm by Simon@Visual Micro »  
Back to top
IP Logged
 
Chevelle
Junior Member
**
Offline


Posts: 35
Joined: Feb 29th, 2020
Re: LittleFS fail to initialze after VS and VSMicro update
Reply #2 - yesterday at 1:40pm
Print Post  
This is interesting...

The File System is set to LittleFS and the data files are set to upload.

I am using the Dev board for testing and if I use the UART connection to upload everything, all works as expected and I get the responses I expect through the Serial monitor.  If I use the UART connection, the firmware upload OK but I do not get any response over the Serial monitor.

Is there a setting I am missing?
  
Back to top
 
IP Logged
 
Simon@Visual Micro
Administrator
*****
Offline


Posts: 2704
Joined: Feb 13th, 2019
Re: LittleFS fail to initialze after VS and VSMicro update
Reply #3 - yesterday at 1:49pm
Print Post  
Sorry you said you are using the UART Connection in both scenarios.

Do you mean the UART Upload works as expected, but using the Programmer does not?
  
Back to top
IP Logged
 
Chevelle
Junior Member
**
Offline


Posts: 35
Joined: Feb 29th, 2020
Re: LittleFS fail to initialze after VS and VSMicro update
Reply #4 - yesterday at 1:52pm
Print Post  
Sorry.  When I use the UART connection on the Dev board, the firmware uploads fine and the Serial monitor has the expected outputs and responds to the expected lines sent to it.

When I use the USB port on the Dev board, the code uploads fine and I presume is running but nothing comes out of the Serial monitor.
  
Back to top
 
IP Logged
 
Simon@Visual Micro
Administrator
*****
Offline


Posts: 2704
Joined: Feb 13th, 2019
Re: LittleFS fail to initialze after VS and VSMicro update
Reply #5 - yesterday at 3:06pm
Print Post  
Thanks for clarifying.

I believe if you change the USB CDC On Boot option, and rebuild and reupload, the messages should now appear over the USB Port.
  
Back to top
IP Logged
 
Chevelle
Junior Member
**
Offline


Posts: 35
Joined: Feb 29th, 2020
Re: LittleFS fail to initialze after VS and VSMicro update
Reply #6 - yesterday at 3:35pm
Print Post  
Still no joy.  Here are the compile settings...
  

Please Register or Login to the Forum to see File Attachments
Back to top
 
IP Logged
 
Simon@Visual Micro
Administrator
*****
Offline


Posts: 2704
Joined: Feb 13th, 2019
Re: LittleFS fail to initialze after VS and VSMicro update
Reply #7 - yesterday at 3:46pm
Print Post  
Thanks, can you show the detail of what is in the Port or IP box as well so we can understand which ports are available?
  
Back to top
IP Logged
 
Chevelle
Junior Member
**
Offline


Posts: 35
Joined: Feb 29th, 2020
Re: LittleFS fail to initialze after VS and VSMicro update
Reply #8 - yesterday at 3:52pm
Print Post  
When it is plugged into the UART port on the Dev board, the COM window shows "COM6 - Silicon Labs CP210x USB to UART Bridge"

When it is plugged into the USB port on the Dev board, the COM windows shows "COM5 - USB Serial Device"

No other ports show up in the list.
  
Back to top
 
IP Logged
 
Simon@Visual Micro
Administrator
*****
Offline


Posts: 2704
Joined: Feb 13th, 2019
Re: LittleFS fail to initialze after VS and VSMicro update
Reply #9 - yesterday at 4:08pm
Print Post  
Thanks for the update.  Does disabling DTR and RTS in the Serial Monitor window help at all? 
(may need to reset the board once the options are changed.)
  
Back to top
IP Logged
 
Chevelle
Junior Member
**
Offline


Posts: 35
Joined: Feb 29th, 2020
Re: LittleFS fail to initialze after VS and VSMicro update
Reply #10 - yesterday at 4:17pm
Print Post  
I just do not know what happened.  I did not change a thing but did shut down VS since our last exchange.  After your last note, I started VS up again and before I made the changes to DTR and RTS, the COM window opened up and all the proper communication went across the USB port.  I uploaded the code to my board and it too worked fine.

It is amost a bad thing when this happens.  I still don't know what changed and whatever caused the issue could creep in again.

For now, I'm good.  Thanks very much.
  
Back to top
 
IP Logged
 
Page Index Toggle Pages: 1
Send TopicPrint