"Failed to run tsec_keygen firmware" on SXOS Pro USB dongle when using fusee payload to launch AMS 1.2.3

[efgamer]

I'm getting the error: "Failed to run tsec_keygen firmware" on SXOS Pro USB dongle when using fusee payload to launch AMS 1.2.3 then after I press the power button to reboot it seems AMS loads normally but I'm not sure if I should be concerned about this error or not.

The system firmware is on 13.1.0.

Has anyone else caught this error?

 

[xFlesk]

you run an ams payload from within sxos recovery boot menu ?

 

[Purple_Heart]

I heard the SXOS chainload Option is broken / not reliable

 

[Purple_Heart]

Had same problem

 

[xFlesk]

I heard the SXOS chainload Option is broken / not reliable

indeed, its impossible to use atmosphere by booting it from tx boot menu.
if you want to use your sx dongle to boot to atmosphere or hekate, you should generate your own custom boot.dat using this script
https://github.com/HunterKing/TX-Custom-Boot

 

[UnderJinx]

Does it work for chipped sxos erista
What is the workaround for chip users

 

[xFlesk]

i dont know, dont have chip
but if sxos chip only looking for boot.dat on the root of sd (like dongle does) then it should work without problems

 

[Tumbleweed]

You can boot it but you need to use package3 instead of fuse... there's an explanation for this issue here https://gbatemp.net/threads/atmosphere-nx-custom-firmware-in-development-by-sciresm.496832/page-329

 

[Badablek]

i dont know, dont have chip
but if sxos chip only looking for boot.dat on the root of sd (like dongle does) then it should work without problems

no, it does not work with sx chip. boot.dat is signed, you can't use anything else than official boot.dat from Xecuter
this only works with SX PRO dongle.

 

[UnderJinx]

i dont know, dont have chip
but if sxos chip only looking for boot.dat on the root of sd (like dongle does) then it should work without problems

I think it does will try this and hopefully it will work if i got the brains for it
okay too bad

 

[Draxzelex]

I'm getting the error: "Failed to run tsec_keygen firmware" on SXOS Pro USB dongle when using fusee payload to launch AMS 1.2.3 then after I press the power button to reboot it seems AMS loads normally but I'm not sure if I should be concerned about this error or not.

The system firmware is on 13.1.0.

Has anyone else caught this error?

Did you update Atmosphere to the latest version?

 

[binkinator]

I had a similar experience. See if this helps….

Post in thread 'Hack SXOS'
https://gbatemp.net/threads/hack-sxos.582831/post-9651425

Long story short there’s a new setup you need in hekate_ipl.ini:

I switched to using package3 and now everything just works!

[Atmosphere CFW] payload=bootloader/payloads/fusee.bin <—-delete this fss0=atmosphere/package3 kip1=atmosphere/kip_patches/* logopath=/graphics/splash/current/atmosphere.bmp icon=/graphics/icons/current/atmosphere.bmp id=atmo

(Your graphics paths will most certainly be different than my custom ones so change to wherever your files are located.)

I works without the payload line too but I have a custom splashscreen that doesn’t work without it (yeah…I know…everyone hates splash screens, but I did a bunch of work to make mine cool so I undid all the hard work done to remove them.)

 

[Turbo_Interceptor]

Hate to revive an old thread but I was a long time user of SX OS until it died and I switched over to Atmosphere.

The first few versions of Atmosphere booted just fine. I would use my SX OS dongle to boot up, click on 'payloads' I think and pick 'fusee' and away it went.

A few versions of Atmosphere ago, I started getting these 'tsec_keygen' errors and would just hit the power button and the Switch would boot into Atmosphere. All my games and home brew apps would work just fine so I didn't think much of it. I still don't but I would like to correct this error.

Searching for an answer, I found this thread here and this one and another.

Absolutely nothing I tried in these threads fixed it. None of the editing I did on the Hekate ini file mattered. My last ditch effort was using my SX Pro dongle to launch Hekate and from there, I launched fusee and same error.

I'm using Atmosphere 1.3.0 and I'm on Switch firmware v14 and my Switch is a launch unit.

Any ideas?

 

[binkinator]

Hate to revive an old thread but I was a long time user of SX OS until it died and I switched over to Atmosphere.

The first few versions of Atmosphere booted just fine. I would use my SX OS dongle to boot up, click on 'payloads' I think and pick 'fusee' and away it went.

A few versions of Atmosphere ago, I started getting these 'tsec_keygen' errors and would just hit the power button and the Switch would boot into Atmosphere. All my games and home brew apps would work just fine so I didn't think much of it. I still don't but I would like to correct this error.

Searching for an answer, I found this thread here and this one and another.

Absolutely nothing I tried in these threads fixed it. None of the editing I did on the Hekate ini file mattered. My last ditch effort was using my SX Pro dongle to launch Hekate and from there, I launched fusee and same error.

I'm using Atmosphere 1.3.0 and I'm on Switch firmware v14 and my Switch is a launch unit.

Any ideas?

please post your hekate_ipl.ini file and let’s take a look.

 

[OrGoN3]

I had a similar experience. See if this helps….

Post in thread 'Hack SXOS'
https://gbatemp.net/threads/hack-sxos.582831/post-9651425

Long story short there’s a new setup you need in hekate_ipl.ini:

I switched to using package3 and now everything just works!

[Atmosphere CFW] payload=bootloader/payloads/fusee.bin fss0=atmosphere/package3 kip1=atmosphere/kip_patches/* logopath=/graphics/splash/current/atmosphere.bmp icon=/graphics/icons/current/atmosphere.bmp id=atmo

(Your graphics paths will most certainly be different than my custom ones so change to wherever your files are located.)

I works without the payload line too but I have a custom splashscreen that doesn’t work without it (yeah…I know…everyone hates splash screens, but I did a bunch of work to make mine cool so I undid all the hard work done to remove them.)

The fss0 and kip1 lines are completely ignored because you have it chainloading a payload, fusee.bin. just fyi.

 

[binkinator]

The fss0 and kip1 lines are completely ignored because you have it chainloading a payload, fusee.bin. just fyi.

Yeah I know…just Saw that. I didn’t want to edit it mid convo.

appreciated. ”updated” it without changing the flaw.

 

[Takokeshi]

Using SX stuff to boot is simply not supported (anymore); you'll have to use something else for payload injection, I'm afraid.

 

[CompSciOrBust]

Hate to revive an old thread but I was a long time user of SX OS until it died and I switched over to Atmosphere.

The first few versions of Atmosphere booted just fine. I would use my SX OS dongle to boot up, click on 'payloads' I think and pick 'fusee' and away it went.

A few versions of Atmosphere ago, I started getting these 'tsec_keygen' errors and would just hit the power button and the Switch would boot into Atmosphere. All my games and home brew apps would work just fine so I didn't think much of it. I still don't but I would like to correct this error.

Searching for an answer, I found this thread here and this one and another.

Absolutely nothing I tried in these threads fixed it. None of the editing I did on the Hekate ini file mattered. My last ditch effort was using my SX Pro dongle to launch Hekate and from there, I launched fusee and same error.

I'm using Atmosphere 1.3.0 and I'm on Switch firmware v14 and my Switch is a launch unit.

Any ideas?

Instead of chain loading through the SX Boot menu grab the SX Gear boot.dat from somewhere and use that instead. It will automatically load payload.bin from the SD card and has better compatibility with non-tx software. Doing that basically turns your SX Pro in to an SX Gear which was made for the sole purpose of booting non-tx CFW.

 

[Takokeshi]

https://github.com/Atmosphere-NX/Atmosphere/issues/1648#issuecomment-926989957

Don't boot via SX gear, it's not supported.

 

[CompSciOrBust]

https://github.com/Atmosphere-NX/Atmosphere/issues/1648#issuecomment-926989957

I don't know why it doesn't seem to work for some people but I know lots of people who still use the SX Gear and it seems to work totally fine for them, both on Erista and Mariko. If that guy tries it and it works why not keep using it even if it is unsupported? If it works it works™