Re: [microblaze-uclinux] uclinux on microblaze

[John Williams <jwilliams@xxxxxxxxxxxxxx>]

Hi Bret,

Bret Ketchum wrote:

> 	Now I am stumped, the 9.1 variety of the Virus spits out:

Virus?  frustrated with EDK perhaps?

> ERROR:MDT - petalinux () - No driver for stdin peripheral RS232_Uart_A.
> Check
>    the following reasons: 
>     1. RS232_Uart_A is not accessible from processor microblaze_0.
>     2. No Driver block is defined for RS232_Uart_A in MSS file.
>        while executing
>    "error "No driver for stdin peripheral $stdin. Check the following
> reasons:
>    \n 1. $stdin is not accessible from processor $processor.\n 2. No Driver
>    bl..."

[snip]

> 	And I think the project is configured correctly:

> BEGIN OS
>  PARAMETER OS_NAME = petalinux
>  PARAMETER OS_VER = 1.00.b
>  PARAMETER PROC_INSTANCE = microblaze_0
>  PARAMETER lmb_memory = dlmb_cntlr
>  PARAMETER main_memory = Generic_DDR2
>  PARAMETER stdin = RS232_Uart_A
>  PARAMETER stdout = RS232_Uart_A
> END
>
> BEGIN DRIVER
>  PARAMETER DRIVER_NAME = uartlite
>  PARAMETER DRIVER_VER = 1.02.a
>  PARAMETER HW_INSTANCE = RS232_Uart_A
> END
>
> BEGIN DRIVER
>  PARAMETER DRIVER_NAME = uartlite
>  PARAMETER DRIVER_VER = 1.02.a
>  PARAMETER HW_INSTANCE = RS232_Uart_B
> END

yep, looks OK

> 	I do have two UARTs which may be a problem (I can try removing one
> today)

Two UARTs won't be a problem by themselves.

> 	Or the opb_bridge may be a problem (which I can look at also). 

Make sure that the bridges are in the correct direction (remember 
opb2opb is unidirectional, you need one in *each direction* to achieve 
bidirectional comms.

Also double check that the bridged address ranges overlap with the 
peripherals you need to be able to access via those bridges.

Failure to ensure either of the above would explain libgen's complaint 
about UART_A not being visible from the MicroBlaze.

One
> question I have is where does xhandle_stdin live?

This part of the generation phase is simply handed off by the PetaLinux 
BSP scripts to a core EDK libgen script, indeed the stdin/stdout 
parameters are completely ignored in the kernel, but are used to 
configure FS-boot and u-boot.

Regards,

John
___________________________
microblaze-uclinux mailing list
microblaze-uclinux@xxxxxxxxxxxxxx
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/