Hardware nintendo DSi CPUs

  • Thread starter Thread starter k66
  • Start date Start date
  • Views Views 4,114
  • Replies Replies 28
  • Likes Likes 8
I converted slot1launch* into a tad file and installed it with TwlNmenu, and it works fine.
(Already signed, no need to install Unlaunch first.)
*slot1launch is a component of TWiLightMenu++ (v27.22.2)

Installation location: NAND:/title/00030004/54574c31
(Uninstall: TwlNmenu → NAND → select TWL1 (3031 54574c31) → press X button )
View attachment 560230View attachment 560235
Now DSi panda can start the Hybrid(DS & DSi) and Limited(DSi only) cart through this icon.:lol:
View attachment 560236View attachment 560237View attachment 560238
It's better to use https://github.com/Lorenzooone/Simple-DS-Slot-1-Launcher rather than what comes bundled with twilight
 
  • Like
  • Love
Reactions: rvtr and k66
It's better to use https://github.com/Lorenzooone/Simple-DS-Slot-1-Launcher rather than what comes bundled with twilight
Thank you for telling me.
I downloaded it, and its release already includes a tad file.
I installed it using TwlNmenu, and the cartridge works fine.
If the cartridge is not inserted at startup, it will display a settings, there are many functions that can be set.
20260305_023548.jpg20260305_023616.jpg20260305_023712.jpg20260305_023813.jpg
 
Last edited by k66,
Based on my previous attempt (DSi panda clone), and the generation principle of the temporary pseudo serial number(only based on MAC address).
I think the HWINFO file can be replaced to allow TwlSystemUpdater to read the serial number (just like factory-set serial number).
.
I tried it and it worked.:O
TwlSystemUpdater installed successfully, it uses the serial number from HWINFO.
The factory-set serial number is indeed carried out during the PREPARE or PREWRITE stage, by creating an HWINFO file that contains the serial number.
20260306.png20260306a.png
.
Setps
1.
TWL EVA PRE_IMPORT
2.ntrboot backup NAND
3.edit NAND, replace HWINFO_N.dat&HWINFO_S.dat&cert.sys, add HWID.sgn&dev.kp (from 'real' DSi panda clone )
(If file from Original DSi panda, TwlSystemUpdater cannot read the serial number. A temporary pseudo serial number will be generated based on the MAC address.)
20260306_023342.jpg20260306_023557.jpg

4.ntrboot restore NAND
5.ntrboot(twlnandtool) install SDMC_Launcher
6.SDMC_Launcher load TwlSystemUpdater and install
Now serial number is VW10000XX00 (my DSi panda EUR)
20260306_025450.jpg20260306_025654.jpg
 
Last edited by k66,
The factory-set serial number is indeed carried out during the PREWRITE or PREWRITE stage, by creating an HWINFO file that contains the serial number.
The best thing about these is that they’ll likely have the retail HWInfo keys! But no dumps exist…
Post automatically merged:

ntrboot restore NAND
It’ll be even faster to replace/edit in my fork of gm9i. Have to compile it yourself, but you can edit files in NAND directly.
(does not boot from the dspico)

https://github.com/rvtr/GodMode9i
 
Last edited by rvtr,
  • Love
Reactions: k66
I converted TWiLightMenu++ title into a tad file.
(from TWiLightMenu-DSi: title/00030004/53524c41/content/00000000.app)
(Because DSipanda cannot install Unlaunch when using the prototype DSimenu, if start TWiLightMenu++ from GodMode9i, launching a game in TWiLightMenu++ will result in a white screen. Exploits can also work, but it is not very convenient to use.)
Installed TWiLightMenu++ title using TwlNmenu, start TWiLightMenu++ from here works fine. (Some homebrew still encounter errors.)
Installation location: NAND:/title/00030004/53524c41
(Uninstall: TwlNmenu → NAND → select SRLA (3031 53524c41) → press X button)
20260413_183157.jpg20260414_145512.jpg
.
.
Boot Unlaunch from the SDcard.
(Booting Unlaunch from the SDcard has very limited functionality, most app and dsiware cannot start. But it can be used to launch some software(e.g. TWL EVA) that GodMode9i cannot, when using the prototype DSimenu.)
Setps
1.
Using TWLMagician to create hiyaCFW(1.6.2).
(Both the dev and retail versions of the system can be used. If it is the retail system hiyaCFW, it needs to replace the dev system hiyaCFW's bootloader.nds)
2. Installed hiyaCFW tad file using TwlNmenu.
(Uninstall: TwlNmenu → NAND → select HIYA (3031 48495941) → press X button)
3. Add Unlaunch TMD, SD:/title/00030017/484e4141/content/title.tmd(set title.tmd to read-only).
(Or add Unlaunch in the title.tmd of the hiyaCFW's Launcher, then set title.tmd to read-only.)
4. LocateSD:/title/00030017/484e41**/content/ , set hiyaCFW's Launcher app to read-only.
When hiyaCFW starts, it boots Unlaunch from the SD card.
20260414_151120.jpg20260414_151137.jpg
What's quite magical is that it can launch the retail version of Launcher.
Unfortunately, most sys apps cannot be used(white screen), SLOT-1 cannot be used(unable to recognize the cartridge).
The Launcher L/R camera of the retail system hiyaCFW can be used.
20260414_182429.jpg20260414_212139.jpg20260414_212658.jpg
PICTOCHAT and DLplay work fine.
20260414_191119.jpg20260429_214703.jpg20260429_215447.jpg20260429_215455.jpg
TWL EVA displays UID(console id) as all 00.
20260413_225830b.jpg
Use AES TEST to check the UID, the first 4 digits become strange.
08A2277024096132 → C0AE6C0224096132
(Using this strange UID to create NAND/hiyaCFW or encrypt tik does not solve the problem.)
uid0.png
.
.
.
 

Attachments

Last edited by k66,
  • Like
Reactions: Tarmfot and rvtr
New IR photo :lol:.
Inspired by @PoroCYon ('CPU TWL' near-IR photo), I also want to take infrared photo of 'LR359A12'. Of course, I am just a noob, so... Two weeks ago, I sent 'LR359A12' to @BIGic_Lab (this is a bilibili link).
I received the IR photo today:wub:.
(Due to limited conditions, this does not seem to be taken with a professional SWIR camera, with a magnification of only 5x, so it is not very clear. I'm quite satisfied, just for fun.)
Because the architecture of 'LR359A12' is the same as 'CPU TWL'(LR359A10), there should be no difference.
The scratches in the photo come from the bottom of the chip and are very obvious under IR, this is normal.
(Click the image to view)
LR359A12 IR.png
01b.png
3x3
1a.png 1b.png 1c.png
2a.png 2b.png 2c.png
3a.png 3b.png 3c.png
.
.
Other photos:
Disassemble the substrate, I first use a soldering iron to remove the solder balls, then file to grind the PCB substrate, and then use the small flame of a gas stove to heat it. The substrate is not heat-resistant and fell off quickly. (If you want to do this at home, you must wear safety goggles and an N99/FFP3 mask, pay attention to fire safety and ventilation.)
20260409_163403.jpg 20260409_164618_(1).jpg
Later, @BIGic_Lab corroded it. (very dangerous, do not try this at home)
001.jpg 002.jpg
2026-04-28_23-11-56_584.jpg 2026-04-28_23-22-59_317.jpg 2026-04-28_23-13-40_234.jpg 2026-04-28_23-20-39_440.jpg
 
Last edited by k66,
Found an 'LR359A22' CPU, from a Nintendo DSi Panda (factory ver).
- CPU: LR359A22 , "1032 5m", produced in 2010/07, console ID:0820225925107136
It is installed on the 'C/TWL-CPU-10' motherboard, NAND product.log date 2012/01/08.
I think it is the development version of 'CPU TWL A'.
20260504_150257.jpg0001.png
0001.PNG
.
Current conclusion:
'LR359A12' (≈CPU TWL, made by Sharp) is used for older version development kits. For DSipanda, board C/TWL-CPU-01 is used.
'LR359A22' (≈CPU TWL A, made by Fujitsu) is used for newer version development kits. For DSipanda, board C/TWL-CPU-10 is used.
:creep:I previously installed 'LR359A12' on the C/TWL-CPU-10 motherboard, and it actually worked properly.:yaynds:
 
Last edited by k66,
Cool, looks like they have much better illumination of the die (and thus, better contrast) than me. I might have some time in a few weeks to play with the IC scan setup again, to see if I can get better illumination.
 
  • Like
Reactions: rvtr and k66

Site & Scene News

Popular threads in this forum