User:<image>Describe the image.
Answer: This is a surreal, digitally manipulated image that blends science fiction with everyday life in an unexpected setting. Here’s a detailed description:
Main Subject:
- A person wearing a white astronaut suit reclines on what appears to be a lunar surface or spacecraft interior.
- Their legs are propped up against the edge of a green cooler box, which has faint graffiti-style writing (“SOMETHING”) visible on its side.
- In their right hand, they hold a bright green glass beer bottle — likely a craft beer — as if enjoying a drink in zero gravity.
Setting & Background:
- The environment is clearly extraterrestrial: gray, cratered terrain resembling the Moon’s surface.
- Behind the astronaut, Earth dominates the sky — its blue oceans and swirling white clouds are visible against the black void of space dotted with stars.
- To the right, part of a metallic ladder or structure leans into the frame, suggesting this might be inside a spacecraft or on a lunar module.
Atmosphere & Style:
- The lighting is dramatic — strong highlights on the astronaut’s helmet visor and suit, contrasting sharply with the dark background.
- There’s a sense of irony or absurdity: an astronaut relaxing with beer next to Earth, defying gravity and normal human behavior in space.
- The image has a hyper-realistic yet dreamlike quality, enhanced by digital effects like lens flares and atmospheric glow around Earth.
Overall Impression: It’s a humorous, thought-provoking piece that plays on the contrast between isolation in space and comfort found in mundane pleasures — drinking beer while floating above our own planet. It invites reflection on human resilience, curiosity, and the strange ways we adapt to extreme environments.
Paper: Qwen3 Technical Report
LLMs (Large Language Models) are neural networks trained on large text datasets to understand and generate language.
VLMs (Vision-Language Models) add a visual encoder so the model can process images and text together.
A combined VLM+LLM system is often referred to as a multimodal model.
These models can be large—hundreds of millions to billions of parameters—which impacts accuracy, memory use, and runtime speed.
On edge devices like the RK3588, available RAM and compute are limited, and even the NPU has strict constraints on supported operations.
Because of this, models typically need to be quantised or simplified to fit.
Performance is usually expressed in tokens (words) per second.
Once converted to RKNN, parts of the model can run on the NPU, improving speed.
Despite these limits, models like Qwen3-2B run well on the RK3588 because the NPU efficiently accelerates the heavy math, and the vision encoder can be optimised. This makes advanced multimodal AI feasible on small, power-efficient devices.
All models, with C++ examples, can be found on the Q-engineering GitHub.
All LLM models are quantized to w8a8, while the VLM vision encoders use fp16.
| model | RAM (GB)1 | llm cold sec2 | llm warm sec3 | vlm cold sec2 | vlm warm sec3 | Resolution | Tokens/s |
|---|---|---|---|---|---|---|---|
| Qwen3.5-9B | 9.2 | 97.1 | 97.1 | 11.5 | 11.5 | 448 x 448 | 3.2 |
| Qwen3.5-4B | 5.4 | 52.8 | 6.2 | 8.5 | 0.9 | 448 x 448 | 5.2 |
| Qwen3.5-2B | 2.9 | 23.9 | 3.2 | 8.5 | 0.8 | 448 x 448 | 11.0 |
| Qwen3.5-0.8B | 1.3 | 10.6 | 1.9 | 2.7 | 0.2 | 448 x 448 | 21.6 |
| Qwen3-2B | 3.1 | 21.9 | 2.6 | 10.0 | 0.9 | 448 x 448 | 11.5 |
| Qwen3-4B | 8.7 | 49.6 | 5.6 | 10.6 | 1.1 | 448 x 448 | 5.7 |
| InternVL3.5-1B | 1.9 | 8.3 | 8.0 | 1.5 | 0.8 | 448 x 448 | 24 |
| InternVL3.5-2B | 3.0 | 22 | 8.0 | 2.7 | 0.8 | 448 x 448 | 11.2 |
| InternVL3.5-4B | 5.4 | 50 | 8.0 | 5.9 | 0.8 | 448 x 448 | 5 |
| InternVL3.5-8B | 8.8 | 92 | 8.0 | 50.5 | 5.8 | 448 x 448 | 3.5 |
| Qwen2.5-3B | 4.8 | 48.3 | 4.0 | 17.9 | 1.8 | 392 x 392 | 7.0 |
| Qwen2-7B | 8.7 | 86.6 | 34.5 | 37.1 | 20.7 | 392 x 392 | 3.7 |
| Qwen2-2.2B | 3.3 | 29.1 | 2.5 | 17.1 | 1.7 | 392 x 392 | 12.5 |
| InternVL3-1B | 1.3 | 6.8 | 1.1 | 7.8 | 0.75 | 448 x 448 | 30 |
| SmolVLM2-2.2B | 3.4 | 21.2 | 2.6 | 10.5 | 0.9 | 384 x 384 | 11 |
| SmolVLM2-500M | 0.8 | 4.8 | 0.7 | 2.5 | 0.25 | 384 x 384 | 31 |
| SmolVLM2-256M | 0.5 | 1.1 | 0.4 | 2.5 | 0.25 | 384 x 384 | 54 |
1 The total used memory; LLM plus the VLM.
2 When an llm/vlm model is loaded for the first time from your disk to RAM or NPU, it is called a cold start.
The duration depends on your OS, I/O transfer rate, and memory mapping.
3 Subsequent loading (warm start) takes advantage of the already mapped data in RAM. Mostly, only a few pointers need to be restored.


To run the application, you have to:
- OpenCV 64-bit installed.
- rkllm library.
- rknn library.
- Optional: Code::Blocks. (
$ sudo apt-get install codeblocks)
Start with the usual
$ sudo apt-get update
$ sudo apt-get upgrade
$ sudo apt-get install cmake wget curl
To install OpenCV on your SBC, follow the Raspberry Pi 4 guide.
Or, when you have no intentions to program code:
$ sudo apt-get install libopencv-dev
$ git clone https://github.com/Qengineering/Qwen3-VL-2B-NPU
To run InternVL3, you need to have the rkllm-runtime library version 1.3.0 installed, as well as the rknpu driver version 0.9.8.
If you don't have these on your machine, or if you have a lower version, you need to install them.
We have provided the correct versions in the repo.
$ cd ./Qwen3-VL-2B-NPU/aarch64/library
$ sudo cp ./*.so /usr/local/lib
$ cd ../include
$ sudo cp ./*.h /usr/local/includeYour rkllm model must match the library.

If you use a model synthesized with the previous 1.2.3 rkllm library and run it with the latest 1.3.0, you will get a malfunction. The internal Byte-Pair Encoding (BPE) dictionary parsing gets misaligned.
The next step is downloading the models.
Both can be downloaded from our Hugging Face page.
- qwen3.5-2b_w8a8_rk3588.rkllm
- qwen3.5-2b-vision_rk3588.rknn
Copy both into this folder.
Once you have the two models, it is time to build your application.
You can use Code::Blocks.
- Load the project file *.cbp in Code::Blocks.
- Select Release, not Debug.
- Compile and run with F9.
- You can alter command line arguments with Project -> Set programs arguments...
Or use Cmake.
$ mkdir build
$ cd build
$ cmake ..
$ make -j4
The application switches dynamically between Single Image Mode and Video Sequence Mode based on how many image files you pass into the arguments.
./VLM_NPU RKNN_model RKLLM_model file1.jpg [file2.jpg file3.jpg ...]| Argument | Comment |
|---|---|
| RKNN_model | The visual encoder model (VLM) compiled for the NPU. |
| RKLLM_model | The large language model (LLM) compiled for the NPU. |
| file1.jpg ... | The images you want to process. Passing 1 file triggers Image Mode. Passing multiple files triggers Video Sequence Mode. |
In the context of the Rockchip RK3588 LLM (Large Language Model) library, NewTokens and ContextLength control the boundaries for text generation and memory allocation.
In main.cpp you will find the line:
RKLLM.LoadModel(vlm_model, llm_model, NewTokens, ContextLength);Here you set your context based on available memory.
NewTokens
This sets the maximum number of tokens (pieces of text, typically sub-word units) that the model is allowed to generate in response to a prompt during a single inference round. For example, if set to 300, the model will not return more than 300 tokens as output, regardless of the prompt length. It is important for controlling generation length to avoid run-on responses and manage resource use.
ContextLength (Dynamic KV Cache)
This specifies the maximum total number of tokens the model can hold in its memory at once, which includes the system prompt, the massive image/video embeddings, your text questions, and all previous generated answers.
We have synthesized the models with a larger KV Cache than normal. Ours can hold up to 16384 tokens!
-
For 32GB Boards (e.g., Rock 5C 32GB): You can safely push the KV Cache to
8192or16384to support processing long video sequences and maintaining deep, multi-turn conversations without the model forgetting the image.RKLLM.LoadModel(vlm_model, llm_model, 2048, 16384); -
For 8GB/16GB Boards: The KV cache is highly memory-intensive. You should keep this at
2048or4096. If you set this higher than your physical RAM can handle, the Linux Out-Of-Memory (OOM) killer will crash the application.RKLLM.LoadModel(vlm_model, llm_model, 2048, 4096);
Typical Command Line Examples:
Single Image Mode:
./VLM_NPU ./models/qwen3.5-2b-vision_rk3588.rknn ./models/qwen3.5-2b_w8a8_rk3588.rkllm ./frame1.jpg
Video Sequence Mode (Passing multiple frames):
./VLM_NPU ./models/qwen3.5-2b-vision_rk3588.rknn ./models/qwen3.5-2b_w8a8_rk3588.rkllm ./frame1.jpg ./frame2.jpg ./frame3.jpg
To process video input, individual frames are first extracted. The VLM converts each frame into embeddings, which are then transformed into vision tokens.
Even on a desktop PC, this process places a heavy load on memory and CUDA resources. It’s therefore no surprise that the Rock 5C, with its more limited hardware, struggles even more.
Each vision token corresponds to about 200 tokens, strongly limiting the number of frames processed per video. Therefore, the video is subsampled, and evenly spaced frames are extracted for processing by Qwen3.5.
For reference, each vision token occupies around 20 MB of RAM — a detail worth keeping in mind when working on systems with limited memory.
Keep also in mind that after loading the models, each frame has to be tokenised, which takes about 0.9 seconds per frame.
Using the application is simple. Once you provide the model and the media files, you can ask anything you want.
Remember, we are on a bare Rock 5C, so don't expect the same speed or quality as massive server-grade models like ChatGPT. On the other hand, as you will see in the examples below, the app performs amazingly well on the edge!
Interacting with Media:
- If you passed a single image and want to talk about it, you must include the
<image>tag in your prompt. (e.g.,"Describe this <image> in detail.") - If you passed multiple images (video sequence), you must use the
<video>tag instead. (e.g.,"What action is happening in this <video>?")
Chat Controls:
- The app remembers the dialogue context continuously. To wipe the model's memory and start a fresh conversation about the loaded media, type
clear. - To leave the application, type
exit.
Below, you find the surprisingly little code of main.cpp.
#include "RK35llm.h"
#include <vector>
int main(int argc, char** argv)
{
// Usage: ./VLM_VIDEO_NPU vlm_model llm_model frame1.jpg [frame2.jpg frame3.jpg ...]
if (argc < 4) {
std::cerr << "Usage: " << argv[0] << " vlm_model llm_model file1.jpg [file2.jpg file3.jpg ...]\n";
return -1;
}
std::string vlm_model = argv[1];
std::string llm_model = argv[2];
RK35llm RKLLM;
RKLLM.SetInfo(true);
RKLLM.SetSilence(false);
RKLLM.LoadModel(vlm_model, llm_model, 2048, 16384);
// Collect all image frames from arguments
std::vector<cv::Mat> frames;
for (int i = 3; i < argc; ++i) {
cv::Mat frame = cv::imread(argv[i]);
if (!frame.empty()) {
frames.push_back(frame);
} else {
std::cerr << "Warning: Could not load image file: " << argv[i] << "\n";
}
}
if (frames.empty()) {
std::cerr << "Error: No valid images loaded. Exiting.\n";
return -1;
}
// Dynamic routing: single image vs. video sequence
if (frames.size() == 1) {
std::cout << "\n[Info] Loading single image mode...\n";
RKLLM.LoadImage(frames[0]);
} else {
std::cout << "\n[Info] Loading video sequence mode (" << frames.size() << " frames)...\n";
RKLLM.LoadVideoFrames(frames);
}
std::string input_str;
std::string output_str;
while (true) {
printf("\nUser: ");
std::getline(std::cin, input_str);
if (input_str == "exit") break;
// Reminder: the user must input the correct tag (<image> or <video>) based on the mode!
output_str = RKLLM.Ask(input_str);
// std::cout << "\nLLM Reply: " << output_str << std::endl; }
return 0;
}Most code speaks for itself. One remark.
The LLM generates the answer to your request in little pieces of text. You see them as if the LLM is typing on your terminal.
RKLLM.SetSilence controls this behaviour. When set to true, it will suppress this output. RKLLM.Ask() also returns the complete answer.
In main.cpp uncomment this line:
std::cout << "\nLLM Answer: " << output_str << std::endl;
User: <video> Describe the video.
Answer: The video captures a dynamic scene inside what appears to be a martial arts dojo or training hall, characterized by light blue padded walls adorned with framed calligraphy and posters. The floor is covered in large, green mats typical for such environments.
In the foreground, an individual dressed in dark traditional attire—likely a black top and pants—is captured mid-motion. They are executing a powerful, acrobatic kick, possibly a high roundhouse or spinning kick, which creates significant motion blur due to the speed of the movement. Their body is twisted, with one leg extended high into the air while their other arm reaches out for balance.
In the background, another person wearing similar dark clothing stands upright near the wall, observing the action. This observer appears relatively still compared to the fast-moving practitioner. The overall atmosphere suggests a demonstration of martial arts skills, focusing on agility and technique within a controlled training space.
Notice the nice Markdown makeup of the answer!
User: Can you make me a C++ call that embeds the Pythagorean theorem?
Answer: Certainly! Here’s a clean, modern C++ function that computes the length of the hypotenuse using the Pythagorean theorem: a² + b² = c², so c = √(a² + b²).
#include <iostream>
#include <cmath> // for std::sqrt
// Function to compute the hypotenuse given two legs of a right triangle
double getHypotenuse(double a, double b) {
return std::sqrt(a * a + b * b);
}
int main() {
double leg1 = 3.0;
double leg2 = 4.0;
double hypotenuse = getHypotenuse(leg1, leg2);
std::cout << "Legs: " << leg1 << ", " << leg2 << std::endl;
std::cout << "Hypotenuse: " << hypotenuse << std::endl;
return 0;
}- We use
std::sqrt()to compute the square root of the sum of squares. - The function is modular and reusable — you can pass any two positive numbers as legs, and it will return the hypotenuse.
- In
main(), we test with classic 3-4-5 triangle values for clarity.
Legs: 3, 4
Hypotenuse: 5
Let me know if you’d like to extend this — e.g., add input validation, handle floating-point precision issues, or visualize the result!
To get a taste, try our professional Qwen3 AI-chatbot running on a Rock 5C: https://rock5gpt.qengineering.eu





