flashrom October 2016

flashrom@flashrom.org

17 participants
36 discussions

Re: [flashrom] Development flashrom
by Agustin Isasmendi 18 Oct '16

18 Oct '16

Pinouts launchpad CC3200. First remove jumpers! When finished my development, Could you publish my development in your web? I would be very happy, it is my first contribution to the community. 2016-10-17 17:59 GMT-03:00 Agustin Isasmendi <isasmendi.agus(a)gmail.com>: > Hi Carl, David > > The launchpad CC3200 have FTDI 2232D for programming CC3200 MCU. I wanted > to use this FT2232 with flashrom. > I can finally use flashrom with launchpad cc3200. > > But i have questions about ft2232_spi.c file (attached) in line 488 > "buf[i++] = 0 & ~cs_bits; /* assertive */" > Why sets all pins to low state? I need keep one pin to high state.The > launchpad CC3200 requires keep Bit 7 to high state for work. > > It work replacement line 488 for this buf[i++] = 0x80; > Any solution? > > attach img with flashrom running. Sorry for quality > > Reggards > > 2016-10-14 20:19 GMT-03:00 Carl-Daniel Hailfinger < > c-d.hailfinger.devel.2006(a)gmx.net>: > >> On 14.10.2016 21:24, David Hendricks wrote: >> > What exactly are you trying to do? How do you plan to use the CC3200? >> > How is the flash memory connected / accessed? >> > >> > TI has some information about flashing it >> > here: http://processors.wiki.ti.com/index.php/CC31xx_%26_CC32xx_FT >> DI_Flashing >> > >> > If you'd like, you can try adding support for the FTDI chip in >> > ft2232_spi.c. >> >> There are various existing open source tools based on libftdi which >> write the EEPROM which does the same thing as FT_PROG. Please note that >> FT_PROG writes the configuation EEPROM of the FTDI chip, not the flash >> chip storing the firmware of the CC3100/CC3200. >> >> >> > If the FTDI D2XX is significantly different you can create a new file >> > (ftdi_d2xx.c, for example), and use ft2232_spi.c as a template. >> >> I think the FTDI D2XX library has a license incompatible with flashrom. >> >> >> If you want to replace TI CCS UniFlash with flashrom, it would make >> sense to check if any protocol documentation for the UART-based flashing >> exists. In that case you won't need D2XX or libftdi. >> >> Regards, >> Carl-Daniel >> > > A non-text attachment has been stripped: image/jpeg; name="IMG_20161017_195848.jpg"

1 0

Re: [flashrom] Development flashrom
by Carl-Daniel Hailfinger 17 Oct '16

17 Oct '16

On 14.10.2016 21:24, David Hendricks wrote: > What exactly are you trying to do? How do you plan to use the CC3200? > How is the flash memory connected / accessed? > > TI has some information about flashing it > here: http://processors.wiki.ti.com/index.php/CC31xx_%26_CC32xx_FTDI_Flashing > > If you'd like, you can try adding support for the FTDI chip in > ft2232_spi.c. There are various existing open source tools based on libftdi which write the EEPROM which does the same thing as FT_PROG. Please note that FT_PROG writes the configuation EEPROM of the FTDI chip, not the flash chip storing the firmware of the CC3100/CC3200. > If the FTDI D2XX is significantly different you can create a new file > (ftdi_d2xx.c, for example), and use ft2232_spi.c as a template. I think the FTDI D2XX library has a license incompatible with flashrom. If you want to replace TI CCS UniFlash with flashrom, it would make sense to check if any protocol documentation for the UART-based flashing exists. In that case you won't need D2XX or libftdi. Regards, Carl-Daniel

2 1

Re: [flashrom] Can't find Write protect screw on Samsung XE500C21
by Chris M 15 Oct '16

15 Oct '16

If anyone wants's to see the output from flashrom. Here it is when I try to disable firmware write protect when the developer switch is flipped to on. https://paste.flashrom.org/view.php?id=2957 On Fri, Oct 14, 2016 at 7:50 PM, Chris M <pugsly003(a)gmail.com> wrote: > Yes, I already have seen that switch on the side of the Chromebook and > flipped it on, Seems like that didn't help with disabling Write protect. My > best guess is it's somewhere on the motherboard. I've already got someone > to try to help https://plus.google.com/+ChrisMcLeod36202/posts/cEMtHE2WYq4 > > On Fri, Oct 14, 2016 at 7:32 PM, David Hendricks <dhendrix(a)google.com> > wrote: > >> If it's Alex, then you'll want to check this page: >> http://www.chromium.org/chromium-os/developer-information- >> for-chrome-os-devices/samsung-series-5-chromebook >> >> Unfortunately the page for Alex doesn't have the WP switch circled, and >> it's been so long that I forgot where it is. It *should* be a jumper, >> though. I seem to recall that there is a plastic shroud near it to guard >> against potential tampering thru the exhaust grill or SD card slot. >> >> PS. Please reply to all so that others in the list can view and/or >> contribute. >> >> >> On Fri, Oct 14, 2016 at 4:19 PM, Chris M <pugsly003(a)gmail.com> wrote: >> >>> Actually, I checked on the ribbon cables and it says Alex. I might of >>> typed in the wrong model number, Whoops https://www.chromium.org/chrom >>> ium-os/developer-information-for-chrome-os-devices/samsung-s >>> eries-5-chromebook >>> >>> On Fri, Oct 14, 2016 at 7:13 PM, David Hendricks <dhendrix(a)google.com> >>> wrote: >>> >>>> Hi Chris, >>>> IIRC the development name for that machine is "Lumpy." There are full >>>> disassembly instructions here: http://www.chromium.org/ >>>> chromium-os/developer-information-for-chrome-os-devices/sams >>>> ung-sandy-bridge >>>> >>>> The write-protect signal is gated by a jumper instead of a screw. The >>>> jumper is located next to the keyboard ribbon connector and memory module. >>>> >>>> >>>> On Thu, Oct 13, 2016 at 5:08 PM, Chris M <pugsly003(a)gmail.com> wrote: >>>> >>>>> Hello, I'm wondering where i could find the Write protect screw on my >>>>> Samsung XE500C21. Got any ideas where I could find it? >>>>> Regards >>>>> -Chris >>>>> >>>>> _______________________________________________ >>>>> flashrom mailing list >>>>> flashrom(a)flashrom.org >>>>> https://www.flashrom.org/mailman/listinfo/flashrom >>>>> >>>> >>>> >>>> >>>> -- >>>> David Hendricks (dhendrix) >>>> Systems Software Engineer, Google Inc. >>>> >>> >>> >> >> >> -- >> David Hendricks (dhendrix) >> Systems Software Engineer, Google Inc. >> > >

1 0

Re: [flashrom] Can't find Write protect screw on Samsung XE500C21
by Chris M 15 Oct '16

15 Oct '16

Yes, I already have seen that switch on the side of the Chromebook and flipped it on, Seems like that didn't help with disabling Write protect. My best guess is it's somewhere on the motherboard. I've already got someone to try to help https://plus.google.com/+ChrisMcLeod36202/posts/cEMtHE2WYq4 On Fri, Oct 14, 2016 at 7:32 PM, David Hendricks <dhendrix(a)google.com> wrote: > If it's Alex, then you'll want to check this page: > http://www.chromium.org/chromium-os/developer-information-for-chrome-os- > devices/samsung-series-5-chromebook > > Unfortunately the page for Alex doesn't have the WP switch circled, and > it's been so long that I forgot where it is. It *should* be a jumper, > though. I seem to recall that there is a plastic shroud near it to guard > against potential tampering thru the exhaust grill or SD card slot. > > PS. Please reply to all so that others in the list can view and/or > contribute. > > > On Fri, Oct 14, 2016 at 4:19 PM, Chris M <pugsly003(a)gmail.com> wrote: > >> Actually, I checked on the ribbon cables and it says Alex. I might of >> typed in the wrong model number, Whoops https://www.chromium.org/chrom >> ium-os/developer-information-for-chrome-os-devices/samsung- >> series-5-chromebook >> >> On Fri, Oct 14, 2016 at 7:13 PM, David Hendricks <dhendrix(a)google.com> >> wrote: >> >>> Hi Chris, >>> IIRC the development name for that machine is "Lumpy." There are full >>> disassembly instructions here: http://www.chromium.org/ >>> chromium-os/developer-information-for-chrome-os-devices/sams >>> ung-sandy-bridge >>> >>> The write-protect signal is gated by a jumper instead of a screw. The >>> jumper is located next to the keyboard ribbon connector and memory module. >>> >>> >>> On Thu, Oct 13, 2016 at 5:08 PM, Chris M <pugsly003(a)gmail.com> wrote: >>> >>>> Hello, I'm wondering where i could find the Write protect screw on my >>>> Samsung XE500C21. Got any ideas where I could find it? >>>> Regards >>>> -Chris >>>> >>>> _______________________________________________ >>>> flashrom mailing list >>>> flashrom(a)flashrom.org >>>> https://www.flashrom.org/mailman/listinfo/flashrom >>>> >>> >>> >>> >>> -- >>> David Hendricks (dhendrix) >>> Systems Software Engineer, Google Inc. >>> >> >> > > > -- > David Hendricks (dhendrix) > Systems Software Engineer, Google Inc. >

1 0

Re: [flashrom] Can't find Write protect screw on Samsung XE500C21
by David Hendricks 15 Oct '16

15 Oct '16

If it's Alex, then you'll want to check this page: http://www.chromium.org/chromium-os/developer-information-for-chrome-os-dev… Unfortunately the page for Alex doesn't have the WP switch circled, and it's been so long that I forgot where it is. It *should* be a jumper, though. I seem to recall that there is a plastic shroud near it to guard against potential tampering thru the exhaust grill or SD card slot. PS. Please reply to all so that others in the list can view and/or contribute. On Fri, Oct 14, 2016 at 4:19 PM, Chris M <pugsly003(a)gmail.com> wrote: > Actually, I checked on the ribbon cables and it says Alex. I might of > typed in the wrong model number, Whoops https://www.chromium.org/ > chromium-os/developer-information-for-chrome-os-devices/samsung-series-5- > chromebook > > On Fri, Oct 14, 2016 at 7:13 PM, David Hendricks <dhendrix(a)google.com> > wrote: > >> Hi Chris, >> IIRC the development name for that machine is "Lumpy." There are full >> disassembly instructions here: http://www.chromium.org/ >> chromium-os/developer-information-for-chrome-os-devices/ >> samsung-sandy-bridge >> >> The write-protect signal is gated by a jumper instead of a screw. The >> jumper is located next to the keyboard ribbon connector and memory module. >> >> >> On Thu, Oct 13, 2016 at 5:08 PM, Chris M <pugsly003(a)gmail.com> wrote: >> >>> Hello, I'm wondering where i could find the Write protect screw on my >>> Samsung XE500C21. Got any ideas where I could find it? >>> Regards >>> -Chris >>> >>> _______________________________________________ >>> flashrom mailing list >>> flashrom(a)flashrom.org >>> https://www.flashrom.org/mailman/listinfo/flashrom >>> >> >> >> >> -- >> David Hendricks (dhendrix) >> Systems Software Engineer, Google Inc. >> > > -- David Hendricks (dhendrix) Systems Software Engineer, Google Inc.

1 0

Re: [flashrom] Can't find Write protect screw on Samsung XE500C21
by David Hendricks 15 Oct '16

15 Oct '16

Hi Chris, IIRC the development name for that machine is "Lumpy." There are full disassembly instructions here: http://www.chromium.org/chromium-os/developer-information-for-chrome-os-dev… The write-protect signal is gated by a jumper instead of a screw. The jumper is located next to the keyboard ribbon connector and memory module. On Thu, Oct 13, 2016 at 5:08 PM, Chris M <pugsly003(a)gmail.com> wrote: > Hello, I'm wondering where i could find the Write protect screw on my > Samsung XE500C21. Got any ideas where I could find it? > Regards > -Chris > > _______________________________________________ > flashrom mailing list > flashrom(a)flashrom.org > https://www.flashrom.org/mailman/listinfo/flashrom > -- David Hendricks (dhendrix) Systems Software Engineer, Google Inc.

1 0

Re: [flashrom] Development flashrom
by David Hendricks 14 Oct '16

14 Oct '16

What exactly are you trying to do? How do you plan to use the CC3200? How is the flash memory connected / accessed? TI has some information about flashing it here: http://processors.wiki.ti.com/index.php/CC31xx_%26_CC32xx_FTDI_Flashing If you'd like, you can try adding support for the FTDI chip in ft2232_spi.c. If the FTDI D2XX is significantly different you can create a new file (ftdi_d2xx.c, for example), and use ft2232_spi.c as a template.

1 0

[PATCH] adding Adesto at25sf041a serial spi flash
by Diego Roversi 14 Oct '16

14 Oct '16

Hello, This patch implements the handling of the Adesto AT25SF041A flash chip. This chip is an improved version of the Atmel AT25DF041A, and support the same protcol, but with a different id, 0x8401 insted of 0x4401. Tested on BeagleBone board. Signed-off-by: Diego Roversi <diegor(a)tiscali.it> Index: flashchips.c =================================================================== --- flashchips.c (revision 1955) +++ flashchips.c (working copy) @@ -1558,10 +1558,48 @@ .read = spi_chip_read, .voltage = {2700, 3600}, /* 2.3-3.6V & 2.7-3.6V models available */ }, { + .vendor = "Adesto", + .name = "AT25SF041A", + .bustype = BUS_SPI, + .manufacture_id = ATMEL_ID, + .model_id = ATMEL_AT25SF041A, + .total_size = 512, + .page_size = 256, + .feature_bits = FEATURE_WRSR_WREN, + .tested = TEST_OK_PREW, + .probe = probe_spi_rdid, + .probe_timing = TIMING_ZERO, + .block_erasers = + { + { + .eraseblocks = { {4 * 1024, 128} }, + .block_erase = spi_block_erase_20, + }, { + .eraseblocks = { {32 * 1024, 16} }, + .block_erase = spi_block_erase_52, + }, { + .eraseblocks = { {64 * 1024, 8} }, + .block_erase = spi_block_erase_d8, + }, { + .eraseblocks = { {512 * 1024, 1} }, + .block_erase = spi_block_erase_60, + }, { + .eraseblocks = { {512 * 1024, 1} }, + .block_erase = spi_block_erase_c7, + } + }, + .printlock = spi_prettyprint_status_register_at25df, + .unlock = spi_disable_blockprotect_at2x_global_unprotect, + .write = spi_chip_write_256, + .read = spi_chip_read, + .voltage = {2700, 3600}, /* 2.3-3.6V & 2.7-3.6V models available */ + }, + + { .vendor = "Atmel", .name = "AT25DF081", .bustype = BUS_SPI, .manufacture_id = ATMEL_ID, .model_id = ATMEL_AT25DF081, Index: flashchips.h =================================================================== --- flashchips.h (revision 1955) +++ flashchips.h (working copy) @@ -131,10 +131,11 @@ #define AMIC_A49LF040A 0x9d #define ATMEL_ID 0x1F /* Atmel (now used by Adesto) */ #define ATMEL_AT25DF021 0x4300 #define ATMEL_AT25DF041A 0x4401 +#define ATMEL_AT25SF041A 0x8401 #define ATMEL_AT25DF081 0x4502 /* EDI 0x00. AT25DL081 has same ID + EDI 0x0100 */ #define ATMEL_AT25DF081A 0x4501 /* Yes, 81A has a lower number than 81 */ #define ATMEL_AT25DF161 0x4602 #define ATMEL_AT25DF321 0x4700 /* Same as 26DF321 */ #define ATMEL_AT25DF321A 0x4701 -- Diego Roversi <diegor(a)tiscali.it>

1 0

Can't find Write protect screw on Samsung XE500C21
by Chris M 14 Oct '16

14 Oct '16

Hello, I'm wondering where i could find the Write protect screw on my Samsung XE500C21. Got any ideas where I could find it? Regards -Chris

1 0

[PATCH 4/4] Initial MX66L51235F support
by Timothy Pearson 13 Oct '16

13 Oct '16

Add initial support for MX66L51235F devices. --- flashchips.c | 47 +++++++++++++++++++++++++++++++++++++++++++++++ flashchips.h | 1 + 2 files changed, 48 insertions(+) diff --git a/flashchips.c b/flashchips.c index 61075dd..1e6f4a4 100644 --- a/flashchips.c +++ b/flashchips.c @@ -8092,6 +8092,53 @@ const struct flashchip flashchips[] = { { .vendor = "Macronix", + .name = "MX66L51235F", + .bustype = BUS_SPI, + .manufacture_id = MACRONIX_ID, + .model_id = MACRONIX_MX66L51235F, + .total_size = 65536, + .page_size = 256, + /* OTP: 512B total; enter 0xB1, exit 0xC1 */ + .feature_bits = FEATURE_WRSR_WREN | FEATURE_OTP | FEATURE_4BA_SUPPORT, + .four_bytes_addr_funcs = + { + .enter_4ba = spi_enter_4ba_b7, /* enter 4-bytes addressing mode by CMD B7 */ + .read_nbyte = spi_nbyte_read_4ba, /* read from 4-bytes addressing mode */ + .program_byte = spi_byte_program_4ba, /* write from 4-bytes addressing mode */ + .program_nbyte = spi_nbyte_program_4ba /* write from 4-bytes addressing mode */ + }, + .tested = TEST_OK_PREW, + .probe = probe_spi_rdid, + .probe_timing = TIMING_ZERO, + .block_erasers = + { + { + .eraseblocks = { {4 * 1024, 16384} }, + .block_erase = spi_block_erase_20_4ba, + }, { + .eraseblocks = { {32 * 1024, 2048} }, + .block_erase = spi_block_erase_52_4ba, + }, { + .eraseblocks = { {64 * 1024, 1024} }, + .block_erase = spi_block_erase_d8_4ba, + }, { + .eraseblocks = { {64 * 1024 * 1024, 1} }, + .block_erase = spi_block_erase_60, + }, { + .eraseblocks = { {64 * 1024 * 1024, 1} }, + .block_erase = spi_block_erase_c7, + } + }, + /* TODO: security register and SBLK/SBULK; MX25L12835F: configuration register */ + .printlock = spi_prettyprint_status_register_bp3_srwd, /* bit6 is quad enable */ + .unlock = spi_disable_blockprotect_bp3_srwd, + .write = spi_chip_write_256, + .read = spi_chip_read, /* Fast read (0x0B) supported */ + .voltage = {2700, 3600}, + }, + + { + .vendor = "Macronix", .name = "MX25U1635E", .bustype = BUS_SPI, .manufacture_id = MACRONIX_ID, diff --git a/flashchips.h b/flashchips.h index 9ffb30f..7171a62 100644 --- a/flashchips.h +++ b/flashchips.h @@ -482,6 +482,7 @@ #define MACRONIX_MX25L25635F 0x2019 /* Same as MX25L25639F, but the latter seems to not support REMS */ #define MACRONIX_MX25L1635D 0x2415 #define MACRONIX_MX25L1635E 0x2515 /* MX25L1635{E} */ +#define MACRONIX_MX66L51235F 0x201a /* MX66L51235F */ #define MACRONIX_MX25U1635E 0x2535 #define MACRONIX_MX25U3235E 0x2536 /* Same as MX25U6435F */ #define MACRONIX_MX25U6435E 0x2537 /* Same as MX25U6435F */ -- 2.9.3

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom October 2016