Electronics > Repair
Fluke 289 not quite sorted.
frenky:
So I dumped contents of "RedBoot config" and got this out:
d -b 0x107FF000 -l 0x00001000
--- Code: ---107FF000: 00 10 00 00 CE FA AD 0B 01 0C 01 00 62 6F 6F 74 |............boot|
107FF010: 5F 73 63 72 69 70 74 00 00 00 00 00 04 11 01 0C |_script.........|
107FF020: 62 6F 6F 74 5F 73 63 72 69 70 74 5F 64 61 74 61 |boot_script_data|
107FF030: 00 62 6F 6F 74 5F 73 63 72 69 70 74 00 66 69 73 |.boot_script.fis|
107FF040: 20 75 6E 6C 6F 63 6B 20 66 73 0A 66 73 20 6D 6F | unlock fs.fs mo|
107FF050: 75 6E 74 20 2D 64 20 2F 64 65 76 2F 66 6C 61 73 |unt -d /dev/flas|
107FF060: 68 2F 66 69 73 2F 66 73 20 2D 74 20 6A 66 66 73 |h/fis/fs -t jffs|
107FF070: 32 20 2F 0A 6C 6F 61 64 20 2D 6D 20 66 69 6C 65 |2 /.load -m file|
107FF080: 20 2F 73 79 73 74 65 6D 2F 61 70 70 73 2F 63 6C | /system/apps/cl|
107FF090: 65 6D 2E 69 6D 67 0A 66 73 20 75 6D 6F 75 6E 74 |em.img.fs umount|
107FF0A0: 20 2F 0A 67 6F 20 2D 63 20 2D 6E 0A 0A 00 00 00 | /.go -c -n.....|
107FF0B0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
107FF0C0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
107FF0D0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
107FF0E0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
107FF0F0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
107FF100: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
107FF110: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
107FF120: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
107FF130: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
107FF140: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
107FF150: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
107FF160: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
107FF170: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
107FF180: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
107FF190: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
107FF1A0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
107FF1B0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
107FF1C0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
107FF1D0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
107FF1E0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
107FF1F0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
107FF200: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
107FF210: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
107FF220: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
107FF230: 00 00 00 00 00 00 00 00 00 00 00 00 00 02 14 01 |................|
107FF240: 0C 62 6F 6F 74 5F 73 63 72 69 70 74 5F 74 69 6D |.boot_script_tim|
107FF250: 65 6F 75 74 00 62 6F 6F 74 5F 73 63 72 69 70 74 |eout.boot_script|
107FF260: 00 01 00 00 00 01 06 01 00 62 6F 6F 74 70 00 00 |.........bootp..|
107FF270: 00 00 00 05 14 00 06 62 6F 6F 74 70 5F 6D 79 5F |.......bootp_my_|
107FF280: 67 61 74 65 77 61 79 5F 69 70 00 62 6F 6F 74 70 |gateway_ip.bootp|
107FF290: 00 00 00 00 00 05 0C 00 06 62 6F 6F 74 70 5F 6D |.........bootp_m|
107FF2A0: 79 5F 69 70 00 62 6F 6F 74 70 00 C0 A8 09 85 05 |y_ip.bootp......|
107FF2B0: 11 00 06 62 6F 6F 74 70 5F 6D 79 5F 69 70 5F 6D |...bootp_my_ip_m|
107FF2C0: 61 73 6B 00 62 6F 6F 74 70 00 FF FF 00 00 05 10 |ask.bootp.......|
107FF2D0: 01 00 62 6F 6F 74 70 5F 73 65 72 76 65 72 5F 69 |..bootp_server_i|
107FF2E0: 70 00 C0 A8 64 64 02 12 01 00 63 6F 6E 73 6F 6C |p...dd....consol|
107FF2F0: 65 5F 62 61 75 64 5F 72 61 74 65 00 00 C2 01 00 |e_baud_rate.....|
107FF300: 05 07 01 00 64 6E 73 5F 69 70 00 00 00 00 00 01 |....dns_ip......|
107FF310: 09 01 00 65 74 68 30 5F 65 73 61 00 01 00 00 00 |...eth0_esa.....|
107FF320: 06 0E 01 09 65 74 68 30 5F 65 73 61 5F 64 61 74 |....eth0_esa_dat|
107FF330: 61 00 65 74 68 30 5F 65 73 61 00 00 80 40 00 22 |a.eth0_esa...@."|
107FF340: 85 00 00 02 09 01 00 67 64 62 5F 70 6F 72 74 00 |.......gdb_port.|
107FF350: 28 23 00 00 01 13 01 00 69 6E 66 6F 5F 63 6F 6E |(#......info_con|
107FF360: 73 6F 6C 65 5F 66 6F 72 63 65 00 01 00 00 00 02 |sole_force......|
107FF370: 14 01 13 69 6E 66 6F 5F 63 6F 6E 73 6F 6C 65 5F |...info_console_|
107FF380: 6E 75 6D 62 65 72 00 69 6E 66 6F 5F 63 6F 6E 73 |number.info_cons|
107FF390: 6F 6C 65 5F 66 6F 72 63 65 00 00 00 00 00 01 0A |ole_force.......|
107FF3A0: 01 00 6E 65 74 5F 64 65 62 75 67 00 00 00 00 00 |..net_debug.....|
107FF3B0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
107FF3C0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
--- End code ---
Made it readable and run found commands manually:
fis unlock fs
fs mount -d /dev/flash/fis/fs -t jffs2 /
load -m file /system/apps/clem.img
fs umount /
go -c -n
--- Code: ---RedBoot>
fis unlock fs.fs
fis unlock fs.fs
No image 'fs.fs' found
RedBoot>
fis unlock fs
fis unlock fs
RedBoot>
fs mount -d /dev/flash/fis/fs -t jffs2 /
fs mount -d /dev/flash/fis/fs -t jffs2 /
RedBoot>
load -m file /system/apps/clem.img.fs
load -m file /system/apps/clem.img.fs
fs: Open failed, error 2
Can't load '/system/apps/clem.img.fs': error 0
RedBoot>
fs list
fs list
1 drwxr-xr-x 1 size 0 .
1 drwxr-xr-x 1 size 0 ..
4 drwxr-xr-x 1 size 0 tmp
5 drwxr-xr-x 1 size 0 user
3 drwxr-xr-x 1 size 0 system
2 drwxr-xr-x 1 size 0 checkpoint
RedBoot>
fs list tmp
fs list tmp
4 drwxr-xr-x 1 size 0 .
1 drwxr-xr-x 1 size 0 ..
RedBoot>
fs list user
fs list user
5 drwxr-xr-x 1 size 0 .
1 drwxr-xr-x 1 size 0 ..
10 drwxr-xr-x 1 size 0 setup
11 drwxr-xr-x 1 size 0 stored
9 drwxr-xr-x 1 size 0 calibration
RedBoot>
fs list system
fs list system
3 drwxr-xr-x 1 size 0 .
1 drwxr-xr-x 1 size 0 ..
6 drwxr-xr-x 1 size 0 apps
7 drwxr-xr-x 1 size 0 health
RedBoot>
fs list system/apps
fs list system/apps
6 drwxr-xr-x 1 size 0 .
3 drwxr-xr-x 1 size 0 ..
jffs2_read_inode() failed
Unable to stat file system/apps/clem.img
--- End code ---
So I get the error "Unable to stat file system/apps/clem.img".
Perhaps this image is somehow corrupted?
But now I'm pretty sure that I'll be able to load image into flash via xmodem.
purpose:
:-+
frenky:
With ExtraPuTTY I was able to load clem.img into mcu's memory:
load -m xmodem
go -c -n
But When I run "go -c -n" nothing happened so I'm a bit lost here...
Anyway I went into another path of finding all jtag intefaces...
First of ARM9 MC9328MXS mcu. I overlaid pinout from datasheet on the back of pcb to see were are jtag bga pads:
Then I measured resistance to the header on the side of pcb, to find out which signal goes where:
trst tms tdo tck tdi
e37 e36 e34 tp19 tp21
Then used jtagenum to confirm that pins are correct:
ntrst:DIG_6 tck:DIG_3 tms:DIG_5 tdo:DIG_4 tdi:DIG_2 IR length: 4
Starting scan for IDCODE...
ntrst:DIG_6 tck:DIG_3 tms:DIG_5 tdo:DIG_4 tdi:DIG_2 devices: 1
0x1092001D
And yes this is correct id according to this: https://github.com/MonsieurV/msk/blob/master/apf9328flash.cfg
# The CPU - mc9328mxl
set _CHIPNAME mc9328mxl
set _ENDIAN little
# There is only one TAP
set _CPUTAPID 0x1092001d
Terry01:
Frenky.
I have just been In my new 289 to check the cap, yours looks upside down compared to mine. Please don't shout at me for being a ***** IDIOT or anything like that. I may/probably be completely wrong. I am a complete beginner electronics wise to you guys so don't know much about these things. The cap looking upside down compared to mine jumped right out at me when I saw the picture of yours.
Hope this helps....
Terry01:
If you wait till tonight UK time I will be able to get a decent quality pic of mine and post it?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version