Re: [U-Boot] Can't boot my FIT image: 'Could not find configuration node'

7 Aug 2018


      Hi Johann,
I apologize, that typo is actually just in the email. My actual file has
"kernel-0" in both locations. It seems my fit image is formed correctly
based on the header information:
...$ mkimage -F sel4.itb
FIT description: SeL4
Created:         Tue Aug  7 10:56:42 2018
 Image 0 (kernel-0)
  Description:  SeL4 image
  Created:      Tue Aug  7 10:56:42 2018
  Type:         Kernel Image
  Compression:  uncompressed
  Data Size:    1033080 Bytes = 1008.87 kB = 0.99 MB
  Architecture: ARM
  OS:           QNX
  Load Address: 0x48000000
  Entry Point:  0x48000000
 Default Configuration: 'config-0'
 Configuration 0 (config-0)
  Description:  default config
  Kernel:       kernel-0
Likewise, I get the same information using the `iminfo` command within
u-boot.
Sorry again for the typo,
Grant
On Tue, Aug 7, 2018 at 12:16 AM Johann Neuhauser <
jneuhauser@dh-electronics.de> wrote:
...
Dear Grant,
I see there is a typo in your kernel node name.
In the image section you wrote kerne-0 and in the config section you wrote
kernel = "kernel-0";
Probably this is the issue that no config and kernel  image is found.
Regards,
Johann Neuhauser
...
-----Ursprüngliche Nachricht-----
Von: U-Boot [mailto:u-boot-bounces@lists.denx.de] Im Auftrag von Grant
Jurgensen
Gesendet: Montag, 6. August 2018 19:50
An: u-boot@lists.denx.de
Betreff: [U-Boot] Can't boot my FIT image: 'Could not find configuration
node'
Hi,
I'm using U-boot to boot an ELF image. I am easily able to load the
image into
...
memory and boot it with the `bootelf` command. However, I'd like to
create
...
a FIT image in order to make use of the convenient hashing and secure
boot
...
features, but I'm having trouble getting my image to boot.
Here is my current `.its` file (currently as simple as possible until I
get it to
...
boot):
/dts-v1/;
/ {
    description = "SeL4";
    #address-cells = <1>;
images {
    kerne-0 {
        description = "SeL4 image";
        data = /incbin/("./test_app-image-arm-exynos5");
        type = "kernel";
        arch = "arm";
        os = "qnx";
        compression = "none";
        load = <0x48000000>;
        entry = <0x48000000>;
    };
};

configurations {
    default = "config-0";
    config-0 {
         description = "default config";
         kernel = "kernel-0";
    };
};

};
By the way, my ELF image isn't actually a qnx kernel. It is a sel4
kernel,
...
however "sel4" is not an option. (I can make a uImage with `mkimage -A
arm
...
-a 0x48000000 -e 0x48000000 -C none -T kernel -O qnx -d
test_app-image-exynos5 image` and can actually boot the resulting image
here with `bootm` no problem, so I believe using the qnx OS setting
shouldn't be a problem.)
I am then able to create the FIT image with `mkimage -f sel4.its
sel4.itb`.
...
I copy this image to my SD card, successfully load the fit image into
memory
...
(with `fatload`), but then `bootm` fails with the following message:
## Loading kernel from FIT Image at 50000000 ...
Could not find configuration node
ERROR: can't get kernel image!
I can't make sense of this error. `iminfo` recognizes my default
configuration,
...
yet `bootm` can't find the configuration node?
Thanks,
Grant
_______________________________________________
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot

Re: [U-Boot] Can't boot my FIT image: 'Could not find configuration node'

Grant Jurgensen