BSP Updates – NET+OS 6.2

 

 

 

Last Updated: 06/26/07         Fix Count: 10

__________________________________________________________________________________________________________________________

 
Title 
GPIO cleanup
 
Case:  23360
 
Date Fixed:  06/25/07
 
Description
Errors in the #defines in bsp/devices/ns9xxx/ns9360/gpio/gpio.c could cause problems with several GPIO pins.
 
Solution 
Corrected errors affecting pins 11, 65, 68, 69, 70, and 71
__________________________________________________________________________________________________________________________
 
Title 
Data corruption on USB device Control endpoint
 
Case:  17624
 
Date Fixed:  01/19/06
 
Description
Cache coherency failures are occurring when memory adjacent to the driver DMA buffers is being accessed after the DMA memory is setup
(invalidated), but prior to the actual transfer causes. This access pulls the line into cache and then becomes incoherent when the DMA occurs.
 
Solution 
Aligned and isolated the DMA buffer on 32-byte boundaries for the
Control-Out endpoint.
__________________________________________________________________________________________________________________________
 
Title
FTP authentication failure
 
Case:  17521
 
Date Fixed: 01/04/06




 
Description
User callback function was beinig called twice with error "Invalid Password" during a single authentication sequence.
 
Solution
Corrected defect that caused the registered application error handler from NARegisterTraceFailure() to be called multiple times for a single authentication failure.
__________________________________________________________________________________________________________________________

 

Title

Application rom.bin Fails to initialize

 

Case:  17301

 

Date Fixed:  11/26/05

 

Description

When loading an application’s rom.bin file (instead of using the bootloader), used to run an image directly from Flash, as opposed to RAM, the initialization fails, and an "nccInitializationFailed:. . . “  message is displayed instead of the dialog.

 

Solution

Corrected the function nccGetRequiredRamSize to check its location in memory and deduce from this information whether it is running in ROM or RAM.  Based on this information, if in ROM will not include the text section in its calculation of RAM needed, while if running in RAM, it will include the text section size.

__________________________________________________________________________________________________________________________

 

Title

Telnet authentication failure

 

Case:  17109

 

Date Fixed:  10/16/05

 

Description

It was possible for an error to occur and never generate a call to the validation failure callback.

 

Solution

Fixed implementation in NACheckAuthentication.

 

 
Title
Setting up External IRQ1 on a 9360 based platform
 
Case:  16760
 
Date Fixed: 08/22/05




 
Description
There is a defect when setting up a NS9360-based platform to use the alternate path of the external IRQ1 (GPIO 28).  The value loaded into the configuration register is going to the wrong place.  So this value remains in the default state and the value loaded for GPIO 24 is getting inadvertently changed. 
 
Solution
Correct the programming for NS9360 platforms to put this data into the right location.
__________________________________________________________________________________________________________________________
 
Title
Timer API fails to properly configure 
 
Case:  16737
 
Date Fixed: 08/22/05




 
Description
When used as a raw timer, the NATimerConfigure() is failing to successfully configure.
 
Solution
Corrected a defect in the timer code, where a switch instance was missing a break statement and falling through the default, which is used to trap unrecognizable conditions.
 

 

Title

Setting multiple FIRQ handlers

 

Case:  16743

 

Date Fixed:  08/18/05

 

Description

The ARM processor allows one FIRQ, but the function naIsrInstall() allows multiple FIRQ handlers to be registered.

 

Solution

A mechanism was added to naIsrInstall() to trap when an FIRQ was already registered.

__________________________________________________________________________________________________________________________

 

Title

NS9750 Chip Select CS4 and CS5 Initialization Problems

 

Case:  15810

 

Date Fixed:  06/24/05

 

Description

The initialization sequence for CS4 and CS5 (in the 9750 platform) is backwards, such that the base address is set prior to the mask. This could cause the processor to remap this chip select inadvertently, potentially overlapping the chip select used to fetch instructions, potentially causing a system to crash when these chip selects are populated.

 

Solution

The mask register will be set first, followed by the base register.

__________________________________________________________________________________________________________________________

 

Title

Non-volatile configuration resets on upgrade

 

Case:  15710

 

Date Fixed:  05/13/05

 

Description

When upgrading to version 6.2, the configuration values are being reset to their default values.

 

Solution

Extend the algorithm to check for prior versions of the configuration, using the prior configuration data, such that only those parameters which are not present in the older version will have default values.

 

The following describes the algorithm:

 

a.       Check the CRC for the current board parameters in the flash

b.       If the CRC fails, then see if the CRC works if we check the CRC

         only for the record size.

c.       If this fails then check the CRC for considering the original

         NET+OS 6.2 data type. 

d.       If this fails then try with NET+OS 6.1 data type. 

e.       If this fails then try NET+OS 6.0 type of data structure. If

         this succeeds then move the wireless data to the new location

         and update new field based on the default value. 

f.       If step e. fails then as a last resort try with NET+OS 5.0 and

         5.1 type of data structure.

g.       If any of the above steps succeed, then update the new record

         size and calculate the new CRC and write it back to flash.

h.       If all fails then return the default values back to the caller

         and update the flash with default values.

 

 

Files:   netos\h\pthread.h

            netos\h\wln_api.h

            netos\h\boardParams.h

            netos\h\semaphore.h

            netos\src\bsp\common\sysAccess.c

            netos\src\bsp\devices\common\timer\timer.c

            netos\src\bsp\devices\ns9xxx\common\usb\usb.c

            netos\src\bsp\devices\ns9xxx\common\usb\usb_driver.c

            netos\src\bsp\devices\ns9xxx\common\usb\usb_def.h

            netos\src\bsp\devices\ns9xxx\9360\gpio\gpio.c

            netos\src\bsp\init\arm9\mc_isr.c

            netos\src\bsp\init\arm9\NCC_INIT.c

            netos\src\bsp\platforms\connectem\ boardParams.c
            netos\src\bsp\platforms\connectme\ boardParams.c
            netos\src\bsp\platforms\connectsp\ boardParams.c
            netos\src\bsp\platforms\net50_d\ boardParams.c
            netos\src\bsp\platforms\net50bga_a\ boardParams.c
            netos\src\bsp\platforms\ns7520_a\ boardParams.c
            netos\src\bsp\platforms\ns9360_a\ boardParams.c

            netos\src\bsp\platforms\ns9750_a\ boardParams.c
            netos\src\bsp\platforms\connectwiem\ boardParams.c
            netos\src\bsp\platforms\connectwime\ boardParams.c
            netos\src\examples\nausbdevapp\usb_test.c

            netos\src\examples\nausbdevapp\data.c

 

Special Instructions

 

  • Unzip the patch(es) to the root of your NET+OS installation, for example C:\netos62_gnu\.
  • Be sure to install any patches listed under Dependencies below
  • Rebuild your BSP.
  • Rebuild your application.

                               

Patch Link:  BSPUpdates_62

 

Dependencies

This patch also requires the installation of the following patch(es):