[ECOS] gdb hang

[ECOS] gdb hang

[Daniel.Andersson]

Hi,

When i have downloaded eCos to my EB40 board and trying to run it then it
hangs on the same line every time. It is the last line in the clip below
(104):

-----------clip------------------
86	#ifdef CYGDBG_INFRA_DIAG_USE_DEVICE
87	
88	// Initialize after IO devices.
89	static Cyg_dummy_diag_init_class cyg_dummy_diag_init_obj 
90
CYGBLD_ATTRIB_INIT_AFTER(CYG_INIT_IO);
91	
92
/*----------------------------------------------------------------------*/
93	/* Write single char to output
*/
94	
95	externC void diag_write_char(char c)
96	{
97	    diag_device_write_char(c);
98	}
99	
100	#else
101	
102	// Initialize after HAL.
103	static Cyg_dummy_diag_init_class cyg_dummy_diag_init_obj 
104
CYGBLD_ATTRIB_INIT_AFTER(CYG_INIT_HAL);
-----------clip------------------

Why is this function used? Can i disable it or in some other way come around
the problem?

/Daniel

Re: [ECOS] gdb hang

[Jonathan Larmour]

Daniel.Andersson@combitechsystems.com wrote:
> 
> Hi,
> 
> When i have downloaded eCos to my EB40 board and trying to run it then it
> hangs on the same line every time. It is the last line in the clip below
> (104):
> 
> -----------clip------------------
> 86      #ifdef CYGDBG_INFRA_DIAG_USE_DEVICE
> 87
> 88      // Initialize after IO devices.
> 89      static Cyg_dummy_diag_init_class cyg_dummy_diag_init_obj
> 90
> CYGBLD_ATTRIB_INIT_AFTER(CYG_INIT_IO);
> 91
> 92
> /*----------------------------------------------------------------------*/
> 93      /* Write single char to output
> */
> 94
> 95      externC void diag_write_char(char c)
> 96      {
> 97          diag_device_write_char(c);
> 98      }
> 99
> 100     #else
> 101
> 102     // Initialize after HAL.
> 103     static Cyg_dummy_diag_init_class cyg_dummy_diag_init_obj
> 104
> CYGBLD_ATTRIB_INIT_AFTER(CYG_INIT_HAL);
> -----------clip------------------
> 
> Why is this function used? Can i disable it or in some other way come around
> the problem?

It initializes the serial port. It may indicate that the default port
parameters in the hal_diag part of the platform HAL do not correspond with
what's being used before that. For example if the ROM monitor that loaded
the program was intended to work at 38K4, but the application was built
assuming 57K6, or whatever.

Jifl
-- 
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine