• Welcome to SCdev.org. Please log in.

Welcome to the new SCdev forums!

HOW TO use Supercard and DSLink at the same time

Started by bitblt, November 19, 2006, 07:29:52 PM

Previous topic - Next topic

ratx

bltblt I haven't tried it on a supercard no, but its a "homebrew" file, try running as patched via scmhbp ;)

bitblt

Quote from: "ratx"bltblt I haven't tried it on a supercard no, but its a "homebrew" file, try running as patched via scmhbp ;)

I know sm-mk4ds.nds is written by the Neo team but it doesn't have a standard "homebrew" header. Even scmhbp thinks it's a commercial ROM . . .

sm-mk4ds.nds: size: 256k
sm-mk4ds.nds: ndsloader not detected
sm-mk4ds.nds: 0x20 found arm9 offset
sm-mk4ds.nds: is probally a commerical ROM... exiting
Hit RETURN to exit

moviecouple

bitblt

QuoteI see that it works with the latest 1.70 firmware for Supercard CF/SD/miniSD.... what about the Supercard Lite MicroSD?

bitblt

moviecouple

I don't know if it will work with SC lite because I don't have one. I think it should work but I'm not sure. Basicly what unpatcher does is replace 'BOOT' in the SC firmware with spaces, so flashme doesn't auto boot the Supercard.

EDIT TYPO:

Basicly what unpatcher does is replace 'PASS' in the SC firmware with spaces, so flashme doesn't auto boot the Supercard.

moviecouple

OK. Wish someone could confirm this before I try. I would hate to destroy my Supercard Lite.

bitblt

Quote from: "moviecouple"OK. Wish someone could confirm this before I try. I would hate to destroy my Supercard Lite.

I understand.

BTW there is a way to recover the SC lite firmware if something goes wrong trying to use unpatcher.

moviecouple


bitblt

Romman posted this recovery procedure on the Supercard site . . .
http://eng.supercard.cn/

Update(2006.11.11):About the SuperCard Lite upgrade & downgrade problem

Recently, there are some customers downgrade the SuperCard Lite version firmware v1.7 to v1.63. Even I don't know why they downgrade it, but they found out that the SuperCard Lite crash.
Here list below are the steps: How to upgrade to V1.7 again.

1. Format a MicroSD card.
2. Copy the firmware V1.7 file on it. Don't copy any other files.
3. Insert the MicroSD card and SuperCard Lite.
4. Open the DS power switch, don't care about the screen and wait 5 seconds.
5. press "A" button. You will find out that you can upgrade to V1.7

ratx

bltblt try just prepending the loader manually?

bitblt

Thanks ratx, to my surprise manually prepending ndsloader.bin worked. What threw me off was that scmhbp.exe and DSLink 1.32 both recognized sm-mk4ds.nds as a commercial ROM?

As you said mk4ds.nds works in both directions. The only downside is that it only works one time. In other words mk4ds.nds doesn't work correctly the second time it's run for some reason.

Anyway, excellent find ratx. This solution can be used as an alternative to using the Suprcard firmware unpatcher. The best case scenario is to boot the Supercard menu normally, use mk4ds.nds to boot the DSLink menu, and then return to the Supercard menu again using LoveLite.

Now that I know it's possible, I'm going to try and figure out how to modify Licks libcartreset to support booting the DSLink menu. I want to create a simple utility that will allow switching back and forth between Supercard and DSLink.

moviecouple

bitblt

Isn't that recovery only from downgrading? Is using the unpatcher really a downgrade to the firmware... or more of just an alteration to the current firmware you are using?

ratx

bltblt yeah that is a bit odd, it has a weird secure area crc 77/4d?? bizarre.. I've added it to scmhbp anyway, will get a new build out when I  can get mingw to download / installl.

Does the dslink patcher not patch homebrew then? I've just put homebrew stuff straight on my dslink without problem ( well you need to create a sav file unless you don't mind it moaning ) , just curious how come it thought it was commerical?

bitblt

Quote from: "moviecouple"bitblt

Isn't that recovery only from downgrading? Is using the unpatcher really a downgrade to the firmware... or more of just an alteration to the current firmware you are using?

I believe it's a standard recovery procedure.  Rommans team put this "back door" feature in the firmware before anyone (even Romman) knew there was a problem downgrading SC Lite.

However, SC lite owners might prefer to avoid any possible risk and use sm-mk4ds.nds as ratx has suggested.

bitblt

Quote from: "ratx"bltblt yeah that is a bit odd, it has a weird secure area crc 77/4d?? bizarre.. I've added it to scmhbp anyway, will get a new build out when I  can get mingw to download / installl.

Does the dslink patcher not patch homebrew then? I've just put homebrew stuff straight on my dslink without problem ( well you need to create a sav file unless you don't mind it moaning ) , just curious how come it thought it was commerical?

The DSLink patcher does not patch homebrew, it only copies homebrew to the TF. I manually copy 'homebrew.nds' stuff straight to my DSLink without prepending ndsloader.bin or using scmhbp. This is how homebrew works with DSLink.

Normally DSLink only creates a save file for commercial ROMs. When I run sm-mk4ds.nds the DSLink expects a save file to be present as if it was commercial. When I run sm-mk4ds.nds through the DSLink patcher it generates a save file as if it was commercial. The DSLink has never done this with other homebrew.  I guess it's because sm-mk4ds.nds has a non-standard packed header?

ratx

bltblt ah yeah I see what you mean... thanks