I've got a 3g150m that seemed to be working fine until I loaded a bad firmware on it. Now, the uboot interface doesn't seem to finish loading the firmware from tftp.

This is what happens when I attempt to boot normally (from the serial console):

U-Boot 1.1.3 (Mar 19 2010 - 16:33:16)

Board: Ralink APSoC DRAM:  32 MB
relocate_code Pointer at: 81fb4000
spi_wait_nsec: 3e   
spi deice id: c2 20 16 c2 20 (2016c220)
find flash: mx25l3205d
raspi_read: from:30000 len:1000   
*** Warning - bad CRC, using default environment

It just hangs there.

I can tell the uboot to load a firmware from tftp, but it never seems to finish after the firmware is loaded:

Please choose the operation:
   1: Load system code to SDRAM via TFTP.
   2: Load system code then write to Flash via TFTP.
   3: Boot system code via Flash (default).
   4: Entr boot command line interface.
   9: Load Boot Loader code then write to Flash via TFTP.

You choosed 2

0

2: System Load Linux Kernel then write to Flash via TFTP.
 Warning!! Erase Linux in Flash then burn new one. Are you sure?(Y/N)
 Please Input new ones /or Ctrl-C to discard
      Input device IP (10.10.10.123) ==:10.10.10.123
      Input server IP (10.10.10.3) ==:10.10.10.3
      Input Linux Kernel filename () ==:test.bin

 netboot_common, argc= 3

 NetTxPacket = 0x81FE4400

 KSEG1ADDR(NetTxPacket) = 0xA1FE4400

 NetLoop,call eth_halt !

 NetLoop,call eth_init !
Trying Eth0 (10/100-M)

 Waitting for RX_DMA_BUSY status Start... done

 Header Payload scatter function is Disable !!

 ETH_STATE_ACTIVE!!
Using Eth0 (10/100-M) device
TFTP from server 10.10.10.3; our IP address is 10.10.10.123
Filename 'test.bin'.

 TIMEOUT_COUNT=10,Load address: 0x80100000
Loading: Got ARP REPLY, set server/gtwy eth addr (00:e0:b8:6d:32:ec)
Got it
T #
 first block received
################################################################
       #################################################################
       #################################################################
       #################################################################
       #################################################################
       #################################################################
       #################################################################
       #################################################################
       #################################################################
       ##############################
done
Bytes transferred = 3145732 (300004 hex)

And there it hangs. I've tried the Tenda firmware and I've tried the "factory" firmware and the "sysupgrade" firmware from images I've loaded successfully in the past using sysupgrade. All seem to have the same result. Does anyone have any suggestions? Should I try loading a new uboot image? If so, where would I find something like that?

James