Fusee Fatal Error: Unknown EmcDvfsTimingTableIndex: -1

[LiquidPaper]

Hello folks!
I recently purchased a Nintendo Switch brand new which is a Mariko with SkHynix memory, I already installed a modchip (the picofly from aliexpress which is ready to install with flex cables). I can enter to Hekate, I can launch CFW in sysNAND and OFW. But when I launch CFW on emuNAND. I get the fatal error: Error: Unknown EmcDvfsTimingTableIndex: -1. I wiped the emunand several times, I downloaded atmosphere, sigpatches, and hekate a lot of times... but no luck. Also I notice something weird, I opened console info in hekate and the row that shows the memory says "contact me!" and this tell me maybe this memory is not supported yet? who should I contact?

Any clue on this will be much appreciated! Thanks!

 

[masagrator]

Go here
https://discord.com/invite/CPAJfgej

And in #switch channel ping CTCaer and write your issue, including info about unsupported ram module.

 

[ListNowZfy]

Me having the almost same symptom. Help me, Please. BTW, your invitation link has expired.

My console info is as below, brand new Mariko bought days ago.

 

[detilmalala]

Me having the almost same symptom. Help me, Please. BTW, your invitation link has expired.

My console info is as below, brand new Mariko bought days ago.
View attachment 411398

same problem here, mariko too. 17.0.1, i dont know what is happening

 

[masagrator]

Use Hekate's fss0 method instead of Atmosphere's fusee payload.

 

[detilmalala]

Use Hekate's fss0 method instead of Atmosphere's fusee payload.

how do i do that? any tutorial?

 

[LiquidPaper]

same problem here, mariko too. 17.0.1, i dont know what is happening

@ListNowZfy @detilmalala as masagrator said, I ended up using fss0 to launch atmosphere. In your hekate_ipl.ini file, change the payload attribute.
Before:

[Atmosphere CFW]
payload=bootloader/payloads/fusee.bin
icon=bootloader/res/icon_payload.bmp

After:

[Atmosphere CFW]
fss0=atmosphere/package3
kip1patch=nosigchk
emummcforce=1
icon=bootloader/res/icon_payload.bmp

 

[SorataVP69]

@ListNowZfy @detilmalala as masagrator said, I ended up using fss0 to launch atmosphere. In your hekate_ipl.ini file, change the payload attribute.
Before:

[Atmosphere CFW]
payload=bootloader/payloads/fusee.bin
icon=bootloader/res/icon_payload.bmp

After:

[Atmosphere CFW]
fss0=atmosphere/package3
kip1patch=nosigchk
emummcforce=1
icon=bootloader/res/icon_payload.bmp

You are my savior thank you very much I had the same problem