Target Observability- target not connected

Miscellaneous

Outline another way that Target Observability communication chain can be incomplete.

Users of Target Observability on targets that have ethernet setup

ObjecTime 5.0

Target Observability was not working because the host workstation running ObjecTime had two network cards installed and the target board was not configured properly.

There was a main network for host workstations and a sub-network for various target boards. When the target board was initially booted it was configured as follows:

boot> inet address of target?  
boot> inet address of host to boot from?  
boot> inet address of gateway?  

This target board configuration allowed the ObjecTime executable to be successfully downloaded and the target debug agent to start. Communication from the host to the target succeeded. Communication, across the ethernet, from the target to the host failed. (Serial communication from target to host was unaffected, of course.) This resulted in ObjecTime reporting 'target not connected' and 'Navigator View: target not responding'.

When the following settings were used Target Observability worked.

boot> inet address of target? 
boot> inet address of host to boot from? 
boot> inet address of gateway? 

Only applies to target boards with ethernet and the capability to communicate with a host which is on a different network than the target board.

Hardware configuration setup for your specific target hardware dealing with ethernet setup, specifically information relating to the situation when your target in on a different network than the host with which you are attempting to communicate.