Welcome guest, is this your first visit? Click the "Create Account" button now to join.
Page 1 of 2 12 LastLast
Results 1 to 10 of 11
  1. #1
    Junior Member
    Join Date
    Jun 2019
    Location
    UK
    Posts
    5
    Rep Power
    0

    Default Zumo 590/595 Boot Logo

    Unlike previous Zumo models, it's not officially possible to change the Splash Screen at startup. However, since different Splash Screens DO exist (eg: BMW, Harley Davidson, and Touratech have different splash screens from the standard Garmin one) if we knew where these were located, perhaps it would be possible to change them.

    When I updated a Harley Davidson 590 to the Garmin 595 firmware (there is no HD version of the 595), the splash screen changed. Originally it shows the Harley Davidson logo, and after the upgrade, surprisingly NOT the Garmin splash screen, but a tine white square containing the words "GIR Low Mem". That suggests the splash screen is not in the firmware file itself, but the firmware instructs the Garmin to display a file from elsewhere, and as the Garmin one is not on the device, it can't find it, and doesn't know about the HD Logo. Whatever the splash image is, I can't find it, so I'm guessing it's contained within another file - a .bin file perhaps? Perhaps the GarminDevice.xml file tells it where to get the splash image? Has anyone looked at this in detail, as I'd like the Zumo to display something after the 595 upgrade, other than the little white square.....

    Following what is done at [Only registered and activated users can see links. ] I used the RGN Tool to save the regions from the original HD firmware as .bin files from the .GCD, and used GIR Editor to look at the 4 .bin files to see what was there.

    In boot.bin no graphics found
    In fw1_resources.bin no graphics found
    In unknown.bin many found, but neither the HD Logo graphic nor the standard Garmin one
    In fw_all.bin many found, but neither the HD Logo graphic nor the standard Garmin one

    I think (though I know little about programming!) that these boot splash screens don't reside in the firmware files, but elsewhere, and the "GIR Low Mem" might be telling the truth, so it can't load the HD Logo, and the Garmin one isn't on the device. But the hardware has not changed, just the firmware, so why "GIR Low Mem" after the firmware upgrade? The HD Zumo v.330 GCD file is twice the size of the v.460 GCD file too..

    Anyone expert enough to help?
    Last edited by Boki_Srb; 20th November 2020 at 07:19 PM. Reason: approved

  2.    Advertissements


  3. #2
    Master Butters's Avatar
    Join Date
    Jul 2017
    Location
    CA
    Posts
    972
    Rep Power
    142

    Default

    @bert smith
    Are you saying that in those devices the logo splash screen image is not contained in region 16?

  4. #3
    Junior Member
    Join Date
    Jun 2019
    Location
    UK
    Posts
    5
    Rep Power
    0

    Default

    Well, I believe that's the case, Butters - but only because there seem to be no graphics found in boot.bin by the GIR editor. (May be nonsense on my part though!)

    Another thought - maybe the HD logo IS somewhere, but boot.ini allocates a lower amount of GIR memory in the 595 firmware, and there's not enough allocated to allow it to be displayed. I guess we need someone who understands boot.ini to say if that's possible....
    Last edited by Boki_Srb; 21st November 2020 at 07:47 PM. Reason: merged 2 posts, approved

  5. #4
    Master Butters's Avatar
    Join Date
    Jul 2017
    Location
    CA
    Posts
    972
    Rep Power
    142

    Default

    Well, maybe i don't ask the question directly enough. As far as i know for Western Garmin devices there has not been an instance of the logo splash screen image contained in RGN/GCD firmware files, afaik certainly not in the ramloader aka "boot.bin" (which i'm assuming you meant by "boot.ini") or any other fw components meant to be flashed to other regions such as 14, 127, or 158 if populated. Those factory-loaded images which are displayed during starting are contained in rgn16 (hex 0x10). Some devices allow a change of splash screen image from within the device's setting menu but that doesn't change any other data in rgn16 which may be crucial to properly displaying the splash screen and if the device has been cross-flashed there is sometimes no way for the device to load from region 16 on boot-up. That results in display of a blank screen, sometimes with a small error message, rather than the usual splash image(s).

    So have you tried with either HD 590 or zumo 595 or both to dump rgn16 with Ldr.bin and 'rrgn' text command and then examining the dump in GIR_Editor? It may be that the HD logo data still contained in rgn16 is incompatible with the zumo 595 firmware and so no image is displayed. Some conversions such as nuvi 37x0 to 34x0 also require a change of logo file, so that problem isn't without precedent.

  6. #5
    Junior Member
    Join Date
    Jun 2019
    Location
    UK
    Posts
    5
    Rep Power
    0

    Default

    Thanks Butters.

    > "boot.bin" (which i'm assuming you meant by "boot.ini")

    I did mean, boot.bin, sorry!

    > Some devices allow a change of splash screen image from within the device's setting menu

    Earlier Zumos did, the 590/595 doesn't

    > if the device has been cross-flashed there is sometimes no way for the device to load from region 16 on boot-up.

    If I flash a Garmin Zumo 590 with the 595 firmware, it still displays the standard Garmin boot logo, so I suspect that even with the 595 firmware, it still loads from region 16 if that's where the Logo is. Only with the HD 590 does it change to the small error message after flashing. (The HD Zumo 590 and the Garmin Zumo 590 have the same HW ID.)

    > So have you tried with either HD 590 or zumo 595 or both to dump rgn16 with Ldr.bin and 'rrgn' text command and then examining the dump in GIR_Editor? It may be that the
    > HD logo data still contained in rgn16 is incompatible with the zumo 595 firmware and so no image is displayed. Some conversions such as nuvi 37x0 to 34x0 also require a change
    > of logo, so that problem isn't without precedent.

    That sounds possible! But you are dealing with a stupid newbie here! :-) Can you tell me how to dump rgn16 with Ldr.bin and 'rrgn' text command, please? When I load the .GCD file into the RGN Tool, I don't see that region.

    Spoiler: Image
    [Only registered and activated users can see links. ]
    Last edited by bert smith; 22nd November 2020 at 12:55 PM.

  7. #6
    Master Butters's Avatar
    Join Date
    Jul 2017
    Location
    CA
    Posts
    972
    Rep Power
    142

    Default

    Quote Originally Posted by bert smith View Post
    .............
    If I flash a Garmin Zumo 590 with the 595 firmware, it still displays the standard Garmin boot logo, so I suspect that even with the 595 firmware, it still loads from region 16 if that's where the Logo is. Only with the HD 590 does it change to the small error message after flashing. (The HD Zumo 590 and the Garmin Zumo 590 have the same HW ID.)
    That seems to confirm what i was suggesting, that the zumo 595 operating firmware is not playing nicely with the data in rgn16 of the HD 590 (which has a different logo splash than zumo 590/595. It seems the likely cure will be to flash the Garmin logo splash to replace the HD one.

    > So have you tried with either HD 590 or zumo 595 or both to dump rgn16 with Ldr.bin and 'rrgn' text command and then examining the dump in GIR_Editor? It may be that the
    > HD logo data still contained in rgn16 is incompatible with the zumo 595 firmware and so no image is displayed. Some conversions such as nuvi 37x0 to 34x0 also require a change
    > of logo, so that problem isn't without precedent.

    That sounds possible! But you are dealing with a stupid newbie here! :-) Can you tell me how to dump rgn16 with Ldr.bin and 'rrgn' text command, please?
    Ok, baby steps then:
    1. What you need to do is dump the 'standard' Garmin logo from a virgin zumo 590 or 595 and it sounds like you have a zumo 590 available, correct?
    2. You should also make a copy of the HD 590's logo in case things don't work out and you need to restore it.
    3. You need to flash the zumo 590's logo to the converted device.
    4. You can learn how to make those dumps and flashing using sd card by reading [Only registered and activated users can see links. ] in the thread you linked in your initial post.

    WARNING: If you don't understand the exact procedure please ask before going ahead. You need to use the correct Ldr.bin (boot.bin) depending on how you chose to make your conversion to 595 - i.e., depending on whether you did a hybrid or full firmware conversion. In the former you'd have used the original 490 boot.bin combined with the remained of the 595's fw components. In the latter it's as it sounds, the full (original) fw of zumo 595 would have been flashed to the HD590 which means it's required to use the 595's boot.bin as Ldr.bin in the sd card. From here-on the risk is entirely yours. Any flashing carries risk, non-standard flashing is quite riskier.

    EDIT: I see you added something while i was making this post. Forget about looking for the logo in the firmware. It's in region 16 which isn't normally flashed using a standard fw file.
    Last edited by Butters; 22nd November 2020 at 01:06 PM.

  8. #7
    Junior Member
    Join Date
    Jun 2019
    Location
    UK
    Posts
    5
    Rep Power
    0

    Default

    Was just reading post #91 when you replied. :-)

    I do have a Garmin 590 to play with, yes. (Flashed to 595, but still shows the Garmin Logo)

    I'd really like an HD logo on the HD one, so I guess it may be possible to use a modified one, if the existing one is incompatible with the 595 firmware?

    I won't flash anything until I'm properly certain, so I may be back to ask for advice!

  9. #8
    Master Butters's Avatar
    Join Date
    Jul 2017
    Location
    CA
    Posts
    972
    Rep Power
    142

    Default

    Yes, you can likely extract the HD images from the dumped BIN file and write it to the Garmin BIN using GIR_Editor. I say likely because i'm unaware of the type of images used by those devices and some later types of images aren't able to be saved from BINs with GIR_Editor. This thread gives an example of how to do the image changes in the BIN file: [Only registered and activated users can see links. ] (for general information only).

  10. #9
    Junior Member
    Join Date
    Jun 2019
    Location
    UK
    Posts
    5
    Rep Power
    0

    Default

    OK, at this point I just want to READ the logo, not to flash a new one. Should I delete the xrgn,16,2:/16.bin line from the update.txt file?

    OK, have extracted from both the Garmin and the HD. Both files are 800x480x32, but the Garmin is 10KB in size, while the HD is 25KB. Both are in .png format.

    Would it be accurate to guess, then, that the HD file is too big to display with the 595 firmware? If I can reduce it in (file, not physical) size, it might display?


    Spoiler: large images
    [Only registered and activated users can see links. ]

    [Only registered and activated users can see links. ]



    Edit:

    SUCCESS!!! All sorted, now displaying my reduced size HD Logo on Bootup.

    A million thanks to you Butters!
    Last edited by Boki_Srb; 22nd November 2020 at 07:42 PM. Reason: merged 3 posts

  11. #10
    Important User Zumo 590/595 Boot Logo
    Zumo 590/595 Boot LogoZumo 590/595 Boot LogoZumo 590/595 Boot LogoZumo 590/595 Boot Logo
    osiris4isis's Avatar
    Join Date
    Apr 2012
    Location
    Darkside of the Moon
    Posts
    2,968
    Rep Power
    1209

    Default

    Quote Originally Posted by Butters View Post
    Well, maybe i don't ask the question directly enough. As far as i know for Western Garmin devices there has not been an instance of the logo splash screen image contained in RGN/GCD firmware files, afaik certainly not in the ramloader aka "boot.bin" (which i'm assuming you meant by "boot.ini") or any other fw components meant to be flashed to other regions such as 14, 127, or 158 if populated....

    So have you tried with either HD 590 or zumo 595 or both to dump rgn16 with Ldr.bin and 'rrgn' text command and then examining the dump in GIR_Editor?...
    Region 16 is another region to make a backup of like the nonvol region, no?
    Last edited by Boki_Srb; 22nd November 2020 at 10:51 PM. Reason: quote shortened
    Do not PM me with questions. That's what a forum is for.

 

 

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •