Pages: 1 ... 4 5 [6] 7
Author Topic: ME7Sum: Open Source Checker/Corrector for ME7  (Read 55462 times)
nyet
Administrator
Hero Member
*****

Karma: +385/-42
Online Online

Posts: 8791


WWW
« Reply #75 on: November 25, 2016, 07:26:46 PM »

yes
Logged

ME7.1 tuning guide (READ FIRST)
ECUx Plot
ME7Sum checksum checker/corrrector for ME7.x

Please do not ask me for tunes. I'm here to help people make their own.

Do not PM me technical questions! Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your experience.
Awaken
Jr. Member
**

Karma: +1/-0
Offline Offline

Posts: 45


« Reply #76 on: November 26, 2016, 02:37:51 AM »

Is there a way for Me7Sum to correct this, or is it something it cannot do yet? I read that some RSA support was added.
Thank you!
Logged
nyet
Administrator
Hero Member
*****

Karma: +385/-42
Online Online

Posts: 8791


WWW
« Reply #77 on: November 26, 2016, 02:50:18 AM »

Does it not work?
Logged

ME7.1 tuning guide (READ FIRST)
ECUx Plot
ME7Sum checksum checker/corrrector for ME7.x

Please do not ask me for tunes. I'm here to help people make their own.

Do not PM me technical questions! Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your experience.
Awaken
Jr. Member
**

Karma: +1/-0
Offline Offline

Posts: 45


« Reply #78 on: November 26, 2016, 06:40:14 AM »

Unfortunately not, unless I use it wrong. I do ME7Sum.exe {filename}.bin. The output I just posted 2 posts ago is from ME7Sum, not ME7Check and the output is following (just pasting the problematic areas):

Step #3: Reading RSA signatures ..
 Searching for RSA offset #0...OK
 Searching for RSA offset #1...OK
         Signature: @8ec6a-8ecea
           Modulus: @167c2-16842
          Exponent: @16842 = 3
 Searching for MD5 ranges...OK
 MD5 Block Offset Table @1679e [32 bytes]:
 1) 0x00010002-0x00013FFE
 2) 0x00014252-0x00017F4E
 3) 0x00018192-0x0001FBDC
 4) 0x00026A00-0x0002FFFC
 EncrMD5: b6 87 d5 35 c6 9b 50 b3 d5 c5 1d eb 9a 73 2b 58
 CalcMD5: a1 6b 4d e4 20 39 c5 92 ac c2 ba 43 a9 70 9c c2
 ** NOT OK **

*** Found 70 checksums in asd.ori

*** WARNING! 1/1 uncorrected error(s) in asd.ori! ***

I am attaching the bin in question again. For the function call I had renamed it to asd.bin since it does not accept spaces in file names.

Does it matter if I used the MTX plugin prior to using ME7Sum? Because MTX seems to fix the checksums, just not the RSA.

Thank you for your replies, I appreciate it!


Logged
Awaken
Jr. Member
**

Karma: +1/-0
Offline Offline

Posts: 45


« Reply #79 on: November 26, 2016, 11:48:20 AM »

Actually, I was using it wrong, I was missing the out file. It worked perfectly now.

Still this might turn useful to somebody: don't forget to give an out file name to the command.

Me7Sum.exe in_file.bin out_file.bin
Logged
nyet
Administrator
Hero Member
*****

Karma: +385/-42
Online Online

Posts: 8791


WWW
« Reply #80 on: November 26, 2016, 11:49:26 AM »

Me7Sum.exe in_file.bin out_file.bin

yea, it is in the first post. Literally.
Logged

ME7.1 tuning guide (READ FIRST)
ECUx Plot
ME7Sum checksum checker/corrrector for ME7.x

Please do not ask me for tunes. I'm here to help people make their own.

Do not PM me technical questions! Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your experience.
Awaken
Jr. Member
**

Karma: +1/-0
Offline Offline

Posts: 45


« Reply #81 on: November 26, 2016, 12:50:44 PM »

Smiley Sorry about that, too much information in one piece, some things are bound to slip thru.
Logged
Colt45
Jr. Member
**

Karma: +0/-1
Offline Offline

Posts: 37


« Reply #82 on: May 19, 2017, 04:35:40 PM »

Hi, I tested this file with an 07K ECU (2.5L NA 5cyl from mkV a-platform cars), ME7.1.1, early one that is C167 and not ST10.

I don't intend to use this one for anything so it's not critical ME7Sum supports it, but I thought the data point might be helpful for greater support, I don't know.

I pulled the file off an eBay ECU, maybe someone was in it before, maybe not (case was a bit mangled)

can attach the files if any interest.

############


$ ./me7check.exe ../ori/07k/07K906032_0261208870_377692.bin
==============================================================================
me7check v1.12 (c) mki, 06/2004-05/2012
Checking file ../ori/07k/07K906032_0261208870_377692.bin (size=1048576)
Reading Version Strings...
-> Bootrom Version = embedded in CPU, asume 06.02/06.05
-> EPK = 45/1/ME7.1.1/120/C1103B//24M/A4A05M50/110705/
-> Contents of ECUID data table:
   - '0261208870'         (SSECUHN)
   - '1037377692'         (SSECUSN)
   - '07K906032   '       (VAG part number)
   - '7826'               (VAG sw number)
   - 'R5 AT          '    (engine id)
-> Contents of ECUID data table:
   - 'HW_MAN004'


-> No errors found. File is OK.   *********************



#############

$ ./me7sum.exe ../ori/07k/07K906032_0261208870_377692.bin fixed.bin
ME7Tool (v1.0.3) [Management tool for Bosch ME7.x firmwares]
Inspiration from Andy Whittaker's tools and information.
Written by 360trev and nyet [BSD License Open Source].

Attempting to open firmware file '../ori/07k/07K906032_0261208870_377692.bin'

Step #1: Reading ROM info ..
 Searching for EPK signature...OK
 Searching for ECUID table...0 matches, missing
Step #1: ERROR! Skipping ROM info.. UNDEFINED

Step #2: Reading ROMSYS ..
 Startup section: word[0x008000]+word[0x00FFFE]
 @008038 Add=0x00AFB7 CalcAdd=0x00AFB7  ADD OK
 Program pages: 8k page first+last in 0x0000-0xFFFF and 0x20000-0xFFFFF
 @00803c Add=0x74A1A1 CalcAdd=0x74A1A1  ADD OK
 All param page: word[0x010000]+word[0x01FFFE]
 @01e814 Add=0x00971D CalcAdd=0x00971D  ADD OK

Step #3: Reading RSA signatures ..
 Searching for RSA offset #0...OK
 Searching for RSA offset #1...OK
         Signature: @c8d10-c8d90
           Modulus: @16830-168b0
          Exponent: @168b0 = 3
 Searching for MD5 ranges...OK
 MD5 Block Offset Table @1680c [32 bytes]:
 1) 0x00010002-0x00013FFE
 2) 0x00014502-0x00017EFE
 3) 0x00018192-0x0001FBDC
 4) 0x00026A00-0x0002FFFC
 EncrMD5: 17 c4 3f 60 e4 c3 21 e0 8d 7e 31 45 07 18 ae 35
 CalcMD5: 17 c4 3f 60 e4 c3 21 e0 8d 7e 31 45 07 18 ae 35
  OK

Step #4: Finding CRC table(s) ..
 Searching for CRC table(s)...missing
 Searching for CRC table(s) using fallback...*** WARNING: ASM detect failed, fell back (found 0) in ../ori/07k/07K906032_0261208870_377692.bin
OK
Step #4: ERROR! Couldn't find CRC table(s)

Step #5: Reading Main Data Checksums ..
 Searching for main data CRC pre block...missing
 Searching for main data CRC/csum blocks...OK
 Searching for main data CRC offsets...missing
 Searching for main data checksum offsets...OK
 Main Checksums:
 1) 0x010002-0x013FFE CalcCSM: 0013FFA9
 2) 0x014502-0x017EFE CalcCSM: 002B08FC
 3) 0x018192-0x01FBDC CalcCSM: 004A8ADD
 4) 0x026A00-0x02FFFC CalcCSM: 00AA0926
 @c9556 CSM: 00AA0926 CalcCSM: 00AA0926  Main data checksum OK

Step #6: Reading Main Program Checksums ..
 Searching for main program checksum..OK
 ROM Checksum Block Offset Table @294f8 [16 bytes]:
 1) 0x000000-0x00FBFF CalcChk: 4672F6E7
    0x00FC00-0x01FFFF CalcChk: 24A071FC CalcCRC: 46DB0B62 SKIPPED
 2) 0x020000-0x0FFFFF
    <fffe0>  Chk: 16C1A373 CalcChk: 16C1A373 OK (i)

Step #7: Reading Multipoint Checksum Blocks ..
 Searching for multipoint block descriptor #1...missing
 Searching for multipoint block descriptor #2...OK
 1) <1fbde>  0x000000-0x003FFF Chk: 0E59D5C8 Boot: (whitelisted) OK
 2) <1fbee>  0x004000-0x007FFF Chk: 1077FB35 Boot: (whitelisted) OK
 3) <1fbfe>  0x000000-0x003FFF Chk: 10942779 CalcChk: 10942779 OK
 4) <1fc0e>  0x004000-0x007FFF Chk: 0E83C050 CalcChk: 0E83C050 OK
 Multipoint #2: [66 blocks x <16> = 1056 bytes]

*** Found 70 checksums in ../ori/07k/07K906032_0261208870_377692.bin

*** ABORTING! 2 uncorrectable error(s) in ../ori/07k/07K906032_0261208870_377692.bin! ***

Logged
nyet
Administrator
Hero Member
*****

Karma: +385/-42
Online Online

Posts: 8791


WWW
« Reply #83 on: July 22, 2017, 12:17:58 PM »

v1.0.5 is released; hopefully making it so you don't have to re-run me7sum several times on the same file

http://nyetwurk.github.io/ME7Sum/downloads/me7sum-v1.0.5.zip
« Last Edit: July 24, 2017, 11:32:30 PM by nyet » Logged

ME7.1 tuning guide (READ FIRST)
ECUx Plot
ME7Sum checksum checker/corrrector for ME7.x

Please do not ask me for tunes. I'm here to help people make their own.

Do not PM me technical questions! Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your experience.
nyet
Administrator
Hero Member
*****

Karma: +385/-42
Online Online

Posts: 8791


WWW
« Reply #84 on: July 24, 2017, 11:34:08 PM »

can attach the files if any interest.

Go for it. No guarantees I can make it work but I can try
Logged

ME7.1 tuning guide (READ FIRST)
ECUx Plot
ME7Sum checksum checker/corrrector for ME7.x

Please do not ask me for tunes. I'm here to help people make their own.

Do not PM me technical questions! Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your experience.
Arti
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 4


« Reply #85 on: January 03, 2018, 12:46:26 AM »

Hi,
me7.5 file 1mb from winols (checksum calculated with winols 2.24) and after using ME7sum I get

Step #3: Reading RSA signatures ..
 Searching for RSA offset #0...missing
 Searching for RSA offset #1...missing

Searching for main data checksum offsets...missing RSA offset

finally program write
*** Found 71 checksums in v1.bin
*** DONE! 0/0 error(s) in v1.bin corrected in v1corr.bin! ***

but v1corr.bin file doesn't exist

Just to be sure: everything is ok file is not created because input file is 100% ok? (checksum in the file)?
"Missing..." is not an error?
Arti
Logged
nyet
Administrator
Hero Member
*****

Karma: +385/-42
Online Online

Posts: 8791


WWW
« Reply #86 on: January 03, 2018, 01:26:53 PM »

RSA not found is fine, it means there's no RSA to correct.

As to your other issue, it looks like an actual bug. Thanks for reporting it!
Logged

ME7.1 tuning guide (READ FIRST)
ECUx Plot
ME7Sum checksum checker/corrrector for ME7.x

Please do not ask me for tunes. I'm here to help people make their own.

Do not PM me technical questions! Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your experience.
360trev
Full Member
***

Karma: +17/-1
Offline Offline

Posts: 111


« Reply #87 on: August 24, 2018, 12:12:00 AM »

@ nyet

I've been doing some more work on the checksumming code recently as part of my recent bit of time to explore again.

After some more time analyzing the main rom checksums (byte-summing) I noted we inherited the use of 'hardcoded locations' to identify where it is. This isn't really the best approach. Also we always assume there are only 2 sections (since for most roms this is the case, however its not always so, i've found some with 3). This means with these updates for instance it ME7Sum can work to checksum Alfa's too Smiley

So I'm using the needle/mask approach to identify the rom sum function itself...



#define SKIP    0x00
#define XXXX    0x00
#define YYYY    0x00
#define MASK    0xff

//
// this is the needle (masked) for the Main Checksum function to extract Start Address and End Address then extract the segment offset function and the hi/lo words directly out of the code..
//

const unsigned char needle_2[] = {
 0xF6, 0x8E, XXXX, XXXX,     // mov  var_x, zeros
 0xF6, 0x8E, XXXX, XXXX,     // mov  var_x, zeros
 0xF7, 0x8E, XXXX, XXXX,     // movb var_x, zeros
 
 0xD7, 0x50, XXXX, XXXX,     // extp #XXXXh, #2       <--- * this is the segment offset
 0xF2, XXXX, YYYY, YYYY,     // mov  rX, var_y        <--- * this is the offset to the [checksum_1_hi] word (start address for main rom)
 0xF2, XXXX, YYYY, YYYY,     // mov  rX, var_y        <--- * this is the offset to the [checksum_1_lo] word (start address for main rom)
 0xF6, YYYY, XXXX, XXXX,     // mov  var_x, rY
 0xF6, YYYY, XXXX, XXXX,     // mov  var_x, rY
 
 0xE1, 0x18,                 // movb r14, #1
 0xF7, YYYY, XXXX, XXXX,     // movb var_x, rY

 0xD7, 0x50, XXXX, XXXX,     // extp #XXXXh, #2       <--- * this is the segment offset (typically 0x206 or 0x207)
 0xF2, XXXX, YYYY, YYYY,     // mov  rX, var_y        <--- * this is the offset to the [checksum_2_hi] word (end address for main rom)
 0xF2, XXXX, YYYY, YYYY,     // mov  rX, var_y        <--- * this is the offset to the [checksum_2_lo] word (end address for main rom)
 0xF6, YYYY, XXXX, XXXX,     // mov  var_x, rY
 0xF6, YYYY, XXXX, XXXX,     // mov  var_x, rY

 0xDB, 0x00                  // rets
};

const unsigned char mask_2[] = {
 MASK, MASK, SKIP, SKIP,     // mov  var_x, zeros
 MASK, MASK, SKIP, SKIP,     // mov  var_x, zeros
 MASK, MASK, SKIP, SKIP,     // movb var_x, zeros
 
 MASK, MASK, SKIP, SKIP,     // extp #206h, #2       // memory offset selection
 MASK, SKIP, SKIP, SKIP,     // mov  rX, var_y        // ***checksum1_hi***
 MASK, SKIP, SKIP, SKIP,     // mov  rX, var_y        // ***checksum1_lo***
 MASK, SKIP, SKIP, SKIP,     // mov  var_x, rY           // to ram address1_hi
 MASK, SKIP, SKIP, SKIP,     // mov  var_x, rY         // to ram address1_lo
 
 MASK, MASK,                 // movb r14, #1          // set boolean on
 MASK, SKIP, SKIP, SKIP,     // movb var_x, rY         // actually set variable

 MASK, MASK, SKIP, SKIP,     // extp #206h, #2       // memory offset selection
 MASK, SKIP, SKIP, SKIP,     // mov  rX, var_y        // ***checksum2_hi***
 MASK, SKIP, SKIP, SKIP,     // mov  rX, var_y        // ***checksum2_lo***
 MASK, SKIP, SKIP, SKIP,     // mov  var_x, rY         // to ram address2_hi
 MASK, SKIP, SKIP, SKIP,     // mov  var_x, rY         // to ram address2_lo
 
 MASK, MASK                  // rets
};



(pm me and I can send you the code which does this). And this is what the output looks like...




Opening '0261206715_SW127735611_VER_10A0Xw00_ME731_9_613_3_Alfa.bin' file
Succeded loading file.

>>> Scanning for Main ROM Checksum sub-routine #1 [to extract Start/End regions]
main checksum byte sequence #1 found at offset=0x6f7ec.

Main Region Block #1:
        lo:0x1d054 hi:0x1d056 (seg: 0x207 phy:0x81d054) : 0x800000
        lo:0x1d058 hi:0x1d05a (seg: 0x207 phy:0x81d058) : 0x80fe6d sum=4bcae83a ~sum=b43517c5 : acc_sum=0
Main Region Block #2:
        lo:0x1d05c hi:0x1d05e (seg: 0x207 phy:0x81d05c) : 0x820000
        lo:0x1d060 hi:0x1d062 (seg: 0x207 phy:0x81d060) : 0x837fff sum=63b0207e ~sum=9c4fdf81 : acc_sum=4bcae83a
Main Region Block #3:
        lo:0x1d064 hi:0x1d066 (seg: 0x207 phy:0x81d064) : 0x840000
        lo:0x1d068 hi:0x1d06a (seg: 0x207 phy:0x81d068) : 0x87ffff sum=c350f52 ~sum=f3caf0ad : acc_sum=af7b08b8

Final Main ROM Checksum calculation:  0xbbb0180a (after 3 rounds)
Final Main ROM Checksum calculation: ~0x444fe7f5

Logged
360trev
Full Member
***

Karma: +17/-1
Offline Offline

Posts: 111


« Reply #88 on: August 24, 2018, 12:17:09 AM »

And you can also use the same needle/mask approach to identify the location where these main rom checksums should end up going...



>>> Scanning for Main ROM Checksum sub-routine #2 [to extract stored checksums and locations in ROM]
main checksum byte sequence #2 block found at offset=0x6f894.

Stored Main ROM Block Checksum:
        lo:0x7ffe0 hi:0x7ffe2 (seg: 0x21f phy:0x87ffe0) : 0xbbb0180a
Stored Main ROM Block ~Checksum:
        lo:0x7ffe4 hi:0x7ffe6 (seg: 0x21f phy:0x87ffe4) : 0x444fe7f5

MAIN STORED ROM  CHECKSUM: bbb0180a ? bbb0180a : OK!     ~CHECKSUM: 444fe7f5 ? 444fe7f5 : OK!



Here's the needle I use for this ...




//
// this is the needle (masked) for the Main Checksum function to extract the stored checksum Hi & Lo Words
//

const unsigned char needle_3[] = {

 0xF2, 0xF4, XXXX, XXXX,     // mov r4, var_Y
 0xF2, 0xF5, XXXX, XXXX,     // mov r5, var_Y
 0xD7, 0x50, 0x1f, 0x02,    // extp #21fh, #2                <--- * this is the segment offset (should be 0x21f - LAST SEGMENT IN 512Kbyte ROM)
 0x22, 0xF4, XXXX, XXXX,    // sub r4, var_Y                 <--- * this is offset to the [EndFirmware_hi] word (stored checksum)
 0x32, 0xF5, XXXX, XXXX,    // subc r5, var_Y                <--- * this is offset to the [EndFirmware_lo] word (stored checksum)
 0x3D, XXXX,                 // jmpr cc_NZ, offset_XXXX
 
 0xE6, 0xF4, XXXX, XXXX,     // mov r4, #XXXXh
 0xE6, 0xF5, XXXX, XXXX,     // mov r5, #XXXXh
 0xDC, 0x45,                 // extp r5, #1
 0xA9, 0x64,               // movb r13, [r4]
 0x77, 0xF6, 0x08, 0x00,     // orb  r13, #8
 0xE6, 0xF4, XXXX, XXXX,     // mov  r4, #XXXXh
 0xE6, 0xF5, XXXX, XXXX,     // mov  r5, #XXXXh
 0xDC, 0x45,                 // extp r5, #1
 0xB9, 0x64,                 // mov [r4], r13
 0x0D, 0x0E                  // jmpr cc_UC, +0xE
};

const unsigned char mask_3[] = {

 MASK, MASK, SKIP, SKIP,     // mov r4, var_Y
 MASK, MASK, SKIP, SKIP,     // mov r5, var_Y
 MASK, MASK, MASK, MASK,    // extp #21fh, #2                <--- * this is the segment offset (should be 0x21f - LAST SEGMENT IN 512Kbyte ROM)
 MASK, MASK, SKIP, SKIP,    // sub r4, var_Y                 <--- * this is offset to the [EndFirmware_hi] word (stored checksum)
 MASK, MASK, SKIP, SKIP,    // subc r5, var_Y                <--- * this is offset to the [EndFirmware_lo] word (stored checksum)
 MASK, SKIP,                 // jmpr cc_NZ, offset_XX
 
 MASK, MASK, SKIP, SKIP,     // mov r4, #XXXXh
 MASK, MASK, SKIP, SKIP,     // mov r5, #XXXXh
 MASK, MASK,                 // extp r5, #1
 MASK, MASK,               // movb r13, [r4]
 MASK, MASK, MASK, MASK,     // orb  r13, #8
 MASK, MASK, SKIP, SKIP,     // mov  r4, #XXXXh
 MASK, MASK, SKIP, SKIP,     // mov  r5, #XXXXh
 MASK, MASK,                 // extp r5, #1
 MASK, MASK,                 // mov [r4], r13
 MASK, MASK                  // jmpr cc_UC, +0xE
};



Logged
360trev
Full Member
***

Karma: +17/-1
Offline Offline

Posts: 111


« Reply #89 on: August 24, 2018, 07:45:37 AM »

And ofcourse you can also do this for the multipoint checksum blocks too.. tried it on a 1mb (rather than 512kbyte) file I downloaded from the ecu dump section on here for file 06A906032DS 0261207080 360930.

It reveals 66 multipoint checksums on a 1mb file that need correcting. I noted my code match for finding end of rom failed to find end of 1mb file.. I need to investigate that now... but it did find ALL of the multipoints with my new code..


 Opening '06A906032DS 0261207080 360930' file
Succeded loading file.

>>> Scanning for Main ROM Checksum sub-routine #1 [to extract Start/End regions]
main checksum byte sequence #1 found at offset=0x880b8.

Main Region Block #1:
        lo:0x1dfc0 hi:0x1dfc2 (seg: 0x207 phy:0x81dfc0) : 0x800000
        lo:0x1dfc4 hi:0x1dfc6 (seg: 0x207 phy:0x81dfc4) : 0x80fbff sum=48cf9ca6 ~sum=b7306359 : acc_sum=0
Main Region Block #2:
        lo:0x1dfc8 hi:0x1dfca (seg: 0x207 phy:0x81dfc8) : 0x820000
        lo:0x1dfcc hi:0x1dfce (seg: 0x207 phy:0x81dfcc) : 0x8fffff sum=4851122c ~sum=b7aeedd3 : acc_sum=48cf9ca6

Final Main ROM Checksum calculation:  0x9120aed2 (after 2 rounds)
Final Main ROM Checksum calculation: ~0x6edf512d



>>> Scanning for Main ROM Checksum sub-routine #2 [to extract stored checksums and locations in ROM] No match found
main checksum byte sequence #2 not found
Giving up.


>>> Scanning for Multipoint Checksum sub-routine #1 [to extract stored checksum list location in ROM]
Multipoint byte sequence #1 block found at offset=0x8b854.

Blk #01:
        lo:0x1fbde (seg: 0x207 phy:0x81fbde) : Start: 0x00000000
        lo:0x1fbe2 (seg: 0x207 phy:0x81fbe2) : End:   0x00003fff
        lo:0x1fbe6 (seg: 0x207 phy:0x81fbe6) : CRC32: 0x0fa0f5cf
        lo:0x1fbea (seg: 0x207 phy:0x81fbea) : ~CRC32 0xf05f0a30 Bootblock #1 ram/rom offset: 0x00000000 len=0x3fff
Blk #02:
        lo:0x1fbee (seg: 0x207 phy:0x81fbee) : Start: 0x00004000
        lo:0x1fbf2 (seg: 0x207 phy:0x81fbf2) : End:   0x00007fff
        lo:0x1fbf6 (seg: 0x207 phy:0x81fbf6) : CRC32: 0x0f4716b3
        lo:0x1fbfa (seg: 0x207 phy:0x81fbfa) : ~CRC32 0xf0b8e94c Bootblock #2 ram/rom offset: 0x00004000 len=0x3fff

... cut ... cut ... (message too big!)

Blk #64:
        lo:0x1ffce (seg: 0x207 phy:0x81ffce) : Start: 0x008f4000
        lo:0x1ffd2 (seg: 0x207 phy:0x81ffd2) : End:   0x008f7fff
        lo:0x1ffd6 (seg: 0x207 phy:0x81ffd6) : CRC32: 0x1fffe000
        lo:0x1ffda (seg: 0x207 phy:0x81ffda) : ~CRC32 0xe0001fff rom offset: 0x000f4000 len=0x3fff
Blk #65:
        lo:0x1ffde (seg: 0x207 phy:0x81ffde) : Start: 0x008f8000
        lo:0x1ffe2 (seg: 0x207 phy:0x81ffe2) : End:   0x008fbfff
        lo:0x1ffe6 (seg: 0x207 phy:0x81ffe6) : CRC32: 0x1fffe000
        lo:0x1ffea (seg: 0x207 phy:0x81ffea) : ~CRC32 0xe0001fff rom offset: 0x000f8000 len=0x3fff
Blk #66:
        lo:0x1ffee (seg: 0x207 phy:0x81ffee) : Start: 0x008fc000
        lo:0x1fff2 (seg: 0x207 phy:0x81fff2) : End:   0x008fffff
        lo:0x1fff6 (seg: 0x207 phy:0x81fff6) : CRC32: 0x1ffde002
        lo:0x1fffa (seg: 0x207 phy:0x81fffa) : ~CRC32 0xe0021ffd rom offset: 0x000fc000 len=0x3fff
Logged
Pages: 1 ... 4 5 [6] 7
  Print  
 
Jump to:  

Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Page created in 0.03 seconds with 16 queries. (Pretty URLs adds 0s, 0q)