Hacking WIP [Trinket] [Rebug] [Others] SWITCHBOOT_UF2 / FUSEE_UF2 modchip software

[mattytrog]

if i disable AutoRCM then i boot normal to horizon os with fuse count fitting to fw version 4 fuses for 3.01 FW

That should not happen.

If you have all straps connected (which if its one I did, you WILL have)
and SWITCHBOOT remains the version I put on... The joycon AND volume button,
then there is a hardware problem with your chip.

Try this...

With the console off and autoRCM disabled, hold down vol+ and press power. Does it then boot up into Hekate?

 

[josete2k]

Just tested here.

Upgraded bench unit to 7.0.1, 9 fuses burnt...

rawnand restore back to 6.2.0... Boots without a problem.

Is SXOS using emunand? if so, that is how it can boot.

Thanks for testing.

All operations are on sysnand.

The downgrade was from 7.0.1 to 6.1.0 with choidujournx.

SXOS can boot the unit but the modchip payload (hekate) can't.

Strange...

 

[FunThomas]

With the console off and autoRCM disabled, hold down vol+ and press power. Does it then boot up into Hekate?

yes it boots to hekate, you did the mod short over a week ago and i did not flash any updates to the mod chip

if i disable AutoRCM then i boot normal to horizon os with fuse count fitting to fw version 4 fuses for 3.01 FW

my old message meant that i did the reboot to normal with fusecount 4 on 3.01and the reboot to normal did not burn any fuses since the fusecount was as promised for the fw version, so i dont know if the fuse burn/check was skipped or not

 

[mattytrog]

yes it boots to hekate, you did the mod short over a week ago and i did not flash any updates to the mod chip


my old message meant that i did the reboot to normal with fusecount 4 on 3.01and the reboot to normal did not burn any fuses since the fusecount was as promised for the fw version, so i dont know if the fuse burn/check was skipped or not

I'm trying to diagnose if you might have lost a strap or not.

I'm bloody good at soldering. But I'm not perfect.

From being switched off, your console should boot to hekate via the chip every time. And I mean every time.

If you have lost a fuse, it is because either...

1) Reset was pressed at an incorrect time during boot, leading to a fuse to burn

Or

2) a strap has become faulty.

That's what I'm trying to get to the bottom of

 

[FunThomas]

i never pressed reset short before or after the FW update to 3.01

i pressed reset short some days ago to test the hole i made to be able to press reset without opening and to see the led on the backplate from the trinket

i dont know if a strap has become faulty, but i recognised since the day the switch arrived i had some (maybe 4 times in the last week, or maybe 20% of the tries) not working starts and it was hanging in black screen, dont know if it was in rcm mode

 

[mattytrog]

i never pressed reset short before or after the FW update to 3.01

i pressed reset short some days ago to test the hole i made to be able to press reset without opening and to see the led on the backplate from the trinket

i dont know if a strap has become faulty, but i recognised since the day the switch arrived i had some (maybe 4 times in the last week, or maybe 20% of the tries) not working starts and it was hanging in black screen, dont know if it was in rcm mode

OK. Well, we need to check if a strap has become faulty.
Best way to do that, is to get to the main Switch home screen with joycons connected, then press RESET on the chip. The volume slider should appear and the joycon logo showing a disconnect should appear.

It is important we get to the bottom of this.

 

[FunThomas]

the volume slider shows and the right joycon disconnect logo shows

 

[mattytrog]

the volume slider shows and the right joycon disconnect logo shows

Ok so your chip has not let you down and is working.

The reset button must have been pressed during boot. That is the only way a fuse could have burnt.

SWITCHBOOT power is on the same 3v trace as the emmc and m92t36. The straps are dropped before the emmc has even thought about initialising itself. When the chip powers off, so does the emmc, therefore it cannot complete the fuse burn in normal circumstances.

The only exceptions to this are if a strap has become disconnected or the reset button is pressed when powered on, thus not dropping the straps and permitting a "burning boot".

The moment MAX77620 activates that 3v trace, those straps are dropped.

So if you didn't press reset during boot, you have a dodgy strap. If you have, I'll put it right at no cost. Like I say I am not perfect.

But you are getting the vol and disconnected symbols. Which says the straps are working.

 

[FunThomas]

Ok so your chip has not let you down and is working.

The reset button must have been pressed during boot. That is the only way a fuse could have burnt.

SWITCHBOOT power is on the same 3v trace as the emmc and m92t36. The straps are dropped before the emmc has even thought about initialising itself. When the chip powers off, so does the emmc, therefore it cannot complete the fuse burn in normal circumstances.

The only exceptions to this are if a strap has become disconnected or the reset button is pressed when powered on, thus not dropping the straps and permitting a "burning boot".

The moment MAX77620 activates that 3v trace, those straps are dropped.

So if you didn't press reset during boot, you have a dodgy strap. If you have, I'll put it right at no cost. Like I say I am not perfect.

But you are getting the vol and disconnected symbols. Which says the straps are working.

So i will use AutoRCM in combination for the safety of fuses ;-) thanx for the offer for repairing but the shipping costs are to high only for repair one switch,
Maybe i will ask a friend if he will mod his switch too and we can share shipping cost then i will let you check again.

 

[mattytrog]

So i will use AutoRCM in combination for the safety of fuses ;-) thanx for the offer for repairing but the shipping costs are to high only for repair one switch,
Maybe i will ask a friend if he will mod his switch too and we can share shipping cost then i will let you check again.

There isn't anything to "repair" it seems. The straps are working.

However if you get any problems, the offer is there

 

[Dougiejones]

@mattytrog Hi. Since Simple_UF2 holds in your Hekate 4.8 Mod and thus from starting boot do we need all the folder (bootloader) and files like the classic ?

If think the answer is no because you boot Hekate without the SD in place...isn't it ?

 

[FunThomas]

@mattytrog Hi. Since Simple_UF2 hold in your Hekate 4.8 Mod and thus from starting boot do we need all the folder (bootloader) and files like the classic ?

If think the answer is no because you boot Hekate without the SD in place...

Its only the first payload for starting hekate thats on the modchip to do something more you maybe need the hekate ini for some bootconfigs and the bootloader screen but also the payloads *.kip are needed to boot into something?
and for 7.x the sept ...

 

[Dougiejones]

Its only the first payload for starting hekate thats on the modchip to do something more you maybe need the hekate ini for some bootconfigs and the bootloader screen but also the payloads *.kip are needed to boot into something?
and for 7.x the sept ...

Yep i agree that Hekate's ini is essential though it would be created upon first Hekate start.
And as to the payloads if correctly named and placed for instance at the root of the SD then the " Modchip " + Simple_UF2 will catch'em won't them ?

--------------------- MERGED ---------------------------

 

[mattytrog]

Yep i agree that Hekate's ini is essential though it would be created upon first Hekate start.
And as to the payloads if correctly named and placed for instance at the root of the SD then the " Modchip " + Simple_UF2 will catch'em won't them ?

--------------------- MERGED ---------------------------

Simple uf2 is hekate with my bolt on bits. All files, folders and inis that you use for hekate work with this

 

[smasha]

Hi Matty,

Can you please upload FlashStorage.h to git or link it here? Can't compile/push sketch manually via arduino without it.

https://github.com/cmaglie/FlashStorage/blob/master/src/FlashStorage.h

Is this the one you used? Cheers

 

[pcwizard7]

what are the advantage of using a mod chip? so I know this allows you to have internal payload launcher and allows you to update without burning fuses. but is there anything more?

 

[FunThomas]

what are the advantage of using a mod chip? so I know this allows you to have internal payload launcher and allows you to update without burning fuses. but is there anything more?

you will not have to carry a dongle and a jig with the switch and boot easy to cfw and dont hang in rcm mode and full drain your battery because of AutoRCM and no payload sender

 

[noX1609]

Did the offset for mode selection change in the latest version? Because tried it but didn‘t work.
So i thought i ask if it changed, if not i have done something wrong

I‘m using the Joycon strap only with trinket board if that makes any difference.

 

[mattytrog]

Did the offset for mode selection change in the latest version? Because tried it but didn‘t work.
So i thought i ask if it changed, if not i have done something wrong

I‘m using the Joycon strap only with trinket board if that makes any difference.

No its probably me thats got it wrong. Like I say, I haven`t worked out the details yet.

Heres one for you boys and girls...

Launch this with TegraRCMsmash and see if you can find the new feature...

Yes, the built-in bootlogo is now a black screen due to space purposes...

 

[darrin41]

What uf2 files to use with trinket mo for atmosphere 8.5 thanks