chip migration

Hi thepancake,

thanks for the answer.

I double-checked the board, and the situation looks to be slightly different respect of what I said yesterday :o.

Perhaps I had some trouble with the oscilloscope probe tip. I replaced it with another one (double-checked too).

I attached a report which should explain what I'm seeing. In the attachment you'll find two nCONFIG signals (nCONFIG1 and nCONFIG2) as boards has two EPLD that are programmed by the EPM70xx chip.

So, at today, the situation is:

- a board with EPM7032 and old FW works (I have tried that on 3 boards up to now, moving the EPM7032 chip);

- the same board(s) with EPM7064 and recompiled FW is not able to release the CONF_DN1, but COND_DN2, after configuration bits are (apparently) sent.

Since FW for EPM7032 looks to be good, I opened that .pof and I have looked at contents with an hex editor.

It addresses from 0x0000 up to 0x0850, so 0x851 bytes in hex notation, so 2129 bytes, in decimal notation.

I did the same for recompiled FW for EPM7064.

Addresses are from 0x0000 up to 0x0FF0, so 0xFF1 bytes in hex notation, so 4081 bytes, in decimal notation.

I expected 4258 bytes in EPM7064 .pof, since EPM7032 has 2129 bytes in its .pof and it works that way. Perhaps that difference is a matter of compiler/fitter processes.

As already said, the target devices that should be programmed are both FLEX EPF 10K30ETC144-1N. I found that EPF10K30e requires 473720 bits (59215 Bytes) for SRAM configuration. Is that correct? However, how many bits shall I send to that targets to fill their SRAM completely?

Bye.