Re: Kernel Panic During Linux Boot on ML405

[Peter Mendham <petermendham@computing.dundee.ac.uk>]

Sharon Feldman wrote:
> Make Sure That when you generate the bsp you need to specify the drivers you wish to generate bsp for in the software platform settings
> in "OS and Libraries" Tab you should click on the connected peripherial and add the peripherials you wish to generated bsp for, also you must specify a driver for them in the "DRIVERS" TAB, otherwise you will not beable to add them.
>   
That was exactly my problem.  I do feel pretty stupid, but I just 
assumed that when I selected mvl as the OS the EDK would assume that I'd 
quite like it to support my peripherals.  I've learnt my lesson over 
that one.  Sorry for bothering people.

However, now I have new problem, this time at shutdown.  I get the 
following messages:

The system is going down NOW !!
Sending SIGTERM to all processes.
Xilinx OS Independent Code XAssert: xuartlite.c:195
Code may crash due to unhandled errors.
gs: gs_close: bad port count; tty->count is 1, port count is 3
System halted.
System Halted

The assert at xuartlite.c:195 is:
XASSERT_NONVOID(((signed)NumBytes) >= 0);
during XUartLite_Send.  This checks to see if the number of bytes 
forming the send request is greater than zero (quite reasonably I 
feel).  The "gs" appears to relate to generic_serial and comes from 
gs_close in generic_serial.c  I don't understand any more than that.  
Does anyone have any ideas where to start looking?

Thanks,
-- Peter