Path: chuka.playstation.co.uk!scea!pro1-145.barrie.connex.net!user From: skennedy@bconnex.net (Sean Kennedy) Newsgroups: scee.yaroze.freetalk.english,scea.yaroze.freetalk Subject: Re: TestCard() issue Date: Wed, 16 Sep 1998 23:08:28 -0500 Organization: Wooden Tulip Ltd. Lines: 70 Message-ID: References: <35FC10F2.3841CEE6@bigfoot.com> <35FD49AC.7FA76186@augsburg.baynet.de> NNTP-Posting-Host: pro1-145.barrie.connex.net Xref: chuka.playstation.co.uk scee.yaroze.freetalk.english:2347 scea.yaroze.freetalk:936 > > I'm posting this message in the freetalk area because I don't think that > > many people read the codewarrior newsgroup. I had a few responses to > > that post, but the issue is still unresolved. So here it goes. > > Has anyone had any problems using TestCard() in CodeWarrior? > > I just recently bought a new memory card (Hey, it was a black memory > > card. I just HAD to have it to match my black playstation. :) and I > > wanted to find out how a new, unformatted card behaved. So I write this > > really small program: (No this isn't my programing style, I just wrote > > it quickly to see how it works) > > > > -- START OF CODE -- code bits here deleted, see before... -sean > > -- END OF CODE -- > > > > I tried to run it in CodeWarrior... And my playstation ALWAYS chokes on > > the TestCard routine. Always. No visible error. It just locks up. Blam. > > Doesn't matter what card is in the slot. Even without a card. Crash. > > Burn. Die. > > I can't get it to work. No matter what I do. I tried changing alot of > > target information, but it didn't seem to help. > > Then I compiled this same exact program in GCC and it works like a > > charm. (BTW, New memory cards return 4, and the access card returns 0) Yep, and a GCC code or CodeWarrior code bit Will Work. Except while in the Debugger. When Codewarrior is used for downloading code, they envoke the run-time debugger at startup communcation, watch the NTSC console, then look at the terminal window and try running the debugger from there. HEH, have a Nice Day.... THIS DEBUGGER SHOULD NOT BE USED THIS WAY. As it turned out I ran into a similar problem when I was testing some context RTOS code the I compiled using CodeWarrior, In the debugger it crashed. in SIOCONS, it worked. Here's a quick todo. Compile the app into a floppy, go into the CW preferences and look up where the code segment is located to. Take floppy to COMMAND.COM and run SIOCONS, BLOAD the file to the same address and run it from the terminal console. It should work. AND it was compiled on Codewarrior! not GCC! Now I have to figure out how to update my dev environment from GCC Net Yaroze MkLinux from Gcc to EGCS, -Sigh-. -sean > > In the other newsgroup someone tested my code and confirmed that it > > crashes the yaroze when compiled with codewarrior. This would seem to be > > a serious problem... I'm suprised that no one has run into it before. > > 'Darco > You're not the only one with that problem. I have the same problem with > CodeWarrior. > Unfortunately i don't no any solutions. > Maybe, Metrowerks knows an answer to this problem. They do, I don't know if Joel Sumner has been able to make any changes in regards to this, since those who wish to try their hand at Assembler are pretty well cooked in the CW IDE environment. Hence my deviation to GCC running on MkLinux. On PC's having a program like Z-Term would be really cool. And modifying Z-Term for MacOS to do PSX terminal stuff would be super cool. BLOAD support from a Mac Terminal program would benefit us all. And we can make our own breakpoints CTRL-Z? anyone. Anyone? -sean