cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
7,898 Views
Registered: ‎05-16-2015

PetLinux xuartps bootup erroor: e0000000.serial: failed to get alias id, errno -19

Jump to solution

Hi all,

 

I'm moving the first steps in the PetLinux world.

 

I've been able to boot the prebuilt image for my development board (microzed) using both, the board and the qemu.

 

I'm trying to get the things to work by building the peta linux kernel with the peta linux SDK.

I've been "successful" on building the image.

 

By trying to bootup the that image I'm running into an error (in both cases: qemu & hardware):

 

 

io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-267056
dma-pl330 f8003000.ps7-dma: 	DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
xuartps e0000000.serial: failed to get alias id, errno -19
e0000000.serial: ttyPS0 at MMIO 0xe0000000 (irq = 59, base_baud = 992063) is a xuartps
console [ttyPS0] enabled
bootconsole [earlycon0] disabled

 

the qemu doesn't seems to go further.

On HW:

io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-267056
dma-pl330 f8003000.ps7-dma:     DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
xuartps e0000000.serial: failed to get alias id, errno -19
e0000000.serial: ttyPS0 at MMIO 0xe0000000 (irq = 59, base_baud = 3124999) is a xuartps
INFO: rcu_preempt detected stalls on CPUs/tasks: { 0} (detected by 1, t=6502 jiffies, g=4294967051, c=4294967050, q=50)
Task dump for CPU 0:
swapper/0       R running      0     1      0 0x00000002
[<c04919c8>] (__schedule) from [<00000000>] (  (null))
INFO: rcu_preempt detected stalls on CPUs/tasks: { 0} (detected by 1, t=26007 jiffies, g=4294967051, c=4294967050, q=50)

Any hint on this ? What I forgot to perform/configure?

 

Thank you in advance!

0 Kudos
1 Solution

Accepted Solutions
14,299 Views
Registered: ‎05-16-2015
0 Kudos
2 Replies
rfs613
Scholar
Scholar
7,878 Views
Registered: ‎05-28-2013

This occurs when you boot a newer kernel with an old device tree (dtb). The newer serial driver looks for serial alias, such as:

aliases {
     serial0 = &uart0;
}

For a more complete example, see line 21 to 25 in https://github.com/Xilinx/linux-xlnx/blob/master/arch/arm/boot/dts/zynq-zed.dts

0 Kudos
14,300 Views
Registered: ‎05-16-2015
0 Kudos