AT!MAPUART strange behavior



I’m trying to set the MangOH Green with “AT!MAPUART=1,1”. However, when I run the command to check if it worked the result is “AT!MAPUART: 17,16”, looking at the developers datasheet this is not even possible, can someone give me a hint if the command is working and what I’m doing wrong?



what module are you using and fw revision?
run cm info on the device


Hi Asyal, thanks for the feedback.

Device: WP7702
IMEI: 352653090001751
FSN: VU735370470101
Firmware Version: SWI9X06Y_02.16.04.00 019853 jenkins 2018/05/15 19:28:37
Bootloader Version: SWI9X06Y_02.16.04.00 019853 jenkins 2018/05/15 19:28:37
MCU Version: 002.009
PRI Part Number (PN): 9907365
PRI Revision: 001.001
Carrier PRI Name: GENERIC
Carrier PRI Revision: 001.021_000
SKU: 1103530
Last Reset Cause: Power Down
Resets Count: Expected: 79 Unexpected: 15


Can you print your direct output for the AT command?


Sure, I’m attaching it. However, I got it wrong, the output is still strange but not as I said. Can you explain these outputs?



Hi @fefer, that looks good to me. As per AT command spec (

• Execution: AT!MAPUART=<service>[,<uart>]
Response: OK
Purpose: Map the specfiied <service> to the specified <uart> (if no <uart> is
specified, UART1 is used).
• Query: AT!MAPUART?
Response: !MAPUART: <service (UART1)>, <service (UART2)>
Purpose: Report the current mappings for both UARTs

(edit: And by “looks good” I mean it matches the spec :). The asymmetry of the get/set parameters on this one trips me up too.)


Oh, gotcha, thanks a lot!! Yes, it was written but it’s a bit tricky. Another thing about this command that I didn’t get, I saw that I can change both MUX by hardware (using the dipswitch) or by software (using MAPUART). So, how does this works?


Sorry, I don’t follow the MUX/dipswitch comment. Can you point me to the document you’re referring to? I don’t think there are any hardware mechanisms to override the MAPUART configuration, but maybe there is some conflicting documentation.



Sure, Developers guide page 27 and 28, there is a table of how you can change UART settings, it says by hardware/software method. Bellow is the table:


The MUX allows you to direct UART1 to either IoT0 or IoT1 slot.
The AT commands allow you set the desired state of the UART (linux etc.)


Thanks for the clarifying it. The MUX hardware settings allow setting to the Arduino too, right? So, If I’m right and I want a connection of Arduino to the Linux as a bridge connecting to CF3 module I need dipswitch 6 set to OFF and AT!MAPUART set to 17,1, right?