From: zoldnap at freemail.hu <zoldnap@freemail.hu>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] dataflash problem
Date: Mon, 10 Oct 2005 01:27:15 +0000 [thread overview]
Message-ID: <1128907635.31053.5.camel@localhost> (raw)
In-Reply-To: <20051009213620.GB24243@vap.homelinux.net>
Hi,
thank you for your answer!
in the last few hours I've managed to track down that the error is not
in
the address range checking, but in at45.c : AT91F_DataFlashRead
function.
Within that, the AT91F_DataFlashWaitReady function is timeouting
resulting that cmd_mem.c:do_mem_cmd continues execution at line 167,
where it attemts to read non-existing memory..
I dont really know why is this timeout occuring, since I've written
some codes which run natively (without Linux) on the board, and I
can access the DataFlash without problems.
regards,
Zoli
> Absence of NAND flash uncovers an issue with flash address
> ranges checking.
> The problem can be bypassed with either of two methods:
>
> First: hack address ranges checking in common/flash.c:
>
> --- u-boot-1.1.3/common/flash.c 2005-08-14 03:53:35.000000000 +0400
> +++ u-boot-1.1.3-new/common/flash.c 2005-09-15 01:15:58.000000000 +0400
> @@ -105,6 +105,8 @@
> int i;
>
> for (i=0, info=&flash_info[0]; i<CFG_MAX_FLASH_BANKS; ++i, ++info) {
> + if (info->size == 0)
> + continue;
> if (info->flash_id != FLASH_UNKNOWN &&
> addr >= info->start[0] &&
> /* WARNING - The '- 1' is needed if the flash
>
>
> Second: disable NAND flash by setting CFG_MAX_FLASH_BANKS to 0 in board
> config.
>
> I'm not sure it is right solution, but it at least looks as working
> for me :)
>
--
zoldnap at freemail.hu <zoldnap@freemail.hu>
prev parent reply other threads:[~2005-10-10 1:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-09 22:58 [U-Boot-Users] dataflash problem zoldnap at freemail.hu
2005-10-09 21:36 ` Andrey P. Vasilyev
2005-10-10 1:27 ` zoldnap at freemail.hu [this message]
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=1128907635.31053.5.camel@localhost \
--to=zoldnap@freemail.hu \
--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