Pictures are being uploaded now, I live in the Northwest and a massive snowstorm has limited my bandwidth and connection severely. Images are on the way.
I know everything is correct as far as wiring/solder/etc.
I'm monitoring the console with both Comms and Network
This will be the 9th total Trinity Ive done, and also done 3 Corona as well with the same DGX so I know it is not an issue with the DGX hardware.
Tried following tricks already:
CPU_RST;
Slim Ground Cable on "D"
Yellow DGC wire on "D"
10pf Cap
POST_OUT;
normal yellow dgx
6cm up to 170cm and everywhere in between with wire from Cat6 ethernet cable (this setup worked on 6 Trinitys so far for me personally)
"slim blue, and phat green" wire length trick
Kynar 120cm (WNYConsoles trick around x-clamp and hanging)
No matter what the wiring, and man I've been on this one console for a week now, I do get the DBG light pulsing (Green light on DGX) but the fan starts "ticking" every time. Sometimes as short as 30 seconds, sometimes it tried to glitch for up to an hour and then the fans started going.
I do however have the lovely time of finding a set of Bad Blocks in the ecc area, which it appears Jrunner has remapped for me.
When Flashing the DGX ecc it also appears that Jrunner has remapped it correctly.
Stock Nand works great still when flashed back (and Jrunner remaps this as well)
So Here's my Bad Blocks readout:
• Bad Block ID @ 0x5 [Offset: 0x14A00]
• Bad Block ID @ 0x6 [Offset: 0x18C00]
• Bad Block ID @ 0xBE [Offset: 0x30FC00]
• Bad Block ID @ 0xFD [Offset: 0x413A00]
• Bad Block ID @ 0xFE [Offset: 0x417C00]
• Bad Block ID @ 0x5 Found @ 0x3FF[Offset: 0x107BE00]
• Bad Block ID @ 0x6 Found @ 0x3FE[Offset: 0x1077C00]
• Bad Block ID @ 0xBE Found @ 0x3FD[Offset: 0x1073A00]
• Bad Block ID @ 0xFD Found @ 0x3FC[Offset: 0x106F800]
• Bad Block ID @ 0xFE Found @ 0x3FB[Offset: 0x106B600]
I've literally tried every conceivable wire length and swap, every trick I could find from anyone on the Forum before making a new thread. Where I'm at now I'm wondering if the reset loop (fan ticking) is perhaps not being brought by the wire length so much as it may be from the console having the two bad blocks in the ecc area of the nand.
---------- Post added at 08:52 ---------- Previous post was at 08:48 ----------
PROBABLY UNRELATED:
But this is the first I've done with the SonusQSB installed as well, I highly doubt it would have much difference really, but it is the only difference from the others (aside from the obvious bad blocks)
This Trinity was also a M$ Replacement console, I know that on some of the phat consoles this resulted in a different CB structure however it seems to me that the CB and everything is right in line.
I know everything is correct as far as wiring/solder/etc.
I'm monitoring the console with both Comms and Network
This will be the 9th total Trinity Ive done, and also done 3 Corona as well with the same DGX so I know it is not an issue with the DGX hardware.
Tried following tricks already:
CPU_RST;
Slim Ground Cable on "D"
Yellow DGC wire on "D"
10pf Cap
POST_OUT;
normal yellow dgx
6cm up to 170cm and everywhere in between with wire from Cat6 ethernet cable (this setup worked on 6 Trinitys so far for me personally)
"slim blue, and phat green" wire length trick
Kynar 120cm (WNYConsoles trick around x-clamp and hanging)
No matter what the wiring, and man I've been on this one console for a week now, I do get the DBG light pulsing (Green light on DGX) but the fan starts "ticking" every time. Sometimes as short as 30 seconds, sometimes it tried to glitch for up to an hour and then the fans started going.
I do however have the lovely time of finding a set of Bad Blocks in the ecc area, which it appears Jrunner has remapped for me.
When Flashing the DGX ecc it also appears that Jrunner has remapped it correctly.
Stock Nand works great still when flashed back (and Jrunner remaps this as well)
So Here's my Bad Blocks readout:
• Bad Block ID @ 0x5 [Offset: 0x14A00]
• Bad Block ID @ 0x6 [Offset: 0x18C00]
• Bad Block ID @ 0xBE [Offset: 0x30FC00]
• Bad Block ID @ 0xFD [Offset: 0x413A00]
• Bad Block ID @ 0xFE [Offset: 0x417C00]
• Bad Block ID @ 0x5 Found @ 0x3FF[Offset: 0x107BE00]
• Bad Block ID @ 0x6 Found @ 0x3FE[Offset: 0x1077C00]
• Bad Block ID @ 0xBE Found @ 0x3FD[Offset: 0x1073A00]
• Bad Block ID @ 0xFD Found @ 0x3FC[Offset: 0x106F800]
• Bad Block ID @ 0xFE Found @ 0x3FB[Offset: 0x106B600]
I've literally tried every conceivable wire length and swap, every trick I could find from anyone on the Forum before making a new thread. Where I'm at now I'm wondering if the reset loop (fan ticking) is perhaps not being brought by the wire length so much as it may be from the console having the two bad blocks in the ecc area of the nand.
---------- Post added at 08:52 ---------- Previous post was at 08:48 ----------
PROBABLY UNRELATED:
But this is the first I've done with the SonusQSB installed as well, I highly doubt it would have much difference really, but it is the only difference from the others (aside from the obvious bad blocks)
This Trinity was also a M$ Replacement console, I know that on some of the phat consoles this resulted in a different CB structure however it seems to me that the CB and everything is right in line.
