Philips 60PFL8708S/12 - QFU1.2E LA - Error code 53

[Maalobs]

Re: Philips 60PFL8708S/12 - QFU1.2E LA - Error code 53

For the point 4:
I have already tried some times ago this method but even if the RC is ok (led blinks) the tv makes no output on video, the usb pen lights up the light for some sec. then back off, then on and off several times until the led error code.

Yes, that's because it does 7 boot attempts before it falls into Protection Mode, and only when it has arrived there will it blink the error code.
I saw some cyclic changes in measurements in power readings too before I started reading the UART output, then later I realized that the measurements were just side channel noise from the ongoing reboot cycle.

For the point 4:
I have done another try and for now i have done it with the file named software.upg and placed on to UPGRADES directory, no other files in. You have explained very few, how it does exactly? If it doesn't work it will appear something about error... not?

I didn't have any other Philips remote controls and the TV was completely unresponsive to those I had.
But I went out and bought a Philips IR remote and when I use the new remote, there is actually response from the TV.

I plugged in the USB-stick again with autorun.upg in the root folder.

First I booted the TV in SDM while reading TXD-SERVICE, and holding down OK on the IR-remote when I plugged in the mains power.
Now I got new output:

0xF98A30E2 cycle now
Jump to 0xB5034100 02 key is used
Getting Hash...
0xBFC00000 01 10 00 00 52 55 00 0F 36 74 B3 80 00 00 00 00
Hash:
0xB5034570 1D 86 AE FF E3 71 65 8F 13 61 12 66 C4 5F 8D B0
Buffer for BIG NUM is at B5034E2C, size is 0440.
nand.c:nand_readwithinpage
0x00000000 page is reading
0x00000004 0x00000007 0x00000000 StartUnit/EndUnit/offset
Reading out data:
 04 unit:


waiting ECC result ready
 00 bits error in the unit.
 05 unit:


waiting ECC result ready
 00 bits error in the unit.
 06 unit:


waiting ECC result ready
 00 bits error in the unit.
 07 unit:


waiting ECC result ready
 00 bits error in the unit.

nand.c:nand_readwithinpage
0x00000001 page is reading
0x00000000 0x00000003 0x00000000 StartUnit/EndUnit/offset
Reading out data:
 00 unit:


waiting ECC result ready
 00 bits error in the unit.
 01 unit:


waiting ECC result ready
 00 bits error in the unit.
 02 unit:


waiting ECC result ready
 00 bits error in the unit.
 03 unit:


waiting ECC result ready
 00 bits error in the unit.

nand.c:nand_readwithinpage
0x00000001 page is reading
0x00000004 0x00000007 0x00000000 StartUnit/EndUnit/offset
Reading out data:
 04 unit:


waiting ECC result ready
 00 bits error in the unit.
 05 unit:


waiting ECC result ready
 00 bits error in the unit.
 06 unit:


waiting ECC result ready
 00 bits error in the unit.
 07 unit:


waiting ECC result ready
 00 bits error in the unit.

nand.c:nand_readwithinpage
0x00000002 page is reading
0x00000000 0x00000000 0x00000000 StartUnit/EndUnit/offset
Reading out data:
 00 unit:


waiting ECC result ready
 00 bits error in the unit.


{preboot}
 <000>
 <010>
 <020>KKG0G1                                           <------------ This is the line where it would previously stop!
 <030>DDDDDDDDDDDDDD
 <040>secure
      Load uboot


U-Boot 2009.01_Production (Jun 11 2013 - 10:29:06)

UNAND: NAND, size:1024MB, Micron(ID:0x2c,0x38), block size:512KB
1024 MiB
Env:  NAND @ 0x01800000
bootcmd4
BOOTREASON=upgrade
APP CPU==>1GHz
Found: /boot
Found: /bootenv
Found: /systemA
Found: /systemB
Found: /rwboot
Found: /rwdata
Found: /bbt
Found 7 partitions
Creating 1 MTD partitions on "NAND 1GMiB 3,3V 8-bit":
0x02e00000-0x0fd00000 : "mtd=2"
UBI: attaching mtd0 to ubi0
UBI: physical eraseblock size:  524288 bytes (512 KiB)
UBI: logical eraseblock size:  516096 bytes
UBI: smallest flash I/O unit:  4096
UBI: VID header offset:     4096 (aligned 4096)
UBI: data offset:        8192
UBI: fixable bit-flip detected at PEB 88
UBI: fixable bit-flip detected at PEB 269
UBI: fixable bit-flip detected at PEB 302
UBI warning: ubi_eba_init_scan: cannot reserve enough PEBs for bad PEB handling, reserved 4, need 40
UBI: attached mtd0 to ubi0
UBI: MTD device name:      "mtd=2"
UBI: MTD device size:      0 MiB
UBI: number of good PEBs:    414
UBI: number of bad PEBs:     0
UBI: max. allowed volumes:    128
UBI: wear-leveling threshold:  4096
UBI: number of internal volumes: 1
UBI: number of user volumes:   2
UBI: available PEBs:       0
UBI: total number of reserved PEBs: 414
UBI: number of PEBs reserved for bad PEB handling: 4
UBI: max/mean erase counter: 21/5
simple_strtoul
simple_strtoul ret
Authenticating ubootenvaddon.tdf....offset: 0x288 (648)
pld->payloadSize: 0x8c4 (2244)
sizeof(TdfSignedPayload_t): 0x104 (260)
sizeof(TdfPayloadHeader_t): 0x8 (8)
pData=82400000 count=0x7b8 (1976)
bucket=0x7b8 (1976)
suceeds
## Executing script at 82400000
U-boot script: %version: blr18mgr#42.1.5 % -- %created_by: rp_int % -- %date_created: Thu Jul 4 11:18:12 2013 % -- addon=%version: 31 % /// creator!= the helpdesk
simple_strtoul
simple_strtoul ret
Authenticating appmipsauth.tdf....offset: 0x288 (648)
pld->payloadSize: 0x2c04 (11268)
sizeof(TdfSignedPayload_t): 0x104 (260)
sizeof(TdfPayloadHeader_t): 0x8 (8)
pData=a5c00000 count=0x2af8 (11000)
bucket=0xd78 (3448)
suceeds
## Starting application at 0xA5C00000 ...
999simple_strtoul
simple_strtoul ret
Authenticating vmlinux_plf.tdf....offset: 0x288 (648)
UBI: fixable bit-flip detected at PEB 132
UBI: schedule PEB 132 for scrubbing
UBI: fixable bit-flip detected at PEB 134
UBI: schedule PEB 134 for scrubbing
suceeds
simple_strtoul
simple_strtoul ret
Authenticating vmlinux_app.tdf....offset: 0x288 (648)
UBI: fixable bit-flip detected at PEB 135
UBI: schedule PEB 135 for scrubbing
UBI: fixable bit-flip detected at PEB 135
UBI: schedule PEB 135 for scrubbing
UBI: fixable bit-flip detected at PEB 135
UBI: schedule PEB 135 for scrubbing
UBI: fixable bit-flip detected at PEB 136
UBI: schedule PEB 136 for scrubbing
suceeds
simple_strtoul
simple_strtoul ret
Authenticating display.tdf....offset: 0x288 (648)
UBI: fixable bit-flip detected at PEB 144
UBI: schedule PEB 144 for scrubbing
suceeds
simple_strtoul
simple_strtoul ret
Authenticating avdecoder.tdf....offset: 0x288 (648)
UBI: fixable bit-flip detected at PEB 138
UBI: schedule PEB 138 for scrubbing
UBI: fixable bit-flip detected at PEB 139
UBI: schedule PEB 139 for scrubbing
UBI: fixable bit-flip detected at PEB 140
UBI: schedule PEB 140 for scrubbing
UBI: fixable bit-flip detected at PEB 141
UBI: schedule PEB 141 for scrubbing
UBI: fixable bit-flip detected at PEB 143
UBI: schedule PEB 143 for scrubbing
suceeds
commandline passed to kernel is = mem=40m@72m mem=354m@2206m vecaddr=2m@70m loglevel=3 lpj=1949696 ipcfg_preopen_dly=0 ipcfg_postopen_dly=0 BOOTREASON=upgrade ip=172.21.1.2::172.21.1.1:255.255.0.0::vec0:off root=/dev/nfs rw nfsroot=172.21.1.1:/,udp,rsize=32768,wsize=32768,timeo=600,retrans=2,nfsvers=3 ph_debug=none ph_sys=A ph_def=A ph_alt=B
## Starting application at 0x80100800 ...
flush cache do_go 82
commandline passed to kernel is = console=ttyS0,115200n8 mtdparts=NAND:24m(/boot),22m(/bootenv),207m(/systemA),207m(/systemB),72m(/rwboot),468m(/rwdata),24m(/bbt) mem=70m@0k mem=80m@2126m vecaddr=2m@70m loglevel=3 lpj=1363968 lockd.nlm_grace_period=1 mm_ra_disable=1 BOOTREASON=upgrade ubi.mtd=3 secureblock.hook=31:9 root=f900 rootfstype=squashfs ip=none ph_debug=none ph_sys=A ph_def=A ph_alt=B
 address of cmdlineparam = 80f34b24
[  0.328630] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(249,0)

It's reading the Micron NAND Flash and detecting a bunch of "fixable bit-flips", before ending in a kernel panic because of a filesystem error on the last line.
Nothing else happened after this line.
The screen remained black, and the LED started blinking error code 53.

After a few minutes I unplugged the mains power and disabled SDM.
Still reading TXD-SERVICE, I booted the TV again with the IR remote trick.
There was no change in the output from my original reading which I have described in the original post.
The screen remained black, and the TV was cycling through the boot attempts as before.

I switched to reading TXD-STANDBY and repeated the boot again, both with and without SDM, but again there was no change in the output compared to what I have described in my original post.
There was one difference in that each time I pressed a key on the IR remote, it was reflected in the UART output.
Pressing "OK" on the IR remote resulted in "TV_OK" being printed on the screen, etc.
The screen again remained black.

Now I switched back to the first mode again where I had the new output; reading TXD-SERVICE with SDM enabled.
But again, I am only getting the output of the original post, where it stops mid sentence on the "<020>K" line.
I can't reproduce the new output anymore, it only worked once, and therefore maybe it was just a coincidence?

And anyway, the TV never got so far as to enter any kind of software upgrade mode.

I was off this problem for a few days because to add insult to injury, my notebook died as well with what I eventually concluded was a system board error.
But I have ordered a new computer now and the old hunk o' junk is shelved until the day I find schematics and a boardview for it.

I'm thinking that now when I have the back of the SSB exposed, I should find and measure the power rails on that side, just to be 100% sure that there is no fundamental problem on the board, even though everything was 100% functional on the top side.

[Diah]

Re: Philips 60PFL8708S/12 - QFU1.2E LA - Error code 53

well i found out Reflow the CPU enough to make it boot, with out change NAND or do BGA ball for CPU too, easy way. folow this English version of German side

[Davi.p]

Re: Philips 60PFL8708S/12 - QFU1.2E LA - Error code 53

For the point 4:
I have already tried some times ago this method but even if the RC is ok (led blinks) the tv makes no output on video, the usb pen lights up the light for some sec. then back off, then on and off several times until the led error code.I have done another try and for now i have done it with the file named software.upg and placed on to UPGRADES directory, no other files in. You have explained very few, how it does exactly? If it doesn't work it will appear something about error... not?

[Maalobs]

Re: Philips 60PFL8708S/12 - QFU1.2E LA - Error code 53

Well, it looks like I have managed to answer a few of my own questions.

4.
Der Alpengeist actually explains the remote control trick in another blogpost:

The first thing to do is to start the emergency software installation.
For that, you need an infrared remote, which does not come with the TV.
You can get one for around 10€.
The reason being that the software, which manages the original radio remote control will not be loaded under such circumstances.

• Disconnect the TV from the mains
• Press OK or DOWN on the remote and hold it
• Plug in the mains.

I did that and the recovery program came up.
Good!
This means that the screen, the backlight, and the main processor are doing fine.

I interpret that as a software feature executing in the main processor, not in the standby processor, so again it's not useful in my case.
I still tried it with every IR remote control in my house, but nothing happened.
Now that I had more details, I found a description of this in the service manual, in a flowchart on page 36.
Maybe there is room here to investigate this further with a verified Philips IR remote control.

7.
Your talk about the foam gave me the confidence to try again to lift the SSB.
The sticky foam covers a 5x5cm section right under the center of the SSB, and if you try to lift the PCB by the edges it goes all U-shaped in the profile.
But I eventually managed to dislodge the PCB, even without damaging the underlying foam!
Thanks for the encouragement!

Now I have full access to all the memory chips:


Some of the solder joints seem to have been covered with a nail polish-like conformal coating of some kind:


The NAND Flash is not the exact same part number as was specified in the service manual:

This is MT29F8G08ABABA, but it seems the same datasheet covers both.

Finally the EEPROM is accessible too:


I don't know what those two round epoxy blobs are good for.
There is nothing significant there according to the bottom layout schematic in the service manual.

One piece remains;
If anyone is able to help me out with memory dumps for this TV model, then please post them here.

I really want to try that route before I start butchering the Fusion chip with my totally inadequate hot air gun.
If I mess up that BGA reflow, it's finito for this SSB.

[diif]

Re: Philips 60PFL8708S/12 - QFU1.2E LA - Error code 53

That is not the content, is the programmed chip to buy..

Yes. Just as a car with a shopping in the boot is a car and shopping.
You said you couldn't find the content and I'm showing it can be found.

[Davi.p]

Re: Philips 60PFL8708S/12 - QFU1.2E LA - Error code 53

That is not the content, is the programmed chip to buy..

[diif]

Re: Philips 60PFL8708S/12 - QFU1.2E LA - Error code 53

The nand contents aren't that hard to find.

https://www.sahy.cz/Philips-QFU1-2E-...BABA-d4318.htm

[Davi.p]

Re: Philips 60PFL8708S/12 - QFU1.2E LA - Error code 53

I have a 2014 vintage Philips

THe things from 80s are vintage not 2014...
I don't understand this people's hunger for brand new things...
Heart would be better if people would be happy without changing electronics and gadgets every 2-3 years...

error 53 problem could be caused by corruption in either the SPI Flash, in the NAND Flash, the EEPROM , or it could be caused by the Fusion chip itself needing a BGA reflow.

Yes, this is the list that i have isolated in my similar model, even if it's not short, apart the eeprom that read well by programmer.

they have added a thick piece of some sort of EMC foam that is glued with a very strong adhesive right underneath the Fusion chip

How much thick is it? 6-7mm? Its colour? Reddish/purpleish dark grey? Is it gelly? If yes thah is the same silicone bumper like mine, it's enough to pullp it up.

Anyway, reading the logs seems to be possible a software problem, but unless i will not spend that 35 euro for an upgrade to my RT809F programmer i will never know..!
Anyway hoping to find flash contents in internet for free or even paid is out question.. very rare like white fly..

[Diah]

Re: Philips 60PFL8708S/12 - QFU1.2E LA - Error code 53

Here's a picture of the top side of the board before I soldered on the bodge wires on the SDM and the debug-connector:


Here is the sticker:


Does anyone have memory dumps of the EEPROM, SPI Flash and NAND Flash of this TV model?
I'd really like to try that that route before I attempt to reflow the Fusion processor.

the fault caused while TV working, its much BGA issue not SW.
reflow the Fusion processor a good start. even could be one of the DDR

[Maalobs]

Re: Philips 60PFL8708S/12 - QFU1.2E LA - Error code 53

Hi,

Thanks for replying!

The autorun.upg is encrypted, how do I unpack all the various memory dumps from it?
I read through this old comment thread about cracking the autorun.upg, but it involves security weaknesses in the main software that Philips has consequently fixed:
https://web.archive.org/web/20160421...ilips-pfl9703/
It's no use in my case anyway, because the TV doesn't boot the main software, it just goes into protection mode with a black screen and with error code 53 blinking on the LED.

If you know of a way to flash an autorun.upg on the TV while in this error 53 state, then please let me know how!
That would be really helpful to my situation.

I have already tried the obvious; to have a USB-stick plugged in with autorun.upg in the root of the FAT32 filesystem and then boot the TV both with and without SDM enabled, but nothing happened, the TV just failed into the protection mode as usual.

PS:
What is "Philips plat forum"?

[Diah]

Re: Philips 60PFL8708S/12 - QFU1.2E LA - Error code 53

with yours Philips plat forum you can always downgrade or upgrade firmware, boot within autorun.upg

[Maalobs]

Re: Philips 60PFL8708S/12 - QFU1.2E LA - Error code 53

Here's a picture of the top side of the board before I soldered on the bodge wires on the SDM and the debug-connector:


Here is the sticker:


Does anyone have memory dumps of the EEPROM, SPI Flash and NAND Flash of this TV model?
I'd really like to try that that route before I attempt to reflow the Fusion processor.

[Maalobs]

Hi,

I have a 2014 vintage Philips 60PFL8708S/12 that suddenly died in the middle of the kids watching a show.

The relevant service manual for the chassis is available here.
The TV no longer powers on, and leaving it powered on for a few minutes results in the layer-1 error with 2 blinks.
When I short the SDM to ground I get the layer-2 error code 53.

The inside of the TV has no damaged components and no swollen capacitors.
In SDM-mode when all the power rails are left on despite entering the protection mode, I tracked down and measured the voltage level and ripple of every single power rail with the help of the service manual, and I measured the switching frequency of every switching regulator as well, and they are all fine.

Error code 53 is described in table 5-2 in the service manual as:

Description          Layer 1 Layer 2 Monitored by Error/Prot Error Buffer/Blinking LED Device Defective Board
MIPS doesn't boot (SW cause) 2    53    Stby µP    P      BL             FUSION SSB

The "Extra Info" section below the table says:
Error 53.
This error will indicate that the Fusion device has read his bootscript (when this would have failed, error 15 would blink) but initialization was never completed because of hardware problems (NAND flash, DDR...) or software initialization problems.
Possible cause could be that there is no valid software loaded (try to upgrade to the latest main software version).
Note that it can take a few minutes before the TV starts blinking LAYER 1 error = 2 or in SDM (maintain grounding continuously), LAYER 2 error = 53.

The debug-port 1CV5 is unpopulated but I soldered in wires on TXD-SERVICE and TXD-STANDBY so I could monitor them with serial adapters.

The TXD-SERVICE output is identical both with and without SDM enabled, it starts like this and then retries 6 more times:

0xF98A30F3 cycle now
Jump to 0xB5034100 02 key is used
Getting Hash...
0xBFC00000 01 10 00 00 52 55 00 0F 36 74 B3 80 00 00 00 00
Hash:
0xB5034570 1D 86 AE FF E3 71 65 8F 13 61 12 66 C4 5F 8D B0
Buffer for BIG NUM is at B5034E2C, size is 0440.
nand.c:nand_readwithinpage
0x00000000 page is reading
0x00000004 0x00000007 0x00000000 StartUnit/EndUnit/offset
Reading out data:
 04 unit:


waiting ECC result ready
 00 bits error in the unit.
 05 unit:


waiting ECC result ready
 00 bits error in the unit.
 06 unit:


waiting ECC result ready
 00 bits error in the unit.
 07 unit:


waiting ECC result ready
 00 bits error in the unit.

nand.c:nand_readwithinpage
0x00000001 page is reading
0x00000000 0x00000003 0x00000000 StartUnit/EndUnit/offset
Reading out data:
 00 unit:


waiting ECC result ready
 00 bits error in the unit.
 01 unit:


waiting ECC result ready
 00 bits error in the unit.
 02 unit:


waiting ECC result ready
 00 bits error in the unit.
 03 unit:


waiting ECC result ready
 00 bits error in the unit.

nand.c:nand_readwithinpage
0x00000001 page is reading
0x00000004 0x00000007 0x00000000 StartUnit/EndUnit/offset
Reading out data:
 04 unit:


waiting ECC result ready
 00 bits error in the unit.
 05 unit:


waiting ECC result ready
 00 bits error in the unit.
 06 unit:


waiting ECC result ready
 00 bits error in the unit.
 07 unit:


waiting ECC result ready
 00 bits error in the unit.

nand.c:nand_readwithinpage
0x00000002 page is reading
0x00000000 0x00000000 0x00000000 StartUnit/EndUnit/offset
Reading out data:
 00 unit:


waiting ECC result ready
 00 bits error in the unit.


{preboot}
 <000>
 <010>
 <020>K     <------ It ends here, right after the K, so the next iteration begins after that character.

The TXD-STANDBY output with SDM enabled is minimal, just a single iteration.

BootMode B
Trident MCU SDK, Chip type:Chip FUSION 77.04.08.00 Date:Jul 19 2013 Time: 15:36:29

 Warning!!!: PowerON pin going to be configured
 Toggle ENABLE WOLAN tdShmInit
Enable 12V dip detect
STARTUP FAILURE GOING TO PROTECTION LAYER

The TXD-STANDBY output without SDM enabled has a wierd line on one of the later iterations (highlighted below) before it finally gives up:

BootMode B
Trident MCU SDK, Chip type:Chip FUSION 77.04.08.00 Date:Jul 19 2013 Time: 15:36:29

 Warning!!!: PowerON pin going to be configured
 Toggle ENABLE WOLAN tdShmInit
Enable 12V dip detect
HOST STARTUP TIMEOUT

Going to Standby....!
WOLAN and RESET ETHERNET DISABLED
 Toggle ENABLE WOLAN tdShmInit
Enable 12V dip detect
HOST STARTUP TIMEOUT

Going to Standby....!
WOLAN and RESET ETHERNET DISABLED
 Toggle ENABLE WOLAN tdShmInit
Enable 12V dip detect
HOST STARTUP TIMEOUT

Going to Standby....!
WOLAN and RESET ETHERNET DISABLED
 Toggle ENABLE WOLAN tdShmInit
Enable 12V dip detect
HOST STARTUP TIMEOUT

Going to Standby....!
WOLAN and RESET ETHERNET DISABLED
 Toggle ENABLE WOLAN tdShmInit
Enable 12V dip detect
HOST STARTUP TIMEOUT

Going to Standby....!
WOLAN and RESET ETHERNET DISABLED
 Toggle ENABLE WOLAN tdShmInit
Enable 12V dip detect
HOST STARTUP TIMEOUT
Raghu: TRY WITH UPGRADE MODE                <------ Line of interest.

Going to Standby....!
WOLAN and RESET ETHERNET DISABLED
 Toggle ENABLE WOLAN tdShmInit
Enable 12V dip detect
HOST STARTUP TIMEOUT
STARTUP FAILURE GOING TO PROTECTION LAYER 1

Going to Standby....!
WOLAN and RESET ETHERNET DISABLED

From the description in the service manual as well as from research on the internet regarding QFU chassis Philips TVs, it sounds like this error 53 problem could be caused by corruption in either the SPI Flash (7CT3, STMicro M25P05-AVMN6), in the NAND Flash (7JA0, Micron MT29F8G08ABACAWP:C), the EEPROM (7JA2, STMicro M24C64-WDW6), or it could be caused by the Fusion chip itself needing a BGA reflow.

To understand the next course of action, I have a few questions that I hope someone is able to answer:
1.
Is it possible to flash the TV with the latest autorun.upg (version 000.173.067.000 from 2016-01-28) without having booted the Fusion processor?
In my experience with enterprise network devices, there is often a way to program firmware from a rudimentary boot loader environment.

2.
How do I initiate the task that this line refers to in the TXD-STANDBY output without SDM:
Raghu: TRY WITH UPGRADE MODE

3.
Section 5.8.7 in the service manual mentions this:
Startup in the SW upgrade application and observe the Uart logging:
Starting up the TV set in the Manual Software Upgrade mode will show access to USB, meant to copy software content from USB to the DRAM.
Progress feedback can be found in the logging.
How do I initiate this "Manual Software Upgrade mode"?

4.
In the blog comments here, there is mention of using a simpler IR remote in a context where the EEPROM was mentioned (search for all instances of the text "remote"):
https://alpengeist-tvrepair.blogspot...-usb-uart.html
What task can be achieved with this IR remote control solution?

5.
In this post on this very forum someone posted a couple of versions of a Philips software program that's supposed to solve reboot issues:
https://www.badcaps.net/forum/showpo...&postcount=372
Sadly the 8000-series models are not listed as supported in the post comments.
Is this software tool meaningful in my situation?
Does anyone have it for my TV model or can I request it from Philips Support as a consumer?

6.
If all else fails, I have an XGecu TL866II Plus flash programmer, it supports the SPI Flash and the EEPROM, but maybe not the NAND Flash (the closest matching model name pattern is "MT29F" out of the full name "MT29F8G08ABACAWP:C").
Does anyone have firmware dumps of all these chips for this TV model?

7.
A practical question; I have read about the heat complaints of the QFU series and in this TV model they have added a thick piece of some sort of EMC foam that is glued with a very strong adhesive right underneath the Fusion chip, which is right in the middle of the SSB.
I'm assuming that this thick, strong foam has some heat transfer properties, because underneath the SSB the foam is in turn glued with the strong adhesive right against the big aluminium chassis.
The SSB only has the SPI Flash on the top side, so if I have to reach the EEPROM or NAND for a manual flash using the programmer, or if I have to ghetto-reflow the Fusion chip with my measly 858D heatgun, then I need to remove the SSB first.
Does anyone have a suggestion on how to detach the SSB in the correct manner from the foam underneath the PCB?
It's not mentioned in the service manual.
I can't get any tool that deep underneath the SSB, there is no space to rotate the PCB, and if I pull on the PCB by the edges it bends dangerously and the adhesive still doesn't let go.
Also, if the foam gets ruined in the process; Does anyone know what the name is of that material so I can buy a piece of replacement?
It seems vital to maintain what little cooling properties there are.

8.
Does anyone have any suggestion on how to proceed?


Many thanks in advance!