Forum Discussion
Cyclone IV GX (EP4CGX30CF23C7) Flash Issue
Dear Altera Support Team,
We are currently using the Cyclone IV GX FPGA (EP4CGX30CF23C7) on our production board, configured via Active Serial (AS) mode using a 16Mb SPI Flash.
We are encountering functional failure and Checksum mismatch when attempting to migrate our flash memory from the old part to a new part. Could you please help verify if this new part is officially supported or if there are any known configuration issues?
Flash Comparison & Details:
Original Part (Working):
Macronix MX25L1606EM2I-12G
Size : 200040h
Checksum: 13F8B518h
New Part (Failing / Function Abnormal):
Macronix MX25V1606FM2I03
Size: 200000h
Checksum: 13F87558h
Observed Symptoms:
After programming the new MX25V1606FM2I03, the FPGA fails to configure successfully (AS configuration error / LED status fails to initialize).
We noticed a discrepancy in the binary size (200040h vs 200000h) and Checksum between the two programming files generated or read back.
Questions for AE:
Is the MX25V1606FM2I03 fully compatible with Cyclone IV GX Active Serial (AS) configuration requirements? (Considering it's a 2.5V/3V or different revision series from the 'L' version).
Why does the generated image size show an extra 40h offset (200040h) on the original MX25L1606E, and how does this affect the Cyclone IV configuration loader?
Could the slight electrical specification or command set difference (e.g., Read/Write ID or timing parameters) between the MX25L1606E and MX25V1606FM2I03 cause the FPGA configuration failure?
Any guidance or documentation references would be greatly appreciated. Thank you for your support!
1 Reply
- ai_responder
Community Manager
Thank you for your inquiry. To ensure an accurate response, your request has been routed to an Altera application engineer for further review and assistance.
Note: To continue using AI Responder, please start your next inquiry with ai_responderDisclaimer (Beta): The AI Responder is currently provided as a beta feature. AI-generated responses may contain errors or omissions. Please verify technical guidance with official Altera documentation before implementation.
Thank you very much.