Hi Alan,
Yes - this is a bug - probably a cut&paste error.
It looks like, as you say, that there are two errors cancelling out.
The target_read_buffer() function should reference the address variable.
If you need an explanation of any parts of the code, let me know.
You will probably find that eCos stacks register in the same order
that FreeRTOS and ThreadX do on the Cortex-M3 platform. If that is
the case, all you need to do is to implement the reading of the eCos
thread list(s).
Regards,
Evan Hunter
Quoting Alan Bowman <alan.michael.bow...@gmail.com>:
I'm looking through the new RTOS/thread code, with a view to adding
eCos/Cortex-M3 support (if time and hardware allow) and I'm a bit
confused by a section in src/rtos/rtos.c. In
rtos_generic_stack_read():534, address is modified by the size of the
stacked register set (having been set to the value of the stack_ptr).
However, it is never used from that point on. Since this is a section
of code that appears to be used by FreeRTOS/ThreadX I assume that it
works, or they both have their stack growth direction set incorrectly
and the two errors cancel out. Can anyone clarify?
I think that line 536 should use address, rather than stack_ptr as the
lookup address, but this would seem to break the existing examples.
Cheers
Alan
_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
