From patchwork Thu Nov 25 14:02:16 2021 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: =?utf-8?b?0KHQtdGA0LPQtdC5INCv0L3QvtCy0LjRhw==?= X-Patchwork-Id: 1559754 Return-Path: X-Original-To: incoming@patchwork.ozlabs.org Delivered-To: patchwork-incoming@bilbo.ozlabs.org Authentication-Results: bilbo.ozlabs.org; dkim=fail reason="signature verification failed" (1024-bit key; unprotected) header.d=yandex.ru header.i=@yandex.ru header.a=rsa-sha256 header.s=mail header.b=SXqyjcTP; dkim-atps=neutral Authentication-Results: ozlabs.org; spf=pass (sender SPF authorized) smtp.helo=coreboot.org (client-ip=78.46.105.101; helo=coreboot.org; envelope-from=flashrom-bounces@flashrom.org; receiver=) Received: from coreboot.org (coreboot.org [78.46.105.101]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by bilbo.ozlabs.org (Postfix) with ESMTPS id 4J0Lpc2lSMz9sVc for ; Fri, 26 Nov 2021 02:07:51 +1100 (AEDT) Received: from authenticated-user (PRIMARY_HOSTNAME [PUBLIC_IP]) by coreboot.org (Postfix) with ESMTPA id 6740016E3D31; Thu, 25 Nov 2021 15:07:42 +0000 (UTC) Received: from authenticated-user (PRIMARY_HOSTNAME [PUBLIC_IP]) by coreboot.org (Postfix) with ESMTP id C70AC16E3D29 for ; Thu, 25 Nov 2021 14:02:17 +0000 (UTC) Received: from authenticated-user (PRIMARY_HOSTNAME [PUBLIC_IP]) by forward108j.mail.yandex.net (Yandex) with ESMTP id D048B3F209A4; Thu, 25 Nov 2021 17:02:16 +0300 (MSK) Received: from authenticated-user (PRIMARY_HOSTNAME [PUBLIC_IP]) by iva8-bad74b408dcf.qloud-c.yandex.net (mxback/Yandex) with ESMTP id cWNJPTu7cZ-2GDSgi9m; Thu, 25 Nov 2021 17:02:16 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1637848936; bh=MnnvgKSIvSbkGJXV4FEOiGxSGoMp3/qLIi0JjB3dHNU=; h=In-Reply-To:References:Date:To:From:Subject:Message-ID:Cc; b=SXqyjcTPyXImqTtk1zMKN9ceLNzOyqSLL3XULaBxhWQmGhvM1ktfLG+9k+KQ36foq g/r6RgEgP2dc7OYsbl9po4rOQs6gxtUtUxQxM4UbIkD/oE4eqvd0Zsv30KkyDXscAb MOsUdKaM+TlQpxhypJCsLOK2r+B4vQvz+xzf+wvA= Received: from authenticated-user (PRIMARY_HOSTNAME [PUBLIC_IP]) Thu, 25 Nov 2021 17:02:16 +0300 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) (Client certificate not present) X-Yandex-Fwd: 2 Message-ID: From: =?utf-8?b?0KHQtdGA0LPQtdC5INCv0L3QvtCy0LjRhw==?= To: Mike Banon Date: Thu, 25 Nov 2021 17:02:16 +0300 In-Reply-To: References: MIME-Version: 1.0 X-MailFrom: sergei.ianovich@yandex.ru X-Mailman-Rule-Hits: nonmember-moderation X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-flashrom.flashrom.org-0; header-match-flashrom.flashrom.org-1; header-match-flashrom.flashrom.org-2; header-match-flashrom.flashrom.org-3; header-match-flashrom.flashrom.org-4; header-match-flashrom.flashrom.org-5; header-match-flashrom.flashrom.org-6; header-match-flashrom.flashrom.org-7; header-match-flashrom.flashrom.org-8; header-match-flashrom.flashrom.org-9; header-match-flashrom.flashrom.org-10; header-match-flashrom.flashrom.org-11; header-match-flashrom.flashrom.org-12; header-match-flashrom.flashrom.org-13; header-match-flashrom.flashrom.org-14; header-match-flashrom.flashrom.org-15; header-match-flashrom.flashrom.org-16; header-match-flashrom.flashrom.org-17; header-match-flashrom.flashrom.org-18; header-match-flashrom.flashrom.org-19; header-match-flashrom.flashrom.org-20; header-match-flashrom.flashrom.org-21; header-match-flashrom.flashrom.org- 22; header-match-flashrom.flashrom.org-23; header-match-flashrom.flashrom.org-24; header-match-flashrom.flashrom.org-25; header-match-flashrom.flashrom.org-26; header-match-flashrom.flashrom.org-27; header-match-flashrom.flashrom.org-28; header-match-flashrom.flashrom.org-29; header-match-flashrom.flashrom.org-30; header-match-flashrom.flashrom.org-31; header-match-flashrom.flashrom.org-32; header-match-flashrom.flashrom.org-33; header-match-flashrom.flashrom.org-34; header-match-flashrom.flashrom.org-35; header-match-flashrom.flashrom.org-36; header-match-flashrom.flashrom.org-37; header-match-flashrom.flashrom.org-38; header-match-flashrom.flashrom.org-39; header-match-flashrom.flashrom.org-40; header-match-flashrom.flashrom.org-41; header-match-flashrom.flashrom.org-42; header-match-flashrom.flashrom.org-43; header-match-flashrom.flashrom.org-44; header-match-flashrom.flashrom.org-45; header-match-flashrom.flashrom.org-46; header-match-flashrom.flashrom.org-47; header-match-flash rom.flashrom.org-48; header-match-flashrom.flashrom.org-49; header-match-flashrom.flashrom.org-50; header-match-flashrom.flashrom.org-51; header-match-flashrom.flashrom.org-52; header-match-flashrom.flashrom.org-53; header-match-flashrom.flashrom.org-54; header-match-flashrom.flashrom.org-55; header-match-flashrom.flashrom.org-56; header-match-flashrom.flashrom.org-57; header-match-flashrom.flashrom.org-58; header-match-flashrom.flashrom.org-59; header-match-flashrom.flashrom.org-60; header-match-flashrom.flashrom.org-61; header-match-flashrom.flashrom.org-62; header-match-flashrom.flashrom.org-63; header-match-flashrom.flashrom.org-64; header-match-flashrom.flashrom.org-65; header-match-flashrom.flashrom.org-66; header-match-flashrom.flashrom.org-67; header-match-flashrom.flashrom.org-68; header-match-flashrom.flashrom.org-69; header-match-flashrom.flashrom.org-70; header-match-flashrom.flashrom.org-71; header-match-flashrom.flashrom.org-72; header-match-flashrom.flashrom.org-73; h eader-match-flashrom.flashrom.org-74; header-match-flashrom.flashrom.org-75; header-match-flashrom.flashrom.org-76; header-match-flashrom.flashrom.org-77; header-match-flashrom.flashrom.org-78; header-match-flashrom.flashrom.org-79; header-match-flashrom.flashrom.org-80; header-match-flashrom.flashrom.org-81; header-match-flashrom.flashrom.org-82; header-match-flashrom.flashrom.org-83; header-match-flashrom.flashrom.org-84; header-match-flashrom.flashrom.org-85 Message-ID-Hash: XS5KCRJVMZE3XL5UVKH6IXONKR2EJBPN X-Message-ID-Hash: XS5KCRJVMZE3XL5UVKH6IXONKR2EJBPN X-Mailman-Approved-At: Thu, 25 Nov 2021 15:07:30 +0000 CC: flashrom X-Mailman-Version: 3.3.5rc1 Precedence: list Subject: [flashrom] Re: failed write to an erased chip List-Id: flashrom discussion and development mailing list Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: Authentication-Results: coreboot.org; auth=pass smtp.auth=mailman@coreboot.org smtp.mailfrom=flashrom-bounces@flashrom.org X-Spamd-Bar: / On Wed, 2021-11-24 at 13:17 +0300, Mike Banon wrote: > Your log looks right to me, like a file has been programmed into your > chip successfully. How did you check that the writing operation was a > failure instead? Thanks for looking into this. The error message didn't make into the log, b/c it was on stderr. The diff is: # flashrom -p ... -VVV -w 8.bin > log3 2>&1 $ diff -aU 1 log2 log3 If I read the image from chip, I get 8Mib of 0xFF. I can attach the full log if necessary. > P.S. I hope that your 1.8V chip wasn't partially damaged by a > temporary usage of 3.3V on it It is possible, but seems unlikely. The chip correctly responds to flasrom probing queries. I suspect I activated a write protection of some kind. /WP is high at 1.81V now. So I am investigation software WP in the chip now. --- log2 2021-11-23 19:06:06.693202071 +0300 +++ log3 2021-11-25 16:51:28.493684854 +0300 @@ -1084,2 +1084,6 @@ Erase/write done. -Verifying flash... programmer_unmap_flash_region: unmapped 0x00000000 +Verifying flash... FAILED at 0x00000010! Expected=0x5a, Found=0xff, failed byte count from 0x00000000-0x007fffff: 0x3489ce +Your flash chip is in an unknown state. +Please report this on IRC at chat.freenode.net (channel #flashrom) or +mail flashrom@flashrom.org, thanks! +programmer_unmap_flash_region: unmapped 0x00000000