Products > Test Equipment

MSO2000 Application module hack

<< < (20/24) > >>

timb:


--- Quote from: computer7geek9 on March 01, 2016, 06:59:10 am ---Well I managed to brick my mso2014b so thats fun. Any ideas on how to repair? I was attempting to install a firmware version with no password and it stayed on the splash screen for hours so I had no choice but to unplug it. Now it just has a white screen. Any ideas?

--- End quote ---

Ohh, that's bad. Is it still under warranty? Tektronix might need to replace it.

When Tek first sent me a MSO2024 (about 2 years ago), the first thing I did was to upgrade to the latest firmware. So I grabbed it from their site, popped it on an SD card and used a USB to SD dongle (I didn't have a sub-8GB USB drive handy) to load it. Same thing happened. Sat on the firmware screen for hours, so I finally unplugged it and...white screen.

I relayed the info to my contact at Tek, hoping they maybe had a sequence to get into an emergency boot loader or something. She put me in touch with a technician who put me in touch with one of the firmware engineers. No such luck. They ended up replacing it with a brand new MSO2024B.

Now, if you're not under warranty, maybe we can get some info out of the serial console as it boots. Perhaps force the boot loader to try the USB drive, if it's still intact.

Worse case scenario, it might require figuring out how factory firmware is programmed in. Maybe an onboard debug connector or something.

I know this isn't what you wanted to hear. :-/

computer7geek9:
I tried connecting to the serial console but was unable to get any data, plus I don't know the password (hence why I was updating it). I will try again to see if I have the wrong pins on the connector or something, but I'm afraid I might be out of luck. I don't know what could've gone wrong. I just edited the /etc/passwd file, re-tar, re-gz, changed the MD5, then made an img file. I used and online md5 calculator so I wonder if thats what caused it, but I would expect to see some kind of "upgrade failed" problem if it was just an md5 error. Could it be that the serial port isn't even initialized? 

drsurfer:
I simply don't understand.   :(
I just posted the password, and decoding it from /etc/passwd is a trivial task for any casual "hacker" like myself.
I haven't actually tried it, but there is no reason it does not work.
The point is you hadn't a working console. Where do you hope to go, even with removed password?

Anyway did you try to load the original unmodified firmware on a fresh USB key and retry flashing from scratch?

timb:
One would think that it wouldn't overwrite the boot loader first, but I don't know exactly how the upgraded works. It obviously copies the installer into to ram. Judging by the white screen and lack of serial data, I suspect it may wipe flash before copying the new bootloader and OS over.

If this is the case, the machine obviously wiped the flash and then encountered a silent error while copying the new data over.

If that's the case, then the only way to get the thing going may be through some sort of JTAG process.

timb:


--- Quote from: drsurfer on March 01, 2016, 09:30:07 am ---Anyway did you try to load the original unmodified firmware on a fresh USB key and retry flashing from scratch?

--- End quote ---

He can't reload off the USB key. The scope won't even boot.

When this happens you get nothing. Just a white display (meaning it's not getting past the bootloader).

Navigation

[0] Message Index

[#] Next page

[*] Previous page

There was an error while thanking
Thanking...
Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod