| Electronics > Repair |
| Fluke 289 not quite sorted. |
| << < (45/49) > >> |
| MihaiV:
Congratulations, hope you enjoy the meter for a long time! May I ask what flash contents and what component part number you used? You used the Jlink or another programmer? Thanks, Mihai V. |
| maximalcho:
First I used dump from kjk24 (thank you kjk24) reply #153 and program last dump from archive (_ok_0x10000000-0x101E0010).Multimeter start but not fully load (my multimeter was fully dead) then i program dump from AnJu (Спасибо AnJu ) reply #83 and thadaaa the multimeter came back to life.And because the АnJu dump is from 287 and mine is 289, I made an official update for 289 via the Ir port just in case.I used the jlink programmer and I ordered the flash ic from digikey https://www.digikey.bg/en/products/detail/alliance-memory-inc/PC28F640P30TF65A/13543373. PS:To make connection with Jlink LCD must be connected ! Оtherwise mxs is in sleep mode and no connection can be made. |
| maximalcho:
One more thing.First when i program dump from kjk24 my multimeter stuck at the same screen like yours from reply #166.You can try to program with jlink a dump from AnJu and if you are lucky the multimeter will come to life. |
| MihaiV:
Hello, Thank you! I tried today something. Here goes: I managed to connect to the target using Jflash and the configuration file from post #163, from kaiser. The log output is: --- Code: ---Connecting ... - Connecting via USB to probe/ programmer device 0 - Probe/ Programmer firmware: J-Link Pro V4 compiled Sep 24 2021 16:41:59 - Device "ARM7" selected. - Target interface speed: 30 kHz (Fixed) - VTarget = 3.071V - TotalIRLen = 4, IRPrint = 0x01 - JTAG chain detection found 1 devices: - #0 Id: 0x1092001D, IRLen: 04, ARM920T Core - Identified core does not match configuration. (Found: ARM9, Configured: ARM7) - CP15.0.0: 0x41129200: ARM, Architecture 4T - CP15.0.1: 0x0D172172: ICache: 16kB (64*8*32), DCache: 16kB (64*8*32) - Cache type: Separate, Write-back, Format A - Executing init sequence ... - Initialized successfully - Adaptive clocking not supported for selected CPU core. Only supported for -S cores. - Auto JTAG speed: 8000 kHz - Target interface speed: 8000 kHz (Auto) - Found 1 JTAG device. Core ID: 0x1092001D (None) - Connected successfully --- End code --- Next, I tried to read the flash contents: Target>Manual Programming>Read back>Entire chip. The response is: --- Code: ---Reading selected sectors ... - 67 of 67 sectors selected, 1 range, 0x10000000 - 0x107FFFFF - Start of determining flash info (Bank 0 @ 0x10000000) - End of determining flash info - Flash bank info: - 63 * 128 KB @ 0x10000000 - 4 * 32 KB @ 0x107E0000 - Start of preparing flash programming - ERROR: Failed to read back RAMCode for verification. - ERROR: Failed to prepare for programming. Failed to download RAMCode! - End of preparing flash programming - Start of restoring - End of restoring - ERROR: Failed to read back target memory Disconnecting ... - Disconnected --- End code --- And a warning message (photo 3). Next, I tried to connect using the command line (JLink commander). Connected ok and saved the entire contents of the flash using savebin command, starting from address 0x10000000. And it worked, i have a copy of the flash contents, from 0x10000000 to 0x107FFFFF. This means that the flash chip and the connections to it are ok. I attached it below. I checked its contents with the dump from AnJu, as indicated by maximalcho (Thansks!). They are very similar. I tried to check the RAM, as indicated by kjk24 in post 201, using the w4 and mem32 commands. However, there is no response. I tried with single bytes and I do not get an output. See photo 2. Reading works using the mem8 command on flash (see photo 1). The output fits with the contents i got using the savebin command. Does it mean i have a bad ram, or with bad connections? Is itpossible to brick the meter if I upload the contents from AnJu ("2.fs 0x10040000.bin" starting from address 0x10040000 and "3.FIS directory 0x107E0000.bin" from address 0x107E0000) and having a bad ram? Especially if using "Use target ram" option enabled? Thank you, MihaiV. |
| maximalcho:
Once you have a full dump on your flash chip I don't think you can brick the multimeter.If the ram is really damaged when trying to program flash it will probably give an error in the worst case the device will stop but when you change the ram you will be able to restore it.If you try to program flash and it doesn't work you may have tried to reball the memory or just to reflow.Try to change the core type in the configuration file because it is not correct at the moment, but keep in mind that when you change it you have to reconfigure the type of flash memory and its address. |
| Navigation |
| Message Index |
| Next page |
| Previous page |