Known released Issues 6.2 These are the known defects in this release of NET+Works: 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 Step Over when on a branch instruction. Known Issue: When debugging ARM9-based applications with the Raven debugger, the application will not start after continuing when setting a breakpoint immediately after loading a program. [15611] Workaround: To avoid this, breakpoints must be refreshed after the MMU is enabled. A temporary breakpoint (tbreak) has been included in the default .gdbinit file immediately after the MMU is enabled. Additionally, the BSP_BUILD_CACHE_DRIVER must never be set to FALSE. 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.2, 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: 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: 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 any of the support NET+Works platforms. 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: 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: Even though NET+Works contains various references to Kerberos, the protocol is not supported by software. These references are contained in the source code and in the On-Line Help. These include defines in the application header file appconf.h (like APP_KERBEROS_REALMNAME, APP_KERBEROS_KDC, APP_KERBEROS_USERNAME, APP_KERBEROS_PASSWORD), or references to Kerberos in the BSP file boardParam.c (like NAGetAppKerberosRealmName(), or NAGetAppKerberosPassword(), et. al.) and several other spots. [14385] No Workaround 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 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: The clock selection is incorrect on the Connect-ME, Connect-WIME, and Connect-WIEM platforms. The PLLTST_SELECT definition uses NAusesTheInternalOscillator(), which references the NS7520/NET+50 Development board table, pulling a value based on chip revision, out of the NANetarmInitData table, which uses an oscillator input instead of a crystal. [15625] Workaround: This can cause the system clock to be off, which results in an error in the baud rate generation, which can cause errors in serial. To correct this, the following should be used in bsp.h, replacing the present definition. #define PLLTST_SELECT SELECT_THE_CRYSTAL_OSCILLATOR_INPUT 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: 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: Nibble ID mode has known defects in the NS9750. For details see, the Hardware Reference manual. No Workaround Known Issue: USB Device endpoint number 11 is not supported; endpoints 0-10 are supported. This is on the NS9750 and the NS9360. No Workaround