Internal modchip - SAMD21 (Trinket M0, Gemma M0, ItsyBitsy M0 Express) Guide, Files & Support

Chocola · Jun 19, 2019

Hi @mattytrog, on first place thanks for all documentation, usually I should check on various places to do things like this but your guide seems ultracomplete and I apreciate a lot the "Anti disaster replacement list".

Well, now that emunand are working, I'm planing to install a modchip to avoid the use of the jig and injector on each boot, I have experience on micro electronic so I think I can install them without problems, on my case I wan't the full instalation (Power button for OFW and Power + Vol+ for boot hekate), but I have three questions:

What chip you recomend to install? For now I doubt on Trinket M0 or Rebug modchip, as I can see the space are minimal and I don't want to make any modification on the retail hardware (like cut aluminium, block the air flow of the rear aluminium plate, etc etc...) only solder a little wires for the chip without touch the Switch hardware.

If I want to update the payload, I can do through Switch port? I see that your schemes point wires to D+ and D- of USB C, but reading the topic (fast, can't read the 138 pages on detail) I see how you say that avoid enter on RCM when it's connected to charger, dock or USB, if not I can use inmutable payload that chainload another from SD card to avoid open the Switch on each update, but if I can flash Hekate directly and update it through Switch port its awesome.

Can damage or produce any issue on Switch? I didn't check the software for now, but as I can see the instalation are clean and don't should produce any issue on the Switch hardware, but I ask this to be sure, if I have something to know before install it (charging/dock issues, usb connection issues, etc etc...) please advice me.

A lot of thanks! ^^

mattytrog · Jun 19, 2019

Chocola said:
Hi @mattytrog, on first place thanks for all documentation, usually I should check on various places to do things like this but your guide seems ultracomplete and I apreciate a lot the "Anti disaster replacement list".

Well, now that emunand are working, I'm planing to install a modchip to avoid the use of the jig and injector on each boot, I have experience on micro electronic so I think I can install them without problems, on my case I wan't the full instalation (Power button for OFW and Power + Vol+ for boot hekate), but I have three questions:

OK... Let's do one at a time...

Chocola said:
What chip you recomend to install? For now I doubt on Trinket M0 or Rebug modchip, as I can see the space are minimal and I don't want to make any modification on the retail hardware (like cut aluminium, block the air flow of the rear aluminium plate, etc etc...) only solder a little wires for the chip without touch the Switch hardware.

This is a false economy in my opinion.
1) you need to remove the heatsink and replace the thermal paste if doing the job correctly... As a result, some high quality aftermarket compound will equal or surpass the OEM stuff.

2) by modifying the shield, air flow is not reduced at all. Coupled with the fact you are replacing the heatsink compound, the end result is that the soc will probably run EVEN COOLER then stock.

3) furthermore... I'm assuming you don't want to modify the shield for warranty purposes etc etc...
I'll say this now...
Forget the warranty.

If you claim under warranty (even for joycons) the whole unit will be required and will come back as an ipatched unit. So forget the warranty. If you are forgetting the warranty, then I recommend modifying the shield.

In addition to the points above, if the shield is modified, you can remove later if required for servicing without desoldering the chip

The rigidity of the console is the same.
The cooling capacity of the shield is the same.

Also, when you are fitting without modifying the shield, airflow is (slightly) restricted. In practice, this matters little and is only a miniscule amount.
You also have to be careful manipulating the leads. There is a bigger potential to pull a freshly soldered lead off a component, possibly damaging a component or trace.

Chocola said:
If I want to update the payload, I can do through Switch port? I see that your schemes point wires to D+ and D- of USB C, but reading the topic (fast, can't read the 138 pages on detail) I see how you say that avoid enter on RCM when it's connected to charger, dock or USB, if not I can use inmutable payload that chainload another from SD card to avoid open the Switch on each update, but if I can flash Hekate directly and update it through Switch port its awesome.

Yes. Not a problem.

Chocola said:
Can damage or produce any issue on Switch? I didn't check the software for now, but as I can see the instalation are clean and don't should produce any issue on the Switch hardware, but I ask this to be sure, if I have something to know before install it (charging/dock issues, usb connection issues, etc etc...) please advice me.

A lot of thanks! ^^

Absolutely you can damage it.

The most common are the VOL+ function being damaged (it's a resistor that gets damaged)

The second most common is pin 5(or 6) smoothing capacitors bridged or damaged. This can lead to charging problems (flashing green led on dock) and system instability.

There is also the possibility of damaging the ram. If this happens, you are in deep trouble. You will have a blank screen when trying to boot anything, even Linux. And you will only have the IRAM availsble (memloader will give you a MTC_LOAD error, with 246400 bytes out instead of 43xxxxxxxxx)

Use the 3v pad. Do not use the regulator on the trinket.

Cheers

Chocola · Jun 19, 2019

mattytrog said:
This is a false economy in my opinion.
1) you need to remove the heatsink and replace the thermal paste if doing the job correctly... As a result, some high quality aftermarket compound will equal or surpass the OEM stuff.

2) by modifying the shield, air flow is not reduced at all. Coupled with the fact you are replacing the heatsink compound, the end result is that the soc will probably run EVEN COOLER then stock.

3) furthermore... I'm assuming you don't want to modify the shield for warranty purposes etc etc...
I'll say this now...
Forget the warranty.

If you claim under warranty (even for joycons) the whole unit will be required and will come back as an ipatched unit. So forget the warranty. If you are forgetting the warranty, then I recommend modifying the shield.

In addition to the points above, if the shield is modified, you can remove later if required for servicing.

The rigidity of the console is the same.
The cooling capacity of the shield is the same.

Also, when you are during without modifying the shield, airflow is (slightly) restricted. In practice, this matters little and is only a miniscule amount.
You also have to be careful manipulating the leads. There is a bigger potential to pull a freshly donated lead off a component, passively damaging a component or trace.

Isn't for warranty purposes, just it's a gift with a lot of value for me then I want to have a method for comeback to it's retail state, so I think that I can buy a replacement rear plate and cut it to acomodate the chip.

Respect the thermal compound, I always use the Artic MX-4 on the computers, atleast for computers are good and have good performance, it's valid for Switch or I need a special one?

mattytrog said:
Yes. Not a problem.

Here I have another doubt, break the USB functionality of the device or can I use the same port for both? How I can swap between trinket flash mode and switch usb mode?

mattytrog said:
Absolutely you can damage it.

The most common are the VOL+ function being damaged (it's a resistor that gets damaged)

The second most common is pin 5(or 6) smoothing capacitors bridged or damaged. This can lead to charging problems (flashing green led on dock) and system instability.

There is also the possibility of damaging the ram. If this happens, you are in deep trouble. You will have a blank screen when trying to boot anything, even Linux. And you will only have the IRAM availsble (memloader will give you a MTC_LOAD error, with 246400 bytes out instead of 43xxxxxxxxx)

Use the 3v pad. Do not use the regulator on the trinket.

There im explain wrong (my English are so bad), I don't refer to damages that I can cause on install, I mean if the chip produce any issue, damage or break any function of the console.

A lot of thanks for the help ^^

cmcollander · Jun 20, 2019

Chocola said:
There im explain wrong (my English are so bad), I don't refer to damages that I can cause on install, I mean if the chip produce any issue, damage or break any function of the console.

The chip itself won't cause any damage to your switch if installed properly. Any damage to the switch will be due to installation problems as described above.

Chocola · Jun 20, 2019

cmcollander said:
The chip itself won't cause any damage to your switch if installed properly. Any damage to the switch will be due to installation problems as described above.

Nice, I gona place a order then xP

ZerOneX · Jun 20, 2019

Guys, sorry for the noob question, but I did not get properly where to solder the 'pink' pins checking the schematic.

Just to be double sure, should I just ground them? That is it?

Thank you all in advance.

Regards,

ZerO.

mattytrog · Jun 20, 2019

ZerOneX said:
Guys, sorry for the noob question, but I did not get properly where to solder the 'pink' pins checking the schematic.

Just to be double sure, should I just ground them? That is it?

Thank you all in advance.

Regards,

ZerO.

The pink pins are extra functions. Leave disconnected.

ZerOneX · Jun 21, 2019

@mattytrog I think I got everything now to start it.... my trinket is ready and flashed accordingly...

My only doubt is regading this part 'With BOTH UF2, permanent CFW booting is enabled, this saves your fuses. HOWEVER, if you are in UF2 update mode, or you press the reset switch on the back during a power-on / reboot, FUSES WILL BURN!!!'

How we avoid such scenario if we need (for some reason) to update an UF2 file? To preserve the fuses for me is a must have.

Thank you on more time and have a great day.

Regards,

ZerO.

Scettles · Jun 21, 2019

I bought a switchme last year.... I have done very poor soldering in my life. I'm curious where I could potentially take my switch to get it done or send it somewhere trustworthy.... Or come tips to get me practicing on some stuff for a while before attempting lol. I'm using an emunand dual boot where have to plug into my phone every time and etc... And dang kids keeps leaving switch on in autorcm mode and it dies and etc lol. So wanting to get a full vol strap install and everything done to have the truest form of dual boot.... Normal boot when power up... Hold vol... Emunand!

Thanks in advance!

mattytrog · Jun 21, 2019

ZerOneX said:
@mattytrog I think I got everything now to start it.... my trinket is ready and flashed accordingly...

My only doubt is regading this part 'With BOTH UF2, permanent CFW booting is enabled, this saves your fuses. HOWEVER, if you are in UF2 update mode, or you press the reset switch on the back during a power-on / reboot, FUSES WILL BURN!!!'

How we avoid such scenario if we need (for some reason) to update an UF2 file? To preserve the fuses for me is a must have.

Thank you on more time and have a great day.

Regards,

ZerO.

The fuses are only checked at power on. The only way you could get into this scenario is if you double press reset while booted into update mode, then flash a BAD bootloader which would prevent the straps being pulled low, and powering on.

But...
1... You need to power off completely to restart the console, resulting in chip reset, resulting in straps dropped. Correct behaviour. So no chance of forgetting it is in bootloader mode as the trinket is power cycled, pulling straps low again.

It isn't a concern. As long as your soldering is good and you have done a QUALITY install, your fuses are safe forever.

Only by bricking the trinket will the fuses be compromised. And that can only happen if you change the Switchboot bootloader (part1)uf2 and it bricks or you flash incorrect file for your pinouts.

If you flash a faulty part 2 uf2, the bootloader will be unaffected and fuses are safe

Scettles said:
I bought a switchme last year.... I have done very poor soldering in my life. I'm curious where I could potentially take my switch to get it done or send it somewhere trustworthy.... Or come tips to get me practicing on some stuff for a while before attempting lol. I'm using an emunand dual boot where have to plug into my phone every time and etc... And dang kids keeps leaving switch on in autorcm mode and it dies and etc lol. So wanting to get a full vol strap install and everything done to have the truest form of dual boot.... Normal boot when power up... Hold vol... Emunand! Thanks in advance!

Can fix it.

Drop me a pm.

Certainly is truest form of dual boot. No messy exploits!

recgame77 · Jun 21, 2019

Hi i m planning to install it internal ; but lookig at the source code here : https://github.com/mattytrog/SAMD-F...et M0_LEGACY_METHOD_3_Hekate4.2/main/main.ino

I dont get when does the chip turn off ?

Can we use the switch usb with tinfoil or uboot sd mount with an internal chip ?

ZerOneX · Jun 21, 2019

@mattytrog Thank you man. You always answer the questions. Very nice nice of you. Have a great day.

mattytrog · Jun 21, 2019

recgame77 said:
Hi i m planning to install it internal ; but lookig at the source code here : https://github.com/mattytrog/SAMD-Fusee-Launcher/blob/master/Trinket M0_LEGACY_METHOD_3_Hekate4.2/main/main.ino

I dont get when does the chip turn off ?

Can we use the switch usb with tinfoil or uboot sd mount with an internal chip ?

While the console is operating and booted, it is in a deep sleep. When it is off, the chip is dead.

The __wfi instruction places unit into a coma.

recgame77 · Jun 21, 2019

mattytrog said:
While the console is operating and booted, it is in a deep sleep. When it is off, the chip is dead.

The __wfi instruction places unit into a coma.

Ha ok it was in the headers; big thanks.

Any idea when the PIN 2 on the trinket trigger for the interupt exactly ?

mattytrog · Jun 21, 2019

recgame77 said:
Ha ok it was in the headers; big thanks.

Any idea when the PIN 2 on the trinket trigger for the interupt exactly ?

The interrupt is "global". It can be triggered at any time it is required, even while doing a task

mrdude · Jun 22, 2019

@mattytrog.

I don't know if you're using argon-nx mod I posted, I've modded gui_argon_menu.c and changed some code, when you press the about icon, if you press vol- at the same time it will generated the ini file needed if you're using sd card hidden emunand, this is the code I changed if you want to use it:

Code:

int tool_about() {
  bool emunand = btn_read() & BTN_VOL_DOWN;
  if (emunand)
      if (f_stat("emummc/emummc.ini", NULL)) {
          f_mkdir("emummc");
          sd_save_to_file("[emummc]\nemummc_enabled = 1\nemummc_sector = 0x2\nemummc_nintendo_path = Emutendo", 79, "emummc/emummc.ini");
          string = "emummc/emummc.ini created";
          text_centre();
          gfx_printf(&g_gfx_con, "%k%s%k", GREEN, string, MYBLUE);
      }
   
      else
      {
          string = "emummc/emummc.ini already exists";
          text_centre();
          gfx_printf(&g_gfx_con, "%k%s%k", colour_red, string, MYBLUE);   
      }
 
  else
      {
      string = "Property of MrDude";
      text_centre();
      gfx_printf(&g_gfx_con, "%k%s%k", MYBLUE, string, MYBLUE);
      }
   return 0;
}

You might need to change some idents - as the forum seems to mess them up.

mattytrog · Jun 22, 2019

mrdude said:
@mattytrog.

I don't know if you're using argon-nx mod I posted, I've modded gui_argon_menu.c and changed some code, when you press the about icon, if you press vol- at the same time it will generated the ini file needed if you're using sd card hidden emunand, this is the code I changed if you want to use it:

Code:

int tool_about() { bool emunand = btn_read() & BTN_VOL_DOWN; if (emunand) if (f_stat("emummc/emummc.ini", NULL)) { f_mkdir("emummc"); sd_save_to_file("[emummc]\nemummc_enabled = 1\nemummc_sector = 0x2\nemummc_nintendo_path = Emutendo", 79, "emummc/emummc.ini"); string = "emummc/emummc.ini created"; text_centre(); gfx_printf(&g_gfx_con, "%k%s%k", GREEN, string, MYBLUE); } else { string = "emummc/emummc.ini already exists"; text_centre(); gfx_printf(&g_gfx_con, "%k%s%k", colour_red, string, MYBLUE); } else { string = "Property of MrDude"; text_centre(); gfx_printf(&g_gfx_con, "%k%s%k", MYBLUE, string, MYBLUE); } return 0; }

You might need to change some idents - as the forum seems to mess them up.

Good work Sir!

I've been meaning to get back to doing a bit on argon but things always crop up. Bugs in other projects... Young son wanting to play etc...

I do have big plans for various stuff, but I'm trying to keep aligned with other peoples work (just create drop in replacements).

Will have a play tomorrow definitely.

mrdude · Jun 22, 2019

Cheers Mattytrog.

I've still got a function to write to show the status if emunand is enabled/disabled - and a switch to toggle it on and off. If I get time, I'll do that later today. I've got a lot on myself just now. - I'll post the code when I'm done.

Also I know you're busy and haven't been too well. Family comes first, so it's best to spend the time with the children and wife, and only mess about with code and stuff when you have time to burn - this is just a hobby after all and not really important compared to the other things in life that really matter.

recgame77 · Jun 22, 2019

mattytrog said:
The interrupt is "global". It can be triggered at any time it is required, even while doing a task

Hi

I mean what is the benefit of connecting the pin 2 to the usb dizconect strap point ?

Thanks for all answer

mrdude · Jun 22, 2019

@mattytrog, here's my modded code for argon-nx mod:

Hold V+ and tap the gear icon to generate ini file
Hold V- and tap gear icon to delete ini file
Power and tap gear icon - shows about info
Tap gear icon (without pressing any buttons) to show status - if ini files exists, shows emunand is enabled.

Code:

int tool_about() {
  bool emunand = btn_read() & BTN_VOL_UP;
  bool emunand2 = btn_read() & BTN_VOL_DOWN;
  bool Power = btn_read() & BTN_POWER;
 
  if (emunand)
      if (f_stat("emummc/emummc.ini", NULL)) {
          f_mkdir("emummc");
          sd_save_to_file("[emummc]\nemummc_enabled = 1\nemummc_sector = 0x2\nemummc_nintendo_path = Emutendo", 79, "emummc/emummc.ini");
          string = "emummc/emummc.ini created";
          text_centre();
          gfx_printf(&g_gfx_con, "%k%s%k", GREEN, string, MYBLUE);
      }
     
      else
      {
          string = "emummc/emummc.ini already exists";
          text_centre();
          gfx_printf(&g_gfx_con, "%k%s%k", colour_red, string, MYBLUE);     
      }
  else if (emunand2)
      {
          if (f_stat("emummc/emummc.ini", NULL)) {
              string = "emummc/emummc.ini doesn't exist";
              text_centre();
              gfx_printf(&g_gfx_con, "%k%s%k", colour_red, string, MYBLUE); 
          }
          else {
              f_unlink("emummc/emummc.ini");
              string = "emummc/emummc.ini deleted";
              text_centre();
              gfx_printf(&g_gfx_con, "%k%s%k", colour_red, string, MYBLUE);           
          }
      }
  else if (Power)
      {
          string = "Argon-NX Mod by MrDude";
          text_centre();
          gfx_printf(&g_gfx_con, "%k%s%k", MYBLUE, string, MYBLUE);   
      }
 
  else
      {
          if (f_stat("emummc/emummc.ini", NULL)) {
              string = "Emunand: Disabled";
              text_centre();
              gfx_printf(&g_gfx_con, "%kEmunand: %kDisabled%k", MYBLUE, colour_red, MYBLUE);
              }
          else {
              string = "Emunand: Enabled";
              text_centre();
              gfx_printf(&g_gfx_con, "%kEmunand: %kEnabled%k", MYBLUE, GREEN, MYBLUE);
          }
      }       
   
    return 0;
}

That might save you some time messing about - as I know you're busy.

Attachments

GBAtemp Meowgular

You don`t want to listen to anything I say.

GBAtemp Meowgular

Member

GBAtemp Meowgular

Active Member

You don`t want to listen to anything I say.

Active Member

Active Member

You don`t want to listen to anything I say.

Well-Known Member

Active Member

You don`t want to listen to anything I say.

Well-Known Member

You don`t want to listen to anything I say.

Developer

You don`t want to listen to anything I say.

Developer

Well-Known Member

Developer

Similar threads

Popular threads in this forum