Cart New Account Login

HomeAbout usProductsSupportForumsBlogCustomer Service

search inside this forum
32p file format specification needed
john S. Aug 19, 2015 at 08:38 PM (20:38 hours)
Staff: Takao Y.

  • I'm trying to debug a board with a programming problem. It will not complete the connection process. Using a MC68332 processor. I reset the chip and that works fine, then CM (Choose Module) and I select the correct .32p file that is used for this board. The .32p file works on every other board so this is a good file. The following error message is seen.

    Error Loading .32p file: filename at address 00100000

    I look at the .32p file and there looks to be S19 record format lines toward the bottom. I'm not sure what these are for. The first one is to address 100000 which is the same address that is being reported as having an error.

    I'm would like to know how to interpret this .32p file. There doesn't seem to be any documentation on your web site.

    I'm thinking that I could create my own .32p files for different types of testing if I just knew the format the file and what each section does.




    Comments

  • Here is the text of the .32p file

    ;version 1.01, 11/24/1999, Copyright P&E Microcomputer Systems, www.pemicro.com
    ;device AMD, 29F400-B, 1x16x256k
    ;begin_cs device=$00000000, length=$00080000, ram=$00080000
    WRITE_WORD=2BFF/00FFFA44/    ; CSPAR0
    WRITE_WORD=0300/00FFFA46/    ; CSPAR1
    WRITE_WORD=0006/00FFFA48/    ; CSBARBT   
    WRITE_WORD=7830/00FFFA4A/    ; CSORBT   
    WRITE_WORD=0806/00FFFA4C/    ; CSBAR0   
    WRITE_WORD=6C30/00FFFA4E/    ; CSOR0   
    WRITE_WORD=0806/00FFFA50/    ; CSBAR1   
    WRITE_WORD=3C30/00FFFA52/    ; CSOR1   
    WRITE_WORD=0806/00FFFA54/    ; CSBAR2   
    WRITE_WORD=5C30/00FFFA56/    ; CSOR2   
    WRITE_WORD=0806/00FFFA58/    ; CSBAR3   
    WRITE_WORD=7430/00FFFA5A/    ; CSOR3
    WRITE_WORD=0006/00FFFA74/    ; CSPAR10   
    WRITE_WORD=7470/00FFFA76/    ; CSOR10
    WRITE_WORD=3F00/00FFFA04/ ;Double clock speed 16MHz w 32KHz Xtal
    WRITE_BYTE=00/00FFFA21/ ;Turn off watchdog timer
    ;end_cs
    NO_TIMING_TEST
    USER=BE Block Erase 1Block > /00000000/0000000A/
    ;
    S214100000001003A0001001600000020000000000B5
    S21410001000080000000000000010010200000000B0
    S21410002000000000001000C40000000000100116C0
    S2141000300010004C0010004E001000500000000091
    S21410004000000000000000000010007E4AFA4AFA85
    S2141000504AFA0000000000004000000060000000A7
    S21410006080000001000000020000000300000004F1
    S2141000700000000500000006000000070000227CBB
    S2141000800010005220710400D1FC0000000033FC68
    S214100090AAAA0000AAAA33FC55550000555433FCF2
    S2141000A080800000AAAA33FCAAAA0000AAAA33FCE1
    S2141000B055550000555430BC30300C50FFFF66FAD2
    S2141000C042804AFA33FCAAAA0000AAAA33FC555565
    S2141000D00000555433FC80800000AAAA33FCAAAA5C
    S2141000E00000AAAA33FC55550000555433FC1010D6
    S2141000F00000AAAA0C79FFFF0000000066F64280F6
    S2141001004AFA0C58FFFF6606558066F64AFA203CF7
    S214100110FFFFFFFF4AFA287C0010016048E710181E
    S21410012033FCAAAA0000AAAA33FC55550000555461
    S21410013033FCA0A00000AAAA36DC302CFFFEB06B61
    S214100140FFFE66FA558366D84CDF1808B74C66086B
    S214100150558366F842804AFA203CFFFFFFFF4AFAB2
    S804000000FB

    Ûq

  • Greetings,

    The Srecrod data at the end of all algorithms are proprietary code. This data is what is loaded into RAM of your chip and then executes the commands you want to do, like erase and program.

    The algorithms you see in the vast list in your folder are just default algorithms. If they do not work, that means you have non-default hardware connections. Maybe you have address or data lines that are not connected in the conventional manner? Or you have a chip select that is not CS0?

    If this is the case, please go to Support Page -> Support Requests and request for an algorithm. Here you should detail the lines connected between your host MCU to your external flash chips. Schematics are perfect if that is available.


    Takao Yamada

  • Takao,

    Thanks for the feedback. I mentioned we use this file successfully on all our boards, so we don't have any signal mapping issues. We just have this one board from our stuffing house that will not work and fails with the error noted above.

    From your discussion, I'm assuming the error message has to do with the proprietary code that is loaded into RAM since it refers to address 0x100000. So it looks like this one board probably has some sort of RAM issue.

    Thanks for the pointer. I'll let you know what we find.

    Regards,

    John

  • Takao,

    I decoded the WRITE_WORD register programming information and it looks like the address space mapping is as follows.

    0x000000 - 0x07FFFF : Flash (512 KB)
    0x080000 - 0x0FFFFF : RAM (512 KB)

    So I'm confused what section of RAM the SREC(S19) format records are being written. These SREC records start at address 0x100000 which is not defined by the Chip Select Base Address Registers.

    Regards,

    John

  • Greetings,

    Sorry for the delayed response. Has this issue been resolved? Were you able to find out why your one board was not working while all the others were working fine?


    Takao Yamada

Add comment


   Want to comment? Please login or create a new PEMicro account.







© 2017 P&E Microcomputer Systems Inc.
Website Terms of Use and Sales Agreement