johnbaumann / openmc Goto Github PK

Finish designing a 3d printed case for the standard sized pcb.

An attempt is made to mount the SD card at startup, but the status is not polled beyond then. If the card is unexpectedly removed or re-inserted after this time, it should be detected and handled accordingly.

Files are not written back to SD card. Investigate ways to handle this gracefully. Need to delay from last memory card write activity and ensure no ram write collisions occur.

Need to add default behavior for loading files from the card.

If no card assigned, create a default file on card?
Load last used?
Assign default to load(i.e. freepsxboot)?

Merge bare metal branch back to master

Need a file for loading/saving general settings.

Default file(i.e. freepsxboot, manually define or toggle through web interface)
Last file(if no default, load last mounted file. If blank, create new. If no space, card on ram only?)

PS1 pins were moved when testing for WiFi interference. Verify this is not an issue and consider moving these pins back. Pins are currently out of order and will be annoying to route.

Task sizes are allocated arbitrarily. Investigate actual usage using uxTaskGetStackHighWaterMark() and resize accordingly.

Implement retries on write failures.
Sometimes writes are occurring too close to last write activity. For example, writes to spiffs storage can take quite a bit longer than SD cards. Consider adding a test write when initializing the filesystem, and using some portion of this as a delay between failed writes.

Need to finalize pcb design and upload files required for producing a board.

Most of the ESP features were quickly hacked in from esp-idf example code. Several issues may occur if one process fails, such as mounting the SD card or connecting to WiFi.

Now that core0 stalls during SIO traffic, it is important for the process to bail if there is no activity for a certain length of time. This is most likely to occur if the console is powered down.

Create wifi_client.txt and load SSID + Password settings. If file not found, start server in WiFi AP mode. Allow creating file from web server, or uploading to SD card.

It might be useful if SPIFFS could be used as a fallback for the SD Card for reading/writing saves + file server storage.

The error checking issue raised in #2 will be closely tied to this issue

Need to remove all spiffs usage from code, disable as fallback storage etc. Spiffs too unreliable for use.

I've spent most of my spare time this week trying to get into this same project. Got a board here with WROOM32, SD card on VSPI and PSX wired to HSPI and another SD card on the MMC.. nothing but issues with both my ESP32's.. both bricked. One in a boot loop. Just googled to see if ANYONE else had done anything like this that was open source and found this! I'm an absolute beginner but looking forward to getting some new boards and seeing what stage this is up to. I will be doing mine from scratch, but I'll keep my eye on this and reference it if i use any ideas off it.

My first issue arose instantly, I didn't want to use the flash as an in between from the console to the SD card, but even though these are stated to have a certain amount of RAM (over 500Kb) you can't fit an entire 15 blocks (128Kb) in an SRAM buffer/ structure.

Anyway, I'm an absolute beginner. Couple projects on a normal Arduino then decided to jump into this and having a memcarduino that I often use, figured there was enough info out there (especially with no cash having all the command bytes and returns etc listed)

I figured step one was to just stream memory card reads and writes to the serial monitor and get a grasp of what's happening, then after that get the ESP32 to ignore anything until it received the memory card flag and sort of puzzle it together slowly from there with the help of memcarduino source / no$ information. Got a shock when I found this....

Cheers

:)

Directory support(and probably several other things) breaks when HTML URL encoding/entities are encountered.

Determine if OLED should even have a file browser, max number of files per folder, etc.