JTAG debug real-time trouble

Follow

mario sangalli

• July 06, 2012 14:50

Hi, I've found that the debug under Crossworks seems to freeze the execution for about 50/100ms every 2sec.

I'm using a LPX24XX based board and the ROWLEY USB JTAG or the Olimex USB TINY one, with same execution

suspension using a PC in Windows XP env..

Someone has experienced such trouble?

It's a problem of PC USB, the  JTAG or its the debugger software that suspend cyclically the CPU?

There is a workaround to avoid the suspension?

Thanks,

M. Sangalli

0

• 

  Richard Webb

  • July 09, 2012 13:47

  Not seeing anything like that here, nor have I in any of the projects I've done with CrossWorks under the debugger.

  Just threw together a quick LPC2103 app that toggles a pin every msec and set a logic analyzer to trigger if the pin held a value of 1 or 0 for longer than 1.01 msec. As expected, it never triggered.

  Is it possible that you're experiencing a watchdog reset? I have (confession time) once or twice mis-configured a watchdog and then spent far too much time tracking down the "problem."

  0

  Comment actions Permalink
• 

  mario sangalli

  • July 09, 2012 14:30

  I have had my problems using the watchdog :-)

  But is not the problem here ... The problem is evidenced under an application

  running under freeRtos .... and when interrupts are running.

  No problems in toggling IO port pin in a thread, that works fine:

  But I' ve also some serials working in RS485: I've to change direction at the end of Tx

  frame as fast as possible... and here the trouble comes. Just every 2seconds , all

  seeems to freeze and monitoring RS485 direction I've noted a delay of 50/100ms....

  If I detach JTAG, all works rigth...  It is a hassle to try to understand where the problem is,

  and I will hope that is just a debugger/JTAG problem and not some other malfunction in

  my sw :-)

  M.Sangalli

   

   

   

  0

  Comment actions Permalink
• 

  Royce Arnold

  • July 09, 2012 14:59

  An idea....

  Have you checked the refresh rate (the drop down list) of your Watch windows.  If it is not set to 'Never', I believe Crossworks will poll the memory even if the processor is not in a stopped state.  That might cause what you are seeing as it would have to temporary interrupt normal processor operation to read the memory.

  RA

  0

  Comment actions Permalink
• 

  mario sangalli

  • July 11, 2012 15:50

  It was that... the refresh rate was set  to 2sec!

  Thank You

  MS

  0

  Comment actions Permalink

Please sign in to leave a comment.