Electronics > Repair
Tektronix MSO4000B Front Panel Repair
<< < (3/3)
dbator:
It looks like even if I went the hard way through and was thinking now with all that knowledge I collected everyone should encounter no obstacles and repair easy their front panels, it turned out Tektronix must had complicate things even within the same series of scopes. Well almost the same - B and non-B can perhaps be considered as different series.

So:
1) No crystal at front panel MCU on this scope - internal clock as source is used.
2) No BDM connector and no jumper resistors populated on the PCBA - as if Tektronix covered up the tracks, so one does not think it is possible to access the MCU externally (or the board is used on different models, where in some the components are populated or in other they are not populated). I wonder, whether they removed the components after programming or they just used an external programming device. Good job at figuring out that missing components can be populated.
3) MCU was secured. Unless it is possible to get the MCU secured by installation of any application module because I suspect, front panel MCU manages the application modules slots. Maybe via SPI. I will try to trace the lines before I assembly my scope back and will let you know.

The possible reason why the MCU is no longer secured after programming it with route66_fp.s19 is either difference between the files (the file extracted from the package may not consist of security on purpose due complexity of securing the MCU via I2C, less possible) or executed program does secure the device which you didn't notice since you didn't run the code after programming. Or did you?
According to the datasheet of MC9S08AW32, the MCU has the security set by default after FLASH erase, so the manufacturer recommends to unsecure the blank device by setting proper bits before programming it in case no protection will be used.

Anyway, now we know, there are big chances for any of us by simple re-programming of the front panel MCU on the DPO4000/MSO4000/MDO4000 series of scopes with file extracted from firmware package with firmware package that can be downloaded from Tektronix support website. I hope joebot5 will be able to repair their front panel too that way.

I wonder why the program in FLASH gets corrupted that easy? Do you remember in which circumstances the issue occurred? Occurred it after firmware update?
And what is the route66b_fe.s19 file for? Debug log from your scope consists of something interesting:

--- Code: ---feReprogramFeProc: Platform Route66b fw 1028 filefw 1028
 Front Panel Firmware update not needed
   Current firmware 1028 >= 1028
--- End code ---

That's the route66b_fe.s19 file which is indicated there. It is also called front panel firmware and it seems to be up to date. Then master CPU on acquisition board attempts to communicate to the salve CPU (front panel MCU) and fails.
Well, maybe someone of us will find out someday what is the purpose of that file.
daveyk:
I love MSO4104 (no-B); it is my favorite scope (I have too many TDS3000 series scopes - lol).  Lately it has been having issues responding to certain front panel buttons (i.e. Magnifying glass, but most importantly the second button from the left under the display).  One of the other button right of it has problems to.  I need to keep this scope ISO17025 calibrated and not sure if there is a repair facility that could handle it. 

I then found out that unplugging the USB cable, in the back, seems to have cured the issues.   I use that interface to control the scope and get data from it with a lot of programs I use on a daily basis.  Remote control via that port works perfectly.  I have not tried via the network port; I'm not sure I should let the scope on my network and my test computer only has one network port.

Anyway, with the USB unplugged from my test computer, the front panel seems to be working fine, so I am sure I can send it out for ISO17025 calibration in October.  Don't laugh, but I swear this started after a Wiondows 11 update a month ago.



Using the scope for trouble-shooting with a flakey front panel is impossible. So, I just haven't used the MSO4104 for trouble-shooting lately because of this. 

This issue started a couple of months ago and I am not sure how to proceed, or if I should, and just live with it the way it is.
Navigation
Message Index
Previous page
There was an error while thanking
Thanking...

Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod