Created attachment 1412 [details] putty_stop_kernel-3-7 We followed the manuals of RocketBoards.org to compile and bake a linux kernel, root filesystem etc. But if we create our own SD-card image of these parts booting on the Arrow SoC kit fails. In the next step we used a working SD-card image from terasiC and updated it only partially. Everything works fine with our self-compiled root filesystem. All the other parts, especially the kernel, don’t work with the SD-card. For our self-compiled kernel (dylan-altera from [1]) we get the following error message when booting from SD-card after the attempt to read the uImage: “Wrong Image Format for bootm command ERROR: can't get kernel image!” We followed the instructions given in [3]. For our self-compiled kernel (kernel 3.7 from [2]) we see the following when booting from SD-card after the attempt to read the uImage (start procedure stops at this step): - for the output see the attached png file 'putty_stop_kernel-3-7' - We don’t see our mistake because we followed the instructions of RocketBoards exactly and all the other parts on the SD-card image as uboot work fine. [1] http://git.rocketboards.org/?p=poky-socfpga.git;a=summary [2] http://www.rocketboards.org/foswiki/Documentation/AlteraSoCDevelopmentBoardYoctoGettingStarted [3] http://www.rocketboards.org/foswiki/Documentation/GitGettingSTarted
We have bitbake version 1.18.0, which was not selectable.
Have you been in contact with Rocketboards to discuss this issue? This appears to be an issue with their kernel. The Yocto Project supports the core qemu and 4 reference hardware devices. Please check with Rocketboards.org. Also not quite sure what the bitbake reference and selectivity is about.
Since this is an issue with the ARROW SOC BSP, I am going to close this, if the issue is in oe-core, please file a new bug.