Results 1 to 5 of 5

Thread: Reading and Programming Chips using offsets

  1. #1
    RIP EagleMark's Avatar
    Join Date
    Feb 2011
    Location
    North Idaho
    Age
    63
    Posts
    10,477

    Reading and Programming Chips using offsets

    Programming chips using offsets. From Moates article!


    File Size ----- Chip ------ Buffer Start -> End ----- Chip Start -> End
    4k ( 4096 ) - AT29C256 - 000000 -> 000FFF ------ 007000 -> 007FFF
    16k (16384) - AT29C256 - 000000 -> 003FFF ----- 004000 -> 007FFF
    32k (32768) - AT29C256 - 000000 -> 007FFF ----- 000000 -> 007FFF
    4k ( 4096 ) - 27SF512 - 000000 -> 000FFF -------- 00F000 -> 00FFFF
    16k (16384) - 27SF512 - 000000 -> 003FFF ------- 00C000 -> 00FFFF
    32k (32768) - 27SF512 - 000000 -> 007FFF ------- 008000 -> 00FFFF
    56k (57344) - 27SF512 - 000000 -> 00DFFF ------- 002000 -> 00FFFF
    64k (65536) - 27SF512 - 000000 -> 00FFFF ------- 000000 -> 00FFFF
    -------------------------------------------------------------------

    Now the reading of chips I can't find anywhere so we will start one here.

    File Size ------ Chip-----Buffer Start-> End ----- Chip Start -> End
    4k - (4096) - 2732a --- 000000 -> 000FFF ----- 00F000 -> 00FFFF
    27C128
    27C256
    64k (65536) 27C512 --- 00000 -> 0FFFF ------- 00000 -> 0FFFF


    Anyone who has information just post it up and I will complete this so everyone has a place to go for the proper offsets to read and write chips. Thanks!

    1990 Chevy Suburban 5.7L Auto ECM 1227747 $42!
    1998 Chevy Silverado 5.7L Vortec 0411 Swap to RoadRunner!
    -= =-

  2. #2
    Administrator
    Join Date
    May 2011
    Location
    Lakes Region, NH
    Age
    54
    Posts
    3,847

    Re: Reading and Programming Chips using offsets

    Not sure why you had to use those offsets. Chip / file address should be 000 to FFF on the 2732 or 2732A. Otherwise, reading the chip is the same as programming in terms of addressing. The most consistent method I know is to read the entire address range then view the file in a hex editor. If you see the chip "repeating" at the 1/2 or 1/4 point then you know the actual file size is a fraction of the chip size.

  3. #3
    RIP EagleMark's Avatar
    Join Date
    Feb 2011
    Location
    North Idaho
    Age
    63
    Posts
    10,477

    Re: Reading and Programming Chips using offsets

    I don't know much about the offsets or hex but I read the chip with your offsets and the ones listed above and they both look the same in the hex editor.

    1990 Chevy Suburban 5.7L Auto ECM 1227747 $42!
    1998 Chevy Silverado 5.7L Vortec 0411 Swap to RoadRunner!
    -= =-

  4. #4
    Super Moderator Six_Shooter's Avatar
    Join Date
    Feb 2011
    Posts
    2,968

    Re: Reading and Programming Chips using offsets

    Quote Originally Posted by 1project2many
    Not sure why you had to use those offsets. Chip / file address should be 000 to FFF on the 2732 or 2732A. Otherwise, reading the chip is the same as programming in terms of addressing. The most consistent method I know is to read the entire address range then view the file in a hex editor. If you see the chip "repeating" at the 1/2 or 1/4 point then you know the actual file size is a fraction of the chip size.

    This is what I do.

    The only ones that through a loop into that (or make you think) are the ones that don't have anything at the beginning of the chip and start an 1/8 or so into the hex editor addressing.
    The man who says something is impossible, is usually interrupted by the man doing it.

  5. #5
    Administrator
    Join Date
    May 2011
    Location
    Lakes Region, NH
    Age
    54
    Posts
    3,847

    Re: Reading and Programming Chips using offsets

    I don't know much about the offsets or hex but I read the chip with your offsets and the ones listed above and they both look the same in the hex editor.
    We're using different tools to read the chip and that may explain why the Moates article recommends different addresses. You should learn some basics about using hex and working with addresses and a hex editor. There are times when you might want to hand edit a calibration or when you might want to confirm that a file isn't corrupt that would require the hex edit tool.

    The only ones that through a loop into that (or make you think) are the ones that don't have anything at the beginning of the chip and start an 1/8 or so into the hex editor addressing.
    Some of the 2.3 cals have data all over the place. I thought my disassembler was broken when I first started working on one because it just wasn't arranged like a normal GM cal. And the coding is different, too. I think the code was generated by a newer compiler than what's used for many of the more common cals.

Similar Threads

  1. Bench programming a LT1 PCM ?
    By EagleMark in forum GM EFI Systems
    Replies: 22
    Last Post: 01-26-2014, 04:37 AM
  2. Looking for an old eprom programmer for 2732a chips
    By EagleMark in forum GM EFI Systems
    Replies: 19
    Last Post: 12-24-2011, 04:58 AM
  3. Burning Memcal Chips
    By EagleMark in forum GM EFI Systems
    Replies: 5
    Last Post: 07-14-2011, 08:34 AM
  4. Reading a 1227730 chip
    By EagleMark in forum GM EFI Systems
    Replies: 11
    Last Post: 07-04-2011, 03:38 AM
  5. Painless VSS + 16197427 = no VSS reading.
    By Six_Shooter in forum GM EFI Systems
    Replies: 4
    Last Post: 03-21-2011, 03:09 AM

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
  •