Known Released Issues 6.3 
 

          These are the known defects in this release of NET+Works:


Known Issue:

The DHCP client is limited to no more than 50 DHCP options in the Vendor specific section of any DHCP packet. This includes inbound and outbound packets. This can occur if the server sends too many options, or if the client requests too many. [11488]

Workaround:

This can be corrected on the server by configuring the server to send fewer options. This can be corrected on the client by not requesting more than 50 options in the desired_params member, of the configAceDhcpInfo structure, inside the NADefaultEthInterfaceConfig structure. 


Known Issue: 

GNU/C++ Exception Handling is not thread safe. Thus using the try-throw-catch keywords within multiple threads may cause instabilities, including data aborts or data corruption. [13620]

Workaround:

To avoid this condition, GNU/C++ applications should avoid these native language constructs and instead use classic C style handling of exceptional conditions. 


Known Issue: 

It has been reported, intermittently, after typing a password or an IP address in the serial dialog that the following line of output from the unit will not appear on the display. [13691]

Workaround:

Note the only known workaround is to recycle power and restart if this prevents further operation.


Known Issue: 

The Cygwin file fcntl.h defines O_NONBLOCK as 0x4000. NET+OS, however, defines it (in serParams.h and mqueue.h) as 0x20.  This can cause serial channels to inadvertently act in blocking mode, and thus cause application failures. [13860]

Workaround:

This can be corrected by either not using the fcntl.h header in NET+OS serial application files, or if the header is required, hardcoding the value directly. 


Known Issue: 

On the NS9750. when using PCI devices with bus master capability, PCI device memory cycles have failed when the PCI_EXPOSE_LOCAL_MEMORY ioctl exposed segments and translated the address (for instance, the pci_localMap_t localAddress and the pciAddress did not match). [14493]

Workaround:

Note this can be avoided by exposing the full memory map (starting at RAM address 0) and exposing address 0 in the localAddress and pciAddress members. 


Known Issue: 

The I/O control SIO_TERM_ECHO, from the legacy serial API will drop characters intermittently, thus not return the proper serial ECHO under all conditions on the NS9750. [15132]

Workaround:

Instead, a simple ECHO server should be implemented using the read() and write() calls, directly. 


Known Issue: 

If the NET+Works software is loaded on a Windows 2003 Server, the Raven OCDRemote 2.10 SW can be unstable. [15254]

Workaround:

Note the Windows 2003 Server is not a supported platform. This problem does not occur on the any of the support NET+Works platforms. 


Known Issue: 

Using a GNU bt (backtrace) command can cause warnings and lead to unstable behavior. [15383]

Workaround:

This problem does not occur when using the View-Stack feature of the Visual GDB window, launched by the GNU gdbtk command. 


Known Issue: 

The Address Conflict Detection (ACD) software, by default, is setup to use AUTO-IP in the case of an address conflict detection. This will occur even if AUTO-IP is disabled in ACE. [15384]

Workaround:

Note this can be changed in the customization files. 


Known Issue: 

Execution may continue to free run in a debugged image, after exiting the Raven debugger, using GNU on an NS7520. [15523]

Workaround:

To prevent this condition, always recycle power on the board immediately after exiting the debugger. 


Known Issue: 

The USB host class driver software, provided with NET+Works 6.3, will only interoperate with USB 1.1 hubs, even though the NS9360 and NS9750 can support USB 2.0 Hubs. [15542]

No Workaround


Known Issue: 

Under extreme and abusive conditions, TCP/IP low memory conditions can occur causing the sockets API functions select() and recvfrom() (with the MSG_PEEK flag set) to indicate data is available, but a subsequent call to recvfrom() may have no data. In the case where this is a blocking socket, the recvfrom() call could erroneously block. [15609]

Workaround:

Note this condition is extremely rare, is theoretical in nature, and has never been observed. To avoid this, either use non-blocking socket calls or allocate more memory for APP_NET_HEAP_SIZE than expected to use. Alternatively, use of the watchdog timer and links to critical threads can be used to reset a unit once this deadlocked condition is detected. 


Known Issue: 

All wireless units, under heavy use, can quickly enter the TCP/IP low memory condition. [16220]

Workaround:

To avoid this, allocate as much system memory for APP_NET_HEAP_SIZE as possible. 


Known Issue: 

When debugging ARM9-based applications with the Raven debugger, stepping over (Next) assembly branch instructions causes a disconnect between the gdb and the target. Stepping in (Step) or stepping out (Finish) does work fine. [15610]

Workaround:

To avoid debugger disconnects, do not use step over when on a branch instruction. 


Known Issue: 

NET+Works SSL contains interoperability issues with some DIGI box product servers.[15617]

No Workaround


Known Issue: 

The File System utility function ftell() is not implemented.  The lack of the ftell() utility function eliminates the usefulness of fseek(). [15875]

No Workaround


Known Issue: 

Multiple -cpu definitions will occur when converting a legacy.bld build file to a .gpj format, using the GHS 4.0.5 conversion utility. [15999]

Workaround:

To correct this, hand edit the .gpj file and remove the second -cpu definition. (This is documented as a part of the legacy conversion procedure described in 16004 above.) 


Known Issue: 

NET+Works SSL contains interoperability issues upon connection with some SSLv3 servers. [16147]

No Workaround


Known Issue: 

When running a system service or any Cygwin tool outside of an X-term environment and you have a previous version of NET+OS installed, execution of the service might fail or crash. [16191]

Workaround:

To avoid this, add C:\Cygwin\bin to the system path and remove any and all Cygwin directories containing a cygwin1.dll from the user's system path. 


Known Issue: 

The nahttp_fs sample application may not function correctly with multiple simultaneous clients. With more than one browser simultaneously browsing to different directories, containing different directory information, continuous refreshes (via the F5 key) may eventually display the wrong directory information to the browser. [16219]

Workaround:

To avoid this, either limit the number of allowed connections to one, or place update code in the application that allows multiple access to the static data structures. 


Known Issue: 

When using the Raven debugger and GNU, the debugger may not break into the processor after a prior debug session. [16261]

Workaround:

To avoid this, power cycle the development board prior to every debug load. 


Known Issue: 

When debugging a 9750 development board that contains a valid flash image, problems are occasionally observed on inputing data to the dialog screen. [16283]

Workaround:

To correct this, a jumper on J1 to disable flash while the debugger is downloading the software image. The jumper can then be pulled before starting execution.