[okl4-developer] Problem about porting OKL4

Geoffrey Lee glee at ok-labs.com
Mon Aug 11 21:57:08 EST 2008


On Mon, Aug 11, 2008 at 04:29:04PM +0800, Sean wrote:
> Dear
> 
> Now I'm porting OKL4 to a ARM922T platform.
> I have already finished modification of UART, timer and interrupt
> controller.
> And I can get the output message from serial port.
> 
> But when the kernel run into schedule, the example program can't execute.
> There is no output from example program.
> 
> I can sure that the timer interrupt is executed successfully by printing the
> current_time variables in scheduler_t::handle_timer_interrupt() function.
> (current_time = 10000
> current_time = 20000
> current_time = 30000
> current_time = 40000)
> 
> The serial output show follow,
> ==========================================
> OKL4 - (provider: Open Kernel Labs) built on Aug 11 2008 12:23:49 using gcc
> version 3.4.4.
> Initialized tracebuffer @ 32140000
> Init spaceids for 256 spaces
> Initializing kernel space @ f001ff58...
> Initializing kernel debugger...
> Initializing interrupts...
> System running with alignment exceptions enabled
> Processor Id => 41029220: v4T, ARM922, rev 0
> Initializing timer...
> TLB lock: vectors @ ffff0000
> TLB lock: utcb @ ff000000
> TLB lock: kernel @ f0000000
> Locked kernel into TLB
> Init mutexids for 256 mutexs
> Init clistids for 16 clists
> domain pairs: (0, 1)
> Initialising scheduler...
> Switching to idle thread
> Initializing root servers
> root-servers: utcb_area: dff00100 (64KB)
> creating root server (00000001)
> ==========================================
> Then the output screen is halted.
> 
> Can anyone give me any idea where the problem is?
> 


You can break into the debugger to find out what the user thread
is doing by looking at the stack pointer, instruction pointer
or the register dump.


> Thanks a lot!!
> 
> Best Regards,
> Sean

	-gl


> _______________________________________________
> Developer mailing list
> Developer at okl4.org
> https://lists.okl4.org/mailman/listinfo/developer


-- 




More information about the Developer mailing list