I suppose you would need to check with nocash to see wether or not the upload utility for that takes the initial address from the EXE or just defaults to a prefixed address (although I would have thought it would do). To test my theory you could try to run a different EXE that was built with PSXSDK ...

mrhaboobi wrote: ↑November 22nd, 2018, 11:01 am You should have siont which was a rebuild of sicons to supports nt and non dos stuff

Where can you find SioNT?

Thanks

This is something I am interested in, as I want to get some stuff running on RaspberryPi.
Will give it a go later.

Thanks

The reason might be the initial address that the different libs use. Think the BladeLibs/PsyQ created binaries load at certain address and PSXSDK binaries load at another. Xavi92 had this issue when trying to load PSXSDK binaries via PSXSERIAl, as it uses a hardcoded address rather than loading it f...

Doesn't need to be an FX, I use a Xplorer pro as well.

There are always plenty on eBay, you can pick them up for as little as £6-10

Yeah it's harder with the AR's.. you need to use a hardware latch and whatnot and completely different software, way beyond my capabilities. The above will work with an Xplorer/Xploder device only. That being said, if someone could get the Linux port of catflap to work with Freewing hardware again, ...

No worries, glad you got it working.

Just to add, you don't need to do anything to use psxserial or anything else, just use as is as it works for everything. No need to reprogram the ftdi with ftdi-prog or whatever.

You are only inverting the handshaking lines, which psxserial doesn't use so it works with both.

No problem at all, nice to see someone following my guide and getting stuck in.

I really like the look of that sparkfun module, may pick one up and update the guide a bit seen as it's a certified genuine FTDI part

GetPadBuf() is a function in the Yaroze SDK.

could be your example is targetting the wrong SDK?

This is something I have always wanted to get working, and dreamt about way back in 2012 when I got a RaspberryPi Model B at launch. My current Xplorer setup used a HP thin terminal, which worked fine but the thin client was actually larger than the Playstation. With Arduino etc there was always goi...

Best setup I find is still an Xplorer flashed with Caetla + parallel printer port cable. You can use modern operating systems to communicate with it using catflap, for which there are both Linux & Windows ports. This gives you the most flexibility. For Simplicity, you have psxserial using the se...

Looks perfect from the signal point of view (RTS-CTS etc)

Just don't worry about the internal wiring colours, as they differ from cable to cable.

That will do the job perfectly . It has all the pins needed broken out and more, and seems very cheap too.

Also, it mentions the eeprom which is the bit the fakes don't copy.. which we need for the above.

I am going to stick with the ESPlink firmware for now, as it is much more user friendly to set-up (web based interface for settings). I suppose the first bit is to get a version of psxserial that we can pipe to a TCP port rather than serial and see what the ESPlink firmware does with the data and ta...

The ESP32 has three hardware UARTS, i think two of them can be mapped to pretty much any pins you like one you are past the bootloader. ESP32 is an amazing bit of kit - with its pin mux you can pretty much map any pin to anything within reason. Its slightly overkill for this mind you. I have absolut...

Adafruit should be genuine, but that is missing DTR/DSR signals broken out to pins so wouldnt work - unless you dont mind soldering directly to the pins on the IC itself which I wouldn't recommend. With that pin layout they are mainly designed for programming Arduino Pro Micro and that kind of thing...

I only ever use no$psx, which worked fine for me. It has a lot more debugging information so it should be easier to see where its going wrong - it supports loading EXE's so should be fine.

If your build output is correct, and you can covert it to an EXE without issue it should run fine.

Hello and welcome.

sounds like you are part way there if you have compiled the EXE.. but what are you trying to actually run the EXE file in? Ignore the fact that it is called an EXE, you cant run it in Windows - you need to load the EXE into a PlayStation Emulator like no$psx etc..

Basically, avoid eBay and anything that is cheap. Amazon have a few - see attached picture (depends on your location, not sure about Australia) - this model says that it is genuine. To check if you have a genuine, try changing some of the values in FTprog, you will find that the changes are always l...