From: Teresa Remmet <t.remmet@phytec.de>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: Barebox List <barebox@lists.infradead.org>
Subject: AM335x NAND boot on next
Date: Mon, 17 Dec 2018 11:54:30 +0100 [thread overview]
Message-ID: <1545044070.6213.11.camel@phytec.de> (raw)
Hello Sascha,
I watend to test the gpmc driver changes for our am335x boards using
latest next. I noticed that booting from nand is not working correct
any more. The MLO can not correctly obtain the image size of the
barebox image.
barebox 2018.11.0-00199-g5a1a5ed2537d #1549 Mon Dec 17 10:46:01 CET
2018
Board: Phytec phyCORE AM335x
nand: ONFI flash detected
nand: NAND device: Manufacturer ID: 0x2c, Chip ID: 0xdc (Micron
MT29F4G08ABADAH4), 512Mi
B, page size: 2048, OOB size: 64
booting from NAND
failed to get image size
trying to load image from backup partition.
failed to get image size
booting failed
bisected this down to:
5a1a5ed2537d7d12f851f3778707681d6c08d6e8 is the first bad commit
commit 5a1a5ed2537d7d12f851f3778707681d6c08d6e8
Author: Sascha Hauer <s.hauer@pengutronix.de>
Date: Tue Oct 9 15:28:12 2018 +0200
ARM: images: use piggydata
I guess the get_image_size(void *head) of arch/arm/mach-omap/xload.c
needs rework. Any hint how to fix this?
SD-Card booting works. As tested with bbb.
Regards,
Teresa
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2018-12-17 10:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-17 10:54 Teresa Remmet [this message]
2018-12-17 11:14 ` AM335x NAND boot on next Sascha Hauer
2018-12-17 14:02 ` Teresa Remmet
2018-12-18 7:44 ` Sascha Hauer
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=1545044070.6213.11.camel@phytec.de \
--to=t.remmet@phytec.de \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.