MOD5234 Boot port 2?

[barttech]

I'm using MOD5234-200's for a project where the customer doesn't want ethernet. I've used -100 to develope and now want to put the program on the -200 for delivery. The project uses port 2 for the customer interface so I want to make port 2 be the boot port as well. I ran Setup and set the boot port to 2, and now I don't get any response to 'A' on that port, but if I do (amd only when I do) type 'A' the application won't start either. Of course I set it to Quiet Boot. I know my port 2 is good, when the application starts it uses port 2.
My questions are:
Is Boot Port 2 legitimate on MOD5234 (and if not, why does the Monitor (V 1.11) allow you to change it to 2?)?
How can I get back to being able to program my -200? No RJ45 (do I have to make a RJ-45 to 10-pin cable?), and I can't get setup on any port.
Thanks!
Sam

[Ridgeglider]

It's been a while since I used the 5234 or the Dev 100 board, but I seem to recollect that if you are using the 5234 on either the Dev 100 or the Dev 70 IO boards that Port 2 is not brought out at RS232 levels. An additional level shifter is required for anything other than logic level signals. Could that be your issue? Com0 and Com1 do have level shifters for various protocols on both Dev boards, but not Com2.

[barttech]

You are right about the Dev boards, but I'm using my own board, it actually has RS422 on Port 2 (customer requirement). Port 2 works fine both ways when the application runs.
Sam

[Ridgeglider]

take a look at the SerialEnableHwTxFlow() call in section 19.7 of the NB runtime library. It mentions that this call is how to configure the port for RS422 mode. Maybe you need to set this up in the monitor too? Don't have a '34 handy to check whether hardware handshake options are in the monitor???

[barttech]

There are no Monitor settings for handshaking, and if I could get ot the Monitor I could change back to Port 0. My RS422 port works fine in the application w/o handshaking. I don't think the RS422 issue relates to getting the Monitor back to Boot Port 0.

nb>HELP
Boot alternate app ABOOT
Block fill BF<width> <begin> <end> data
Block move BM<width> <begin> <end> dest
Boot the app BOOT
DownLoad DL
Flash monitor FLM
Flash app FLA
Go GO addr
Help Help
Memory display MD<width> <begin> <end>
Memory modify MM<width> addr <value>
Memory read MR<width> addr
RAM memory test MT <begin> <end>
TFTP download NDL filename
TFTP flash app NFLA filename
TFTP new monitor NFLM filename
Register display RD reg
Register modify RM reg data
Reset Reset
Setup options Setup
Version Version

Sam

[sulliwk06]

I recently tried do the same thing, setting my 5234 to boot from port 2. When I did that the boot prompt actually reverted to port 0 even though it said 2 in the config record. I think the monitor is only set up to use port 0 or 1 for the boot prompt. Try accessing it from port 0 and see if it comes up.

[pbreed]

The current released version of the 5234 montior only supports ports 0,1.


Paul

[barttech]

With the MOD5234 that I tried to switch to Boot Port 2 (which I now understand is invalid),
I don't get a monitor response to an 'A' from any port, using the Mod-Dev-70 set up for RS232. The MOD5234 is running the Factory Demo and it sends out that message on UART0 if I don't send a character on UART1 at boot. Sending a character on UART1 at boot seems to prevent the FD from running. Any boot-time input on UART0 is ignored and the FD starts.
With a MOD5234 that I have not changed the boot port on, I can get to the monitor on UART0. But if I try to send a character to UART1 during boot-time, it hangs up this board as well. If this is really what is happening it seems like a monitor problem to me, since an application could have input on that port while booting, which would prevent booting, when it should just be ignored.

It seems the Monitor has two problems, it can be hung by an inadvertent input to UART1, and it allows a '2' option for boot port which then renders the Monitor inaccessible.

My original problem still persists, "how do I regain access to the monitor on this -200 board?"

Thanks,

[barttech]

Further testing reveals:
1) On the MOD5234 that I tried to set to boot port 2, the FD startup message starts with the "Trying DHCP..." line, it does not display the:
Waiting 2sec to start 'A' to abort
Mod5234 Factory Demo Program
Configured IP = 0.0.0.0
Configured Mask = 0.0.0.0
MAC Address= 00:03:f4:06:f0:7a
that is usually displayed.

2) On the -1588 boards that I have, sending a character to UART1 while booting does not effect the Monitor or the booting process, so maybe there is not a UART1 boot-time problem, or maybe it only effects the -200 somehow?