From: Trevor Woerner <twoerner@gmail.com>
To: drew.moseley@mender.io
Cc: yocto@yoctoproject.org
Subject: Re: [meta-chip][RFC PATCH 3/3] chip: Add chip-u-boot-scr recipe and flash script
Date: Mon, 19 Jun 2017 01:48:32 -0400 [thread overview]
Message-ID: <20170619054832.GA7840@linux-uys3> (raw)
In-Reply-To: <195a92fc1faa49495d1a2b6cda0134f07ce72189.1497646644.git.drew.moseley@mender.io>
On Fri 2017-06-16 @ 05:15:40 PM, drew.moseley@mender.io wrote:
> +This script will take some time to execute.
true
> If you have a serial console connected to
> +your board, you will see the progress and a message on the console will indicate when
> +the flashing is completed.
hmmm, never saw this. I have a console connected, the moment the script
started, on the console I got:
U-Boot SPL 2016.01 (Jun 19 2017 - 00:32:19)
DRAM: 512 MiB
CPU: 1008000000Hz, AXI/AHB/APB: 3/2/2
Trying to boot from
which looks right, the date+time are good.
Where I started the script I get:
# UBI_IMAGE=core-image-full-cmdline-chip.ubi
# tmp-glibc/deploy/images/chip/flash_CHIP_board.sh
100% [================================================] 3537 kB, 557.5 kB/s
100% [================================================] 616 kB, 823.9 kB/s
100% [================================================] 2 kB, 733.9 kB/s
100% [================================================] 654311 kB, 771.4 kB/s
> Additionally, once the image is properly flashed, the status
> +LED on the CHIP board will flash 30 times per second indicating that it is safe to power
> +down your board and disable FEL mode.
I don't get any LED flashing, and nothing other than what I've pasted above on
the console.
Rebooting the board after flashing outside of FEL mode simply boots the
previous u-boot and image.
Any thoughts?
next prev parent reply other threads:[~2017-06-19 5:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-16 21:15 [meta-chip][RFC PATCH 0/3] Initial attempt at flashing instructions drew.moseley
2017-06-16 21:15 ` [meta-chip][RFC PATCH 1/3] u-boot-chip: Deploy the sunxi-spl-with-ecc.bin file drew.moseley
2017-06-16 21:15 ` [meta-chip][RFC PATCH 2/3] chip: Build sunxi-tools-native drew.moseley
2017-06-19 4:30 ` Trevor Woerner
2017-06-16 21:15 ` [meta-chip][RFC PATCH 3/3] chip: Add chip-u-boot-scr recipe and flash script drew.moseley
2017-06-19 5:19 ` Trevor Woerner
2017-06-19 5:48 ` Trevor Woerner [this message]
2017-06-19 7:33 ` Trevor Woerner
2017-06-19 11:22 ` Drew Moseley
2017-06-19 14:40 ` Trevor Woerner
2017-06-22 4:22 ` Petter Mabäcker
2017-06-22 12:16 ` Drew Moseley
2017-06-22 4:16 ` [meta-chip][RFC PATCH 0/3] Initial attempt at flashing instructions Petter Mabäcker
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=20170619054832.GA7840@linux-uys3 \
--to=twoerner@gmail.com \
--cc=drew.moseley@mender.io \
--cc=yocto@yoctoproject.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.