Picofly in Switch V1 Erista "unknown pkg1 version hos version not supported"

[Paulo_Suzuki]

I would like to ask a question if you could help me, I have the attached problem on a switch v1 console, I just soldered a picofly but I always get this screen, I have already downloaded and copied several files, including the latest version of atmosphere, latest version hekate, I tried with cnx and several others, they all show the same error, I replaced the micro SD with other genuine brands and got the same result, do you know what could be happening?

 

[zamastyle]

This is usually a bad sd card setup with something out of date. Try using the HATS pack on a clean sd card and see if it boots.

 

[E1ite007]

I would suggest instead of running any pack like HATS or jits, just trying to run plain Atmosphere first. Then you can use whatever pack pleases you.
Also, you should verify the integrity of the SD card with H2TestW, just do a whole backup of the SD card before. It may be that your SD is dying.

 

[Paulo_Suzuki]

Thanks for the answers, the micro sd was tested with htestw, and I also put the clean atmosphere package, I still get the same problem. Has anyone else experienced this problem with the V1 model?

 

[Ondrashek06]

HOS = HorizonOS, i.e. the firmware.

There's a mismatch in something related to the boot sequence - are both your sysMMC and emuMMC on the same version?

 

[Paulo_Suzuki]

HOS = HorizonOS, i.e. the firmware.

There's a mismatch in something related to the boot sequence - are both your sysMMC and emuMMC on the same version?

I just updated the picofly firmware again, I put ATMO 1.6.2 and the latest hekate, I changed 5 different original cards and tested in htestw (sandisk, lexar). I removed the chip to check the current system version, which is 16.0.3. Would the firmware incompatibility you are referring to be the firmware of the chip? I'm trying to start with sysmmc and ofw with the chip and I get the same error, does anyone have any packages available for version 16.0.3 that I could test on?

 

[zamastyle]

I suggested trying hats because its known good starting point. It may not be what you want to use but at the very least you will know whether your switch boots with a known good setup and if it does, you will have baseline for comparing your own set up to. If it still won't boot with HATS, then the software probably isnt the issue.

https://github.com/sthetix/HATS/releases/tag/1.6.2

 

[E1ite007]

-snip-

 

[deeps]

try the emmc benchmark in hekate

 

[Paulo_Suzuki]

try the emmc benchmark in hekate

I ran this test, it informed me that the emmc is in slow mode, could this be the cause of the problem? I think it's strange that this is the reason for the problem because I can start the console normally in OFW. I'm using the picofly tiny, which already has the resistors.

 

[zamastyle]

Thats not great. If you havent already, take a full backup and dump your keys.

 

[deeps]

I ran this test, it informed me that the emmc is in slow mode, could this be the cause of the problem? I think it's strange that this is the reason for the problem because I can start the console normally in OFW. I'm using the picofly tiny, which already has the resistors.

the cause of the problem is that the resistance isn't enough and the electrical noise from the rp2040 is interfering with cpu-emmc communication. this exact problem has been asked and solved almost a hundred times by now in the huge picofly thread. you need 100 ohm resistance on dat0+cmd, rp2040-tiny comes with 47/47/47 by default which was the initial picofly recommendation, however as more install data came in it turned out to not be enough for all switches so a lot of people started doing 100/100/47 instead which works for all switches. you need to either add additional 47ohm each on dat0+cmd or replace the on-board resistors with 100 ohm variants

 

[Ondrashek06]

I just updated the picofly firmware again, I put ATMO 1.6.2 and the latest hekate, I changed 5 different original cards and tested in htestw (sandisk, lexar). I removed the chip to check the current system version, which is 16.0.3. Would the firmware incompatibility you are referring to be the firmware of the chip? I'm trying to start with sysmmc and ofw with the chip and I get the same error, does anyone have any packages available for version 16.0.3 that I could test on?

No, HorizonOS specificially refers to the firmware of the Switch itself.

 

[Paulo_Suzuki]

the cause of the problem is that the resistance isn't enough and the electrical noise from the rp2040 is interfering with cpu-emmc communication. this exact problem has been asked and solved almost a hundred times by now in the huge picofly thread. you need 100 ohm resistance on dat0+cmd, rp2040-tiny comes with 47/47/47 by default which was the initial picofly recommendation, however as more install data came in it turned out to not be enough for all switches so a lot of people started doing 100/100/47 instead which works for all switches. you need to either add additional 47ohm each on dat0+cmd or replace the on-board resistors with 100 ohm variants

Thank you everyone for all the information! I managed to solve the problem with deeps' solution, the problem really was the lack of this 47ohm resistor, after putting an additional 47ohm in dat0 and cmd, I got a successful boot in sysmmc, thank you very much for this!

I was confused at first because I did the same procedure on a switch lite, this one worked perfectly from the beginning, but with the v1 model I had all these problems, but I'm grateful because everything was resolved.

I just have one question for you, I tested the emmc on the hekate, and it indicated slow emmc on the switch lite, but the games worked, could this cause problems in the future?

 

[deeps]

Thank you everyone for all the information! I managed to solve the problem with deeps' solution, the problem really was the lack of this 47ohm resistor, after putting an additional 47ohm in dat0 and cmd, I got a successful boot in sysmmc, thank you very much for this!

I was confused at first because I did the same procedure on a switch lite, this one worked perfectly from the beginning, but with the v1 model I had all these problems, but I'm grateful because everything was resolved.

I just have one question for you, I tested the emmc on the hekate, and it indicated slow emmc on the switch lite, but the games worked, could this cause problems in the future?

yes, this indicates that you have interference errors on the lite as well. it might not be severe enough to prevent boot but issues can manifest themselves in different ways, for example random crashing or corruption over time. For a proper install according to spec you should fix the resistors on the lite as well

 

[Paulo_Suzuki]

Even putting 100ohm in dat0 and cmd, sometimes I got the same error, the rp2040 tiny is really complicated to deal with, but then I discovered that a thin wire in dat0 and cmd also causes this problem, I believe it affects the resistance, I also had to remove the resistors of the board and only put 1 120ohm resistor, as it was the only one I had available, after that I didn't get any more errors on the lite and v1 models, both work perfectly.