#System On Module

[tootimetraveltimemachine]

OpenCV Porting on T507 Platform with Linux 4.19: A Deep Comparison Between Standalone Compilation and Buildroot Compilation

OpenCV is an open-source computer vision library that provides a rich set of image processing and computer vision algorithms, supporting multi-platform development. It can be used for various computer vision tasks such as image and video processing, feature extraction, object detection, image segmentation, pose estimation, and object recognition. There are two methods for porting OpenCV: standalone compilation and Buildroot compilation.

Standalone Compilation of OpenCV

Standalone compilation requires CMake, a cross-platform build system similar to the commonly used ./configure. Once configured, it generates a CMakeLists.txt file that defines the project's build rules.

1. Install CMake

2. Configuration

First, extract opencv-2.4.13.7.tar.gz, enter its directory, and run cmake-gui to open the configuration interface.

(1)Set the source code path and build output path (the output path must be created in advance);

(2)Click Configure and select Unix platform cross-compilation mode;

(3)Configure compiler settings.

(4)Configure compiler settings after configuration.

Enable TIFF support.

Disable CUDA (Compiling with CUDA fails; CUDA is for NVIDIA GPUs, which are not available on T507, so disabling it has no impact).

Select Grouped to configure the installation path in cmake.

Cancel GTK

Reconfigure and generate the build files.

3. Compilation

Before compiling, modify the CMakeLists.txt file to configure linker rules:

The goal is to configure the rules for the connector,

-lpthread: Links the libpthread.so library, which provides multithreading support

-lrt: links the librt.so library, which provides real-time extension-related functions

-lrt: links the librt.so library, which provides real-time extension-related functions

make compilation

4. Installation and Deployment

The installation path needs to be cleared before installation.

make install.

Generated test program.

Generated library.

There is also a part of the build path.

Package the above content and release it to the file system of the board.

5. Test

The program can be called to the library to run normally.

However, there are still some errors in the application processing.

Build root compile opencv

1. Enter the Graphical Interface

2. Select Compilation Parameters

Select opencv3 in the following path

Tick all the parameter items.

3. Save the .config file.

Go to the output path of the source package/OKT507-linux-sdk/out/t507/okt507/longan/buildroot，

Change the existing target file to any name and create a new target file

4. Standalone Compilation

Networking is required for the compilation process

Buildroot outputs the standalone compiled content to the previously created **target** directory. The contents can then be packaged and deployed to the **filesystem**.

5. Test

ZD-Atom provides an OpenCV Qt test program based on **i.MX6UL**, where the **.pro** file defines the application's dependencies.

These libraries are available in the files generated by the compilation.

Both methods have their pros and cons:

Standalone Compilation: Allows trying different source versions and offers more flexible parameter configuration, but the process is complex.

Buildroot Compilation: Enables easy deployment by simply extracting the generated files, but switching versions is inconvenient.

[chemical-processes]

I want a fic where murderbot has to act human around another Secunit who's 10000% convinced that it's human and needs immediate rescue

[forlinx]

Forlinx Officially Launches RISC-V SoM Based on StarFive JH7110!

Forlinx has officially launched their latest System-on-Module, featuring the powerful StarFive JH7110 RISC-V chip. These versatile SoM and compatible carrier board are now available for order, catering to a wide range of applications including commercial, medical, and industrial automation.

Recently, a few embedded products have emerged utilizing the same processor, including the VisionFive 2, Pine64, and Milk-V Mars. However, the FET7110 SoM will be the first product from Forlinx to feature the integrated Jinghong 7110 processor. See the JH7110 block diagram for reference.

• JH7110 – 64-bit RISC-V, up to 1.5GHz (quad SiFive U74-RV64GC, up to 5.09 CoreMark/MHz)

JH7110 block diagram

The JH7110’s GPU integrates the IMG BXE-4-32 MC1 (up to 600MHz) which offers full support for mainstream APIs like OpenCL 3.0, OpenGL ES 3.2, and Vulkan 1.2.

Regarding power consumption, Forlinx indicates that the JH7110 is segmented into eight independently switchable power domains. Additionally, the CPU frequency can be dynamically adjusted via software, allowing customers to fine-tune the frequency based on various application scenarios that require flexible control and power consumption.

The JH7110 facilitates camera access through both MIPI-CSI and DVP interfaces, with ISP support. It enables video decoding capabilities of up to 4K@60fps and video encoding of 1080p@30fps. Moreover, the SoM supports HDMI (4K@30fps) and RGB (1080p@30fps) display output interfaces, along with MIPI-DSI (2K@30fps).

Specifications listed for the FET7110-C SoM include:

• Memory/Storage:

￮ 2/4GB LPDDR4 RAM

￮ 32GB eMMC 5.0

￮ 100 Mbps QSPI

￮ SD 3.0/MMC 5.0

• Connectivity:

￮ 2x GMAC for RMII/RGMII 10/100/1000 Mbps

• Display/Audio:

￮ 1x HDMI 2.0 (up to 4K@30fps)

￮ 1x 4-lane MIPI DSI, (up to 2K@30fps)

￮ 8-lane I2S PCM/TDM

• Camera:

￮ 1x 4-lane MIPI-CSI

• Expansion:

￮ 1x PCIe2.0x1, 2 PCIe2.0 controllers integrated w/ PHY

• USB:

￮ 1x USB 2.0

￮ 1x USB 3.0

• I/O Peripherals:

￮ 6x UART, 7x I2C, 7x SPI

￮ 1x SDIO

￮ 8x PWM

￮ 64x GPIOs

￮ 2x CAN 2.0B (Up to 5Mbps)

• Power:

￮ 5V DC

• OS:

￮ Linux 5.15.0

• Mechanical:

￮ 60 x 38mm

￮ B2B connectors (3x 80-pin)

Specifications listed for the OK7110-C development board include:

• Memory/Storage:

￮ 2/4GB  LPDDR4 RAM

￮ 32GB eMMC 5.0

￮ 100 Mbps QSPI

￮ SD 3.0/MMC 5.0

• Connectivity:

￮ 2x Gigabit Ethernet ports

• Display/Audio:

￮ 1x HDMI 2.0 port

￮ 1x MIPI DSI

￮ 2x Speakers

￮ 1x Mic

• Camera:

￮ 1x MIPI-CSI

• Expansion:

￮ 2x PCIE 2.0

￮ 1x Micro SIM

• USB:

￮ 1x USB Type-C

￮ 3x USB 3.0

• I/O Peripherals:

￮ 2x CAN

￮ 2x RS485

• Other Features:

￮ 1x Power button, 1x Reset key

￮ RTC battery

• Power:

￮ 12V DC (via barrel connector)

• Mechanical

￮ B2B connectors (3x 80-pin)

These products are now available for ordering. Customers can find the product page for the FET7110-C SoM here.

[tcfactory]

Think fast, Sentinel. That is what you are for, after all.

Today on "this is not what I planned to draw, but I think it turned out Neat": a nightmare.

Sentinel from my ongoing fanfic verse, Crossed Sparks.

This won't make much sense without the context of the fic, but I'm basically playing around with the idea of a Sentinel who was custom made for his position of the Principal Aide.

Bonus closeup because this thing is huge:

[broken-risk-assessment-module]

rip secunit 3 😔😔😔 you're not dead but you would have loved saving the lives of a whole colony of innocent humans by making a factually honest and emotionally compelling documentary 😔😔😔

[mothcpu]

i was reading dect like any ultrakill fan would but then i had a question in mind

i might be thinking too hard into it, but what would those parts be named? do they already have names? or were they randomly labled for the story?

they absolutely have names; they're all FANUC industrial machine part numbers!

[radiantmists]

so murderbot assumes that three offered its armor because it doesn't understand that the armor can belong to it and thinks mb taking the armor is just good resource allocation.

but if it assumes it doesnt have control over the armor, it would probably let whoever it sees as in charge (maybe ART?) handle it, or at least make the suggestion directly to that person. even newly freed in NE, it's willing to give its security advice (on hostage situations being undesirable) even if it doesn't expect to be taken seriously. it doesn't make sense to me that it would have so much trouble expressing the offer if it were just a security suggestion.

and then i think about how murderbot says later in the book that even if three felt fondly toward its fellow SecUnits, the govmod would prevent it from expressing that care or knowing it was returned.

so-- imagine you're three, and you havent yet internalized that you can just say "i care about you and dont want you to get hurt" to another SecUnit; but you can make sure that it has every resource it might need; you could probably do that even before the govmod was hacked.

you can't explain why, but you can hope that the gesture is explanation enough, and you can look for similar caretaking gestures in return; things like being given code and advice to do your job better, and being reassured when you express that you're finding said job difficult.

i think *murderbot* isn't aware of this language of care, because it hasnt had much opportunity to bond with other constructs. but three probably is, and probably knows how to read between the lines and guess that murderbot is starting to care about it, too.

[wintercalamity]

Ok so v1 has internal organs and enough sentience to not wanna die

[iamfuckingsorry]

"Do you know where we are going next?" I asked ART.

Y'know what, I think maybe I don't need any more Murderbot books. I think maybe ending things here is fucking perfect and as much as I love Wells's writing I'm genuinely not sure it can get better for me.

Like, so much of the books are about MB learning how to be a person, about becoming okay with being a complete individual with everything it entails. The first thing it does once it's actually allowed to decide on its own is it runs away from it all (admittedly to go on a mission to confirm some things about its past, because it genuinely just wants to be *good*). It shoves all its emotions away as much as it's able to. Then shit happens, and it makes its first friends, makes decisions based on these friendships, goes through a lot of emotionally intense situations...

And we get to this point here. MB having zero doubts about going with ART says a lot about its relationship with ART, but it also says a lot about its relationship with its humans - it knows that wherever it goes, when it comes back, the humans will still be there. Its humans actively acknowledge its struggles with being a now-free SecUnit and MB is willing to entertain the discussions to an extent and share information about its deeply personal experiences. Hell, System Collapse ends with MB admitting it might be somewhat broken, but that's okay as long as it can keep doing its job, and agreeing to basically do counselling - this is the guy what would rewatch its favourite TV show again and again in order to avoid acknowledging it even had Emotions a couple books back.

Reading this, I know that MB will be okay. It has hopes and goals and genuinely believes in itself and it has an amazing support system that its willing to lean on for the first time in its life. I'm convinced it'll go on to do great things with ART. And that's really the only thing I need to know.

[lonestarflight]

Worker installing the Aerojet AJ10-137 (Service Module Engine) on an Apollo Service Module at North American's Downey facility.

Date: March 28, 1966

SDASM Archives Casson_0023, Casson_0024

[usiglobal]

Choosing the Right IoT Module for Your Project: A Beginner’s Guide

Choosing the right IoT module is essential for a successful project. As a beginner, start by considering factors like connectivity (Wi-Fi, Bluetooth, or cellular), power consumption, range, and compatibility with other components. By aligning your project goals with module features, you’ll find an IoT module that perfectly fits your needs.

[syistoppedgivingafuck]

[forlinx]

Applications and Development of FETMX8MP-C System On Module (SoM)

FETMX8MP-C System On Module (SoM) is a type of system module based on the NXP i.MX 8M Plus processor, which is mainly used in machine learning and vision, advanced multimedia, and industrial automation. The module series has three different iMX8M processor models and can be used in applications such as smart homes, smart cities, Industry 4.0, and IoT.

The module has powerful image processing, multimedia functions, and real-time control, and can meet the needs of various applications such as high-speed networks, high-definition videos, dual-band WIFI, and high-speed industrial Ethernet.

Q&A Discussion:

Q: What are the main application areas of FETMX8MP-C System On Module (SoM)? A: FETMX8MP-C System On Module (SoM) is mainly used in machine learning and vision, advanced multimedia, and industrial automation. It can be used in applications such as smart homes, smart cities, Industry 4.0, and IoT.

Q: What are the characteristics of FETMX8MP-C System On Module (SoM)? A: FETMX8MP-C System On Module (SoM) has powerful image processing, multimedia functions, and real-time control. It uses a system module based on the NXP i.MX 8M Plus processor with strong multimedia functions, including video encoding and decoding, 3D/2D graphics acceleration, and multiple audio and voice functions.

[whirligig-girl]

What's your favorite Spacecraft, both real and fictional?

It would be impossible to choose a favorite real spacecraft but my favorite fictional spacecraft is probably the Galaxy Class USS Enterprise NCC-1701-D.

Partly because I love the TNG technical manual and partly because it's just gorgeous. Easily the best looking ship to carry the name.

Some candidates for my favorite real spacecrafts: The Space Shuttle Orbiters (Space Transportation System) (1981-2011). Truly horrendous design. Unsafe, inefficient, but unquestionably gorgeous and utterly iconic, having defined human spaceflight for at least two generations.

You may have a death toll but I can't stay mad at you...

The Apollo Lunar Modules (1969-1972). These babies have a negative death toll, being instrumental in the rescue of the Apollo 13 astronauts and being uninvolved in the Apollo 1 fire. They are also one of two unquestionably iconic U.S. government vehicles designed and built by Grumman with "L" in the name--the other is the USPS Long Life Vehicle.

Skylab. They really did just say "what if we emptied out a rocket tank and turn it into a space station." and it has the dubious honor of being the only space station with a spacious enough volume to test cold-gas EVA-jetpacks and to have a shower. All while having its sun shield and one of its solar panels torn off. It's even large enough that you can run along the outside, and the centrifugal force of your own circular motion is enough to keep you on the walls/floor.

New Horizons (launch 2006, arrival at Pluto 2015, arrival at Arrokoth 2019).

Cassini (launch 1997, arrival 2004, destroyed at end of mission 2017)

and the Voyagers (especially Voyager 2) Launch: 1977 Jupiter: 1979 Saturn: 1980 and 1981 Uranus: 1986 Neptune: 1989 Heliopause: 2012 & 2018 Current status: transmitting from Interstellar space (in terms of heliophysics. Still well within the sun's gravitational sphere of influence)

Robotic spacecrafts are the fuckin' best.

[broken-risk-assessment-module]

this system sure is collapsing, am i right?

anyway meet procedure module <3 it has like..... chill older brother energy. its design is not creative lmao

[thehumanwiki]

I wonder what would happen if the Maestro from Doctor Who, who is music incarnate, knew about microtones. Like, if they saw this—

would they explode.