Re: [ECOS] and another thing ..

Re: [ECOS] and another thing ..

[Laurie.Gellatly]

Using configtool, if you DON'T config to build Redboot, then libtarget gets
built instead.
I have a redboot.ecc and a mydev.ecc.
mydev.ecc has the libtarget in it and all the ecos packages my device needs.
Its also setup to 'Work with a rom monitor' as redboot is used to load and
run my app. 
You can use GDB with a remote target to connect to redboot and load/debug
your app.

...Laurie:{)

--------- Original Message --------
From: Chuck McManis <ecos@mcmanis.com>
To: ECOS Discussion Group <ecos-discuss@sources.redhat.com>
Subject: [ECOS] and another thing ..
Date: 21/02/07 02:46

> So I can't easily gdb this from a terminal (Hmm, I might be able to on the

> terminal server, should try that next). To compile libtarget.a -g is there

> a config option? CYG_MAKE_THIS_STUFF_DEBUGGABLE or something? Clearly a 
> network debug stops as soon as the interface gets re-initialized.
> 
> --Chuck
> 
> 
> -- 
> Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
> 
> 

________________________________________________
Message sent using UebiMiau 2.7.9



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

Re: [ECOS] and another thing ..

[Chuck McManis]

At 07:52 PM 2/21/2007, Laurie.Gellatly wrote:

>Using configtool, if you DON'T config to build Redboot, then libtarget gets
>built instead.


Yes, this I am familiar with. I've got a directory (redboot-epia that 
builds redboot and a directory epia-ecos that builds libtarget.a. And by 
setting CFLAGS I can in fact have it build -g. So that is all good.

Another bit of information is that watching my DHCP logs I see that when 
the program starts DHCP is getting the request for an IP address and it 
"offers" 192.168.110.123. (the mac actually changes so its not confused by 
this, in my redboot setup I was pre-setting the mac, hmmm I could try that 
here too)

But what seems to be happening is that it responds with the offer and the 
target board doesn't see it. This is reminescent of an earlier problem I 
had with redboot and DHCP/BOOTP but I fixed it there and it seems to be 
here. Almost like my nic card is not seeing any received packets.

Hmm, back to the painful printf process it looks like. I can actually 
attach to the board through the terminal server to the serial port (9600 
baud max, its an old terminal server) but the server cannot deal with gdb 
slamming so much data through it, it gets corrupted packets.

Thanks for the response though! I'll keep plugging away

--Chuck



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

Re: [ECOS] and another thing ..

[Laurie.Gellatly]

The MAC changes - interesting.
So your NIC supports working with two MACs simultaneously?
You might try by simplifying things and keeping just the one MAC and having
it support two IPs which I know works.
Why do you want both Redboot and your app to be DHCP?
Again, I'd look to nail these to some static addresses to get you started
and then make it fancier later.

...Laurie:{)

--------- Original Message --------
From: Chuck McManis <cmcmanis@mcmanis.com>
To: Laurie.Gellatly <laurie.gellatly@netic.com>, Chuck McManis
<ecos@mcmanis.com>, ECOS Discussion Group <ecos-discuss@sources.redhat.com>
Subject: Re: [ECOS] and another thing ..
Date: 21/02/07 03:05

> At 07:52 PM 2/21/2007, Laurie.Gellatly wrote:
> 
> &gt;Using configtool, if you DON'T config to build Redboot, then libtarget
gets
> &gt;built instead.
> 
> 
> Yes, this I am familiar with. I've got a directory (redboot-epia that 
> builds redboot and a directory epia-ecos that builds libtarget.a. And by 
> setting CFLAGS I can in fact have it build -g. So that is all good.
> 
> Another bit of information is that watching my DHCP logs I see that when 
> the program starts DHCP is getting the request for an IP address and it 
> &quot;offers&quot; 192.168.110.123. (the mac actually changes so its not
confused by 
> this, in my redboot setup I was pre-setting the mac, hmmm I could try that

> here too)
> 
> But what seems to be happening is that it responds with the offer and the 
> target board doesn't see it. This is reminescent of an earlier problem I 
> had with redboot and DHCP/BOOTP but I fixed it there and it seems to be 
> here. Almost like my nic card is not seeing any received packets.
> 
> Hmm, back to the painful printf process it looks like. I can actually 
> attach to the board through the terminal server to the serial port (9600 
> baud max, its an old terminal server) but the server cannot deal with gdb 
> slamming so much data through it, it gets corrupted packets.
> 
> Thanks for the response though! I'll keep plugging away
> 
> --Chuck
> 
> 
> 
> -- 
> Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
> 
> 

________________________________________________
Message sent using UebiMiau 2.7.9



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

Re: [ECOS] and another thing ..

[Chuck McManis]

At 08:21 PM 2/21/2007, you wrote:
>The MAC changes - interesting.
>So your NIC supports working with two MACs simultaneously?
>You might try by simplifying things and keeping just the one MAC and having
>it support two IPs which I know works.
>Why do you want both Redboot and your app to be DHCP?
>Again, I'd look to nail these to some static addresses to get you started
>and then make it fancier later.

Well as I expected hard coding the address didn't really change anything. 
Basically I'm not seeing any of the response packets. So I went back to my 
old notes from a year ago where I had a similar issue with Redboot and 
there were issues with enabling the CRC checking / generation which I've 
confirmed are not the issue here.

Sigh, time to match Ethereal traces with debugging output and try to narrow 
down where things go wrong. I suppose the good news is that when I use DHCP 
the DHCP server *is* seeing the transmitted packets so I can contentrate 
primarily on the receiver. It does complain about not being able to set 
multicast but I don't think that is a real problem. I'll know after I dig 
into the traces more thoroughly. Hmm, I suppose I could dig up my old Intel 
board as well and see if that board had similar issues. Another avenue to 
try ...

--Chuck


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

RE: [ECOS] and another thing ..

[Laurie Gellatly]

Have you set the ethernet chip to receive boradcasts as well as unicasts or
any
other such filtering?

			...Laurie:{)

-----Original Message-----
From: Chuck McManis [mailto:ecos@mcmanis.com]
Sent: Thursday, 22 February 2007 5:30 PM
To: ECOS Discussion Group
Cc: Laurie.Gellatly
Subject: Re: [ECOS] and another thing ..


At 08:21 PM 2/21/2007, you wrote:
>The MAC changes - interesting.
>So your NIC supports working with two MACs simultaneously?
>You might try by simplifying things and keeping just the one MAC and having
>it support two IPs which I know works.
>Why do you want both Redboot and your app to be DHCP?
>Again, I'd look to nail these to some static addresses to get you started
>and then make it fancier later.

Well as I expected hard coding the address didn't really change anything.
Basically I'm not seeing any of the response packets. So I went back to my
old notes from a year ago where I had a similar issue with Redboot and
there were issues with enabling the CRC checking / generation which I've
confirmed are not the issue here.

Sigh, time to match Ethereal traces with debugging output and try to narrow
down where things go wrong. I suppose the good news is that when I use DHCP
the DHCP server *is* seeing the transmitted packets so I can contentrate
primarily on the receiver. It does complain about not being able to set
multicast but I don't think that is a real problem. I'll know after I dig
into the traces more thoroughly. Hmm, I suppose I could dig up my old Intel
board as well and see if that board had similar issues. Another avenue to
try ...

--Chuck


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

[ECOS] and another thing ..

[Chuck McManis]

So I can't easily gdb this from a terminal (Hmm, I might be able to on the 
terminal server, should try that next). To compile libtarget.a -g is there 
a config option? CYG_MAKE_THIS_STUFF_DEBUGGABLE or something? Clearly a 
network debug stops as soon as the interface gets re-initialized.

--Chuck


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