#157232 - 11X_daemon_X11 - Tue May 20, 2008 9:27 pm
Now, I'm messing around with a hex editor on my DS, decided to run ds linux really quick, used the whole DF command to check memory and it found two files. so on the hex editor, I decided to experiment. Those two files (/dev/rom0 and /dev/dldi1) were able to be opened in the hex editor, and I was wondering what those two files actually are seeing how I don't have a director of /dev, nor any files named rom0 or dldi1. I noticed in the rom0 there were alot of lines in ascii that said rom* (* meaning a different number each time). Would the rom0 file be the firmware or rom on the games N music card, or just a file temporarily created on the SD card? Just wondering if I found anything special xD
_________________
IRC (please join :D):
http://evilnetirc.ath.cx/
#157233 - tepples - Tue May 20, 2008 9:53 pm
http://en.wikipedia.org/wiki/Device_node
_________________
-- Where is he?
-- Who?
-- You know, the human.
-- I think he moved to Tilwick.
#157234 - 11X_daemon_X11 - Tue May 20, 2008 9:59 pm
So its nothing special? darn :(
edit: well... the reason I thought I coulda found something special was because (even though for what ever reason, my DS is being stupid and is having problems with telling the amount of memory used and saying there is no memory left on the card) they both had a memory number. One was I do believe 400 some kilobytes (or bytes... I can't remember, which was the rom0) and the other had 120mb (about 122000kb as it said, which was the dldi1), which is the exact memory number on my SD card.
_________________
IRC (please join :D):
http://evilnetirc.ath.cx/
#157235 - tepples - Tue May 20, 2008 10:06 pm
I guess /dev/dldi1 must correspond to /dev/sda1 or /dev/hda1 on an ordinary PC running Linux.
_________________
-- Where is he?
-- Who?
-- You know, the human.
-- I think he moved to Tilwick.
#157236 - 11X_daemon_X11 - Tue May 20, 2008 10:10 pm
All right.. :) well the thing about that that I found weird is that I opened the dldi1 file with the hex editor, but I don't think you're supposed to be able to do that. I'm guessing you're right because that sounds like what it should be, so I'm going to go with you on that one :)
_________________
IRC (please join :D):
http://evilnetirc.ath.cx/
#157257 - sonny_jim - Wed May 21, 2008 8:28 am
Once again, I'll remind you to use the DSLinux forums for DSLinux related things:
http://dslinux.org/
Please do not clutter up the GBADEV forums with posts that 99% of the people here do not want to read
EDIT: /dev/dldi is the whole DLDI device (ie SD card), /dev/dldi1 is the first partition on /dev/dldi and IIRC /dev/rom* and /dev/firmware are the firmware of the DS(read-only for safety)
#157274 - pepsiman - Wed May 21, 2008 3:46 pm
sonny_jim wrote: |
EDIT: /dev/dldi is the whole DLDI device (ie SD card), /dev/dldi1 is the first partition on /dev/dldi and IIRC /dev/rom* and /dev/firmware are the firmware of the DS(read-only for safety) |
rom0 is the device the romfs is mounted from.
firmware is the DS firmware.
dldi* are the flash device.
#157365 - 11X_daemon_X11 - Thu May 22, 2008 8:00 pm
Sonny, this wasn't really a linux ment post, I said I found the dldi and such with linux :p and actually, I do believe that /dev/rom is the ds firmware, but oh well... (that's how I found and copied the DS firmware to my SD card, anyway)
But I have a question that has nothing to do with linux, I have a hexfile of the DS firmware, is there anyway to turn this into a .nds file to mess around with? :)
_________________
IRC (please join :D):
http://evilnetirc.ath.cx/
#157585 - dantheman - Mon May 26, 2008 11:25 pm
You could use DSLazy to unpack Olimar's *.nds firmware file, change some stuff around with a hex editor, then repack it. I messed around with changing the text for some menus, but didn't do anything else besides that.
His firmware.nds file can be found at http://forum.gbadev.org/viewtopic.php?t=13459
#157590 - 11X_daemon_X11 - Mon May 26, 2008 11:37 pm
Well what I wanted to do was use my Games N' Music card as a booter (which only works if you boot to dso to run the firmware I guess =\) and mod the DS firmware so that when you changed game cards, it would recognize that theres another game in instead of freezing up. would that be possible?
_________________
IRC (please join :D):
http://evilnetirc.ath.cx/
#157594 - tepples - Tue May 27, 2008 12:08 am
11X_daemon_X11 wrote: |
Well what I wanted to do was [...] mod the DS firmware so that when you changed game cards, it would recognize that theres another game in instead of freezing up. would that be possible? |
In order for modified firmware to recognize a hot-swapped DS Game Card, it would have to include a dumper. Right now, the firmware relies on a dumper hidden in a double-secret part of the BIOS.
_________________
-- Where is he?
-- Who?
-- You know, the human.
-- I think he moved to Tilwick.
#157596 - 11X_daemon_X11 - Tue May 27, 2008 12:16 am
Ahhh so right now, its not possible to allow that?
_________________
IRC (please join :D):
http://evilnetirc.ath.cx/
#157630 - tepples - Tue May 27, 2008 12:45 pm
There are two reasons we can't put a dumper in the firmware. First, the existing dumpers are treated as closely guarded secrets in order to make life more difficult for pirates. But more importantly, there isn't any space left.
_________________
-- Where is he?
-- Who?
-- You know, the human.
-- I think he moved to Tilwick.
#157633 - sonny_jim - Tue May 27, 2008 2:39 pm
Also, just to clarify:
/dev/firmware is the firmware
/dev/rom0 is the location of the initrd used to boot DSLinux, which I'm almost positive you aren't interesting in.
#157674 - 11X_daemon_X11 - Tue May 27, 2008 8:09 pm
If you want, use cp /dev/rom1 /media/, it'll allow you to copy the /dev/firmware (as firmware can't be copied by itself. It'll created an empty file). rom1 is also the firmware.
_________________
IRC (please join :D):
http://evilnetirc.ath.cx/
#157686 - sonny_jim - Tue May 27, 2008 8:54 pm
The firmware can be read, as an application called fwver uses it to check the version and also print a cake on the users birthday :-)
/dev/rom0, as pepsiman said earlier, is the romfs which contains all the applications that are needed for DSLinux before the DLDI device is mounted. This is appended to the end of the dslinux.nds file during compilation and gets loaded into RAM during boot.
Short version = It's not the firmware you are copying.
#157750 - 11X_daemon_X11 - Wed May 28, 2008 8:10 pm
I never said rom0, I said rom1. like I said, use the command cp /dev/rom1 /media you'll copy the firmware because of how the /dev/firmware won't copy. :p
_________________
IRC (please join :D):
http://evilnetirc.ath.cx/
#157767 - sonny_jim - Thu May 29, 2008 12:45 am
I think I might believe pepsiman's opinion over yours concerning anything to do with DSLinux.
You can't use cp to copy /dev/firmware because it doesn't work like that. Try using dd instead. Post a new topic over on the DSLinux forums if you want more assistance
#157774 - 11X_daemon_X11 - Thu May 29, 2008 1:50 am
I don't need assistence sorry about tht I was just saying you can use cp /dev/rom1 to obtain the firmware :p but yes, I would like to request this be closed :)
[Secret Bear was here]
_________________
IRC (please join :D):
http://evilnetirc.ath.cx/