Hello everyone,
I am trying to make the Hello app run on the zedboard but it gets stuck at "Scanning up to 512 MB RAM, starting at offset 32MB".
I have configured both fiasco and l4re with the correct configuration (I have attached my config files) and cross compiled them from a x86_64 linux machine with "Linaro GCC 4.9-2014.09 4.9.2 20140904".
I searched the mailing lists archives but I can't seem to find a similar problem. I tried changing the uart port I was using, in case it was printing in another port, but nothing changed.
Any ideas/suggestions on what could go be going wrong and/or how can I solve it?
Thank you for your time, Manolis
The output of u-boot:
reading uImage 970816 bytes read in 108 ms (8.6 MiB/s) reading initramfs.cpio.gz 128 bytes read in 17 ms (6.8 KiB/s) reading devicetree.dtb 9331 bytes read in 16 ms (569.3 KiB/s) ## Booting kernel from Legacy Image at 03000000 ... Image Name: L4 Image #2 Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 970752 Bytes = 948 KiB Load Address: 01000000 Entry Point: 01000000 Verifying Checksum ... OK ## Loading init Ramdisk from Legacy Image at 02000000 ... Image Name: Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 64 Bytes = 64 Bytes Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 02a00000 Booting using the fdt blob at 0x2a00000 Loading Kernel Image ... OK Loading Ramdisk to 0f31d000, end 0f31d040 ... OK Loading Device T^H.��.\Build: #2 Fri Dec 11 14:35:25 EET 2015, 4.9.2 20140904 (prerelease) Scanning up to 512 MB RAM, starting at offset 32MB
Hi,
On Fri Dec 11, 2015 at 15:02:16 +0200, Manolis Ragkousis wrote:
Hello everyone,
I am trying to make the Hello app run on the zedboard but it gets stuck at "Scanning up to 512 MB RAM, starting at offset 32MB".
I have configured both fiasco and l4re with the correct configuration (I have attached my config files) and cross compiled them from a x86_64 linux machine with "Linaro GCC 4.9-2014.09 4.9.2 20140904".
I searched the mailing lists archives but I can't seem to find a similar problem. I tried changing the uart port I was using, in case it was printing in another port, but nothing changed.
Any ideas/suggestions on what could go be going wrong and/or how can I solve it?
Loading Device T^H.��.\Build: #2 Fri Dec 11 14:35:25 EET 2015, 4.9.2 20140904 (prerelease) Scanning up to 512 MB RAM, starting at offset 32MB
This looks like some UART issue. I suppose Linux is running ok? What does it say on its UART/tty init? And does this happen everytime in the same way or does the pattern change?
Adam
l4-hackers@os.inf.tu-dresden.de