´╗┐The RAM config in current u-boot is taken from the devicetree. Modify the "memory" node.

You should make a "reserved" RAM region instead of reducing the size.

On 01-12-16 08:39, Arno Steffens wrote:
I switched from an older yocto u-boot (2015.01) to recent one (2016.01). Now I 
can't boot anymore:

Zynq> boot
QSPI: Kernel/Devicetree - NFS: rootfs
SF: Detected S25FL128S_64K with page size 256 Bytes, erase size 64 KiB, total 
16 MiB
device 0 offset 0x4b0000, size 0x10000
SF: 65536 bytes @ 0x4b0000 Read: OK
device 0 offset 0x4c0000, size 0x380000
SF: 3670016 bytes @ 0x4c0000 Read: OK
## Booting kernel from Legacy Image at 02080000 ...
   Image Name:   Linux-4.4.0-xilinx
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3513736 Bytes = 3.4 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 02000000
   Booting using the fdt blob at 0x2000000
   Loading Kernel Image ... OK
ERROR: Failed to allocate 0x82a5 bytes below 0x0.
device tree - allocation error
FDT creation failed! hanging...### ERROR ### Please RESET the board ###

My guess for reason of that is following, but I can't solve it.

My board (based on MicroZed) has 512MB Ram, but 16MB are used for FPGA.

I managed that before with

-#define CONFIG_SYS_SDRAM_SIZE          (1024 * 1024 * 1024)
+#define CONFIG_SYS_SDRAM_SIZE          (496 * 1024 * 1024)

In newer Uboot I can't find this definition not in that way. Nevertheless I 
added this line.
(If not, that my last message is "Starting kernel ...")

Although digging around, I couldn't find how nowadays this is handled. This 
seems memory size is not board-specific anymore. How it is handled?


Kind regards,

Mike Looijmans
System Expert

TOPIC Products
Materiaalweg 4, NL-5681 RJ Best
Postbus 440, NL-5680 AK Best
Telefoon: +31 (0) 499 33 69 79
E-mail: mike.looijm...@topicproducts.com
Website: www.topicproducts.com

Please consider the environment before printing this e-mail

meta-xilinx mailing list

Reply via email to