06-11-2018 12:12 AM
Hello
I am trying to use the MPSOC OCM to pass parameters from the FSBL to UBoot (specifically the board's custom Ethernet MAC address). However, I cannot read OCM from Uboot using the 'md' command.
I get the following output when I run "md 0xfffc0000":
Xilinx Zynq MP First Stage Boot Loader
Release 2017.4 Jun 11 2018 - 09:06:01
NOTICE: ATF running on XCZU9EG/silicon v3/RTL5.1 at 0xfffea000, with PMU firmware
NOTICE: BL31: Secure code at 0x0
NOTICE: BL31: Non secure code at 0x8000000
NOTICE: BL31: v1.3(release):47af34b
NOTICE: BL31: Built : 12:29:09, Feb 22 2018
U-Boot 2017.01 (Jun 11 2018 - 08:50:23 +0200) Xilinx ZynqMP ZCU102 revB
I2C: ready
DRAM: 4 GiB
ERROR: usb dr_mode not found
at /home/mruser/petalinux/frm125001u1r1/build/tmp/work/plnx_aarch64-xilinx-linux/u-boot-xlnx/v2017.01-xilinx-v2017.4+gitAUTOINC+5fa7d2ed06-r0/git/drivers/usb/common/common.c:32/usb_get_dr_mode()
EL Level: EL2
Chip ID: xczu9eg
MMC: sdhci@ff170000: 0 (SD)
zynqmp_qspi_ofdata_to_platdata: CLK 124999999
SF: Detected n25q512a with page size 512 Bytes, erase size 128 KiB, total 128 MiB
*** Warning - bad CRC, using default environment
In: serial
Out: serial
Err: serial
Bootmode: LVL_SHFT_SD_MODE1
Net: ZYNQ GEM: ff0e0000, phyaddr c, interface rgmii-id
eth0: ethernet@ff0e0000
U-BOOT for frm125001u1r1
00:0a:35:00:22:01
ethernet@ff0e0000 Waiting for PHY auto negotiation to complete....... done
BOOTP broadcast 1
BOOTP broadcast 2
*** Unhandled DHCP Option in OFFER/ACK: 252
*** Unhandled DHCP Option in OFFER/ACK: 252
DHCP client bound to address 192.168.2.139 (262 ms)
Hit any key to stop autoboot: 0
ZynqMP> md 0xfffc0000
fffc0000:"Synchronous Abort" handler, esr 0x96000006
ELR: 7ff5c288
LR: 7ff5c248
x0 : 0000000000000009 x1 : 0000000000000000
x2 : 000000000000080a x3 : 00000000fffc0000
x4 : 0000000000000000 x5 : 000000007ff732b4
x6 : 0000000000000004 x7 : 000000000000000f
x8 : 000000007deaf900 x9 : 0000000000000000
x10: 000000007deaf169 x11: 0000000000000021
x12: 0000000000000008 x13: 00000000ffffffff
x14: 000000007deafcbc x15: 000000007ff7ca40
x16: 0000000000000000 x17: 0000000000000000
x18: 000000007deafde8 x19: 0000000000000040
x20: 00000000fffc0000 x21: 00000000fffc0000
x22: 000000007ff72cbf x23: 0000000000000008
x24: 0000000000000004 x25: 0000000000000004
x26: 0000000000000004 x27: 000000007deafac8
x28: 0000000000000000 x29: 000000007deafa40
Resetting CPU ...
resetting ...
Please provide some advice as to why I can't access the OCM from UBoot.
I am doing development on the ZCU102 development board.
I am using Petalinux 2017.4.
I am building with Vivado 2017.4.
Thank you.
06-13-2018 03:02 AM
Hi
Could you please try adding this to your uboot config file and see if you are able to access OCM?
CONFIG_DEFINE_TCM_OCM_MMAP
Best Regards
Shabbir
06-13-2018 03:02 AM
Hi
Could you please try adding this to your uboot config file and see if you are able to access OCM?
CONFIG_DEFINE_TCM_OCM_MMAP
Best Regards
Shabbir