PS3Key LED Flickering constantly!!!

[csta]

Ever since i as many people updated there PS3Key's the LED is Flickering constantly!!!

I have updated to the latest Firmware on my PS3Key 2.3 and still same thing from red to blue and repeats its self constant!!!

I key never done this when i first got it but after them promising to fix this problem still no fix to fix the led light fault!!!

I tryed everything from jumping bk to earlyier updates with no success please help!!!

[Pawsed]

Ever since i as many people updated there PS3Key's the LED is Flickering constantly!!!

I have updated to the latest Firmware on my PS3Key 2.3 and still same thing from red to blue and repeats its self constant!!!

I key never done this when i first got it but after them promising to fix this problem still no fix to fix the led light fault!!!

I tryed everything from jumping bk to earlyier updates with no success please help!!!

I'm sorry to say that their code isn't open, and we have little option to help. The same applies even to their AVRKey code, which when they DO bother to release as PS3key Open, they don't include the source, just the hex file. This is why we are unable to simply write one file with LED code for AVRKey and compile it right away with the latest builds of PSGroove.

If you are confused at the difference between the two, there are vast differences.

This thread is very well written and explains a lot of questions about the two devices that are quite vague it would seem from the seller and manufacturer:
http://psx-scene.com/forums/f181/bet...-avrkey-67397/ (Better understanding between PS3Key and AVRKey)

The main difference is that the PS3Key comes with a PS3Key bootloader on it that uses their own .upd format, so you have to wait on their releases to update that way. The AVR uses an AVR Bootloader that uses .hex releases compiled here (or when they get around to releasing PS3Key 'Open' versions, something they haven't done since v2.1). As stated, we do not have an LED source to use, but both chips use a ATMega32u2, as does the Teensy1.0, so using that hex will always work (without LEDs as the Teensy1.0 has none).

Your options are this: You can wait for PS3Key to update their own releases, as we do not. Or you can flash your PS3Key with an AVR Boot loader (This is not reversible as far as I know, it may be but just a warning) and use it as an AVR. Once it's flashed as an AVR, you'll be able to use Teensy1.0 hex files that are usually one of the first you'll find compiled. However, as stated, the LEDs wont work because Teensy has none. But the chip is the same, and it will work will all the latest PSGroove features.

The fact is that even PS3Key v2.3 doesn't include hermes v3 (they're 'testing' that still according to their news), so v2.3 isn't even up to date with. Not to mention they haven't put v2.3 Open hex out for AVRKey yet, and it'll be behind the times when it does come.

Simply put, my suggestion is to use Teensy1.0 hex files and no LEDs until a later date. At some point, the scene releases will slow down, and time between them will be so much that the PS3Key will get their up to date version out, and their up to date Open version soon after...and that will fix your LEDs. Until such time, with these constant updates, just get the Teensy1.0 hex.

[dcemureviews]

I'm sorry to say that their code isn't open, and we have little option to help. The same applies even to their AVRKey code, which when they DO bother to release as PS3key Open, they don't include the source, just the hex file. This is why we are unable to simply write one file with LED code for AVRKey and compile it right away with the latest builds of PSGroove.

If you are confused at the difference between the two, there are vast differences.

This thread is very well written and explains a lot of questions about the two devices that are quite vague it would seem from the seller and manufacturer:
http://psx-scene.com/forums/f181/bet...-avrkey-67397/ (Better understanding between PS3Key and AVRKey)

The main difference is that the PS3Key comes with a PS3Key bootloader on it that uses their own .upd format, so you have to wait on their releases to update that way. The AVR uses an AVR Bootloader that uses .hex releases compiled here (or when they get around to releasing PS3Key 'Open' versions, something they haven't done since v2.1). As stated, we do not have an LED source to use, but both chips use a ATMega32u2, as does the Teensy1.0, so using that hex will always work (without LEDs as the Teensy1.0 has none).

Your options are this: You can wait for PS3Key to update their own releases, as we do not. Or you can flash your PS3Key with an AVR Boot loader (This is not reversible as far as I know, it may be but just a warning) and use it as an AVR. Once it's flashed as an AVR, you'll be able to use Teensy1.0 hex files that are usually one of the first you'll find compiled. However, as stated, the LEDs wont work because Teensy has none. But the chip is the same, and it will work will all the latest PSGroove features.

The fact is that even PS3Key v2.3 doesn't include hermes v3 (they're 'testing' that still according to their news), so v2.3 isn't even up to date with. Not to mention they haven't put v2.3 Open hex out for AVRKey yet, and it'll be behind the times when it does come.

Simply put, my suggestion is to use Teensy1.0 hex files and no LEDs until a later date. At some point, the scene releases will slow down, and time between them will be so much that the PS3Key will get their up to date version out, and their up to date Open version soon after...and that will fix your LEDs. Until such time, with these constant updates, just get the Teensy1.0 hex.

Theres no way to install HEX onto PS3Key. FLIP will not recognize it and PS3Key has not stated to me or even on the web as to even how to do this. All they said to me was that you can install HEX but can not put back PS3Key updates.

[Pawsed]

All they said to me was that you can install HEX but can not put back PS3Key updates.

This implies there is a way to erase the encrypted bootloader and replace it with AVRKey's AVR DFU Bootloader. Thus, making it an AVRKey. They state you could no longer put back PS3Key updates because the PS3Key bootloader is encrypted and we have no way of reflashing it once you erase it. However, as they have been producing more and more AVRKey instead of PS3Key for legal reasons, they've started to release Open Version of their own code, compiled already as a .hex, for AVRKeys.

Internally, they are EXACTLY the same device. One just comes with the PS3Key encrypted bootloader on it which uses .upd, the other comes with AVR DFU Bootloader which uses FLIP and .hex files. They will continue to support both by releasing 'Open' versions of their code for the AVRKey, so converting your PS3Key to an AVRKey wouldn't be a terrible idea; you'd get teensy1.0 updates fast in the short term, and long term you could use PS3Key's Open .hex files as they release them.

I haven't figured out yet how to reflash the bootloader, but I'm sure there is a way. They even said "you can install HEX but can not put back PS3Key updates." That statement implies it can be done.

[csta]

i was only asking if this is normal to other PS3Key customers after updating there sticks

[tsb]

mine alternates while loading and stays blue after success on 2.3

[Wraith92]

Theres no way to install HEX onto PS3Key. FLIP will not recognize it and PS3Key has not stated to me or even on the web as to even how to do this. All they said to me was that you can install HEX but can not put back PS3Key updates.

I'm really confused here. DCEmureviews you have said repeatedly that there is NO way to install .hex files to PS3Key, but according to your above post team PS3Key has said you can do it there is just no way to go back if you do. My question is this; you have posted threads like better understanding the difference between AVRKey and PS3Key, but are you as unclear as the rest of us on this issue. It seems that if you are going to advise posters that there is NO way to do something then you should just say that. According to your own post here above you seem to suggest that according to PS3Key there is in fact a way to do it. It seems YOU, like the rest of us are just unclear as to how to make this happen. I am not flaming you, not personally attacking you, but there is 1 user that I can think of who posted in UDIP's hermes update post that managed to flash AT90USB162 to his PS3Key, and later posted a frown after he discovered his LED's did not work after the flash. I don't want to get into a war of words, but if necessary I will link the post. Anyway, no offense to you and my apologies to you if I have done so, but just please be clear. Your above post is one of the most convoluted things I have ever read.

[dcemureviews]

I'm really confused here. DCEmureviews you have said repeatedly that there is NO way to install .hex files to PS3Key, but according to your above post team PS3Key has said you can do it there is just no way to go back if you do. My question is this; you have posted threads like better understanding the difference between AVRKey and PS3Key, but are you as unclear as the rest of us on this issue. It seems that if you are going to advise posters that there is NO way to do something then you should just say that. According to your own post here above you seem to suggest that according to PS3Key there is in fact a way to do it. It seems YOU, like the rest of us are just unclear as to how to make this happen. I am not flaming you, not personally attacking you, but there is 1 user that I can think of who posted in UDIP's hermes update post that managed to flash AT90USB162 to his PS3Key, and later posted a frown after he discovered his LED's did not work after the flash. I don't want to get into a war of words, but if necessary I will link the post. Anyway, no offense to you and my apologies to you if I have done so, but just please be clear. Your above post is one of the most convoluted things I have ever read.

Please provide link. It may be confusing but I'm going by what my source has told me and from my own personal experience. As you can tell already, PS3Key isnt clear on things themselves and give half an answer. I've tried using FLIP on PS3Key, PS3Key updater with HEX and neither work or can be recognized. That is why I'm saying it cant be done. But PS3Key says it can.

I guess the only way would be to see if they would tell me how it can be done.

This implies there is a way to erase the encrypted bootloader and replace it with AVRKey's AVR DFU Bootloader. Thus, making it an AVRKey. They state you could no longer put back PS3Key updates because the PS3Key bootloader is encrypted and we have no way of reflashing it once you erase it. However, as they have been producing more and more AVRKey instead of PS3Key for legal reasons, they've started to release Open Version of their own code, compiled already as a .hex, for AVRKeys.

Internally, they are EXACTLY the same device. One just comes with the PS3Key encrypted bootloader on it which uses .upd, the other comes with AVR DFU Bootloader which uses FLIP and .hex files. They will continue to support both by releasing 'Open' versions of their code for the AVRKey, so converting your PS3Key to an AVRKey wouldn't be a terrible idea; you'd get teensy1.0 updates fast in the short term, and long term you could use PS3Key's Open .hex files as they release them.

I haven't figured out yet how to reflash the bootloader, but I'm sure there is a way. They even said "you can install HEX but can not put back PS3Key updates." That statement implies it can be done.

Yes, it can be done but no one has found out how and my source at PS3Key has not told me how to do so. From the looks of it now, theres more updates with PS3Key than there is with the open hex. And whoever plans on putting HEX files should of gotten a AVRKey and not a PS3Key.

[Wraith92]

Yes, it can be done but no one has found out how and my source at PS3Key has not told me how to do so. From the looks of it now, theres more updates with PS3Key than there is with the open hex. And whoever plans on putting HEX files should of gotten a AVRKey and not a PS3Key.

Why, it is our device. Bought and paid for. We don't need you to tell us which device we should have purchased. In point of fact, some sellers had the item listed as PS3Key/AVRKey and stated that the name was only changed for legal reasons. If PS3Key had not intended for the end user to decide what to flash it with they would not have posted this on their site:

Optionally PS3Key can be supplied with an "open" firmware which does not support backup loading. Users would then have to download a firmware update for PS3Key to get full functionality.

[dcemureviews]

Why, it is our device. Bought and paid for. We don't need you to tell us which device we should have purchased. In point of fact, some sellers had the item listed as PS3Key/AVRKey and stated that the name was only changed for legal reasons. If PS3Key had not intended for the end user to decide what to flash it with they would not have posted this on their site:

Optionally PS3Key can be supplied with an "open" firmware which does not support backup loading. Users would then have to download a firmware update for PS3Key to get full functionality.

If you dont like my opinion, ignore me. Seriously, I dont know what your problem is. I'm here to help and inform people since I own both products and speaking from experience.

The sellers are confused themselves because it doesnt seem like there was a name change...was there? PS3Key comes preloaded with files. AVRKey is blank. Thats where the whole confusion got.

As stated, PS3Key isnt clear in explaining or describing themselves. Thats also why things got confused and it doesnt help when both products have the same hardware and no logo.

Maybe I should contact PS3Key and have them update that so there is no confusion. Than again, it could be there as a "legal" reason when in fact, it comes preloaded. I dont know what their intentions or reason for that was. Maybe you want to read what they wrote again...

Optionally PS3Key can be supplied with an "open" firmware which does not support backup loading. Users would then have to download a firmware update for PS3Key to get full functionality.

Ummmm....last time I checked the "open" firmware (which is the HEX), it supported backup loading. PS3Key also has support for backup loading out of the static bag. So you really want to take PS3Key's info word for word? Think about it.