Hello Everybody
I work in a school and we have 3 BK2190 oscilloscopes that stay stuck in the on-screen. Is there a way to update the firmware or apply an hardware reset?
I found this post https://www.eevblog.com/forum/repair/bk-precision-2190e-stuck-in-boot-screen/msg3647065/#msg3647065
but it doesn´t work for me.
Can somebody help me please?
Only with the recovery package listed in that thread.
Read, understand and follow the PDF instructions exactly.
2190E is a SDS1102CNL+ but at glance the BK recovery package appears identical to the CNL+ one from Siglent.
Getting the USB stick configured correctly and it being 8GB or smaller is of highest importance for the recovery process to work.
Try several 8GB or smaller USB sticks until you find the one that works. Those with an activity LED are most useful to see the files are being transferred over.
There is also this:
https://siglentna.com/operating-tip/oscilloscope-hardware-reset/
Thanks for your reply.
I have formatted the usb in FAT32 mode and pasted the 3 files in the root, my usb is 1GB but hasn't LED. I'll try with another one.
Bad news!
The USB doesn't turn the LED on.
I think the oscilloscopes are beyond repair!
Bad news!
The USB doesn't turn the LED on.
I think the oscilloscopes are beyond repair!
Maybe not, we have some other tools.
When I have some spare time I can contact you to get your email and we'll try another line of attack !
Hello. I've got two 2190e scopes that have this same issue as E_Sosa posted above. I've tried the USB drive with the recovery_by_USB_driver files, and have also tried the method of pressing MATH repeatedly upon power up, both to no avail. If any of you have other tips, I would be excited to hear them. Thanks!
Hello. I've got two 2190e scopes that have this same issue as E_Sosa posted above. I've tried the USB drive with the recovery_by_USB_driver files, and have also tried the method of pressing MATH repeatedly upon power up, both to no avail. If any of you have other tips, I would be excited to hear them. Thanks!
Welcome to the forum.
The USB stick and how it's configured is the key to success.
It must be max 8GB, formatted in FAT32 4k clusters and suitable for bootable application.
The recovery files must also be in the root of the drive.
Multiple attempts are sometimes required as is using a different USB stick.
Thanks tautech. I'll give a few more usb sticks a try. I've tried two so far to no avail, both 8GB, both formatted to be FAT32 and both with the recovery files in the root of the USB stick. I've got a few more sticks I can try.
Thanks tautech. I'll give a few more usb sticks a try. I've tried two so far to no avail, both 8GB, both formatted to be FAT32 and both with the recovery files in the root of the USB stick. I've got a few more sticks I can try.
Ideally you want a stick with an activity LED to see the files being transferred over then give it some time to rebuild the OS before it can continue on to boot.
It should be quick but not instant so give it time to do its thing.
Life got busy so it took me a while to get back to this. Trying several different USB sticks helped. After trying several USB stickss (all <8GB) I found an old 256MB stick and that finally worked... for one of my two frozen scopes. The other scope does not respond in any way to the recovery USB stick in that the USB stick shows no activity at all when plugged in. I'm going to try the USB-B on the rear of the oscilloscope once I receive a USB-A to USB-B adapter. Will report back after that's done.
Thanks for the suggestions!
Life got busy so it took me a while to get back to this. Trying several different USB sticks helped. After trying several USB stickss (all <8GB) I found an old 256MB stick and that finally worked... for one of my two frozen scopes. The other scope does not respond in any way to the recovery USB stick in that the USB stick shows no activity at all when plugged in. I'm going to try the USB-B on the rear of the oscilloscope once I receive a USB-A to USB-B adapter. Will report back after that's done.
Thanks for the suggestions!
Good, you got one working.
Is there any chance the other is older and was running on an older firmware version ?
We may need to use a different recovery process.
Slightly off topic, but might be useful. I have a B&K 2190 completely different earlier unit, but the soldering was so bad - one channel blew a dual mosfet at the input. Also some of the board interconnector’s pins pulled right out of the board connectors - probably this set escaped being inspected before it was packed in the box.
Steven
It is possible that one has older firmware than the other. I purchased two batches of these oscilloscopes, separated by about a year. I don't know which batch each of these oscilloscopes came from.
What would this different recovery process entail? Is there any harm to trying it?
It is possible that one has older firmware than the other. I purchased two batches of these oscilloscopes, separated by about a year. I don't know which batch each of these oscilloscopes came from.
What would this different recovery process entail? Is there any harm to trying it?
Opening it. No harm at all but the process is more complex.
Continue with email.
PM sent with contact info. Thanks!
The reset worked for me! Great! Of course... after I disassembled the whole scope to check all wire connections, etc... (hw guy...)
I guess I should update the firmware - or is that going to risk another boot-up hang?
The reset worked for me! Great! Of course... after I disassembled the whole scope to check all wire connections, etc... (hw guy...)
I guess I should update the firmware - or is that going to risk another boot-up hang?
Welcome to the forum.
FW updates never brick scopes.
If you used the latest USB recovery method you should already have the latest FW version installed, V6.01.01.25
I actually have the BK 2190D - where can I find the latest firmware for that? I have 5.01.02.22R5.
Thx!!
I actually have the BK 2190D - where can I find the latest firmware for that? I have 5.01.02.22R5.
Thx!!
BK would be your first port of call.
BK D model has 40kPts mem depth which makes it equivalent to older CNL models (without LAN) for which there is no recent firmware.
Repeatedly pushing the MATH button during power-up worked for me (after a few tries).