VOXL 2 / M0062 Configuration Questions

[김다연]

Hardware: (board / drone / SKU, serial # if you have it): voxl2

Software version: (paste the output of voxl-version

Configuration / services: (paste the output of voxl-inspect-services)bolded text

What I am trying to do:
1. IMX412 Camera Frame Rate Configuration

• list itemCould you confirm whether the IMX412 camera’s frame rate can be set to 8.6 fps to match the operating frequency of our IR camera (Lenton)?

• list itemIf this requires modifications to the kernel or camera driver, could you provide instructions for building and flashing the modified software?

• list itemIs it possible to change the frame rate through software configuration after boot without modifying the kernel?

2. UART Configuration on the J3 Connector

• list itemCould you explain how to configure and enable the UART7 and UART13 pins on the VOXL 2 J3 connector for communication with an STM32?

3. Camera FSync Configuration on the J3 Connector

• list itemCould you confirm the GPIO assignment and control mechanism for outputting an FSync (Frame Sync) signal to a camera through the J3 connector?

• list itemCould you provide instructions for enabling the FSync signal, configuring its period, and applying the settings?

4. Clarification Regarding the Boot Mode Switches on the M0062 Board

Our understanding is as follows:

• list itemFastboot is a bootloader mode used to install or update system images.

• list itemEDL is a low-level recovery mode used when a boot failure prevents access to Fastboot.

The VOXL 2 includes Fastboot and EDL switches. We believe access to these switches may be necessary during development and operation in case recovery is required. Please refer to the image below for the connections between the VOXL 2 and the M0062 board.

However, based on the M0062 board block diagram, the boot mode switches on the M0062 board appear to be unused. Could you confirm whether these switches are actually used and, if so, under what circumstances?

What actually happens: (error messages, behavior)

Steps to reproduce:

Logs / pictures: (attach files; PX4 logs -> https://logs.px4.io)bolded text

[Vinny]

Hi @김다연
Responses in order:

1. IMX412 frame rate

Frame rate is set per-camera in /etc/modalai/voxl-camera-server.conf, no kernel rebuild required, but you are limited to the sensor modes the driver defines. 8.6 fps is not a standard IMX412 mode, so it almost certainly requires a new mode in the sensor driver and a kernel rebuild. Before going down that path: if you only need the two cameras aligned, use the frame sync hardware rather than matching free-run rates. Camera config: https://docs.modalai.com/configure-cameras/

2. UART on J3

J3 exposes UART7 only, on pins 3 and 5 (GPIO_23 RXD, GPIO_22 TXD), enumerated as /dev/ttyHS1. UART13 is not on J3, it is on J5, the high-speed B2B. Full J3 and J5 pinouts: https://docs.modalai.com/voxl2-connectors/

3. FSync on J3

J3 does not carry a camera sync signal. FSync is GPIO 109 on the camera group connectors (J6/J7/J8) and is driven by voxl-fsync-mod, enabled through voxl-camera-server. There is nothing on J3 to configure for this.

4. M0062 boot mode switches

Your understanding of the two modes is correct. The DIP switch on the M0062 is unused. The Fastboot and EDL switches are wired in parallel with VOXL 2’s own SW1 and SW2 and do exactly the same thing, so use whichever is physically accessible in your build. Recovery procedures are documented here: https://docs.modalai.com/voxl2-connectors/#buttons and https://docs.modalai.com/voxl2-unbricking/

SW2 (EDL) should be left OFF in normal operation.

[김다연]

This post is deleted!

[김다연]

@Vinny said:

J3는 3번 핀과 5번 핀(GPIO_23 RXD, GPIO_22 TXD)을 통해 UART7만 제공하며, 해당 장치는 /dev/ttyHS1로 열거됩니다. UART13은 J3가 아닌 고속 B2B 포트인 J5에 있습니다. J3 및 J5의 전체 핀 구성은 다음 링크를 참조 하십시오. https://docs.modalai.com/voxl2-connectors/

We would like to use UART7 on J3 and UART13 on J5 to communicate with an STM32F103. Are these UART interfaces enabled by default, or is any additional hardware or software configuration required?