On 31/03/2016 22:32, Kevin Hilman wrote:
On Thu, Mar 31, 2016 at 12:05 PM, Kevin Hilman khilman@baylibre.com wrote:
On Mon, Feb 15, 2016 at 8:31 AM, Marc Titinger mtitinger@baylibre.com wrote:
From: Marc Titinger mtitinger@baylibre.com
- specific u-boot prompt
- specific C-c interrupt char
- uImage only: hardkernel u-boot sources are heavily hardcoded in an old u-boot version (no bootz)
Signed-off-by: Marc Titinger mtitinger@baylibre.com
Tested this in my local LAVA instance with this board:
Tested-by: Kevin Hilman khilman@baylibre.com
As Neil pointed out, it does an extra 'dhcp' command in u-boot, which is harmless, but should still be removed. After that change:
Acked-by: Kevin Hilman khilman@baylibre.com
Oops, scratch that.
I wasn't testing what I thought I was testing. This doesn't seem to work yet for me. Among other things, I think it needs a text_offset setting for a specific uImage load address required by the factory boot loader. But even with that, I'm not having luck with the appended DTB on this platform.
Yes, my apologies for the poor follow-up with this right now. I too thought this was doing ok, but I think the default config is missing proper FDT handling! parts like:
setenv fdt_addr_r "'0xxxxxxxxxx", setenv loadfdt "'tftp ${fdt_addr_r} {DTB}'", ... run loadfdt; ...
Kevin