From: Brendan Simon (eTRIX) <brendan.simon@etrix.com.au>
To: u-boot@lists.denx.de
Subject: [U-Boot] fw_env.config settings for Digilent ZedBoard (Zynq 7020 Soc)
Date: Sun, 6 Dec 2015 12:01:08 +1100 [thread overview]
Message-ID: <566388D4.6070806@etrix.com.au> (raw)
Hi,
I'm using a Digilent ZedBoard with a Xilinx Zynq 7020 SoC. The kernel
is from Analog Devices and is a fork of 4.0.0 (according to the Makefile).
I am struggling to work out the fw_env.config file required to use with
fw_printenv/fw_saveenv.
fw_printenv continually gives me CRC error and uses the defaults.
Google hasn't provided much assistance, with some people reporting that
the settings required are different to what /proc/mtd shows.
Here is info from /proc/mtd and my /etc/fw_env.config.
root at bjs:~# cat
/proc/mtd
dev: size erasesize name
mtd0: 00500000 00010000 "boot"
mtd1: 00020000 00010000 "bootenv"
mtd2: 00020000 00010000 "config"
mtd3: 00a80000 00010000 "image"
mtd4: 01040000 00010000 "spare"
root at bjs:~# cat
/etc/fw_env.config
# Configuration file for fw_(printenv/setenv) utility.
# Up to two entries are valid, in this case the redundant
# environment sector is assumed present.
# MTD device name Device offset Env. size Flash sector size
# /dev/mtd1 0x0000 0x20000 0x40000
# /dev/mtd1 0x0000 0x20000 0x20000
# /dev/mtd1 0x0000 0x20000 0x10000
# /dev/mtd2 0x0000 0x20000 0x40000
# /dev/mtd2 0x0000 0x20000 0x20000
/dev/mtd2 0x0000 0x20000 0x10000
Does anyone have any insight into what the correct fw_env.config
settings should be from the above info?
How can I find out the correct settings. Is there a command in u-boot
itself which will report the correct information?
Thanks,
Brendan.
next reply other threads:[~2015-12-06 1:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-06 1:01 Brendan Simon [this message]
2015-12-07 9:35 ` [U-Boot] fw_env.config settings for Digilent ZedBoard (Zynq 7020 Soc) Anatolij Gustschin
2015-12-07 11:38 ` Brendan Simon
2015-12-07 12:56 ` Anatolij Gustschin
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=566388D4.6070806@etrix.com.au \
--to=brendan.simon@etrix.com.au \
--cc=u-boot@lists.denx.de \
/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