Hello Alfin,
thanks for your report. Have you connected all input pins of the flash chip to the programmer? The behavior shown in the log extract could be coming from a floating write protection pin. That's pin #9 (diagonally opposite to the pin #1 marker on the 16-pin sop/soic package). I'd check if that pin is pulled-high towards VCC (pin #2). Likewise all other *input* pins should be driven - either statically to GND or VCC (ideally by resistors), or dynamically by the programmer's clock and data out pins. HTH
Hello Stefan,
Thanks for your response. I have connected all the pins (CLK,DI,DO,CS) and 3.3v to VCC, HOLD, WP. IC type is EN25QH128A-HIP ( 4 pins ). Try using Arduino Duemilanove (serprog:dev=/dev/ttyUSB0:2000000) result remains the same.
Regards, Alfin
2014-06-01 16:55 GMT+07.00, Stefan Tauner stefan.tauner@alumni.tuwien.ac.at:
Hello Alfin,
thanks for your report. Have you connected all input pins of the flash chip to the programmer? The behavior shown in the log extract could be coming from a floating write protection pin. That's pin #9 (diagonally opposite to the pin #1 marker on the 16-pin sop/soic package). I'd check if that pin is pulled-high towards VCC (pin #2). Likewise all other *input* pins should be driven - either statically to GND or VCC (ideally by resistors), or dynamically by the programmer's clock and data out pins. HTH
-- Kind regards/Mit freundlichen Grüßen, Stefan Tauner