dosis_r, What frequency is the quartz set to in your clone? You need to find or configure firmware for the same frequency.
If I'm not mistaken, dosis_r seems to run a firmware compiled for 8 MHz on an ATmega with a 16 MHz clock.
I got the firmware also from this forum and used an Atmega 328P MCU.
I hope friends on this forum can give me an explanation or teach me how to fix this problem..
This is my firmware, but you must indicate the name of the archive you installed.
It is necessary to find out the frequency indicated on the quartz, indicated by the red arrow. For example, I highlighted the incorrect values in Show data. What is not clear is the blue background, this is a BGR display, but it looks like 16 MHz quartz?
On displays released in 2022, the 16 MHz firmware did not work. You can try it on your display...
dosis_r, What frequency is the quartz set to in your clone? You need to find or configure firmware for the same frequency.
I don't know sir, maybe is 16000MHz Xtal..
Because the component doesn't have a marking (only AG), I bought the ESR from local store in here.
Seller doesn't have response my message.
If I'm not mistaken, dosis_r seems to run a firmware compiled for 8 MHz on an ATmega with a 16 MHz clock.
Maybe sir, Because I just downloaded the firmware from this forum then tried it and it worked, only the capacitor reading was not correct. I can't choose an accurate firmware because my ESR doesn't have marking on Xtal component..
This is my firmware, but you must indicate the name of the archive you installed.
On displays released in 2022, the 16 MHz firmware did not work. You can try it on your display...
Hi Sir,
I want to thank you in advance, and sorry if I use your firmware without your permission first. I bought this ESR because the test results display were good and it all turned out to be your work.
I use the firmware with the name
ST7735_RGB_en.zip and attached are some of the firmware that I have downloaded to try to get my ESR back on. Thanks for your new firmware and I will try it as soon as possible..
I use the firmware with the name ST7735_RGB_en.zip and attached are some of the firmware that I have downloaded to try to get my ESR back on. Thanks for your new firmware and I will try it as soon as possible..
This firmware has not been tested with your display, errors may occur. First you need to show the Selftest results and Show data. Using film capacitors 470 nF - 1000 nF and 10 nF - 20 nF for the resonant method of measuring inductances.
This firmware has not been tested with your display, errors may occur. First you need to show the Selftest results and Show data. Using film capacitors 470 nF - 1000 nF and 10 nF - 20 nF for the resonant method of measuring inductances.
Okay sir,
I have tested the new firmware that you provided and the results are quite good, the firmware is able to read Capacitor :
1. 220nF (Mutimeter) = 215nF (ESR Meter)
2. 10nF (Multimeter) = 9.7nF (ESR Meter)
I haven't been able to test the 470nF-1000nF capacitor because it doesn't have a components, maybe tomorrow I can get it.
It's just that the previous firmware display (RGB) was what appeared when I first got this ESR Meter. The appearance is different from the BGR Firmware you provided.
Attached is the result of show data using your new firmware. Thank You..
Now the readings are normal. You don't have to look for 470-1000 nF.
I now see that the
RGB display, the colors are mixed up. You need to install this firmware...
Hi guys,
Sorry for such delay, but here it is - updated ISO 8859-2 Polish translation file
v1.52m
...
- Added option to optimize the interrupt vector table to reduce firmware size (Makefile: OPTIMIZE_VECTORS, thanks to Viktor Klimkovich).
...
This option doesn't work correctly with my avr-gcc version 8.3.0, version 5.4.0 (the debian stable default), 7.3.0, and 13.2.0 work as expected.
This is what I get with avr-gcc-8.3.0:
.section .vectors,"ax",@progbits
.global __vectors
.func __vectors
__vectors:
XJMP __init // __vectors[0]
0: 0c 94 23 0e jmp 0x1c46 ; 0x1c46 <__ctors_end>
.altmacro
.set i,1
.rept 127 // __vectors[1..127]
vector %i
.set i,i+1
.endr
4: 0c 94 00 2e jmp 0x5c00 ; 0x5c00 <__bad_interrupt>
8: 0c 94 00 2e jmp 0x5c00 ; 0x5c00 <__bad_interrupt>
c: 0c 94 00 2e jmp 0x5c00 ; 0x5c00 <__bad_interrupt>
10: 0c 94 00 2e jmp 0x5c00 ; 0x5c00 <__bad_interrupt>
14: 0c 94 00 2e jmp 0x5c00 ; 0x5c00 <__bad_interrupt>
18: 0c 94 00 2e jmp 0x5c00 ; 0x5c00 <__bad_interrupt>
1c: 0c 94 00 2e jmp 0x5c00 ; 0x5c00 <__bad_interrupt>
20: 0c 94 00 2e jmp 0x5c00 ; 0x5c00 <__bad_interrupt>
24: 0c 94 00 2e jmp 0x5c00 ; 0x5c00 <__bad_interrupt>
28: 0c 94 00 2e jmp 0x5c00 ; 0x5c00 <__bad_interrupt>
2c: 0c 94 00 2e jmp 0x5c00 ; 0x5c00 <__bad_interrupt>
30: 0c 94 00 2e jmp 0x5c00 ; 0x5c00 <__bad_interrupt>
34: 0c 94 00 2e jmp 0x5c00 ; 0x5c00 <__bad_interrupt>
38: 0c 94 00 2e jmp 0x5c00 ; 0x5c00 <__bad_interrupt>
3c: 0c 94 00 2e jmp 0x5c00 ; 0x5c00 <__bad_interrupt>
40: 0c 94 00 2e jmp 0x5c00 ; 0x5c00 <__bad_interrupt>
00000044 <__trampolines_end>:
while e.g. ver 13 gives:
.section .vectors,"ax",@progbits
.global __vectors
.func __vectors
__vectors:
XJMP __init // __vectors[0]
0: 0c 94 23 0e jmp 0x1c46 ; 0x1c46 <__ctors_end>
00000004 <.Loc.1>:
.altmacro
.set i,1
.rept 127 // __vectors[1..127]
vector %i
4: 0c 94 55 2e jmp 0x5caa ; 0x5caa <__bad_interrupt>
8: 0c 94 55 2e jmp 0x5caa ; 0x5caa <__bad_interrupt>
c: 0c 94 55 2e jmp 0x5caa ; 0x5caa <__bad_interrupt>
10: 0c 94 55 2e jmp 0x5caa ; 0x5caa <__bad_interrupt>
14: 0c 94 55 2e jmp 0x5caa ; 0x5caa <__bad_interrupt>
18: 0c 94 55 2e jmp 0x5caa ; 0x5caa <__bad_interrupt>
1c: 0c 94 fb 2d jmp 0x5bf6 ; 0x5bf6 <__vector_7>
20: 0c 94 55 2e jmp 0x5caa ; 0x5caa <__bad_interrupt>
24: 0c 94 55 2e jmp 0x5caa ; 0x5caa <__bad_interrupt>
28: 0c 94 55 2e jmp 0x5caa ; 0x5caa <__bad_interrupt>
2c: 0c 94 17 2e jmp 0x5c2e ; 0x5c2e <__vector_11>
30: 0c 94 55 2e jmp 0x5caa ; 0x5caa <__bad_interrupt>
34: 0c 94 55 2e jmp 0x5caa ; 0x5caa <__bad_interrupt>
38: 0c 94 55 2e jmp 0x5caa ; 0x5caa <__bad_interrupt>
3c: 0c 94 55 2e jmp 0x5caa ; 0x5caa <__bad_interrupt>
40: 0c 94 05 2e jmp 0x5c0a ; 0x5c0a <__vector_16>
00000044 <Inductor_table>:
...
This change fixes the behaviour for ver 8.3.0:
diff --git a/gcrt1.S b/gcrt1.S
index 71689db..dad52e1 100644
--- a/gcrt1.S
+++ b/gcrt1.S
@@ -70,7 +70,7 @@
.macro vector i
.if (. - __vectors <= last_used_vector*4)
.weak __vector_\i
- .set __vector_\i, __bad_interrupt
+ // .set __vector_\i, __bad_interrupt
XJMP __vector_\i
.endif
.endm
EDIT: After this "fix" I get:
.section .vectors,"ax",@progbits
.global __vectors
.func __vectors
__vectors:
XJMP __init // __vectors[0]
0: 0c 94 23 0e jmp 0x1c46 ; 0x1c46 <__ctors_end>
.altmacro
.set i,1
.rept 127 // __vectors[1..127]
vector %i
.set i,i+1
.endr
4: 0c 94 00 00 jmp 0 ; 0x0 <__vectors>
8: 0c 94 00 00 jmp 0 ; 0x0 <__vectors>
c: 0c 94 00 00 jmp 0 ; 0x0 <__vectors>
10: 0c 94 00 00 jmp 0 ; 0x0 <__vectors>
14: 0c 94 00 00 jmp 0 ; 0x0 <__vectors>
18: 0c 94 00 00 jmp 0 ; 0x0 <__vectors>
1c: 0c 94 00 2e jmp 0x5c00 ; 0x5c00 <__vector_7>
20: 0c 94 00 00 jmp 0 ; 0x0 <__vectors>
24: 0c 94 00 00 jmp 0 ; 0x0 <__vectors>
28: 0c 94 00 00 jmp 0 ; 0x0 <__vectors>
2c: 0c 94 d8 2d jmp 0x5bb0 ; 0x5bb0 <__vector_11>
30: 0c 94 00 00 jmp 0 ; 0x0 <__vectors>
34: 0c 94 00 00 jmp 0 ; 0x0 <__vectors>
38: 0c 94 00 00 jmp 0 ; 0x0 <__vectors>
3c: 0c 94 00 00 jmp 0 ; 0x0 <__vectors>
40: 0c 94 ee 2d jmp 0x5bdc ; 0x5bdc <__vector_16>
00000044 <__trampolines_end>:
Slightly different, but not an issue b/c also "__bad_interrupt" jumps to address 0:
00005c64 <__bad_interrupt>:
.global __bad_interrupt
.func __bad_interrupt
__bad_interrupt:
.weak __vector_default
.set __vector_default, __vectors
XJMP __vector_default
5c64: 0c 94 00 00 jmp 0 ; 0x0 <__vectors>
This "fix" works with all my available avr-gcc versions 5.4.0, 7.3.0, 8.3.0, and 13.2.0
EDIT2: corrected the debian stable version (5.4.0)
Now the readings are normal. You don't have to look for 470-1000 nF.
I now see that the RGB display, the colors are mixed up. You need to install this firmware...
Oke Sir, Thanks You..
Now my ESR is working again as it should...
:
Thank you very much for your help and all the friends here...
Hello everyone.
Who doesn't find it difficult, please compile the firmware for my device for quartz 8 MHz and 16 MHz, the interface language is English and Russian?
Greetings to all. The LCR TC-1 v2.0 transistor tester has a U5 chip labeled AL816. Does anyone know what kind of chip it is?
That should be the SD6271 boost converter.
Who doesn't find it difficult, please compile the firmware for my device for quartz 8 MHz and 16 MHz, the interface language is English and Russian?
I don't recognize your tester model. Do you have any more details?
Who doesn't find it difficult, please compile the firmware for my device for quartz 8 MHz and 16 MHz, the interface language is English and Russian?
I don't recognize your tester model. Do you have any more details?
The device is assembled according to this scheme
Yes, the firmware size shouldn't exceed 100%. Disable one or two features you don't need (e.g. SW_UJT) to reduce the size.
Hello everyone.
Who doesn't find it difficult, please compile the firmware for my device for quartz 8 MHz and 16 MHz, the interface language is English and Russian?
Please find attached the AY-AT versions for 8, 16 and 20 MHz based on my setup for 1.52m.
Setup can be found in my repo:
https://github.com/Ho-Ro/ComponentTester/tree/AY-AT_20MHz
Hi I bought LCR T4, but is different then my old one, I want to change firmware, but board is v.4.1.3 and no pinot to hook programer.
Anyone see this board?
Thanks
Your picture is too blurry. I can't see the writing on the MCU to even know what it is...