Forum Discussion
Altera_Forum
Honored Contributor
10 years agoI am trying to identify the reboot process, and the difference in data being read on EPROM data lines.
Regardless if I am looking at the .jic/JTAG image or if I used my application to write the .rbf file, the states seem to be the same: a. DCLK starts low, data lines high (starts with nCS trigger; signal goes low) b. READ STATUS (register) op code c. READ DEVICE ID op code and it reads the fact I have an EPCQ256 device d. FAST READ op code followed by a string of data over the D1 line only (as is appropriate for Fast Read operation) Fast Read lasts .24ms and ends with a pulse in the nCS (the JTAG/jic version also includes e. EXTENDED QUAD INPUT FAST READ op code followed by 32-b address of 0x00012C00 and data in on all 4 D-lines) However, in the version where I reboot from my application, it tries the FAST READ and must not like the data it's reading because it continually restarts the process after reading about 3ms of data. Any idea what the data is that it is trying to read here? Is this supposed to be the actual image file? The data doesn't seem to match the image, or even a bit reversal of image data (jic or sof or rbf) Also - dsl - you mention bit reversal. Is that by 4 or 8 bits? Do you have a suggestion on simple ways to do this to create a new image to write? Thanks so much!