JPEG Decoder Behavior

JPEG Decoder Behavior

Feature Description

The JPEG Decoder behavior allows the user to decode JPEG images at runtime using the hardware decoder. This means that the pre-decoded bitmaps need not be included in the assets, reducing the overall asset size. JPEG images are compressed, making them smaller in size, and they can be decoded by supported platforms.

Supported Platforms

At present, the JPEG decoder is exclusively supported on the Infineon Traveo 2 platform.

Limitations

The JPEG Decoder Behavior currently has the following limitations.

• Single Image Decoding: Only one image can be decoded at a time.
• Preloaded Images in the asset only: The image must be part of the asset and cannot be dynamically supplied at runtime.
• Baseline JPEG with RGB Encoding: The JPEG decoder behavior only supports baseline JPEG images encoded in RGB format.
• Scene Editor cannot display the decoded image: The Scene Editor currently cannot display the decoded image; it is only viewable on the hardware.
  

How to use the JPEG Decoder

1. Import the jpeg image as raw resource: Using the import menu select ““Import Raw Resources”Resources”. This ensures that the image is available in its original format for further processing
   
   
   
   
2. Add the Bitmap node to the scene: Add a bitmap node to a 2D scene.
3. Add the Behavior to a Bitmap Node: Place the JPEG Decoder behavior onto a Bitmap Node in the scene.
   
   
   
   
4. Set the Resource Candera Name: Paste the Candera Name of the raw JPEG image into the Resource Candera Name property using the steps below.
   a. Step 1: Copy the Candera Name of the raw JPEG image from the Solution Explorer under the Asset properties of the JPEG resource.
   
   
   
   b. Step 2: Paste the Candera Name into the ResourceCanderaName property of the JPEG Decoder Behavior in the Properties panel.
   
   
   
   
5. Enable/Disable the Decoder: You can toggle the decoder using the enabled property.

Changes required inChoosing the correct toolchain file for cross-compilation

The path toIf the Infineon Traveo 2 JPEG decoder driverfeature mustis bebeing addedused, toensure that the correct toolchain file sincehas thebeen JPEGused. DecoderToolchain behavior uses this driver to decode the JPEG images. Add the following line to the cross-compilation toolchain file:
set(CGIDEVICE_TARGET_TRAVEO2_JPEG_DRIVER_PATH "path\to\jpeg\decoder\driver\root" CACHE PATH "Root path to the Traveo2 JPEG decoder driver.")
Ensure the following foldersfiles are available in the driverdirectory root path:
cgi_studio_devices\src\Traveo2\ToolchainFiles

Use

Bin\arm-none-ghs\productionone (\debugof orthe \release)following Source\jpgdec\includetwo Source\jpgdec\lib_includetoolchain files with

Buildingthe suffix _JPEG if using the JPEG decoder behavior so that the linker file dedicates a section for the JPEG Decoder Driveroutput. from

sourceMULTI-toolchain-Traveo2_C_6M_JPEG.txt (ifMULTI-toolchain-Traveo2_C_6MDDR_JPEG.txt
available)

In caseIf the JPEG decoder driver binaries areis not available,being itused, use the toolchain files that do not have the _JPEG suffix.

Changes in the linker_directives.ld file

The following two lines present in linker directives file create a jpeg decode buffer section to which the JPEG decoder will write the decoded image.

.jpeg_decode_buffer_base ALIGN(1) : > .
.jpeg_decode_buffer ALIGN(1) PAD(1M) : > . // JPEG decoder output

The size of the section and the location can be builtchanged fromaccording source as well, if available, followingto the stepstarget givenfor below.

Open "TVII_JPEG_Driver\Build\GHS\jpeg_driver\prj\jpeg_driver.gpj" in Multi Project Manager. Inwhich the toolbar, click on Build > Build Top Project jpeg_driver.gpj as shown in the image below

The JPEG Decoder driver can only be built in production environment, however, if the base application is being builtbuilt.
For example, in releasethe or6m debugDDR environment,board, copiesthe location of the Bin/arm-none-ghs/productionjpeg_decode_buffer foldersection can be createdinside andthe renamedLPDDR4_RAM area, however for the 6m board, it would have to releasebe in either SRAM or debugVRAM as(preferred).

required.

Example for 6m board

Example for 6m DDR board

Converting images to supported format

To ensure compatibility, you may need to convert your JPEG images to an RGB-encoded baseline JPEG format. Follow the steps below to install the necessary tools and use the conversion script.

Software Requirements

The conversion script uses djpeg and cjpeg utilities, which are part of the libjpeg-turbo software. You need to install them and make them accessible via your system’system’s PATH environment variable.

Installation Steps

1. Download libjpeg-turbo from this link (libjpeg-turbo).
2. Extract the downloaded files, install the exe and locate libjpeg-turbo-gcc64\bin.
3. Since libjpeg-turbo includes the necessary executables, its bin folder path must be added to the system's Environment Variables.
4. Add the folder path to your system’system’s Environment Variables:
   a. Open System Properties > Environment Variables.
   b. Under System Variables, find and edit the Path variable.
   c. Add the path to libjpeg-turbo-gcc64\bin.
   

Using the Conversion Script

The provided batch script, encode_jpeg_as_rgb.bat, automates the conversion of YCbCr JPEGs into RGB-encoded JPEGs. You simply drag and drop a JPEG file onto the script, and it processes the image automatically.

Steps for Conversion

1. Ensure libjpeg-turbo is installed and is accessible in PATH.
   
2. Place the batch script in a directory where your images are stored.
   
3. Drag and drop a JPEG file onto the script.
   
4. The script will generate a new file with _rgb appended to the filename.
   

Example Usage

• Input: sample.jpg (YCbCr format)
  
• Output: sample_rgb.jpg (RGB format)
  
• After running the script, the folder will look like this, with the converted images having '_rgb' appended to their filenames.
  
  

Verifying the Converted Images

To check if the image needs conversion, the following method can be used:

1. Install ffmpeg from the link: Download FFmpeg
   
2. Ensure the ffprobe command can be run on terminal by adding the path to the ffmpeg bin folder into the system PATH environment variable.
   
3. Open a terminal in the folder where the image is located and run the command ““ffprobe image_name.jpg”jpg”.
   
4. Ensure that the format of the image as displayed by the ffprobe command is (Baseline), gbrp. 
   
   

Even when run on single images, the ffprobe command will show the type as mjpeg.