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]
Other format: [Raw text]

Re: crash in tftp_client_test.c


On Sat, Apr 26, 2003 at 11:04:15AM -0400, HG wrote:
> Hi All,
> 
> I found out what was causing the problem in the previously reported problems
> with that test program . It might be useful to others on the list that bring
> up new boards.
> 
> It appears that the interrupts where not set correctly. The
> hal_intc_translation_table in variant.inc did not route all the interrupts
> correctly (some but not all) . The HAL_PCI_TRANSLATE_INTERRUPT was not
> routing the interrupts to the correct vector for that pci chip. The
> experimental observations of the problem where confusing.

Can you contribute a patch? 

> retesting for file sizes of 255k and 1 Meg usually works except in the
> following circumstances : when an other computer on the network (an NT
> workstation ) issues udp to the broadcast address of computers on the
> network the ecos application crashes (see trace below) . This is viewed by
> dumps of the udp activity and also by viewing the logic analyser : when the
> app hangs , the service request from the 82559 stays low until the board is
> reset.
> 
> is there any ecos application ,  package ,  enhancement , workaround to
> improve the robustness of the tftp program?

Its not the tftp program thats at fault. Its probably your HAL or the
ethernet device driver. You need to debug this further to see what is
going on. It's is not a problem anyone else has seen before, so there
is no package, enhancement, workaround etc.....

How old is the redboot on your device? A year ago there was a problem
with NTP Broadcast's killing redboot, but i expect you have a more
recent version.

I would try reproducing the problem with a low bandwidth test, eg
pings. Once you can get the system crashing with this, then put some
breakpoints in which are called when broadcast packets are received
and then trace it through to see why it crashes.

    Andrew

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


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