Hi Ron,
On 28 February 2017 at 17:06, Ron Brash wrote:
> Hello,
>
> Here is a list of things I have tried: The raw zImage (which is compressed
> with XZ), various addresses from indeed load address 0x2300, entry
> at 0x23008000
> (and the same), I've tried setting the
Hi Ron,
On 21 February 2017 at 11:08, Ron Brash wrote:
> Hello all,
>
> I am adding verified kernel support on a board we are using and I am
> struggling to fully understand all of the concepts and steps required to
> pull everything together (on ARM, using ZImages and
Hi Ron,
On 27 February 2017 at 14:49, Ron Brash wrote:
> Looks like far more progress:
>
> #> setenv my_bootcount 0; bootm 0xD0084000
> Initial value for argc=3
> Final value for argc=3
> ## Current stack ends at 0x23f11db8 * kernel: cmdline image address =
> 0xd0084000
>
I've been swamped this week. I hope to pick this up with you next week.
On Tue, Feb 28, 2017 at 4:06 PM, Ron Brash wrote:
> Hello,
>
> Here is a list of things I have tried: The raw zImage (which is compressed
> with XZ), various addresses from indeed load address
Hello,
Here is a list of things I have tried: The raw zImage (which is compressed
with XZ), various addresses from indeed load address 0x2300, entry
at 0x23008000
(and the same), I've tried setting the FTD address since it sets itself
neatly at 0x22f and change, which will probably get
Hello,
Still for some reason - there is an issue with booting from the FIT. With
a version of Uboot without the FIT related CONFIGs enabled; everything
works.
Here is me taking my zImage and converting it to a u-image ( I am not sure
on the addresses)
mkimage -A arm -O linux -C none -T kernel
Looks like far more progress:
#> setenv my_bootcount 0; bootm 0xD0084000
Initial value for argc=3
Final value for argc=3
## Current stack ends at 0x23f11db8 * kernel: cmdline image address =
0xd0084000
Reading image header from dataflash address d0084000 to RAM address
2200
FIT/FDT
Okay - it seems, after working my way through a bunch of the documentation
and examples in /doc/uImage.FIT - I noticed a discrepancy
/dts-v1/;
/{
description = "Configuration to load a Basic Kernel";
#address-cells = <1>;
images {
linux_kernel@1 {
description = "Linux zImage";
data =
I've never seen the kernel load address (the start address for copying
the kernel image into RAM) being the same as the entrypoint address
(where U-Boot jumps to begin executing the kernel). I'd expect the
load address to be 0x2300.
It looks like you are converting the zImage into a U-Boot
You set the load address for the linux image to the same location as the
FIT. U-Boot verified the hashes on the FIT and then tried to copy the
kernel over top the FIT. I assume you put the FIT in flash. Pick a
location in RAM for the kernel's load address.
On Mon, Feb 27, 2017 at 1:49 PM, Ron
The projects I'm working on are based on Yocto so I've been using the
u-boot signing support that is built in there. I believe the magic you are
looking for is in
http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/classes/uboot-sign.bbclass.
Specifically, when you run 'mkimage -F -k -K -r
Hi Mr. Altherr,
I don't have time today to re-clarify everything mentioned in this stream,
but I will begin to reformat my initial inquiries given all of the provided
information and provide them again.
>From my last point:
Anybody have the spare cycles to organise a
Hello all (and thanks Mr. Altherr for this insight),
Excellent feedback and I agree that all of this needs to find a home either
on the global docs on the website and/or the text-only documentation.
Regardless, this leads me to a few questions.
NOTE: the use of a uboot control DTS, control DTB
On Wed, 22 Feb 2017 10:51:22 -0800
Rick Altherr wrote:
> On Tue, Feb 21, 2017 at 10:08 AM, Ron Brash
> wrote:
>
> > Hello all,
> >
> > I am adding verified kernel support on a board we are using and I am
> > struggling to fully understand all of the
On Tue, 21 Feb 2017 13:08:19 -0500
Ron Brash wrote:
> Hello all,
>
> I am adding verified kernel support on a board we are using and I am
> struggling to fully understand all of the concepts and steps required
> to pull everything together (on ARM, using ZImages and booting
Hello all,
I am adding verified kernel support on a board we are using and I am
struggling to fully understand all of the concepts and steps required to
pull everything together (on ARM, using ZImages and booting with a working
DTB on 4.4.3x). I also looked at the test script inside of examples,
16 matches
Mail list logo