mattpannella / pupdate

Pupdate - A thing for updating your Analogue Pocket
https://mattpannella.github.io/pupdate/
MIT License
989 stars 33 forks source link

Error in framework RS: BRIDGE not responding #293

Closed marcussharpe closed 1 month ago

marcussharpe commented 2 months ago

Describe the bug

Error message reported when attempting to start a PC Engine game:

Error in framework RS: BRIDGE not responding

(I realise this may well be a Pocket issue, not a pupdate issue, but reporting here for the record.)

To Reproduce Steps to reproduce the behavior (note that I'm a little hazy on the order of some of the steps here):

  1. Use pupdate to set up my SD card e.g. pupdate -p /Volumes/Pocket.
  2. Load up my SD card with PC Engine ROMs.
  3. Play PC Engines ROMs on the Pocket.
  4. Use pupdate to update my SD card e.g. pupdate -p /Volumes/Pocket to the latest releases of everything (cores, pocketOS, etc.)
  5. Add some more PC Engine ROMs.
  6. Attempt to play one of the new ROMs and get the "Error in framework RS: BRIDGE not responding" error.
  7. Attempt to play one of the old ROMs and get the same error.
  8. Run pupdate again to update everything - still see the same error.

Expected behavior I would expect to be able to play the old and new ROMs successfully.

Screenshots N/A

Desktop (please complete the following information):

Contents of settings file pupdate_settings.json

Additional info

I also ran pupdate in a temp directory on my Mac just to be able to compare and contrast the difference between that and the contents of my Pocket's SD card. The thing that most stood out was a difference in shasum of the Cores/agg23.PC Engine/pce.rev file - the file size was the same but the sum was different. I parachuted the pce.rev file from the temp directory onto my Pocket's SD card, and this fixed the issue - all my ROMs ran without display the error message. I then reverted the file to the "broken" version, and the error started being seen again.

I grepped the pupdate code for references to this via the .core.cores[].filename field in cores.json for that core but couldn't find anything from a cursory look, but I may well have missed something. However, I realise this might well be a Pocket issue, not a pupdate issue, so sorry for the noise if so :)

lunchpacked130 commented 2 months ago

I haven't had any issues with this, but a quick search suggests that this error is from a broken/corrupt core...

If you haven't already, Try the following: (This information is a trimmed down version focusing only on pupdate taken from a more substantial upcoming troubleshooting guide I'm writing, It's made to be universal, so it should work on any core.)

Core Errors and Faults:

[!TIP] On search engies (google, bing etc), write the error message as it appears and try adding quotation marks around the error message. Sometimes a different core could have had the exact same problem/error message, and if it doesn't give an answer, it can often give an indication of what might be wrong.

On github, remember to look through "closed issues" to see if this is an already resolved issue. on the issues page for the project, click " Closed" ( is numbers) or add "is:closed" to the filter bar to see the closed issues

Reinstall the core:

Using pupdate:

  1. Run Pupdate.exe from memorycard root
  2. select [6] Pocket Maintenance
  3. Select [1] Reinstall Select Cores
  4. Find the affected core in the list and [X] mark it.
  5. Select Save Choices at the bottom to reinstall the core.

Clean install:

[!NOTE] All file/folder locations described below are based on being from the root folder of the SDcard.

Actions using Pupdate:

  1. Run Pupdate.exe from memorycard root
  2. Select [6] Pocket Maintenance
  3. select [3] Uninstall Select Cores
  4. Find and [X] mark the affected core.
  5. Select Save Choices at the bottom to Uninstall the core
  6. After Uninstallation, exit Pupdate.

Actions using OS file browser (explorer/finder etc):

  1. Delete folder \Cores\"affected core
  2. Delete file "affected core".json from \Platforms
  3. Delete folder \Settings\"affected core"
  4. Delete folder \Assets\"affected core" *

[!NOTE]

  • = You don't always have to delete the entire assets folder. to keep romfiles, follow step 10a. below instead
    10a. Keep Romfiles [Expand to show]

10a-1. Open the \Assets\"affected core" folder.

10a-2. Delete all files/folders except common folder.

10a-3. Open the \Assets\"affected core"\common folder

10a-4. Delete all Bios and/or System files (depends on core).

If you still have issues after completing a clean install, you might have to remove the \Assets\"affected core"\ folder completely and re-aquire the romfiles (either do a fresh dump/download) to be sure there isn't any corruption or similar in the romfiles.

  1. Redownload Newest pupdate release and overwrite the one on your SDcard (even if it's the same version)

  2. Run Pupdate.exe and select [2] Select Cores(make a selection if asked)

  3. Find the core in the list and mark it [X] for installation.

  4. Select [8] Settings and make sure "Download missing assets" is [X] marked (Alternatively also [ ] Unmark the "Skip alternative roms")

  5. Run [0] Update All to download core and bios/system files

[!NOTE] If reinstall or clean install did not fix the issue, you can try one or more of the following: ● Running Pupdate.exe as administrator ● Try using another freshly formatted SD card ● Resetting Analogue Pocket settings ● Manually downloading the core direct from github and/or building it yourself ● Reformat the SD card

[!IMPORTANT] I'm not responsible for any dataloss etc from these procedures.

Remember to Back-up any files and folders first to avoid any potential data loss)

[!NOTE] Download speeds are slow, typically 2-300kb/s so be aware that depending on the amount of assets/alt assets to be downloaded, it might take up to several hours to finish a complete asset download (especially with alternative roms)