On Tue, Jun 3, 2014 at 8:16 AM, Peter Dufault wrote:
> I tried to figure out why I don't see any issues during normal debugging when
> I set breakpoints and then start GDB, I only have a problem when I hit ^C to
> enter GDB. Since bsp_idle_thread() is unusual in that the generated code has
> no
I tried to figure out why I don't see any issues during normal debugging when I
set breakpoints and then start GDB, I only have a problem when I hit ^C to
enter GDB. Since bsp_idle_thread() is unusual in that the generated code has no
return from subroutine:
0006ef44 :
6ef44: 48 00 00 00
On Jun 2, 2014, at 02:54 , Sebastian Huber
wrote:
>
> Maybe the debugger has a problem with the wait instruction?
>
This is the MPC5554 and the wait instruction is only implemented on the 567X
family (at least in our BSP).
I stumbled on something. If I disconnect the ethernet it will work
On 2014-05-30 15:03, Peter Dufault wrote:
On the Phytec MPC5554 with the current head as of yesterday I'm having funny
problems with GDB and the McGraigor wiggler. I don't need to use this setup
that often so everything has changed since I last used it: GCC, GDB, RTEMS, the
version of Linux,
