Just a curiosity on Petalinux 2014.2

[indar]

Hi,

I have done a simple experiment using the reference design 720_bsp_full_snapshot and I just removed the axi_iic and axi_gpio modules (together with the corresponding AXI interconnect and the system reset) and then build the petalinux based on the exported hardware (plus its bitstream). Everything works just fine, except I don't see any sign of the u-boot prompt during booting until the petalinux was completely loaded. Here is the output of my screen:

******************************************************************
*           TE0720 Unique MAC Addr: 00 04 A3 AC 24 E8            *
*----------------------------------------------------------------*
console [ttyPS0] enabled
bootconsole [earlycon0] disabled
e0001000.serial: ttyPS1 at MMIO 0xe0001000 (irq = 82, base_baud = 3124999) is a xuartps
xdevcfg f8007000.ps7-dev-cfg: ioremap 0xf8007000 to f0068000
brd: module loaded
loop: module loaded
cdns-spi e0006000.ps7-spi: pclk clock not found.
cdns-spi: probe of e0006000.ps7-spi failed with error -2
cdns-spi e0007000.ps7-spi: pclk clock not found.
cdns-spi: probe of e0007000.ps7-spi failed with error -2
m25p80 spi32766.0: found w25q256, expected n25q128
m25p80 spi32766.0: failed to read ear reg
m25p80 spi32766.0: w25q256 (32768 Kbytes)
4 ofpart partitions found on MTD device spi32766.0
Creating 4 MTD partitions on "spi32766.0":
0x000000000000-0x000000500000 : "boot"
0x000000500000-0x000000520000 : "bootenv"
0x000000520000-0x000000fa0000 : "kernel"
0x000000fa0000-0x000002000000 : "spare"
e1000e: Intel(R) PRO/1000 Network Driver - 2.3.2-k
e1000e: Copyright(c) 1999 - 2013 Intel Corporation.
xemacps e000b000.ps7-ethernet: pdev->id -1, baseaddr 0xe000b000, irq 54
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-pci: EHCI PCI platform driver
zynq-dr e0002000.ps7-usb: Unable to init USB phy, missing?
usbcore: registered new interface driver usb-storage
mousedev: PS/2 mouse device common for all mice
i2c /dev entries driver
cdns-i2c e0004000.ps7-i2c: 400 kHz mmio e0004000 irq 57
cdns-i2c e0005000.ps7-i2c: 400 kHz mmio e0005000 irq 80
zynq-edac f8006000.ps7-ddrc: ecc not enabled
cpufreq_cpu0: failed to find cpu0 node
cpufreq-cpu0: probe of cpufreq-cpu0.0 failed with error -2
Xilinx Zynq CpuIdle Driver started
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pltfm: SDHCI platform and OF driver helper
mmc0: no vqmmc regulator found
mmc0: no vmmc regulator found
mmc0: SDHCI controller on e0100000.ps7-sdio [e0100000.ps7-sdio] using ADMA
mmc1: no vqmmc regulator found
mmc1: no vmmc regulator found
mmc1: SDHCI controller on e0101000.ps7-sdio [e0101000.ps7-sdio] using ADMA
mmc0: new high speed SDHC card at address 59b4
mmcblk0: mmc0:59b4 USD   14.7 GiB
mmcblk0: p1
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
TCP: cubic registered
NET: Registered protocol family 17
Registering SWP/SWPB emulation handler
regulator-dummy: disabling
/opt/petalinux/petalinux-v2014.2-final/components/linux-kernel/xlnx-3.14/drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
mmc1: BKOPS_EN bit is not set
Freeing unused kernel memory: 3660K (c067d000 - c0a10000)
INIT: version 2.88 booting
Starting Bootlog daemon: bootlogd.
Creating /dev/flash/* device nodes
random: dd urandom read with 9 bits of entropy available
starting Busybox inet Daemon: inetd... done.
Starting uWeb server:
NET: Registered protocol family 10
update-rc.d: /etc/init.d/run-postinsts exists during rc.d purge (continuing)
Removing any system startup links for run-postinsts ...
  /etc/rcS.d/S99run-postinsts
INIT: Entering runlevel: 5
Configuring network interfaces... xemacps e000b000.ps7-ethernet: eth0: no PHY setup
udhcpc (v1.22.1) started
Sending discover...
Sending select for 10.162.242.99...
mmc1: new high speed MMC card at address 0001
mmcblk1: mmc1:0001 MMC04G 3.52 GiB
mmcblk1boot0: mmc1:0001 MMC04G partition 1 16.0 MiB
mmcblk1boot1: mmc1:0001 MMC04G partition 2 16.0 MiB
mmcblk1rpmb: mmc1:0001 MMC04G partition 3 128 KiB
Lease of 10.162.242.99 obtained, lease time 3600
mmcblk1:
mmcblk1boot1: unknown partition table
mmcblk1boot0: unknown partition table
/etc/udhcpc.d/50default: Adding DNS 10.156.33.53
/etc/udhcpc.d/50default: Adding DNS 129.187.5.1
done.
Stopping Bootlog daemon: bootlogd.

Built with PetaLinux v2014.2 (Yocto 1.6) TE720 /dev/ttyPS0
TE720 login: random: nonblocking pool is initialized

Built with PetaLinux v2014.2 (Yocto 1.6) TE720 /dev/ttyPS0
TE720 login:

Afterwards, I can login on the petalinux and don't see anything strange (except that randon nonblocking pool message). So, why does u-boot disappear? I didn't do anything, just simple/normal build as described on the TE0720 Petalinux BSP Guide. Any hints? Thanks!
Btw, I use Vivado 2014.2 on Ubuntu 14.04 64-bit.

best,
Indar

[Antti Lukats]

uboot did send its console to wrong uart, thats all,

the console settings are a bit scattered it is sure possible to get it back and working, no worry

we have not updated the 2014.2 as we hope the 2014.3 is out maybe next week already.

The first print did come from FSBL, that did read out an SET the MAC address to the ETH0 IP
then missing > wrong uart
then linux

[indar]

Great, thanks for your hint Antti!

best,
Indar

[mengnantiger]

Hi
   could you please post your dts , i meet a similar problem , thank you

[Antti Lukats]

if it missing output from uboot then this is not dts devicetree setting, uboot config is separate

[indar]

And more thing, sometimes I get the following error message:

xusbps-dr e0002000.ps7-usb: Unable to init USB phy, missing?

Hence, I couldn't access USB. But sometimes I didn't get such message and the USB works just fine!
This happens not only with Petalinux 2014.2 but also 2013.4. It's a bit annoying, sometimes it works sometimes it doesn't!
However, if I use the original (pre-installed) linux on the flash, the USB is *always* accessible!  Do you know why it happens in petalinux and how to solve it?

Thanks!
Indar

ps. I don't know if this is related with this one:
https://github.com/Xilinx/linux-xlnx/issues/19

[Antti Lukats]

yes this is on todo list as well, I am guessing the USB PHY reset is not toggled properly at startup, we are onto it.