Infectus Problems

**StillBlue** · 11-10-2011,02:58 PM

I have my my infectus set up using a 360-clip soldered to it.

After dumping the NAND's on my FAT a few times, until I was happy with it, I edited the dumps as per the dospiedras method and started to rewrite them to the NAND's. The first NAND wrote fine, then the Infectus wouldn't connect to the second one. After trying again and again, I put it back to the chip I had already rewritten and no sucess with that one now.

After a closer look, it appeared the infectus firmware had corrupted.

I have gone back to reinstall the firmware to infectus and I am getting the following.

When I try to load the .dat file I get:-

Code:

ActID = 02a121cf
ExpID = 02a121cf
Initializing Target Device...
Setting BSR Configurations...
Reading Security...
Verifying FPGA Array...
Verify 0 failed Row Number : 1242

And it comes back with 'Failed to Verify FPGA'

If I try to erase I get:-

Code:

ActID = 02a121cf
ExpID = 02a121cf
Initializing Target Device...
Setting BSR Configurations...
Reading Security...
Erase...
ACTEL_SLOG_UROW = 
FF FF FF FF BB E5 70 2B 10 08 04 02 C1 06 C9 00 
Programming UROW...

And it comes back with 'Failed to Program UROW'

I'm hoping that someone here can give me some guide what to do now. I am hoping that the infectus hasnt failed, as I'm really happy with the soldering job, and how easy it was just shoving the 360-clip on to the NAND!!

TIA

**hedak** · 11-10-2011,05:28 PM

Hi,

i tried to read/write my NAND flashes with infectus v2 months ago. As it didnt work i used the latest infectus software which updated the infectus firmware. But then the infectus software didnt have the "Double NAND" option anymore and i put this topic away. A few weeks ago i accidentally found an infectus firmware to downgrade the infectus (which wasnt possible before) to get "Double NAND" option back. But somehow my infectus couldnt be flahed anymore. I got the same errors you have (other numbers).

I think the fpga is defect. I was looking for a solution, but never found one. I only found the datasheet of that fpga... I thought of contacing the progseek team as they wrote that they bought many infectus chips (regarding their dual booting solution) to using the infectus programming chip (the smaller circuit board). So they should have a lot of fpga circuit boards left...

(Btw, if i got the infectus working again i wanted to use the solderless 360-clip)

If u find a solution, please contact me. I wish you good luck!

**StillBlue** · 11-11-2011,07:23 AM

Something I can't quite work out is the UROW error.

If I load the '17_0102A121_double_nand' dat, and then go to Erase, I get:-

Code:

ActID = 02a121cf
ExpID = 02a121cf
Initializing Target Device...
Setting BSR Configurations...
Reading Security...
Erase...
ACTEL_SLOG_UROW = 
FF FF FF FF BB E5 70 2B 10 08 04 02 C1 0A C9 00 
Programming UROW...

Then I get 'Failed to Program UROW'.

Whereas if I load the '17_0102A121_double_nand' dat, and then go to Program I get:-

Code:

ActID = 02a121cf
ExpID = 02a121cf
Initializing Target Device...
Setting BSR Configurations...
Reading Security...
Performing Data Authentication...
.
.
.
.
.
.
.
.
.
.
.
.
.
Erase...
ACTEL_SLOG_UROW = 
FF FF FF FF BB E5 70 2B 10 08 04 02 01 0B C9 00 
Programming UROW...
Programming FPGA Array...
.
.
.
.
.
.
.
.
.
.
.
.
.
Verifying FPGA Array...
Verify 1 failed Row Number : 1243

I then get 'Failed to verify FPGA' but it does look like it managed to program UROW ok this time.

Also the row number it has failed on seems to have changed (gone up one number) since I was trying yesterday.

Is this bad hardware, or firmware/loader problems?

Did Infectus give any other .dat files?

**hedak** · 11-11-2011,10:40 AM

Here's my failure code (only erasing gives the same error):

Code:

ActID = 02a121cf
ExpID = 02a121cf

Initializing Target Device...

Setting BSR Configurations...

Reading Security...

Performing Data Authentication...
.
.
.
.
.
.
.
.
.
.
.
.
.

Erase...

ACTEL_SLOG_UROW = 
00 00 04 40 BB E5 70 2B 10 08 04 02 01 00 48 00 

Programming UROW...

Failed UROW programming

**hedak** · 11-11-2011,10:41 AM

Here's my failure code (only erasing gives the same error):

ActID = 02a121cf
ExpID = 02a121cf

Initializing Target Device...

Setting BSR Configurations...

Reading Security...

Performing Data Authentication...
.
.
.
.
.
.
.
.
.
.
.
.
.

Erase...

ACTEL_SLOG_UROW =
00 00 04 40 BB E5 70 2B 10 08 04 02 01 00 48 00

Programming UROW...

Failed UROW programming

**StillBlue** · 11-13-2011,06:35 AM

I have found the following on a german website (cant post a link due to not enough posts),

This is roughly translated by Google:-

Written by Chip World on 29/02/2008 at 11:41:

Argon: about faulty chips

Should you have you bought a Wii after the argon and the following is
Installation shown, the chip is faulty (which is a production error)!

Here is the error description:

First The chip can be flash, but breaks off at the Verifying and following error message occurs:

Verifying FPGA - Array
Verify 0 failed
Row Number: 1243

------

Second The LED is not lit and when flashing the following message:

Error:
"IDCODE = ffffffff

STAPL_IDCODE = 2a121cf

The chips were exchanged by the relevant dealers without problems
be because the production error was confirmed by Infectus Team
and will replace any defective chips.

There are approximately 10% of the affected chips extradited

**hedak** · 11-13-2011,11:07 AM

Can u send me a private message with the link? I'm german

**StillBlue** · 11-13-2011,02:18 PM

I would if I could find a PM link anywhere!!!

tinyurl . com / blwbku3

**hedak** · 11-14-2011,11:16 AM

U are right. I cant PM anymore too...

Your google-translation is ok. There is nothing to misinterpret.

It seems as if you have exactly the issue that is described there. When (and where) did you buy your infectus?

**StillBlue** · 11-21-2011,05:54 AM

I purchased it from mrmodchips, he has finally got back to me after a week (says within 6 hours on his website), basically saying that there is nothing wrong with the chip, its the soldering!!

Bit of a shame really, as if he had been a bit more helpful I would have probably bit the bullet, and got another one from him. Think I will go elsewhere now though. I had seen a lot of bad press about him, but thought I would give him a chance.

Found elsewhere on the internet now that suppliers were sent a note from Infectus making them aware of this problem. Would be handy to get hold of a copy of that.

Still seems a strange fault though!

User Tag List

Thread: Infectus Problems

Tweet

LinkBack

Thread Tools

Display


	Would you like to get all the new info from PSX-Scene in your email each day? Subscribe to our Daily Digest! Want to learn more about the team keeping you up to date with the latest scene news? Read about them now! Check out our Developer bios, too!