Tek CSA7404/TDS7000 repair project (Upgraded memory/CPU)

[CNsam]

I still can't modify the first item....

[Jwalling]

Hey!! I successfully connected the instrument! But I've encountered a new problem. I want to modify the data in the previous row, what should I do?

When you type C it should go to the first row (boot device). Set it to "sm".

[CNsam]

But when I enter C, it jumps directly to the second line. .

[CNsam]

I completed the configuration on my old computer. But it looks like I'm in trouble again. .

[coromonadalix]

pls  not being rude  can you make some efforts to show us some correct pictures, orientation  etc  .... 

the picture doesn't help at all


and  like the first thread page,   you push any keyboard key to stop the countdown,  and you type  the minus c   not the caps C ....  you had this  in vxworks if you where successful to stop it

[VxWorks Boot]: ?
 ?                     - print this list
 @                     - boot (load and go)
 p                     - print boot params
 c                     - change boot params
 l                     - load boot file
 g adrs                - go to adrs
 d adrs[,n]            - display memory
 m adrs                - modify memory
 f adrs, nbytes, value - fill memory
 t adrs, adrs, nbytes  - copy memory
 e                     - print fatal exception
 n netif               - print network interface device address
 N                     - set ethernet address
 
type c  and enter,  you should begin to do the settings like this :  and your entries should be after   see in bold, at first youlle se what they are, and after in bold you put yours ....


[VxWorks Boot]: c

'.' = clear field;  '-' = go to previous field;  ^D = quit

boot device          : sm   sm
processor number     : 0   0
host name            : host    host
file name            : c:\vxBoot\vxWorks.st      c:\vxBoot\vxWorks.st
inet on ethernet (e) : 192.168.0.2:ffffff00     192.168.0.2:ffffff00
inet on backplane (b): 192.168.0.2:ffffff00      192.168.0.2:ffffff00
host inet (h)        : 192.168.0.1                         192.168.0.1
gateway inet (g)     : 192.168.0.2                        192.168.0.2
user (u)             : anonymous                             anonymous
ftp password (pw) (blank = use rsh): anonymous          anonymous
flags (f)            : 0x1000    0x1000          some had to put 0x1008  in my case it did not help
target name (tn)     : target         tds7000     this one should be tds7000, otherwise tekscope will not save settings
startup script (s)   : c:\vxBoot\dio_rst.vsh      c:\vxboot\topscript.hw
other (o) :                    this one play tricks   had to put 0x0 or 0x0000  tekscope had some problems, some have put 0x1000 

[CNsam]

Sorry for giving you a bad impression, my old computer is not connected to the Internet... so I just used my phone to take the photos.
I successfully stopped the boot and set up nvram according to the link. But my 7104 still stays on the 'welcome' interface after booting.
I'll keep trying to fix it, thank you very much for your help.

[CNsam]

My 7104 successfully entered the oscilloscope! ! !

During the troubleshooting, I found that the NVRAM voltage was abnormal. After replacing it with a new one and setting the NVRAM, my instrument was able to work normally! ! !

Thank you again! ! ! ! ! ! ! ! ! ! ! !

[coromonadalix]

 


bu sure to wait at least  20 mins,  with no  probes

do  a self calibration,  it will go clicking for a few minutes,  you need to see pass

and do spc    when finished you have to get no errors codes  on all the informations   


it will rewrite files in the calcon folder, in you vxWorks folder on c:\    who could be hidden ...

i had errors  because of an eeprom corruption in the acquisition section ...

[pasta2018]

I replaced the sram which is HM628128DLT5SL，but it also show nvram walking one test failed. There is another chip DS13D12，I am not sure I should replace this one or use another new nvram chip.

[pasta2018]

finally I replaced the nvram. and now it's working properly.

[Yroger]

CNsam wrote:

But when I enter C, it jumps directly to the second line. .

How were you able to solve this problem because for me I am still stuck at this point 
Thank you.

[coromonadalix]

check in your terminal software  if ou have local echo  or some setting who could hinder cr+lf  cr  lf  ...  ??

9600, n , 8 , 1 .....
 

[Yroger]

I use CoolTerm 64bits and the local echo seems disabled yet

[Yroger]

Thanks to coromonadalix because thanks to his advice I was able to solve my "echo" problem when I entered certain commands. In the software I use: Coolterm, in addition to unchecking the local echo box, I had to change the key emulation entry from CR+LF to CR.
======
Unfortunately this was not enough. The Vxboot page loads but then I only have errors displayed. As a result, the program always remains frozen at the start page.

[coromonadalix]

the vxboot may load,  but you may still have errors,  and since its a long boot process try to copy / save it, in a file

i had bad settings it it, and the scope SW stalled on the start page  ....

it is not easy,  many trials and errors, read tons of threads ...

took me at least 2 weeks  to re-start a 7404,  getting all the needed materials  old stuff etc ...   the 7254  i re-started  1 year ago was easier ....  more recent stuff  vs the 7404 ...

the 4 last pages of this thread and xdev's  give you lots to work with

[Yroger]

Yes quite !! I think my answers are already present somewhere in this topic.
Thank 

[Yroger]

Good morning,
This command line thing is really annoying. On my csa8000 the vxboot starts, but I have errors which still prevent the Tektronix program from starting (see below the copy of the console log)
Dos anyone have an idea to solve this new problem ?
I only left the end of the diary
A++

TpExecDebugTrace = 0x1
TpExecDebugTrace = 0x1314eb8: value = 1 = 0x1
hwaLibStartup
ERROR- Function: acqLibLoadDspProgramVector, SysCall: ioctl, errno 0, Msg: HI32_DRV_EXECUTE
0x31ec480 (hwaStartup): diagLoadCodeForAcqDsps: AcqDSP#0 NOT RESPONDING
ERROR- Function: acqLibGetDspStatus, Msg: acqLibSendCmd
ERROR- Function: acqLibClearAcqErrorStatus, Msg: acqLibGetDspStatus
ERROR- Function: acqLibClearAcqErrorStatus, SysCall: ioctl, errno 0, Msg: HI32_DRV_CLR_ERROR
0x031ec480: hwaStartup:Assertion failed: status != ERROR, file ../src/calDiagMgr.c, line 3681

[coromonadalix]

not sure the 8000 series are managed the same way as 7000 series ...    for sure the log is not the same  or you omited some section ?   

and pls   put this log into a txt  file    the thread become way too long

[charlyd]

@CNsam from what i see he needs to do a clearDB

[charlyd]

who can help me with figuring out where the instrument ID is set of the TDS7000 series.   first i got a tds7404 where i could not get any option key installed.  after  uninstalling and reinstall the tekscope 2.5.3 software it detect the unit as a  tds7254.

then i can imagine the key is not picked up correct.  i exported my nvram content. cleared  the nvram with all FF , reconfigured it manually like new boorsettings and so but nothing then i decided to revert the earlier saved content back but no change.  i guess it will be saved in the NVRAM (in my case FRAM) but it looks like it is not set  on that location.

so i need to figure out the location where it can be changed and after another reinstall of the software it detects the unit as a TDS7404 and not a TDS7254. 

of course is a dirty workarround to re-generate the option key to a tds7254 but that is not my way of fixing things.

[coromonadalix]

hi

I never found out where the model is taken from ..

but can you put your vxwork boot log from the side port connector ?   into a txt file ?

[charlyd]

i have looked into the log  but there is nothing found in it apart from bad instrumentID

what i can do tomorrow, swap the board and see if that changes something. the instrumentID is married to the ACQ board i guess.

[colorburst]

I have no experience with the TDS7000 series, but on related scopes the model is loaded from the acquisition board. I'd first verify that your board hasn't been exchanged from the lower bandwidth model.

If you can communicate with the console, the command raxDbgRead "GTL/BRDID" should tell you the contents of the board id register. The mapping appears to be 0xd = TDS7254 and 0xf = TDS7404. I haven't tested this personally.

The instrument id is a function of the model and the serial number.

[charlyd]

Hi @Colorburst, yes you are right it is the ACQ board from an other unit i guess. where on the Acq is the Instrument id  set.  anbody any idea which resistors-set /on what location is used for the selection?

[charlyd]

And a complete other question, i want to discuss with you technicians...about these 7000 units. did anybody ever had broken trigger chips without visible signs.
normally they get bulgy on top.
or text  off or slightly brown Colored.
or even exploded or just one or two pins burned off the chip.

i mean to say:

i now have two trigger chips without any visible sign of broken on a board , which also passes all diag tests. can these chips still be broken ?