IDE-EXI - no file contents displayed??

[megalomaniac]

ive been having major issues with trying to read a hdd...
ive tried different hdds, IDE and SATA, all formatted to fat32 and also assigned different cluster sizes to the drives for testing....
all drives contain a cleanrip iso and collision.dol in root...with a coleco directory and various contents in the directory

however as the picture shows, the contents are not displayed in the browser...


i am using a recompiled version of swiss for troubleshooting and with this version i can verify,IF ANYTHING, the IDE-EXI can successfully read the drive size, model, serial number, and verify LBA48 support on all the drives being tested...
if i go to "SWISS INFO" i can see "CURRENT DEVICE: 74 GB HDD in Slot B

note: this is my own ide-exi xilinx build, however since the ide-exi software is detected within swiss correctly and since swiss can access the drive to read size, model, etc, all data connections must be considered good....




has anyone else experienced this issue with no data showing up and, if so, how was it resolved???
anyone who provides the correct solution will receive a prize

[dilav]

I had the same problem when I upgraded from Swiss 0.2 to 0.3 and I think I recall reading emu_kidid mentioning something about small drive/partitions problems on Swiss 0.3 and to use a (120?)GB drive or larger.

[megalomaniac]

ok so i tried swiss v1 r52 and i get nothing at all


also the only drives i have available are all under 120GB.....

[emu_kidid]

if you're using the ide-exi v2 code, use Swiss 0.2 or 0.3 only. Swiss 0.1 doesn't support it.

[megalomaniac]

i only have swiss v1 and v3
v3 doesnt show contents and i dont know if i have v2 anymore...

[yamaharacer]

emu where do I get the v2 code? I am just building 3 other ide exis at the moment and want to have them up to date.

[megalomaniac]

got me a 250GB drive now...
tested with v2 r124 and v3 r183

file browser still shows up unpopulated....

[julius]

I do not use swiss v0.3 because it happened the same for me with my ide-exi adapter. I do not know if my ide-exi code is v1 or v2 because I do not know the way of knowing it, so I will keep using swiss 0.2 until we have a new swiss version ide-exi compatible.

[emu_kidid]

All public code is v1, v2 is only beta and I sent it to megaLomaniac as it was having issues.

[megalomaniac]

here is the results of my testing....
a real hair pulling experience over the last few weeks....


i designed my own ide-exi board and needed to test functionality. since it was not a bluechip, magic, or whatever, there was no easy way to find answers/support for my custom version...

i had been having issues with data not showing up in the file browser and i needed a way to troubleshoot my build. i didnt even know if the chip was properly flashed to begin with....emu_kidid provided me with the ide-exi v2 beta firmware which has a signature assigned to it...swiss is able to detect this signature and using a recompiled version of swiss i was able to detect the v2 firmware...this allowed me to at least know i was flashing the chip properly....also (i think) that is when i posted the alternate xilinx flasher design

ide-exi v2 support was added as of Swiss r115...therefore i have been using swiss r124, r174, and a special build of r183 (ide-exi troubleshooter version)


no matter which hdd i used, no matter which method i used to format and write files to hdd, i could not get anything to show up in the swiss file browser with v1 or v2 firmware.....add in some wireporn issues and this get to be too much fun real fast....

based on the comments about similar issues with smaller drives, i sacrificed (reformatted) a 250GB hdd to test the higher storage capacity theory...still no data showing in the swiss browser

based on the comments about similar issues with swiss v2 vs v3 i reflashed the xilinx back to v1 to try swiss r94 (no v2 firmware support in r94)... success!! i can finally see the contents in the file browser (compatible mode only)

since i now have the file browser contents showing up i decided to retest swiss with all my hdds....



with Swiss r94 these are my results:

Code: Select all

SEAGATE 40GB IDE
ST340014A

drive did not work...try again later

Code: Select all

HITACHI 80GB IDE
IC35L09AVV207-0

drive did not work...try again later

Code: Select all

SAMSUNG 250GB SATA
SP2504C
fast = hangs during reading slot B
compatible = contents in browser, hangs on executing app loader

Code: Select all

SEAGATE 80GB SATA
ST380013AS
fast = hangs during reading slot B
compatible = contents in browser, hangs on executing app loader

in all cases these same results occurred with the "working" drives tested:
Swiss r183 - fast & compatible = no browser data displayed
Swiss r174 - fast & compatible = no browser data displayed
Swiss r124 - fast & compatible = stack dump??


...but for the purposes of my testing needs, i am now able to read browser entries and consider this project completed....i can work on trying to get a better drive later to actually use this ide-exi someday...



dilav and julius both win a prize...PM sent

[Cubdax]

Hello. I took several months with the same problem as you. I built my own IDE-EXI and perfect, but always had the same problem that did not show the files.
After a long time I have the right combination to make it work perfectly. Games works perfect too.

HDD (Hitachi 230gb IDE tried, smallers HDD dont work) + Swiss 0.1 r33 (others old versions should work) + DVD Backup in the drive + No Stop DVD motor (very important).

Swiss 0.1 r33 added.

PD: Sorry for my English, is very bad

Some photos:

[emu_kidid]

very nice!

[megalomaniac]

Going back to the original post, for anyone who has experienced the same no browser contents with swiss 0.3, i have had very successful results with latest swiss updates..please try testing again with latest build...viewtopic.php?f=25&t=1375

Remember, patching titles is different with the very latest version of swiss compared to previous swiss v2. So ensure you are only testing to determine if titles listings appear in the browser...if successful, I suggest to begin making a few clean dumps and perform title playback testing..
if everything seems good, test some more and provide feedback results