Hi Andreas, I tried a different address for ramdisk i.e. 0x24E00000 and it executed successfully. Please tell me how can I check what is the issue with address 0x23000000, why u-boot is giving error for ramdisk stored at 23000000 and not for address 24E00000?
Please suggest!! Thanks and Regards Gaurav Pathak Contact No: 9028531335 On 22 May 2015 15:42, "Gaurav Pathak" <[email protected]> wrote: > Hi Andreas, > > Thank you for your quick reply. I am using sam-ba utility for transferring > images to RAM... > > >> What type of image(s)? > I am using kernel image as uImage at address 22000000, initrd.cpio at > 23000000 and dtb.bin at address 21000000 > and u-boot.bin at address 26F00000. > > >> What was the command failing? > When I try to run iminfo 23000000 it ends up in "Verifying checksum... Bad > data CRC." But the same command successfully executes for kernel image > (iminfo 22000000). > Due to this reason when I run bootm 22000000 23000000 21000000, it fails > at loading rootfs because of Checksum Error. > > > >> Which addresses used and how many RAM is available? > So, the addresses used are 22000000 for kernel image, 23000000 for rootfs > and 21000000 for device tree blob > and U-boot is at 26F00000 > > The RAM is 512MiB. > > >> Any constraints regarding reserved memory? > There is no any reserved memory in RAM, whole RAM is available for > execution. > > > I don't know whether u-boot is relocating itself during execution or not!! > How should I verify that relocation of u-boot is enabled or disabled? > > --------------------------------------------- > Thanks & Regards > Gaurav Pathak > Contact No: 9028531335 > > > > > On Fri, May 22, 2015 at 2:07 PM, Andreas Bießmann < > [email protected]> wrote: > > > > Dear Gaurav Pathak, > > > > On 05/21/2015 02:01 PM, Andreas Bießmann wrote: > > > Dear Gaurav Pathak, > > > > > I'll verify that sama5d3xek is loading ramdisk larger than 4MiB with > > > mainline U-Boot and post the results. > > > > The latest mainline does support loading 8MiB ramdisk on a sama5d3xek > > (sama5d34): > > > > ---8<--- > > U-Boot> version > > > > U-Boot 2015.07-rc1-00274-g3238639 (May 22 2015 - 00:15:46) > > arm-unknown-linux-uclibcgnueabi-gcc (crosstool-NG 1.20.0) 4.7.4 > > GNU ld (crosstool-NG 1.20.0) 2.22 > > U-Boot> bootz 0x22000000 0x23000000 0x21000000 > > Kernel image @ 0x22000000 [ 0x000000 - 0x3315c8 ] > > ## Loading init Ramdisk from Legacy Image at 23000000 ... > > Image Name: Application Ramdisk > > Image Type: ARM Linux RAMDisk Image (gzip compressed) > > Data Size: 8047596 Bytes = 7.7 MiB > > Load Address: 00000000 > > Entry Point: 00000000 > > Verifying Checksum ... OK > > ## Flattened Device Tree blob at 21000000 > > Booting using the fdt blob at 0x21000000 > > Loading Ramdisk to 3f2db000, end 3fa87bec ... OK > > Loading Device Tree to 3f2d0000, end 3f2da78a ... OK > > > > Starting kernel ... > > > > Uncompressing Linux... done, booting the kernel. > > Booting Linux on physical CPU 0x0 > > Linux version 3.18.14 (andreas@andreas-pc) (gcc version 4.6.2 > > (OSELAS.Toolchain-2011.11.0) ) #2 Thu May 21 23:51:50 CEST 2015 > > ... > > --->8--- > > > > Andreas > > _______________________________________________ U-Boot mailing list [email protected] http://lists.denx.de/mailman/listinfo/u-boot
