public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stephen Graf <stephen.graf@gmail.com>
To: Andre Przywara <andre.przywara@arm.com>
Cc: Mikhail Kalashnikov <iuncuim@gmail.com>,
	Jagan Teki <jagan@amarulasolutions.com>,
	Vignesh R <vigneshr@ti.com>,
	Jaehoon Chung <jh80.chung@samsung.com>,
	Jernej Skrabec <jernej.skrabec@gmail.com>,
	Piotr Oniszczuk <piotr.oniszczuk@gmail.com>,
	u-boot@lists.denx.de, linux-sunxi@lists.linux.dev
Subject: Re: mdt_debug write
Date: Wed, 29 Nov 2023 16:20:33 -0800	[thread overview]
Message-ID: <a2e62d55-8209-432e-b01f-253e05c11186@gmail.com> (raw)
In-Reply-To: <0d46cc83-8820-4bf2-95bd-a0c12b6f7aff@arm.com>

Thank you for the update Andre.

The flashcp worked.  I rebooted without an SD card and the new u-boot 
started properly.

Now as to making a patch file, I will give it a try.  Keep in mind that 
when I started my working career the concept of patching was to shuffle 
a deck of IBM 80 column punched cards.

Console output:

root@orangepizero3:~# flashcp -v 
/home/sysadmin/u-boot-sunxi-with-spl.bin_with_792_clk /dev/mtd0
Erasing blocks: 206/206 (100%)
Writing data: 822k/822k (100%)
Verifying data: 822k/822k (100%)
root@orangepizero3:~#




On 2023-11-29 3:57 p.m., Andre Przywara wrote:
> Hi Stephen,
> 
> On 28/11/2023 20:07, Stephen Graf wrote:
>> Below is the consol log from trying to use mtd_debug write. It 
>> returned immediately with a strange success message.
>>
>> root@orangepizero3:~# mtd_debug write /dev/mtd0 0 0xf0000 
>> /home/sysadmin/u-boot-sunxi-with-spl.bin
>> file_to_flash: fread, size 0xf0000, n 0xf0000
>> fread(): Success
> 
> interesting, I was under the impression that "mtd_debug write" would be 
> the way to write to flash. In hindsight, the "debug" in that name should 
> have probably put me off. Anyway, "cat" is probably not a good choice, 
> "dd" is better, but it looks like "flashcp" (also part of mtdutils) is 
> the go-to tool, since it does the required erasing automatically and 
> also reportedly does some error detection. Can you please test this?
> # flashcp u-boot-sunxi-with-spl.bin /dev/mtd0
> I would test this on my end ASAP as well.
> 
> Do you feel like sending a patch to the U-Boot documentation to get this 
> changed then?
> 
> Thanks,
> Andre
> 

  reply	other threads:[~2023-11-30  0:20 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-14  1:31 [PATCH 0/3] sunxi: add OrangePi Zero 3 board support Andre Przywara
2023-11-14  1:31 ` [PATCH 1/3] mtd: spi-nor: Add support for zBIT ZB25VQ128 Andre Przywara
2023-11-14  1:31 ` [PATCH 2/3] sunxi: H616: remove default AXP305 selection Andre Przywara
2023-11-14 13:24   ` Jaehoon Chung
2023-11-14  1:31 ` [PATCH 3/3] sunxi: H616: Add OrangePi Zero 3 board support Andre Przywara
2023-11-25 17:43   ` Mikhail Kalashnikov
2023-11-26  0:23     ` Andre Przywara
2023-11-26  4:27       ` Stephen Graf
2023-11-26 12:23         ` Andre Przywara
2023-11-27 20:21           ` Stephen Graf
2023-11-27 22:31             ` Stephen Graf
2023-11-28  1:37               ` Andre Przywara
2023-11-28  2:35                 ` Stephen Graf
2023-11-28  6:03                 ` Stephen Graf
2023-11-28 20:07                 ` mdt_debug write Stephen Graf
2023-11-29 23:57                   ` Andre Przywara
2023-11-30  0:20                     ` Stephen Graf [this message]
2023-11-30  1:13                     ` Stephen Graf
2023-12-01  0:27                       ` Andre Przywara
2023-12-01 18:50                         ` [PATCH 1/1] correct documentation for SPI flashing Stephen Graf
2023-12-03 23:40                           ` Andre Przywara
2023-11-29 18:45                 ` OrangePI Zero3 memory timing testing Stephen Graf
2023-11-30  0:10                   ` Andre Przywara
2023-11-30  1:15                     ` Siarhei Siamashka
2023-11-28  1:29             ` [PATCH 3/3] sunxi: H616: Add OrangePi Zero 3 board support Andre Przywara
2023-11-26 13:30       ` Mikhail Kalashnikov
2023-11-26 11:45     ` Bob McChesney

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=a2e62d55-8209-432e-b01f-253e05c11186@gmail.com \
    --to=stephen.graf@gmail.com \
    --cc=andre.przywara@arm.com \
    --cc=iuncuim@gmail.com \
    --cc=jagan@amarulasolutions.com \
    --cc=jernej.skrabec@gmail.com \
    --cc=jh80.chung@samsung.com \
    --cc=linux-sunxi@lists.linux.dev \
    --cc=piotr.oniszczuk@gmail.com \
    --cc=u-boot@lists.denx.de \
    --cc=vigneshr@ti.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox