[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4688: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3823)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4690: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3823)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4691: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3823)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4692: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3823)
Parallella Community • View topic - Edited: Cannot boot Zedboard from the 13020600 image

Edited: Cannot boot Zedboard from the 13020600 image

Forum about Parallella boot process, linux kernel, distros, SD-cards, etc.

Edited: Cannot boot Zedboard from the 13020600 image

Postby mipt98 » Fri Jul 12, 2013 10:39 pm

Edited:

Dear All, please help
Cannot boot Zedboard with 64-core Epiphany using zedboard_parallella_64_13020600.img It continues printing something like

detect: f0 1 0 0
detect: f0 1 0 0
* * *
or

detect: 90 2 0 3
detect: 90 2 0 3
* * *

if Epiphany board is not connected and doesn't go any further. The boot messages are below. I have no idea what causes the trouble, and will highly appreciate any input. One thing is that it doesn't seem to be an SD issue. I wrote the Zedboard image that came with the board to the same 32gb SD and the board booted without problems.

-Ivan

U-Boot 2012.04.01-00304-g7639205-dirty (Jan 14 2013 - 18:20:30)

DRAM: 512 MiB
WARNING: Caches not enabled
MMC: SDHCI: 0
Using default environment

In: serial
Out: serial
Err: serial
Net: zynq_gem
Hit any key to stop autoboot: 3 ··· 2 ··· 1 ··· 0
Copying Linux from SD to RAM...
Device: SDHCI
Manufacturer ID: 3
OEM: 5344
Name: SU32G
Tran Speed: 25000000
Rd Block Len: 512
SD version 2.0
High Capacity: Yes
Capacity: 29.7 GiB
Bus Width: 4-bit
reading zImage

2493032 bytes read
reading devicetree.dtb

3981 bytes read
reading ramdisk8M.image.gz

** Unable to read "ramdisk8M.image.gz" from mmc 0:1 **
## Starting application at 0x00008000 ...
Uncompressing Linux... done, booting the kernel.
Booting Linux on physical CPU 0

Linux version 3.3.0-01412-g71b0efa-dirty (lars@lars-adi-laptop) (gcc version 4.5.1 (Sourcery G++ Lite 2010.09-62) ) #2504 SMP PREEMPT Fri Jun 8 20:12:45 CEST 2012

CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=18c5387d

CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache

Machine: Xilinx Zynq Platform, model: Xilinx Zynq ZED

bootconsole [earlycon0] enabled

Memory policy: ECC disabled, Data cache writealloc

BUG: mapping for 0xf8f00000 at 0xfe00c000 out of vmalloc space

BUG: mapping for 0xe0001000 at 0xfe001000 out of vmalloc space

BUG: mapping for 0xffff1000 at 0xfe200000 out of vmalloc space

PERCPU: Embedded 7 pages/cpu @c0de4000 s6400 r8192 d14080 u32768

Built 1 zonelists in Zone order, mobility grouping on. Total pages: 117824

Kernel command line: console=ttyPS0,115200 root=/dev/mmcblk0p2 rw earlyprintk rootfstype=ext4 rootwait devtmpfs.mount=0

PID hash table entries: 2048 (order: 1, 8192 bytes)

Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)

Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)

Memory: 240MB 224MB = 464MB total

Memory: 460424k/460424k available, 31096k reserved, 0K highmem

Virtual kernel memory layout:

vector : 0xffff0000 - 0xffff1000 ( 4 kB)

fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)

vmalloc : 0xde800000 - 0xfd000000 ( 488 MB)

lowmem : 0xc0000000 - 0xde000000 ( 480 MB)

pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)

modules : 0xbf000000 - 0xbfe00000 ( 14 MB)

.text : 0xc0008000 - 0xc04715c4 (4518 kB)

.init : 0xc0472000 - 0xc0499900 ( 159 kB)

.data : 0xc049a000 - 0xc04d15c0 ( 222 kB)

.bss : 0xc04d15e4 - 0xc09d990f (5153 kB)

Preemptible hierarchical RCU implementation.

·RCU lockdep checking is enabled.

·Verbose stalled-CPUs detection is disabled.

NR_IRQS:128

xlnx,ps7-ttc-1.00.a #0 at 0xde800000, irq=43

Console: colour dummy device 80x30

Lock dependency validator: Copyright (c) 2006 Red Hat, Inc., Ingo Molnar

... MAX_LOCKDEP_SUBCLASSES: 8

... MAX_LOCK_DEPTH: 48

... MAX_LOCKDEP_KEYS: 8191

... CLASSHASH_SIZE: 4096

... MAX_LOCKDEP_ENTRIES: 16384

... MAX_LOCKDEP_CHAINS: 32768

... CHAINHASH_SIZE: 16384

memory used by lock dependency info: 3695 kB

per task-struct memory footprint: 1152 bytes

Calibrating delay loop... 1332.01 BogoMIPS (lpj=6660096)

pid_max: default: 32768 minimum: 301

Mount-cache hash table entries: 512

CPU: Testing write buffer coherency: ok

CPU0: thread -1, cpu 0, socket 0, mpidr 80000000

smp_twd: clock not found: -2

Calibrating local timer... 333.38MHz.

hw perfevents: enabled with ARMv7 Cortex-A9 PMU driver, 7 counters available

Setting up static identity map for 0x329d98 - 0x329dcc

CPU1: Booted secondary processor

CPU1: thread -1, cpu 1, socket 0, mpidr 80000001

Brought up 2 CPUs

SMP: Total of 2 processors activated (2664.03 BogoMIPS).

devtmpfs: initialized

------------[ cut here ]------------

WARNING: at arch/arm/mm/dma-mapping.c:198 consistent_init+0x70/0x104()

Modules linked in:

[<c0012dbc>] (unwind_backtrace+0x0/0xe0) from [<c001f510>] (warn_slowpath_common+0x4c/0x64)

[<c001f510>] (warn_slowpath_common+0x4c/0x64) from [<c001f540>] (warn_slowpath_null+0x18/0x1c)

[<c001f540>] (warn_slowpath_null+0x18/0x1c) from [<c04765b8>] (consistent_init+0x70/0x104)

[<c04765b8>] (consistent_init+0x70/0x104) from [<c0008668>] (do_one_initcall+0x94/0x168)

[<c0008668>] (do_one_initcall+0x94/0x168) from [<c0472850>] (kernel_init+0x84/0x130)

[<c0472850>] (kernel_init+0x84/0x130) from [<c000e22c>] (kernel_thread_exit+0x0/0x8)

---[ end trace 1b75b31a2719ed1c ]---

------------[ cut here ]------------

WARNING: at arch/arm/mm/dma-mapping.c:198 consistent_init+0x70/0x104()

Modules linked in:

[<c0012dbc>] (unwind_backtrace+0x0/0xe0) from [<c001f510>] (warn_slowpath_common+0x4c/0x64)

[<c001f510>] (warn_slowpath_common+0x4c/0x64) from [<c001f540>] (warn_slowpath_null+0x18/0x1c)

[<c001f540>] (warn_slowpath_null+0x18/0x1c) from [<c04765b8>] (consistent_init+0x70/0x104)

[<c04765b8>] (consistent_init+0x70/0x104) from [<c0008668>] (do_one_initcall+0x94/0x168)

[<c0008668>] (do_one_initcall+0x94/0x168) from [<c0472850>] (kernel_init+0x84/0x130)

[<c0472850>] (kernel_init+0x84/0x130) from [<c000e22c>] (kernel_thread_exit+0x0/0x8)

---[ end trace 1b75b31a2719ed1d ]---

NET: Registered protocol family 16

L310 cache controller enabled

l2x0: 8 ways, CACHE_ID 0x410000c8, AUX_CTRL 0x72360000, Cache size: 524288 B

registering platform device 'pl330' id 0

registering platform device 'arm-pmu' id 0

hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.

hw-breakpoint: maximum watchpoint size is 4 bytes.

MIO pin 11 not assigned(00001760)

xslcr xslcr.0: at 0xF8000000 mapped to 0xDE808000

bio: create slab <bio-0> at 0

gpiochip_add: registered GPIOs 0 to 245 on device: xgpiops

xgpiops e000a000.gpio: gpio at 0xe000a000 mapped to 0xde80a000

status: 10006, mask: 4, value: 0

status: 10002, mask: 4, value: 0

status: 10002, mask: 4, value: 0

SCSI subsystem initialized

usbcore: registered new interface driver usbfs

usbcore: registered new interface driver hub

usbcore: registered new device driver usb

Advanced Linux Sound Architecture Driver Version 1.0.24.

Switching to clocksource xttcpss_timer1

NET: Registered protocol family 2

IP route cache hash table entries: 4096 (order: 2, 16384 bytes)

TCP established hash table entries: 16384 (order: 5, 131072 bytes)

TCP bind hash table entries: 16384 (order: 7, 655360 bytes)

TCP: Hash tables configured (established 16384 bind 16384)

TCP reno registered

UDP hash table entries: 256 (order: 2, 24576 bytes)

UDP-Lite hash table entries: 256 (order: 2, 24576 bytes)

NET: Registered protocol family 1

xscugtimer xscugtimer.0: ioremap fe00c200 to de810200 with size 400

pl330 dev 0 probe success

msgmni has been set to 899

io scheduler noop registered

io scheduler deadline registered

io scheduler cfq registered (default)

e000100ˇconsole [ttyPS0] enabled, bootconsole disabled
console [ttyPS0] enabled, bootconsole disabled

xdevcfg f8007000.devcfg: ioremap f8007000 to de814000 with size 1000
[drm] Initialized drm 1.1.0 20060810
brd: module loaded
loop: module loaded
xqspips e000d000.spi: at 0xE000D000 mapped to 0xDE816000, irq=51
GEM: BASEADDRESS hw: e000b000 virt: de818000
XEMACPS mii bus: probed
eth0, pdev->id -1, baseaddr 0xe000b000, irq 54
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
usb_hcd_xusbps_probe: No OTG assigned!
usb_hcd_xusbps_probe: OTG now assigned!
xusbps-ehci xusbps-ehci.0: Xilinx PS USB EHCI Host Controller
xusbps-ehci xusbps-ehci.0: new USB bus registered, assigned bus number 1
xusbps-ehci xusbps-ehci.0: irq 53, io mem 0x00000000
xusbps-ehci xusbps-ehci.0: USB 2.0 started, EHCI 1.00
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
Xilinx PS USB Device Controller driver (Apr 01, 2011)
mousedev: PS/2 mouse device common for all mice
Linux video capture interface: v2.00
gspca_main: v2.14.0 registered
usbcore: registered new interface driver uvcvideo
USB Video Class driver (1.1.1)
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pltfm: SDHCI platform and OF driver helper
mmc0: Hardware doesn't specify timeout clock frequency.
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
ALSA device list:
No soundcards found.
TCP cubic registered
NET: Registered protocol family 17
adv7511 0-0039: Failed to add route DAI IN->TMDS
VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
Registering SWP/SWPB emulation handler
drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
asoc: adv7511 <-> 75c00000.axi-spdif-tx mapping ok
axi-spdif 75c00000.axi-spdif-tx: Failed to set DAI format: -22
Waiting for root device /dev/mmcblk0p2...
detect: 90 2 1 0
No connectors reported connected with modes
[drm] Cannot find any crtc or sizes - going 1024x768
Console: switching to colour frame buffer device 128x48
fb0: frame buffer device
drm: registered panic notifier
[drm] Initialized analog_drm 1.0.0 20110530 on minor 0
detect: 90 2 0 3
detect: 90 2 0 3
detect: 90 2 0 3
detect: 90 2 0 3
detect: 90 2 0 3
detect: 90 2 0 3
detect: 90 2 0 3
detect: 90 2 0 3
detect: 90 2 0 3
mipt98
 
Posts: 17
Joined: Sat May 25, 2013 12:39 am

Re: Edited: Cannot boot Zedboard from the 13020600 image

Postby mipt98 » Sun Jul 14, 2013 3:23 pm

Could anybody post their boot log? Thanks!
mipt98
 
Posts: 17
Joined: Sat May 25, 2013 12:39 am

Re: Edited: Cannot boot Zedboard from the 13020600 image

Postby aolofsson » Mon Jul 15, 2013 1:25 am

Ivan,

I haven't seen this before, maybe others have had similar problems and can assist?

Just to summarize the burn and boot process that is the most thoroughly tested so far:

1.) For the 64-core board grab this file.
ftp://ftp.parallella.org/parallella/sd_ ... 020600.zip

2.) Use a 8GB or 16GB card SDHC card like the following:
http://www.amazon.com/SanDisk-MicroSDHC ... 695&sr=1-2

3.) Use the win32diskimager to write the image to the sd card. (I am sure you can do it in Linux, but this is what we started with..)
http://sourceforge.net/projects/win32di ... t/download

4.) Make sure the Epiphany FMC card is plugged in at boot.

5.) Read the quick start guide here, make sure all the jumpers are in the correct positions!
https://github.com/adapteva/epiphany-li ... _guide.pdf

6.) If for some reason the board still has issues, it might be a uart or hdmi issue? Try hooking up the ethernet cable only and see if the machine comes up on the network...sorry for asking you to try this.

Andreas
User avatar
aolofsson
 
Posts: 1005
Joined: Tue Dec 11, 2012 6:59 pm
Location: Lexington, Massachusetts,USA

Re: Edited: Cannot boot Zedboard from the 13020600 image

Postby mipt98 » Tue Jul 16, 2013 6:28 pm

I went through all the steps but still struggling with the boot process and eager to see a successful boot log...

I have one suggestion. Currently, the kernel launch parameters are hardcoded in the device tree. It would be great to expose them to U-boot environment in order to be able to quickly modify them. For instance, I would like to try to mount the root fs to RAM and see what will happen, but can't do it without recompiling the tree. Apparently a standard way of doing it is to
$ setenv bootargs '<args>'; boot
However it seems that the hardcoded parameters take precedence over the environment settings.
-Ivan
mipt98
 
Posts: 17
Joined: Sat May 25, 2013 12:39 am

Re: Edited: Cannot boot Zedboard from the 13020600 image

Postby mipt98 » Wed Jul 17, 2013 6:33 am

First good news in the last several days. I was blaming the SD detect feature, thought maybe it was a hardware problem, bad pin or something. So decided to disable the card detect in the kernel (make it always be true), but first simply compiled the kernel from gen0 in https://github.com/parallella/parallella-linux. And this new kernel booted. Presumably there was some sort of mismatch between the zedboard I have and the kernel on the FTP site.

Still things look glitchy: getting different boot messages from time to time. Sometimes I get errors. For instance, first I can get these
Freeing init memory: 152K
* Starting mDNS/DNS-SD daemon [ OK ]
* Starting Bridge udev events into upstart [ OK ]
* Starting network connection manager [ OK ]
* Starting Bridge udev events into upstart [ OK ]
* Starting Bridge udev events into upstart [ OK ]
* Stopping cold plug devices [ OK ]
* Stopping log initial device creation [ OK ]
* Starting load fallback graphics devices [ OK ]
* Starting configure virtual network devices [ OK ]
* Starting load fallback graphics devices [fail]
* Starting configure network device security [ OK ]
* Starting Userspace bootsplash [ OK ]

and at the next boot I see the following
Freeing init memory: 152K
modprobe: FATAL: Could not load /lib/modules/3.6.0-xilinx/modules.dep: No such file or directory

modprobe: FATAL: Could not load /lib/modules/3.6.0-xilinx/modules.dep: No such file or directory

* Starting mDNS/DNS-SD daemon [ OK ]
* Starting network connection manager [ OK ]
* Starting Bridge udev events into upstart [ OK ]
* Stopping cold plug devices [ OK ]
* Stopping log initial device creation [ OK ]
* Starting load fallback graphics devices [ OK ]
* Starting load fallback graphics devices [fail]


Does it look normal or not?
-Ivan
mipt98
 
Posts: 17
Joined: Sat May 25, 2013 12:39 am

Re: Edited: Cannot boot Zedboard from the 13020600 image

Postby 9600 » Wed Jul 17, 2013 11:12 am

Andrew Back
User avatar
9600
 
Posts: 997
Joined: Mon Dec 17, 2012 3:25 am

Re: Edited: Cannot boot Zedboard from the 13020600 image

Postby 9600 » Wed Jul 17, 2013 11:19 am

Andrew Back
User avatar
9600
 
Posts: 997
Joined: Mon Dec 17, 2012 3:25 am

Re: Edited: Cannot boot Zedboard from the 13020600 image

Postby aolofsson » Wed Jul 17, 2013 12:40 pm

User avatar
aolofsson
 
Posts: 1005
Joined: Tue Dec 11, 2012 6:59 pm
Location: Lexington, Massachusetts,USA

Re: Edited: Cannot boot Zedboard from the 13020600 image

Postby mipt98 » Wed Jul 17, 2013 10:23 pm

mipt98
 
Posts: 17
Joined: Sat May 25, 2013 12:39 am

Re: Edited: Cannot boot Zedboard from the 13020600 image

Postby aolofsson » Thu Jul 18, 2013 12:12 am

Ivan,

That's great news! What you are seeing is the result of a know anomaly in the E64 chip. There is an errata (documented in the datasheet) that limits fetching instructions and loading data (LDR) from DRAM to row-2. Using DMA to bring in data on that row works fine. This is unfortunate, but in many programs workarounds to this issue are ok.

With respect to the matmul, this is likely due to an old example. I recommend installing the latest SDK. viewtopic.php?f=13&t=422

Andreas
User avatar
aolofsson
 
Posts: 1005
Joined: Tue Dec 11, 2012 6:59 pm
Location: Lexington, Massachusetts,USA

Next

Return to Linux/U-Boot

Who is online

Users browsing this forum: No registered users and 66 guests