[ECOS] RedBoot and eCos application both using the same network port

[Jonathan Larmour]

Chris Garry wrote:
>>From the archive I believe that RedBoot and eCos may share a network
> port if they have different IP addresses assigned.
> 
> When I try this on the E7T, the board locks up as soon as the eCos
> application begins to run.  What is actually causing the problem is a
> line in the ks32c5000 ethernet driver (in the installInterrupts() function)
> which writes to the BDMARXPTR register in the ethernet controller.
> This breaks things since GDB is already talking to the board through the
> network port.
> 
> Does the ks32c5000 eth driver need to be updated to prevent this from
> happening when RedBoot has already set up the ethernet controller?
> 
> Or am I missing something?

Well, what's meant to happen in the case of both RedBoot and eCos sharing 
an ethernet device is that RedBoot sets up the eth driver for itself. Then 
eCos sets it up again with its own eth driver, but when the eCos code 
receives a packet, common stuff in io/eth/current/src/net/eth_drv.c does a 
check for if it was a "ctrl-c", and if so hal_ctrlc_check in 
hal/common/current/src/hal_if.c sets a breakpoint and we enter RedBoot. 
When RedBoot sends a packet, magic in eth_drv_send() in eth_drv.c also 
ensures the right stuff happens.

But the point is, when eCos takes over, RedBoot will use the *eCos* driver 
for its debug.

Now the only exception to all this is if you're trying to debug the 
ethernet driver itself while debugging over ethernet. If that's what 
you're doing, my response is.... don't ;-).

Jifl
-- 
eCosCentric    http://www.eCosCentric.com/    The eCos and RedBoot experts
--[ "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