Switch OLED Instinct-NX V6S eMMC Write Cache and Estimated Life

[Khontrail]

Hello, Does anyone know what the problem is with my Switch OLED?

I recently installed the Instinct-NX V6S in my Switch OLED and ran in to a couple problems. Sometimes the console boots in to Hekate immediately and sometimes it takes 25 seconds. Sometimes when loading in to a game in the cfwemmc games will crash with the message "The software was closed because an error occurred", but immediately after relaunching it the second time, the game will launch and work normally. This was not normal to me so I did some digging around under the Internal eMMC Info page within Hekate and found out that the Write cache was set to "2 MiB" instead of "64 MiB". Also, I noticed the Estimated Life was set to "A: -, B: 100%" instead of "A: 100%, B: 100%"

I included a picture of the Internal eMMC Info page.

Does anyone know if this is normal for some Switches or is there a way to fix this? possible DAT0 problem or cooked RAM module? If it aint broke, dont fix it? Let me know, thanks!

 

[jkyoho]

emmc info is normal. I have same hynix NAND.
glitch timing is really depending on the way you do dat0(adapter, permeant wiring or kamikaze grinding) plus what modchip you use. 25sec is kind of on the long side but acceptable IMO.

 

[Khontrail]

emmc info is normal. I have same hynix NAND.
glitch timing is really depending on the way you do dat0(adapter, permeant wiring or kamikaze grinding) plus what modchip you use. 25sec is kind of on the long side but acceptable IMO.

Thank you for your reply. I am using the Instinct-nx v6s on fw 2.0 using the dat0 adapter. Do you think its possible that the wire gauge and length could be causing these extended boot times? I understand samsung NAND is the fastest. I see that you said were using the same hynix NAND, is your write cache and estimated life ratings the same as mine?

 

[jkyoho]

is your write cache and estimated life ratings the same as mine?

yes, same 2MiB

Do you think its possible that the wire gauge and length could be causing these extended boot times?

No, the gauge of wire using on a signal line(dat0) does not matter. It is the adapter style been used giving inconsistency

 

[Khontrail]

yes, same 2MiB

No, the gauge of wire using on a signal line(dat0) does not matter. It is the adapter style been used giving inconsistency

Ok thats a huge relief! The adapter is the updated version that has 4 ground points. I only used the top two ground points. Console works great and glitches everytime, its just that sometimes it looks like its relearning after shutting down and the chip blinks red 25 times and then turns green and boots. Sometimes it blinks red like 3 times and then steady green in to successful boot.

I also have a V2 switch running rp2040 with a samsung NAND. It boots immediately everytime no matter what and the Estimated Life: A 100%, B 100%. so I thought my OLED hynix was half working since I didnt get a reading for A.

Do you know what the A and B is for? I was thinking it was A ram and B ram like a pc motherboard but it didnt make sense to me since I believe the NAND is storage.

all in all Im happy im getting a Max Rate of 400mb/s as I know others had problems with that...

 

[jkyoho]

Do you know what the A and B is for? I was thinking it was A ram and B ram like a pc motherboard but it didnt make sense to me since I believe the NAND is storage.

quick looking up from Hekate code, I guess that A/B is just some different kind of calculation type for nand life-time. No big deal. Hynix tends to be less reliable than samsung anyway

 

[Khontrail]

quick looking up from Hekate code, I guess that A/B is just some different kind of calculation type for nand life-time. No big deal. Hynix tends to be less reliable than samsung anyway

Oh man Im glad to hear it. Thanks for all the information, its been a great help!