Welcome guest, is this your first visit? Click the "Create Account" button now to join.
Page 3 of 5 FirstFirst 12345 LastLast
Results 21 to 30 of 49
  1. #21
    Master
    Join Date
    Feb 2011
    Location
    Sofia
    Age
    31
    Posts
    919
    Rep Power
    213

    Default

    @ snehne

    No problem. Although I would feel better if you succeed. I don't like making things unfinished.

    As I wrote the logo starts with "GARMIN BITMAP 01". Search for that string in Hex and you will find it. I will give link to an image to show you how it looks in hex. In my opinion you should experiment merging the logo header (look at the attached image) with 480x272 BMP RGB 565 and flash. I am not sure about the footer. Also I have a feeling the 6xx series use only one image in the logo so probably no need for footer. Don't know. Of course this is better. For example in the logo of 2x5w series the logo have 2 images and in 13xx series 4 images. Look at the topic of RGN_Tool (page 20) on gpspassion. Turbo there have explained very good the meaning of the header etc. I can't give link to a topics in a neighbour forum as it is forbiden here. So you should find it your self.

    Hope it is helpful,

    Code:
    Please Login or Register to see the links
    Last edited by ddabcd277; 9th April 2011 at 20:27.

  2.    Advertissements


  3. #22
    Member snehne's Avatar
    Join Date
    Apr 2011
    Location
    USA
    Posts
    24
    Rep Power
    0

    Default

    updates --

    * with all the instructions/examples I finally managed to produce 480x272 logo bin files that can be loaded and modified by GIR_Editor. I actually created two versions: one with a single image, and the other with 2 images. Both can be loaded onto the 660, and both showed the correct boot-up image.

    * What I did was simply putting the header and the bmp(s) together, filled it up with FF, and with a dummy checksum byte; the I loaded into GIR_Editor, replaced the image, and saved -- the tool will produce the right checksum.

    * However, It now seems that there are two display steps , one for boot-up, and one for initialization and USB connection mode. The first one is now all correct. But the second one is still messed up -- It looks like that every line gets left shifted by a pixel or two compared with the previous line. With the 2 image version (both images the same) the second display also has a very dark blue overlay (the twisted imaged was barely visible). This looks like it is trying to display a e.g. 478x272 image into 480x272; each line eats a couple more pixels from the next line the the previous line.

    * Moreover, with the single image version, I can change the splash image via the "display" setting (previously frozen); it works, but again, only the first display is good; the second one is the shifted/twisted version of the first one. With the two image version, this would freeze as before.

    * So it seems that a single image is correct (no freeze, replaceable); however it seems that the logo bin file needs some extra information, probably at the end of the image file (I think my 2-image version was not right, but the bytes after the image made some difference).

    * The problem of GIR_Editor with the "original" logo.bin was the incorrect size of the bmp (the header has the right size which is 480x272x2, but the image seems larger). But that one (despite garbled) shows up the same way for both display steps. So there is something right about the "wrong" size ...

  4. #23
    Member TCIII's Avatar
    Join Date
    Apr 2010
    Location
    usa
    Posts
    23
    Rep Power
    14

    Default

    Seems you are getting close......especially being able to change splash.........thanks for the update.....maybe someone will come up with an original 660 logo.bin

    We will both be happy

  5. #24
    Master Thefatboy's Avatar
    Join Date
    May 2009
    Location
    Thailand
    Posts
    204
    Rep Power
    237

    Default

    I have a complete back up from a new zumo 660 I sold, what file and in what folder is it that you want?
    Happy it sunny Thailand

  6. #25
    Master
    Join Date
    Feb 2011
    Location
    Sofia
    Age
    31
    Posts
    919
    Rep Power
    213

    Smile

    @ snehne
    The puzzle seems chalenging Unfortunately I am at work now and don't have the proper tools but when I come back home I will try to think of something. Can you upload your logo bin file you have created merging header and bmp 480x272? I want to look at it also. BTW did you see the dumps I have uploaded in the previous posts from where I have extracted the two splashes? Probably I have messed something while extracting.

    * I saw you asked in the GIR Editor topic about templates. Here what I have found and gathered in one place:
    nuvi 2xx, 2xxw, 660, 670, 360 Mini, SP c5xx splash screens I have extracted from the PouchX dumps. Haven't tested them. Don't know is there problem with them also. Use them at your own risk!

    etrex HC, nuvi 2x5, 2x5w and 1xxx series splash screens I have read people write that there is no problem with them:
    [Only registered and activated users can see links. ]

    I also read that some of the splash screens are also compatible with other models for example the splash screen of 2x5w is compatible with 760. Just the header needs to be corrected with the proper part number.

    Hope this info is helpful,
    Last edited by ddabcd277; 12th April 2011 at 09:31.

  7. #26
    Member snehne's Avatar
    Join Date
    Apr 2011
    Location
    USA
    Posts
    24
    Rep Power
    0

    Default

    @ddabcd277

    I'm out of town now -- will upload the image later this week when I get home.

    The way I put it together was to just take the header out of the logo.bin you extracted from the "PouchX dump" up to the size of the image (the 4 bytes turboccc mentioned in the other thread), and then appended a 480x272 RGB565 image after it; then added a few FF bytes to the end to round the size up. Per turboccc the last byte should be the checksum; being lazy I did not calculate it, rather I just threw in a random byte. Then I loaded it into GIR_editor, which accepted it; then replaced the image with another 480x272 (actually the same one), and save it -- GIR_editor seems to calculate the correct checksum in the course.

    This followed the recipe turboccc posted on the other forum. This may not be exactly what the 660 wants (looks like not) but this is how GIR_Editor accepts.

    BTW I compared your extraction with the larger bin file, and you did not seem to break anything; what I didn't understand is where the extraction ended -- if we take turboccc's spec as the rule, then there should be exactly 480x272x2 bytes for the image after the header, followed by some numbers of FF filler bytes (and a byte for checksum). In your logo.bin, the "image" part is larger than 480x272x2 (and that is why GIR_Editor would crash). How did you decide the size?

    Sean

    p.s. Now that I think about it, it could be that I/we did not fully comprehend the meaning of the header. As I said the garbled images all look like images with wrong widths (e.g. if we display a 6x6 image as 9x4, we would have similar effect). So maybe there are some bytes somewhere that specify how the second display should work. I'll try more when I get back.

    p.p.s. I noticed on the other forum that someone also had issue with the second display (being completely dark in his case). And someone noticed that for that device logo.bin contains 2 images (or 4). That is why I tried a 2-image version, to no avail. Note however that I was merely following a GIR_Editor compatible format; that may not be the correct one.
    Last edited by snehne; 12th April 2011 at 22:09.

  8. #27
    Member snehne's Avatar
    Join Date
    Apr 2011
    Location
    USA
    Posts
    24
    Rep Power
    0

    Default

    @Thefatboy

    Thanks. What we need is the complete original firmware (rgn file?) which I believe is not user visible (?) The "update" firmware is not complete (e.g. the logo is not included).

    I suppose there is away to dump the entire firmware but I don't know how.

    Are zumo and nuvi the same?

    Your kindness is appreciated.

    Sean

  9. #28
    Master Thefatboy's Avatar
    Join Date
    May 2009
    Location
    Thailand
    Posts
    204
    Rep Power
    237

    Default

    Quote Originally Posted by snehne View Post
    @Thefatboy

    Thanks. What we need is the complete original firmware (rgn file?) which I believe is not user visible (?) The "update" firmware is not complete (e.g. the logo is not included).

    I suppose there is away to dump the entire firmware but I don't know how.

    Are zumo and nuvi the same?

    Your kindness is appreciated.

    Sean
    You are right there are no rgn files in a complete backup sorry

    The zumo and the nuvi are not the same
    Happy it sunny Thailand

  10. #29
    Member snehne's Avatar
    Join Date
    Apr 2011
    Location
    USA
    Posts
    24
    Rep Power
    0

    Default

    OK, here are the two log files I created:

    [Only registered and activated users can see links. ]

    [Only registered and activated users can see links. ]

    If anyone can improve either into a fully working version, please post. Thanks

  11. #30
    Master
    Join Date
    Feb 2011
    Location
    Sofia
    Age
    31
    Posts
    919
    Rep Power
    213

    Default

    Haven't forget about that. Ok, I downloaded the splashes and will see what I can do. So the problem on the double splash is the second image isn't it? Can you make a shot of the second image how it loads and post it?

    BTW my skype is same as name. If you wish we can comunicate there not to spam this forum with useless chat.

    Cheers,

 

 
Page 3 of 5 FirstFirst 12345 LastLast

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
  •  
This website uses cookies
We use cookies to store session information to facilitate remembering your login information, to allow you to save website preferences, to personalise content and ads, to provide social media features and to analyse our traffic. We also share information about your use of our site with our social media, advertising and analytics partners.