next »

[mabcom]

 Oke i have played a bit with the Argon and a external clock (i have used one of Modbo chip i had laying around)

And the results are as following

i have used the 2.0 and 2.5 beta firmwares

on 2.0  the drive stays a live and with power on i can get a backup running in 80% of the cases (M-galaxy) if i do a Reset i can reboot the game in 70% of the occasion but in 30% of the occasians it does not show up or i get the message that the disk is not readable
the eject bug keeps exisisting but this has to do with some missing code in the argon

on the 2.5 firmware the results are a bit less

on most occasion i get a complete lockup of the system and in some occasions it boots a game , i think that in the 2.5 they already experimented with the clock in the firmware

what the infectus team should decide fast is to see of they can get the firmware stable on the existing clock of the argon or just be honnest and tell us to use a external clock (is is pretty easy to ad it to the argon)

if they are struggling to long with that in my opinion easy solution of a external clock they can better release a optimised firmware with the fixed 50mhz frequenty and continue on fixing the eject bugs

this is probably not what most of the people want to hear but it is impossible to make a mod future proof,
you can afcourse reprogram it with a Jtag a lot more then in the past because you can reprog the acatel but this is only a processor and in some occasions you just need some addons to make it useable in new situations,even a resistor can be needed in some occasions

what argon should do is to make the chip a bit larger and Ad some extra solder points on where you can solder some new components ,from where you can rewire to the acatel ,on this way you can say that you have a 95% future proof modchip
and a bit experiented  modder can easy ad some revision changes ,like last time we had to ad the spi and now we should in my opinion ad a clock

i will wait and see what the comming beta shows us, otherwise just tell everyone to ad the extra 2 dollar component ,because i keep repeating is not a real big deal for most of us ,

i have decided not to post any picures of my addon clock because i don't want to let other people experiment without any experience,because there is some risk that if the clock frequenty is not correct you can kill your drive or Modchip

if Infectus release a optimized firmware i have no problem to show a how to do

with regards
MABCOM


Ps long story's are always difficult for me to do in english so please don't flame me because of wrong used words also if you can make some spelling changes please do so that for other people it is also readable

so now i gonna start my free weekend

[Jadgamez]

Just tested this code on a D2C V1 (no eject problem running 1.1)

V2b:
Will load every time from power on, but from disc insert screen it will just flash “insert disc” with blue led on drive flashing too. The drive has locked up and must be powered down to fix. Disc does eject but only when powered down and rebooted.

V2.5b:
Will not load up anything even from a power down cycles it either gets stuck in the insert disc loop or unable to read disc. Disc will only eject when its say “disc unrecognized” in the disc channel.

Now you have my results I hope V3 will be more stable as its back to V1.1 for me as that worked 100% every time 

P.S. I don't believe that you had 10 beta testers check this code I think you rushed it out and WE are the beta testers.

[idog]

Oke i have played a bit with the Argon and a external clock (i have used one of Modbo chip i had laying around)

And the results are as following

i have used the 2.0 and 2.5 beta firmwares

on 2.0  the drive stays a live and with power on i can get a backup running in 80% of the cases (M-galaxy) if i do a Reset i can reboot the game in 70% of the occasion but in 30% of the occasians it does not show up or i get the message that the disk is not readable
the eject bug keeps exisisting but this has to do with some missing code in the argon

on the 2.5 firmware the results are a bit less

on most occasion i get a complete lockup of the system and in some occasions it boots a game , i think that in the 2.5 they already experimented with the clock in the firmware

what the infectus team should decide fast is to see of they can get the firmware stable on the existing clock of the argon or just be honnest and tell us to use a external clock (is is pretty easy to ad it to the argon)

if they are struggling to long with that in my opinion easy solution of a external clock they can better release a optimised firmware with the fixed 50mhz frequenty and continue on fixing the eject bugs

this is probably not what most of the people want to hear but it is impossible to make a mod future proof,
you can afcourse reprogram it with a Jtag a lot more then in the past because you can reprog the acatel but this is only a processor and in some occasions you just need some addons to make it useable in new situations,even a resistor can be needed in some occasions

what argon should do is to make the chip a bit larger and Ad some extra solder points on where you can solder some new components ,from where you can rewire to the acatel ,on this way you can say that you have a 95% future proof modchip
and a bit experiented  modder can easy ad some revision changes ,like last time we had to ad the spi and now we should in my opinion ad a clock

i will wait and see what the comming beta shows us, otherwise just tell everyone to ad the extra 2 dollar component ,because i keep repeating is not a real big deal for most of us ,

i have decided not to post any picures of my addon clock because i don't want to let other people experiment without any experience,because there is some risk that if the clock frequenty is not correct you can kill your drive or Modchip

if Infectus release a optimized firmware i have no problem to show a how to do

with regards
MABCOM


Ps long story's are always difficult for me to do in english so please don't flame me because of wrong used words also if you can make some spelling changes please do so that for other people it is also readable

so now i gonna start my free weekend

Thanks for the efforts man
I took your tip of wrapping the clock wire with ground and used it on D2Pro installs. No issues whatsoever. And for what it's worth.. you're right

[XeroX]

Oke i have played a bit with the Argon and a external clock (i have used one of Modbo chip i had laying around)

And the results are as following

i have used the 2.0 and 2.5 beta firmwares

on 2.0  the drive stays a live and with power on i can get a backup running in 80% of the cases (M-galaxy) if i do a Reset i can reboot the game in 70% of the occasion but in 30% of the occasians it does not show up or i get the message that the disk is not readable
the eject bug keeps exisisting but this has to do with some missing code in the argon

on the 2.5 firmware the results are a bit less

on most occasion i get a complete lockup of the system and in some occasions it boots a game , i think that in the 2.5 they already experimented with the clock in the firmware

what the infectus team should decide fast is to see of they can get the firmware stable on the existing clock of the argon or just be honnest and tell us to use a external clock (is is pretty easy to ad it to the argon)

if they are struggling to long with that in my opinion easy solution of a external clock they can better release a optimised firmware with the fixed 50mhz frequenty and continue on fixing the eject bugs

this is probably not what most of the people want to hear but it is impossible to make a mod future proof,
you can afcourse reprogram it with a Jtag a lot more then in the past because you can reprog the acatel but this is only a processor and in some occasions you just need some addons to make it useable in new situations,even a resistor can be needed in some occasions

what argon should do is to make the chip a bit larger and Ad some extra solder points on where you can solder some new components ,from where you can rewire to the acatel ,on this way you can say that you have a 95% future proof modchip
and a bit experiented  modder can easy ad some revision changes ,like last time we had to ad the spi and now we should in my opinion ad a clock

i will wait and see what the comming beta shows us, otherwise just tell everyone to ad the extra 2 dollar component ,because i keep repeating is not a real big deal for most of us ,

i have decided not to post any picures of my addon clock because i don't want to let other people experiment without any experience,because there is some risk that if the clock frequenty is not correct you can kill your drive or Modchip

if Infectus release a optimized firmware i have no problem to show a how to do

with regards
MABCOM


Ps long story's are always difficult for me to do in english so please don't flame me because of wrong used words also if you can make some spelling changes please do so that for other people it is also readable

so now i gonna start my free weekend

Can you show us a picture of your added clock ?

[DnD]

Can you read ?

i have decided not to post any picures of my addon clock because i don't want to let other people experiment without any experience,because there is some risk that if the clock frequenty is not correct you can kill your drive or Modchip

but if you know what you are doing XeroX its really not so hard to add that clock

[moely]

Thanks for the efforts man
I took your tip of wrapping the clock wire with ground and used it on D2Pro installs. No issues whatsoever. And for what it's worth.. you're right

Yes, same experience here with D2Pro. I first tried without wrapping the clock wire with ground and also that was working quite well. I inserted and ejected a disc 50 times and just once I had the EJECT issue. Now I have wrapped the wire and it didn't happen anymore. But I have to admit that it takes more time to now for sure that this issue is really gone.

[idog]

Thanks for the efforts man
I took your tip of wrapping the clock wire with ground and used it on D2Pro installs. No issues whatsoever. And for what it's worth.. you're right

Yes, same experience here with D2Pro. I first tried without wrapping the clock wire with ground and also that was working quite well. I inserted and ejected a disc 50 times and just once I had the EJECT issue. Now I have wrapped the wire and it didn't happen anymore. But I have to admit that it takes more time to now for sure that this issue is really gone.

en dan noem je mij een nachtbraker

Still no probs here as well. Seems like a solid piece of advise from Mabcom

[chris2k2]

which one is the clock wire.? J or C .? and also you got a piccy.??

[idog]

which one is the clock wire.? J or C .? and also you got a piccy.??

C

Wires could be routed better, I agree.. but just to give you an idea:

http://img27.picoodle.com/img/img27/4/6/14/f_idogD2pro9vm_479bcb1.jpg

Ah, and in case you're wondering. The other end of the purple wrapped wire is outside the picture but goes to a ground point.

[rataplan]

Ah, and in case you're wondering. The other end of the purple wrapped wire is outside the picture but goes to a ground point.

I am not sure that one is right. Perhaps you must connect one point only otherwise it picks up new interferences. Hoping not to be in error ...

[Jadgamez]

I am not sure that one is right. Perhaps you must connect one point only otherwise it picks up new interferences. Hoping not to be in error ...

No it won't as GND is GND. idog has done it correctly.

[chris2k2]

which one is the clock wire.? J or C .? and also you got a piccy.??

C

Wires could be routed better, I agree.. but just to give you an idea:

http://img27.picoodle.com/img/img27/4/6/14/f_idogD2pro9vm_479bcb1.jpg

Ah, and in case you're wondering. The other end of the purple wrapped wire is outside the picture but goes to a ground point.

cheers..ill give that a try on my sisters wii...it plays up quite a lot using the d2pro9....

im gonna try the alt points aswell.....

[rataplan]

I am not sure that one is right. Perhaps you must connect one point only otherwise it picks up new interferences. Hoping not to be in error ...

No it won't as GND is GND. idog has done it correctly.

you suppose that ground is the same ground in any point of the circuit but this is not true. This is known well and can cause interferences if a wire is connected so as to create a current like a ring. You can find probably an explanation in English language (for me not easy) here  http: /en.wikipedia.org/wiki/Ground_loop_(electricity)

[chris2k2]

i agree with the above, but the examples used are inappropriate here....

they are talking about several pieces of equipment connected to different ac outlets...and connected to each other via cables....the chip and the wii use the same ground and +v supply rails so there wont be any ground loops...if there was the wii wouldnt operate correctly...the system would crash due to noise on data rails. sometimes on electrical items there are 2 ground connections. 1 for general power supply outputs and 1 known as a digital ground which is common to all digital devices. there maybe 2 ics connected together using different ground points but the output from one to the other will become common along the line. usualy on the output on one and input on the other........

[moely]

Well, I don't think that the two points to GND will give a problem in this case. I've tried and tested one point connected to GND and two points like idog did. It seems two points gives a better result regarding the EJECT issue.
But only after intensive testing in several days one can be sure.