- Joined
- Jan 3, 2014
- Messages
- 1,420
- Solutions
- 1
- Reaction score
- 2,068
- Trophies
- 3
- Age
- 42
- Location
- New Albany, Indiana
- XP
- 4,133
- Country


SS[4.ExperimentalASMCode]
20000000
[ 4.1 RP減らない/Inf RP]
20000000
[ 4.1.1 RP減らないOn/Inf RP On]
C1000F30
040F0000 01DFA4B4 71000129
[ 4.1.2 RP減らないOff/Inf RP Off]
C1000F30
040F0000 01DFA4B4 6B160129

@Eiffel2018 thanks to making tutorial.
I was at a loss coz I didn't know hot to use elf file with gdb
So It is very helpful for me.
@TomSwitch thanks to updating SE tools.
gdb and SE tools make searching and creating code more easiler.
By the way,does Edizon SE support code type 0xC0?
When I use code type 0xC0,EdizonSE shows cheat list,but key condition seems to be corrupted.
cheat sample
SS
View attachment 286037
Thanks for your advice.Normally, I open 2 ida pro simultaneously,
one for elf
one for gdb
all changes are marked in elf, and will be used for further version upgrade
and there should be a cheat code file in NS machine.
Every time I start the game,
and load the cheat files by Edizon SE,
then detact the dmnt and exit Edizon SE
Afterward load GDB and start debugger


Click on the address line 364D4B8E0 and press "c" and the code will be show.I have a question about IDA pro.
When program stops by breakpoint, the disassembly text at PC chaged to DCB instruction in my enviroment.
Yes, the same bug we have got. But it only display wrongly in IDA. Do not affect the code in NS machineThanks for your advice.
If I get confused about changing the base address, I'll try two windows.
I have a question about IDA pro.
When program stops by breakpoint, the disassembly text at PC chaged to DCB instruction in my enviroment.
Is it same in your enviroment?
In this case,disassembly text at 364D4B8E0 is MOV instruction before stopping by breakpoint.
View attachment 286068
and changed to DCB instruction after stopping by breakpoint
View attachment 286069
No,I can't.Click on the address line 364D4B8E0 and press "c" and the code will be show.
Thanks for informationYes, the same bug we have got. But it only display wrongly in IDA. Do not affect the code in NS machine
After several days my experience tell me:
1. Reduce setting breakpoints on the code, use F4 as much as possible.
2. If a breakpoints need to be set, disable it immediately after it in effect
3. For manual define segment, only main and heap and stack is enough. (don't add sdk or nsldr)
since it is a multi thread processor, the register PC will switch between threads,
if there is no SDK segment, only main code will be show on the screen, it is easy to use F7/F8 to trace the codes. (may be press 2 or 3 F8, for one command step)
That is a bug by IDA or GDBstub, not sure.Click on the address line 364D4B8E0 and press "c" and the code will be show.
F4 works fine,and also confirmed F8 can correct disassembly textThat is a bug by IDA or GDBstub, not sure.
When the breakpoint in effect, it refresh the codes there,
but the result is 1 bit/byte only, the other byte become FF in the 64-bit command, that ida cannot translate to correct code.
To correct the wrongly display, Need disable the breakpoint and press F8 once, and then refresh memory


Can't work, even using WSL.@Eiffel2018 DId you get PINCE set up on windows? I may try to install it on my linux machine to test it out. It looks really promising. I'd just love to get it going on windows.
Keep getting this error all the time though...
Oops! internal error 1338 occured.
Further work is not possible and IDA will close.
Would you like to create a crash dump for a bug report?

After I set the breakpoint, I press f9 to continue and then f9 immediately correctErrors causes by Breakpoints mostly,
Switch it off manually and immediately , when it fire.
Otherwise, the NS machine seems store a wrong breakpoint. and alert you frequently.
Then, you need to detach and attach again to erase the wrong breakpoint.
I wonder if PINCE support ARMv64So I've got PINCE set up on my Linux machine, but it's pretty buggy. GDB connects and attaches, but commands to continue or run just throw errors, so you can't actually search for anything once you've attached. Shame, I'll keep working with it, but I'm running out of patience haha.
If it can somehow attach properly, then it will be a game changer, because it will basically be cheat engine for the switch..
Edit: I don't think it can be done at the moment without some kind of update to the software. It needs gdb-multiarch to run properly and only has gdb.




