Nanopi R2S only shows 512M memory

[ybh1998]

Armbianmonitor:

http://ix.io/2l8d

Hi,

I have one FriendlyARM NanoPi R2S. It should have 1G DDR4 memory. Everything works fine with latest Armbian 20.02.08 except only 512M memory shows up. Both Buster and Bionic have the same issue:

Armbian_20.02.8_Nanopi-r2s_buster_current_5.4.28

Armbian_20.02.8_Nanopi-r2s_bionic_current_5.4.28

 

I tried FriendlyARM official FriendlyCore. I can see all 1G memory, /proc/meminfo on FriendlyCore is as follows:

MemTotal:         971052 kB
MemFree:          842880 kB
MemAvailable:     844352 kB
Buffers:            8012 kB
Cached:            48272 kB
SwapCached:            0 kB
Active:            45904 kB
Inactive:          31580 kB
Active(anon):      21408 kB
Inactive(anon):     4768 kB
Active(file):      24496 kB
Inactive(file):    26812 kB
Unevictable:           4 kB
Mlocked:               0 kB
SwapTotal:             0 kB
SwapFree:              0 kB
Dirty:              1392 kB
Writeback:             0 kB
AnonPages:         21116 kB
Mapped:            24300 kB
Shmem:              4976 kB
KReclaimable:      19212 kB
Slab:              36376 kB
SReclaimable:      19212 kB
SUnreclaim:        17164 kB
KernelStack:        1824 kB
PageTables:          780 kB
NFS_Unstable:          0 kB
Bounce:                0 kB
WritebackTmp:          0 kB
CommitLimit:      485524 kB
Committed_AS:     114152 kB
VmallocTotal:   262930368 kB
VmallocUsed:        2664 kB
VmallocChunk:          0 kB
Percpu:              656 kB
AnonHugePages:         0 kB
ShmemHugePages:        0 kB
ShmemPmdMapped:        0 kB
FileHugePages:         0 kB
FilePmdMapped:         0 kB
CmaTotal:          16384 kB
CmaFree:           15344 kB
HugePages_Total:       0
HugePages_Free:        0
HugePages_Rsvd:        0
HugePages_Surp:        0
Hugepagesize:       2048 kB
Hugetlb:               0 kB

 

I don't have UART to USB at home, so i get these information through ssh. How can i use the other half of the memory?

[piter75]

5 hours ago, ybh1998 said:

only 512M memory shows up

This is a known issue with currently available builds.

It is fixed with moving it to mainline u-boot. Prebuilt images will be available soon.

[Igor]

For testing - to see if things are better:

 

https://dl.armbian.com/nanopi-r2s/Focal_current_minimal_nightly

https://dl.armbian.com/nanopi-r2s/Focal_dev_minimal_nightly

[ybh1998]

19 hours ago, Igor said:

For testing - to see if things are better:

 

https://dl.armbian.com/nanopi-r2s/Focal_current_minimal_nightly

https://dl.armbian.com/nanopi-r2s/Focal_dev_minimal_nightly

The first one Armbian_20.02.14.129_Nanopi-r2s_focal_current_5.4.39_minimal works fine. I can see all 1G RAM now.

The second one Armbian_20.02.14.129_Nanopi-r2s_focal_dev_5.6.11_minimal doesn't startup. LEDs onboard don't blink and no devices on DHCP. I'm ordering a USL-TTL adapter to see if there is anything on serial.

[Igor]

3 hours ago, ybh1998 said:

The second one Armbian_20.02.14.129_Nanopi-r2s_focal_dev_5.6.11_minimal doesn't startup.

This is the reason:
 

Spoiler

U-Boot 2020.04-armbian (May 07 2020 - 22:13:44 +0200)

Model: FriendlyElec NanoPi R2S
DRAM:  1022 MiB
PMIC:  RK8050 (on=0x40, off=0x00)
MMC:   rksdmmc@ff500000: 1
Loading Environment from MMC... *** Warning - bad CRC, using default environment

In:    serial@ff130000
Out:   serial@ff130000
Err:   serial@ff130000
Model: FriendlyElec NanoPi R2S
Net:   eth0: ethernet@ff540000
Hit any key to stop autoboot:  0 
switch to partitions #0, OK
mmc1 is current device
Scanning mmc 1:1...
Found U-Boot script /boot/boot.scr
2940 bytes read in 5 ms (574.2 KiB/s)
## Executing script at 00500000
Boot script loaded from mmc 1
161 bytes read in 4 ms (39.1 KiB/s)
10527744 bytes read in 461 ms (21.8 MiB/s)
20505088 bytes read in 893 ms (21.9 MiB/s)
libfdt fdt_check_header(): FDT_ERR_BADMAGIC
No FDT memory address configured. Please configure
the FDT address via "fdt addr <address>" command.
Aborting!
2698 bytes read in 8 ms (329.1 KiB/s)
Applying kernel provided DT fixup script (rockchip-fixup.scr)
## Executing script at 39000000
## Loading init Ramdisk from Legacy Image at 06000000 ...
   Image Name:   uInitrd
   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
   Data Size:    10527680 Bytes = 10 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
ERROR: Did not find a cmdline Flattened Device Tree
   Loading Ramdisk to 3d51c000, end 3df263c0 ... OK
FDT and ATAGS support not compiled in - hanging
### ERROR ### Please RESET the board ###

 

 

 

[piter75]

5 hours ago, ybh1998 said:

The second one Armbian_20.02.14.129_Nanopi-r2s_focal_dev_5.6.11_minimal doesn't startup.

Until yesterday evening NanoPi R2S was only supported in current. That's why dev build is not working.

 

Next builds (@Igor will this happen automatically if I added dev target to targets.conf) will work properly.

[Igor]

5 hours ago, piter75 said:

Next builds (@Igor will this happen automatically if I added dev target to targets.conf) will work properly.

If some target does not build, nightly builds stops and waits for manual intervention ... I restarted it this morning and its not finished yet. In last https://dl.armbian.com/nanopi-r2s/nightly/ those changes are not included yet.

 

In a few hours.