• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 100 subscribers
  • Views 425 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

SK-AM62A-LP: SDK 9.0 Unable to use make commands to build kernel image sensor drivers

Steve T
Intellectual 290 points
Part Number: SK-AM62A-LP

Hello,

I've just started using the SDK 9.0 and I'm running into multiple issues trying to add and build additional image sensor module drivers for the OV5647 and AR0521 using the make commands. It looks like the online documentation hasn't changed from the 8.6 SDK version and I've been successfully adding and building image sensors overlays and drivers using the 8.6 SDK version . I've been following the instructions here: 

https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-edgeai/AM62AX/09_00_00/exports/docs/linux/Foundational_Components_Kernel_Users_Guide.html#compiler

So far I've diverted from them in the following ways to try and get modules and additional overlays to build:

Add build tool chain to the $PATH:

Fullscreen
1
export PATH=~/ti/AM62A/SDK-9_0/external-toolchain-dir/arm-gnu-toolchain-11.3.rel1-x86_64-aarch64-none-linux-gnu/bin:$PATH
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

Add overlay dtbs to the base Linux build directory Rules.make file:

Fullscreen
1
2
3
4
5
....
KERNEL_DEVICETREE?= ti/k3-am62a7-sk.dtb ti/k3-am62a7-sk-csi2-imx219.dtbo ti/k3-am62a7-sk-fusion.dtbo ti/k3-am62a7-sk-ethernet-dc01.dtbo ti/k3-am62a7-sk-csi2-ov5647.dtbo ti/k3-am62a7-sk-csi2-ar0521.dtbo
....
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

Created dtso overlays and updated the Makefile in the ".../arch/arm64/boot/dts/ti/" Linux build directory to mimic the imx219 image sensor:

Fullscreen
1
2
3
4
k3-am62a7-sk-csi2-ar0521-dtbs := k3-am62a7-sk.dtb k3-am62a7-sk-csi2-ar0521.dtbo
k3-am62a7-sk-csi2-ov5647-dtbs := k3-am62a7-sk.dtb k3-am62a7-sk-csi2-ov5647.dtbo
dtb-$(CONFIG_ARCH_K3) += k3-am62a7-sk-csi2-ar0521.dtb
dtb-$(CONFIG_ARCH_K3) += k3-am62a7-sk-csi2-ov5647.dtb
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

I'm able to build the device tree overlays successfully using the command "make ARCH=arm64 CROSS_COMPILE=aarch64-none-linux-gnu- dtbs"

The "make ARCH=arm64 CROSS_COMPILE=aarch64-none-linux-gnu- Image" command doesn't produce any errors but it is only showing a few build messages unlike the plethora it did with 8.6 version so I'm suspicious that it is working.

The "make ARCH=arm64 CROSS_COMPILE=aarch64-none-linux-gnu- modules" command produced prompted a lot of questions on inital run that I tried to answer as best as I could and then errored out in a way that I'm not sure how to fix:

Fullscreen
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
cad1@cad1-Ubuntu22:~/ti/AM62A/SDK-9_0/board-support/linux-6.1.33+gitAUTOINC+8f7f371be2-g8f7f371be2$ make ARCH=arm64 CROSS_COMPILE=aarch64-none-linux-gnu- modules
arch/arm64/Makefile:36: Detected assembler with broken .inst; disassembly will be unreliable
SYNC include/config/auto.conf.cmd
*
* Restart config...
*
*
* ARMv8.3 architectural features
*
Enable support for pointer authentication (ARM64_PTR_AUTH) [Y/n/?] y
Use pointer authentication for kernel (ARM64_PTR_AUTH_KERNEL) [Y/n/?] (NEW) Y
*
* ARMv8.4 architectural features
*
Enable support for the Activity Monitors Unit CPU extension (ARM64_AMU_EXTN) [Y/n/?] y
Enable support for tlbi range feature (ARM64_TLB_RANGE) [Y/n/?] (NEW)
*
* ARMv8.5 architectural features
*
Branch Target Identification support (ARM64_BTI) [Y/n/?] y
Enable support for E0PD (ARM64_E0PD) [Y/n/?] y
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX


I'm wondering if this is reproducible or I'm missing some kind of configuration still some where?

Thank you for your support,

Steve T

  • 0
    TI__Guru 65377 points
    Steve T said:
    I'm wondering if this is reproducible or I'm missing some kind of configuration still some where?

    Did you apply the default arm64 defconfig + the TI delta, as per SDK doc instructions, as your first step? This is always required, otherwise it is customary for the Kernel config tool to ask a lot of questions, which seems to be what's happening in your case.

    Fullscreen
    1
    make ARCH=arm64 CROSS_COMPILE=aarch64-none-linux-gnu- defconfig ti_arm64_prune.config
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    Regards, Andreas

  • 0 in reply to Andreas Dannenberg
    Intellectual 290 points

    Yes, I ran that command before trying to build the modules. Here is the output from running it:

    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    cad1@cad1-Ubuntu22:~/ti/AM62A/SDK-9_0/board-support/linux-6.1.33+gitAUTOINC+8f7f371be2-g8f7f371be2$ make ARCH=arm64 CROSS_COMPILE=aarch64-none-linux-gnu- defconfig ti_arm64_prune.config
    *** Default configuration is based on 'defconfig'
    #
    # configuration written to .config
    #
    Using .config as base
    Merging ./kernel/configs/ti_arm64_prune.config
    Value of CONFIG_ARCH_ACTIONS is redefined by fragment ./kernel/configs/ti_arm64_prune.config:
    Previous value: CONFIG_ARCH_ACTIONS=y
    New value: CONFIG_ARCH_ACTIONS=n
    Value of CONFIG_ARCH_SUNXI is redefined by fragment ./kernel/configs/ti_arm64_prune.config:
    Previous value: CONFIG_ARCH_SUNXI=y
    New value: CONFIG_ARCH_SUNXI=n
    Value of CONFIG_ARCH_ALPINE is redefined by fragment ./kernel/configs/ti_arm64_prune.config:
    Previous value: CONFIG_ARCH_ALPINE=y
    New value: CONFIG_ARCH_ALPINE=n
    Value of CONFIG_ARCH_APPLE is redefined by fragment ./kernel/configs/ti_arm64_prune.config:
    Previous value: CONFIG_ARCH_APPLE=y
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    Best Regards,

    Steve

  • +1 in reply to Steve T
    TI__Guru 65377 points

    Hm that's strange. Were you before trying to use/forward port an earlier, older defconfig file perhaps (from SDK v8.6)?

    Can you completely clean our your Kernel tree and try again (`make ARCH=arm64 mrproper`).

    Regards, Andreas

  • 0 in reply to Andreas Dannenberg
    Intellectual 290 points

    I'm using a fresh install of the required Ubuntu 22 and only have SDK 9 installed on the system so it shouldn't be affected by any other SDK.

    The mrproper make command appears to have fixed it after running the other commands from the start of the guide afterwards. I'm currently building the modules.

    I did run the following make commands before using the make command for the defconfig (as I didn't understand that to be an absolute requirement) so maybe that's what goofed it up:

    make ARCH=arm64 CROSS_COMPILE=aarch64-none-linux-gnu- dtbs
    make ARCH=arm64 CROSS_COMPILE=aarch64-none-linux-gnu- Image
    make ARCH=arm64 CROSS_COMPILE=aarch64-none-linux-gnu- modules
    make ARCH=arm64 CROSS_COMPILE=aarch64-none-linux-gnu- modules-install

    Thank you for your assistance to get it working!

    Best Regards,

    Steve T