Well done! There is always a link file in that directory, but it should be empty and not pointing to anything.
Maybe before trying anything else out do a reinstall of a version 2.41, then put the link file on a flash drive and copy it over when logged in via telnet.
The rest is simple, there where 2 .lnk files in Secure\Startup, one infiniivision.lnk and one infiniivision_ext.lnk. Why? You tell me. Renamed infiniivision_ext.lnk to infiniivision_ext.xxx and rebooted the scope. Bingo! That's enough for this evening, I'll try the -l all -l bw50 tomorrow
Gratz on the fix!
BTW, its possible what you've got two lnk files because the scope was upgraded to 2.41 at some point of time and for some reason old lnk file was left in its startup folder.
Attached is the CELoader.exe for anyone running into the same problem. Please read the thread how to get an older firmware and how to extract the NK.BIN.COMP and decompress it into NK.BIN.
I have no idea what OS you need to run the exe, but it works fine in Windows 10. You can always download the source yourself and compile.
https://celoader.codeplex.com/(Edit: WTF? Why does it say "downloaded 3 times" right after posting?
)
(Edit 2: WTF!!! "downloaded 66 times" 10 seconds later??? )
@PA0PBZ Great news for you and thanks for sharing 😀
Yes, an excellent result and a close shave!
Aftermath:
First I tested the options manually:
- processmgr kill infiniivisionlauncher.exe
- infiniivisionlauncher -l all -l bw50
That worked as expected so:
- ren infiniivision.lnk infiniivision.xxx
- ren infiniivision_ext.xxx infiniivision_ext.lnk
- reboot scope
Works fine, I didn't bother to change the 63# count as I was expecting it doesn't matter and it didn't.
Now please excuse me, I'm going to play with my new toy
Aftermath:
First I tested the options manually:
- processmgr kill infiniivisionlauncher.exe
- infiniivisionlauncher -l all -l bw50
That worked as expected so:
- ren infiniivision.lnk infiniivision.xxx
- ren infiniivision_ext.xxx infiniivision_ext.lnk
- reboot scope
Works fine, I didn't bother to change the 63# count as I was expecting it doesn't matter and it didn't.
Now please excuse me, I'm going to play with my new toy
I am sure I've missed it somewhere, but do you know what did cause the problem?
I am sure I've missed it somewhere, but do you know what did cause the problem?
Basically the 2 links in the startup folder, but apart from memset's suggestion in #1151 I have no idea why that happened.
DSOX3000 series logic analyzer cable on ebay for $155.00 USD shipped(in the US) if someone needs one. It isn't mine, I don't know the seller. You'd also still need the little grabber hooks. Still a pretty decent deal though -
http://www.ebay.com/itm/351837124622edit - it has been sold.
Stupid Muppet Bricked their scope
Suggestions WelcomeHello all, I used the USB boot file "3ka_v241_linkinstall.cab" with the intention of "cough, cough" upgrading my scope.
I thought I'd upgraded my scope to 2.41, but like a complete numpty, I didn't check, it was, in fact, running 2.37.
So, now I have a bricked scope. It loads, shows the boot screen, then black screen with "Agilent Technoliges", then the screen goes blank.
Any suggestions on how to unbrick it?
Any suggestions on how to unbrick it?
Do you have the LAN interface or can you get hold of one? If yes, can you get a telnet prompt?
Otherwise open the scope and get the TTL RS232 port connected to your PC, see around second page of this thread.
Stupid Muppet Bricked their scope Suggestions Welcome
Hello all, I used the USB boot file "3ka_v241_linkinstall.cab" with the intention of "cough, cough" upgrading my scope.
I thought I'd upgraded my scope to 2.41, but like a complete numpty, I didn't check, it was, in fact, running 2.37.
So, now I have a bricked scope. It loads, shows the boot screen, then black screen with "Agilent Technoliges", then the screen goes blank.
Any suggestions on how to unbrick it?
You can try to prepare complete firmware on USB flash drive and boot from it (use same FW 2.37).
Otherwise you needs to disassemble scope and use PA0PBZ tool....
If you have new scope I will rather try to contact official support, rather than loosing warranty.
Just got a 2022A, used the 3ka_v241_linkinstall.cab and scope is bricked. Scope does have 2.41 firmware.
I#m assuming its due to the .lnk file not being the correct length as per previous posts. (#63 instead of #62).
I do have a LAN card but cant get a telnet connection. I've tried rebooting with the base 2.41 firmware and it hangs on the keysight logo screen. From here I can ping the scopes IP address, but still cant get a Telnet session.
Ideas?
Ouch - based on PA0PBZ's experience you will need to to open it up and connect to the serial port so you can load a file off the network. Once the file is loaded you will be able to telnet in, remove the link file that was added and reboot which should get you right back to an unmodified version 2.41. His experience is detailed over the past two pages or so.
Just got a 2022A, used the 3ka_v241_linkinstall.cab and scope is bricked. Scope does have 2.41 firmware.
I#m assuming its due to the .lnk file not being the correct length as per previous posts. (#63 instead of #62).
I do have a LAN card but cant get a telnet connection. I've tried rebooting with the base 2.41 firmware and it hangs on the keysight logo screen. From here I can ping the scopes IP address, but still cant get a Telnet session.
Ideas?
OUCH, you used the version for 3k series
Can you open scope or it has any warranty sticker? First I will try USB boot and in case it will fail dismantle scope and upload FW by PA0PBZ tool.
Description how to make USB bootable flash is almost on beginning of this thread. You do not need any hacked files, just extract files from 2.41 firmware.
Do not give up in case first flash will not work and try faster USB drive.
Just got a 2022A, used the 3ka_v241_linkinstall.cab and scope is bricked. Scope does have 2.41 firmware.
I#m assuming its due to the .lnk file not being the correct length as per previous posts. (#63 instead of #62).
I do have a LAN card but cant get a telnet connection. I've tried rebooting with the base 2.41 firmware and it hangs on the keysight logo screen. From here I can ping the scopes IP address, but still cant get a Telnet session.
You probably have the same problem I had, 2 links in the folder so the scope is trying to run 2 instances of the infiniivision executable. See this post how I fixed it:
https://www.eevblog.com/forum/testgear/dsox2000-and-3000-series-licence-have-anyone-tried-to-hack-that-scope/msg1022248/#msg1022248A few posts below that I attached the tool, and the howto for the RS232 connection can be found somewhere around page 2 of this thread.
Edit: the length (#) is not the problem, as far as I can see it is not even checked.
OUCH, you used the version for 3k series
AFAIK that is perfectly fine, I've seen a post of someone who did exactly that and succeeded.
Can you open scope or it has any warranty sticker? First I will try USB boot and in case it will fail dismantle scope and upload FW by PA0PBZ tool.
Description how to make USB bootable flash is almost on beginning of this thread. You do not need any hacked files, just extract files from 2.41 firmware.
Do not give up in case first flash will not work and try faster USB drive.
Version 2.41 will not boot from USB.
Thanks for that PAOPBZ, saw your previous posts on this. Think i've got a RS232 knocking around somewhere. Sigh....
Just so that ive got it straight, you cant boot 2.41 from USB?
Thanks for that PAOPBZ, saw your previous posts on this. Think i've got a RS232 knocking around somewhere. Sigh....
Just so that ive got it straight, you cant boot 2.41 from USB?
If you have a 2.41 scope it will not boot from USB, not sure if it is the firmware, an updated bootloader or something else. So... you can boot 2.41 from USB as long as your scope has a previous firmware version, but the "boot from USB" no longer works in the current firmware.
Edit: Please note that the RS232 is 3.3V level, not RS232 level.
OUCH, you used the version for 3k series
AFAIK the firmware files for 2000 and 3000 series are the same - this will not be the problem.
PAOPBZ,
What term package did you use? Im trying HTERM (recommended earlier in the thread) and I cant get it to pause the boot process.
This is the error its giving though:-
Performing Startup
Exception 'Raised E|ception' (-1-:Thread-Id=05d5000a(pth=84a19000), Proc-Id=05d4000a(pprc=8419cb08) 'infiniivisionlauncher.exe', VM-active=05d4000a(pprc=8419cb08) 'infiniivisionlauncher.exe'
PC=40068ag0(coredll.dll+0x00058ae0) RA=803782c8(kernel.dll+0x000062c8) SP=0002f9b0, BVA=0002fabc
PARSE ERROR: Argument: â¬l
$ Couldn't find match for argument
As per your experience it then goes into a loop with this:-
ERROR: c:\WINCE600\3RDPARTY\Agilent\HPP\Common\Drivers\sh600_serial\.\sh600_serial_drv.cpp line 661: SER2 SER Driver: does not support multiple Open()'s
OUCH, you used the version for 3k series
AFAIK the firmware files for 2000 and 3000 series are the same - this will not be the problem.
Just confirming... I did a compare on 2000XSeries.02.41.2015102200.cab and 3000XSeries.02.41.2015102200.cab. They are identical.
PAOPBZ,
What term package did you use? Im trying HTERM (recommended earlier in the thread) and I cant get it to pause the boot process.
This is the error its giving though:-
Performing Startup
Exception 'Raised E|ception' (-1-:Thread-Id=05d5000a(pth=84a19000), Proc-Id=05d4000a(pprc=8419cb08) 'infiniivisionlauncher.exe', VM-active=05d4000a(pprc=8419cb08) 'infiniivisionlauncher.exe'
PC=40068ag0(coredll.dll+0x00058ae0) RA=803782c8(kernel.dll+0x000062c8) SP=0002f9b0, BVA=0002fabc
PARSE ERROR: Argument: â¬l
$ Couldn't find match for argument
As per your experience it then goes into a loop with this:-
ERROR: c:\WINCE600\3RDPARTY\Agilent\HPP\Common\Drivers\sh600_serial\.\sh600_serial_drv.cpp line 661: SER2 SER Driver: does not support multiple Open()'s
Hi Dean,
I use PuTTY
http://www.chiark.greenend.org.uk/~sgtatham/putty/download.htmlStart sending <space> at the very moment you turn on the scope. What do you see on the serial port when the scope is switched on?