From: Ivan Kuten <ivan.kuten@promwad.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] 1.1.6 at91 based board dataflash copy panic.
Date: Thu, 4 Jan 2007 16:54:14 +0200 (EET) [thread overview]
Message-ID: <49143.127.0.0.1.1167922454.squirrel@localhost> (raw)
In-Reply-To: <1167921259.5828.29.camel@localhost>
Hello,
> When CFG_NO_FLASH is defined the content of either flash.h or flash.c is
> not included in the code, but dataflash support depends on that so I get
> a compilation error. I have been playing around and it seems that it is
> not possible to do a exclusive dataflash binary for u-boot, am I right?
Yes, now there is quite a mess with dataflash only setup.
I was able to do "exclusive dataflash binary for u-boot" by adding
necessary defines from flash.h to dataflash.h (these changes where
included in patch I sent):
------------------------------------------------
#define ERR_OK 0
#define ERR_TIMOUT 1
#define ERR_NOT_ERASED 2
#define ERR_PROTECTED 4
#define ERR_INVAL 8
#define ERR_ALIGN 16
#define ERR_UNKNOWN_FLASH_VENDOR 32
#define ERR_UNKNOWN_FLASH_TYPE 64
#define ERR_PROG_ERROR 128
/*
* Protection Flags for flash_protect():
*/
#define FLAG_PROTECT_SET 0x01
#define FLAG_PROTECT_CLEAR 0x02
------------------------------------------------
and removing flash related commands such as CFG_CMD_FLASH CFG_CMD_IMLS
from board config. It was just quick workaround.
------------------------------------
Best regards, Ivan
Embedded Linux Engineer
Promwad - www.promwad.com
------------------------------------
> Hi.
>
> I have applied that patch and the problem is solved. Anyway I have
> needed to do some additional changes. I will try to explain.
>
> When CFG_NO_FLASH is defined the content of either flash.h or flash.c is
> not included in the code, but dataflash support depends on that so I get
> a compilation error. I have been playing around and it seems that it is
> not possible to do a exclusive dataflash binary for u-boot, am I right?
>
> As code is written CFG_NO_FLASH means that there isn't _any kind_ of
> flash. So I guess the define in your patch should be CFG_DATAFLASH_ONLY
> or similar.
>
> Thanks for your help,
>
> Regards.
>
> --
> Gerardo Mart?nez Bernat
> tlf: 91 351 11 20
> Barracuda Systems SL
> C/ Luxemburgo n?4
> 28224 Madrid
>
>
>
>
>
next prev parent reply other threads:[~2007-01-04 14:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.221629.1167910946.30209.u-boot-users@lists.sourceforge.net>
2007-01-04 12:17 ` [U-Boot-Users] 1.1.6 at91 based board dataflash copy panic Ivan Kuten
[not found] ` <1167921259.5828.29.camel@localhost>
2007-01-04 14:54 ` Ivan Kuten [this message]
2006-12-26 11:53 Raúl Sánchez Siles
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=49143.127.0.0.1.1167922454.squirrel@localhost \
--to=ivan.kuten@promwad.com \
--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