# MuxConfTool with Developer Studio **URL:** \ **Category:** Development tools\ **Created:** [August 19, 2010, 4:42pm UTC](https://forum.sierrawireless.com/t/muxconftool-with-developer-studio/4620 "2010-08-19T16:42:08Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![cory\_johannsen](https://avatars.discourse-cdn.com/v4/letter/c/a9a28c/32.png) [@cory\_johannsen](https://forum.sierrawireless.com/u/cory_johannsen)\ **Post date:** [August 19, 2010, 4:42pm UTC](https://forum.sierrawireless.com/t/muxconftool-with-developer-studio/4620/1 "2010-08-19T16:42:08Z")
Hello folks, I am building an OpenAT application that will require the use of UART1 to be multiplexed. In the final application, I will need route several communication types over the UART1: 1. AT command access (for diagnostics/test) 2. RTE access (for trace/debug/programming) 3. Data-mode interface to OpenAT application for direct control (used for automated test) I did some digging on the forums and discovered MuxConfTool. I enabled the mux capabilities on my PCs COM1 port (connected to UART1 on my dev kit), and opened two DLCs (COM11 and COM12) I then configured the Target Management perspective in Developer Studio to use COM11. I can connect successfully, retrieve the target info, and can execute AT commands. However, when I attempt to launch the application in RTE debug mode, I get the following (cryptic) RTE kernel error message from RemoteTasks Monitor when I start the application: “SEVERE ERROR: buffer:opic\_wrapperQueryForRTE : NULL == opicint\_wrapperMapForRTE” At this point, RTM dies. I can’t debug, and the application is not running. Anybody have any idea if what I am attempting is possible, and if so, how I do it? Thanks, Cory ---
**Author:** ![awneil](https://avatars.discourse-cdn.com/v4/letter/a/49beb7/32.png) [@awneil](https://forum.sierrawireless.com/u/awneil)\ **Post date:** [August 19, 2010, 5:01pm UTC](https://forum.sierrawireless.com/t/muxconftool-with-developer-studio/4620/2 "2010-08-19T17:01:17Z")
> [@cory\_johannsen](#): > > Anybody have any idea if what I am attempting is possible Yes, it is certainly possible - I am doing it as we speak! > [@](#): > > and if so, how I do it? Apart from downloading, forget M2M/DeveloperStudio for any kind of target interaction - use the old Target Monitoring Tool (TMT) and Terminal Emulator (TE) instead! Until a new version of DeveloperStudio is released with working Target Management, that is… ---
**Author:** ![cory\_johannsen](https://avatars.discourse-cdn.com/v4/letter/c/a9a28c/32.png) [@cory\_johannsen](https://forum.sierrawireless.com/u/cory_johannsen)\ **Post date:** [August 19, 2010, 6:39pm UTC](https://forum.sierrawireless.com/t/muxconftool-with-developer-studio/4620/3 "2010-08-19T18:39:44Z")
Correct me if I am wrong, but with the old tools (Target Monitor/TerminalEmulator) I am limited to trace debugging, correct? I need breakpoints and stepping. Assuming that I could get by without real debugging, which kind of build configuration do I need to create the appropriate binary to program the module with my application such that it is compatible with Target Monitor? I am currently using an RTE Debug configuration. I am using an SL6087 module on a WISMO218 dev kit, which from what I understand does not support JTAG, so I don’t exactly have any other options. ---
**Author:** ![cory\_johannsen](https://avatars.discourse-cdn.com/v4/letter/c/a9a28c/32.png) [@cory\_johannsen](https://forum.sierrawireless.com/u/cory_johannsen)\ **Post date:** [August 19, 2010, 10:00pm UTC](https://forum.sierrawireless.com/t/muxconftool-with-developer-studio/4620/4 "2010-08-19T22:00:10Z")
I discovered the section of the API that details how to create custom AT command handlers, and for my application this will work perfectly (all the diagnostics commands submitted to the device during test are AT-style anyway). I’d still like the ability to utilize the multiplexing on UART1 at some point, but for now I can proceed with an all-AT implementation of the test interface. ---
**Author:** ![awneil](https://avatars.discourse-cdn.com/v4/letter/a/49beb7/32.png) [@awneil](https://forum.sierrawireless.com/u/awneil)\ **Post date:** [August 20, 2010, 5:55am UTC](https://forum.sierrawireless.com/t/muxconftool-with-developer-studio/4620/5 "2010-08-20T05:55:23Z")
> [@cory\_johannsen](#): > > which kind of build configuration do I need to create the appropriate binary to program the module with my application such that it is compatible with Target Monitor? > [@DeveloperStudio with Terminal Monitor and TerminalEmulator](https://forum.sierrawireless.com/t/developerstudio-with-terminal-monitor-and-terminalemulator/4621/2): > > It’s not just the developers - SiWi themselves have admitted that the Target Management in the current DeveloperStudio (aka M2MStudio) is fundamentally broken. A major re-work (“refactoring”) is under way. I have never used RTE mode in M2MStudio, and hadn’t used it for ages with the old tools - there were just too many restrictions and deviations from normal behaviour. eg, see: [https://forum.sierrawireless.com/t/quick-timer-question/4581/8](https://forum.sierrawireless.com/t/quick-timer-question/4581/8) The Debug configurations from M2MStudio work perfe… ---
**Author:** ![daav](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/daav/32/2767_2.png) [@daav](https://forum.sierrawireless.com/u/daav)\ **Post date:** [August 23, 2010, 7:47am UTC](https://forum.sierrawireless.com/t/muxconftool-with-developer-studio/4620/6 "2010-08-23T07:47:12Z")
Please note that RTE mode is indeed not compatible with a connection to the device through MUX protocol. RTE mode is requiring some things to be enabled deeply at system level, and very too early before the MUX protocol has any chance to be restored after the system reset (since starting the application in RTE mode requires also a device system reset). ---
**Author:** ![nguyenducminh](https://avatars.discourse-cdn.com/v4/letter/n/a6a055/32.png) [@nguyenducminh](https://forum.sierrawireless.com/u/nguyenducminh)\ **Post date:** [August 12, 2021, 7:02am UTC](https://forum.sierrawireless.com/t/muxconftool-with-developer-studio/4620/7 "2021-08-12T07:02:22Z")
Could you please tell me where I can download the MuxConfTool? Thank you in advance ---
**Author:** ![jyijyi](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/jyijyi/32/4766_2.png) [@jyijyi](https://forum.sierrawireless.com/u/jyijyi)\ **Post date:** [August 12, 2021, 7:32am UTC](https://forum.sierrawireless.com/t/muxconftool-with-developer-studio/4620/8 "2021-08-12T07:32:59Z")
which module are you using now? ---
**Author:** ![nguyenducminh](https://avatars.discourse-cdn.com/v4/letter/n/a6a055/32.png) [@nguyenducminh](https://forum.sierrawireless.com/u/nguyenducminh)\ **Post date:** [August 12, 2021, 9:02am UTC](https://forum.sierrawireless.com/t/muxconftool-with-developer-studio/4620/9 "2021-08-12T09:02:40Z")
I am using RC7620. I found Linux driver but not Windows version. I run in Windows 10 PC. ---
**Author:** ![jyijyi](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/jyijyi/32/4766_2.png) [@jyijyi](https://forum.sierrawireless.com/u/jyijyi)\ **Post date:** [August 12, 2021, 9:09am UTC](https://forum.sierrawireless.com/t/muxconftool-with-developer-studio/4620/10 "2021-08-12T09:09:52Z")
muxconftool is not for RC76… ---
**Author:** ![nguyenducminh](https://avatars.discourse-cdn.com/v4/letter/n/a6a055/32.png) [@nguyenducminh](https://forum.sierrawireless.com/u/nguyenducminh)\ **Post date:** [August 12, 2021, 9:12am UTC](https://forum.sierrawireless.com/t/muxconftool-with-developer-studio/4620/11 "2021-08-12T09:12:57Z")
@jyijyi : thank you. Can I ask you some question via Whatsapp with regards to AT commands for RC7620?