Results 1 to 5 of 5

Thread: Making a .bin

  1. #1
    Senior Member
    Join Date
    Dec 2015
    Posts
    126

    Default Making a .bin

    So I figured some of you have multiple files... Maybe with a jtag read, and they are disorganized. Hopefully this will help you in sorting them together into a single .bin, mainly for .cax development.

    Step 1. Make a giant hex file filled with FF FF for whatever size you need to be (like 4Mb maybe). You can use any hex editor, notepad++ will work.

    Step 2. Find a piece of your read, any piece will do. Then try to find an obvious segment and go to the end of that segment. You will find some bytes that go like this.

    55 55 04 00 41 31 32 36 37 38 32 35 32 41 41 01 00 00 38 80 00 E0 07 00

    Yours will look different, obviously, but it will be at the end of every segment.

    Anyway let's disect this, this contains the part number or software id or whatever you want to call it: 12678252 (31 32 36 37 38 32 35 32). Hopefully this will help you find it if you know the part number.

    After this skip ahead a few bytes to 00 00 38 80 which is an address. Do some byte swapping you will get 80380000. Now this is the address in the ecu, which you don't want so slice off the 80 and you get 380000.

    Step 3: Paste the segment to that address.

    Repeat for each segment. Verify by importing to efi live. Wuhlah, you went from junk to something more reasonable.

    Additionally the bytes immediately following is the size of the segment (in this case,7E000). Make sure your paste is that size. I'm sure this is enough info that you will figure it out.
    Last edited by Snipesy; November 23rd, 2016 at 09:06 PM.

  2. #2
    Lifetime Member GMPX's Avatar
    Join Date
    Apr 2003
    Posts
    13,148

    Default

    Bosch (Tri-Core) stuff is hard because of the dumb $80xxxxxx offset to the real position in the bin....and everything is stored backwards
    I no longer monitor the forum, please either post your question or create a support ticket.

  3. #3
    Senior Member
    Join Date
    Dec 2015
    Posts
    126

    Default

    Endianness was a pretty big mistake... Lititle endian which is what this is, is simpler to do math on (because math is done small side first). But in practice it really doesnt matter. It's just something to add to the pile of complexity...

  4. #4
    Lifetime Member GMPX's Avatar
    Join Date
    Apr 2003
    Posts
    13,148

    Default

    It depends on what you first experienced. I've only known Motorola CPU's since the 80's which of course have numbers in the order that our brains process easier.
    Would you rather pay $00.95 for a chocolate bar or $95.00
    I no longer monitor the forum, please either post your question or create a support ticket.

  5. #5
    Joe (Moderator) joecar's Avatar
    Join Date
    Apr 2003
    Posts
    28,403

    Default

    +1 Motorola for me, hex addresses view easier in big endian as Ross said.

Similar Threads

  1. making tunes
    By lp14255 in forum Duramax 06 LLY / 06+ LBZ & LMM
    Replies: 1
    Last Post: August 25th, 2014, 01:17 PM
  2. Making my own Calc PID
    By andrewjamesbond1 in forum Duramax 06 LLY / 06+ LBZ & LMM
    Replies: 15
    Last Post: June 12th, 2012, 02:04 PM
  3. Making PIDS
    By minytrker in forum General
    Replies: 2
    Last Post: October 16th, 2009, 04:13 AM
  4. Map making question...........
    By FreddyG in forum Gen III V8 Specific
    Replies: 0
    Last Post: November 15th, 2007, 10:06 AM
  5. Making Scripts.
    By 5.7ute in forum Tips and tricks
    Replies: 2
    Last Post: September 12th, 2007, 09:30 AM

Posting Permissions

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