Home/Support/Support Forum/stdio set to com0, but exceptions still come to com1
Welcome to Digi Forum, where you can ask questions and receive answers from other members of the community.

stdio set to com0, but exceptions still come to com1

0 votes
Whenever my program has an exception, the error message comes out com0 instead of stdio, which I have set to com1. Is there some config that I can change so it comes out com1 like it should? It's annoying because the extra data messes up the equipment connected to com0, not to mention I can't easily see the exception data.

The changes I made for changing the stdio port:
#define BSP_STDIO_PORT "/com/1"
#define BSP_DIALOG_PORT "/com/1"
#define BSP_SERIAL_PORT_2 BSP_SERIAL_UART_DRIVER

Thanks,
Mike


Message was edited by: turbo2ltr
asked Nov 2, 2007 in NET+OS by turbo2ltr New to the Community (8 points)
recategorized Dec 18, 2013 by tuxembb

Please log in or register to answer this question.

2 Answers

0 votes
Did you do a full build-all and reload the boot block rom.bin as well as image.bin? That may be a factor (just guessing).
answered Nov 14, 2007 by harding New to the Community (14 points)
0 votes
Well I did a full build of the BSP. I always assumed that when you debug in the Digi ESP, it loads the complete firmware via jtag including the boot block.

It seems it stems from the fact that the OS uses low level "SimpleSerial" functions for exceptions and it must be hardcoded to com 0. Unfortunately I don't think it's changeable...

BTW, I just realized that title is wrong..
Should be "stdio set to com1, but exceptions still come to com0"

Thanks!
answered Nov 14, 2007 by turbo2ltr New to the Community (8 points)
...