Downgrading From U-Boot 1.1.4/1.1.6 To U-Boot 1.1.3 On Cc9P9360 Modules To Run Old Wince5.X or Lxnetes-3.X Firmware, Using Nvram From Eeprom
Downgrading From U-Boot 1.1.4/1.1.6 To U-Boot 1.1.3 On Cc9P9360 Modules To Run Old Wince5.X or Lxnetes-3.X Firmware, Using Nvram From Eeprom
Downgrading From U-Boot 1.1.4/1.1.6 To U-Boot 1.1.3 On Cc9P9360 Modules To Run Old Wince5.X or Lxnetes-3.X Firmware, Using Nvram From Eeprom
3 on CC9P9360 modules to
run old WinCE5.x or LxNETES-3.x firmware, using NVRAM from EEPROM.
EOL Replacement
FS-3013 U-Boot 1.1.3 NVRAM in EEPROM, no R2 CC-9P-V225-Z1 U-Boot 1.1.4 NVRAM in Flash, no R2
populated populated
Modules CC-9P-x2xx-Z1 have programmed NVRAM in a flash partition maintained by U-Boot 1.1.4 or higher. U-Boot
1.1.3 and operating systems WinCE5.x, LxNETES-3.x expect NVRAM in on module EEPROM.
Downgrade U-Boot and NVRAM into EEPROM from U-Boot console as following:
Connect ethernet with TFTP server providing your latest U-Boot 1.1.3 binary or USB stick with this binary. If it fits
your need, you can also use latest U-Boot 1.1.3 FS.3 binary from Digi:
http://ftp1.digi.com/support/patches/uboot113fs3-binaries.zip
http://ftp1.digi.com/support/patches/UBootFixes_113F3.htm
On all other CC9P9360 modules (e.g. FS-3013 and all CC-9P-?2?? replacements) the resistor R2 is not populated,
allowing to use GPIO13 for other purposes (e.g. serial ring indicator). Drawback is, that you can't use the DS1337 RTC
interrupt input in your software. If your software depends on this, you should either change the software or patch the
module with a 0 Ohm connection on R2.