Linux/AM5728: Issues with U-Boot 2016.05 on SR1.1 device

The software team have been notified. They will respond here.

Hi Wilson,

What is the console output? Do you get any debug log, if yes, please share it?

Best Regards,
Yordan

Yordan,

Below is the console output:

No matching DT out of these options:
am572x-evm
<2, 0, 1024>
Failed to mount ext2 filesystem...
spl_load_image_ext_os: ext4fs mount err - 0
<2, 0, 1024>
Failed to mount ext2 filesystem...
spl_load_image_ext: ext4fs mount err - 0
Jumping to U-Boot
loaded - jumping to U-Boot...image entry point: 0x80800000

We have EVMs with AM5728 Silicon 1.1 and Silicon 2.0 versions. The bootloader images load fine in silicon version 2.0.

Hi,

I refer to SDK 3.02 (kernel 4.4.32, u-boot 2016.05)

Try changing
CONFIG_DEFAULT_DEVICE_TREE="am57xx-beagle-x15"
in your am57xx_evm_defconfig file, to match the dts file you use. The defconfig is located in the configs/ folder.

Best Regards,
Yordan

Yordan,

We have built u-boot 2016.05 using am57xx_defconfig which contains CONFIG_DEFAULT_DEVICE_TREE="am57xx-beagle-x15". Installing the MLO and u-boot.img files on a silicon revision 2.0 am572x EVM the system boots up normally. However, installing the same files on a silicon revision 1.1 am572x EVM we see the "No matching DT out of these options" error. Please see console outputs below:

DRA752-GP ES2.0
Trying to boot from MMC2_2
reading args
spl_load_image_fat_os: error reading image args, err - -1
reading u-boot.img
reading u-boot.img
reading u-boot.img
reading u-boot.img


DRA752-GP ES1.1
Trying to boot from MMC2_2
reading args
spl_load_image_fat_os: error reading image args, err - -1
reading u-boot.img
reading u-boot.img
reading u-boot.img
No matching DT out of these options:
am57xx-beagle-x15
am572x-idk
am571x-idk

Would the DRA752-GP ES1.1 require different build options?

Thank you.

Building am57xx_evm_nodt_defconfig generates bootloader files that work on both silicon revisions.

We have AM57xx devices and using am57xx_evm_nodt_defconfig allows us to execute u-boot (2016.05) and Linux (4.4.32).

Does SR1.1 support CONFIG_ARMV7_LPAE? Our breadboards have 4GB (2GB -> EMIF1 + 2GB -> EMIF2) installed but only 2GB is recognized in both u-boot and Linux.

We have taken am57xx_evm_nodt_defconfig, added CONFIG_ARMV7_LPAE=y, and updated the dmm_lisa_map_regs as follows:
.dmm_lisa_map_0 = 0x00000000,
.dmm_lisa_map_1 = 0x00000000,
.dmm_lisa_map_2 = 0x80740300,
.dmm_lisa_map_3 = 0xFF020100,
.is_ma_present = 0x1

Would anything else be required to have the additional 2GB recognized on an SR1.1 device?

Hi,

Would anything else be required to have the additional 2GB recognized on an SR1.1 device?

Correct lisa map settings should be enough.

The settings you share correspond to:
lisa_map_2 = 0x80740300 =>
[9:8]SDRC_MAP = 0x3: Mapped on EMIF1 and EMIF2 (interleaved)
To enable interleaving, SDRC_MAP must be 0x3 and
SDRC_INTL must be a nonzero value .
[18:19]SDRC_INTL = 0x1 => 128 byte interleaving
[20:22]SYS_SIZE = 0x7 => 2-GiB section


lisa_map_3 = 0xFF020100
[9:8]SDRC_MAP = 0x1: Mapped on EMIF1 only (not interleaved)
[16:17]SDRC_ADDRSPC = 0x2: SDRAM controller address space for view mapping i
[19:18]SDRC_INTL = 0x0: No interleaving
[22:20]SYS_SIZE = 0x0: 16-MiB section

LISA_MAP_2 seems to match your use case. Verify the settings of LISA_MAP_3.

Best Regards,
Yordan