Thanks, that fixes all of the issues I've been having.
But I'm a bit confused. Isn't that the same as what's used to compile for the original DS?
This code is running on the arm9 processor which is mostly the same as the DS. There's also the arm11 processor.
For anybody using GNU/Linux, I made a modified build.py file. Be sure to chmod +x it.
Also to get this to compile, I had to add the following to 3dsploit.py in lib/p3ds:
Then set 3dsploit.py to have execute permissions using chmod +x. The compiler I'm using is arm-eabi-gcc instead of arm-none-eabi-gcc. I'm not sure what the difference between the two is, but arm-eabi-gcc seems to work fine.
Also to get this to compile, I had to add the following to 3dsploit.py in lib/p3ds:
Code:
#!/usr/bin/python2
I can confirm that you are right as well, thanks
Funny then that the build otions in build.py have
Code:
CC+" -g source/*.c -c -mcpu=mpcore -march=armv6k -mlittle-endianYou guys are posting about stuff you don't understand. Spreading fog and misinformation. Please keep your dumb wrong technical guesswork to yourself and leave it to the pros to discuss the advanced stuff.
http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.ddi0301h/apbs02s02.html
Not you, that's for sure. It's from user tomiga - he knows what he's doing - you and your mates don't
edit - ok maybe you did the original.
I still don't think the code is running on arm9 - where is the fucking arm9 processor? - source of this information please?
I still don't think the code is running on arm9 - where is the fucking arm9 processor? - source of this information please?
Ok, well that page doesn't say anything about a physical arm9 cpu - it would surely be visible on the circuit board anyway. The arm11 processor is backward compatible with arm9 code so I assume they just switch the chip into a special DSi compatible mode by lowering the speed and disabling dual-core. Similarly arm11 is backwards compatible with arm7 code (but arm9 wasn't backward compatible with arm7 - which is why the DSi had a separate arm7 cpu) - so for DS mode even lower speed single core processor mode needs to be engaged.
http://www.arm.com/products/processors/classic/arm11/index.php
Maybe your compiler options are causing arm11 simd instructions to be generated and executed in a mode for which the arm11 can't execute these codes (because dual-core disabled??)
lol - now I'd doing what i accused you guys of, just guessing.
Anyway - I was wrong to act like a dick - but I still think there is no physical arm9 chip as Bond697 posted - just various compatibility modes of the dual-core arm11 cpu which you switch between via register pokes
Why would there be? - the arm11 is backwards compatible with arm9 (and arm7)
Where is your source? - eg a picture of this extra cpu would be good.
Also - I have now solved the confusion of how they execute arm7 DS code - the code is executed on an arm11 (in single core mode) NOT on an arm9 cpu?
Similar threads
-
@
SylverReZ:
@Veho, Sounds and smells like bullshit. They don't give you cancer, and California should know that. I don't get why they stick labels that say "may or may not cause reproductive harm or cancer". -
-
-
-
-
-
-
-
-
@
Psionic Roshambo:
Mame should be two sets one for preservation of everything and one set for people who just want to play and enjoy the old old ganes -
-
-
-
@
SylverReZ:
@Psionic Roshambo, Believe Japan was going to make it legal at some point, according to a Kotaku story.+1
-
@
Psionic Roshambo:
I swear like 99% of arcade games wouldn't even exist these days outside of MAME the arcade machines are old and busted very few ever saw any sort of home conversion
-
-
@
SylverReZ:
@Psionic Roshambo, There's a lot of obscure Japanese arcade titles that are either lost to time or dumped.+1
-
-
@
Psionic Roshambo:
I mean if a company could use AI to do the work of a home conversion for essentially free why not? The rights for some games are completely lost though
-
-
-
-
-
-
