Modify

Opened 9 years ago

Closed 7 years ago

#7 closed defect (fixed)

Doesn't seem to be able to write on ICH-2 (maybe other ICH-x) mainboards

Reported by: uwe Owned by: uwe
Priority: critical Milestone:
Component: flashrom (please use trac on flashrom.org) Keywords:
Cc: Dependencies:
Patch Status: there is no patch

Description

See http://www.linuxbios.org/pipermail/linuxbios/2006-October/016087.html

I have problems writing flash chips with flashrom on multiple ICH-x
boards, e.g. ICH-2 and ICH-4. The code is pretty much the same for
all ICH-x so I guess all of them have the problem(?)

Detecting and reading from a chip works fine. Writing _seems_ to work
fine (no errors, doesn't abort), but when I try to verify (or just
read the chip again) I get the same content as before the write.

The hardware itself as well as the flash chip is ok, as I can write
the chip using Uniflash.

Has anybody successfully written any chip on an ICH-x? Is more code
needed to make it work? Motherboard-specific code maybe?

Attachments (0)

Change History (5)

comment:1 Changed 9 years ago by stepan

  • include_gantt set to 1

comment:2 Changed 9 years ago by stepan

  • due_assign set to 11/30/2006
  • due_close set to 12/31/2006

comment:3 Changed 9 years ago by stepan

  • Owner changed from somebody to uwe

Is this related to #26?

comment:4 Changed 7 years ago by uwe

  • Patch Status set to there is no patch
  • Summary changed from flashrom: Doesn't seem to be able to write on ICH-2 (maybe other ICH-x) mainboards to Doesn't seem to be able to write on ICH-2 (maybe other ICH-x) mainboards
  • version v2 deleted

comment:5 Changed 7 years ago by uwe

  • Resolution set to fixed
  • Status changed from new to closed

This was more or less a false alarm. As recently tested on my ICH2-based board the general ICH2 (ICHx) code in flashrom works fine, the problem was that my board was using a custom write-enable hack. Marking this issue as fixed.

Add Comment

Modify Ticket

Action
as closed The owner will remain uwe.
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.