Apply custom images to Ford Convers+

[Solltex]

I only try images from google

[Solltex]

have little problem with background, (in line screen very empty area), try with Pal and Custom BGR very bad, try only image and bin, no bad, but see dots, where problem?

[Gwe89]

have little problem with background, (in line screen very empty area), try with Pal and Custom BGR very bad, try only image and bin, no bad, but see dots, where problem?

I use no pal

[Solltex]

yes, you logo good, maybee photoshop not good images made, I after made logo in photoshop, image save as png. After, Infarview degrease colors, and save as jpg

[Gwe89]

Anyone managed to put any images in main every time I try convers just bootloops

[ronald0001]

Anyone managed to put any images in main every time I try convers just bootloops

if you have bootloop maybe offsets are not correct...i had this with bootlogo/animation

[Gwe89]

Convershacker is showing the logo file offset is D9000 so I don't know what's happening, before moving to D9000 the bgr was saying 0xEFEFEF

Capture.PNG

If I move image to D9000
And it works

screenshot_14-213045.png

[DGAlexandru]

As I already mentioned you in private, you are doing it wrong
Usually CH can detect and show an image even if the instruction for that image doesn't match the offset where the image is... so what seems to work in CH might not work in Convers+.
You've sent me a modified Main Flash with the image you want... so now, I'll try to explain the mess you did

First of all, you said that you want that image to be saved in Main Flash at address 0xDE000.. but the IMAGE FRAME explains that this image is to be found at 0xDE400:

bad image frame.jpg

Next mistake is the offset that tells Convers where it can find the IMAGE FRAME: 0x000E564C

offset of IMAGE FRAME.jpg

Which is 0x5000 less than the REAL offset: Main flash from VBF is written starting from 0x5000 in Main Flash memory of MAC7116.
There is a lot of information about this on this forum and also CH tells you not to forget about this 0x5000 value when you use its functions to create an image.
.. so, after removing the VBF header and adding the missing 0x5000 bytes what do we see at this 0x000E564C offset:

there is no IMAGE FRAME here.jpg

=> Convers will boot-loop as it cannot decode this nonsense (not a "standard" IMAGE FRAME).
The real, correct offset for this IMAGE FRAME is according to this image:

real offset of IMAGE FRAME.jpg

All of the above information is needed only for Convers+, CH would still be able to show an image if these ones were not correct, but CH still needs to have a correct IMAGE FRAME in order to know where to load the image from... and as already explained earlier, this instructs to go to 0xDE400 and load from there .. till offset of IMAGE FRAME. Let's see what we find at 0xDE400:

000DE400 offset.jpg

lots of 0xEF ... and we have a Winner! ... We now know why the BGR offset is 0xEFEFEFEF
What is actually our real offset for IMAGE HEADER:

real offset of IMAGE HEADER.jpg

.. again the problem with that 0x5000 first bytes of Main Flash that aren't taken into consideration. The other 0x400 bytes are because, maybe, you used the IMAGE FRAME from an image that had its own BGR... we might never know, as even if you request for help and are asked to say what you are trying to do and how, you never explain it to us ... as like you are above us and we don't deserve such details.
Also, this IMAGE HEADER is not a standard one... so, again, without you explaining the steps you did, I cannot find an explanation on why you used a non-standard one.

Later Edit:
Acually this IMAGE is missing its IMAGE HEADER.. Adding a standard one seems to be a good step in making CH show an image that can be understood - a Ford logo.. but still a dizzy image - probably the IMAGE bytes are not in a correctly 4-byte alligned format...

[Gwe89]

As I already mentioned you in private, you are doing it wrong
Usually CH can detect and show an image even if the instruction for that image doesn't match the offset where the image is... so what seems to work in CH might not work in Convers+.
You've sent me a modified Main Flash with the image you want... so now, I'll try to explain the mess you did

First of all, you said that you want that image to be saved in Main Flash at address 0xDE000.. but the IMAGE FRAME explains that this image is to be found at 0xDE400:
bad image frame.jpg
Next mistake is the offset that tells Convers where it can find the IMAGE FRAME: 0x000E564C
offset of IMAGE FRAME.jpg
Which is 0x5000 less than the REAL offset: Main flash from VBF is written starting from 0x5000 in Main Flash memory of MAC7116.
There is a lot of information about this on this forum and also CH tells you not to forget about this 0x5000 value when you use its functions to create an image.
.. so, after removing the VBF header and adding the missing 0x5000 bytes what do we see at this 0x000E564C offset:
there is no IMAGE FRAME here.jpg
=> Convers will boot-loop as it cannot decode this nonsense (not a "standard" IMAGE FRAME).
The real, correct offset for this IMAGE FRAME is according to this image:
real offset of IMAGE FRAME.jpg

All of the above information is needed only for Convers+, CH would still be able to show an image if these ones were not correct, but CH still needs to have a correct IMAGE FRAME in order to know where to load the image from... and as already explained earlier, this instructs to go to 0xDE400 and load from there .. till offset of IMAGE FRAME. Let's see what we find at 0xDE400:
000DE400 offset.jpg
lots of 0xEF ... and we have a Winner! ... We now know why the BGR offset is 0xEFEFEFEF
What is actually our real offset for IMAGE HEADER:
real offset of IMAGE HEADER.jpg
.. again the problem with that 0x5000 first bytes of Main Flash that aren't taken into consideration. The other 0x400 bytes are because, maybe, you used the IMAGE FRAME from an image that had its own BGR... we might never know, as even if you request for help and are asked to say what you are trying to do and how, you never explain it to us ... as like you are above us and we don't deserve such details.
Also, this IMAGE HEADER is not a standard one... so, again, without you explaining the steps you did, I cannot find an explanation on why you used a non-standard one.

Later Edit:
Acually this IMAGE is missing its IMAGE HEADER.. Adding a standard one seems to be a good step in making CH show an image that can be understood - a Ford logo.. but still a dizzy image - probably the IMAGE bytes are not in a correctly 4-byte alligned format...

I made the image with CH so the 00 0D E4 00 is not what I have put into the image, I made the image for address DE000 I put at address DE000 without vbf header put the pointer address what convershacker says and I just get bootloop,


(as like you are above us and we don't deserve such details.)? What's rattled your cage I'm only asking for help ain't this what the forum is about?

[Gwe89]

now i understand the missing 0x5000 bytes things work i only needed help we all miss things and make mistakes dint need a whole assay to where i went wrong, you also state convershacker reminds about these 0x5000 bytes i get no such message coming up