Cart New Account Login

HomeAbout usProductsSupportForumsBlogCustomer Service

search inside this forum
Inconsistent flash programming and/or read back on 68332 with AM29F8008B
john S. Dec 16, 2014 at 12:24 PM (12:24 hours)
Staff: Takao Y.

  • I'm trying to create an S19 file with data for every location in flash. First I erase the flash using EM. I'm using the command line program cprog32z to program each location in flash using 262144 PW (program word) commands. Each command has an incrementing data pattern from 0000 to FFFF which repeats 4 times.

    I can program the first 131072 words (00000 to 3fffe) and read them back with upload module (UM). This is consistent and works reliably. The problem I have is programming and/or reading back the last 131072 words (40000 to 7fffe). Show Module (SM) and Upload Module (UM) show different results and multiple runs of Upload Module yield different results.

    This is a old design and it has worked for years so I don't think there is any problem with the hardware.

    Is this some sort of software bug or maybe the device file is not correct? Is there any documentation on the S19 portion of the device file. What is that used for?

    I'm using the 1x16x512K part just because the 1x16x256K part is not readily available any more. The upper address line is tied low.

    processor MC68332
    flash AM29F8008B
    prog32z version 2.06.00.00
    device file: ~Am_400bw.32p

    ;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/    ; CSPAR10
    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




    Comments

  • Greetings,

    I am sorry no one has answered your question. Is this issue resolved? Do you still need assistance with this problem?


    Takao Yamada

  • yes. This is still a problem.

  • Greetings,

    Could you go to Support page -> Support requests and create a ticket? I would like you to upload the algorithm you are using. This algorithm must have been customized because it does not look like an algorithm we deliver by default. From there we can figure out why you are not able to program the second half of the memory. Second half would indicate the upper bits of address is not setup correctly.


    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