[uClinux-dev] Hang on first call to sti()

Thomas Chen tchen at on-go.com
Sun Mar 2 11:08:37 EST 2003


this sounds like when you do a sti, you already have one or more
than one pending interrupts..... and somehow they are not being
cleared properly???  i would check interrupt pending registers
to see what is going on before the sti interruption

on 3/1/03 8:44 PM, HenrySimmons17 at HenrySimmons17 at netzero.net wrote:

> Hello Ryan 
> 2 places you will find these answers:
> in uClinux distribution in file:
> linux/arch/m68knommu/platform/68EZ328/ucsimm/crt0_ram.S
> Motorola MC68EZ328 User's Manual.
> There is an ezample code for the setup.
> Henry
> ----- Original Message -----
> From: Ryan Hulsker <rhulsker at emergentsolutions.ca>
> To: <uclinux-dev at uclinux.org>
> Sent: Wednesday, February 26, 2003 8:04 AM
> Subject: [uClinux-dev] Hang on first call to sti()
> 
> 
>> 
>> I have finally started to make some progress with my Dragonball
>> board.  I now have the dram working and tested, and my kernel boots all
>> the way up to the first call to sti() and then hangs.
>> 
>> I have a feeling that I am generating an interrupt during my setup
>> that I am not clearing properly before the kernel starts.  Below are my
>> setup brecords.  I'm wondering if someone can see what I am doing wrong.
>> 
>> I am also wondering what are the minimum hardware requirements for the
>> kernel to run properly.  My brecord setup disables the RTC/Watchdog etc,
>> but I am pretty sure that the OS needs some sort of regular interrupt to
>> keep it going.  I am assuming that it is done with the RTC/GPT causing
>> an interrupt at the jiffies rate or something.  But what exactly are the
>> parameters?
>> 
>> My board is just a 68EZ328 with 8M dram, no rom or flash.  I have been
>> using the ucsimm build, modified to my needs.
>> 
>> 
>> Thanks,
>> Ryan Hulsker
> 
> 
> 
> _______________________________________________
> uClinux-dev mailing list
> uClinux-dev at uclinux.org
> http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
> This message was resent by uclinux-dev at uclinux.org
> 




More information about the uClinux-dev mailing list