This is the mail archive of the ecos-discuss@sources.redhat.com mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

peculiar RedBoot network problem


I run my programs over the network using RedBoot.  RedBoot is set to use
the ip 172.16.1.240.  My eCos application is set to get an IP using
DHCP.  It gets an ip of 172.16.1.11.  Now, I ran my eCos program from
RedBoot, and now a reset of the board does not reset the IP to
172.16.1.240.  It's almost as if the eCos application has taken over
some how.  Of course RedBoot doesn't listen on 172.16.1.11 so I can't do
a GDB connection to there.  Also, running fconfig through a serial port
shows that 172.16.1.240 is in fact the IP RedBoot is setup for.

Any ideas why this might happen?  I've been running eCos programs with
network support enabled for the past day using the network GDB of
RedBoot and this hasn't occurred until now.
 
Trenton D. Adams
Embedded Developer
Windows Developer
Extreme Engineering Ltd.
Calgary Alberta.




Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]