5G intelligent camera developed based on ARM platform

Abstract

The utility model relates to the technical field of 5G intelligent cameras, and discloses a 5G intelligent camera developed based on an ARM platform, the 5G intelligent camera comprises a mainboard, a carrier plate and a lamp panel, the mainboard comprises an ubuntu ARM Quard A55, and the ubuntu ARM Quard A55 is connected with an eMMC DATAO-DATA7 16GB through an eMMC 5.1 HS400. According to the 5G intelligent camera developed on the basis of the ARM platform, USB3.0 high-speed data transmission, gigabit network high-speed data transmission and 4G / 5G communication wireless transmission can be applied to the industrial camera for the first time, and the intelligent industrial camera with the computing power capable of achieving local computing can support a C-port lens and an M12 lens and meanwhile support a lamp source of the camera.

Description

Technical Field

[0001] The utility model relates to the technical field of 5G smart cameras, and in particular to a 5G smart camera developed based on an ARM platform. Background Art

[0002] A 5G smart camera is a smart camera that transmits data using 5G wireless communication technology. Compared with traditional cameras or smart cameras (which usually use Wi-Fi or wired network connections), 5G smart cameras can use the high speed, low latency and large number of connections provided by 5G networks to perform more efficient video transmission and data processing.

[0003] 5G is the abbreviation of the fifth generation of mobile communication technology (5th Generation Wireless Systems), which represents the latest progress in wireless communication technology. 5G aims to provide higher data speeds, lower latency, higher system capacity and a larger number of device connections than 4G. However, compared with 4G technology, 5G technology is not mature enough on many devices, especially in the field of smart cameras. At present, most of them still use 4G technology to transmit information. Even if there are a few smart cameras based on 5G technology, the technology is not mature enough and needs to be improved in data transmission and image processing.

[0004] Therefore, the utility model provides a 5G smart camera developed based on the ARM platform to solve the problems raised in the above background technology. Utility Model Content

[0005] The purpose of the utility model is to solve the shortcomings of the prior art and propose a 5G smart camera developed based on the ARM platform. The 5G smart camera developed based on the ARM platform can realize USB3.0 high-speed data transmission, Gigabit network high-speed data transmission, and 4G / 5G communication wireless transmission for the first time in industrial cameras. It is an intelligent industrial camera with local computing power, which can support C-mount lenses, M12 lenses, and support the camera's own light source.

[0006] In order to achieve the above purpose, the utility model provides the following technical solutions:

[0007] A 5G smart camera developed based on the ARM platform, comprising a mainboard, a carrier board and a light board, characterized in that: the mainboard comprises an ubuntu ARM Quard A55, the ubuntu ARM Quard A55 is connected to an eMMCDATAO-DATA7 16GB via an eMMC 5.1HS400, the ubuntu ARM Quard A55 is connected to an LPDDR4 32bit 2GB via DDR_CH0 / 1_32bit, and the ubuntu ARM Quard A55 is connected to an EEPROM 24C02 via I2C;

[0008] The ubuntu ARM Quard A55 is connected to KEYx3 via GPIO, ADC, the ubuntu ARM QuardA55 is connected to Debug UART2 via UART2_TX / RX, the ubuntu ARM Quard A55 is connected to PMIC RK809-5, the PMIC RK809-5 is connected to DCDC, the DCDC is connected to BTB Connect No. 1, and the ubuntu ARMQuard A55 is connected to BTB Connect No. 1 via MDI, USB3.O, HDMI, UART, PWM, and GPIO;

[0009] The ubuntu ARM Quard A55 is connected to a MIPI Camera via a 4Lane MIPI CSI, the ubuntu ARM Quard A55 is connected to a DVP Camera via a DVP 16Bit, and the ubuntu ARM Quard A55 is connected to an RTC / Cell via an I2C and a GPIO;

[0010] The carrier board includes a No. 2 BTB Connect, the No. 2 BTB Connect is connected to RJ451000Gbs via MDI, the No. 2 BTB Connect is connected to HDMI Type-A via HDMI, the No. 2 BTB Connect is connected to 5G M.2Connect via USB3.0 and GPIO, and the 5G M.2Connect is connected to Nano SIM Card 5G.

[0011] Furthermore, the ubuntu ARM Quard A55 is connected to USB3.0Type-B via USB2.0 OTG+USB3.0.

[0012] Furthermore, the ubuntu ARM Quard A55 is connected to a USB2.0 Type-A via USB2.0.

[0013] Furthermore, the ubuntu ARM Quard A55 is connected to LEDx4.

[0014] Furthermore, the carrier board and the light board are both provided with PWM and GPIO, and the carrier board and the light board are connected via two PWM and GPIO.

[0015] Furthermore, the No. 2 BTB Connect of the carrier board is bidirectionally connected to the No. 1 BTB Connect of the main board, and is also connected via SV.

[0016] Furthermore, the second BTB Connect is connected to a DCDC, and the DCDC is connected to a POE 12V / 2A and M12RS232, DI, and DO.

[0017] The utility model has the following beneficial effects:

[0018] The utility model proposes a 5G smart camera developed based on the ARM platform. The utility model can realize high-speed data transmission of the device USB3.0 5G bandwidth, transmit image data through the UVC protocol, and the transmission interface is the device end. The self-developed GIGE VISION protocol is used to transmit image data on the gigabit network port device end, with a maximum bandwidth of 1G. It is the first time that 4G / 5G communication is applied to the field of industrial camera products. The application technology inserts the 4G / 5G module into the motherboard end through the PCIE interface. Wireless transmission is more convenient for application in industrial scenarios where line deployment is difficult. The ARM platform with computing power is selected as the main chip of the smart industrial camera, so that the image algorithm can run locally on the camera, effectively solving the problems of delay and network bandwidth. The chip itself has an ISP function and can process image effects well. The camera supports multiple version changes: a, wired transmission C-mount lens; b, wired transmission M12 lens camera with built-in light source; c, wireless transmission C-mount lens; d, wireless transmission M12 lens camera with built-in light source. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] Figure 1 This is a hardware technology block diagram of the utility model. DETAILED DESCRIPTION

[0020] The following will be combined with the drawings in the embodiments of the utility model to clearly and completely describe the technical solutions in the embodiments of the utility model. Obviously, the described embodiments are only part of the embodiments of the utility model, not all of the embodiments. Based on the embodiments in the utility model, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the utility model.

[0021] Example

[0022] Reference Figure 1 , the utility model provides an embodiment: a 5G smart camera developed based on the ARM platform, including a main board, a carrier board and a light board, the main board includes ubuntu ARM Quard A55, ubuntu ARM Quard A55 is connected to eMMC DATAO-DATA7 16GB through eMMC5.1HS400, ubuntu ARM Quard A55 is connected to LPDDR4 32bit 2GB through DDR_CH0 / 1_32bit, and ubuntu ARM Quard A55 is connected to EEPROM 24C02 through I2C;

[0023] ubuntu ARM Quard A55 is connected to KEYx3 via GPIO,ADC, ubuntu ARM Quard A55 is connected to Debug UART2 via UART2_TX / RX, ubuntu ARM Quard A55 is connected to PMIC RK809-5, PMICRK809-5 is connected to DCDC, DCDC is connected to No. 1 BTB Connect, ubuntu ARM Quard A55 is connected to No. 1 BTB Connect via MDI, USB3.O, HDMI, UART, PWM, GPIO;

[0024] ubuntu ARM Quard A55 is connected to MIPI Camera via 4Lane MIPI CSI, ubuntu ARMQuard A55 is connected to DVP Camera via DVP 16Bit, ubuntu ARM Quard A55 is connected to RTC / Cell via I2C and GPIO;

[0025] The carrier board includes BTB Connect No. 2, which is connected to RJ45 1000Gbs via MDI, BTB Connect No. 2 is connected to HDMI Type-A via HDMI, BTB Connect No. 2 is connected to 5GM.2Connect via USB3.0 and GPIO, and 5GM.2Connect is connected to Nano SIM Card 5G.

[0026] ubuntu ARM Quard A55 is connected to USB3.0Type-B via USB2.0 OTG+USB3.0, ubuntuARM Quard A55 is connected to USB2.0 Type-A via USB2.0, ubuntu ARM Quard A55 is connected to LEDx4, both the carrier board and the light board are equipped with PWM and GPIO, and the carrier board and the light board are connected through two PWM and GPIO, the No. 2 BTBConnect of the carrier board is bidirectionally connected to the No. 1 BTB Connect of the motherboard, and is also connected through SV, the No. 2 BTB Connect is connected to DCDC, and the DCDC is connected to POE 12V / 2A and M12RS232, DI, and DO.

[0027] Based on the invented system architecture, the details are as follows:

[0028] ubuntu ARM Quard A55 refers to the Ubuntu operating system running on devices equipped with the Cortex-A55 processor in the ARM architecture.

[0029] Ubuntu: is an open source operating system based on Debian, which is commonly used on personal computers, servers and recently also supports running on some ARM devices.

[0030] ARM: stands for Advanced RISC Machine, a microprocessor architecture originally developed by ARM Holdings and widely used in mobile devices and embedded systems.

[0031] A55 or Cortex-A55: It is a processor core designed by ARM for the mid-range market and belongs to the Cortex-A series. Compared with its predecessor Cortex-A53, it provides higher energy efficiency and performance.

[0032] Quad: refers to a quad-core processor, which in this case means this ARM Cortex-A55 processor has four cores.

[0033] Ubuntu ARM Quad A55 refers to the Ubuntu operating system installed on a device equipped with a quad-core ARM Cortex-A55 processor. This type of device may be an embedded system with ARM processing power, such as a tablet such as Raspberry Pi, or other mobile or desktop devices that support ARM architecture.

[0034] eMMC 5.1HS400

[0035] eMMC 5.1HS400 is a specific type of embedded MultiMediaCard specification version, as well as the name of a high-speed interface mode it supports. The following is an explanation of the components:

[0036] eMMC: eMMC is the abbreviation of "Embedded MultiMediaCard", which is a form of storage device widely used in many mobile devices and consumer electronics, such as smartphones, tablets, navigation systems and digital cameras. eMMC devices integrate NAND flash memory and controller in a small package to provide a compact and efficient internal storage solution.

[0037] 5.1: This represents the version number of eMMC. Each new version of eMMC brings improvements, including but not limited to higher data transfer speeds and improved features. For eMMC 5.1, compared with its predecessors (such as eMMC 5.0), it adds some new features, including support for Command Queuing and Safe Delete functions, as well as improved data transfer efficiency.

[0038] HS400: This is one of the interface modes supported in the eMMC 5.1 specification, and "HS" stands for High Speed. The eMMC interface in HS400 mode is capable of data transfer rates of up to 400MB / s (megabytes per second). This is achieved by using a higher signal frequency and bilateral transmission technology - data is transmitted on both the rising and falling edges of the clock signal.

[0039] Therefore, eMMC 5.1HS400 refers to embedded storage solutions that support transfer rates up to 400MB / s and comply with the eMMC 5.1 specification. This type of storage is often used in devices that require both compactness and high data read and write speeds.

[0040] eMMC DATAO-DATA7 16GB is a 16GB capacity eMMC memory component, and DATA0 to DATA7 are mentioned, which represent the eight data lines of the eMMC device. eMMC devices usually communicate with host devices (such as smartphones or tablets) through a set of interfaces with multiple data lines. Multiple data lines can increase data transfer rates because they allow multiple bits of data to be transmitted in parallel.

[0041] To be more specific, when the eMMC storage communicates with the host device, it uses these eight data lines as transmission channels to provide higher data transmission bandwidth. For example, if the eMMC memory follows the eMMC 5.0 standard or higher, then these eight data lines can support up to 400MB / s data transmission speed (High-Speed ​​200MHz, 8-bit DDR mode). 16GB refers to the total storage capacity of the eMMC memory.

[0042] In summary, "ubuntu ARM Quad A55 connected to eMMC DATA0-DATA7 16GB via eMMC 5.1HS400" is a system based on a quad-core ARM Cortex-A55 CPU with the Ubuntu operating system, which is connected to a 16GB eMMC storage via the HS400 mode of the eMMC 5.1 interface, which has 8 data lines for data transfer.

[0043] DDR_CH0 / 1_32bit connected to LPDDR4 32bit 2GB describes a specific memory configuration, which includes the use of two channels (Channel 0 and Channel 1) for connection and access to LPDDR4 type DRAM memory. The detailed description is:

[0044] DDR: Refers to Double Data Rate, which is a memory technology that can transfer data twice on each clock signal. Usually, the term DDR is used with one or more generations of DRAM technology (such as DDR2, DDR3, DDR4) to indicate the standard of memory.

[0045] CH0 / 1: This indicates that the system has two independent memory channels, Channel 0 and Channel 1. Dual-channel addressing can improve processing performance because two memory modules can be accessed simultaneously.

[0046] 32bit: This means that the data bus width of each memory channel is 32 bits. The memory bus width is the size of the data that can be transferred between the memory controller and the memory module. A 32-bit data bus can transfer 32 bits of data in each clock cycle.

[0047] Connect LPDDR4: This refers to the type of memory connected is LPDDR4, a memory standard designed for mobile devices such as smartphones and tablets. LPDDR4 (Low Power Double Data Rate 4) memory can provide higher data transfer rates while significantly reducing power consumption than previous versions.

[0048] 32bit 2GB: This means that each memory module has a 2GB (Gigabyte) capacity and the memory interface width is 32 bits.

[0049] Putting this information together, an ARM-based Ubuntu operating system with four Cortex-A55 processor cores connected to 2GB of LPDDR4 memory via two channels of a 32-bit data bus, each of which is configured to efficiently manage memory operations, can be expected to show good performance and power consumption ratio under low to medium loads. Such a configuration can provide good performance in multitasking and high-demand memory operations, and can balance power efficiency and be used cautiously in mobile devices where battery life is a concern.

[0050] Connecting EEPROM 24C02 via I2C: I2C (Inter-Integrated Circuit) is a serial communication bus that allows two-wire communication (one communication signal line SCL and one data signal line SDA) between connecting low-speed peripheral devices and a microcontroller (or processor).

[0051] EEPROM (Electrically Erasable Programmable Read-Only Memory) is a non-volatile memory that can be used to store a small amount of data. It can retain data even when the power is turned off and allows the data to be erased and written multiple times.

[0052] 24C02 refers to a specific EEPROM chip model, which has a storage capacity of 256 bytes (2,048 bits). '24C' often represents the EEPROM series, while the '02' at the end indicates the capacity of the chip (in this case, 2048 bits, or 2k bits).

[0053] Putting this information together, "Ubuntu ARM Quad A55 connected to EEPROM 24C02 via I2C" describes an Ubuntu system running on a device based on an ARM Cortex-A55 quad-core processor, which is connected to a 2KB EEPROM (model 24C02) via the I2C bus. This type of memory is often used to store very small but important data such as configuration parameters, device identification, and version information. Connecting such EEPROM modules is common in system designs because they provide a simple way for devices to persist critical information.

[0054] USB2.0 OTG: USB OTG (On-The-Go) is a supplement to the USB specification that enables devices to switch to host mode, allowing connections to communicate directly between USB ports without going through a computer as an intermediary. Here, 2.0 refers to the version of the USB specification, the second generation of USB, which has a slower data transfer speed of up to 480Mbps compared to newer standards such as USB 3.x.

[0055] USB3.0: This is a specification of high-speed USB interface. Compared with USB2.0, the maximum transfer rate of USB3.0 standard (also known as SuperSpeed ​​USB) can reach 5Gbps. It provides faster data transfer speed and better power management.

[0056] USB3.0 Type-B: USB Type-B usually refers to a type of USB connector connected to a printer or external hard disk device. The USB3.0 version of the Type-B connector has additional pins to support the higher speeds of USB3.0, and is slightly different in appearance from the USB2.0 Type-B to maintain backward compatibility (although the speed will drop to the USB 2.0 standard).

[0057] Combining the above points, "Ubuntu ARM Quad A55 connects to USB3.0 Type-B via USB2.0 OTG + USB3.0" indicates that the system is running in an Ubuntu environment with a quad-core ARM Cortex-A55 processor that supports connecting devices via one USB2.0 OTG port (possibly for bumping or expansion functions) and at least one USB3.0 port. If the referenced device has a USB3.0 Type-B port, this indicates that the device can be connected to the ARM device via a standard USB3.0 Type-B to Type-A or Type-B to Micro-B / Type-C data cable, and can take advantage of the high-speed data transfer provided by USB3.0. In actual configuration, make sure to use cables and interfaces that support USB3.0 speeds to get the fastest speed.

[0058] USB 2.0: This is a data transfer standard with a maximum transfer speed of 480Mbps.

[0059] Type-A: USB Type-A is one of the most common USB interface shapes and is often used to connect standard peripherals such as mice, keyboards, and data storage disks. A device connected via USB 2.0 to a peripheral using a USB 2.0 Type-A interface means that the connection will transfer data at the speed standard of USB 2.0.

[0060] In practice, you can plug peripherals into the USB 2.0 ports on an Ubuntu ARM device. Once the operating system recognizes the connected peripheral, it can interact with it through the driver, such as transferring files, sending print jobs, or other input / output tasks. In general, it means that the quad-core Cortex-A55 CPU based on the ARM architecture is running the Ubuntu operating system, and the device is connected to a peripheral using a USB 2.0 Type-A connector through the USB 2.0 interface.

[0061] The ARM-based Quad A55 system (running the Ubuntu operating system) is equipped with four LED lights (LEDx4). Such a configuration is often used to indicate status, display messages, send signals, or any scenario that requires visual feedback.

[0062] LEDs (Light Emitting Diodes) are a type of light source commonly used in electronic devices because they take up little space, consume little power, and have a long lifespan. In systems, LEDs are often used as indicator lights to show power status, processor activity, and network transmissions. For example, one LED may indicate that a device is powered on (usually a green or blue LED), while another may indicate hard drive activity (usually a yellow or red LED).

[0063] These four LEDs can be connected to the ARM Cortex-A55 CPU in a number of ways:

[0064] Directly connected to GPIO: A common way is to connect the LED directly to the general-purpose input and output port (GPIO). In this case, the CPU can control the LED on and off by controlling the voltage on the GPIO port.

[0065] Via I / O expander or controller: If the number of GPIO ports is insufficient or more complex control is required, the LEDs may be connected to the CPU via an I / O expander or dedicated LED controller.

[0066] Control via software: Once the LEDs are connected to the ARM device, they can be controlled by writing scripts or using existing software tools. On Ubuntu, this may involve tools such as gpio, or directly manipulating files in the / sys / class / gpio or / sys / class / leds special folders in the Linux kernel.

[0067] For example, to control an LED on a GPIO port via a simple bash script, we would do the following:

[0068]

[0069] Before writing such a script, you need to make sure you have the correct permissions to operate the GPIO and know which GPIO port each LED is connected to.

[0070] The Ubuntu system based on the ARM Cortex-A55 processor needs to connect three keys (KEYx3) through the GPIO (General-purpose input / output) and ADC (Analog-to-Digital Converter) interfaces. You need to follow the steps below to set it up:

[0071] Physical Connection:

[0072] For GPIO: The button needs to be connected to the corresponding GPIO pin on the processor. Usually, one pin is connected to one side of the button and the other side is connected to the common ground (GND). When the button is pressed, the ground (low level) is detected by the GPIO pin; when the button is released, the pin may be kept high by an internal or external pull-up resistor.

[0073] For ADC: If the button is connected to an analog signal (for example, it may be a pressure change), you need to connect it to an ADC pin. The ADC is used to convert the analog signal of the button into a digital signal that can be read by the processor.

[0074] Configure GPIO:

[0075] The Linux kernel exports the GPIO interface for control, which is similar to the above-mentioned control of the LED through the / sys / class / gpio / folder.

[0076] Configure the GPIO pin as input mode and set appropriate pull-up / pull-down resistors according to the actual circuit conditions.

[0077] Configure ADC:

[0078] The configuration of the ADC can be more complex and usually requires loading or writing an appropriate driver to read the value of the ADC pin. Many modern ARM SoCs provide a certain number of ADC pins that can be used through specific device tree configuration or directly through the kernel interface.

[0079] Reading ADC values ​​usually involves reading a specific device file, say / sys / bus / iio / devices / iio:device0 / in_voltage0_raw, where in_voltage0_raw represents an actual ADC input.

[0080] Software Programming:

[0081] Write a program or script to monitor the state changes of GPIO or ADC pins. For GPIO, it may be to detect the change of voltage level; for ADC, it may be to detect the change of value.

[0082] The corresponding functions are implemented according to the operating logic of the buttons, such as starting programs, issuing commands, and changing settings.

[0083] Debouncing:

[0084] Keys often vibrate during physical operation, resulting in multiple rapid level changes.

[0085] Debounce is implemented in software, usually by briefly ignoring the next change in level for a period of time.

[0086] Here is a simple script example showing how to read the state of a button connected to a GPIO (excluding the debounce logic):

[0087]

[0088]

[0089]

[0090] The actual paths and file names for ADC and GPIO can vary depending on the hardware platform. Before you start writing code and physical wiring.

[0091] Connecting a debug interface (Debug UART2) through UART2 (Universal Asynchronous Receiver / Transmitter) on the ARM Cortex-A55 platform in Ubuntu is to make serial output for debugging purposes or as console output. UART is a widely used, simple, asynchronous, serial communication protocol.

[0092] To achieve this, the following steps are required:

[0093] 1. Hardware connection:

[0094] Connect TX (Transmit): The UART2_TX pin on the A55 platform needs to be connected to the RX pin of an external device (such as a USB-to-serial adapter or another UART device).

[0095] Connect RX (receive): The UART2_RX pin on the A55 platform needs to be connected to the TX pin of the external device.

[0096] This allows full-duplex communication, where both sending and receiving occur simultaneously between two devices.

[0097] 2. Make sure UART2 is enabled:

[0098] Depending on your hardware, make sure the relevant device tree files (Device Tree) or BIOS / UEFI configurations are correctly set up to make the UART2 port available.

[0099] In Ubuntu, you need to confirm that the corresponding serial port device file (such as / dev / ttyS1, where 1 is an example port number) exists and has the correct permissions.

[0100] 3. Set UART communication parameters:

[0101] Use command line tools such as stty to configure the serial port communication parameters of UART2, including baud rate, parity, data bits, and stop bits. For example, to set the baud rate to 115200:

[0102] stty -F / dev / ttyS1 115200

[0103] Here / dev / ttyS1 should be replaced with the corresponding UART port file in the actual system.

[0104] 4. Use the debugging terminal software:

[0105] On another computer or device, use debugging terminal software (such as minicom, PuTTY, screen) to connect to the UART port.

[0106] Configure the software to use the same communication parameters as in step 3 to ensure correctness.

[0107] 5. Test the connection:

[0108] Send some test data to see if you can correctly send and receive data through UART2. If you can, it means that the DebugUART2 connection settings are correct.

[0109] For example, you can run the following command in a terminal on an Ubuntu system to output some information through the UART:

[0110] echo "Hello,Debug UART2!"> / dev / ttyS1.

[0111] The sent information should be visible in the debugging terminal software on the other side.

[0112] Before starting, it is important to confirm that the UART port number and settings are correct. The UART port assignments may be different on different hardware platforms. For example, UART2 may be / dev / ttyS1 on one hardware system and / dev / ttyAMA1 on another system.

[0113] Connecting an ARM Cortex-A55 processor-based development board (such as a board based on the RK3399 SoC) to the PMIC (Power Management Integrated Circuit) RK809-5, DCDC (Direct Current to DirectCurrent) converter, and BTB (Board-to-Board) connector involves hardware design and interface configuration. RK809-5 is a power management integrated circuit commonly used in Rockchip SoCs (such as RK3399).

[0114] Understand the role of components:

[0115] PMIC (RK809-5): Provides stable voltage and current to SoC and other onboard components, usually including multiple DCDC converters, low dropout linear regulators (LDOs), charging controllers and other functions.

[0116] DCDC: Provides high-efficiency power conversion at different voltage levels. It can be onboard or inside the PMIC.

[0117] BTB Connect: This is a board-to-board connector that allows the transfer of signals and / or power from one circuit board to another.

[0118] Hardware Connection:

[0119] According to the data sheet and reference design diagram of RK809-5, it needs to be connected to the appropriate pins of the ARM Cortex-A55 processor board.

[0120] Connect the PMIC:

[0121] The input power supply is connected to the input of the PMIC.

[0122] The power pins of the ARM Cortex-A55 are connected to the corresponding outputs of the PMIC (e.g., core voltage, I / O voltage, memory supply).

[0123] Connect DCDC:

[0124] If DCDC is not provided internally by the PMIC, it may be necessary to source power from the PMIC output to a separate DCDC converter.

[0125] The output from the DCDC is then directed to different subsystems or components, such as BTB Connect, to provide the required power.

[0126] Connect to BTB Connect:

[0127] Ensure that the output voltage and current of the DCDC converter meet the requirements of the subsystem to which the connected BTB Connect is connected. Consult the specifications of the subsystem components and the BTB Connector to ensure compatibility.

[0128] Software Configuration:

[0129] Make sure the OS (Ubuntu) has the appropriate power management drivers for communicating with and controlling the PMIC.

[0130] For Rockchip platforms, you may need power management drivers provided by Rockchip, which must be integrated with the Linux kernel to manage power allocation and respond to power-related events.

[0131] Measure the power demands of the operating system on the processor, memory, and peripherals and ensure the PMIC is configured to meet those requirements.

[0132] Debug and Verify:

[0133] Perform a checklist before powering up to ensure all connections are correct as per the specifications of the PMIC and other components.

[0134] Use a multimeter and oscilloscope equipment to check that the output voltage and current are as expected to ensure that the connections between the boards are stable.

[0135] Monitor the system boot process to see if there are any power management related error logs and adjust the PMIC configuration or driver settings to correct these issues.

[0136] When connecting Ubuntu ARM Cortex-A55 devices with BTB (Board-to-Board) Connect through various interfaces, it means ensuring the correct configuration and required physical connections of the mainboard and expansion board. Whether it is MDI (Medium Dependent Interface), USB 3.0, HDMI, UART, PWM (Pulse Width Modulation), or GPIO (General Purpose Input / Output), they are all specific communication or control interfaces that need to be designed and implemented in combination with specific hardware platforms.

[0137] The general steps are as follows:

[0138] Hardware Hookup

[0139] MDI (Medium Dependent Interface):

[0140] It is the physical layer interface of Ethernet.

[0141] An appropriate RJ45 connector or other Ethernet transmission medium is required to connect the A55 system board to another board.

[0142] USB 3.0:

[0143] Directly connect the USB 3.0 port of the ARM Cortex-A55 development board to the corresponding USB port of the BTB Connect.

[0144] To complete the physical connection, a USB 3.0 cable is required.

[0145] HDMI:

[0146] Use a standard HDMI cable to connect the HDMI output of the development board to the HDMI input of the BTB Connect.

[0147] UART:

[0148] Typically used for debugging or simple serial communications.

[0149] The UART pins (TX, RX, (optional) RTS, CTS) need to be connected to the corresponding UART pins of the other board, possibly using appropriate level shifters.

[0150] PWM (Pulse Width Modulation):

[0151] PWM signals are used to control, for example, LED brightness or motor speed.

[0152] Connect the PWM output to the corresponding input of BTB Connect to ensure it can control the designated device.

[0153] GPIO (General Purpose Input / Output):

[0154] The GPIOs can be used for various control and monitoring purposes.

[0155] Connect the GPIO to the BTB Connect in the correct way according to the required functionality.

[0156] Software Configuration

[0157] For software configuration, these interfaces are usually directly supported by the driver in the ARM Cortex-A55 core, and these hardware can be controlled through the relevant system interfaces in the Ubuntu operating system.

[0158] Testing and debugging

[0159] Once the hardware is connected and the driver is installed correctly, you can test the working status of these interfaces separately in the Ubuntu environment.

[0160] Test USB 3.0: Use the lsusb command to check device recognition and perform a file transfer test.

[0161] Test HDMI: Connect a monitor and test if the image is output correctly.

[0162] Test UART: Use screen and minicom tools to test whether serial communication is normal.

[0163] Testing PWM: Write a simple program to vary the duty cycle of a PWM signal and check if the connected device responds to the change.

[0164] Testing GPIO: Use the sysfs GPIO system or the gpio-tools package to test the GPIO pins.

[0165] These checks ensure that the software can communicate with the external device through the appropriate interfaces. This can also help diagnose any potential hardware connection problems.

[0166] MIPI CSI (Mobile Industry Processor Interface Camera Serial Interface) is a high-speed serial interface commonly used in mobile devices, which allows camera modules to transfer data with the main processor or image signal processors (ISPs). When using 4-lane MIPI CSI to connect a MIPI camera on an ARM Cortex-A55 architecture development board, you need to pay attention to the following steps:

[0167] Hardware Connection:

[0168] Camera module: Make sure the selected MIPI camera module supports the 4-lane MIPI CSI interface and is compatible with your ARMCortex-A55 development board.

[0169] Interface physical connection: Use appropriate cables and / or connectors to connect the CSI interface of the MIPI camera to the MIPI CSI interface provided on the ARMCortex-A55 development board. Be careful when connecting because the high-speed signal lines are very sensitive.

[0170] Power supply: Make sure the MIPI camera module is properly powered. This includes the usual power lines (such as 3.3V and 1.8V) and ground, as well as I / O power that may be required.

[0171] Software Configuration:

[0172] Device tree configuration: Modify the device tree file on the development board (usually a .dts or .dtb file) to include the definition and configuration information for the camera module. This may include vendor specific information, clock settings, I2C addresses, port configuration.

[0173] Camera driver: Install or write the Linux kernel driver for the MIPI camera module. The driver is responsible for initializing the camera, setting the resolution, format, and improving the underlying data transmission function.

[0174] ISP configuration: If an image signal processor is used, the ISP needs to be configured to process the data stream from the MIPI camera. On some development boards, the ISP configuration may be tightly integrated with the camera driver.

[0175] Tested and verified:

[0176] Debug and test: Check the dmesg log at system startup to confirm that the camera module is correctly recognized and initialized. Use the v4l2-ctl tool to check and set camera parameters.

[0177] Image capture: Use ffmpeg, gstreamer, or v4l2-ctl multimedia frameworks and tools to capture images or videos from a MIPI camera to verify that the data stream is working properly.

[0178] DVP (Digital Video Port) is a parallel camera interface used to connect a digital camera module to a processor or image signal processor (ISP). The DVP interface has a variety of data widths, 16-bit is a relatively high bandwidth configuration, allowing a larger data transfer rate for high-resolution or high frame rate cameras.

[0179] To connect a DVP camera to an ARM Cortex-A55 based Ubuntu system via a 16-bit DVP interface, here are some key steps:

[0180] Hardware Hookup

[0181] Ensure compatibility: Confirm that the electrical characteristics of the camera module (such as I / O levels and power consumption) match those of the ARM Cortex-A55 development board.

[0182] Physical connection: Connect the camera module to the DVP interface on the development board. This involves data lines (D0-D15), clock lines (PCLK), and synchronization signal lines (HSYNC and VSYNC), as well as possible I2C bus for camera control.

[0183] Power supply: Provide the camera with appropriate power, which may include a power line (such as 3.3V) and a ground line.

[0184] Software Configuration

[0185] Device tree configuration: Make sure the device tree file (dts) accurately describes the camera and the interface to be used. The properties of the DVP interface need to be configured, this includes data width, port mode and multiplexing settings.

[0186] Camera driver: Install or write the Linux kernel driver required for the DVP camera. This driver will be responsible for setting the camera's working mode (such as resolution, frame rate) and reading the sensor's image data.

[0187] Adjust kernel settings: You also need to recompile the kernel to support the camera module.

[0188] Testing and Verification

[0189] Kernel boot information: Check the kernel log (dmesg) when the development board boots to ensure that the camera module and DVP interface are initialized correctly.

[0190] Capture image: Use Video4Linux (v4l2) tools such as v4l2-ctl to test whether the camera can capture image data normally.

[0191] Multimedia framework: Use ffmpeg or gstreamer to capture video streams and perform further verification.

[0192] Connecting RTC (Real Time Clock) and Cell (Cellular Network Module) to ARM Cortex-A55 processor based on Ubuntu system usually requires using I2C bus and GPIO (General Purpose Input Output) pins. These components are used to provide accurate time tracking and cellular network connection functions. Here are the basic steps to connect these devices through I2C and GPIO:

[0193] Connecting the RTC

[0194] Hardware Connection:

[0195] I2C: Connect the I2C lines (SDA and SCL) of the RTC module to the corresponding I2C bus interface provided by the development board.

[0196] Power Supply: Connect the required power pins of the RTC module (usually VCC and GND).

[0197] Backup Power: If the RTC module has a backup battery connection, make sure that is connected as well.

[0198] Software Configuration:

[0199] Load the I2C driver: If the I2C driver has not been loaded yet, load it through the modprobe command.

[0200] Device tree modification: You may need to modify the device tree (.dts file) to add the I2C address and clock information of the RTC module.

[0201] Synchronize time: Install NTP or other time synchronization software to ensure that the RTC can be synchronized with the network time server when the system starts.

[0202] test:

[0203] Use the i2cdetect command to detect devices on the I2C bus.

[0204] Use the hwclock command to test whether the RTC module can set and read the time normally.

[0205] Connect Cell (mobile network module)

[0206] Hardware Connection:

[0207] I2C / GPIO: Connect the mobile network module's I2C or GPIO pins to the development board if supported by the module.

[0208] Power: Make sure the mobile network module is properly powered.

[0209] SIM card: Insert a SIM card to enable mobile network services.

[0210] Antenna: Connect the necessary antenna to the mobile network module to ensure signal coverage.

[0211] Software Configuration:

[0212] Serial interface: Most Cell modules provide AT command operations through serial interfaces (such as UART), so you need to make sure these interfaces are correctly configured in the Ubuntu system.

[0213] Kernel module: Load the required USB serial or other network driver modules to operate the Cell module.

[0214] Network management: Configure network management tools, such as NetworkManager or other network connection software, to manage mobile network connections.

[0215] test:

[0216] Use serial communication software such as minicom to interact with the Cell module via AT commands to confirm its functionality.

[0217] Use ifconfig, ip, or nmcli commands to view the network status and test the network connection.

[0218] Note:

[0219] Module datasheets: Be sure to read the datasheets of the RTC and Cell modules carefully, as different hardware may require different configuration steps and electrical connections.

[0220] Power Management: Ensure that power management sequences including startup, shutdown, and restart actions are handled appropriately.

[0221] Exception handling: When writing software, you must be able to properly handle exceptions when hardware problems occur.

[0222] Permissions: Depending on Ubuntu's security policy, administrator (root) permissions may be required to perform certain hardware operations.

[0223] Module drivers and firmware: Some Cell modules may require specific drivers and / or firmware files, so make sure they are installed in your Ubuntu system.

[0224] BTB (board-to-board) connectors are generally used to connect modules or daughter cards to the main carrier board. To connect to the RJ45 jack using MDI (media dependent interface) through the carrier board's BTB connector to support Gigabit Ethernet (1000Gbps usually refers to 1Gbps, i.e. 1000Mbps), follow these steps:

[0225] Hardware Design and Connectivity

[0226] BTB Specifications Confirmed:

[0227] Verify that the pinout of the BTB connector supports Ethernet transmission.

[0228] Verify that the connector meets the signal integrity requirements for 1Gbps transmission.

[0229] MDI interface:

[0230] MDI that supports Gigabit Ethernet typically requires the use of differential signal pairs to transmit data, which means at least four twisted pairs are required to support full Gigabit bandwidth.

[0231] Therefore, ensure that the BTB connector and carrier board routing can accommodate these four pairs of differential lines.

[0232] RJ45 connector and magnetic transformer:

[0233] Choose a high-quality RJ45 connector suitable for 1Gbps transmission, which should include a built-in magnetic transformer (also called a ferrite bead).

[0234] Verify that the RJ45 connector is compatible with the carrier board's BTB socket and can be connected via the defined pinouts.

[0235] Carrier board design:

[0236] The carrier board should have a physical layer device (PHY) that handles the transmission and reception of data and is connected to the BTB connector.

[0237] Check the carrier board layout design, especially the layout of differential signal pairs needs to meet the requirements of Ethernet design to reduce crosstalk and keep signal stability.

[0238] Testing and debugging:

[0239] After the hardware is built, test the Ethernet connection using network testing equipment such as a network tester or a configured switch.

[0240] Ensure the connection is capable of 1Gbps and test the network connection through a switch or a direct connection.

[0241] Software Configuration

[0242] Drivers:

[0243] On Ubuntu, make sure the Network Interface Card (NIC) driver is properly installed and loaded.

[0244] For most common network interface cards, Ubuntu automatically detects and loads the appropriate driver module.

[0245] Network Configuration:

[0246] Configure the network interface to use the correct IP settings. You can use DHCP to automatically obtain the configuration, or you can manually set a static IP address.

[0247] Make sure / etc / network / interfaces or / etc / netplan is configured correctly and the networkd or NetworkManager service is managing the network interface correctly.

[0248] Performance Testing:

[0249] Perform network performance tests, such as using iperf or netcat tools.

[0250] Check network traffic and network connection stability to ensure high-speed transmission.

[0251] Connecting to a device with an HDMI Type-A interface through the BTB Connect connector (board-to-board connector) on the carrier board requires ensuring that the hardware design, connection, and signal transmission protocols comply with the HDMI standard. The following is an overview of some of the design and implementation steps:

[0252] Hardware Design and Connectivity

[0253] Interface specification confirmation:

[0254] Check whether the pins of the carrier board's BTB connector support the bandwidth and signal type of HDMI signal transmission.

[0255] Ensure that the BTB connector is capable of transmitting high-speed video signals.

[0256] HDMI Type-A interface:

[0257] HDMI Type-A is usually a standard full-size HDMI interface that supports high-definition video and audio transmission.

[0258] Depending on the HDMI version (such as 1.4, 2.0, 2.1), different versions of HDMI support different resolutions and frame rates.

[0259] Routing and Signal Integrity:

[0260] The carrier board should be designed with appropriate differential traces to accommodate the data channels required by the HDMI interface. These channels usually include at least three pairs of differential signal lines (for video signals), as well as clock signals and other control signals.

[0261] To ensure signal quality, the differential signal pairs must have equal length and impedance matching, and appropriate shielding methods are required to reduce electromagnetic interference.

[0262] Hardware conversion interface:

[0263] Considering that the BTB connector of the carrier board may not directly support HDMI signals, it is necessary to design a hardware converter interface or use an existing adapter module.

[0264] This hardware interface should serve as a bridge between the carrier board's BTB connector and the external HDMI Type-A interface.

[0265] Tested and validated:

[0266] After the hardware is designed and built, test the connection using standard HDMI signal sources and sinks.

[0267] Ensure that video and audio transmissions are clear and stable, with no noticeable delays or dropped frames.

[0268] Software Configuration and Support

[0269] Drivers:

[0270] If the carrier board has a processor and operating system, you need to make sure it has the correct HDMI output driver.

[0271] For Linux or other Unix-like systems, this may mean configuring and compiling the appropriate kernel modules.

[0272] Display and sound configuration:

[0273] Make sure the operating system can detect the HDMI interface and is able to configure display and sound output.

[0274] In Linux, this might include modifying the / etc / X11 / xorg.conf file, configuring display settings using the xrandr command, or adjusting the settings of a sound server such as PulseAudio.

[0275] Connecting a device with 5G M.2 connectivity using USB 3.0 and GPIO (general purpose input / output) interfaces through the carrier board’s BTB (board-to-board) connector and using a Nano SIM card to connect to a 5G network requires ensuring that the following hardware and software design issues are properly addressed:

[0276] Hardware Design

[0277] BTB Connector:

[0278] Make sure the BTB connector has enough pins for USB 3.0 and GPIO connections and meets signal transmission requirements.

[0279] Verify the specifications of the BTB connector to ensure it can transmit the high-speed signals required by USB 3.0.

[0280] USB 3.0 Cabling:

[0281] Design the carrier board's USB 3.0 connections so they can connect to the corresponding USB port endpoints on the M.2 lockable expansion card.

[0282] Ensure differential signal pairing, length matching, and impedance control to reduce timing jitter and maximize high-speed data transmission quality.

[0283] GPIO Connections:

[0284] GPIO routing should take into account the control signals or interrupt signals that the M.2 module may need to use.

[0285] If power management is required, the pins should also be routed appropriately for turning the module on / off or resetting it.

[0286] M.2 Connector:

[0287] The carrier board should be designed with an M.2 slot to support the installation of an M.2 5G module.

[0288] Make sure the key type of the M.2 slot (such as M key, B key) matches the 5G M.2 module.

[0289] SIM card interface:

[0290] Designed to support the Nano SIM card slot and ensure it is properly connected with the 5G M.2 module.

[0291] The interface of a SIM card usually requires power supply, ground, data I / O and possibly a reset signal.

[0292] Power supply design:

[0293] Considering the power requirements of the 5G module, ensure sufficient power supply and have appropriate power management logic.

[0294] Testing and certification:

[0295] Test the hardware connection between the 5G module and the carrier board, including USB 3.0 function and GPIO function.

[0296] Verify that the equipment complies with local electrical safety and radio transmission standards.

[0297] Software Configuration

[0298] Drivers and Firmware:

[0299] To ensure that the USB 3.0 interface and 5G M.2 module work properly, you need to make sure the correct drivers and firmware are installed.

[0300] Download and install the driver for your operating system from the M.2 module manufacturer's official website.

[0301] 5G Network Connection:

[0302] Configure the operating system to recognize and manage 5G connections.

[0303] Use the network management tool of the operating system or follow the instructions of the 5G module provider to set up the network interface.

[0304] Connecting the BTB Connect on the carrier board to the DC-DC converter to provide power to other components (such as 12V / 2A via POE or RS232, digital input (DI) and digital output (DO) connected to the M12 interface) involves multiple hardware design and electrical integration considerations. The following are the key points to pay attention to when integrating such a system:

[0305] DC-DC Converter Selection and Integration

[0306] Voltage and current requirements:

[0307] Choose the right DC-DC converter based on the interface requirements. For example, POE (Power over Ethernet) usually requires a 48V input, but in this particular case, 12V / 2A is required.

[0308] Calculate the total power requirements and ensure that the DC-DC converter can provide at least enough current to meet the requirements under the highest load conditions.

[0309] Input voltage range:

[0310] Most POE devices will provide 44-57V DC input, but you need to make sure that the DC-DC converter can receive a voltage from the BTBConnect that is suitable for its input range.

[0311] Output stability and efficiency:

[0312] In order to ensure stable operation of the equipment, select a DC-DC converter with high efficiency and stable output.

[0313] Consider the converter's thermal management and protection functions, such as over-temperature protection and short-circuit protection.

[0314] Electrical Isolation:

[0315] If the system requires isolation to limit noise or provide user protection, make sure the DC-DC converter provides adequate isolation voltage levels.

[0316] Verification and Authentication:

[0317] Verify that the converter meets any necessary industrial or safety standards, such as UL certification, CE marking, or other relevant standards.

[0318] POE Integration

[0319] POE Standards:

[0320] Determine which POE standard is used (e.g. IEEE 802.3af, IEEE 802.3at), which affects the output voltage and current as well as the required power level.

[0321] POE Injector or Switch:

[0322] If the carrier board needs to provide POE functionality from a traditional Ethernet network, a POE injector or a network switch with POE capability will be required.

[0323] Cables and Connectors:

[0324] Use POE-compliant cables and durable M12 connectors that ensure good contact.

[0325] M12 interface design

[0326] RS232 communication:

[0327] Ensure the RS232 communications path from the BTB Connect to the M12 connector is wired appropriately.

[0328] Includes necessary signal lines (such as TX, RX, GND and possible control signals).

[0329] Digital Input / Output:

[0330] Design appropriate digital input and output circuits and provide them to external devices through the BTB Connect connector.

[0331] Includes the necessary isolation and drive circuitry to ensure signal integrity and system safety.

[0332] Based on the above detailed description, the overall description is:

[0333] The present invention is an embedded computing platform based on ARM architecture, and the processor used is Quad A55, i.e., a quad-core ARM Cortex-A55 smart camera. The main features and components of the computing platform include:

[0334] Ubuntu ARM Quad A55: This is the central processing unit (CPU) of this system, which runs the Ubuntu operating system. The "Quad" indicates that it has four processor cores, and the "A55" refers to the ARM Cortex-A55 core.

[0335] storage:

[0336] eMMC: 16GB of eMMC provides storage for the embedded multimedia card interface, using the eMMC 5.1HS400 interface, which is a high-speed storage solution.

[0337] LPDDR4 Memory: 2GB of LPDDR4 random access memory provides memory access through a 32-bit wide data channel.

[0338] I / O interfaces and peripherals:

[0339] EEPROM: The 24C02 EEPROM connected through the I2C interface can be used as the system's non-volatile memory to store important system data.

[0340] USB: There is one USB 3.0 Type-B and one USB 2.0 Type-A interface, supporting the connection of multiple USB devices.

[0341] LEDs: Four LEDs are used to display system status.

[0342] Buttons (KEYs): Three buttons connected through GPIO and ADC are used for user input.

[0343] Debug UART2: Serial communication interface used for debugging.

[0344] PMIC (RK809-5): A power management integrated circuit used to manage the power supply of the processor and other components.

[0345] Expansion and communication capabilities:

[0346] MIPI and DVP Cameras: These are the connectable camera interfaces, MIPI Camera uses MIPI CSI interface and DVP Camera uses DVP interface.

[0347] RTC / Cell: Real-time clock and possible cellular module connected via I2C and GPIO.

[0348] Interface connection: including a BTB (Board-to-Board) Connector supporting Ethernet, HDMI, UART, PWM and GPIO, which is used to connect the motherboard to other boards or components.

[0349] Carrier board:

[0350] BTB Connect No. 2: Connected with RJ45 to support 1000Mbps Ethernet, as well as HDMI Type-A and 5GM.2 interfaces, including a 5G communication module connected to the Nano SIM Card 5G device.

[0351] Power supply: Includes support for POE (Power Over Ethernet) 12V / 2A and M12 RS232, which may be used as an interface and power supply for industrial control.

[0352] PWM and GPIO: Both the carrier board and the light board contain PWM signals and GPIO pins, which are used to control hardware such as motors or lights.

[0353] Bidirectional connection: Communication between the carrier board and the main board is bidirectional, with the main board connected via BTB Connect 1 and the carrier board connected via BTB Connect 2. In addition, additional connections are made via SV (Secure Video: In smart camera applications, "SV" may be used to represent a secure or encrypted video transmission channel to ensure that video data transmitted from the camera is secure and leak-free).

[0354] Finally, it should be noted that the above is only a preferred embodiment of the present invention and is not intended to limit the present invention. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art can still modify the technical solutions described in the aforementioned embodiments or make equivalent substitutions for some of the technical features therein. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present invention should be included in the protection scope of the present invention.

Claims

1. The 5G smart camera developed based on the ARM platform includes a main board, a carrier board and a light board, and is characterized by: The motherboard includes ubuntu ARM Quard A55, the ubuntu ARM Quard A55 is connected to eMMCDATAO-DATA716GB via eMMC 5.1HS400, the ubuntu ARM Quard A55 is connected to LPDDR4 32bit2GB via DDR_CH0 / 1_32bit, and the ubuntu ARM Quard A55 is connected to EEPROM 24C02 via I2C; The ubuntu ARM Quard A55 is connected to KEYx3 via GPIO, ADC, the ubuntu ARM Quard A55 is connected to Debug UART2 via UART2_TX / RX, the ubuntu ARM Quard A55 is connected to PMIC RK809-5, the PMIC RK809-5 is connected to DCDC, the DCDC is connected to BTB Connect No. 1, the ubuntu ARM QuardA55 is connected to BTB Connect No. 1 via MDI, USB3.O, HDMI, UART, PWM, GPIO; The ubuntu ARM Quard A55 is connected to a MIPI Camera via a 4Lane MIPI CSI, the ubuntu ARM Quard A55 is connected to a DVP Camera via a DVP 16Bit, and the ubuntu ARM Quard A55 is connected to an RTC / Cell via an I2C and a GPIO; The carrier board includes a No. 2 BTB Connect, the No. 2 BTB Connect is connected to RJ45 1000Gbs via MDI, the No. 2 BTB Connect is connected to HDMI Type-A via HDMI, the No. 2 BTB Connect is connected to 5G M.2Connect via USB3.0 and GPIO, and the 5G M.2Connect is connected to Nano SIM Card 5G.

2. The 5G smart camera developed based on the ARM platform according to claim 1, characterized in that: The ubuntuARM Quard A55 is connected to USB3.0 Type-B via USB2.0 OTG+USB3.

0.

3. The 5G smart camera developed based on the ARM platform according to claim 1, characterized in that: The ubuntuARM Quard A55 is connected via USB2.0 with USB2.0 Type-A.

4. The 5G smart camera developed based on the ARM platform according to claim 1, characterized in that: The ubuntuARM Quard A55 is connected with LEDx4.

5. The 5G smart camera developed based on the ARM platform according to claim 1, characterized in that: The carrier board and the light board are both provided with PWM and GPIO, and the carrier board and the light board are connected via two PWM and GPIO.

6. The 5G smart camera developed based on the ARM platform according to claim 1, characterized in that: The No. 2 BTB Connect of the carrier board is bidirectionally connected to the No. 1 BTB Connect of the main board, and is also connected via SV.

7. The 5G smart camera developed based on the ARM platform according to claim 1, characterized in that: The second BTBConnect is connected to DCDC, and the DCDC is connected to POE 12V / 2A and M12 RS232, DI, and DO.

Images