RE: [ECOS] How to disable GDB STUBS?

RE: [ECOS] How to disable GDB STUBS?

[Agarwal, Lomesh]

I changed inferred value to user value and now inferrence engine is
getting conflicts. Here is the output:

U CYGHWR_HAL_ARM_DUMP_EXCEPTIONS, new inferred value 0
U CYGDBG_HAL_DEBUG_GDB_INCLUDE_STUBS, new inferred value 1
U CYGDBG_HAL_COMMON_CONTEXT_SAVE_MINIMUM, new inferred value 0
C CYGBLD_BUILD_REDBOOT, "requires" constraint not satisfied:
!CYGINT_HAL_DEBUG_GDB_STUBS || CYGDBG_
HAL_DEBUG_GDB_INCLUDE_STUBS
C CYGBLD_BUILD_REDBOOT, "requires" constraint not satisfied:
!CYGINT_HAL_DEBUG_GDB_STUBS || CYGDBG_
HAL_DEBUG_GDB_BREAK_SUPPORT
C CYGBLD_BUILD_REDBOOT, "requires" constraint not satisfied:
!CYGINT_HAL_DEBUG_GDB_STUBS || CYGDBG_
HAL_DEBUG_GDB_INCLUDE_STUBS
C CYGBLD_BUILD_REDBOOT, "requires" constraint not satisfied:
!CYGINT_HAL_DEBUG_GDB_STUBS || CYGDBG_
HAL_DEBUG_GDB_BREAK_SUPPORT

Unable to generate build tree, this configuration still contains
conflicts.
Either resolve the conflicts or use --ignore-errors
make: *** No targets specified and no makefile found.  Stop.

Any suggestions?

Thanks,
Lomesh

-----Original Message-----
From: Bart Veer [mailto:bartv@ecoscentric.com] 
Sent: Tuesday, November 05, 2002 1:35 PM
To: Agarwal, Lomesh
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] How to disable GDB STUBS?


>>>>> "Lomesh" == Agarwal, Lomesh <lomesh.agarwal@intel.com> writes:

    Lomesh> In my redboot_ROM.ecm file I added an entry:
    Lomesh> cdl_option CYGDBG_HAL_DEBUG_GDB_INCLUDE_STUBS {
    Lomesh>     inferred_value 0
    Lomesh> };
    Lomesh> But still all the code under #ifdef
    Lomesh> CYGDBG_HAL_DEBUG_GDB_INCLUDE_STUBS is getting compiled.
    Lomesh> How can I undef it?

Part of the problem may be that the inference engine is changing the
value of this option again. "inferred_value" should be used only for
options that were updated by the inference engine to resolve some
conflict in the configuration. If there are still conflicts in the
configuration then the engine is allowed to reset the value to 1, if
that solves the problem(s).

Instead you should be using a user_value:

    cdl_option CYGDBG_HAL_DEBUG_GDB_INCLUDE_STUBS {
        user_value 1
    }

The inference engine will not override user settings. If there are
conflicts it will try to resolve them some other way, or report the
configuration as invalid.

Bart

--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

Re: [ECOS] How to disable GDB STUBS?

[Bart Veer]

>>>>> "Lomesh" == Agarwal, Lomesh <lomesh.agarwal@intel.com> writes:

    Lomesh> I changed inferred value to user value and now inferrence engine is
    Lomesh> getting conflicts. Here is the output:

    Lomesh> U CYGHWR_HAL_ARM_DUMP_EXCEPTIONS, new inferred value 0
    Lomesh> U CYGDBG_HAL_DEBUG_GDB_INCLUDE_STUBS, new inferred value 1
    Lomesh> U CYGDBG_HAL_COMMON_CONTEXT_SAVE_MINIMUM, new inferred value 0
    Lomesh> C CYGBLD_BUILD_REDBOOT, "requires" constraint not satisfied:
    Lomesh> !CYGINT_HAL_DEBUG_GDB_STUBS || CYGDBG_
    Lomesh> HAL_DEBUG_GDB_INCLUDE_STUBS
    Lomesh> C CYGBLD_BUILD_REDBOOT, "requires" constraint not satisfied:
    Lomesh> !CYGINT_HAL_DEBUG_GDB_STUBS || CYGDBG_
    Lomesh> HAL_DEBUG_GDB_BREAK_SUPPORT

    Lomesh> Unable to generate build tree, this configuration still contains
    Lomesh> conflicts.
    Lomesh> Either resolve the conflicts or use --ignore-errors
    Lomesh> make: *** No targets specified and no makefile found.  Stop.

    Lomesh> Any suggestions?

Looking at the CDL constraints, the configuration you are after
(RedBoot without gdb stubs) is not currently supported. If you want to
build RedBoot (CYGBLD_BUILD_REDBOOT) and if the architectural HAL (or
possibly variant or platform HAL) provides the necessary support
(CYGINT_HAL_DEBUG_GDB_STUBS) then the generic stubs code in the
common HAL package (CYGDBG_HAL_DEBUG_GDB_INCLUDE_STUBS) is needed.

Changing this would require modifications to RedBoot itself, and
appropriate adjustments to the CDL. These would probably take the form
of a new RedBoot configuration option or component that controls
whether or not RedBoot should be built with gdb stubs functionality.
The requires constraint could then be moved from CYGBLD_BUILD_REDBOOT
to the new option, and the user could then disable that option. I do
not know how much of RedBoot would be affected by such a change.

Bart

-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

Re: [ECOS] How to disable GDB STUBS?

[Iztok Zupet]

On Wednesday 06 November 2002 23:18, Bart Veer wrote:
> Looking at the CDL constraints, the configuration you are after
> (RedBoot without gdb stubs) is not currently supported. If you want to

I've noticed a kind of cyclic dependancy in CDL constraints regarding stubs, 
preventing tham beeing disabled. But I'd like to know the trick to debug the 
RedBoot startup code with RedBoot if it exists?

Iztok

-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

Re: [ECOS] How to disable GDB STUBS?

[Nick Garnett]

Iztok Zupet <iztok.zupet@vsr.si> writes:

> On Wednesday 06 November 2002 23:18, Bart Veer wrote:
> > Looking at the CDL constraints, the configuration you are after
> > (RedBoot without gdb stubs) is not currently supported. If you want to
> 
> I've noticed a kind of cyclic dependancy in CDL constraints regarding stubs, 
> preventing tham beeing disabled. But I'd like to know the trick to debug the 
> RedBoot startup code with RedBoot if it exists?
> 

There's no trick, you have to do it the hard way. This usually means
flashing LEDs or using assembly code to poke bytes out of a serial
port. Once the HAL serial drivers are initialized properly, then you
can use diag_printf()'s to find out what's happening. Most network
drivers have optional diagnostic output that can be turned on.

If RedBoot is working sufficiently that you can use it for
debugging something then, almost by definition, the startup code must
be working. Also, since RedBoot usually goes into ROM, there is not
much that can be done in the way of setting breakpoints or single
stepping.

-- 
Nick Garnett - eCos Kernel Architect
http://www.eCosCentric.com/

-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

Re: [ECOS] How to disable GDB STUBS?

[Bart Veer]

>>>>> "Lomesh" == Agarwal, Lomesh <lomesh.agarwal@intel.com> writes:

    Lomesh> In my redboot_ROM.ecm file I added an entry:
    Lomesh> cdl_option CYGDBG_HAL_DEBUG_GDB_INCLUDE_STUBS {
    Lomesh>     inferred_value 0
    Lomesh> };
    Lomesh> But still all the code under #ifdef
    Lomesh> CYGDBG_HAL_DEBUG_GDB_INCLUDE_STUBS is getting compiled.
    Lomesh> How can I undef it?

Part of the problem may be that the inference engine is changing the
value of this option again. "inferred_value" should be used only for
options that were updated by the inference engine to resolve some
conflict in the configuration. If there are still conflicts in the
configuration then the engine is allowed to reset the value to 1, if
that solves the problem(s).

Instead you should be using a user_value:

    cdl_option CYGDBG_HAL_DEBUG_GDB_INCLUDE_STUBS {
        user_value 1
    }

The inference engine will not override user settings. If there are
conflicts it will try to resolve them some other way, or report the
configuration as invalid.

Bart

-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

RE: [ECOS] How to disable GDB STUBS?

[Agarwal, Lomesh]

Jifi,
You mean I should put something like this in my ecm file:
cdl_option CYGDBG_HAL_DEBUG_GDB_INCLUDE_STUBS {
    user_value 0
};
In place of
cdl_option CYGDBG_HAL_DEBUG_GDB_INCLUDE_STUBS {
    inferred_value 0
};
Right?

Thanks,
Lomesh

-----Original Message-----
From: Jonathan Larmour [mailto:jifl@eCosCentric.com] 
Sent: Tuesday, November 05, 2002 1:24 PM
To: Gary Thomas
Cc: Agarwal, Lomesh; eCos Discussion
Subject: Re: [ECOS] How to disable GDB STUBS?


Gary Thomas wrote:
> On Tue, 2002-11-05 at 12:36, Agarwal, Lomesh wrote:
> 
>>I have ported RedBoot to my custom board. I am using it to load Linux
>>and to manage flash binaries. I don't need any GDB support for my
>>platform. But when user types + or $ it goes into GDB stuff and hangs.
>>So, I was thinking it to remove completely so that it doesn't hang.
>>
> 
> 
> More properly, just use the CLI the way it's designed.  If you need
> to type a "+" or "$", escape them.  For example:

I think disabling included stubs should still work though. There are 
ifdefs in redboot exactly to catch this. Lomesh should disable the
option 
with user_value 0 by editing the CYGDBG_HAL_DEBUG_GDB_INCLUDE_STUBS
option 
in the ecos.ecc file _after_ doing the import of the .ecm file.

Jifl
-- 
eCosCentric       http://www.eCosCentric.com/
<info@eCosCentric.com>
--[ "You can complain because roses have thorns, or you ]--
--[  can rejoice because thorns have roses." -Lincoln   ]--
Opinions==mine

--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

Re: [ECOS] How to disable GDB STUBS?

[Jonathan Larmour]

Gary Thomas wrote:
> On Tue, 2002-11-05 at 12:36, Agarwal, Lomesh wrote:
> 
>>I have ported RedBoot to my custom board. I am using it to load Linux
>>and to manage flash binaries. I don't need any GDB support for my
>>platform. But when user types + or $ it goes into GDB stuff and hangs.
>>So, I was thinking it to remove completely so that it doesn't hang.
>>
> 
> 
> More properly, just use the CLI the way it's designed.  If you need
> to type a "+" or "$", escape them.  For example:

I think disabling included stubs should still work though. There are 
ifdefs in redboot exactly to catch this. Lomesh should disable the option 
with user_value 0 by editing the CYGDBG_HAL_DEBUG_GDB_INCLUDE_STUBS option 
in the ecos.ecc file _after_ doing the import of the .ecm file.

Jifl
-- 
eCosCentric       http://www.eCosCentric.com/       <info@eCosCentric.com>
--[ "You can complain because roses have thorns, or you ]--
--[  can rejoice because thorns have roses." -Lincoln   ]-- Opinions==mine


-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

RE: [ECOS] How to disable GDB STUBS?

[Gary Thomas]

On Tue, 2002-11-05 at 12:36, Agarwal, Lomesh wrote:
> I have ported RedBoot to my custom board. I am using it to load Linux
> and to manage flash binaries. I don't need any GDB support for my
> platform. But when user types + or $ it goes into GDB stuff and hangs.
> So, I was thinking it to remove completely so that it doesn't hang.
> 

More properly, just use the CLI the way it's designed.  If you need
to type a "+" or "$", escape them.  For example:

    RedBoot> \+ this is a test
    ** Error: Illegal command: "+"
    RedBoot> \$ this is also
    ** Error: Illegal command: "$"

BTW - your platform isn't hanging - it's waiting for GDB commands.

-- 
------------------------------------------------------------
Gary Thomas                  |
eCosCentric, Ltd.            |  
+1 (970) 229-1963            |  eCos & RedBoot experts
gthomas@ecoscentric.com      |
http://www.ecoscentric.com/  |
------------------------------------------------------------


-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

RE: [ECOS] How to disable GDB STUBS?

[Agarwal, Lomesh]

I have ported RedBoot to my custom board. I am using it to load Linux
and to manage flash binaries. I don't need any GDB support for my
platform. But when user types + or $ it goes into GDB stuff and hangs.
So, I was thinking it to remove completely so that it doesn't hang.

-----Original Message-----
From: Gary Thomas [mailto:gthomas@ecoscentric.com] 
Sent: Tuesday, November 05, 2002 11:25 AM
To: Agarwal, Lomesh
Cc: eCos Discussion
Subject: Re: [ECOS] How to disable GDB STUBS?


On Tue, 2002-11-05 at 12:21, Agarwal, Lomesh wrote:
> In my redboot_ROM.ecm file I added an entry:
> cdl_option CYGDBG_HAL_DEBUG_GDB_INCLUDE_STUBS {
>     inferred_value 0
> };
> But still all the code under #ifdef CYGDBG_HAL_DEBUG_GDB_INCLUDE_STUBS
> is getting compiled. How can I undef it?

Why would you want to disable the GDB stubs in RedBoot?

-- 
------------------------------------------------------------
Gary Thomas                  |
eCosCentric, Ltd.            |  
+1 (970) 229-1963            |  eCos & RedBoot experts
gthomas@ecoscentric.com      |
http://www.ecoscentric.com/  |
------------------------------------------------------------

--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

Re: [ECOS] How to disable GDB STUBS?

[Gary Thomas]

On Tue, 2002-11-05 at 12:21, Agarwal, Lomesh wrote:
> In my redboot_ROM.ecm file I added an entry:
> cdl_option CYGDBG_HAL_DEBUG_GDB_INCLUDE_STUBS {
>     inferred_value 0
> };
> But still all the code under #ifdef CYGDBG_HAL_DEBUG_GDB_INCLUDE_STUBS
> is getting compiled. How can I undef it?

Why would you want to disable the GDB stubs in RedBoot?

-- 
------------------------------------------------------------
Gary Thomas                  |
eCosCentric, Ltd.            |  
+1 (970) 229-1963            |  eCos & RedBoot experts
gthomas@ecoscentric.com      |
http://www.ecoscentric.com/  |
------------------------------------------------------------


-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

[ECOS] How to disable GDB STUBS?

[Agarwal, Lomesh]

In my redboot_ROM.ecm file I added an entry:
cdl_option CYGDBG_HAL_DEBUG_GDB_INCLUDE_STUBS {
    inferred_value 0
};
But still all the code under #ifdef CYGDBG_HAL_DEBUG_GDB_INCLUDE_STUBS
is getting compiled. How can I undef it?

Thanks,
Lomesh

--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss