Imbrium, contd.

UPDATE2: There’s a bug in early GDEMU bootloaders that was fixed in late 2016, it can randomly lock up the device while trying to execute the updater. Sorry about the download link confusion, I have a revised version ready but I need to test it some more. I will upload that one in 2-3 days.

UPDATE: The updater was tested on pretty much every GDEMU revision there was, including the early 2014 v5.0 models, and worked every time so I’m releasing it.

Okay – the updater for older GDEMUs is ready and has been tested. Still, after that angry comment in the last post I’m again questioning the wisdom of openly distributing a FW file that can potentially brick your device if you don’t follow my instructions to the letter. And apparently some people only read every second line or so, and then come to their own conclusions.

And, frankly, there could still be a bug in it, or perhaps my instructions are not that clear to begin with. Though – somewhat surprisingly – the people who have most problems are those that nearly don’t speak English and use various automated translation tools but also the native speakers.

My English might be somewhat rough around the edges but when I ask you to first rename a file and then copy it to the card, it’s not because I’m unable to form a complex sentence. You are supposed to do exactly that, in this particular order, step by step. I meant it when I said pretty much all issues people had updating the FW were self-inflicted.

So, this being a big update and a potential major disaster waiting to happen, I’m asking for some volunteers first. Leave a note in the comments, especially if you own an older (pre 2016) device. I will select a few people and offer full help should something go wrong. If that goes well, I will upload the updater for everyone to use. Also, people who can make a YT tutorial for those with, shall we say, shorter attention span are very welcome. A good video might be useful as well.

The gist of the update process is this:

  1. Flash the updater FW following the usual instructions on the blog page.
  2. Remove the card and power the Dreamcast once, without any card inserted, to let the updater do its work. Wait for BIOS menu to appear.
  3. Power off and then insert the 5.20+ FW to flash that, again follow the instructions.

And that’s it. Few notes:

  • Older GDEMUs (and I mean the realy early ones) have different flash patterns for FW update. In general it’s OK to go to step 2 anyway because if the file was corrupted or something went wrong, your device will simply blink and not start, but will not be bricked. So you can retry.
  • When booting the updater, wait for the Dreamcast to go the main menu. Then you can turn it off. If you get weird blinks on your device instead, contact me. The short LED blinking burst on power-on is normal.
  • Speaking of weird LED flashes, make sure your Dreamcast runs well and did not just get affected by the “bad PSU contact disease”. For example run it for few minutes first and make sure it doesn’t randomly reboot or go back to the menu from inside a game. You really don’t want the power loss to occur when updater is running.
  • If you turn off the console after updater has run and then turn it on again, GDEMU will blink like if it had no FW installed. That’s normal, it now wants the 5.20+ version and will no longer work with any previous one. Though if you follow the instructions you shouldn’t ever get here.
  • The updater actually does have some rudimentary OLED support but the 5.20 FW does not. I really need to make that connection diagram ASAP in case someone wants to use it.

130 thoughts on “Imbrium, contd.

  1. just to update my gdemu is all flashed and working great thank you for all your hard work

  2. reporting problems and make fixes or features requests its a good thing but let me make the other thing that is missing and its even better whitch is simply reporting the corect operation of the gdemu and its newly released fw. i have beat from start to finish re cv (the english translated japan one via vga 60hz) on new 5.20.1 fw and indeed the new fw is working wonderfull for this game. i lack free time but i will test other games as well. my gdemu ini read_limit is set to 1250 yes im working my whole game library to gdrom speeds but that is not necesary for anyone to folow. the read_limit -1 in the ini can ensure slow down only to problematic games recv and soa.

  3. another question. i have bought a second gdemu little latter after mine for a friend. he has stock psu. i would clean the contacts of motherboard and the psu first before update. but what i dont know is how reliable his psu is. (he doent have freezes or reboots) but does an iterupt of the update of the bootloader updater can brick a device needing a special fix? if that is the case i would update his gdemu on my console that has a pico psu.

    • Oh I’m sorry, I’ve modified that link but it seems I forgot to press Update button. Try now.

  4. I had a bit of an issue with the latest firmware that I wanted to mention in case someone else runs into it. I updated to the latest firmware yesterday, tested both problem games, and seeing as they both where working as promised, called it a day. This morning, I tried to boot up Sonic Adventure 2, and got kicked back to the Dreamcast bios. After a bit I discovered about 10 previously working disk images where no longer booting. After I had already replaced them all, I got an idea to turn image tests off, which I have never had to do before. So I loaded all the problem disk images up, turned off image integrity tests with the ini file, and everything worked again as before the firmware update. I’ve never had to turn off the image tests before this, so I am wondering what has changed.

    I should mention that all the images that stopped working after the update had been edited to add custom cover art and to reduce the file size.

    TLDR: Previously working images stopped working after FW update. Turning off image integrity tests fixed it.

      • i used the same sd card that i have my games when doing both updates. no coruption all my games are working ok although i will make a deep test. im using gdis that are either by tosec or tryrip. redump is to avoid for gdemu use

      • No Redumps, and yeah they where all GDI. They where all from the GDEMU top 55 collection FirebrandX put together.

      • Not familiar with that collection. Does it use “repacked” GDIs perhaps? If so you’ll need to disable the image integrity checks like you did.

      • I can’t find anything mentioning repacked GDI’s but you’re probably right in thinking they are. Thanks for the reply by the way!

  5. Just updated the bootloader and latest firmware for my GDEMU for the first time since owning my GDEMU. Easy to follow instructions. No problems at all during update process. Thanks GDEMU, much appreciated.

    • Hey gdemu,
      So pleased to see this development, thank you.
      However the firmware updater link appears to be dead.
      If you could update the link please I’d be extremely grateful.
      Many thanks in advance.

    • there is an update2 regarding the reason for removal of the updater. for the rest of us that we updated just fine will we have the need to reflash the new updater? (because of fixes) or it is just a corection for the gdemus that wont work with the first one. but for the rest its just the same thing?

  6. any have the link to the new firmware updater file i need for my gdemu?

  7. I successfully updated the bootloader and firmware. I decided to try Resident Evil CV (it’s the older TOSEC GDI dump, so I believe it’s a good rip). The game froze on me twice. First, it wouldn’t even boot and the second time, it stuttered & then froze on the very first intro video sequence. All the other TOSEC rips I tested seem to be working fine. Has anybody else encountered this problem? I see there is a new read_limit option in the .ini file, but I’m not sure what value to set it to on a NTSC USA console. Thanks!!!

    • Either it’s a PSU problem or that image hasn’t been recognized – but I’ve tested all GDI rips so that’s unlikely.
      Well, the SD card could also be causing problems. Always try another one of different brand – preferably some cheap 2-8GB one. These aren’t fast by today standards but also don’t suffer from random latency spikes.

      • Thanks for the suggestion. I tried my smallest Sandisk Ultra card I have (16 GB and it strangely locked up as well on the beginning intro movie as well, though it is rated at 80MB/s) I noticed that gdmenu 0.6 comes with an gdemu.ini file that sets open_time=150 and detect_time=150. I don’t know if that would cause any problems, though. Also, I replaced my replaced my old original psu with a pico dreamcast 1.1 & picoPSU-80W/12V from mini-box

      • Try 250ms times, or even 500ms but note that will slow down the card scan on boot.
        Replacement PSU might still be affected by the bad contact if the problem is on the mobo pin side. Do you have a volt meter? Measure voltage on GDEMU directly, use first and last of the holes in the vertical row over the status LED. You should get 3.3V, and anything below 3.15V is too low and possibly a bad contatct.

      • 250ms worked great and now the game no longer freezes. Thanks again for your hard work in perfecting this product!

  8. Just to confirm, does GDMenu display the correct FW? I’ve followed the update instructions, including the FW for older models, on my GDemu from 14/9/9 and everything went as it should however it’s still displaying 5.1. I just want to confirm before I start trying a reflash

    • Don’t try to “reflash” the update, it won’t work. Make sure your GDMenu version is 0.6 and that you are reading the correct line. If in doubt post a screenshot.

      • Thank you for the help ! I was using an old version which ironically was version 5.1, the same version # as the GDemu update I was trying to update from, and that’s what was being displayed at the bottom right of the menu. I updated GDMenu and verified I the 5.20.1 update was properly installed by going into the proper menu.

        Thanks again for your help and your fantastic products!

  9. Hey GDEMU. Mine is has a date stamped on the device itself of 2017-09-01 do i need to follow this update or can I just use the current one you have listed on the update page?

  10. To GDEMU, Unfortunately after being told that my job was safe, I was laid off yesterday, so I wont be able to buy a GDEMU this round. I hope to get in an order next time if I find a new job.
    Please give my place in line to someone else.
    Thanks

  11. Can someone help me? I did something stupid and tried to update to 5.20.3 BEFORE doing the FW Update first (yes, I misread the update instructions). It didn’t work so I went back and did the FW Update and then 5.20.3 again. This time it will boot back into GDMENU and it shows a FW of 5.20.3, but now half of my games won’t load. Did I brick my GDEMU?

  12. Nevermind. I saw a comment to disable image tests and now they’re all working again. Whew.

  13. So I updated the firmware (after some minor issues) and for the most part it works just fine except if the SD card is plugged in when I turn on the Dreamcast it won’t boot GDMENU and the system becomes frozen on the Dreamcast logo. I have to leave the card unplugged when powering on the Dreamcast and once the BIOS screen is loaded then I can insert the card and GDMENU will boot up fine and all my games will play with no issues. Is there something I’m supposed to do on the new firmware to get GDMENU to boot up on power-on with the SD card inserted? Thanks.

  14. It says on the blog “IMPORTANT: Devices shipped prior to 2020 and running on FW older than 5.20.0 require a special update to be applied first. Read this blog entry for more details” my fw version is 5.15.0 so its pre 5.20 so where is this special update to be applied first?? Ive tried applying the latest update and its a no go it just keeps going to the gdemu bios like normal. even though ive followed the steps listed here. thanks

    • If you can’t find the update then you didn’t read the text carefully enough. And yet that didn’t stop you from ignoring the warning and flashing 5.20 anyway?

      I already regret making that new FW public again…

      • GDEmu, i think it may be beneficial to maybe make a brand new post dedicated to those people who are waiting for your pre-2020 boot-loader file? It seems theres still a few people not reading your posts clearly enough. Do you have a rough timeframe for the release of the boot-loader for us older GDEmus? Thanks for evrrything!

Comments are closed.