ambit 200 connection problem TCP CONNECTION FAILURE

[mainblazer123]

when i start hyperterminal this is what is happenin what have i done wrong


TCNiSO 5100 Bootstrap CPU = BCM3348A1
Ebi Initialized: 000002020000001C
Sdram Initialized: [ OK ]
CPU instruction cache size: 2000
CPU instruction cache line size: 0010
CPU data cache size: 2000
CPU data cache line size: 0010
Sdram access: [ OK ]
TCNiSO Compressed bootloader detected
Compressed bootloader size: 0062DA
Compressed Image location: 81F80000
Decompression Status: 00000000
Dcompressed Bootloader size: 00011005
BSS Initialized:
TMP Stack initialized: [ OK ]
Perm Stack initialized: [ OK ]
MemSize: ......................... 8M
flashDetect: ERROR: Flash programming FAILED: 3
flashGetBase: ERROR: Flash programming FAILED: 3
flashDetect: ERROR: Flash programming FAILED: 3
flashGetBase: ERROR: Flash programming FAILED: 3
flashDetect: ERROR: Flash programming FAILED: 3
flashGetBase: ERROR: Flash programming FAILED: 3
flashDetect: ERROR: Flash programming FAILED: 3
flashGetBase: ERROR: Flash programming FAILED: 3
flashDetect: ERROR: Flash programming FAILED: 3
flashGetBase: ERROR: Flash programming FAILED: 3
TCNiSO SIGMA Bootloader v2.6
Build date: May 9 2005
flashDetect: ERROR: Flash programming FAILED: 3
flashGetBase: ERROR: Flash programming FAILED: 3
flashDetect: ERROR: Flash programming FAILED: 3
flashGetBase: ERROR: Flash programming FAILED: 3
Location: 0xBFC10000
Signature: 3348
Control: 0000
Major Rev: 0002
Minor Rev: 0001
Build Time: 2006/11/3 02:33:33 Z
File Length: 966321 bytes
Load Address: 80500000
Filename: SB5100-2.3.2.7-SCM00-NOSH.bin

Bypassing CRC Verifiction on Image 1...
Loading Image 1...
Executing Image 1...

flashDetect: ERROR: Flash programming FAILED: 3
flashGetBase: ERROR: Flash programming FAILED: 3
Piggyback Firmware Loader
Detected Compressed Firmware..... Decompressing...
Target Address: 0x80010000
....................
Decompressed length: 5243448
3348
NFS client support not included.
usrRoot:usrNetInit: complete!
Loading symbol table from admin:/vxWorks.st.sym
st.sym: status = 0xd0001
Hello... and welcome to the wonderful world of vxWorks!!

CmTargetLowLevelInit: Loading Flash/ProgramStore/NonVol drivers...
FlashDeviceDriver:etectFlash: ERROR - Failed to detect flash type (not CFI-co
mpliant)!
FlashDeviceDriver::FlashDriverInit: ERROR - Failed to autodetect flash device!
CmTargetLowLevelInit: Creating singletons for ProgramStore/BootloaderStore/NonV
ol devices...
Detecting the next image number that we will store to by default...
0x14 Computing CRC32 over image2 to ensure that it is valid...
ProgramStoreDeviceDriver::ProgramStoreDriverIsImag eValid: ERROR - Failed to ope
n flash driver!
0x1e Done computing CRC32!
By default, we will dload to image number 2!
FlashDeviceDriver::FlashDriverGetRegionInfo: WARNING - Invalid region specified
; returning NULL
NonVolDeviceDriver::NonVolDriverMaxSizeBytes: ERROR - Failed to query flash reg
ion info!
FlashDeviceDriver::FlashDriverGetRegionInfo: WARNING - Invalid region specified
; returning NUL
NonVolDeviceDriver::NonVolDriverMaxSizeBytes: ERROR - Failed to query flash reg
ion info!
Reading Dynamic settings from non-vol...
FlashDeviceDriver::FlashDriverGetRegionInfo: WARNING - Invalid region specified
; returning NULL
NonVolDeviceDriver::ReadTrueSegmentSizeBytes: ERROR - Failed to open the flash
driver!
NonVolDeviceDriver::NonVolDriverRead: ERROR - Failed to query the segment size
(returned 0 bytes)! There is no valid data to read.
0x00000064 ['tStartup' id=0x807e3690] BcmNonVolDeviceDriverBridge
onVol Device) ERROR - Failed to read the length from the settings data!
0x00000078 ['tStartup' id=0x807e3690] BcmNonVolDeviceDriverBridge::Read: (NonVo
l Device) ERROR - Failed to read the buffer from the device! Resetting the enti
re section to defaults.
0x00000082 ['tStartup' id=0x807e3690] BcmSnmpNonVolSettings::ResetDefaults: (SN
MP NonVol Settings) WARNING - Resetting Dynamic Settings!
*
*
* Failed to read non-vol settings from the device!
*
*
Reading Permanent settings from non-vol...
FlashDeviceDriver::FlashDriverGetRegionInfo: WARNING - Invalid region specified
; returning NULL
NonVolDeviceDriver::ReadTrueSegmentSizeBytes: ERROR - Failed to open the flash
driver!
NonVolDeviceDriver::NonVolDriverRead: ERROR - Failed to query the segment size
(returned 0 bytes)! There is no valid data to read.
0x000000be ['tStartup' id=0x807e3690] BcmNonVolDeviceDriverBridge::ReadImpl: (N
onVol Device) ERROR - Failed to read the length from the settings data!
0x000000c8 ['tStartup' id=0x807e3690] BcmNon
l Device) ERROR - Failed to read the buffer from the device! Resetting the enti
re section to defaults.
0x000000dc ['tStartup' id=0x807e3690] BcmHalIfNonVolSettings::ResetDefaults: (H
alIf NonVol Settings) WARNING - Resetting Permanent Settings to defaults! MAC a
ddresses and other settings are now invalid!
0x000000f0 ['tStartup' id=0x807e3690] BcmCmBpiNonVolSettings::ResetDefaults: (C
M BPI NonVol Settings) WARNING - Permanent settings (BPI Keys and other unique v
alues) are being reset to their default va
0x000000fa ['tStartup' id=0x807e3690] BcmSnmpNonVolSettings::ResetDefaults: (SN
MP NonVol Settings) WARNING - Resetting all Permanent Settings! The serial numb
er and other Sys Info items are probably invalid!
0x0000010e ['tStartup' id=0x807e3690] BcmDocsisCmDownstreamCalibrationNonVolSett
ings::ResetDefaults: (DOCSIS CM Downstream Calibration NonVol Settings) WARNING
- Resetting Permanent Settings to defaults! The downstream calibration table w
ill reset to default values!
0x0000012c ['tStartup' id=0x807e3690] BcmDocsisCmUpstreamCalibrationNonVolSettin
gs::ResetDefaults: (DOCSIS CM Upstream Calibration NonVol Settings) WARNING - R
esetting Permanent Settings to defaults! The upstream calibration tables will b
e configured for the default Amplifier!
*
*
* Failed to read non-vol settings from the device!
*
*
0x00000172 ['Telnet Thread' id=0x807ec540] BcmTelnetThread::ThreadMain: (Telnet
Thread) Telnet server thread running...
Calling Vendor PreDriverInitialization...
PreDriverInitialization: Tuner 0 Amp 4
tunerInit()
Attaching network interface lo0... done.

NOTE: Driver initialization was skipped! The application will not run or fowar
d data. You can change NonVol Setting, but that's about it...

*
* *
* *
* *
* *
* *
* *
* *
* *
* *
* *
* *
* *
* *
* *
* *
* * * *
* * * * * * ***
* * * * * * * * *******************
* * * * * *
* *
Copyright (c) 1999 - 2003 Broadcom Corporation
+----------------------------------------------------------------------------+
| Build Date: Aug 26 2003 |
| Build Time: 15:51:17 |
| Built By: MGI1145 |
| |
| Revision: 2.9.2n RELEASE vxWorks PID=0x3348 |
| |
| Features: DOCSIS 1.0/1.1/2.0 BPI/BPI+ (no IPSEC) (no EMTA) Propane |
| Features: Vendor:Motorola Corporation SNMPv3 (WindRiver WindManage 9.3) |
+----------------------------------------------------------------------------+
Broadcom DOCSIS 1.0/1.1/2.0 Cable Modem Application starting...
'The cubicle across from you is empty...go now!'

Beginning Cable Modem operation...

Type 'help' or '?' for a list of commands...
WARNING - No DOCSIS Control thread provided. DOCSIS state machine can't run!
CM>

[aviz06]

looks proper fooked to me, may have to re-flash the chip via Jtag???

[mastergee]

looks like its the wrong flashchip on the modem... check what flashchip is on the modem ie: if its 0btc, its not compatible sigma

[mainblazer123]

no it dont look like that chip

[mainblazer123]

please help its some thing that goin wrong ive done another two with the same TCP CONNECTION FAILURE WHEN I TRY TO READ MAC

[skye00]

nobody nows its a mystery!!

[mainblazer123]

does any one have clue why im getting rhis error yet it stressin me out

[fitz]

Yes. It is because you have flashed your modem with inappropriate firmware / suffered a bad flash and killed it.

Try connecting to your modem using the softjtag program and rs232 interface. you can flash just the bootloader or the entire flash from here.

Failing that, you can resurrect the modem like a fat one-legged pigeon rising from the ashes by using a blackcat / poor man's jtag cable and the Schwarze Katze software.

Use 13.5full.stealth.bin as suggested by aviz06 several posts ago.

Or you can just flash the bootloader or whatever, restoring the 'p' option. Anything's better than what you've got on there atm.

****://***.mediafire.com/download.php?gy3vaj2ehye
May help if you flash the firmware using above mentioned program, and whatever may lie at that URL

Of course i'd not know what may be held at that incomplete URL

cheers, fitz.

[abaaba]

I need help for TCP Connection failure, this is what i got in hyperterminal:

BCM3349A0
100000010346890
MemSize: ......................... 8M
Flash detected @0xbe000000
Signature: 3349

Broadcom BootLoader Version: 2.1.6d release Gnu
Build Date: Dec 7 2004
Build Time: 09:10:44
Image 1 Program Header:
Signature: 3349
Control: 0000
Major Rev: 0003
Minor Rev: 0000
Build Time: 2006/11/3 02:33:33 Z
File Length: 880468 bytes
Load Address: 80500000
Filename: 5101hack_mod_by_FERCSA.bin
HCS: c6fe
CRC: c19cfc6c

HCS failed on Image 2 Program Header

Enter '1', '2', or 'p' within 2 seconds or take default...
.

Board IP Address [0.0.0.0]: 192.168.100.1
Board IP Mask [255.255.255.0]:
Board IP Gateway [0.0.0.0]:
Board MAC Address [00:10:18:ff:ff:ff]:
Internal/External phy? (i/e)[i]

Init EMAC, DMA, and MII PHY...
******************** CRASH ********************
EXCEPTION TYPE: GENERAL
R0/ZERO=00000000 R1/AT =f0000000 R2/V0 =ffff8000 R3/V1 =a07039e8
R4/A0 =a07039a0 R5/A1 =00000640 R6/A2 =007065b8 R7/A3 =00000000
R8/T0 =007005f8 R9/T1 =00003200 R10/T2 =00000008 R11/T3 =007039f8
R12/T4 =a0703968 R13/T5 =a07039b0 R14/T6 =00000000 R15/T7 =00000054
R16/S0 =00000080 R17/S1 =00000040 R18/S2 =807002a0 R19/S3 =00000000
R20/S4 =00000000 R21/S5 =00000000 R22/S6 =00000000 R23/S7 =00000000
R24/T8 =00001021 R25/T9 =00000001 R26/K0 =deaddead R27/K1 =deaddead
R28/GP =fffffffe R29/SP =807ffdf0 R30/FP =00000000 R31/RA =81f89560
pc : 0x81f89560 sr : 0x00000002
cause: 0x00008028 addr: 0x00000000

[uksrevivor]

Originally Posted by fitz

Yes. It is because you have flashed your modem with inappropriate firmware / suffered a bad flash and killed it.

Try connecting to your modem using the softjtag program and rs232 interface. you can flash just the bootloader or the entire flash from here.

Failing that, you can resurrect the modem like a fat one-legged pigeon rising from the ashes by using a blackcat / poor man's jtag cable and the Schwarze Katze software.

Use 13.5full.stealth.bin as suggested by aviz06 several posts ago.

Or you can just flash the bootloader or whatever, restoring the 'p' option. Anything's better than what you've got on there atm.

****://***.mediafire.com/download.php?gy3vaj2ehye
May help if you flash the firmware using above mentioned program, and whatever may lie at that URL

Of course i'd not know what may be held at that incomplete URL

cheers, fitz.

Hi
Ok I've done ambit 200 and had to flash as it was blocked. did everything as said in Haynes guide and got back to P part of telnet.
But what now, I tested on a live line but got no lights on moden except power.
Am I missing something?
Pleae help.
Thanks in advance.