[ECOS] GNU tools combination for eCos

[ECOS] GNU tools combination for eCos

[peter_ku]

Hi,

My work environment is Window Me and the hw-target is E7T
I use the following combination to generate eCos, according to the eCos web site.
 binutils 2.10.1
 GCC2.95.2 + ecos-gcc-2952.pat
 Insight 5.0  + insight-tcl.pat

everything is fine, except that I can't run gdb (I can run gdb -nw). and I check the mail list.
and understand that insight 5.0 have some problem running under win98.

But I think maybe the insight 5.0 is too old to find the update version on the ftp site.
So I download insight 5.1, but I fail to compile. maybe the GCC is too old , I think.

Anyone can give me a combination (binutils + GCC + insight, even cygwin) that I can run everything  under 
WindowMe without problem? 

Thanks a lot.

Best Regards,
peter

Re: [ECOS] GNU tools combination for eCos

[Jonathan Larmour]

peter_ku wrote:
> 
> Hi,
> 
> My work environment is Window Me and the hw-target is E7T
> I use the following combination to generate eCos, according to the eCos web site.
>  binutils 2.10.1
>  GCC2.95.2 + ecos-gcc-2952.pat
>  Insight 5.0  + insight-tcl.pat
> 
> everything is fine, except that I can't run gdb (I can run gdb -nw). and I check the mail list.
> and understand that insight 5.0 have some problem running under win98.
> 
> But I think maybe the insight 5.0 is too old to find the update version on the ftp site.
> So I download insight 5.1, but I fail to compile. maybe the GCC is too old , I think.

Perhaps Insight 5.1.1 or 5.2 would be better:
ftp://sources.redhat.com/pub/gdb/releases/

Note you won't need the insight-tcl.pat for these.

Jifl
-- 
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
--[ "You can complain because roses have thorns, or you ]--
--[  can rejoice because thorns have roses." -Lincoln   ]-- Opinions==mine

-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

[ECOS] E7T timer0 interrupt issue ?

[peter_ku]

Hello,

Target = E7T.
I write a simple program to test timer0 interrupt, I want to toggle the led every 1sec. But I can't enter my ISR.
I can see the INTPND = 0x400, and also see my timer0 running!!
Anyone can check the following code?

thanks a lot
Peter


#define TOTAL_THREADS	1

cyg_thread threads[TOTAL_THREADS];

cyg_handle_t handle_thread_show_led;
cyg_handle_t handle_timer0_isr;

cyg_interrupt isr;

char	stack[TOTAL_THREADS][4096];

cyg_thread_entry_t 	show_led_proc;
cyg_ISR_t 		Timer0_ISR;
cyg_DSR_t		Timer0_DSR;

void cyg_user_start(void)
{
  cyg_thread_create(4, show_led_proc , (cyg_addrword_t) 0 , "THREAD SHOW LED", (void *) stack[0], 4096,
  			&handle_thread_show_led, &threads[0]);
  			

  cyg_interrupt_create(CYGNUM_HAL_INTERRUPT_TIMER0,99,0,Timer0_ISR, Timer0_DSR, &handle_timer0_isr, &isr);
  
  cyg_interrupt_attach(handle_timer0_isr);
  
  HAL_WRITE_UINT32(E7T_TDATA0,50000000);  
  HAL_WRITE_UINT32(E7T_TMOD,E7T_TMOD_TE0 | E7T_TMOD_TMD0);
  
  cyg_interrupt_unmask(CYGNUM_HAL_INTERRUPT_TIMER0);
  cyg_interrupt_enable();
  
    
  cyg_thread_resume(handle_thread_show_led);
		
	
}




void show_led_proc(cyg_addrword_t data)
{

   int i,j;
   int temp_data;
   
   
   HAL_READ_UINT32(E7T_IOPDATA,temp_data);
   temp_data |= 0xf0;
   HAL_WRITE_UINT32(E7T_IOPDATA,temp_data);
      
   for( ; ; )
   {
     for( i =0 ; i < 10 ; i++)
     {
   	
   	HAL_READ_UINT32(E7T_IOPDATA,temp_data);
   	temp_data &= ~SEG_MASK;
   	temp_data |= numeric_display[i];
   	HAL_WRITE_UINT32(E7T_IOPDATA,temp_data);
   	for(j = 0; j < 10000000; j++) { }
     }	
		
   }
	
}


cyg_uint32 Timer0_ISR(cyg_vector_t vector, cyg_addrword_t data)
{

   cyg_uint32 temp_data;
   HAL_READ_UINT32(E7T_IOPDATA,temp_data);
   temp_data ^= 0xf0;
   HAL_WRITE_UINT32(E7T_IOPDATA,temp_data);	

   cyg_interrupt_acknowledge(vector);	
   
   return CYG_ISR_HANDLED;
}

void Timer0_DSR(cyg_vector_t vector,cyg_ucount32 count, cyg_addrword_t data)
{

}

RE: [ECOS] GNU tools combination for eCos

[peter_ku]

Hi

thanks a lot.
I give up the Windows Me, and start to use Windows 2000. it looks ok to build all the tools. 
binutils 2.10.1
GCC2.95.2 + ecos-gcc-2952.pat
Insight 5.0  + insight-tcl.pat

If I want to use insight5.1 or insight5.2, is it also fine to build by GCC2.92.2 and binutils 2.10.1 ?

Peter

-----Original Message-----
From: ecos-discuss-owner@sources.redhat.com [mailto:ecos-discuss-owner@sources.redhat.com]On Behalf Of Jonathan Larmour
Sent: Tuesday, May 21, 2002 9:53 AM
To: peter_ku
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] GNU tools combination for eCos


peter_ku wrote:
> 
> Hi,
> 
> My work environment is Window Me and the hw-target is E7T
> I use the following combination to generate eCos, according to the eCos web site.
>  binutils 2.10.1
>  GCC2.95.2 + ecos-gcc-2952.pat
>  Insight 5.0  + insight-tcl.pat
> 
> everything is fine, except that I can't run gdb (I can run gdb -nw). and I check the mail list.
> and understand that insight 5.0 have some problem running under win98.
> 
> But I think maybe the insight 5.0 is too old to find the update version on the ftp site.
> So I download insight 5.1, but I fail to compile. maybe the GCC is too old , I think.

Perhaps Insight 5.1.1 or 5.2 would be better:
ftp://sources.redhat.com/pub/gdb/releases/

Note you won't need the insight-tcl.pat for these.

Jifl
-- 
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
--[ "You can complain because roses have thorns, or you ]--
--[  can rejoice because thorns have roses." -Lincoln   ]-- Opinions==mine

-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

Re: [ECOS] E7T timer0 interrupt issue ?

[Simoncc]

Peter,
    As I knew, you can not invoke any interrupt in your "user_start"
program.
Only you can do that in driver.

Simon



----- Original Message -----
From: "peter_ku" <peter_ku@issc.com.tw>
To: <ecos-discuss@sources.redhat.com>
Sent: Tuesday, May 21, 2002 11:31 AM
Subject: [ECOS] E7T timer0 interrupt issue ?


> Hello,
>
> Target = E7T.
> I write a simple program to test timer0 interrupt, I want to toggle the
led every 1sec. But I can't enter my ISR.
> I can see the INTPND = 0x400, and also see my timer0 running!!
> Anyone can check the following code?
>
> thanks a lot
> Peter
>
>
> #define TOTAL_THREADS 1
>
> cyg_thread threads[TOTAL_THREADS];
>
> cyg_handle_t handle_thread_show_led;
> cyg_handle_t handle_timer0_isr;
>
> cyg_interrupt isr;
>
> char stack[TOTAL_THREADS][4096];
>
> cyg_thread_entry_t show_led_proc;
> cyg_ISR_t Timer0_ISR;
> cyg_DSR_t Timer0_DSR;
>
> void cyg_user_start(void)
> {
>   cyg_thread_create(4, show_led_proc , (cyg_addrword_t) 0 , "THREAD SHOW
LED", (void *) stack[0], 4096,
>   &handle_thread_show_led, &threads[0]);
>
>
>   cyg_interrupt_create(CYGNUM_HAL_INTERRUPT_TIMER0,99,0,Timer0_ISR,
Timer0_DSR, &handle_timer0_isr, &isr);
>
>   cyg_interrupt_attach(handle_timer0_isr);
>
>   HAL_WRITE_UINT32(E7T_TDATA0,50000000);
>   HAL_WRITE_UINT32(E7T_TMOD,E7T_TMOD_TE0 | E7T_TMOD_TMD0);
>
>   cyg_interrupt_unmask(CYGNUM_HAL_INTERRUPT_TIMER0);
>   cyg_interrupt_enable();
>
>
>   cyg_thread_resume(handle_thread_show_led);
>
>
> }
>
>
>
>
> void show_led_proc(cyg_addrword_t data)
> {
>
>    int i,j;
>    int temp_data;
>
>
>    HAL_READ_UINT32(E7T_IOPDATA,temp_data);
>    temp_data |= 0xf0;
>    HAL_WRITE_UINT32(E7T_IOPDATA,temp_data);
>
>    for( ; ; )
>    {
>      for( i =0 ; i < 10 ; i++)
>      {
>
>    HAL_READ_UINT32(E7T_IOPDATA,temp_data);
>    temp_data &= ~SEG_MASK;
>    temp_data |= numeric_display[i];
>    HAL_WRITE_UINT32(E7T_IOPDATA,temp_data);
>    for(j = 0; j < 10000000; j++) { }
>      }
>
>    }
>
> }
>
>
> cyg_uint32 Timer0_ISR(cyg_vector_t vector, cyg_addrword_t data)
> {
>
>    cyg_uint32 temp_data;
>    HAL_READ_UINT32(E7T_IOPDATA,temp_data);
>    temp_data ^= 0xf0;
>    HAL_WRITE_UINT32(E7T_IOPDATA,temp_data);
>
>    cyg_interrupt_acknowledge(vector);
>
>    return CYG_ISR_HANDLED;
> }
>
> void Timer0_DSR(cyg_vector_t vector,cyg_ucount32 count, cyg_addrword_t
data)
> {
>
> }


-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

Re: [ECOS] E7T timer0 interrupt issue ?

[Gary Thomas]

On Mon, 2002-05-20 at 21:31, peter_ku wrote:
> Hello,
> 
> Target = E7T.
> I write a simple program to test timer0 interrupt, I want to toggle the led every 1sec. But I can't enter my ISR.
> I can see the INTPND = 0x400, and also see my timer0 running!!
> Anyone can check the following code?
> 

You need to start the kernel/scheduler, which in turn enables
interrupts.  If you use cyg_start() or cyg_user_start(), this has to be
done manually (see below).  Alternatively, use main() instead of
cyg_user_start().

> thanks a lot
> Peter
> 
> 
> #define TOTAL_THREADS	1
> 
> cyg_thread threads[TOTAL_THREADS];
> 
> cyg_handle_t handle_thread_show_led;
> cyg_handle_t handle_timer0_isr;
> 
> cyg_interrupt isr;
> 
> char	stack[TOTAL_THREADS][4096];
> 
> cyg_thread_entry_t 	show_led_proc;
> cyg_ISR_t 		Timer0_ISR;
> cyg_DSR_t		Timer0_DSR;
> 
> void cyg_user_start(void)
> {
>   cyg_thread_create(4, show_led_proc , (cyg_addrword_t) 0 , "THREAD SHOW LED", (void *) stack[0], 4096,
>   			&handle_thread_show_led, &threads[0]);
>   			
> 
>   cyg_interrupt_create(CYGNUM_HAL_INTERRUPT_TIMER0,99,0,Timer0_ISR, Timer0_DSR, &handle_timer0_isr, &isr);
>   
>   cyg_interrupt_attach(handle_timer0_isr);
>   
>   HAL_WRITE_UINT32(E7T_TDATA0,50000000);  
>   HAL_WRITE_UINT32(E7T_TMOD,E7T_TMOD_TE0 | E7T_TMOD_TMD0);
>   
>   cyg_interrupt_unmask(CYGNUM_HAL_INTERRUPT_TIMER0);
>   cyg_interrupt_enable();
>   
>     
>   cyg_thread_resume(handle_thread_show_led);
> 	
    cyg_scheduler_start();

	
> 	
> }
> 
> 
> 
> 
> void show_led_proc(cyg_addrword_t data)
> {
> 
>    int i,j;
>    int temp_data;
>    
>    
>    HAL_READ_UINT32(E7T_IOPDATA,temp_data);
>    temp_data |= 0xf0;
>    HAL_WRITE_UINT32(E7T_IOPDATA,temp_data);
>       
>    for( ; ; )
>    {
>      for( i =0 ; i < 10 ; i++)
>      {
>    	
>    	HAL_READ_UINT32(E7T_IOPDATA,temp_data);
>    	temp_data &= ~SEG_MASK;
>    	temp_data |= numeric_display[i];
>    	HAL_WRITE_UINT32(E7T_IOPDATA,temp_data);
>    	for(j = 0; j < 10000000; j++) { }
>      }	
> 		
>    }
> 	
> }
> 
> 
> cyg_uint32 Timer0_ISR(cyg_vector_t vector, cyg_addrword_t data)
> {
> 
>    cyg_uint32 temp_data;
>    HAL_READ_UINT32(E7T_IOPDATA,temp_data);
>    temp_data ^= 0xf0;
>    HAL_WRITE_UINT32(E7T_IOPDATA,temp_data);	
> 
>    cyg_interrupt_acknowledge(vector);	
>    
>    return CYG_ISR_HANDLED;
> }
> 
> void Timer0_DSR(cyg_vector_t vector,cyg_ucount32 count, cyg_addrword_t data)
> {
> 
> }



-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

Re: [ECOS] GNU tools combination for eCos

[Jonathan Larmour]

peter_ku wrote:
> 
> Hi
> 
> thanks a lot.
> I give up the Windows Me, and start to use Windows 2000. it looks ok to build all the tools.
> binutils 2.10.1
> GCC2.95.2 + ecos-gcc-2952.pat
> Insight 5.0  + insight-tcl.pat
> 
> If I want to use insight5.1 or insight5.2, is it also fine to build by GCC2.92.2 and binutils 2.10.1 ?

Remember that the GCC and binutils you are using here are to build
compilers for the *target*. Insight builds completely separately.

Jifl
-- 
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
--[ "You can complain because roses have thorns, or you ]--
--[  can rejoice because thorns have roses." -Lincoln   ]-- Opinions==mine

-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

RE: [ECOS] E7T timer0 interrupt issue ?

[peter_ku]

I found the casue that I can't enter my ISR.
Because I use timer0,  if I change to timer1, everything is fine.
I guess eCos use timer0 to do something, right ???

If I have to use timer0 ISR to do something , what should I do?

Peter


-----Original Message-----
From: ecos-discuss-owner@sources.redhat.com [mailto:ecos-discuss-owner@sources.redhat.com]On Behalf Of peter_ku
Sent: Tuesday, May 21, 2002 11:31 AM
To: ecos-discuss@sources.redhat.com
Subject: [ECOS] E7T timer0 interrupt issue ?


Hello,

Target = E7T.
I write a simple program to test timer0 interrupt, I want to toggle the led every 1sec. But I can't enter my ISR.
I can see the INTPND = 0x400, and also see my timer0 running!!
Anyone can check the following code?

thanks a lot
Peter


#define TOTAL_THREADS	1

cyg_thread threads[TOTAL_THREADS];

cyg_handle_t handle_thread_show_led;
cyg_handle_t handle_timer0_isr;

cyg_interrupt isr;

char	stack[TOTAL_THREADS][4096];

cyg_thread_entry_t 	show_led_proc;
cyg_ISR_t 		Timer0_ISR;
cyg_DSR_t		Timer0_DSR;

void cyg_user_start(void)
{
  cyg_thread_create(4, show_led_proc , (cyg_addrword_t) 0 , "THREAD SHOW LED", (void *) stack[0], 4096,
  			&handle_thread_show_led, &threads[0]);
  			

  cyg_interrupt_create(CYGNUM_HAL_INTERRUPT_TIMER0,99,0,Timer0_ISR, Timer0_DSR, &handle_timer0_isr, &isr);
  
  cyg_interrupt_attach(handle_timer0_isr);
  
  HAL_WRITE_UINT32(E7T_TDATA0,50000000);  
  HAL_WRITE_UINT32(E7T_TMOD,E7T_TMOD_TE0 | E7T_TMOD_TMD0);
  
  cyg_interrupt_unmask(CYGNUM_HAL_INTERRUPT_TIMER0);
  cyg_interrupt_enable();
  
    
  cyg_thread_resume(handle_thread_show_led);
		
	
}




void show_led_proc(cyg_addrword_t data)
{

   int i,j;
   int temp_data;
   
   
   HAL_READ_UINT32(E7T_IOPDATA,temp_data);
   temp_data |= 0xf0;
   HAL_WRITE_UINT32(E7T_IOPDATA,temp_data);
      
   for( ; ; )
   {
     for( i =0 ; i < 10 ; i++)
     {
   	
   	HAL_READ_UINT32(E7T_IOPDATA,temp_data);
   	temp_data &= ~SEG_MASK;
   	temp_data |= numeric_display[i];
   	HAL_WRITE_UINT32(E7T_IOPDATA,temp_data);
   	for(j = 0; j < 10000000; j++) { }
     }	
		
   }
	
}


cyg_uint32 Timer0_ISR(cyg_vector_t vector, cyg_addrword_t data)
{

   cyg_uint32 temp_data;
   HAL_READ_UINT32(E7T_IOPDATA,temp_data);
   temp_data ^= 0xf0;
   HAL_WRITE_UINT32(E7T_IOPDATA,temp_data);	

   cyg_interrupt_acknowledge(vector);	
   
   return CYG_ISR_HANDLED;
}

void Timer0_DSR(cyg_vector_t vector,cyg_ucount32 count, cyg_addrword_t data)
{

}

Re: [ECOS] E7T timer0 interrupt issue ?

[Jonathan Larmour]

peter_ku wrote:
> 
> I found the casue that I can't enter my ISR.
> Because I use timer0,  if I change to timer1, everything is fine.
> I guess eCos use timer0 to do something, right ???

Yes the kernel uses it for all timing related operations.
 
> If I have to use timer0 ISR to do something , what should I do?

Obviously either you have to use some either timer, or change the eCos E7T
port to use some other timer.

Or if you aren't interested in using the eCos kernel, for your example
program you could maybe get away with just calling show_led_proc directly
after cyg_interrupt_enable(). You should remove the eCos kernel
(CYGPKG_KERNEL) completely to do this though as otherwise it will include
some startup code to attach its own interrupt handler to timer 0.

And also in that case you should use the driver API (e.g.
cyg_drv_interrupt_enable() etc.)

Jifl
-- 
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
--[ "You can complain because roses have thorns, or you ]--
--[  can rejoice because thorns have roses." -Lincoln   ]-- Opinions==mine

-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss