# How to disable Serial STDOUT after boot and start Serial CLI

**URL:** https://forums.digi.com/t/how-to-disable-serial-stdout-after-boot-and-start-serial-cli/5263
**Category:** NET+OS
**Created:** [January 29, 2013, 4:37pm UTC](https://forums.digi.com/t/how-to-disable-serial-stdout-after-boot-and-start-serial-cli/5263 "2013-01-29T16:37:58Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![jamesarm97](https://avatars.discourse-cdn.com/v4/letter/j/f07891/32.png) [@jamesarm97](https://forums.digi.com/u/jamesarm97)
#### Post date: [January 29, 2013, 4:37pm UTC](https://forums.digi.com/t/how-to-disable-serial-stdout-after-boot-and-start-serial-cli/5263/1 "2013-01-29T16:37:58Z")

</div>

I am using NetOS7.5 and the Digi Connect ME 9210 module. It only has one serial port and I am short on other pins. I would like to still be able to see the boot options as the program starts and any messages my code my display. After getting past a certain point I would like to be able to disable the stdout and re-use the serial port A for serial CLI for local programming and setup. Is this possible? I have tried to just set the CLI serial port to port A but it will not start without an error because of the port already being opened by stdout.

---

<div class="post-metadata">

### Author: ![dakotas\_dad](https://avatars.discourse-cdn.com/v4/letter/d/a88e57/32.png) [@dakotas\_dad](https://forums.digi.com/u/dakotas_dad)
#### Post date: [January 29, 2013, 9:21pm UTC](https://forums.digi.com/t/how-to-disable-serial-stdout-after-boot-and-start-serial-cli/5263/2 "2013-01-29T21:21:50Z")

</div>

Look at file bsp\customize\dialog.c. IN that file is an API NACloseDialog. I believe that will close out the channel used by the dialog, restore all and put you in a position to reopen the serial channel for your own uses.
