Difference between revisions of "WRT54G"

From Embedded Xinu
Jump to navigation Jump to search
(converted separate page to a header in this page)
Line 2: Line 2:
 
* possibly solved by "tighter" transceiver construction
 
* possibly solved by "tighter" transceiver construction
  
Control-C interrupts VxWorks loader, as it does in CFE.
+
== loading CFE ==
  
Configured to load XINU from Morbius; hangs on boot.
+
VxWorks will flash over itself with CFE - http://wiki.openwrt.org/OpenWrtDocs/Hardware/Linksys/WRT54G
  
* remove first 3 lines of loader/start.S
+
Attempted to load micro openWRT kernel and CFE over VxWorks
* check for serial port hardware address; compatible with XINU?
+
* upload failed - incompatible browser?
* VxWorks starting arguments similar to CFE?
+
* despite successful re-load of original firmware, bootloader refuses to find image on flash
 +
* possible solutions are loading fresh VxWorks from network or reloading flash through [[EJTAG]] port
  
VxWorks will flash over itself with CFE - http://wiki.openwrt.org/OpenWrtDocs/Hardware/Linksys/WRT54G
+
== loading XINU ==
  
== Trouble with first attempt ==
+
Control-C interrupts VxWorks loader, as it does in CFE.
 
+
VxWorks has an advantage over CFE in that it will remember bootloader settings for tftp host after powercycle.  This removes the need for special xinu-console script to talk to CFE.  Just run xinu-console, download compiled boot image, and powercycle.
Found reference to others loading non-VxWorks kernels using VxWorks bootloader, but no luck with XINU.
+
Settings for VxWorks bootloader:
 +
* boot device: vl0
 +
* host name: morbius
 +
* file name: {backend name}.boot
 +
* inet on ethernet: 192.168.6.{assigned by morbius}
 +
* host inet: 192.168.6.10
 +
* flags 0x88  --tftp and quickboot
  
Attempted to load micro openWRT kernel and CFE over VxWorks
+
Changes to current XINU revision for 'G' compatibility:
* upload failed
+
*
* despite successful upload of original firmware, bootloader refuses to find image on flash
 
* possible solutions are loading fresh VxWorks from network or reloading flash through [[EJTAG]] port
 

Revision as of 23:31, 7 June 2007

Transceiver from GL causes dropped characters; using Linksys transceiver

  • possibly solved by "tighter" transceiver construction

loading CFE

VxWorks will flash over itself with CFE - http://wiki.openwrt.org/OpenWrtDocs/Hardware/Linksys/WRT54G

Attempted to load micro openWRT kernel and CFE over VxWorks

  • upload failed - incompatible browser?
  • despite successful re-load of original firmware, bootloader refuses to find image on flash
  • possible solutions are loading fresh VxWorks from network or reloading flash through EJTAG port

loading XINU

Control-C interrupts VxWorks loader, as it does in CFE. VxWorks has an advantage over CFE in that it will remember bootloader settings for tftp host after powercycle. This removes the need for special xinu-console script to talk to CFE. Just run xinu-console, download compiled boot image, and powercycle. Settings for VxWorks bootloader:

  • boot device: vl0
  • host name: morbius
  • file name: {backend name}.boot
  • inet on ethernet: 192.168.6.{assigned by morbius}
  • host inet: 192.168.6.10
  • flags 0x88 --tftp and quickboot

Changes to current XINU revision for 'G' compatibility: