I would to use the UART resources on the IoT card connector.
Must I have to connect n_card_detect pin to low level to use with I/O ?
Octave does not use the card detect pin when chosing how to configure the UART on the IOT slot. It uses the configuration at /app/io/config to set the owner of a UART, as well as some parameters such as baud rate, etc.
How are you planning to use the UART? For example, will it be routed to an Octave Service, such as ORP, or do you wish to use the tty directly? If you wish to route to an Octave service, select the service and choose UART2 in the Octave UI.
The tty on the IOT slot is: /dev/ttyHS1
I will use the prototype card to connect an external LoRa modem to the FX30.
I tested the configuration and I use the USP protocole to communicate.
In that case, you should only need to configure USP to use UART 2 under:
Services → Universal Serial Parser → UART2
UART 2 is routed to the IoT Expansion slot. The USP service will configure the baud rate, data bits, stop bits, and pairity.
A couple of notes:
- The UART signals on the IoT Expansion slot are 0 - 1.8V
- Hardware flow control (ie. RTS and CTS) is not currently configurable through Octave. It is disabled by default