From: Franz Skale <fs@cubit.at>
To: u-boot@lists.denx.de
Subject: [U-Boot] Write ENV to File and flash it with openocd (problem) !!!
Date: Thu, 09 Aug 2012 17:05:44 +0200 [thread overview]
Message-ID: <5023D1C8.8020303@cubit.at> (raw)
Hi,
i hope this is the place to solve my problem.
Shortdesc:
I am using opencd and fw_setenv (2008) from the sheeva plug installer to
flash uboot and the env.
The boards/sheevaplug.cfg is reflecting two functions for flashing uboot
and the env.
The sheevapluginstaller version is patched to use the file uboot-env.bin
to write the env to a file and flash it.
With the uboot version 2012.04.1 i am able to flash the uboot loader but
not the env.
There's no error but the env is default.
Could it be, that the Offset in the file of the patched
sheevapluginstaller for a flat file is wrong ?
The fw_env.h of the patched sheevapluginstaller (20080520)
#undef HAVE_REDUND /* For systems with 2 env sectors */
#define DEVICE1_NAME "uboot-env.bin"
#define DEVICE2_NAME "/dev/mtd2"
#define DEVICE1_OFFSET 0x0000
#define ENV1_SIZE 0x00020000 /* 64 KB */
#define DEVICE1_ESIZE 0x00020000 /* 64 KB */
The 2012 version:
#define HAVE_REDUND /* For systems with 2 env sectors */
#define DEVICE1_NAME "/dev/mtd1"
#define DEVICE2_NAME "/dev/mtd2"
#define DEVICE1_OFFSET 0x0000
#define ENV1_SIZE 0x4000
#define DEVICE1_ESIZE 0x4000
#define DEVICE1_ENVSECTORS 2
What has to be done, that the flash to the NAND via openocd will wor
properly ?
I must be able to write to an env file which should work with the
openocd command reflash_env.
I am running out of ideas yet.
Thanks in advance
Franz
reply other threads:[~2012-08-09 15:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=5023D1C8.8020303@cubit.at \
--to=fs@cubit.at \
--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