Electronics > Repair
Fluke 289 not quite sorted.
<< < (33/49) > >>
kjk24:
some infos & thank to Kaiser

RedBoot Abort Pin E29 next to J4
pull it low with pulldown resistor for aborting Redboot to boot

SPLASH_BMP_FLASH_ADDR 0x107C0000

1. flash redboot only
2. fis init

--------------------
bootscript :

3. fconfig- l show config

4. fconfig -i
Initialize non-volatile configuration - continue (y/n)? y
Run script at boot: true
Boot script:
Enter script, terminate with empty line
>> fis unlock fs
>> fs mount -d /dev/flash/fis/fs -t jffs2 /
>> load -m file /system/apps/clem.img
>> fs umount /
>> go -c -n -w 10000
>>
Boot script timeout (1000ms resolution): 10
Use BOOTP for network configuration: false
Gateway IP address:
Local IP address:
Local IP address mask:
Default server IP address:
Console baud rate: 115200
DNS server IP address:
Set eth0 network hardware address [MAC]: false
GDB connection port: 9000
Force console for special debug messages: true
Console number for special debug messages: 0
Network debug at boot time: false
Update RedBoot non-volatile configuration - continue (y/n)? y

copy file to device:
load clem.img -r -b 0x00050000 -m ymodem
fs write -b 0x00050000 -l 0x003bd617 clem.img
RedBoot> fs list
   3 drwxr-xr-x  1 size      0 .
   2 drwxr-xr-x  1 size      0 ..
   4 -rwxr-xr-x  1 size 3921431 clem.img
RedBoot>

reset

SerialNumber @ 0x1DEB60

Rev015
without VR1,VR2 etc.
R121/125 assembeld ModellA
no Jumper ID's on Board

Rev020
without VR1,VR2 etc.
R121/125 assembeld ModellA
R277 (1K pulled down) assembeld ID0

Rev027
without VR1,VR2 etc.
R121/125 assembeld ModellA
R277 (1K pulled down) assembeld ID0
R278 (1K pulled down) assembeld ID1

Rev024
with VR1,VR2 etc.
R121/126 assembeld ModellB
R277 (1K pulled down) assembeld ID0
R278 (1K pulled down) assembeld ID1



kjk24:
for me the Project is finished, i repaired all my 3 dmm.
Thanks to Kaiser he help me a lot.

all infos on your own risk, you can damage your filesystem or calibration or whatever.
dont touch it if you dont sure what you do.

here some infos.

1. dmm switch on and the LCD flickers and not normal screen, check U19 voltages and R101
see attached pic
2. dmm switch on and the LCD hang with a bark, check SPI communication from MXS to MSP
3. dmm switch on and the LCD has additional lines on the screen check ram
4. dmm switch on and bootlogo hang, check clem.img or CRC on flashdrive

my fails on the units wars: LCD Voltage bad (R101) cracked, MXS CPU dead, Ram bad, flash bad, most annoying bad via under MXS (Mosi) to MSP, LCD brocken, batterie metall thing brocken on 2 units.

boot to redboot:
1K pulldown to E29 and switch on, type ctrl-C or space on RS232 Terminal ( i used extra putty)

check RAM:
 boot into redboot becorse the ram has to be initialised, try to read and write to ram or use J-MEM with the  (MC9328MXS.jflash file for initram) and write and read FF and 00 to 0x12000000-0x12FFFFFF

CRC:
 boot into redboot check for a message "somthing with CRC not correct" then some is with filesystem wrong.

clem.img: (extra putty with ymodem)
 boot into redboot and look for the clem.img if its there
>fis unlock fs
>fs mount -d /dev/flash/fis/fs -t jffs2 /
>fs cd /system/apps/
RedBoot> fs list
   6 drwxr-xr-x  1 size      0 .
   3 drwxr-xr-x  1 size      0 ..
 621 -rwxr-xr-x  1 size 3921431 clem.img
 596 -rwxr-xr-x  1 size 3922423 BackupClem.img

copy clem.img to flash via RS232 (115200 8N1 on J5):
 boot into redboot
 fis unlock fs
 fs mount -d /dev/flash/fis/fs -t jffs2 /
 fs cd /system/apps/
 fs list
 fs move clem.img BackupClem.img
 load clem.img -r -b 0x00050000 -m ymodem
 fs write -b 0x00050000 -l 0x003bd617 clem.img
 RedBoot> fs list
   6 drwxr-xr-x  1 size      0 .
   3 drwxr-xr-x  1 size      0 ..
 621 -rwxr-xr-x  1 size 3921431 clem.img
 596 -rwxr-xr-x  1 size 3922423 BackupClem.img
 RedBoot> reset

check redboot bootscript:
boot into redboot,
fconfig -l show config

change the bootscript with wait 10seconds to boot:
fconfig -i
Initialize non-volatile configuration - continue (y/n)? y
Run script at boot: true
Boot script:
Enter script, terminate with empty line
>> fis unlock fs
>> fs mount -d /dev/flash/fis/fs -t jffs2 /
>> load -m file /system/apps/clem.img
>> fs umount /
>> go -c -n -w 10000
>>
Boot script timeout (1000ms resolution): 10
Use BOOTP for network configuration: false
Gateway IP address: 0.0.0.0
Local IP address: 192.168.9.133
Local IP address mask: 255.255.0.0
Default server IP address: 192.168.100.100
Console baud rate: 115200
DNS server IP address: 0.0.0.0
Set eth0 network hardware address [MAC]: true
eth0 network hardware address [MAC]: 0x00:0x80:0x40:0x00:0x22:0x85
GDB connection port: 9000
Force console for special debug messages: true
Console number for special debug messages: 0
Network debug at boot time: false
Update RedBoot non-volatile configuration - continue (y/n)? y

LCD:
J3 (LCD)
1= +20V
2= +18.8V
3= +17.6V
4= +2.4V
5= +1.2V
6= GND
7= GND
8= ?
9-18= Data
19= +9V
20= ? Backlight
if Voltage not correct check R101 & U19


redboot found clem.img and booting it:


MSP Chip bad or communication to it bad:


redboot dont find clem.img bootloader hang:
[ Specified attachment is not available ]


Regards
Kai
goaty:
Wanted to add something I encountered, which might not have to do anything with the Fluke problems, but I thought it might fit:

I have a set of Mastech cable finder which use MSP430F135.

Both sender and receiver have a problem and did not start reliable.
I found that the decoupling caps are very very critical on the analog and digital supply lines.
In the sender, I managed to get it starting up after replacing the caps. Before it had excessive current draw. 3.3V regulator got hot and CPU was not running.

On the receiver it also does not start up, but caps replacement did not help.
I have the suspicion that the MSP430 is very sensitive.
kaiser:
Might come in handy for some..
Here is a J-Flash config setting to read and write to the flash with the use of Flukes onboard RAM which I used on my 289.

In the J-Flash CPU tab, tick "Use target RAM" : write time = approx 2min..
Not ticked write time = approx 5Hrs...... for each write :wtf:

J-Flash ARM V4.20a was used in this case.


K.
                         
nixxon:

--- Quote from: ElecSeb on October 23, 2018, 04:49:10 pm ---Update from my side:
(...)
@Nixxon:
If your unit is not doing anything anymore, check if U17 is actually giving juice (even when powered off.
U17 =  Code PCYI -> TPS770 -> Power 5V   ULTRALOW-POWER 50-mA LOW-DROPOUT LINEAR REGULATORS
(...)

--- End quote ---

I have now started all over again troubleshooting my dead 289. I  am going through all posts regarding 289 troubleshooting in this forum. My 289 has entered the 5x flashing power button state (dead mode). There is no output from the 5V regulator U17 (TP3). This is probably because the enable input pin 3 (EN) of the TPS770 reads 3.1 Volts ("A voltage of 1.7 V or greater on the EN input will disable the TPS770xx internal circuitry...). Does anyone know which component has decided to shut off the 5V regulator by feeding 3.1V to the EN-pin of U17?
Navigation
Message Index
Next page
Previous page
There was an error while thanking
Thanking...

Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod