SC200E Main UART

I have a development kit SMART-EVB-G2_v1.3 with SC200E.

Could someone explain how to use the MAIN UART? If I connect the DEBUG UART to my PC I can get the console, but main UART just send this message at boot “Android Bootloader - UART_DM Initialized!!!” and I can’t do anything with it. The documentation informs that objective of this UART is send AT commands and data, how to do that?

At the end, I need to use this UART to connect a RS485 interface to send and receive application specific data to anothers devices at a proprietary network. If the AT commands really works, I need disable it to get control of this UART.

Here is the ttys, someone knows which one is the main uart?

/dev/ttyHS0
/dev/ttyHS1
/dev/ttyMSM0
/dev/ttyprintk

Thank you,
Leonardo

For the SC200E,
the ttyMSM0 is the debug console.
The ttyHS1 should be the Main uart.
The ttyHS0 Is used for Bluetooth.

But if you would like to test it, you have to make sure the uart would not go to runtime suspend flow.

image

Thank you, it works.

Could you help with more one question?

Is the UART1_TX and UART1_RX used for bluetooth internally? Or it could be used for my application? My doubt is because these pins are avaliable externally at SC200E.

image

According to the Hardware Desigin,
the main uart:

if you would like to use the UART1, even though according to the HD, it can be used, but actually you still need some patches from Quectel. At least, I am sure Quectel have to provide you a TZ image.

But it is sorry I cannot provide it in the forums.

@Bean.Wang-Q could you explain better the use o UART1_TX (GPIO_69) and UART1_RX (GPIO_70) from QUP_SE1?

Looking at scuba-pinctrl.dtsi, scuba-qupv3.dtsi and scuba.dtsi I saw that node for serial exist “qupv3_se1_2uart: qcom,qup_uart@4a84000” but is disabled. For enable it I change at scuba.dtsi

&qupv3_se1_2uart {
status = “ok”;
};

the status to “ok” but it seems not work, at least I can’t get a new /dev/ttyHSx as expected.

At your last post you mentioned about TZ image, could you explain why? I really need Quectel help just to change simple things like this at kernel/Android stage? I was thinking that Quectel changes would be necessary only at bootloader stage.

The things will be much more difficult if I need binaries from Quectel to do this kind of change.

Thank you,

Leonardo