Release Notes PN 93000710_B ConnectCore 3G 9P 9215 82002488_B EOS August 3, 2011 INTRODUCTION This is a production release of firmware for the ConnectCore 3G 9P 9215. SUPPORTED PRODUCTS ConnectCore 3G 9P 9215 SUPPORTED CELLULAR MODEMS Qualcomm Gobi: 2000, Modem Revision: D1025-STUTABGD-3600 1 [Jan 14 2010 14:00:00] Huawei EM680 w/Gobi Technology: 3000, Modem Revision: D3200-STSUGN-1575 1 [Nov 22 2010 09:00:00] ENHANCEMENTS Added USB_WATCHPORT_CAMERA support. Erase NAND Flash during manufacturing before writing to file system. USB memory stick test for manufacturing. Cell Modem test for manufacturing. Powersave GPIO support. Sim Uart and Sim Can support. Add mobile service provider and Gobi support for these GSM providers: - Vodafone - T-Mobile (Europe) - Telefonica - Telcom Italia - Orange - DoCoMo Powersave RTC support Added FIM management so CANBUS cannot open FIM1 if it is being used by the serial port, and the serial port cannot open FIM1 if it is in use by CANBUS. The FIM serial ports cannot be used if the module is strapped for no sim slots. This indicates the GPIO lines for the FIM serial ports are not available to the FIM adapter kit development board. Removed support for CLI commands "df", "du" and "map32". They were never intended for release. The serial port strapping will now determine if XBee can be supported. If the strapping is set to 3 serial ports, XBee will be unconditionally disabled, and the GPIOs will NOT be used by Python. If the strapping is set to less than 3 serial ports, the XBee enable/disable will determine if the GPIOs can be used by Python. The XBee enable/disable will also start / stop XBee operation, and will not require a reset. This design does not allow the customer to talk directly to the XBee via serial. Added the following MMS features 1. IA2 Engine 2. Generic IA Protocol Manager 3. IA Zigbee 4. Modbus/TCP (MM/MP) 5. IA Pages for WebUI (Replacement for IA port profile pages) Added support for the Gobi 3000 modem. BUG FIXES Vantive 37090 - Sometimes USB devices aren't enumerated properly at boot-up. Vantive 37231 - CLI: show mobile, show mobileppp, and show surelink all return the same info when no index value is provided. Vantive 37397 - User Button 1 can't Factory Reset the unit properly. KNOWN LIMITATIONS You can receive a lot of errors/missing items if you switch the number of serial ports your device has between configuration saves/restores. KNOWN ISSUES Vantive 35396 - CLI: display carrier command isn't handled properly. Vantive 37259 - CLI: "display gps" doesn't update Latitude and Longitude properly when the GPS link is down. Vantive 37458 - System doesn't handle long Filenames properly. Vantive 37588 - The NDS FW does not allow to specify the PIN/PUK of the SIM card making it impossible to use a protected card. Vantive 37810 - Mobile PIN Status incorrectly reports Waiting for Pin. Vantive 38417 - CAN bus interface trouble: 200h indent frame not working with sample app. Vantive 38642 - Web Server stutters serving up Web pages from time to time. Vantive 38829 - Gobi 3000 Mobile Country Code incorrect with Sprint configuration. DOCUMENTATION ERRATA None. ADDITIONAL INFORMATION None. HISTORY 82002488_1P KNOWN ISSUES Vantive 34857 - Connecting a USB Flash drive caused the unit to reboot Vantive 34945 - USB Throughput Issues observed writing data to a USB Flash Drive. Vantive 34943 - Surprise Removals of USB Flash drives will likely crash the unit Vantive 34957 - Single-SIM module is reported as a Dual-SIM Module Vantive 34944 - The system appears to limit me to 5 USB Flash Drives connected behind a USB 2.0 Hub. Vantive 34946 - Data Passing test results in Memory Loss of about 150KB / Hour. Vantive 34948 - Modem may not Initialize properly after boot, or after a disconnect. Vantive 34957 - Single-SIM module is reported as a Dual-SIM Module. Vantive 34959 - Disconnects of the NMEA GPS Processor are handled poorly. Vantive 34970 - Initial Mobile Configuration options require a reboot, ideally they shouldn't, but we should inform the user of this. Vantive 34971 - Web UI: Mobile page stutters when opening. Vantive 34996 - Help missing for System Info -> Position and Diagnostics pages. Vantive 35035 - Web UI: The default SIM Slot displayed should be the Active SIM slot. Vantive 35061 - RealPort Server connections aren't getting cleaned up properly. Vantive 35063 - Multiple SIM switches resulted in the system hanging in trying to bring up the Cellular Link. Vantive 35112 - Telnet connections into the WAN IP address of the unit are failing. Vantive 35119 - Web UI blocks user from configuring Service Provider = None. Vantive 35128 - The os.statvfs function returns values that are more like suggestions rather than actual limits. Vantive 35152 - Python Autostart program not running at startup when dealing with the USB Flash Drive. Vantive 35155 - Writing to the USB Flash drive ends up crashing the system when the NAND Flash is nearly full. Vantive 35181 - Ethernet Phy improperly handles the setting MDI Mode = Auto. Vantive 35187 - Web UI Location Area Code and Cell ID fields are reporting "-1". Vantive 35188 - iDigi Descriptors are resulting in the GPS interface being reported as "GPS usb3" Vantive 35268 - USER LED1 on the dev board is still used as the Diag LED by the boot and post. Vantive 35269 - Unit ended up coming up with an Auto-IP Address when it shouldn't have. 82002488_2P KNOWN ISSUES Vantive 34857 - Connecting a USB Flash drive caused the unit to reboot. Vantive 34945 - USB Throughput Issues observed writing data to a USB Flash Drive. Vantive 34946 - Data Passing test results in Memory Loss of about 150KB / Hour. Vantive 34970 - Initial Mobile Configuration options require a reboot, ideally they shouldn't, but we should inform the user of this. Vantive 34971 - Web UI: Mobile page stutters when opening. Vantive 35019 - GASS: Cellular Link is not established reliably after a reboot. Vantive 35112 - Telnet connections into the WAN IP address of the unit are failing. Vantive 35152 - Python Autostart program not running at startup when dealing with the USB Flash Drive. Vantive 35155 - Writing to the USB Flash drive ends up crashing the system when the NAND Flash is nearly full. Vantive 35208 - GASS: The system misreports the Primary and Backup SIMs. Vantive 35269 - Unit ended up coming up with an Auto-IP Address when it shouldn't have. Vantive 35281 - The System provides no Event Log message when the GPS connection fails. Vantive 35282 - Manual disconnects of the GPS connection don't recover automatically. Vantive 35283 - The system shouldn't attempt to download modem FW if the system is not configured for a Mobile Service Provider. Vantive 35391 - Some USB Flash drives take much longer to be queried than others. Vantive 35396 - CLI: display carrier command isn't handled properly. Vantive 35398 - CLI: dis net command returns "00:00:00:00:00:00" for the MAC address of mobile0. Vantive 35447 - USB: Couldn't get volume information error message. Vantive 35919 - Cannot get signal strength, no matter combination of using main and aux connectors and cellular antennas. Vantive 35943 - Hardware reference manual cites LED1 as USER LED1, which is confusing. Vantive 35944 - Silk screen on the development board is confusing regarding the User buttons and LEDs that sit next to them. Vantive 36031 - The ConnectCore device has an abnormally long boot time Vantive 36207 - PPP thread on CC3G stops - unkillable and does not proceed to get a connection. Vantive 36321 - Single-SIM unit is unable to establish the Cellular Link after a long period of having it's antenna disconnected. Vantive 36288 - Spurrious reboots. Vantive 36336 - Writing to USB Flash drives is problematic. Vantive 36342 - CC3G Device sets wrong XBee DD value on Host Gateway. Vantive 36343 - Exception thrown on CC3G device during run of Dia. 82002488_A BUG FIXES Vantive 34857 - Connecting a USB Flash drive caused the unit to reboot. Vantive 34943 - Surprise Removals of USB Flash drives will likely crash the unit. Vantive 34948 - Modem may not Initialize properly after boot, or after a disconnect. Vantive 34957 - Single-SIM module is reported as a Dual-SIM Module. Vantive 34959 - Disconnects of the NMEA GPS Processor are handled poorly. Vantive 34970 - Initial Mobile Configuration options require a reboot, ideally they shouldn't, but we should inform the user of this. Vantive 34996 - Help missing for System Info -> Position and Diagnostics pages. Vantive 35019 - GASS: Cellular Link is not established reliably after a reboot. Vantive 35035 - Web UI: The default SIM Slot displayed should be the Active SIM slot. Vantive 35053 - CLI: "fat32" command returns a confusing entry when a Flash Drive is connected. Vantive 35063 - Multiple SIM switches resulted in the system hanging in trying to bring up the Cellular Link. Vantive 35112 - Telnet connections into the WAN IP address of the unit are failing. Vantive 35119 - Web UI blocks user from configuring Service Provider = None. Vantive 35155 - Writing to the USB Flash drive ends up crashing the system when the NAND Flash is nearly full. Vantive 35175 - BSS: Mobile Firmware Download Error reported in the Event Log. Vantive 35181 - Ethernet Phy improperly handles the setting MDI Mode = Auto. Vantive 35187 - Web UI Location Area Code and Cell ID fields are reporting "-1" Vantive 35208 - GASS: The system misreports the Primary and Backup SIMs. Vantive 35268 - USER LED1 on the dev board is still used as the Diag LED by the boot and post. Vantive 35283 - The system shouldn't attempt to download modem FW if the system is not configured for a Mobile Service Provider. Vantive 35298 - Cellular Link never comes up after a Boot. Vantive 35390 - CLI: flashdrv command appears to limit the device to a 4GB of capacity in the "Bytes" column. Vantive 35391 - Some USB Flash drives take much longer to be queried than others. Vantive 35447 - USB: Couldn't get volume information error message. Vantive 35904 - The Python library 'digihw' has a GPIO misnamed as 'X2-26' instead of 'X2_26'. Vantive 36075 - If the time was never set on the CC3G, using system_power_set(False, 10.0) causes the device to power down, never wake up. Vantive 36107 - CC3g Reports incorrect SIM information on Dual SIM module from 'display mfg' command. Vantive 36031 - The ConnectCore device has an abnormally long boot time Vantive 36288 - Spurrious reboots. Vantive 36336 - Writing to USB Flash drives is problematic. Vantive 36342 - CC3G Device sets wrong XBee DD value on Host Gateway. Vantive 36753 - rci factory default action="erase_user_flash" is not deleting the files in WEB directory. Vantive 36770 - The remote web server is prone to cross-site scripting attacks. Vantive 36872 - ping command returns wrong error when pinging an address that has no route to it. Vantive 36950 - Watchport Camera is not enumerating properly on the CC3G 9P 9215. Vantive 37035 - USB: Reading from the flash drive works in one telnet session fails in another. Vantive 36794 - panic during cellular test. Vantive 37103 - Local Configuration on Port D doesn't provide CLI access. Vantive 37187 - System Time is way off after a 17 day period where the units were idling. Vantive 37244 - CLI: "display carriers" with modem disconnect will PANIC. Fixed problem in the FIM serial driver for NS9215 platforms. This fix only effects platforms which use the FIM UART driver. The problem was that the head and tail pointers in the transmit buffer were getting out of sync with each other when we wrapped at the end of the buffer. This problem was documented in NET+OS Vantives 36895 and 37204. Vantive 37316 - Sleep Mode is broken. KNOWN ISSUES Vantive 34971 - Web UI: Mobile page stutters when opening. Vantive 35281 - The System provides no Event Log message when the GPS connection fails. Vantive 35282 - Manual disconnects of the GPS connection don't recover automatically. Vantive 35396 - CLI: display carrier command isn't handled properly. Vantive 35398 - CLI: dis net command returns "00:00:00:00:00:00" for the MAC address of mobile0. Vantive 35943 - Hardware reference manual cites LED1 as USER LED1, which is confusing. Vantive 37039 - Camera TCP Server: the connection to the Camera Server isn't reestablished after a disconnect. Vantive 37057 - Large Memory Leak observed passing RealPort serial data. Vantive 37090 - Sometimes USB devices aren't enumerated properly at boot-up. Vantive 37231 - CLI: show mobile, show mobileppp, and show surelink all return the same info when no index value is provided. Vantive 37259 - CLI: "display gps" doesn't update Latitude and Longitude properly when the GPS link is down. Vantive 37348 - Unit crashes and reboots while displaying the event log soon after waking up from Hibernation. Vantive 37397 - User Button 1 can't Factory Reset the unit properly. Vantive 37458 - System doesn't handle long Filenames properly. 82002488_A1 KNOWN ISSUES Vantive 34971 - Web UI: Mobile page stutters when opening. Vantive 35281 - The System provides no Event Log message when the GPS connection fails. Vantive 35282 - Manual disconnects of the GPS connection don't recover automatically. Vantive 35396 - CLI: display carrier command isn't handled properly. Vantive 35398 - CLI: dis net command returns "00:00:00:00:00:00" for the MAC address of mobile0. Vantive 35943 - Hardware reference manual cites LED1 as USER LED1, which is confusing. Vantive 37039 - Camera TCP Server: the connection to the Camera Server isn't reestablished after a disconnect. Vantive 37057 - Large Memory Leak observed passing RealPort serial data. Vantive 37090 - Sometimes USB devices aren't enumerated properly at boot-up. Vantive 37231 - CLI: show mobile, show mobileppp, and show surelink all return the same info when no index value is provided. Vantive 37259 - CLI: "display gps" doesn't update Latitude and Longitude properly when the GPS link is down. Vantive 37348 - Unit crashes and reboots while displaying the event log soon after waking up from Hibernation. Vantive 37397 - User Button 1 can't Factory Reset the unit properly. Vantive 37458 - System doesn't handle long Filenames properly. BUG FIXES Vantive 37757 - CC3G - no cellular link possible Vantive 38165 - Cellular 3G connectivity indicator does not work