From: dvo <dan.vo.ict@jvn.edu.vn>
To: u-boot@lists.denx.de
Subject: spi_flash_read issue
Date: Thu, 20 Feb 2020 03:10:26 -0700 (MST) [thread overview]
Message-ID: <1582193426408-0.post@n7.nabble.com> (raw)
Hello,
I encounter an issue with spi_flash_read function. I'd copy uboot from SPI
Flash to DDRAM. If I use the function once. It works OK. If I use the
function is more than 1 time, then it doesn't work properly.
Here is the procedure of what I did:
uboot version: U-Boot 2019.07-00013-g6107815c9c
uboot size: 244288 Bytes
case 1:
- Copy uboot to 0x81000000 -> Jump to uboot at 0x81000000 OK
case 2:
- Copy uboot to 0x81000000
- Copy uboot to 0x83000000
-> Jump to uboot at 0x83000000 NOK. Only able to load some parts of uboot
and then hang.
I hexdump and do memory comparison between 0x81000000 and 0x83000000. The
memory is different from i=78078.
Do I need to do something in between 2 copies to solve the issue?
Has anyone experienced this issue?
Thanks for any help or suggestion.
Dan
--
Sent from: http://u-boot.10912.n7.nabble.com/
next reply other threads:[~2020-02-20 10:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-20 10:10 dvo [this message]
2020-02-20 12:02 ` spi_flash_read issue Fabio Estevam
2020-02-24 14:18 ` dvo
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=1582193426408-0.post@n7.nabble.com \
--to=dan.vo.ict@jvn.edu.vn \
--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