East Tester ET4410&ET4510 Desktop LCR Meter

[Martin72]

And......Fits.

Tried it today with the J-Link, nothing happens in either SWD or JTAG mode.
The signals themselves are static (measured with an oscilloscope).
Only the communication between the two controllers is given, but that was clear.
With a bit of bad luck, the inputs are "tight", which can be determined in advance.
I haven't quite given up on it yet.
The memory area, which must contain the model of the front, is not overwritten by the firmware, otherwise there could not be the same firmware for different types.
You just have to find out where.
I don't know how much time I'll put into it.

[Martin72]

Hi,

Comparison between ET44/4510 and three others...
https://www.eevblog.com/forum/testgear/east-tester-et3502-lcr-bridge/msg5570995/#msg5570995
They're really good, the two of them.
But you might want to consider buying other test leads.

[axb]

Hi,

Maybe someone would be able to help me.

Using all possible tips from this topic, I am doing a firmware update of my ET4410 (bought in Jan 2022). Unfortunately the device still does not want to start working, I keep getting a black screen. The progress bar reaches 100% and nothing happens. Bootloader works all the time, I have repeated this process many times.

I have no idea what to do anymore....

[w.v.s.]

Hello an welcome,

how long did you wait for the reboot after the update? I did not update yet, because I want to try some jtag stuff before, but I think that could be a factor. Good luck and a nice weekend!

[Martin72]

If the update was successful, the system reboots relatively quickly and by itself.
If the screen remains black, something went wrong.
But all is not lost, the system is just “hung”.
In the end, I was able to successfully upgrade the ET4410 and ET4510.

[w.v.s.]

And did you check if your hex file is correct and complete?

[axb]

Thank you for your responses.

I decided to try this update, because pressing the calibration button had no effect. Unfortunately, I was left with a brick.

how long did you wait for the reboot after the update?

For a long time, even many hours.

And did you check if your hex file is correct and complete?

No. How can I do it?

In contrast, I have tried to successfully invoke entry to the booloader from the terminal, but this does nothing. It [1] clears the flash, as in this program, [2] by itself nothing, maybe it waits for the program bytes, [?] displays this menu again.

[Martin72]

What firmware did you try to install?

[axb]

What firmware did you try to install?

I have used this firmware:
https://www.123pan.com/s/2Y9Djv-ZCcvH.html

[w.v.s.]

[2] by itself nothing, maybe it waits for the program bytes.

As far as i remember this is true and the data is directly transmitted in the hex encoding of that firmware file (after erasing the flash and selecting 2, there were dumps posted in this thread). You can unzip the file again and see if it is identical or you can determine the md5 sum, post it and we can tell you if we have the same checksum.

[axb]

[2] by itself nothing, maybe it waits for the program bytes.

You can unzip the file again and see if it is identical or you can determine the md5 sum, post it and we can tell you if we have the same checksum.

I downloaded again, extracted, it is identical.

Size: 594663

MD5: BD3DD611147587DBCE5F4AA75F8F88D9

[Martin72]

If you started the update procedure as usual, via RS232/USB and then with the upgrade tool, then all is not lost.
I had the black screen for “days” and was convinced that the device was broken.
But at some point it had worked.

[axb]

If you started the update procedure as usual, via RS232/USB and then with the upgrade tool, then all is not lost.
I had the black screen for “days” and was convinced that the device was broken.
But at some point it had worked.

Thanks for keeping me hopeful, but I think that some reason for this revival was there after all. Unfortunately for me, you probably just didn't see it.

[Martin72]

I probably didn't see it either, because you can't see anything, I couldn't translate the characters.
Again, if you haven't done anything to the ET4410 other than use the update tool, then it's not broken.
I can offer to try it, but you would have to pay for the shipping costs, there and back.
If you're interested, PM me.

[w.v.s.]

Here are the md5sums of my files

Code: [Select]

7c2467758736f97a7305848db0d22db4 V6.00.2423.059.hex
bd3dd611147587dbce5f4aa75f8f88d9 ET44_V6.00.2409.049.hex
Each line of these intel-hex files also contains a checksum. So you can check if the file is self-consistent. The odds, that your file is broken are not very high, but it could explain the behavior. I also assume that you use a good serial cable (shielded, not too long), so that transfer errors are less likely.

[w.v.s.]

I decided to try this update, because pressing the calibration button had no effect. Unfortunately, I was left with a brick.

By the way. As far as I remember (I don't have the device next to me right now) this is also a question of timing. That button does not react immediately, but after a few (<=3) seconds.

[axb]

Here are the md5sums of my files

Code: [Select]

7c2467758736f97a7305848db0d22db4 V6.00.2423.059.hex


Is this version also for ET4410?

I also assume that you use a good serial cable (shielded, not too long), so that transfer errors are less likely.

Yes, the RS-232 cable I have is a bit long and not shielded. Consequently, I connected my ET4410 directly to the PC motherboard using tape and a plug from the case's herring.
The difference is very big:
1. the progress bar starts by itself, no need to push it with the pause button.
2. the upload time started to be me about the same as yours, which is 353s. Previously it ranged from 197s-202s.
But it still did nothing, the screen as it was black, so it still is 

[axb]

I probably didn't see it either, because you can't see anything, I couldn't translate the characters.

It is Chinese (GB18030). E.g. Sublime by command "Reopen with Encoding" converts it without any problems.

[w.v.s.]

7c2467758736f97a7305848db0d22db4 V6.00.2423.059.hex

A Is this version also for ET4410?

B The difference is very big:
1. the progress bar starts by itself, no need to push it with the pause button.
2. the upload time started to be me about the same as yours, which is 353s. Previously it ranged from 197s-202s.
But it still did nothing, the screen as it was black, so it still is 

A: to my knowledge, yes. I think Martin installed that one with success, too.
B: Sounds like progress to me. Maybe give it two more tries that way.

[Martin72]

@axb:

https://www.eevblog.com/forum/testgear/east-tester-et4410-desktop-lcr-meter/msg5541289/#msg5541289

And following...
I had the same problem.

[axb]

B: Sounds like progress to me. Maybe give it two more tries that way.

It sounds like progress to me, too, of course, but, funny enough, I've tried it a dozen times. Different port speeds, both in data.ini and in the device manager (COM port). Also Delay=0 (penultimate option). Without and with “Locale Emulator” (it prints out a couple of lines of date messages at the end, dashes, dots, the word “file”).

I will still try, of course. Maybe another PC, maybe USB-RS 232.

[axb]

I bypassed the internal MAX202 and the internal tape and connected directly through CP2104. I also tried from another PC. I think this way I have exhausted the subject of transmission errors. Unfortunately, the screen remains black....

[w.v.s.]

I bypassed the internal MAX202 and the internal tape and connected directly through CP2104. I also tried from another PC. I think this way I have exhausted the subject of transmission errors. Unfortunately, the screen remains black....

Does not sound good. The hex files do not contain the whole firmware. Maybe some data is corrupt in an address range, that you don't have overwritten a hundred times. The next thing, I would probably do in your position, is to talk to the device via USB (or RS232) to find out, if it does not boot at all, or if it generally working but the display is not initialized properly.Other thing i am thinking about is addressing the µC via ST-link. I plan to do some test on this, but this is not high priority and I would expect to do this in December, maybe even later.

[axb]

Or maybe my problems are from having an old version? Both boards have F103. Martin, what address did you write to East Tester?

The next thing, I would probably do in your position, is to talk to the device via USB (or RS232) to find out, if it does not boot at all, or if it generally working but the display is not initialized properly.

USB\DEVICE_DESCRIPTOR_FAILURE

[Martin72]

I had contacted Easttester directly via their homepage.
Do you know this post:
https://www.eevblog.com/forum/testgear/east-tester-et4410-desktop-lcr-meter/msg5554217/#msg5554217

This is the latest firmware for ET44/45...