June 11th, 2022, 4:22
June 11th, 2022, 5:55
June 12th, 2022, 3:35
June 12th, 2022, 5:56
suricate.ch wrote:Do you have PC-3000 Portable ? I had a similar issue (always BSY) and I could image it with turn on/off hardware function, it was RDY for 0.5 sec everytime I powered it on, it took a coupld of hours but result was perfect.
June 12th, 2022, 7:19
June 12th, 2022, 7:49
Can you post a screen shot.speakerbox wrote:Yes I do have PC3000 Portable
The drive stays in RDY mode but does not ID (no passport)
June 12th, 2022, 11:00
Lardman wrote:Can you post a screen shot.speakerbox wrote:Yes I do have PC3000 Portable
The drive stays in RDY mode but does not ID (no passport)
June 12th, 2022, 11:08
lcoughey wrote:Why swap the controller?
June 12th, 2022, 12:55
June 12th, 2022, 13:43
digisupport wrote:+1 for MCU is working. Trouble is degraded slow NAND or bit errors in FW.
Swapping MCU or NAND will not help.
June 12th, 2022, 14:24
June 13th, 2022, 6:04
June 13th, 2022, 8:14
speakerbox wrote:- The drive loads firmware from the masked ROM (in the MCU) to the RAM and proceeds its execution
- Memory chips test
- Drive loads main firmware portion from memory chips to RAM and transfers control to it
- The drive reads the structures from SA and generates the translator
- Drive reads its config pages
June 13th, 2022, 8:22
June 13th, 2022, 8:57
lcoughey wrote:speakerbox wrote:- The drive loads firmware from the masked ROM (in the MCU) to the RAM and proceeds its execution
- Memory chips test
- Drive loads main firmware portion from memory chips to RAM and transfers control to it
- The drive reads the structures from SA and generates the translator
- Drive reads its config pages
In the previous post you suggest that the firmware is stored in the controller, then you make this post. There may be some generic firmware code in the controller, but the bulk of it is definitely stored on the degraded NAND. If the board behaved like it had a short, the controller could be one of the many points of failure, thus why it is sometimes easier (a relative term with these coated Apple SSDs) to transplant the NAND to a known working board.
In your cases, I'm 99.9% sure that swapping the ROM would not fix this firmware issue any more than swapping a PCB would fix a firmware issue on a failing hard drive.
It seems to me, there was no point in your asking the question if you are already convinced that it will work. I suggest you go for it and report back with the final result.
June 13th, 2022, 8:58
suricate.ch wrote:Can you get ID if you try to access rom mode, need to short jumper. Not sure which one.
June 13th, 2022, 17:54
suricate.ch wrote:Can you get ID if you try to access rom mode, need to short jumper. Not sure which one.
June 23rd, 2022, 7:21
June 23rd, 2022, 7:24
suricate.ch wrote:Yesterday I had a case like that, highly unstable AHCI SSD. Apple SSD SM0128 GB, SSD is ready but get BSY instantanely when reading, I get ID. So I am cloning with PC3K -Portable, switch on/off, it will take 3-4 days but it's working.
June 23rd, 2022, 7:43
suricate.ch wrote:Yesterday I had a case like that, highly unstable AHCI SSD. Apple SSD SM0128 GB, SSD is ready but get BSY instantanely when reading, I get ID. So I am cloning with PC3K -Portable, switch on/off, it will take 3-4 days but it's working.
Powered by phpBB © phpBB Group.