EZ-Flash USA Forum

No, its not my write code (it's Rudolph's), in fact, I have been far too busy with other things to deal with much of anything else requiring more than short stints at the PC lately, to top it off I still haven't received a "spare" micro sd that I ordered a couple weeks back to do testing on (from Australia of all places).

That said, Image Viewer Ver0.4:
http://mdxonline.dyndns.org/archives/20 ... e_14.shtml
Has what appears to be some write code that should be working. I will test it out in a few hours time, but I havent tried Image Viewer at all to know if it writes anything.

Any input welcome before I get back and do some fiddling.



(PS: thanks guys, I wouldn't ask if I had the time right this second).

just from an initial look

20061110_imgview04_source.zip\20061110_imgview04_source\arm9\source\gba_nds_fat_2006-09-08\ThirdPartyDriver

there's a folder in there 'ezsd_cantwritever'

hopefully that's can't write version, not can't write ever...

i'll dig around a bit more

by ko-tei he means fix (the translator didn't pick it up)

The "function_medium_canwrite" is disabled in that set of files (so it can never write if the driver checks for it) while in the main set it is enabled. The FAT driver I'm testing with doesn't appear to use this attribute at all (while Infantile's does).

Using R17 and only a portion of the files found in the imgview 1.4 source (only used the 3 sdoperator files and the two io_ezsd files) I am getting much more reliable writes than anything else I have looked at so far; it is skipping writing 1 block every 32 with o2 optimization. Out of 7 tests so far of variations on builds and sizes of the file I was copying, there has be 0 instances of FAT corruption as I was seeing previously, and write speed is much much faster.

A bit later...
Found that issue, there is no check with the SD card to be certain it is done writing data... at least, that is my best guess because putting a "status read" at the end of the write function (and discarding the result) appears to have corrected it. If anyone else has different versions of the EZ4 and is willing to test this driver (be certain to backup your data first, just in case), I can attest after much testing of various sizes of "test.bin" files that it is indeed working quite well (with a slight stutter every 32x512bytes for that gap I mentioned above) with the EZ4L deluxe.

Note: it is definitely NOT complete by the standards in place with libFat, but it works well for me under every circumstance I thought up in the last hour to throw at it. A proper status check is probably needed, but for now it is working at least (all without once corrupting my SD card too!)
EZ4FATDemo-Nov-11-2006.zip

and, as promised a looong time ago, when we had a working driver I'd toss a REIN to the test.
REIN_16_EZ4.zip
rein_16_EZ4mod_src.zip

Remember, it is experimental, just because I have had no problems doesnt mean you wont. That said, please let me know if there are issues.

I only have my EZ4lite with me (original model) but it appears to be working on that too. Great work cory1492 and all concerned.
I was trying the demo in the zip by the way.
edit: Rein grabbed my advance wars save too.

I, too, have no real idea who it was who fixed the code. I just know its not entirely complete, but working for me (and should be working in DKP17 and 19).

Thanks, whomever you are who fixed it

Cory,

Thanks for helping to get this working and thanks to the original "unknown" author. Maybe Infantile got it working himself.

Here's what I've tested it on and found:

EZ4 Compact, Kernel 1.72: Working
EZ4Lite, Kernel 1.72: Working
EZ4 Deluxe, Kernel 1.70: Working

Just a note, I get a lot of graphic corruption on the Deluxe compared to the other carts. I'm happy to provide screen shots if you'd like.

Edit:

EZ4 (Phat), Kernel 1.70: Working (and Zero graphic corruption. Odd.)

I tested them all out on my DS Lite. The only difference was the carts and the Kernels, except for the EZ4, which I used a miniSD card, not a microSD.

I don't understand all the details but I have one question
Do you think this discovery should be useful to have DSOrganize writing on EZ4 ?
Since DragonMinded stopped developments, is there someone who should implement this code in the program ?

Shaora,

Yes, it will be most useful in getting DSO working fully. If the code is as complete and easy to drop in, then it shouldn't be too difficult for someone to compile a working DSO.

Infact, it should allow any homebrew to write to the DS card directly. Lets just test it a bit more before shouting out to the world this time Once it's all good, I'll be telling the whole wide world about it.

The person to recompile with write suppport is not me but if you are so inclined davr mirrors the files you will require:
http://blog.davr.org/2006/10/08/dsorgan ... re-mirror/

I'm affraid it won't be me neither... I'm not competent in it.

Wonderful news! Really awesome. :)

2nd the great job!!!! Go cory, work out the bugs with the error checking and distro, implement, and take over as the best for gba compat, nds compat, and now homebrew!!!!!

Way to go!

thanks,

-han

Thanks for the testing guys. No plans to finish any of the "error" (as you put it) code, it is working fine the way it is (with the extra bus read, since to get a bus read it has to wait till the bus is not busy == not writing any more, so it was not to check for an error, just a busy signal) - that can be left to someone else if it is ever merged into libfat.

Slade, you were right, it wasn't very hard (nearly drag and drop with the files I left last night). But after yesterday's service I was far too ready for sleep to make the includes work for DSO too. It was a long long sad day to the end of a long long sad week Thankfully this is something I was able to do to take my mind off it all. Oddly enough, I didnt get any graphic corruption at all with either of the binaries - though I do know how to fix it on any more major applications (use pepsiman's M3powerloader instead of the default one from the toolchains).

Shaora:
DSO-EZ4.zip
Read the readme, there is a comment specifically for you. I would have done more sooner but my father was much more important. Because of the way it seems to be getting invalid data for PersonalData, I was unable to get the IRC function to work (yet? I am somewhat uncomfortable editing the actual DSO app, and the released source was incomplete as "resources" comes pre-built).

hey good work man!