| Products > Test Equipment |
| EEVBlog 121GW Multimeter Firmware Details |
| << < (8/62) > >> |
| exe:
chefkoch84, thanks for providing decompiled FW. Do you know how to compile it back? I believe this should be possible. Unfortunately, I don't have much experience with ARM (I do software for web-servers). So, I picked some random gcc flags used by CubeMX from one of my old project, gcc still complains. I don't bother with missing main function (I believe it just has a wrong name), but I'm worried about other functions missing. How come they are not present in the code? I also tried snowman, another ARM decompiler, but it seems it expects and ELF executable, not raw FW binary :(. Too bad, that tool produced a useful result to me. May be it's time to roll a completely new FW written from scratch? I'll try to start with an empty CubeMX project... when time permits. Since now we have schematics it should be relatively easy to create a proof of concept (I'm not talking about correct measurements or display working). --- Code: ---arm-none-eabi-gcc -mthumb -mcpu=cortex-m4 -mfpu=fpv4-sp-d16 -mfloat-abi=hard --specs=nosys.specs ./EEVBlog.c (.text+0x44): undefined reference to `main' /tmp/ccgtjcep.o: In function `function_117dc': EEVBlog.c:(.text+0x21f0a): undefined reference to `unknown_117bc' /tmp/ccgtjcep.o: In function `function_158ec': EEVBlog.c:(.text+0x294c4): undefined reference to `unknown_ff696e8c' EEVBlog.c:(.text+0x299dc): undefined reference to `unknown_ff696ed4' EEVBlog.c:(.text+0x299e4): undefined reference to `unknown_ff397cfc' /tmp/ccgtjcep.o: In function `function_16ac0': EEVBlog.c:(.text+0x367d6): undefined reference to `unknown_fff9a9c0' EEVBlog.c:(.text+0x36812): undefined reference to `unknown_fff982e8' /tmp/ccgtjcep.o: In function `function_1a4e8': EEVBlog.c:(.text+0x43928): undefined reference to `unknown_fff9b7bc' /tmp/ccgtjcep.o: In function `function_1b872': EEVBlog.c:(.text+0x48054): undefined reference to `unknown_110c4c' EEVBlog.c:(.text+0x48060): undefined reference to `unknown_ffe3ac50' EEVBlog.c:(.text+0x48068): undefined reference to `unknown_fff71c54' EEVBlog.c:(.text+0x48074): undefined reference to `unknown_ff6b4c58' EEVBlog.c:(.text+0x4807c): undefined reference to `unknown_ff801c5c' EEVBlog.c:(.text+0x4809e): undefined reference to `unknown_fff59c60' /tmp/ccgtjcep.o: In function `function_1beee': EEVBlog.c:(.text+0x48934): undefined reference to `unknown_1bf4c' collect2: error: ld returned 1 exit status --- End code --- |
| exe:
I just sacrificed one meter, the chip is STM32L152ZDT6 . Too bad this is not specified on schematic. UP: looks like LCD is driven directly. So, no fancy proprietary drivers or something. Damn, wtf UEI does not release their crappy firmware opensource, I don't believe it is too difficult to write a firmware. |
| firewalker:
We knew the mcu part number. https://www.eevblog.com/forum/testgear/eevblog-121gw-multimeter-issues/msg1406994/#msg1406994 Alexander. |
| exe:
That's the problem, information is spread all over three threads :(. Unfortunately, I don't follow all of them, nor I have enough memory to remember who said what and where. Anyway, following the instructions here I have openocd working: --- Code: ---Escape character is '^]'. Open On-Chip Debugger > dump_image dump.bin 0x08000000 0x1ffff dumped 131071 bytes in 6.293624s (20.338 KiB/s) --- End code --- I'll try to make a hello world over weekend, if time permits. Although, I don't mind if somebody else will do this ahead of me. |
| cwalex:
Does anyone know if there has been an official firmware update released that fixes the slow auto range we can download and use to update our multimeters? It would be nice if there was a support web page that we could go to for news and updates on current issues being worked on and official updates, instructions, info, etc. Does a page like this exist yet? |
| Navigation |
| Message Index |
| Next page |
| Previous page |