Hello,
Sure, I started with using it with correct way via DTB in Linux. But when I rebooted the board, nothing has been written into this section. So I was thinking someone has to "scramble" the memory. So I moved one level down into U-boot. There I also tried to define the "reserved-memory", but it didn't help. As I said, I tried multiple memory addresses (55110000, 944400000, ...) based on:
3d800000-3dbfffff : 3d800000.ddr-pmu ddr-pmu@3d800000
40000000-54ffffff : System RAM
48210000-4975ffff : Kernel code
49760000-49adffff : reserved
49ae0000-49d1ffff : Kernel data
4ffed000-4fffcfff : reserved
55000000-5510ffff : reserved
55110000-553fffff : System RAM
55400000-554fffff : reserved
55500000-7fffffff : System RAM
80000000-80ffffff : reserved
81000000-923fffff : System RAM
92400000-943fffff : reserved
94400000-ffffffff : System RAM
c0000000-ffffffff : reserved
100000000-10fffffff : reserved
100000000-10fffffff : gcContMem
110000000-13fffffff : System RAM
13b0ec000-13f7fffff : reserved
13f827000-13f827fff : reserved
13f82a000-13f82cfff : reserved
13f82d000-13f841fff : reserved
13f842000-13f88ffff : reserved
13f890000-13fffffff : reserved
reserved-memory {
#address-cells = <2>;
#size-cells = <2>;
ranges;
ramoops: ramoops@94400000 {
compatible = "ramoops";
reg = <0 0x94400000 0 0x00100000>; // 1MB at 0x94400000
record-size = <0x10000>; // 64kB per record
console-size = <0x10000>; // 64kB for console
ftrace-size = <0x40000>; // 256kB for ftrace output
pmsg-size = <0x10000>; // 64kB for user messages
};
};
I would say the problem has to be somewhere deeper, that the memory is reset, maybe PMIC? If yes, where/how to configure it to not do a DRAM power cycle.
BR,
Andy