Hi,
On Mon, May 28, 2012 at 05:04:54PM +0200, Stanislav Meduna wrote:
> On 19.05.2012 16:49, Paul Fertser wrote:
> > Basically, if you can load the elf file in gdb and you can "print" the
> > needed variable, then OpenOCD has access to it too (because it
> > basically asks gdb for the offset of a
On 19.05.2012 16:49, Paul Fertser wrote:
> Basically, if you can load the elf file in gdb and you can "print" the
> needed variable, then OpenOCD has access to it too (because it
> basically asks gdb for the offset of a variable it needs).
Hm, correct me if I'm wrong: I investigated a bit and I'm
Hi,
On Sat, May 19, 2012 at 02:50:30PM +0200, Stanislav Meduna wrote:
> (it depends on what symbols the OpenOCD has an access to),
Basically, if you can load the elf file in gdb and you can "print" the
needed variable, then OpenOCD has access to it too (because it
basically asks gdb for the offse
Hi everybody,
I'm afraid the current method of thread awareness for eCos
cannot reliably work as implemented.
The eCos_params_list in src/rtos/eCos.c contains fixed
offsets for a few fields.
const struct eCos_params eCos_params_list[] = {
{
"cortex_m3", /* target_name */
4,/* po
