Re: [ECOS] Re: GCC 3.2.1 libgcc_eh.a issue

2007-07-10 Thread Alexander Neundorf
On Tuesday 10 July 2007 02:13, Sergei Gavrikov wrote: > Alexander Neundorf writes: ... > > I didn't dig deeper into the problem yet. > > Are there any known problems with this (k)ubuntu version and ecos ? > > > > Alex > > Ah, I didn't think that is distro issue. It's pity what I don't remember I t

Re: [ECOS] How to enable diag_printf at Redboot

2007-07-10 Thread Sergei Gavrikov
Execuse me a double post, I have a doubts about e-mail delivery. On Tue, Jul 10, 2007 at 04:23:59PM -0300, Tales Toledo wrote: > On 7/9/07, Sergei Gavrikov <[EMAIL PROTECTED]> wrote: > >I again did review your previous RedBoot dumps. You known/sure that is > >1) RAM copy of `fconfig' is correct, 2

Re: [ECOS] How to enable diag_printf at Redboot

2007-07-10 Thread Tales Toledo
On 7/9/07, Sergei Gavrikov <[EMAIL PROTECTED]> wrote: On Mon, Jul 09, 2007 at 04:11:52PM -0300, Tales Toledo wrote: > On 7/9/07, Sergei Gavrikov <[EMAIL PROTECTED]> wrote: > >On Mon, Jul 09, 2007 at 12:45:16PM -0300, Tales Toledo wrote: > >> On 7/6/07, Sergei Gavrikov <[EMAIL PROTECTED]> wrote: >

Re: [ECOS] Re: eCos invalidating JTAG on ARM architecture ?

2007-07-10 Thread Alexandre
Have you tried the CDL option CYGHWR_HAL_ARM_LPC2XXX_IDLE_PWRSAVE Here is the description. I put it in when I was having problems with the JTAG dropping out. Select this option when it is desired to save power by stoping the processor clock in the idle loop. This is

Re: [ECOS] Re: eCos invalidating JTAG on ARM architecture ?

2007-07-10 Thread Alexandre
cyg_thread_delay() does nothing with hardware. It just waits until the correct number of timer ticks have gone off and then brings sleeping process back to running state. Does the system continue to run even though JTAG has stopped? Yep it does :( What test programs are you using? All the sta

Re: [ECOS] Re: eCos invalidating JTAG on ARM architecture ?

2007-07-10 Thread Andy Jackson
Have you tried the CDL option CYGHWR_HAL_ARM_LPC2XXX_IDLE_PWRSAVE Here is the description. I put it in when I was having problems with the JTAG dropping out. Select this option when it is desired to save power by stoping the processor clock in the idle loop. This is

Re: [ECOS] Re: eCos invalidating JTAG on ARM architecture ?

2007-07-10 Thread Andrew Lunn
On Tue, Jul 10, 2007 at 05:02:12PM +0200, Alexandre wrote: > Okay i seem to have identified the problem and narrowed it down again. > The modification on the PINSEL1 register init now enables me to debug > eCos properly IF i don't use the function cyg_thread_delay(). > For some obscure reason this

Re: [ECOS] Re: eCos invalidating JTAG on ARM architecture ?

2007-07-10 Thread Alexandre
Okay i seem to have identified the problem and narrowed it down again. The modification on the PINSEL1 register init now enables me to debug eCos properly IF i don't use the function cyg_thread_delay(). For some obscure reason this particular function seems to deactivate the JTAG definitely (JTAG1

Re: [ECOS] Re: eCos invalidating JTAG on ARM architecture ?

2007-07-10 Thread Andrew Lunn
On Tue, Jul 10, 2007 at 11:56:12AM +0200, Alexandre wrote: > Ok I implemented that and it enabled me to know what in vectors.S was > disabling JTAG. Ironically, i shortened it to the "bl cyg_start" > instruction at the end of the "start:" label (last instruction for > this label i think). > > I fin

Re: [ECOS] Re: eCos invalidating JTAG on ARM architecture ?

2007-07-10 Thread Alexandre
Ok I implemented that and it enabled me to know what in vectors.S was disabling JTAG. Ironically, i shortened it to the "bl cyg_start" instruction at the end of the "start:" label (last instruction for this label i think). I find it weird because it would mean the launch of the actual kernel soft