Skip to content

GitLab

Switch branch/tag
  1. 24 Feb, 2012 1 commit
  3. 22 Feb, 2012 1 commit
    • Stefan Tauner's avatar
      Fix SFDP probing · 75adf32a
      Stefan Tauner authored 
      
Sfdp_add_uniform_eraser checks for existing erasers. Due to a bug it
looked for eraser slots that have no erase functions set instead of
those that have one set.

Postpone adding an erase function for the special 4k block erase
opcode until we know the flash chip size and add an additional check
to sfdp_add_uniform_eraser.

Fix the output of the parameter table contents.

This patch fixes the index used to retrieve the eraser types, which
was off one double word.

Refine some messages and add a few further debugging prints.

Corresponding to flashrom svn r1505.
Signed-off-by: default avatarStefan Tauner <stefan.tauner@alumni.tuwien.ac.at>
Acked-by: default avatarCarl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net>
      75adf32a
  5. 18 Feb, 2012 1 commit
  7. 17 Feb, 2012 3 commits
  9. 16 Feb, 2012 6 commits
  11. 15 Feb, 2012 1 commit
  13. 13 Feb, 2012 1 commit
  15. 12 Feb, 2012 1 commit
  17. 08 Feb, 2012 1 commit
    • Carl-Daniel Hailfinger's avatar
      SPI command black-/ignorelisting for the flash chip emulator in the dummy programmer · 1b83be5c
      Carl-Daniel Hailfinger authored 
      
Usage:
flashrom -p dummy:spi_blacklist=commandlist
flashrom -p dummy:spi_ignorelist=commandlist

If commandlist is 0302, flashrom will refuse (blacklist) or ignore
(ignorelist) command 0x03 (READ) and command 0x02 (WRITE). The
commandlist can be up to 512 bytes (256 commands) long.
Specifying flash chip emulation is a good idea to get useful results.

Very useful for testing corner cases if you don't own a locked down
Intel chipset and want to simulate such a thing.

Example usage:
dd if=/dev/zeros bs=1024k count=4 of=dummy_simulator.rom
dd if=/dev/urandom bs=1024k count=4 of=randomimage.rom
flashrom -p dummy:emulate=SST25VF032B,image=dummy_simulator.rom,\
spi_blacklist=20,spi_ignorelist=52 -w randomimage.rom -V

Corresponding to flashrom svn r1490.
Signed-off-by: default avatarCarl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net>
Acked-by: default avatarDavid Hendricks <dhendrix@google.com>
      1b83be5c
  19. 07 Feb, 2012 1 commit
  21. 03 Feb, 2012 1 commit
  23. 31 Jan, 2012 1 commit
  25. 19 Jan, 2012 1 commit
  27. 12 Jan, 2012 1 commit
  29. 11 Jan, 2012 1 commit
  31. 04 Jan, 2012 1 commit
  33. 25 Dec, 2011 2 commits
  35. 24 Dec, 2011 1 commit
    • Stefan Tauner's avatar
      Add ich_descriptor_tool to decode all flash descriptors stored in a flash dump file · b3850964
      Stefan Tauner authored 
      
This patch adds an external utility that shares most of the existing descriptor
decoding source code. Additionally to what is available via FDOC/FDOD this
allows to access:
 - the softstraps which are used to configure the chipset by flash content
   without the need for BIOS routines. on ICH8 it is possible to read those
   with FDOC/FDOC too, but this was removed in later chipsets.
 - the ME VSCC (Vendor Specific Component Capabilities) table. simply put,
   this is an SPI chip database used to figure out the flash's capabilities.
 - the MAC address stored in the GbE image.

Intel thinks this information should be confidential for ICH9 and up, but
references some tidbits in their public documentation.
This patch includes the human-readable information for ICH8, Ibex Peak
(5 series) and Cougar Point (6 series); the latter two were obtained from
leaked "SPI Flash Programming Guides" found by google. Data regarding ICH9
and 10 is unknown to us yet. It can probably found in:
"Intel® ICH7, ICH8, ICH9 and ICH10 — SPI Family Flash Programming Guide"
Information regarding the upcoming Panther Point chipset is also not included.

Corresponding to flashrom svn r1480.
Signed-off-by: default avatarStefan Tauner <stefan.tauner@alumni.tuwien.ac.at>
Acked-by: default avatarMatthias Wenzel <bios@mazzoo.de>
      b3850964
  37. 22 Dec, 2011 1 commit
  39. 20 Dec, 2011 4 commits
  41. 18 Dec, 2011 1 commit
  43. 14 Dec, 2011 1 commit
    • Carl-Daniel Hailfinger's avatar
      Use struct flashctx instead of struct flashchip for flash chip access · 63fd9026
      Carl-Daniel Hailfinger authored 
      
Struct flashchip is used only for the flashchips array and for
operations which do not access hardware, e.g. printing a list of
supported flash chips.

struct flashctx (flash context) contains all data available in
struct flashchip, but it also contains runtime information like
mapping addresses. struct flashctx is expected to grow additional
members over time, a prime candidate being programmer info.
struct flashctx contains all of struct flashchip with identical
member layout, but struct flashctx has additional members at the end.

The separation between struct flashchip/flashctx shrinks the memory
requirement of the big flashchips array and allows future extension
of flashctx without having to worry about bloat.

Corresponding to flashrom svn r1473.
Signed-off-by: default avatarCarl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net>
Acked-by: default avatarMichael Karcher <flashrom@mkarcher.dialup.fu-berlin.de>
      63fd9026
  45. 08 Dec, 2011 1 commit
  47. 02 Dec, 2011 1 commit
  49. 23 Nov, 2011 1 commit
  51. 19 Nov, 2011 1 commit
  53. 16 Nov, 2011 1 commit
  55. 15 Nov, 2011 1 commit
  57. 14 Nov, 2011 1 commit

Powered by Integricloud