Trouble Getting into the Monitor

[craiglindley]

I have my 5270/mod-dev-70 system connected to my PC through a usb 2.0 to RS232 adapter. When I hit the reset switch on the mod-dev-70 board I get the prompt

Waiting 2sec to start 'A' to abort

And I hit A but cannot get the nb> prompt. The results are always the same as shown below:

Configured IP = 0.0.0.0
Configured Mask = 0.0.0.0
MAC Address= 00:03:f4:03:01:ec
Initialized GDP tcp

I've tried just about every flow control configuration Mtty has to offer but with no joy.

Is there something else I can try or do I need to send my 5270 back for service.

Any help would be appreciated.

[rnixon]

I had this problem and it was because my usb to serial adapter was not sending out the character. Also, make sure is is a capital A, not lower case. No handshaking is needed.

[craiglindley]

Now I'm wondering if the problem is related to using the newest 2.2 version of the development tools on a MOD 5270 that is a year old. Were there changes to the MOD 5270 hardware necessary for the new software to work? Could downloading my code built with the new tools to my older MOD 5270 board have caused the monitor not to respond?

Also does anyone know where in the netburner code these messages would be coming from and what they mean (especially the final line)? They are not coming from my app I don't think.

Configured IP = 0.0.0.0
Configured Mask = 0.0.0.0
MAC Address= 00:03:f4:03:01:ec
Initialized GDP tcp

Also I have determined my usb2.0 to RS232 converter is not the issue as I found an old PC with a real serial port and connected it to the development board using hyperterm and got exactly the same response. It is as if the monitor is not waiting for a keypress.

Thanks

[Chris Ruff]

Craig:

the data comes from monitor "loud" boot.

The tools essentially have nothing to do with the monitor. If it is there and speaking, it won't change or be changed.

In my opinion, Hyperterm Sux.

Use MTTTY.exe, that is a great terminal app (especially the Ruff'd version in files)

If the default wait value is changed from 2 seconds in the monitor you may have to type in SHIFT-A REAL FAST after powering up.

Chris

[craiglindley]

As it turns out the problem was with my rs232 - USB cable. I could receive data via this cable but not transmit. I went out and bought a new cable and now things work great.