RGH Using Nand-X Update Cable for Monitor COM

[tingedace]

Hi

I've been trying to test out the Monitor COM cable I made from the Nand-X USB Update Cable as per the picture reference in the J-Runner user guide.

But I'm not seeing XeLL output displayed in the monitor window.

Before I post pictures of what I'm doing, can anyone confirm if the monitor com should work with any version of XeLL (or just 0.991)? Also on both phat and slim boards?

Thanks

 

[Martin C]

Monitor COM doesn't have anything to do with XeLL.

Cygnos boards used to use COM to look for the !SWITCH signal for early freeboot images. You should be getting something on boot, even from a freeboot image.

 

[tingedace]

OK thanks Martin. I'll keep trying.

 

[Martin C]

A pic of what you have wired up would be useful.

 

[tingedace]

Actually, looking at the J-Runner guide again under
"For CK3i/X360USBPRO V2/CK3 Ver D (with wire) "
it indicates pin 1 of the J2C3 header is TX and pin 2 is RX.

But under
"Nand-X USB Update Cable "
it indicates the reverse.

 

[Martin C]

it's the same as the DemoN guides. 1 is TX, 2 is RX.

 

[stefanounick]

rofl, you're right
from the top of my head, 1 is RX and 2 is TX
dont quote me on that though

---------- Post added at 21:57 ---------- Previous post was at 21:52 ----------

just checked it
yellow wire is TX - 2 on the header
blue RX - 1 on the header

 

[tingedace]

OK so testing my interpretation skills to the max here.... :rolleyes2:

The Nand-X diagram is correct?

 

[stefanounick]

seems so, i went according to the nandx update cable and the qsbs

 

[tingedace]

Here's the cable I made. So if I just attach it to either a slim or phat RGH console and power on as normal, I should see something?

 

[Martin C]

Yep, that should give you something.

If you have dashlaunch installed, you'll get a message telling you.

 

[tingedace]

Tried on a Jasper. No joy

Could it be the Nand-X cable? Drivers? Not sure what to try next.

 

[Martin C]

What was written to the Jasper?

 

[tingedace]

It's an RGH I've had for a while.
I think it's on freeBOOT 15574

 

[Martin C]

Try dropping the baud rate. try 57600 or even 38400.

 

[tingedace]

I'll try them all later. Thanks for the suggestions.
I checked and it's actually running freeBOOT 14719.

 

[Martin C]

I've just tried a few baud rates with mine and even with Demon-compatible UARTs in my image I still get something. Try a freeware terminal emulator and see if that outputs anything.

 

[tingedace]

Found the problem at last....

It was because I had the USB cable plugged in via a USB hub. Once connected directly in the back of the PC it started to work straight away.:facepalm:

I just held the tx and rx cables together for a loopback test and when I plugged it into the back of the PC I started getting characters echoed back.

 

[Krafter]

Interesting. I would have never suspected a hub causing a problem. Good catch and something to keep in mind.

Maybe the hub is a USB1?


Sent from my iPhone using Tapatalk

 

[tingedace]

Maybe the hub is a USB1?

Good call, but I just checked and it says on it "USB 2.0 4-port hub"

I was pretty sure it wasn't going to be the problem and nearly didn't even try. But glad I did!