Hi,
today I just received a brandnew PicoZed Z7015 Board and I just wanted to try to start it with the Quick Start Guide provided in the PicoZed documentaries, but I got some problems with the board.
I followed exactly the instructions given in the Quick Start Guide.
When I started the board, the blue LED (fpga done) didn't lit. (Do I have to load the fpga for the Quick Start Guide myself? I don't know how to do yet, since I'm quite a beginner in working with boards)
I was able to communicate with the Zynq via USB-UART, but when I tried to u-boot from the QSPI, I got an error message, that the command sf cannot be found:
-Boot 2014.01-dirty (Sep 29 2014 - 09:07:05)
I2C: ready
Memory: ECC disabled
DRAM: 1 GiB
MMC: zynq_sdhci: 0, zynq_sdhci: 1
Using default environment
In: serial
Out: serial
Err: serial
Net: Gem.e000b000
Hit any key to stop autoboot: 0
Copying Linux from QSPI flash to RAM...
Unknown command 'sf' - try 'help'
zynq-uboot>
Edit 08.06.2015: 16:30
Now I tried to reload the QSPI flash with the factory image provided in the support section on the homepage the way it is described in the "Restoring PicoZed QSPI to the Factory Image" v1.0 Guide. The booting works, the fpga done LED is on and I get the expected linux OS, but when I afterwards try to boot from the flash I get the same error as before and the blue LED doesn't glow. Instead the two red LEDs D17 and D18 are on.
This is the relevant output on the terminal during the erasing, reloading and factory tests:
Starting rcS...
++ Mounting filesystem
++ Setting up mdev
++ Starting telnet daemon
++ Starting http daemon
++ Starting ftp daemon
++ Starting ssh daemon
++ Running user script init.sh from SD Card
******************************************************************
*** ***
*** Avnet PicoZed 7015/7030 Factory Test Build V1.0 ***
*** ***
******************************************************************
++ Installing OOB Reference Design files to QSPI flash...
+++ Installing FSBL and U-Boot Bootloaders...
Erasing block: 6/6 (100%)
Writing kb: 376/379 (99%)
Verifying kb: 0/379 (0%) flashcp: verification mismatch at 0x0
++ Starting peripheral tests...
+++ Running FMC Loopback Test...
****many fails due to no Loopback****
+++ Running USB Device Read Test...
******************************************************************
No USB Mass Storage Block Device Enumerated!
Connect the test USB Thumb drive to PicoZed Carrier Card
J5 connector and re-run factory tests
******************************************************************
+++ Running Ethernet Ping Test...
PING 192.168.1.100 (192.168.1.100): 56 data bytes
--- 192.168.1.100 ping statistics ---
10 packets transmitted, 0 packets received, 100% packet loss
******************************************************************
*** ***
*** PicoZed 7015/7030 Factory Test V1.0 Complete ***
*** ***
*** Flash Programming: PASS ***
*** FMC LPC Loopback: FAIL ***
*** Ethernet Ping: FAIL ***
*** USB Device Read: FAIL ***
*** ***
******************************************************************
rcS Complete
Ethernet and USB surely fail, since I'm not using those so far. The loopback is allowed to fail (according to the guide), but I am really wondering why my erasing and reloading process output differs from the one which is referenced in the guide (see Figure 2). E.G. in my case it installs only the FSBL and U-Boot Bootloaders before it starts the tests, in the guide there is also the Linux-Kernel, the Kernel Device Tree, the RAM Disk Image and the PL Binary Bitstream getting installed.
I appreciate any ideas or hints.
Regards,
Daniel
