[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[microblaze-uclinux] Kernel Crash using second serial port
- To: microblaze-uclinux@xxxxxxxxxxxxxx
- Subject: [microblaze-uclinux] Kernel Crash using second serial port
- From: Jeff McBride <mcbridejc@xxxxxxxxx>
- Date: Thu, 22 Sep 2005 13:41:19 -0400
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=LEKNSnM3a7UUq80Lxj1e4GbvimqiHDDfdrUbByTWf3YDuAS0FDdlzl7PTkM2MWK+k1bnWsviVPqHO535tUjeW+98lMEsLdaFTYsiBh8231Pb9oq9KrfM7FuE2Qqe5QLlDPYTsEo1iF5HesgSErKHtUAPPM7VNHYZkzkboY0Vyrs=
- Reply-to: microblaze-uclinux@xxxxxxxxxxxxxx
- Sender: owner-microblaze-uclinux@xxxxxxxxxxxxxx
Hello All,
I am working on my first Microblaze application using uClinux, and I
have run into a problem. I am creating a relatively simple
application, to run on the Atmark-techno suzaku board, that reads
pulse widths for several incoming PWM signals (using custom VHDL
hardware) and that reads and writes data to a second UARTLite on
TTYS1. After initially thinking everything was working fine, I
discovered that the board will hang and stop responding after a random
period, usually somewhere between 2-15 minutes. I have seen a couple
of different error message printed to the console when it crashes. The
first is more frequent, but sometimes it gives the second message:
----------Error 1-----------
VFS: Insert <NULL> and press ENTER
kernel BUG at sched.c:562!
---------Error 2----------
Kernel panic: VFS: Unable to mount root fs on ff:fe
In idle task - not syncing
The basic flow of my application is:
1. read() call to poll serial port for incoming data, and when a full
message is received, process it (this basically means read a status
message and write to a mem addr to control an LED display)
2. Read PWM values (read mem addresses)
3. Write serial message with PWM values to ttyS1
4. usleep(20000)
My hunch is that this is being caused by the second serial port
somehow, because if I remove calls to the serial routines (read(),
write()), and just cycle the LEDS and do usleep() delays, it does not
crash. And if I remove the usleeps and serial write portions of the
application and just do repeated non-blocking reads, it crashes in
seconds.
Has anyone on the list encountered any similar problems, or does
anyone have any suggestions on where to look next? I am somewhat
stumped at this point. I think my next step will be to figure out how
to get rid of the console on ttyS0 and use that for my application.
Thanks for any advice, I will be sure to send an update if I find a solution.
-Jeff
___________________________
microblaze-uclinux mailing list
microblaze-uclinux@itee.uq.edu.au
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/