Forum Discussion
Altera_Forum
Honored Contributor
21 years agoFrom the "Intel StrataFlash® Memory (J3) 28F256J3, 28F128J3, 28F640J3, 28F320J3 (x8/x16)" datasheet. [Order Number: 290667-020 November 2004],
Section "10.2 Read Identifier Codes" Page# 39, Note 1: <div class='quotetop'>QUOTE </div> --- Quote Start --- NOTES: 1. A0 is not used in either x8 or x16 modes when obtaining the identifier codes. The lowest order address line is A1. Data is always presented on the low byte in x16 mode (upper byte contains 00h).[/b] --- Quote End --- It's a bit bizarre, but that's what is says. It also seems to be what it does... The original code got an 'unlock status' of 0x17 (Which is the identifier byte for a 64MB part). This gets interpreted as "locked". For a 32MB part - which you've tested with, you'll read 0x16, which is interpreted as "unlocked" http://forum.niosforum.com/work2/style_emoticons/<#EMO_DIR#>/sad.gif , so your code may fail to unlock blocks on 32MB parts... Thanks for the confirmation that this style of part is supported/tested. I'm sure the above bug (assuming it is a bug) isn't behind the problems I'm having. I need to look much closer at our implementation! - Roddy