Early console with Xilinx-based AXI UART

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello,

We implemented the Xilinx IP AXI UART inside a Artix-7 Xilinx device.
The Xilinx is seen as a PCI peripheral implementing several IO spaces to host, among others, the 4 serial ports.
The PCI configuration space is configured to get the UART to be visible on IO space at 0xb000, 0xb200, 0xb400 and 0xb600.
We are running a 2.6.32 linux on our embedded system, and the kernel detects our 4 new serial ports as /dev/ttyS4 to /dev/ttyS7.
The system console is routed to /dev/ttyS4 (configured in the GRUB menu with 'console=ttyS4,115200') and works flawlessly.
So far so good...

What happens ?
Early in the kernel start sequence, we get following message :
"kdb: Initialization failed - no console.  kdb is disabled.".

This is probably caused by the lack of console at kdb start.
In order to check this hypothesis, I tried to add following parameter in the command line:
"console=uart8250,io,0xb400,115200n8", but the kernel freezes very soon in its starting sequence.

Do you think that this IO space is available at this point of the starting sequence ?
What would be the configuration parameters to be used to the early console on this specific serial port ?

Thanks in advance.
Best regards,
Patrick Agrain
--
To unsubscribe from this list: send the line "unsubscribe linux-serial" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Linux PPP]     [Linux FS]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Video 4 Linux]     [Linmodem]     [Device Mapper]     [Linux Kernel for ARM]

  Powered by Linux